cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Configuration SSO Work Managger 6.3 with SAP Mobile Platform 3.0 SP09

former_member192923
Participant

on ‎01-12-2017 1:22 PM

0 Kudos

Hi All,

Here is the landscape which we are using currently have a look it once.

But for us based on the CLUSTER information in SAP Mobile Platform Administrator and Monitoring Console (Web Console) we didn’t find any CLUSTER Information, please find below screenshot for more information, this is the first issue.

Now we have a Work Manager 6.3 application with having SSO and we deploy this app into first Instance1 of SMP server, after that it automatically created application directory in other Instance2 also well. Likewise i modified all required stuff in both(instance1 and instance2) JavaBE.ini and SSO related stuff as well. Also we follow few things to Configure SSO Work Manager 6.3 with SMP 3.0 SP09, after executed all required things i am not able to see anything in “BACKEND” section of Work Manager application in SMP Admin Console, please find the below screen for more information.

Same will happening in another instance(Instance2). Also i have checked in all Log files like smp server log, agentry related logs (startup, events), error and OSGi log also as well, after reviewing all logs i am not getting where and why issues/errors is occurring.
Please find the below JavaBE.ini files and all error logs in ERROR.txt file.

==================================
|| Instance1 – JavaBE.ini ||
==================================
[HOST]
server=********
;***********************
; mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10…etc
APPNAME=ZAP_WORK_MANAGER_63_EC41

[CONFIG]
; Used to get the SAP Configutaions from SAP if source=SAP or from JavaBE ini file
; SAP Configurations are [ENABLE_TABLE], [TABLE_CHECK], [TABLE_REFRESH], [BAPI_WRAPPER],
; [SAPOBJECT], [CT_SAPOBJECT], [CT_BAPI_WRAPPER], [CT_RETURN_TABLE], [CT_DELETE_TABLE]…..etc
source=SAP

[JCO]
CLASS=JCO3

[JCO3_CUSTOM_PROPERTIES]
; be careful with this section as it can be used to both extend and/or override base property values on the destination

#### example for group logon with SSO
;jco.client.ashost=
;jco.client.sysnr=
;jco.client.mshost=MESSAGE_HOST_NAME
;jco.client.r3name=R3_NAME
;jco.client.group=GROUP_NAME

##### example for snc login
;jco.client.snc_mode=1
;jco.client.snc_partnername=p:CN=SAPSERVER_NAME, O=ORG_NAME, C=COUNTRY_NAME
;jco.client.snc_myname=p:CN=SMPSERVER_NAME, O=ORG_NAME, C=COUNTRY_NAME
;jco.client.snc_qop=3
;jco.client.snc_lib=sapcrypto.dll
;jco.client.snc_sso=0

##### for extra debugging information
;jco.client.trace=1
;jco.client.cpic_trace=3

[TEST_LOGON]
UID=
UPASSWORD=
UGUID=
SERVERSERIALNUM=

; Service login user is used to get the SAP Configutaions from SAP if source=SAP
; Set ENABLED=true if source=SAP or ENABLED=false if source=INI
; If ENABLED=true, set the UID, UPASSWORD and SERVERSERIALNUM
; SERVERSERIALNUM is the Agentry server serial number
[SERVICE_LOGON]
ENABLED=true
UID=COMSMP
UPASSWORD=***********
UPASSWORDENCODED=false

SERVERSERIALNUM=SAP_WORK_MANAGER_63

[PUSH_LOGON]
ENABLED=true
UID=COMSMP
UPASSWORD=**************
UPASSWORDENCODED=false
SHAREDCONNECTION=10

[CLIENT_NUM]
CLIENT=500

[SYSTEM_NUM]
SYSNUM=00

[LANGUAGE]
LANG=ES

[LOGGING]
;1=Fatal, 2=Error, 3=Warning, 4=Info, 5=debug, 6=trace
Level=2

[LOGON_METHOD]
; USER_AUTH if standard UID/Password authentication is used
; USER_AUTH_GLOBAL if pooled connections using single UID/Password is used
; USER_AUTH_GROUP if UID/Password authentication with SAP Message Server
; (load balancing) is used
; USER_AUTH_SSO if SSO2 ticket authentication with SAP Portal Server is used
; USER_AUTH_CUSTOM for a custom login module setup
LOGON_METHOD=USER_AUTH_SSO
;LOGON_METHOD=USER_AUTH

[GLOBAL_LOGON]
; referenced when LOGON_METHOD=USER_AUTH_GLOBAL
; uses a pool of connections to the SAP backend all utilizing a single
; UID/password
UID=
UPASSWORD=
SHAREDCONNECTION=100

