on 01-28-2016 11:05 AM
Hi Expert,
We are using SMP 3.0 SP07 and SDK 3.0 SP08 and trying to run SAP CRM Service Manager 4.3 using below steps.
Step 1 : Creating Zip file from downloaded SAP Portal Service Manager exe file.
Step 2 : Creating and Installing application using Admin portal with Zip file.
Step 3 : Publishing SAPCRMSM-v1-0-0.agxz application as a development version to our SMP Server using eclipse.
Step 4 : Restart SMP Service.
Once Restart done our SMP Server getting dead slow and application not working.
Please find the attached screen shot for the same.
Please provide your suggestions.
Thanks,
Vijay
Hi Sahil & Bill,
We have installed Service Manager 4.3 application using development version.
But we are not able to get "I am here" using application url from browser.
One more thing ".application.lock" file is creating in every few seconds with 0kb size in application folder.
Thanks,
Vijay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Vijay,
By stating that you have nothing loaded in the backend tab after you restarted the SMP app there are a few items here and they are:
1) The startup from SMP 3.0 to the needed backend (SAP) requires that the javaBE.ini and corresponding agentry.ini is properly filled out.
2) From the discussion of our colleagues above (Bill and others - Step 1 to 8), there is an APP settings Agentry Restart that is key to get it to work. By simply restarting the entire SMP 3.0 may not be needed as it may resort to an older default application from the DB.
The key in making items work on startup is making sure item 1 and 2 above is followed.
Best Regards,
SAP Mobile Support Team
Vijay,
1. Create zip from Service manager exe downloaded from SAP Service Marketplace.
2. If development version has to be deployed, extract the zip file.
3. Import the project into eclipse using Agentry.ini file.
4. Set developmentServer=true in Agentry.ini
5. Publish development version of agentry app to same agentry,ini
6. Delete Production folder from Application folder
7. Create a zip.
8. Create new agentry app from SMP Admin cockpit and deploy the zip file that you created.
9. Test application url in browser. App must be ready to use.
10. You don't need to restart development agentry app if you do any customization in Agentry code. You can directly publish the agentry changes & they would reflect in Agentry client after next transmit.
11. While restarting server delete .application.lock file from application folder in case SMP Server restart is very slow.
Regards,
Sahil Dudeja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are trying to setup a development server I recommend the following
Steps 1-4 from above
5. Create the application id in the management cockpit.
6. Copy the extracted contents and updated Agentry.ini (minus the Application folder) to the app id folder
7. Publish development version directly to the server app id location
8. Reload Agentry app via the Cockpit Settings | Agentry App Restart (or restart SMP)
If using development I never upload a zip file. I only upload zip files if working with production published definitions.
--Bill
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.