How to publish Work Manager 6.0 on SMP3.0 ?

[michelm_de]

Hi SCN Community,

I'm trying to get the Work Manager 6.0 running on SMP 3.0 (running on Linux). Currently the events.log within the Agentry folder states, that the Agentry Server was started. But If I look into the Threads*.log I see there might be a problem and I'm also not able to connect to the server.

Unfortunately I couldn't find any manual or post where someone described the steps to get a work manager running on SMP 3.0. The SMP 3.0 server manual as well as the SDK manual just describing in general how to publish an application to the SMP 3.0. But for Work Manager, there might be some special things to be done ...

Any help/hints are welcome!

Here what I did so far:

• Install SMP 3.0 up to SP02 on Suse SLES 11
• Install SAP JCo 2.1.11 (test successful:  java -jar /DVD_HANA/jco/sapjco.jar -stdout )
• Create a new application in SMP with type Agentry and select security profile default
• Install SMP3.0 SDK SP02 (Agentry)
• Setup Eclispe 4.2.2 with Agentry Plugin 7.0.2
• Import a Work Manager 6.0 from Teamshare
• Export Agentry Project as a production version and point to the Agentry.ini which is in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application
• Include all jar files to the ZIP file

• Import the ZIP file within Agentry application in SMP 3.0
• Create JavaBE.ini in folder /opt/SAP/MobilePlatform3/Server which is copied from WM6.0 server
• Adjust Agentry.ini in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application  (see section config files)
• Restart Server

Config files:

Agentry.ini

[Server Administration]
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true
[System Connections]
2=ag3httpxmlbe.dll
1=ag3javabe.dll
[Configuration]
apnsCertificateDirectory=apnsCertificates
apnsCertificatePassword=Rzdrj~SwixoAqzmbVxgi
apnsCertificatePasswordEncoded=True
apnsEnabled=True
applicationGlobalsFile=Globals.ini
applicationStringsFile=ApplicationText.ini
clientStringNamesFile=ClientStringNames.ini
clientStringsFile=ClientText.ini
developmentServer=False
enableFailedTransactionLogging=True
enableOverrideFile=Enables.ini
enableTransactionFailureHandling=False
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
failedTransactionsQueue=FailedTransactionsQueue
gcmEnabled=True
gcmServerAuthorizationKey=Authorization:key=AIzaSyDi0qWQEewdbmNSV_o9QNtSQrlxPnBXtBM
gcmServerLink=https://android.googleapis.com/gcm/send
imagesPath=Application\Development\Images
localizationPath=
localizations=
overrideInfoTableDirectory=OverrideInfoTable
overrideTypesFile=OverrideTypes.ini
postedTransactionDirectory=posted
postedTransactionFile=%{device}.pli
scriptsPath=Application\Development\Scripts
spinDocIniFile=
threadCount=0
transmitConfigurationFile=TransmitConfigurations.ini
trustedCertificateStore=
updateIdleWait=60
updatePeriod=60
urlPath=
[HTTPXML-2]
authenticationCertificateStore=MY
authenticationCertificateStorePassword=
authenticationCertificateStorePasswordEncoded=False
autoDequote=True
baseURL=http://localhost:8282
basicAuthenticationPassword=
basicAuthenticationPasswordEncoded=False
basicAuthenticationUserID=
constantsFile=httpxml_sd.ini
enableAuthentication=False
enablePreviousUserAuthentication=False
httpConnectTimeout=60
httpReceiveTimeout=300
httpResolveTimeout=60
httpSendTimeout=300
listenOn=
name=2
timeZoneName=
timeout=300
trustedCertificateStore=
useSSL=False
xmlNamespaces=
[Java-1]
classPath=./ini4j.jar;./Agentry-v5.jar;./Z_SAPWM-6.0.0.0.jar;./SAPWM-6.0.0.0.jar;./SAPCommon-130881.jar;
constantsFile=
deleteSource=True
enableAuthentication=True
enablePreviousUserAuthentication=True
name=Java-1
outputDirectory=.
performCompile=True
printBusinessLogicStackTrace=False
printStackTrace=False
scriptsPath=
serverClass=com.syclo.agentry.Server
sourceDirectory=.
timeZoneName=
[SpinDoc]
facePath=sql\custom;sql
facepath=sql\custom;sql
[TimeZoneAlias]

Log files:

events.log

