How to deploy custom java code to SMP 3.0 SP05 server?
I have created custom application in management cockpit and published standard agentry definitions to development server and after that I have done the configuration settings in JavaBE.ini file to connect to custom mobile app.
Done changes to class path and server class from cockpit which effect the Agentry.ini file in development server. Here also I have mapped class path for standard java code.
Now I have done changes to the Agentry application and the java code. We have got the standard SAP WM 6.2 java source code from SAP.
Published the custom agentry definitions to development server from editor and mapped customized java classes, BAPI's, POJO's & Stephandlers in config panel parameters and mapped the steplet in editor definitions.
I have copied the custom jar(ZXXX.jar) file to the java folder of the custom application along with standard WM java code & respective other.jar files and I included Agentryv5.jar as well.
Now I have modified the class path from cockpit which would point to the custom .jar file as below.
Class Path: ./ini4j.jar;./sapjco3.jar;./Java/Agentry-v5.jar;./Java;./Java/SAPWM-184.108.40.206.jar;./Java;./Java/SAPCommon-133461.jar;.java/ZWM.jar;
Restarted Agentry app and restarted SMP server. But I could not able to see the sub URL in startup.log file.
I am getting "Communications Error" from device and HTTP not found error in browser.
Could anyone please suggest the process of deploying the custom .jar file to SMP server & Modifications to JavaBE.ini , Agentry.ini file and also please correct me for the above steps.
Any help would be much appreciated.
Thanks & Regards,
Roopa M replied
Thanks for your support. The issue got resolved with java source code. As you said there is no trick to do this.
I have just modified the required BAPI, Object and converted the java code to .jar file. Deployed the custom .jar file to java folder of the application.
Mapped the custom jar files path with BAPI_WRAPPER, SAPOBJECT,STEPHANDLER in config panel.
Modified the class path with custom jar file and then restarted the server.
This resolved my issue. Many thanks for all your support.
Thanks & Regards,