[GROUP_LOGON]
; referenced when LOGON_METHOD=USER_AUTH_GROUP
; individual user authentication using an SAP Message Server which distributes
; client connections among a “group” of SAP application servers based on load
; balancing criteria
;
UID=
UPASSWORD=
SHAREDCONNECTION=
; host name or IP address of SAP Message Server
MESSAGE_SERVER=
R3_NAME=
GROUP_NAME=
SYSTEM_ID=
CLIENT=
SHAREDCONNECTIONS=

[USER_AUTH_SSO]
; referenced when LOGON_METHOD=USER_AUTH_SSO
; SSO related information for use in LoginModuleSSO to facilitate login to
; an SAP system using tickets from a message server.
;
;***********************************
;*******************
PORTAL_URL=*************************

; verificaiton file from the portal. Not required, but if portal names are different from the authenticated username, it will be needed to decode the name.
VERIFICATION_USE=true
VERIFICATION_FILENAME=verifSSP.pse
;VERIFICATION_PASSWORD=
;VERIFICATION_PASSWORD_ENCODED=false

; key store for client authentication to the server if required
KEY_STORE_USE=false
;KEY_STORE_TYPE=WINDOWS-MY
;KEY_STORE_FILENAME=keystoreFileName
;KEY_STORE_PASSWORD=
;KEY_STORE_PASSWORD_ENCODED=false

; trust store for server authentication to the client (accepting only trusted servers to prevent MITM attacks)
TRUST_STORE_USE=true
TRUST_STORE_TYPE=WINDOWS-ROOT
;TRUST_STORE_FILENAME=truststoreFileName
;TRUST_STORE_PASSWORD=
;TRUST_STORE_PASSWORD_ENCODED=false

COOKIE=MYSAPSSO2
HTTPTYPE=http
SSL_VERSION=SSLv3
JAVA_SECURITY_DEBUG=true
JAVA_NET_DEBUG=true

; classes to instantiate for the sso client and the callback handler
SSOCLIENT_CLASS=com.syclo.sap.auth.sso.SSOClient
CALLBACK_HANDLER_CLASS=com.syclo.sap.auth.CallbackHandler

ALTERNATE_USERNAME_INDEX_USE=true
;ALTERNATE_USERNAME_INDEX=0
BYPASS_USERID_CHECK=true

;SAPCRYPTO_FILENAME=C:\\Windows\\System32\\sapcrypto.dll

[USER_AUTH_CUSTOM]
; referenced when LOGON_METHOD=USER_AUTH_CUSTOM
; custom defined login configuration that use JAAS for authentication
;
MODULE_CLASS_1=com.syclo.sap.auth.LoginModuleBasic
MODULE_CLASS_1_FLAG=REQUIRED
MODULE_CLASS_1_OPTION_1_KEY=CLIENT_NUM
MODULE_CLASS_1_OPTION_1_VALUE=clientNum
MODULE_CLASS_1_OPTION_2_KEY=HOST
MODULE_CLASS_1_OPTION_2_VALUE=serverHostName
MODULE_CLASS_1_OPTION_3_KEY=SYS_NUM
MODULE_CLASS_1_OPTION_3_VALUE=sysNum

;MODULE_CLASS_2=
;MODULE_CLASS_2_FLAG=
;
;MODULE_CLASS_3=
;MODULE_CLASS_3_FLAG=

; class to instantiate for the callback handler
CALLBACK_HANDLER_CLASS=com.syclo.sap.auth.CallbackHandler

[REQUIRED_BAPI_WRAPPER]
com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK
com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT
com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET
com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET
com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD
com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD
com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET
com.syclo.sap.bapi.GetEmployeeDataBAPI=/SMERP/HR_DOEMPLOYEE_DATA_GET
com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL
com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET
com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD
com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT
com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL
com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT
com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL
com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.SignatureCaptureBAPI=/SMERP/CORE_DOBDSDOCUMENT_CRT

