Running 2 instances of Work Manager 6.1 on SMP 3 sp4

[Former Member]

Hi experts,

In SMP 3.0 SP3 only one Agentry application could be deployed, after upgrading to SP4 it is now possible to run several Agentry applications. Each Agentry application has its own URL, e.g. https://servername:port/SAPWM for Work Manager 6.1.

Now is it possible to run 2 different instances of Work Manager application in one SMP server? Obviously two instances should have either different port number or different URL so they can be differentiated on client side. And if yes, how the URL can be changed in Work Manager?

Thanks

[Former Member · Accepted solution]

Hi Pouya,

that is right. SMP 3 SP 4 supports that. You have to set the parameter urlPath in the App specific settings. If you got 2 Apps, the first will always be defaulted to *SAPWM. I recommend to set a name that differs the purpose, like SAPWMPROD and SAPWMTEST or as you wish (here the question is creativity). After setting this parameter you have to restart the Agentry services. There is also a new option in the SCC to restart the Agentry server instances or you can do it via the OSGI console.

Kind regards,

Mike

[Former Member · Accepted solution]

Mark,

Thanks for the quick reply, I was able to publish 2 instances of WM using different urlPath parameter as you advised.

The old app is working fine, the url is accessible through browser(says I am her) and the client can connect and pull down work orders. The new app though, is only accessible through url(says I am here) but when I try to connect through client it says "No backends loaded"...

Do I need to change settings on backend too? Like creating a new instance of work manager and point the new app to that instance(I assume through JavaBE.ini file and APPNAME parameter)?

Thanks

[Former Member · Accepted solution]

Agentry Doesn't use the urlPath currently to build the subURL,  instead it uses the application name define in the Editor.  You will need to use a different application name for your other application.

Stephen

[Former Member · Accepted solution]

Hi Stephen,

Would you please elaborate on this? As I mentioned I was able to publish 2 instances of the WM app on SMP with different URLs. So you mean instead of doing that, I should change the App name inside Eclipse using Agentry Editor plugin?

[bill_froelich · Accepted solution]

In SP04 Agentry does use the urlPath in the configuration that becomes the subURL.  I have confirmed this through my testing.  You do not need to change the App name in Eclipse.

--Bill

[Former Member · Accepted solution]

Thanks Bill,

Could you answer my second question?

The new app is only accessible through url(says I am here) but when I try to connect through client it says "No backends loaded"...

Do I need to change settings on backend too? Like creating a new instance of work manager and point the new app to that instance(I assume through JavaBE.ini file and APPNAME parameter)?

[bill_froelich · Accepted solution]

I see no reason you can't point both instances of work manager against the same SAP backend.  You will need to setup each independently within the Management cockpit.

The no backends loaded error indicates that something isn't setup correctly for that instance.

--Bill

[former_member190010 · Accepted solution]

I've configured two agentry apps in SMP 3.0 sp4. SAP Inventory Manager 4.0 and SAP Work Manager 6.1.

Inventory Manager is working fine, and I am able to connect to the backend. But for Work Manger I am also geting the "No backends loaded" error.

[bill_froelich · Accepted solution]

As I mentioned, the no backends loaded error indicates a problem with the configuration for the Work Manager application.

Check your startup.log file to see if it offers any clues along with the events.log.

I have around 8 applications currently defined on my SMP3 SP04 server on my laptop and they all load just fine.

--Bill

[former_member190010 · Accepted solution]

Bill, thank you for your answer.

I've been looking at the logs and I found some errors that call my atention in the events.log file.

I see this post with similar errors (), but the solution proposed there doesn't work for my case because I don't have an Agentry.ini file.

Do you have any idea what these errors refer about?

11/15/2014 10:48:43, 0,        20,       150, Thr       9712, Loading Production application definitions using file "SAPWM-v1-0-0-app"

11/15/2014 10:48:43, 0,        20,       152, Thr       9712, Loading Production application definitions for default localization

