Skip to Content

If you are the first time to use the work manager application, especially for 6.3 version, this quick start guide about Work Manager 6.3.x deployment will be good for you to start.

Note: All the contents of this article are the minimum requirement on this topic.

Prerequisites:

  1. Fully installed in the SAP Mobile Platform
  2. Start the SMP 3.0 Services and make sure the SAP Management Cockpit is active
  3. User configured the SAP Add-on for Work Manager 6.3 (it is similar with Work Manager 6.2, so you can also check the link – http://scn.sap.com/community/mobile/blog/2014/12/04/work-manager-62)

Test Environment:

SAP Mobile Platform 3.0 SP10

Work Manager 6.3.x

WPF Agentry Client v70.11.0

Step by Step guide:

Download the Work Manager 6.3 from SAP ONE Support Launchpad following the link below.

https://launchpad.support.sap.com/#/softwarecenter

Each available software to be downloaded are standalone. For example: Deployment, Crew Management or Meter Management. Users has to choose which one they want and work on it from there.

/wp-content/uploads/2016/05/1_962832.jpg

Unzip the installation file and run the workmanager.server-6.3.0.exe

/wp-content/uploads/2016/05/image003_971919.png

Enter the Work Manager Backend Server address, Client number, Sys Number and User information, and then select directory to generate the application.

/wp-content/uploads/2016/05/image005_971920.png
/wp-content/uploads/2016/05/image007_971987.png

/wp-content/uploads/2016/05/image009_971988.png

During the installation, the workmanager.server-6.3.0.exe will produce the SAP Work Manager 6.3.x application definition, libraries and other configuration files in a zip file “SAPWorkMgr630Deployment-20151103.0552.zip” that will be used in the SAP Mobile Platform Management Cockpit.


Ini files – Configuration files used in Work Manager 6.3, for example: JavaBE.ini file will include the backend connection information that we just input in the previous step;  Java folder will include many *.jar files – Java class files used to interface with SAP backend;
/wp-content/uploads/2016/05/image011_971989.png

Open the SMP Management Cockpit and create a new application with type “Agentry” and set the Authentication providers with ‘No Authentication Challenge” option.

/wp-content/uploads/2016/05/image013_945460.png

/wp-content/uploads/2016/05/image014_971990.png

Save the application and the Agentry application node will be created under the SMP configuration folder, generic ini configuration files area would be generated.

/wp-content/uploads/2016/05/image016_971992.png

Restart the SMP server, check the startup.log and you can see the message about there is no application and backend loaded yet for this new application. Once Restarted, open the application in the management cockpit and navigate to “APP SPECIFIC SETTINGS”, press the Browse button to import the application zip file “SAPWorkMgr630Deployment-20151103.0552.zip” under Publish tab.

/wp-content/uploads/2016/05/image018_971983.png

After loading the application zip file, the backend will be shown in the configuration screen and include the contents in the Agentry.ini file before.

Note: sapsso.jar is only for sso setup and is not part of the out of box deployment files.

/wp-content/uploads/2016/05/image020_971993.png

Save the application and restart SMP server. Check startup.log and event.log, make sure the work manager 6.3 application has been loaded successfully in the SMP/Agentry Server.

/wp-content/uploads/2016/05/image022_971994.png/wp-content/uploads/2016/05/image024_971995.png

Check from IE if you can connect the application in the SMP and see “I am here” by typing https://SMPServerAddress:8081/ApplicationName, open the SMP cockpit and navigate to the configuration screen of this Agentry application, then you can get the application name from the ‘urlPath’ field under APP SPECIFIC SETTINGS.

/wp-content/uploads/2016/05/image026_971996.png

/wp-content/uploads/2016/05/image028_971997.png

During the SMP 3.0 installation, the smp_crt.cer file would be generated under the Server/configuration folder. In order to get the approval for accessing SMP server from Agentry Client, we need to install the certificate file in the mobile device.

In this scenario, copy the smp_crt.cer file to the root folder of WPF Agentry Client and install it under the Trust Root Certification Authorities.

/wp-content/uploads/2016/05/image030_971998.png

/wp-content/uploads/2016/05/image032_971999.png

/wp-content/uploads/2016/05/image034_972000.png

Open the WPF Client, input the Agentry Backend user name and password, enter the URL “https://SMPServerAddress:8081/ApplicationName” that can access the work manager 6.3 deployed in the SMP server and you will see the transmit has started in the popup screen.

/wp-content/uploads/2016/05/image036_972001.png

/wp-content/uploads/2016/05/image038_972005.png

/wp-content/uploads/2016/05/image040_972006.png

At last, if you open the SMP Management Cockpit and navigate to “USERS” option under the APPLICATIONS tab, you would find that the connect information for this user on this Agentry application.

/wp-content/uploads/2016/05/image042_972007.png

Related Link:

http://scn.sap.com/community/mobile/blog/2014/08/30/quick-start-guide-sap-work-manager-6x-with-smp-agentry

To report this post you need to login first.

15 Comments

You must be Logged on to comment or reply to a post.

  1. saket amraotkar

    Hi Kevin,

    I have installed SMP server (Runtime) 3.o SP11 and SDK 3.0 SP13 on my local 64 bit system.

    I have installed the 6.3.1 app with SAP backend details and created the app in cockpit as per this blog and deploy the 6.3.1 zip file app.

    I am able to get “I am here” message on browser while running application URL, but when i try to access the URL in agentry app (v70.12.1.2) i am getting error message:

    “The User ID or Password is invalid. try again, connection failed. Ening Transmission”.

    I have double check my backend credentials and i am able to login to SAP ERP system through SAP GUI.

    Not sure what is the issue, it would be great if you can help us here.

    Regards

    Saket

    (0) 
    1. Kevin Xu Post author

      Hi Ezequiel,
      I think you can create a new question in the SCN because it would let all the experts see it and help you do the troubleshooting together.
      Of course, you can @my name in your new ticket and I will also take care of it.

      Thanks for your cooperation,
      Best Regards,
      Kevin Xu
      SAP Product Support

      (0) 
  2. Ranjith Lingala

    Hi all,

    I have Cluster environment in Production with two instance, shall i need to execute those steps in both instance1 and instance2. Please clarify me. 

    (0) 
      1. Ranjith Lingala

        Hi Kevin,

        Sorry for the information, yes you are right above KBA is for Cluster Environment, 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.

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

        So again my question is how will proceed to install SAP Work Manager 6.3 with SMP 3.0 SP09 with above landscape.

        Thanks,
        Ranjith Lingala

        (0) 
        1. Kevin Xu Post author

          Hi  Ranjith,
          I think currently if you cannot see the SMP nodes in Cluster tab, there should have some problem in your SMP cluster environment. So please check the link below and make sure you have set up a health SMP cluster environment at first.

          https://wiki.scn.sap.com/wiki/display/SAPMOB/How+to+Install+SAP+Mobile+Platform+3.0+in+a+Cluster+Environment+Using+ASE+DB

          At then follow the link provided below, steps by steps, you will finish the SAP work manager deployment on SMP cluster target. (There is a link in this KBA)

          2196375 ‚Äď Example on how to setup Agentry Work Manager 6.2 in SMP 3.0 SP08 cluster.

          Best Regards,
          Kevin

          (0) 
  3. Ranjith Lingala

    Hi Kevin,

    Thanks for your reply, currently we are followed with existing in above Landscape and whenever i Publish the application(Work Manager 6.3) after creating Agentry app in SMP 2.0 SP09 using SMP Admin Console in Instance1 it replicated with another instance2 as well. So, likewise i change 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 screen for that “SMP01 – BACKEND Connection Screen.jpeg”, same will happened in another instance also. Also i have checked in all Log file 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 issue is happened.
    Please find the below JavaBE.ini files and all error logs in ERROR.txt.
    Also is there anyway to contact u directly, please share if you are fine it.

    ==================================
    ||    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

    Thanks,
    Ranjith Lingala

     

    (0) 

Leave a Reply