[REQUIRED_BAPI_CLASS_MAPPING]
ChangePasswordBAPI=com.syclo.sap.bapi.ChangePasswordBAPI
CTBAPI=com.syclo.sap.bapi.CTBAPI
CTConfirmationBAPI=com.syclo.sap.bapi.CTConfirmationBAPI
DTBAPI=com.syclo.sap.bapi.DTBAPI
GetEmployeeDataBAPI=com.syclo.sap.bapi.GetEmployeeDataBAPI
GetUserDetailBAPI=com.syclo.sap.bapi.GetUserDetailBAPI
GetUserProfileDataBAPI=com.syclo.sap.bapi.GetUserProfileDataBAPI
LoginCheckBAPI=com.syclo.sap.bapi.LoginCheckBAPI
PushClearUserQueueBAPI=com.syclo.sap.bapi.PushClearUserQueueBAPI
PushResetUserQueueBAPI=com.syclo.sap.bapi.PushResetUserQueueBAPI
PushStatusUpdateBAPI=com.syclo.sap.bapi.PushStatusUpdateBAPI
RemoteObjectCreateBAPI=com.syclo.sap.bapi.RemoteObjectCreateBAPI
RemoteObjectDeleteBAPI=com.syclo.sap.bapi.RemoteObjectDeleteBAPI
RemoteObjectGetBAPI=com.syclo.sap.bapi.RemoteObjectGetBAPI
RemoteParameterGetBAPI=com.syclo.sap.bapi.RemoteParameterGetBAPI
RemoteReferenceCreateBAPI=com.syclo.sap.bapi.RemoteReferenceCreateBAPI
RemoteReferenceDeleteBAPI=com.syclo.sap.bapi.RemoteReferenceDeleteBAPI
RemoteReferenceGetBAPI=com.syclo.sap.bapi.RemoteReferenceGetBAPI
RemoteUserCreateBAPI=com.syclo.sap.bapi.RemoteUserCreateBAPI
RemoteUserDeleteBAPI=com.syclo.sap.bapi.RemoteUserDeleteBAPI
SignatureCaptureBAPI=com.syclo.sap.bapi.SignatureCaptureBAPI
SystemInfoBAPI=com.syclo.sap.bapi.SystemInfoBAPI

====================================
|| Instance2 – JavaBE.ini ||
====================================
[HOST]
server=*************
;********************************
; mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10…etc
APPNAME=ZAP_WORK_MANAGER_63_EC41

[CONFIG]
; Used to get the SAP Configutaions from SAP if source=SAP or from JavaBE ini file
; SAP Configurations are [ENABLE_TABLE], [TABLE_CHECK], [TABLE_REFRESH], [BAPI_WRAPPER],
; [SAPOBJECT], [CT_SAPOBJECT], [CT_BAPI_WRAPPER], [CT_RETURN_TABLE], [CT_DELETE_TABLE]…..etc
source=SAP

[JCO]
CLASS=JCO3

[JCO3_CUSTOM_PROPERTIES]
; be careful with this section as it can be used to both extend and/or override base property values on the destination

#### example for group logon with SSO
;jco.client.ashost=
;jco.client.sysnr=
;jco.client.mshost=MESSAGE_HOST_NAME
;jco.client.r3name=R3_NAME
;jco.client.group=GROUP_NAME

##### example for snc login
;jco.client.snc_mode=1
;jco.client.snc_partnername=p:CN=SAPSERVER_NAME, O=ORG_NAME, C=COUNTRY_NAME
;jco.client.snc_myname=p:CN=SMPSERVER_NAME, O=ORG_NAME, C=COUNTRY_NAME
;jco.client.snc_qop=3
;jco.client.snc_lib=sapcrypto.dll
;jco.client.snc_sso=0

##### for extra debugging information
;jco.client.trace=1
;jco.client.cpic_trace=3

[TEST_LOGON]
UID=
UPASSWORD=
UGUID=
SERVERSERIALNUM=

; Service login user is used to get the SAP Configutaions from SAP if source=SAP
; Set ENABLED=true if source=SAP or ENABLED=false if source=INI
; If ENABLED=true, set the UID, UPASSWORD and SERVERSERIALNUM
; SERVERSERIALNUM is the Agentry server serial number
[SERVICE_LOGON]
ENABLED=true
UID=COMSMP
UPASSWORD=*********************
UPASSWORDENCODED=false

SERVERSERIALNUM=SAP_WORK_MANAGER_63

[PUSH_LOGON]
ENABLED=true
UID=COMSMP
UPASSWORD=***************
UPASSWORDENCODED=false
SHAREDCONNECTION=10

[CLIENT_NUM]
CLIENT=500

[SYSTEM_NUM]
SYSNUM=00

[LANGUAGE]
LANG=ES

[LOGGING]
;1=Fatal, 2=Error, 3=Warning, 4=Info, 5=debug, 6=trace
Level=2

[LOGON_METHOD]
; USER_AUTH if standard UID/Password authentication is used
; USER_AUTH_GLOBAL if pooled connections using single UID/Password is used
; USER_AUTH_GROUP if UID/Password authentication with SAP Message Server
; (load balancing) is used
; USER_AUTH_SSO if SSO2 ticket authentication with SAP Portal Server is used
; USER_AUTH_CUSTOM for a custom login module setup
LOGON_METHOD=USER_AUTH_SSO
;LOGON_METHOD=USER_AUTH