11/15/2014 10:48:46, 1,         3,         9, Thr       9712, HTTPXML-2, Chickaming HTTPXML, xmlAllowXSLTScript, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/15/2014 10:48:46, 1,         3,         9, Thr       9712, HTTPXML-2, Chickaming HTTPXML, xmlResolveExternals, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/15/2014 10:48:46, 1,         3,         9, Thr       9712, HTTPXML-2, Chickaming HTTPXML, xmlValidateOnParse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/15/2014 10:48:49, 0,        24,         4, Thr       9712, Loaded HTTP-XML Back End (HTTPXML v7.0.4.17) from ag3httpxmlbe.dll

11/15/2014 10:48:49, 1,         3,         9, Thr       9712, Java-1, Chickaming Java, initialHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/15/2014 10:48:49, 1,         3,         9, Thr       9712, Java-1, Chickaming Java, maxHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/15/2014 10:48:49, 1,         3,         9, Thr       9712, Java-1, Chickaming Java, nonStandardJavaOptions, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/15/2014 10:48:49, 1,         3,         9, Thr       9712, Java-1, Chickaming Java, reduceOSSignalUse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/15/2014 10:48:49, 1,        20,        28, Thr       9712, Error starting Java System Connection Java Back End: java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server not found from bundle [com.sap.mobile.platform.server.agentry.core]

Best Regards,

Emanuek

[bill_froelich · Accepted solution]

The badKey errors imply you are using an Agentry.ini that is from a previous version instead of what comes with WM 6.1.

All those badKey messages are informational.  The real problem is this one.

11/15/2014 10:48:49, 1,        20,        28, Thr       9712, Error starting Java System Connection Java Back End: java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server not found from bundle [com.sap.mobile.platform.server.agentry.core]

This message is telling you it couldn't load the java backend hence the No Backends loaded error message you are getting.

I would look at redeploying WM 6.1 again from the SAPWorkMgr611Deployment.exe.

Also are you trying to deploy Development or Production mode Work Manager?

--Bill

[former_member190010 · Accepted solution]

Thank you for your answer Bill.

1) The badKey errors imply you are using an Agentry.ini that is from a previous version instead of what comes with WM 6.1.

I didn't install an older Work Manager edition. I don't know why these errors are happening.

2) Also are you trying to deploy Development or Production mode Work Manager?

The SMP is installed in development mode.

The Work Manager server only has the Production server mode.

I attach an image below that shows that the work manager development mode is not offered in the new installer.

The only idea I have is to install again the SMP 3.0, and installl again the work manager app and see if this solve the issue.

If there is another option, pleaes let me know.

Thanks in advance,

Emanuel

[bill_froelich · Accepted solution]

1) My apologies, since I don't typically run production mode I didn't realize the bundled Agentry.ini had the obsolete key references still in it.  Hopefully this will be corrected for 6.2.

2) You are correct that the installer provides the production mode files for Work Manager.

Since you are running SMP 3.0 SP04 you will need to manually move files over to the correct application directory after install.

If you are intending to configure Work Manager you would simply take the SAPWM-6.1.1.0.zip and extract to a temporary location and use that as the starting point by importing from there into the Editor and then publishing to your SMP3.0 server resulting in a development mode Work Manager.

In that case you would configure the Agentry.ini settings through the Management cockpit copying the needed values from the Agentry.ini in the zip into the cockpit.

--Bill

[former_member190010 · Accepted solution]

Hi Bill,

I am trying to deploy Production mode of Work Manager.

I have followed all the steps, and everything looks to be fine.

1) Create agentry app in SMP

2) Configure authentication

3) Run the Work Manager installer

4) Deploy the .zip file in the app specific settings tab

5) Restart the SMP platform

I am receiving the "I am Here" message at the url:

https://<localhost>:8081/SAPWM

But the Backend is not being loaded in the backend tab.

I don't know why this is happening.

The configuration of the backend is correct, because when I run the connectTest.bat I am pinging the SAP ERP server.

This is the structure I have in the SMP, agentry folder:

