SAP WM 6.0 deployment Issue in SMP 3.0 SP04

[Former Member]

Hi All,

While deploying the SAP work manager 6.0 application in SMP 3.0 SP04, facing exception from java side.

Startup Logs:

01:53:22 11/05/2014: Java Back End: Java Virtual Machine already initialized.

01:53:22 11/05/2014: Exception: 01:53:22 11/05/2014 : 20 (Agentry3), BackEndInitError (Error starting Java System Connection Java Back End: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$AbapException;  (resolved class path: C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM60\ini4j.jar;

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM60\sapjco3.jar;

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM60\Java\Agentry-v5.jar;

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM60\Java;

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM60\Java\SAPWM-6.0.0.0.jar;

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM60\Java;

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM60\Java\SAPCommon-133461.jar;

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM60\Java)),

javaBE.cpp#357:JavaBackEnd::init

01:53:22 11/05/2014: Failed to init Java Back End (Java v7.0.4.17) from ag3javabe.dll.

In my application, I have changed the SapJco, dll, SAPCommon, Agentry-v5 files according to SMP 3.0.

Please assist me on this Issue....

Thanks,

Vino

[vivek_m · Accepted solution]

Hello Vinoth,

Below are findings for the error:

1. SAPWM6.1 uses sapjco3.jar, SAPCommon-133461.jar and SAPWM-6.1.1.0.jar file for runnig it on SMP 3.0.

2. SAPWM6.0 uses sapjco.jar, SAPCommon-122971.jar and SAPWM-6.0.0.0.jar file for running it on SMP2.3

Now it seems you have ported in a way using the below to run SAPWM6.0 on SMP3.0

1. sapjco3.jar

2. SAPCommon-133461.jar

3. SAPWM-6.0.0.0.jar

But the sapjco3 has a lot of changes compared to sapjco.jar file.

Repository Structure for sapjco3 :

Repository Structure for sapjco used in SAPWM6.0

Comparing these two jcos we could conclude the IMPORT paths are different. So when we use SAPWM6.0.0.0.0.jar file the path imported in it is would be like

import com.sap.mw.jco.JCO.*;

So you are getting the NoDefFoundError for the classed being called from sapjco.jar.

Thanks,

Vivek

[bill_froelich · Accepted solution]

Vivek,

SAP Work Manger 6.0 is using the Jco2 libraries not JCo3.  You will need to maintain that Jco version as you move to SMP3.  Work Manager 6.1 switched to use JCo3.

You will need to maintain the same structure as you move it to SMP3.

--Bill

[Former Member · Accepted solution]

Hi Bill,

Thanks for your response. For your information SMP 3.0 SP04 is not accepting the Jco 2.x while deploying the agentry application with the same java structures for SAP wm 6.0 as you are mentioning.

Kindly clarify that whether SMP 3.0 SP04 supports Jco 2.x or not?

Thanks,

Vinoth

[Former Member · Accepted solution]

I have seen Work Manager 6.0 on SMP 3.  You can see what was done on the following thread;

Note, this was for a linux server, but most items would work on both servers.

While it will work, it is not supported by SAP because the applications are tested on release platform. 

[Former Member · Accepted solution]

Hi Stephen,

Thanks for your response.

I have followed this thread, which you mentioned above. In that thread, the SMP 3.0 is for service pack 2(SP02) . In that version, only we can able to deploy one agentry application at the time.

But, in SP04, we can able to deploy more than one agentry application and most of their steps related to JAVA configuration is changed. That's why I'm so sure about the JCo config.

Kindly provide your comments....

Thanks,

Vinoth

[Former Member · Accepted solution]

The only changes between the SP02 and Sp04 you would need to worry about it just putting the jar files in the new application folder path.  The JavaBE.ini goes in the same spot that is stated for SP02, (in the MobilePlatfrom3\Server) folder

Also, for the sapjco Jar files, put them in the MobilePlatfrom\sapjvm_7\bin folder (i think that was the right spot)

Stephen

[resmi_sadasivan2]

Hi Vinoth,

This error will occur mostly if there is any missing files/libraries/wrong path.

Please verify your Agentry.ini, serverclass or classpath, is there any misspell or incorrect parameter. Also verify the system path environment variable.

Thanks

Resmi

[Former Member]

Thanks Resmi,

For your information

Agentry.ini Java Settings

[Java-1]

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

constantsFile=

deleteSource=True

enableAuthentication=True

enablePreviousUserAuthentication=False

name=Java Back End

outputDirectory=.

performCompile=True

printBusinessLogicStackTrace=False

printStackTrace=False

scriptsPath=

serverClass=com/syclo/sap/workmanager/Server

sourceDirectory=.

timeZoneName=

Environmental Variables: PATH

C:\Program Files\Java\jdk1.6.0_38\bin;C:\Program Files\Java\jdk1.6.0_38\lib;C:\Program Files\Java\jdk1.6.0_38\jre\bin\server;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\SQL Anywhere 11\bin32;C:\Program Files\SQL Anywhere 12\bin64;C:\Program Files\SQL Anywhere 12\bin32;C:\Program Files\Java\jdk1.7.0_71\bin;C:\Program Files\Java\jdk1.7.0_71\jre\bin\server;C:\Program Files\Java\jdk1.7.0_71\lib;C:\Program Files\Java\jdk1.7.0_07\jre\lib

Please share your views on this settings...

[resmi_sadasivan2]

Hi Vinoth,

Please verify the class path your old and new value, it should be

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

Thanks

Resmi

[Former Member]

Hi Resmi,

I have changed the class path as you  suggested, even though facing the same error. Is there any way follow to check the compatibility of SAPJCO.jar file.

Thanks,

Vinoth

[Former Member]

Hello Vinoth , After change did you restart Agentry server or services to take new path . Thanks & Regards, Kunal Varaiya