[GLOBAL_LOGON]
; referenced when LOGON_METHOD=USER_AUTH_GLOBAL
; uses a pool of connections to the SAP backend all utilizing a single
; UID/password
UID=
UPASSWORD=
SHAREDCONNECTION=100

[GROUP_LOGON]
; referenced when LOGON_METHOD=USER_AUTH_GROUP
; individual user authentication using an SAP Message Server which distributes
; client connections among a “group” of SAP application servers based on load
; balancing criteria
;
UID=
UPASSWORD=
SHAREDCONNECTION=
; host name or IP address of SAP Message Server
MESSAGE_SERVER=
R3_NAME=
GROUP_NAME=
SYSTEM_ID=
CLIENT=
SHAREDCONNECTIONS=

[USER_AUTH_SSO]
; referenced when LOGON_METHOD=USER_AUTH_SSO
; SSO related information for use in LoginModuleSSO to facilitate login to
; an SAP system using tickets from a message server.
;
;PORTAL_URL=*****************
;PORTAL_URL=**********************
PORTAL_URL=******************************
; verificaiton file from the portal. Not required, but if portal names are different from the authenticated username, it will be needed to decode the name.
VERIFICATION_USE=true
VERIFICATION_FILENAME=verifSSP.pse
;VERIFICATION_PASSWORD=
;VERIFICATION_PASSWORD_ENCODED=false

; key store for client authentication to the server if required
KEY_STORE_USE=false
;KEY_STORE_TYPE=WINDOWS-MY
;KEY_STORE_FILENAME=keystoreFileName
;KEY_STORE_PASSWORD=
;KEY_STORE_PASSWORD_ENCODED=false

; trust store for server authentication to the client (accepting only trusted servers to prevent MITM attacks)
TRUST_STORE_USE=true
TRUST_STORE_TYPE=WINDOWS-ROOT
;TRUST_STORE_FILENAME=truststoreFileName
;TRUST_STORE_PASSWORD=
;TRUST_STORE_PASSWORD_ENCODED=false

COOKIE=MYSAPSSO2
HTTPTYPE=http
SSL_VERSION=SSLv3
JAVA_SECURITY_DEBUG=true
JAVA_NET_DEBUG=true

; classes to instantiate for the sso client and the callback handler
SSOCLIENT_CLASS=com.syclo.sap.auth.sso.SSOClient
CALLBACK_HANDLER_CLASS=com.syclo.sap.auth.CallbackHandler

ALTERNATE_USERNAME_INDEX_USE=true
;ALTERNATE_USERNAME_INDEX=0
BYPASS_USERID_CHECK=true

;SAPCRYPTO_FILENAME=C:\\Windows\\System32\\sapcrypto.dll

[USER_AUTH_CUSTOM]
; referenced when LOGON_METHOD=USER_AUTH_CUSTOM
; custom defined login configuration that use JAAS for authentication
;
MODULE_CLASS_1=com.syclo.sap.auth.LoginModuleBasic
MODULE_CLASS_1_FLAG=REQUIRED
MODULE_CLASS_1_OPTION_1_KEY=CLIENT_NUM
MODULE_CLASS_1_OPTION_1_VALUE=clientNum
MODULE_CLASS_1_OPTION_2_KEY=HOST
MODULE_CLASS_1_OPTION_2_VALUE=serverHostName
MODULE_CLASS_1_OPTION_3_KEY=SYS_NUM
MODULE_CLASS_1_OPTION_3_VALUE=sysNum

;MODULE_CLASS_2=
;MODULE_CLASS_2_FLAG=
;
;MODULE_CLASS_3=
;MODULE_CLASS_3_FLAG=

; class to instantiate for the callback handler
CALLBACK_HANDLER_CLASS=com.syclo.sap.auth.CallbackHandler

[REQUIRED_BAPI_WRAPPER]
com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK
com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT
com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET
com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET
com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD
com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD
com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET
com.syclo.sap.bapi.GetEmployeeDataBAPI=/SMERP/HR_DOEMPLOYEE_DATA_GET
com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL
com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET
com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD
com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT
com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL
com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT
com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL
com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.SignatureCaptureBAPI=/SMERP/CORE_DOBDSDOCUMENT_CRT