com.sap.mobile.platform.server.agentry

com.sap.mobile.platform.server.agentry.application

com.sap.mobile.platform.server.agentry.application.com.sap.wm61

Then, I attach the logs I have:

11/16/2014 23:06:32, 0,         0,         0, Thr       3628, New files opened events.log, messages.log

11/16/2014 23:06:32, 0,         0,         2, Thr       3628, Loading the Agentry Runtime's public/private key for password exchanges.

11/16/2014 23:06:32, 0,         0,         2, Thr       3628, Key pair loaded successfully.

11/16/2014 23:06:32, 0,         0,         2, Thr       3628, Agentry Startup

11/16/2014 23:06:32, 0,         1,         4, Thr       3628, Agentry Server Agent v7.0.4.17

11/16/2014 23:06:32, 0,        20,         4, Thr       3628, com.sap.wm61 v7.0.4.17

11/16/2014 23:06:32, 0,         0,         0, Thr       3628, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-11-16-230632

11/16/2014 23:06:32, 0,         0,        23, Thr       3628, Agentry startup is complete.

11/16/2014 23:06:32, 0,        20,         5, Thr       3628, com.sap.wm61

11/16/2014 23:06:33, 0,        20,       150, Thr       2828, Loading Production application definitions using file "SAPWM-v1-0-0-app"

11/16/2014 23:06:33, 0,        20,       152, Thr       2828, Loading Production application definitions for default localization

11/16/2014 23:06:36, 1,         3,         9, Thr       2828, HTTPXML-2, Chickaming HTTPXML, xmlAllowXSLTScript, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/16/2014 23:06:36, 1,         3,         9, Thr       2828, HTTPXML-2, Chickaming HTTPXML, xmlResolveExternals, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/16/2014 23:06:36, 1,         3,         9, Thr       2828, HTTPXML-2, Chickaming HTTPXML, xmlValidateOnParse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/16/2014 23:06:38, 0,        24,         4, Thr       2828, Loaded HTTP-XML Back End (HTTPXML v7.0.4.17) from ag3httpxmlbe.dll

11/16/2014 23:06:38, 1,         3,         9, Thr       2828, Java-1, Chickaming Java, initialHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/16/2014 23:06:38, 1,         3,         9, Thr       2828, Java-1, Chickaming Java, maxHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/16/2014 23:06:38, 1,         3,         9, Thr       2828, Java-1, Chickaming Java, nonStandardJavaOptions, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/16/2014 23:06:38, 1,         3,         9, Thr       2828, Java-1, Chickaming Java, reduceOSSignalUse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/16/2014 23:06:38, 1,        20,        28, Thr       2828, Error starting Java System Connection Java Back End: java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server not found from bundle [com.sap.mobile.platform.server.agentry.core]

at org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:101)

at org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader.loadClass(BundleDelegatingClassLoader.java:155)

at java.lang.ClassLoader.loadClass(ClassLoader.java:421)

Caused by: java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server

at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)

at java.lang.ClassLoader.loadClass(ClassLoader.java:421)

at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:340)

at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1212)

at org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:97)

... 2 more

;  (resolved class path: )javaBE.cpp#357:JavaBackEnd::init

11/16/2014 23:06:39, 0,        20,       153, Thr       2828, Finished loading Production application definitions for default localization

11/16/2014 23:06:39, 0,        20,       151, Thr       2828, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"

11/16/2014 23:06:39, 0,        17,        14, Thr       3628, com.sap.wm61 v7.0.4.17

11/16/2014 23:06:39, 0,        20,         4, Thr       3628, com.sap.wm61 v7.0.4.17

11/16/2014 23:06:39, 0,        17,        10, Thr       3628, com.sap.wm61 v7.0.4.17

From these data, Do you have any idea what am I doing wrong?

Is there any step is lucking?

Thanks in advance,

Emanuel

[mark_pe · Accepted solution]

In SMP for issues like this in Agentry SAP Work Manager:

"No backends loaded"...

or

java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server

