SMP 3.0 SP4 issue with multiple Agentry apps

[lukasz_grochal]

We have just upgraded SMP 3.0 to the latest SP4 with PL1 and deployed 2 Agentry apps - SAP Work Manager 6.1 and SAP Inventory Manager 4.0. Agentry server start-up and event logs do not show any issues however it is only possible to connect to a single app. In our case SAP Inventory Manager works OK but trying to log on to Work Manager from another client fails. We tried with the Work Manager and Inventory Manager clients for iOS (2 separate apps) as well as 2 separate installs of the Windows client. The following error is displayed in the client when trying to log on with the 2nd app.

Now, if only one app is deployed at a time, the client can connect just fine to either one. Are there any additional steps/adjustments required in addition to the regular deployment/publish steps?

Thanks,

Lukasz

[lukasz_grochal]

Just as an update - I have upgraded another SMP 3.0 server to SP4 PL1 and deployed SAP Work Manager and SAP Inventory Manager to it. It's got the same exact issue. The apps are accessible on the server via their URL's and clients connect to them but the second app (alphabetically) always shows the "client not logged into the server (2)" error. This happens after the user has been logged on. So the client connects to SMP, SMP logs on to ECC but then the error happens. Seems more like a client or ECC error than SMP's.

If you indeed got these 2 apps to work concurrently, please let me know the exact deployment steps.

Thanks,

Lukasz

[Former Member]

Are you using the clients from SDK SP05?

[lukasz_grochal]

Hello Stephen,

Actually I was in the process of downloading the latest SDK when you posted your reply. Now after installing the new Windows client I can connect to both apps. Thanks for the hint.

It still does not work on Apple devices as the iOS clients available on iTunes have not been updated yet. I guess it's just a matter of time though.

Lukasz

[Former Member]

for the iOS client you will need to wait until the new version is on the App store.  If you have an Apple Enterprise developer license you can get the client branded with a development certificate that you can use for your company.  You will need to contact support for that.

[lukasz_grochal]

Also, I've noticed that the app that shows first in the applications list will work fine. It's the next one that fails.

For example I had it defined this way first:

com.sap.im40

com.sap.wm61

In that order Inventory Manager worked fine but Work Manager did not.

Now I've reversed the order to:

com.sap.wm61

com.sap.zim40

and Work Manager is working fine but Inventory Manager is not.

[i834235]

I have tried deploying multiple applications( Work Manager 6.1 and Inventory Manager 4.0) on SP04 and it works fine for me.  Only difference is in my case I gave application name as SAPWM and SAPIM.  Just to try something different by set  urlPath in App-Specific Settings for the application  that is not working as /SAPWM for Work Manager or /SAPIM for Inventory Manager.

Provide URLpath as https://<hostname>:8081/SAPWM or https://<hostname>:8081/SAPIM  while connecting to SMP server from Agentry client.

Thanks

Manju.

[lukasz_grochal]

First, I installed SMP 3.0 SP4 PL1 from scratch now but the issue persists.

The app ID does not really matter. The sub-URLs are accessible from the browser and that is what we enter in the client as well. But I did give it a try and defined the apps as SAPWM and SAPIM. To no avail though. 

The apps are deployed on SMP successfully because Agentry clients can communicate with the server and actually as mentioned in previous posts each time the user is logged into the backend system too. Also each app works fine when deployed individually. I'm starting to think it might be the backend component issue. Were any Syclo OSS notes released along with SMP 3.0 SP4?

In your case when you say that the deployment works fine did you actually test it all the way through with the clients or just by looking at the server logs and testing the sub-URLs?

[bill_froelich]

Lukasz,

I have two Agentry applications both deployed to SMP 3 SP04/PL01.  Testing with two WPF clients at the same time to the two different applications is working as expected.  I am not seeing the error you list.

Have you confirmed both apps are successfully loading on startup.  You mention Work Manager isn't working.  Have you checked the logs to confirm the startup indicates both applications loaded successfully by providing the sub-url for both applications in the startup.log file?

--Bill

[lukasz_grochal]

Hi Bill,

The sub URLs do not show in the start up log. However they are accessible via the browser with responses "I'm here!". Also, it appears that the client logs on the user but then an error happens. That means the apps are accessible from the client and communication with the ECC backend is initiated. I cannot see any error in any of the logs though, including the server log. Again, with one app deployed at a time everything works perfect regardless of what the app is.

We installed SP4 as an upgrade and not a clean install. Should we try a clean one instead?

Here's the contents of the start up log:

06:50:08 09/18/2014: Starting Agentry (64-bit Windows)

06:50:08 09/18/2014: Reading system ini file.

06:50:08 09/18/2014: Starting log file.

06:50:08 09/18/2014: Loading message groups.

06:50:08 09/18/2014: Starting threads.

06:50:08 09/18/2014:    1 initial threads.  Threads will auto-scale.

06:50:08 09/18/2014: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.