[REQUIRED_BAPI_CLASS_MAPPING]
ChangePasswordBAPI=com.syclo.sap.bapi.ChangePasswordBAPI
CTBAPI=com.syclo.sap.bapi.CTBAPI
CTConfirmationBAPI=com.syclo.sap.bapi.CTConfirmationBAPI
DTBAPI=com.syclo.sap.bapi.DTBAPI
GetEmployeeDataBAPI=com.syclo.sap.bapi.GetEmployeeDataBAPI
GetUserDetailBAPI=com.syclo.sap.bapi.GetUserDetailBAPI
GetUserProfileDataBAPI=com.syclo.sap.bapi.GetUserProfileDataBAPI
LoginCheckBAPI=com.syclo.sap.bapi.LoginCheckBAPI
PushClearUserQueueBAPI=com.syclo.sap.bapi.PushClearUserQueueBAPI
PushResetUserQueueBAPI=com.syclo.sap.bapi.PushResetUserQueueBAPI
PushStatusUpdateBAPI=com.syclo.sap.bapi.PushStatusUpdateBAPI
RemoteObjectCreateBAPI=com.syclo.sap.bapi.RemoteObjectCreateBAPI
RemoteObjectDeleteBAPI=com.syclo.sap.bapi.RemoteObjectDeleteBAPI
RemoteObjectGetBAPI=com.syclo.sap.bapi.RemoteObjectGetBAPI
RemoteParameterGetBAPI=com.syclo.sap.bapi.RemoteParameterGetBAPI
RemoteReferenceCreateBAPI=com.syclo.sap.bapi.RemoteReferenceCreateBAPI
RemoteReferenceDeleteBAPI=com.syclo.sap.bapi.RemoteReferenceDeleteBAPI
RemoteReferenceGetBAPI=com.syclo.sap.bapi.RemoteReferenceGetBAPI
RemoteUserCreateBAPI=com.syclo.sap.bapi.RemoteUserCreateBAPI
RemoteUserDeleteBAPI=com.syclo.sap.bapi.RemoteUserDeleteBAPI
SignatureCaptureBAPI=com.syclo.sap.bapi.SignatureCaptureBAPI
SystemInfoBAPI=com.syclo.sap.bapi.SystemInfoBAPI

==================================
|| ERROR.txt ||
==================================

********-smp-server.log
======================================
2017 01 10 10:01:26#0-600#INFO#System.out###Agentry Dev Def Load Loop Thread######## |
2017 01 10 10:01:26#0-600#ERROR#com.sap.mobile.platform.server.agentry.console###Agentry Dev Def Load Loop Thread########Exception: 10:01:26 01/10/2017 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Could not login user COMSMP – com.syclo.sap.auth.sso.TicketVerifierException: MySapEvalLogonTicketEx failed: standard error= 20, ssf error= 25 – Signature couldn’t be verified (20) – Invalid password for signer (25)
), at com.syclo.sap.auth.LoginModuleSSO.verifyTicket(LoginModuleSSO.java:241)
|
2017 01 10 10:01:31#0-600#INFO#System.out###SMPServerStatusManager########SMPServerStatusManager: 126 of 129 tracked bundles have initialized. |

Agentry startup.log
============================================
10:01:08 01/10/2017: Exception: 10:01:08 01/10/2017 : 27 (LocalizationException), Localization Exception (Skipping the ‘en’ localization because no matching override files were found. ), agent\ChickamingAgent.cpp#3414:ChickamingAgent::initializeLocalizations
10:01:09 01/10/2017: Event: 20, 150, Loading Development application definitions
10:01:24 01/10/2017: Initializing HTTPXML-HTTPXMLSystemConnection from ag3httpxmlbe.dll
10:01:24 01/10/2017: HTTPXMLSystemConnection: Reading configuration information.
10:01:24 01/10/2017: HTTPXMLSystemConnection: Setting name to ‘HTTP-XML Back End’.
10:01:24 01/10/2017: HTTP-XML Back End: Initialized.
10:01:24 01/10/2017: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v130.9.3.10) from ag3httpxmlbe.dll
10:01:24 01/10/2017: Initializing Java-SAPJavaConnection from ag3javabe.dll
10:01:24 01/10/2017: SAPJavaConnection: Reading configuration information.
10:01:24 01/10/2017: SAPJavaConnection: Setting name to ‘Java Back End’.
10:01:24 01/10/2017: Java Back End: Initialized.
10:01:24 01/10/2017: Java Back End: Java Virtual Machine already initialized.
10:01:26 01/10/2017: Exception: 10:01:26 01/10/2017 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Could not login user COMSMP – com.syclo.sap.auth.sso.TicketVerifierException: MySapEvalLogonTicketEx failed: standard error= 20, ssf error= 25 – Signature couldn’t be verified (20) – Invalid password for signer (25)
), at com.syclo.sap.auth.LoginModuleSSO.verifyTicket(LoginModuleSSO.java:241)10:01:26 01/10/2017: Failed to init Java Back End (Java v130.9.3.10) from ag3javabe.dll
10:01:26 01/10/2017: Event: 20, 151, Application definitions failed to load. Either the publish has not completed or there is a server misconfiguration. Please check server log for details.
10:01:27 01/10/2017: com.sap.wm63_ec41: Starting threads.
10:01:27 01/10/2017: 1 initial threads. Threads will auto-scale.
10:01:27 01/10/2017: Event: 20, 4, com.sap.wm63_ec41 v130.9.3.10
10:01:27 01/10/2017: Event: 0, 0, Old log files moved into D:\SAP\MobilePlatform3\Server\log\agentry\rolled\2017-01-10-100108
10:01:27 01/10/2017: Event: 0, 23, Agentry startup is complete.