the zip published file you use in the Cockpit needs to be reviewed.

Check for the following:

1) In the zip publish, do you have an Application folder with Production folder in it? If not that might be a problem as this will cause a "No backend loaded"

Or

2) In the Agentry.ini in your zip publish folder, please double check line per line if all the settings are correct including the [Java-1] classPath.  Double check the classPath or server path. Does it still point to an agentry-v5.jar file?  This should be corrected in SAP Work Manager 6.2 as 6.1 still points to the old agentry-v5.jar file. The agentry-v5.jar is embedded in SMP 3.0. But having it does not mean it will not work. The SMP 3.0 will just ignore it as how it was explained to me by my Agentry development team.

- Most likely your Agentry.ini inside the zip publish is missing some definition. Compare it with your development agentry.ini

Or

3) You have some sort of Java incompatibility happening in the SMP 3.0 server versus your mobile application.

- If you have this error your Agentry startup.log or your SMP servername.server.log may say something that you are using an incompatible AJAPI. You may need to use or change your system path variable to use the one provided by the SMP 3.0 server.

Observation: In a production environment I always see the  naming convention of these multi-nodes under the Application/Production folder in the zip publish. The demo I see in production all have different names (like: SAPWM or SAPIM).

If I have to guess your issue is in the Agentry.ini inside your zip publish. Check it line per line.

If you agentry.ini inside the zip publish is all correct then the agentry.ini inside the share or SMP share database is incorrect. Can be corrected by just re-creating the Agentry node with the zip publish that has the correct agentry.ini in it.

Those are the ones I can think of right now.

Hope this helps,

Mark Pe

SAP Senior Support Engineer

[former_member190010 · Accepted solution]

Hi Mark,

Thanks for your answer.

First, I attach the structure of the .zip file I've downloaded from the support site:

SAPWM-6,1,1,0.zip:

Application (folder)
|
---Production (folder)

Agentry.ini (file)

Then, I check the Agentry.ini file and found this:

[Java-1]

classPath=./ini4j.jar;./sapjco3.jar;./Java/Agentry-v5.jar;./Java;./Java/SAPWM-6.1.1.0.jar;./Java;./Java/SAPCommon-133461.jar;

constantsFile=

deleteSource=True

enableAuthentication=True

enablePreviousUserAuthentication=True

My questions are:

1) Should I just remove the line ./Java/Agentry-v5.jar?

Should I add something else?

2) Once I modify the Agentry.ini, should I zip the contents again and that way it will be ready?

Best Regards,
Emanuel

[Former Member · Accepted solution]

The Agentry-v5.jar file will be picked up by the SMP Server as it is a core Agentry file.

The file it is can find is located in: /Java/SAPWM-6.1.1.0.jar;

Stephen

[mark_pe · Accepted solution]

Emanuel,

Hi. In your Agentry.ini don't you have something like this:

~~~~agentry.ini~~~~~

[Java-1]

..

..

serverClass=com/syclo/sap/workmanager/Server

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

Remember you have a server class cannot be found issue. This line item will tell Agentry where to find you Server.class file in your Java package like SAPWM-6.1.1.0.jar (com.syclo.sap.workmanage.server).

The Agentry-v5.jar is built in SMP 3.0. You may just leave it there. I even have it on all my local installs. Also Work Manager 6.2 will have the agentry.ini removed this Agentry-v5.jar from the classPath as confirmed to me by my colleague (Lee - I believe there is a bug against it when he worked in Work Manager product development) or from how it was explained to me by my other Agentry developer colleague (Karl - he claims it is build in SMP 3.0 and no need to specify it in product like Work Manager).  So there is some discussion between the Agentry team and the Product team (Work Manager) to improve the agentry.ini for SMP 3.0. But you will see the results more in the newer product coming out.

Regards,

Mark Pe

SAP Senior Support Engineer

[former_member190010 · Accepted solution]

Thank you Mark and Stephen.

I have checked the Agentry.ini file and found the line you've mentioned.

[Java-1]

