Skip to Content
avatar image
Former Member

Running 2 instances of Work Manager 6.1 on SMP 3 sp4

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Nov 13, 2014 at 06:24 PM

    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

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Mark Pe

      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

  • avatar image
    Former Member
    Nov 17, 2014 at 07:10 PM

    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!

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 01, 2014 at 05:36 AM

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

    Add comment
    10|10000 characters needed characters exceeded