QA Move for Agentry Development
We are developing SAP WM 6.2 on SMP 3.0 SP08 , we have developed unit tested on DEV and now moving to the QA enviroment . Following are the steps we followed:
- 1. Export the Z_SAPWM_61.jar to the development server Java folder (usual
- 2. Publish a Modification Production version to C:\Agentry\PROD_STAGING.
A zip file will be generated
Open Windows Explorer: C:\Agentry\Prod_Staging
- 3. Open the shortcut to the SMP directory.
- 4. Open the Java directory and copy the Z_SAPWM_61.jar file to the
C:\Agentry\PROD_STAGING\Java directory (overwrite file in there already)
- 5. Drag and drop the C:\Agentry\PROD_STAGING\Java to the ZIP file created
in Step #2
Open QMP Control Panel - Open Windows Explorer
- 6. Open the QMP (Quality) control center with this URL:
- 7. Click on the "applications" button and select WorkManager
- 8. On the tabs, click "Client Specific Settings" tab. There will be an
option to "Publish Agentry App" and browse to a file.
- 9. Browse and select the ZIP file created in Step #2. Confirm the Java
directory is in the ZIP file.
- 10. Press "Save" which is at the bottom right of the screen
- Restarted the SMP.
But when we are connecting using Agentry Client the application is giving java(NO class execption) for data table dtAccountIndicator. I think issue is that the zip file created donot have any JAVABE.INI file , so it is referring to standard application . Can you please confirm if the steps I have done are correct for QA move.
Bill Froelich replied
The SMP3 server starting with SP04 supports multiple Agentry applications on the same server. As such, when uploading it will not go into the C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application folder but instead to the application specific folder that is created based on the app id you entered in the cockpit. In your case the C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM folder.
As a production Agentry application, the Agentry.ini and some of the other configuration files are stored in the persistence database and not in the filesystem. This is the normal behavior under SMP3.
After publishing restart either the Agentry Application through the cockpit or the SMP3 instance and try to connect to the URL.