classPath=./ini4j.jar;./sapjco3.jar;./Java/Agentry-v5.jar;./Java;./Java/SAPWM-6.1.1.0.jar;./Java;./Java/SAPCommon-133461.jar;

constantsFile=

deleteSource=True

enableAuthentication=True

enablePreviousUserAuthentication=True

initialHeapSize=256

maxHeapSize=512

name=Java Back End

nonStandardJavaOptions=

outputDirectory=.

performCompile=False

printBusinessLogicStackTrace=False

printStackTrace=False

reduceOSSignalUse=True

scriptsPath=

serverClass=com/syclo/sap/workmanager/Server

sourceDirectory=.

The directory of the .jar files is:

C:\Agentry\WorkManager6.1\configuration\com.sap.mobile.platform.server.agentry.application\Java

In each .jar Java file, it can be found the Server class.

SAPWM-6.1.1.0.jar --> com/syclo/sap/workmanager/Server

SAPCommon-133461.jar --> com/syclo/sap/Server

Agentry-v5.jar --> com/syclo/agentry/Server

My question is:

You've mentioned the Agentry-v5.jar file is built in SMP 3.0.

Which is the directory where the Agentry-v5.jar file can be find?

Once I have this directory, I can search for the class that is not being finding.

I attach the logs I have. Maybe this can help.

Startup.log:

15:15:54 11/17/2014: Starting Agentry (64-bit Windows)

15:15:54 11/17/2014: Reading system ini file.

15:15:54 11/17/2014: Starting log file.

15:15:54 11/17/2014: Loading message groups.

15:15:54 11/17/2014: Starting threads.

15:15:54 11/17/2014:    1 initial threads.  Threads will auto-scale.

15:15:54 11/17/2014: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.

15:15:55 11/17/2014: Event: 0, 2, Key pair loaded successfully.

15:15:55 11/17/2014: Starting Agentry: Agentry Server Agent v7.0.3.159

15:15:55 11/17/2014: Event: 0, 2, Agentry Startup

15:15:55 11/17/2014: Loading 0 front ends

15:15:55 11/17/2014: Loading front end from angelvine

15:15:55 11/17/2014: WebSockets Front End: loading configuration

15:15:55 11/17/2014: Event: 17, 14, WebSockets Front End v7.0.3.159

15:15:55 11/17/2014: Starting Agentry Server Agent

15:15:55 11/17/2014: Agentry Server Agent: Starting threads.

15:15:55 11/17/2014:    1 initial threads.  Threads will auto-scale.

15:15:55 11/17/2014: Agentry Server Agent: Adding messages.

15:15:55 11/17/2014: Event: 1, 4, Agentry Server Agent v7.0.3.159

15:15:55 11/17/2014: Loading agent from ag3.dll

15:15:55 11/17/2014: Starting Server

15:15:55 11/17/2014: Server: reading config file

15:15:55 11/17/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"

15:15:55 11/17/2014: Event: 20, 152, Loading Production application definitions for default localization

15:15:58 11/17/2014: Initializing HTTPXML-HTTPXMLSystemConnection from ag3httpxmlbe.dll

15:15:58 11/17/2014: HTTPXMLSystemConnection: Reading configuration information.

15:15:58 11/17/2014: HTTPXMLSystemConnection: Setting name to 'HTTP-XML Back End'.

15:16:01 11/17/2014: HTTP-XML Back End: Initialized.

15:16:01 11/17/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v7.0.3.159) from ag3httpxmlbe.dll

15:16:01 11/17/2014: Initializing Java-SAPJavaConnection from ag3javabe.dll

15:16:01 11/17/2014: SAPJavaConnection: Reading configuration information.

15:16:01 11/17/2014: SAPJavaConnection: Setting name to 'Java Back End'.

15:16:01 11/17/2014: Java Back End: Initialized.

15:16:01 11/17/2014: Java Back End: Java Virtual Machine already initialized.