Agentry events.log
=======================================================
01/10/2017 10:01:08, 0, 0, 0, Thr 7384, New files opened events.log, messages.log
01/10/2017 10:01:08, 0, 0, 2, Thr 7384, Loading the Agentry Runtime’s public/private key for password exchanges.
01/10/2017 10:01:08, 0, 0, 2, Thr 7384, Key pair loaded successfully.
01/10/2017 10:01:08, 0, 0, 2, Thr 7384, Agentry Startup
01/10/2017 10:01:08, 0, 1, 4, Thr 7384, Agentry Server Agent v130.9.3.10
01/10/2017 10:01:08, 1, 27, 3, Thr 7384, Skipping the ‘en’ localization because no matching override files were found. agent\ChickamingAgent.cpp#3414:ChickamingAgent::initializeLocalizations
01/10/2017 10:01:09, 0, 20, 150, Thr 8200, Loading Development application definitions
01/10/2017 10:01:24, 0, 24, 4, Thr 8200, Loaded HTTP-XML Back End (HTTPXML v130.9.3.10) from ag3httpxmlbe.dll
01/10/2017 10:01:26, 1, 20, 18, Thr 8200, JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Could not login user COMSMP – com.syclo.sap.auth.sso.TicketVerifierException: MySapEvalLogonTicketEx failed: standard error= 20, ssf error= 25 – Signature couldn’t be verified (20) – Invalid password for signer (25)
at com.syclo.sap.auth.LoginModuleSSO.verifyTicket(LoginModuleSSO.java:241)
at com.syclo.sap.auth.LoginModuleSSO.login(LoginModuleSSO.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:587)
at com.syclo.sap.User.handleJAASLogin(User.java:2735)
at com.syclo.sap.User.initSession(User.java:868)
at com.syclo.sap.Server.login(Server.java:490)
at com.syclo.sap.Server.createServiceUser(Server.java:1780)
at com.syclo.sap.Server.getServiceUser(Server.java:1905)
at com.syclo.sap.Server.loadSAPProperties(Server.java:865)
at com.syclo.sap.Server.initServer(Server.java:297)
at com.syclo.sap.Server.<init>(Server.java:272)
at com.syclo.sap.workmanager.Server.<init>(Server.java:30)

01/10/2017 10:01:26, 0, 20, 151, Thr 8200, Application definitions failed to load. Either the publish has not completed or there is a server misconfiguration. Please check server log for details.
01/10/2017 10:01:27, 0, 20, 4, Thr 7384, com.sap.wm63_ec41 v130.9.3.10
01/10/2017 10:01:27, 0, 0, 0, Thr 7384, Old log files moved into D:\SAP\MobilePlatform3\Server\log\agentry\rolled\2017-01-10-100108
01/10/2017 10:01:27, 0, 0, 23, Thr 7384, Agentry startup is complete.