02/27/2014 18:51:45, 0,         0,         0, Thr 140352349296384, New files opened events.log, messages.log
02/27/2014 18:51:45, 0,         0,         2, Thr 140352349296384, Agentry Startup
02/27/2014 18:51:45, 0,        17,        14, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:51:45, 0,         1,         4, Thr 140352349296384, Agentry v7.0.2.151
02/27/2014 18:51:45, 0,        20,       150, Thr 140352200132352, Loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:51:45, 0,        20,       152, Thr 140352200132352, Loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       153, Thr 140352200132352, Finished loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       151, Thr 140352200132352, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:52:08, 0,        24,         4, Thr 140352349296384, Loaded 2 (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/27/2014 18:52:08, 0,        23,         4, Thr 140352349296384, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/27/2014 18:52:08, 0,        20,         4, Thr 140352349296384, Server v7.0.2.151
02/27/2014 18:52:08, 0,        17,        10, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:52:08, 0,         0,         0, Thr 140352349296384, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-27-185145
02/27/2014 18:52:08, 0,         0,        23, Thr 140352349296384, Agentry startup is complete.

Thread-140352200132352.log

2014/02/27 18:52:07.310: Opening log file
2014/02/27 18:52:07.310: + Thread=140352200132352
2014/02/27 18:52:07.310:   + Server=Agentry
2014/02/27 18:52:07.310:     + Load Loop=Production
2014/02/27 18:52:07.310:       + AppIniFile=SAPWM-v1-0-0-app
2014/02/27 18:52:07.310:         + Module=PM
2014/02/27 18:52:07.310:           + Service Event=WorkOrderPushHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkOrderPushHTTPListener'
2014/02/27 18:52:07.310:           + Service Event=WorkorderPushByOperationHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkorderPushByOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushBySubOperationHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushBySubOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=BDSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'BDSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=DMSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'DMSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushByMRSHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushByMRSHTTPListener'

When trying to connect with the WPF client I get a communication error (14) and nothing is shown in the log files ..

Best Regards,

Michel

[Former Member · Accepted solution]

The [Java-2] serverClass=com.syclo.agentry.Server  should be: serverClass=com/syclo/sap/workmanager/Server

*edit* at the top of my head I am not sure if it should have "/" or "." but right now it is using the default Agentry Server Java Class, and not the Application need one.

[michelm_de · Accepted solution]

Steve,

I also tried your suggestion, but this caues a new error:

02/28/2014 06:12:07, 1,        20,        28, Thr 140054299379456, Java-1 - NoClassDefFoundError|java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Exception|classpath = /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application/ini4j.jar:/opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application/Agentry-v5.jar:/opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application/Z_SAPWM-6.0.0.0.jar:/opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application/SAPWM-6.0.0.0.jar:/opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application/SAPCommon-130881.jar/data/asa0_agentry_ba/buildslave/agentry-server-rhel6/rc_7.0server/source_buildbot/Syclo/ag3/agent/javabe/javaBE.cpp#374:JavaBackEnd::init

So, I changed the value back to serverClass=com.syclo.agentry.Server

/Michel

[Former Member · Accepted solution]

Michel,

The new errors are good, means we made progress, so please put it back.  Also did you use "/" or ".". But the server class also has to look at other jar files that looks like the server is not finding

Jar files it wasn't able to find:

ini4j.jar

Agentry-v5.jar

Z_SAPWM-6.0.0.0.jar

SAPWM-6.0.0.0.jar

SAPCommon-130881.jar

From your Agentry.ini I see you have them listed at the root level of the application folder.  Also, the server is looking for them there:

/opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application/

Are they at this location or are they at:

/opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application/Java/ ?

If they are in the Java folder please update your classPath to say

classPath=./Java/ini4j.jar;./Java/Agentry-v5.jar;./Java/Z_SAPWM-6.0.0.0.jar;./Java/SAPWM-6.0.0.0.jar;./Java/SAPCommon-130881.jar;

Stephen

[michelm_de · Accepted solution]

Hi Stephen,

I changed the classpath to the string you suggested and also tested "." and "/" as a separator. For both I get the Java error. The mentioned Java files are in the application folder:

DEWDFLSSP700:/opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application # ls -al
total 2428
drwxr-xr-x  5 root root    4096 Feb 28 20:31 .
drwxr-xr-x 13 root root    4096 Feb 28 20:30 ..
-rwxr-xr-x  1 root root   90232 Feb 28 06:00 Agentry-v5.jar
-rw-r--r--  1 root root    3368 Feb 28 20:23 Agentry.ini
-rw-r--r--  1 root root    3298 Feb 28 06:09 Agentry.ini.1
drwxr-xr-x  3 root root    4096 Feb 28 06:00 Application
-rw-r--r--  1 root root   51605 Feb 28 06:00 ClientStringNames.ini
-rw-r--r--  1 root root   91220 Feb 28 06:00 ClientTextBase.ini
drwxr-xr-x  2 root root    4096 Feb 28 06:01 OverrideInfoTable
-rw-r--r--  1 root root    3344 Feb 28 06:00 OverrideTypes.ini
-rwxr-xr-x  1 root root  318608 Feb 28 06:00 SAPCommon-130881.jar
-rwxr-xr-x  1 root root 1728057 Feb 28 06:00 SAPWM-6.0.0.0.jar
-rwxr-xr-x  1 root root   38891 Feb 28 06:00 Z_SAPWM-6.0.0.0.jar
-rwxr-xr-x  1 root root   96879 Feb 28 06:00 ini4j.jar
drwxr-xr-x  2 root root    4096 Feb 28 06:00 posted

So, it seems to be a tough work to get this up and running ...

Michel

[Former Member · Accepted solution]

Looking at the error again, i see that is saying it is missing:

NoClassDefFoundError: com/sap/mw/jco/

This class path is not a work manager one, but a SAP JCO one.  Looking at the list of classes I don't see SAPJCO.jar.  This is the jar file that is needed to call the SAP Backend using the RFC Calls.

[michelm_de · Accepted solution]

Stephen,

thanks for this error analysis so far!

I added the sapjco.jar to the classpath in Agentry.ini and also copied the sapjco.jar to the Agentry folder. Now, the exception is gone and I can see in the SMP server logs, that Agentry is calling the backend and fetches the parameters from the config panel (globals and application parameters).

There is no error anymore, so I assumed it should work now.

When doing first test using Agentry 7.0.2 client calling the server using https://SERVERIP:8081/workmanager I get an error:

Certificate received is not found in the trusted list, nor can it be traced to a trusted root.

So, I'm working on the certificates now ... Keep you updated.

Best Regards,

Michel

[Former Member · Accepted solution]

If you WPF clients the certificate needs to be installed for the server.  Go to that website address in IE and make sure it says "I am here"  If it does go to address bar and download the certificate and install it to the Windows Trusted Store.

[michelm_de · Accepted solution]

Importing the server's certificate to the trusted root store, fixed this issue . Now I'm able to communicate with SMP3.0, but still not able to connect to Agentry Server.

I was trying to use the following server address as written here (😞

https://server:8081/workmanager (workmanager is my application name)

Using this URL I get the communication error (14). Also tried application id instead (https://server:8081/com.sap.mobile.wm)

None of this is working.

Can anyone tell me how I have to enter the server name in the Agentry Client?

Thanks,

Michel

[Former Member · Accepted solution]

1) In the Agentry Startup.log file you will see a "SubURL" line.  This will be the value at the end of the <servername>:8081.

2) Use a web brower to go to the https://<servername>:8081/<subURL> to see if it says "I am here"

3) If it does get the certificate from this site.