15:16:01 11/17/2014: Exception: 15:16:01 11/17/2014 : 20 (Agentry3), BackEndInitError (Java Back End - ClassNotFoundException|java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server not found from bundle [com.sap.mobile.platform.server.agentry.core]

), at org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:101)

15:16:01 11/17/2014: Failed to init Java Back End (Java v7.0.3.159) from ag3javabe.dll

15:16:02 11/17/2014: Event: 20, 153, Finished loading Production application definitions for default localization

15:16:02 11/17/2014: Event: 20, 151, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"

15:16:02 11/17/2014: Server: Starting threads.

15:16:02 11/17/2014:    1 initial threads.  Threads will auto-scale.

15:16:02 11/17/2014: Event: 20, 4, Server v7.0.3.159

15:16:02 11/17/2014: Starting front ends

15:16:02 11/17/2014: WebSockets Front End: Opening WebSockets servlet for sub-URL /SAPWM

15:16:02 11/17/2014: Event: 17, 10, WebSockets Front End v7.0.3.159

15:16:02 11/17/2014: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-11-17-151554

15:16:02 11/17/2014: Event: 0, 23, Agentry startup is complete.

Events.log:

11/17/2014 15:15:54, 0,         0,         0, Thr       9568, New files opened events.log, messages.log

11/17/2014 15:15:54, 0,         0,         2, Thr       9568, Loading the Agentry Runtime's public/private key for password exchanges.

11/17/2014 15:15:55, 0,         0,         2, Thr       9568, Key pair loaded successfully.

11/17/2014 15:15:55, 0,         0,         2, Thr       9568, Agentry Startup

11/17/2014 15:15:55, 0,        17,        14, Thr       9568, WebSockets Front End v7.0.3.159

11/17/2014 15:15:55, 0,         1,         4, Thr       9568, Agentry Server Agent v7.0.3.159

11/17/2014 15:15:55, 0,        20,       150, Thr      10144, Loading Production application definitions using file "SAPWM-v1-0-0-app"

11/17/2014 15:15:55, 0,        20,       152, Thr      10144, Loading Production application definitions for default localization

11/17/2014 15:15:58, 1,         3,         9, Thr      10144, HTTPXML-2, Chickaming HTTPXML, xmlAllowXSLTScript, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/17/2014 15:15:58, 1,         3,         9, Thr      10144, HTTPXML-2, Chickaming HTTPXML, xmlResolveExternals, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/17/2014 15:15:58, 1,         3,         9, Thr      10144, HTTPXML-2, Chickaming HTTPXML, xmlValidateOnParse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/17/2014 15:16:01, 0,        24,         4, Thr      10144, Loaded HTTP-XML Back End (HTTPXML v7.0.3.159) from ag3httpxmlbe.dll

11/17/2014 15:16:01, 1,         3,         9, Thr      10144, Java-1, Chickaming Java, initialHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/17/2014 15:16:01, 1,         3,         9, Thr      10144, Java-1, Chickaming Java, maxHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/17/2014 15:16:01, 1,         3,         9, Thr      10144, Java-1, Chickaming Java, nonStandardJavaOptions, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/17/2014 15:16:01, 1,         3,         9, Thr      10144, Java-1, Chickaming Java, reduceOSSignalUse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

11/17/2014 15:16:01, 1,        20,        28, Thr      10144, Java Back End - ClassNotFoundException|java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server not found from bundle [com.sap.mobile.platform.server.agentry.core]

  at org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:101)

  at org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader.loadClass(BundleDelegatingClassLoader.java:155)

  at java.lang.ClassLoader.loadClass(ClassLoader.java:421)

Caused by: java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server

  at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)

  at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)

  at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)

  at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)

  at java.lang.ClassLoader.loadClass(ClassLoader.java:421)

  at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:340)

  at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)

  at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1212)

  at org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:97)

  ... 2 more

|classpath = javaBE.cpp#383:JavaBackEnd::init

11/17/2014 15:16:02, 0,        20,       153, Thr      10144, Finished loading Production application definitions for default localization