osgi.log
===============================================
!ENTRY com.sap.gw.rt.com.sap.rhino.engine 4 0 2017-01-10 09:55:37.388
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Exception in com.sap.gateway.js.engine.Activator.JSActivator.stop() of bundle com.sap.gw.rt.com.sap.rhino.engine.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:791)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692)
at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundle$1.run(InternalSystemBundle.java:261)
at java.lang.Thread.run(Thread.java:812)
Caused by: java.lang.NullPointerException: while trying to invoke the method org.eclipse.wst.jsdt.debug.rhino.debugger.RhinoDebugger.stop() of a null object loaded from field com.sap.gateway.js.engine.Activator.JSActivator.debugger of an object loaded from local variable ‘this’
at com.sap.gateway.js.engine.Activator.JSActivator.stop(JSActivator.java:31)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764)
… 11 more
Root exception:
java.lang.NullPointerException: while trying to invoke the method org.eclipse.wst.jsdt.debug.rhino.debugger.RhinoDebugger.stop() of a null object loaded from field com.sap.gateway.js.engine.Activator.JSActivator.debugger of an object loaded from local variable ‘this’
at com.sap.gateway.js.engine.Activator.JSActivator.stop(JSActivator.java:31)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692)
at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundle$1.run(InternalSystemBundle.java:261)
at java.lang.Thread.run(Thread.java:812)
!SESSION Tue Jan 10 10:00:18 CST 2017 ——————————————
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.110
!MESSAGE SMP-INIT-001 SAP Mobile Server – Checking DB…
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.375
!MESSAGE SMP-INIT-001 SAP Mobile Server – DB connection successful.
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.391
!MESSAGE SMP-INIT-002 SAP Mobile Server – cluster name:MXOCCSAPMDP01.NOAM.CEMEXNET.COM-5000-asemdp-aseadminprd cluster version:3.0.9.4 supported versions:3.0.9.4
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.391
!MESSAGE SMP-INIT-002 SAP Mobile Server – Succeeded Version Check.
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.391
!MESSAGE SMP-INIT-001 SAP Mobile Server – DB status check to process DML successful.
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.672
!MESSAGE applying configuration from database to context:com.sap.mobile.platform.server.mobilink
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.672
!MESSAGE No SMPConfigApplier found for context: com.sap.mobile.platform.server.mobilink
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.672
!MESSAGE applying configuration from database to context:/config_master/connection_data/connection.properties
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.672
!MESSAGE applying configuration from database to context:/props.ini
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.687
!MESSAGE applying configuration from database to context:/config_master/org.eclipse.gemini.web.tomcat/default-server.xml
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.734
!MESSAGE applying configuration from database to context:com.sap.mobile.platform.server.agentry.apprestart
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.734
!MESSAGE No SMPConfigApplier found for context: com.sap.mobile.platform.server.agentry.apprestart
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.734
!MESSAGE applying configuration from database to context:configuration/com.sap.mobile.platform.server.launcher/config-sys.properties
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.750
!MESSAGE SMP-INIT-003 SAP Mobile Server – Checking tcp ports…
!ENTRY org.eclipse.equinox.launcher 4 0 2017-01-10 10:00:18.765
!MESSAGE SMP-INIT-003 SAP Mobile Server – TCP ports check successfully.
!SESSION 2017-01-10 10:00:18.765 ———————————————–
eclipse.buildId=unknown
java.version=1.8.0_45
java.vendor=SAP AG
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments: -console localhost:2401

!ENTRY org.eclipse.osgi 2 1 2017-01-10 10:00:29.748
!MESSAGE NLS missing message: CollaborationExtensionCheck_101 in: com.sap.it.ifl.core.checks.messages

!ENTRY org.eclipse.osgi 2 1 2017-01-10 10:00:29.748
!MESSAGE NLS missing message: CollaborationExtensionCheck_106 in: com.sap.it.ifl.core.checks.messages

!ENTRY org.eclipse.osgi 2 1 2017-01-10 10:00:29.748
!MESSAGE NLS missing message: CollaborationExtensionCheck_74 in: com.sap.it.ifl.core.checks.messages

!ENTRY org.eclipse.osgi 2 1 2017-01-10 10:00:29.748
!MESSAGE NLS missing message: CollaborationExtensionCheck_86 in: com.sap.it.ifl.core.checks.messages

!ENTRY org.eclipse.osgi 2 1 2017-01-10 10:00:29.748
!MESSAGE NLS missing message: CollaborationExtensionCheck_91 in: com.sap.it.ifl.core.checks.messages


Please help me to resolve the issue.

Thanks,
Ranjith Lingala

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member192923
Participant
‎01-19-2017 11:51 AM
0 Kudos

Hi All,

Yes @Mark Pe that is true it's dev mode, as i can try to modify and replace the Agentry.ini but after restarting the SMP Server again it's same as like dev only. What i observe is in Agentry.ini one of the parameter "developmentServer" value is always "True". I am not sure from where it's picking up.

We tried to make it False, but after restarting the Server again it back with True only.

