In SMP for issues like this in Agentry SAP Work Manager:
"No backends loaded"...
or
java.lang.ClassNotFoundException: com.syclo.sap.workmanager.Server
the zip published file you use in the Cockpit needs to be reviewed.
Check for the following:
1) In the zip publish, do you have an Application folder with Production folder in it? If not that might be a problem as this will cause a "No backend loaded"
Or
2) In the Agentry.ini in your zip publish folder, please double check line per line if all the settings are correct including the [Java-1] classPath. Double check the classPath or server path. Does it still point to an agentry-v5.jar file? This should be corrected in SAP Work Manager 6.2 as 6.1 still points to the old agentry-v5.jar file. The agentry-v5.jar is embedded in SMP 3.0. But having it does not mean it will not work. The SMP 3.0 will just ignore it as how it was explained to me by my Agentry development team.
- Most likely your Agentry.ini inside the zip publish is missing some definition. Compare it with your development agentry.ini
Or
3) You have some sort of Java incompatibility happening in the SMP 3.0 server versus your mobile application.
- If you have this error your Agentry startup.log or your SMP servername.server.log may say something that you are using an incompatible AJAPI. You may need to use or change your system path variable to use the one provided by the SMP 3.0 server.
Observation: In a production environment I always see the naming convention of these multi-nodes under the Application/Production folder in the zip publish. The demo I see in production all have different names (like: SAPWM or SAPIM).
If I have to guess your issue is in the Agentry.ini inside your zip publish. Check it line per line.
Those are the ones I can think of right now.
Hope this helps,
Mark Pe
SAP Senior Support Engineer