11/17/2014 15:16:02, 0,        20,       151, Thr      10144, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"

11/17/2014 15:16:02, 0,        20,         4, Thr       9568, Server v7.0.3.159

11/17/2014 15:16:02, 0,        17,        10, Thr       9568, WebSockets Front End v7.0.3.159

11/17/2014 15:16:02, 0,         0,         0, Thr       9568, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-11-17-151554

11/17/2014 15:16:02, 0,         0,        23, Thr       9568, Agentry startup is complete.

Thread-10144.log:

2014/11/17 15:16:01.752: Opening log file

2014/11/17 15:16:01.752: + Thread=10144

2014/11/17 15:16:01.752:   + Server=Agentry

2014/11/17 15:16:01.752:     + Load Loop=Production

2014/11/17 15:16:01.752:       + AppIniFile=SAPWM-v1-0-0-app

2014/11/17 15:16:01.752:         + Module=PM

2014/11/17 15:16:01.752:           + Service Event=BDSDocumentPushHTTPListener

2014/11/17 15:16:01.752:             System Connection with ID '2' not found for Service Event

2014/11/17 15:16:01.753:             Failed to load definition for Service Event 'BDSDocumentPushHTTPListener'

2014/11/17 15:16:01.753:           + Service Event=DMSDocumentPushHTTPListener

2014/11/17 15:16:01.753:             System Connection with ID '2' not found for Service Event

2014/11/17 15:16:01.753:             Failed to load definition for Service Event 'DMSDocumentPushHTTPListener'

2014/11/17 15:16:01.754:           + Service Event=WorkorderPushByMRSHTTPListener

2014/11/17 15:16:01.754:             System Connection with ID '2' not found for Service Event

2014/11/17 15:16:01.754:             Failed to load definition for Service Event 'WorkorderPushByMRSHTTPListener'

2014/11/17 15:16:01.754:           + Service Event=WorkorderPushByOperationHTTPListener

2014/11/17 15:16:01.754:             System Connection with ID '2' not found for Service Event

2014/11/17 15:16:01.754:             Failed to load definition for Service Event 'WorkorderPushByOperationHTTPListener'

2014/11/17 15:16:01.754:           + Service Event=WorkorderPushBySubOperationHTTPListener

2014/11/17 15:16:01.754:             System Connection with ID '2' not found for Service Event

2014/11/17 15:16:01.754:             Failed to load definition for Service Event 'WorkorderPushBySubOperationHTTPListener'

2014/11/17 15:16:01.754:           + Service Event=WorkOrderPushHTTPListener

2014/11/17 15:16:01.754:             System Connection with ID '2' not found for Service Event

2014/11/17 15:16:01.754:             Failed to load definition for Service Event 'WorkOrderPushHTTPListener'

Best Regards,

Emanuel

[Former Member]

Will this make it possible to run one instance for Service Orders and one instance for Plant maintenance orders?  According to OSS Note 2093621 it is not possible to have both at the same time...

[bill_froelich]

Lukas,

This is really a different question.  I would recommend posting as a new thread so you can control it.

--Bill

[Former Member]

Thanks Bill, I have done that here:

[former_member190010]

Guys,

Excellent news!

I was able to detect the Backend.

I've just needed to copy the contents of the deployment files into the com.sap.mobile.platform.server.agentry.application folder.

Thank you for everything!

[Former Member]

Emanuel,

Could you explain the step by step process of publishing Work Manager to fix that issue?

Thanks

[mark_pe]

Emanuel,

Cool. Good job. That is part of the quick start guide that we have for Work Manager 6.1 to copy the files into the application folder.

Best Regards,

Mark Pe

SAP Senior Support Engineer

[former_member190010]

Yes Mark. Excellent guide.

The link is below:

http://service.sap.com/sap/support/notes/2060561

Pouya N, you can find there an excellent step by step guide. Very helpful information.

Now I am facing another issue with the ATE.

If someone wants to help, here is the link for the new thread: http://scn.sap.com/thread/3653182.

Best regards,

Emanuel