startup.log
21:30:24 01/18/2017: Java Back End: Initialized.
21:30:24 01/18/2017: Java Back End: Java Virtual Machine already initialized.
21:30:25 01/18/2017: Exception: 21:30:25 01/18/2017 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Could not login user USER1 - com.syclo.sap.auth.sso.TicketVerifierException: MySapEvalLogonTicketEx failed: standard error= 5, ssf error= 27 - Ticket syntactically invalid (5) - Signature invalid or operation not OK for signer (27)
), at com.syclo.sap.auth.LoginModuleSSO.verifyTicket(LoginModuleSSO.java:216)
-----------------------------------
*********-smp-server.og
2017 01 18 21:30:25#0-600#INFO#System.out###Agentry Dev Def Load Loop Thread######## at com.syclo.sap.workmanager.Server.<init>(Server.java:30) |
2017 01 18 21:30:25#0-600#INFO#System.out###Agentry Dev Def Load Loop Thread######## |
2017 01 18 21:30:25#0-600#ERROR#com.sap.mobile.platform.server.agentry.console###Agentry Dev Def Load Loop Thread########Exception: 21:30:25 01/18/2017 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Could not login user USER1 - com.syclo.sap.auth.sso.TicketVerifierException: MySapEvalLogonTicketEx failed: standard error= 5, ssf error= 27 - Ticket syntactically invalid (5) - Signature invalid or operation not OK for signer (27)
), at com.syclo.sap.auth.LoginModuleSSO.verifyTicket(LoginModuleSSO.java:216)
|
2017 01 18 21:30:28#0-600#INFO#System.out###SMPServerStatusManager########SMPServerStatusManager: 126 of 129 tracked bundles have initialized. |

---------------------------------

Above is the ERRORs we have in Agentry startup.log and smp-server.log.

Also i tried to delete application from SMP Web Admin Console to start from the scratch again, but application not deleting completely.

Please have a look and help to resolve the issue.

Thanks,

Ranjith Lingala

+91-9985241328

Show replies
Show replies
former_member192923
Participant
‎01-17-2017 9:00 AM
0 Kudos

@Mark Pe, Thanks for you response.

We tried to resolve this issue by checking one by one, in one of the below step i need to more clarification.

In above Yellow mark sentence stating that Agentry.ini file is in Development mode, so how will change it to Production.

Can you explain little bit more on that.

Show replies
Show replies
mark_pe
Active Contributor
‎01-13-2017 9:38 PM
0 Kudos

Ranjith,

Hi. Thank you for opening this thread tied to your specific issue.

Let us try to break it down.

1) You have issues with Backend - loading. This means that the application.zip file when presented to SMP is having issues connecting to your ECC.

A) Issues here are tied to your javaBE.ini or Agentry.ini inside this application.zip file.

Let us assume that you did not configure your SSO correctly and during startup SMP cannot connect to ECC properly so this can be one area wherein your configuration on SSO may be questionable.

Please refer to the SSO documentation in this link:

https://websmp102.sap-ag.de/~sapidb/012002523100015043802016E/WM641_Install.pdf

2) I noticed this in your logs: Explanation why cluster is not working

~~~~~~~your logs~~~~~~~~~

2017 01 10 10:01:26#0-600#INFO#System.out###Agentry Dev Def Load Loop Thread######## |
2017 01 10 10:01:26#0-600#ERROR#com.sap.mobile.platform.server.agentry.console###Agentry Dev Def Load Loop Thread########Exception: 10:01:26 01/10/2017 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Could not login user COMSMP – com.syclo.sap.auth.sso.TicketVerifierException: MySapEvalLogonTicketEx failed: standard error= 20, ssf error= 25 – Signature couldn’t be verified (20) – Invalid password for signer (25)
), at com.syclo.sap.auth.LoginModuleSSO.verifyTicket(LoginModuleSSO.java:241)

~~~~~~~~~~end~~~~~~~~~~~

Keywords: ""Agentry Dev Def Load Loop" - states you are in dev mode. This is still using Agentry.ini configuration and this means it cannot be used with the cockpit or clustering.

Reference:

The links above will explain why you may not see clustered nodes or pasted herein

"In SMP 3.0 SP03 there was an SMP architectural change to support clusters. The Agentry configurations (setup in the agentry.ini) are now stored in the SMP data store and available to Agentry cluster nodes (or all server nodes), so the standalone agentry.ini is no longer needed in production" <-- SMP 3.0. It seems you are still using dev mode and this is probably or most likely the reason you do not see it. Try to work in production mode of Agentry.

3) Lastly, your Backend is empty means that on startup the SMP 3.0 was not successful to connect to ECC. There is something wrong with your javaBE.ini or agentry.ini if that is the case. If the named server is not working try IP address but refer to the WM641_Install.pdf for pictured examples.

Hope this helps,

Mark Pe - SAP Platinum Support Engineer

Show replies
Show replies
Ask a Question