06:50:08 09/18/2014: Event: 0, 2, Key pair loaded successfully.

06:50:08 09/18/2014: Starting Agentry: Agentry Server Agent v7.0.4.8

06:50:08 09/18/2014: Event: 0, 2, Agentry Startup

06:50:08 09/18/2014: Loading 0 front ends

06:50:08 09/18/2014: Starting Agentry Server Agent

06:50:08 09/18/2014: Agentry Server Agent: Starting threads.

06:50:08 09/18/2014:    1 initial threads.  Threads will auto-scale.

06:50:08 09/18/2014: Agentry Server Agent: Adding messages.

06:50:08 09/18/2014: Event: 1, 4, Agentry Server Agent v7.0.4.8

06:50:08 09/18/2014: Loading agent from ag3.dll

06:50:08 09/18/2014: Starting com.sap.im40

06:50:08 09/18/2014: Event: 20, 4, com.sap.im40 v7.0.4.8

06:50:08 09/18/2014: Loading agent from ag3.dll

06:50:08 09/18/2014: Starting com.sap.wm61

06:50:08 09/18/2014: Event: 21, 4, com.sap.wm61 v7.0.4.8

06:50:08 09/18/2014: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-09-18-065008

06:50:08 09/18/2014: Event: 0, 23, Agentry startup is complete

And here's the event log:

09/18/2014 06:50:08, 0,         0,         0, Thr       3300, New files opened events.log, messages.log

09/18/2014 06:50:08, 0,         0,         2, Thr       3300, Loading the Agentry Runtime's public/private key for password exchanges.

09/18/2014 06:50:08, 0,         0,         2, Thr       3300, Key pair loaded successfully.

09/18/2014 06:50:08, 0,         0,         2, Thr       3300, Agentry Startup

09/18/2014 06:50:08, 0,         1,         4, Thr       3300, Agentry Server Agent v7.0.4.8

09/18/2014 06:50:08, 0,        20,         4, Thr       3300, com.sap.im40 v7.0.4.8

09/18/2014 06:50:08, 0,        21,         4, Thr       3300, com.sap.wm61 v7.0.4.8

09/18/2014 06:50:08, 0,         0,         0, Thr       3300, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-09-18-065008

09/18/2014 06:50:08, 0,         0,        23, Thr       3300, Agentry startup is complete.

09/18/2014 06:50:09, 0,        20,         5, Thr       3300, com.sap.im40

09/18/2014 06:50:09, 0,        20,       150, Thr       2904, Loading Production application definitions using file "SAPIM-v1-0-0-app"

09/18/2014 06:50:09, 0,        20,       152, Thr       2904, Loading Production application definitions for default localization

09/18/2014 06:50:16, 0,        23,         4, Thr       2904, Loaded Java Back End (Java v7.0.4.8) from ag3javabe.dll

09/18/2014 06:50:17, 0,        20,       153, Thr       2904, Finished loading Production application definitions for default localization

09/18/2014 06:50:17, 0,        20,       151, Thr       2904, Finished loading Production application definitions using file "SAPIM-v1-0-0-app"

09/18/2014 06:50:17, 0,        17,        14, Thr       3300, com.sap.im40 v7.0.4.8

09/18/2014 06:50:17, 0,        20,         4, Thr       3300, com.sap.im40 v7.0.4.8

09/18/2014 06:50:17, 0,        17,        10, Thr       3300, com.sap.im40 v7.0.4.8

09/18/2014 06:50:18, 0,        21,         5, Thr       3300, com.sap.wm61

09/18/2014 06:50:18, 0,        21,       150, Thr       3620, Loading Production application definitions using file "SAPWM-v1-0-0-app"

09/18/2014 06:50:18, 0,        21,       152, Thr       3620, Loading Production application definitions for default localization

09/18/2014 06:50:35, 0,        24,         4, Thr       3620, Loaded HTTP-XML Back End (HTTPXML v7.0.4.8) from ag3httpxmlbe.dll

09/18/2014 06:50:38, 0,        23,         4, Thr       3620, Loaded Java Back End (Java v7.0.4.8) from ag3javabe.dll

09/18/2014 06:50:40, 0,        21,       153, Thr       3620, Finished loading Production application definitions for default localization

09/18/2014 06:50:40, 0,        21,       151, Thr       3620, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"

09/18/2014 06:50:40, 0,        17,        14, Thr       3300, com.sap.wm61 v7.0.4.8

09/18/2014 06:50:40, 0,        21,         4, Thr       3300, com.sap.wm61 v7.0.4.8

09/18/2014 06:50:40, 0,        17,        10, Thr       3300, com.sap.wm61 v7.0.4.8

[bill_froelich]

I did do a clean install but only because I recently lost my environments due to a hard drive issue and am currently in the process of reloading from a new imaged hard drive.

Worth trying.  I will also have to get some more complex apps loaded on my environment to see if that changes anything.

--Bill