4) You may need to use the FQDN instead of just the machine name.

[michelm_de · Accepted solution]

Wow, it's working!

In the startup.log it was shown that the application name equals "SAPWM". I was thinking the application name equals to the name I defined in the SMP configuration. But it's the application name which was defined in Agentry Editor.

Once more, thank you very much for your help!

Best Regards,

Michel

[former_member192923]

Hi Michel,

I am also getting same issue when i am testing the app using ATE please find the below threads and no one reply please look at my threads tell me where i am in wrong i am using SMP 3.0 SP03.

Re: Agentry app development using SMP 3.0 SDK SP03

Issue load backend onto Agentry test environment (smp3.0)

By above threads i post my event log and Agentry.ini and JavaBE.ini files and etc..

Your help is greatly appreciated.

Regards,

Ranjith Lingala

[jason_latko]

Michel,

SMP 3.0 and SP02 are having issues with service events being included in an Agentry application.  We are facing the same issues here in product development.  The next service pack for SMP is supposed to correct these issues.  For you to get started, I believe you are going to have to remove all service events from your Agentry application in Eclipse and re-publish.  This will effectively remove any push functionality from the application.  I am told be a colleague that there is a work-around now for SP02 but it is painful to implement.  We are expecting the new service pack shortly.  I would suggest you remove your service events if push is not a requirement of yours, or wait for the next service pack to get started with connectivity.

Jason Latko - Senior Product Developer at SAP

[michelm_de]

Jason,

deleting the service events was helpful regarding the error shown in the Thread log file. After publishing a new version the server seems to start, but has no activity to SAP. I expected at least an initial logon to the SAP system using the service user.

Current log files are:

events.log:

02/28/2014 06:16:36, 0,         0,         0, Thr 140136552040192, New files opened events.log, messages.log
02/28/2014 06:16:36, 0,         0,         2, Thr 140136552040192, Agentry Startup
02/28/2014 06:16:36, 0,        17,        14, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:16:36, 0,         1,         4, Thr 140136552040192, Agentry v7.0.2.151
02/28/2014 06:16:36, 0,        20,       150, Thr 140136413689600, Loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:16:36, 0,        20,       152, Thr 140136413689600, Loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       153, Thr 140136413689600, Finished loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       151, Thr 140136413689600, Finished loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:17:06, 0,        24,         4, Thr 140136552040192, Loaded HTTP-XML Back End (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/28/2014 06:17:06, 0,        23,         4, Thr 140136552040192, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/28/2014 06:17:06, 0,        20,         4, Thr 140136552040192, Server v7.0.2.151
02/28/2014 06:17:07, 0,        17,        10, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:17:07, 0,         0,         0, Thr 140136552040192, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-28-061636
02/28/2014 06:17:07, 0,         0,        23, Thr 140136552040192, Agentry startup is complete.

messages.log is empty and Thread*.log doesn't exist anymore.

Any further idea how to get this up and running?

Best Regards,

Michel

[Former Member]

The reason why it is not showing the log in to the SAP System is because that is with in the Server class file, with the Jar file isn't found, see my post above about getting it so the Jar files are found.

The messages.log will be empty until a User connects to the server, as this file is used to keep track of the messages sent to and from the Agentry Server to client (or Agentry Server to Agentry Server when clustered), not from the Agentry Server to backend.

Stephen

[former_member192923]

Hi Stephen,

I am also getting same issue when i am testing the app using ATE please find the below threads and no one reply please look at my threads tell me where i am in wrong i am using SMP 3.0 SP03.

By above threads i post my event log and Agentry.ini and JavaBE.ini files and etc..

Your help is greatly appreciated.

Regards,

Ranjith Lingala

[Former Member]

Hi Jason,

I am getting this error on SMP3 SP04, can we implement service event for SMP3 SP4?

2015/05/25 14:03:33.831: Opening log file

2015/05/25 14:03:33.831: + Thread=5520

2015/05/25 14:03:33.831:   + Application=com.sap.data.WMest60

2015/05/25 14:03:33.831:     + Load Loop=Production

2015/05/25 14:03:33.831:       + AppIniFile=SAPWM-v1-0-0-app

2015/05/25 14:03:33.831:         + Module=PM

2015/05/25 14:03:33.831:           + Service Event=BDSDocumentPushHTTPListener

2015/05/25 14:03:33.831:             System Connection with ID '2' not found for Service Event

2015/05/25 14:03:33.831:             Failed to load definition for Service Event 'BDSDocumentPushHTTPListener'

2015/05/25 14:03:33.831:           + Service Event=DMSDocumentPushHTTPListener

2015/05/25 14:03:33.831:             System Connection with ID '2' not found for Service Event

2015/05/25 14:03:33.831:             Failed to load definition for Service Event 'DMSDocumentPushHTTPListener'

2015/05/25 14:03:33.831:           + Service Event=WorkorderPushByMRSHTTPListener

2015/05/25 14:03:33.831:             System Connection with ID '2' not found for Service Event

2015/05/25 14:03:33.831:             Failed to load definition for Service Event 'WorkorderPushByMRSHTTPListener'

2015/05/25 14:03:33.831:           + Service Event=WorkorderPushByOperationHTTPListener

2015/05/25 14:03:33.831:             System Connection with ID '2' not found for Service Event

2015/05/25 14:03:33.831:             Failed to load definition for Service Event 'WorkorderPushByOperationHTTPListener'

2015/05/25 14:03:33.831:           + Service Event=WorkorderPushBySubOperationHTTPListener

2015/05/25 14:03:33.831:             System Connection with ID '2' not found for Service Event

2015/05/25 14:03:33.831:             Failed to load definition for Service Event 'WorkorderPushBySubOperationHTTPListener'

2015/05/25 14:03:33.831:           + Service Event=WorkOrderPushHTTPListener

2015/05/25 14:03:33.831:             System Connection with ID '2' not found for Service Event

2015/05/25 14:03:33.831:             Failed to load definition for Service Event 'WorkOrderPushHTTPListener'

Thanks and Regards,

Pratik

[bill_froelich]

Pratik,

Please create a Discussion marked as a Question.  This question is already marked as answered.  This way others may benefit from your solution once it is found, but also because you will have more folks looking to provide a solution when your issue has the greater visibility of a Discussion.

--Bill