cancel
Showing results for 
Search instead for 
Did you mean: 

SMP 3.0 SP04: Agentry Application endpoints - Multiple instances of same type

Former Member
0 Kudos

Hi Experts.

So I have upgraded my local SMP 3.0 to SP04 PL01.

I am testing the multi Agentry application capabilities.

I have initially installed 1 Work Manager 6.1 and 1 Inventory Manager 4.0 (standard versions).

Application endpoints are:

WM61:     https://<FQDN_smp>:8081/SAPWM

IM40:        https://<FQDN_smp>:8081/SAPIM

So far so good - I can connect to both of them.

Problem 1.

In the startup log I will see this line for the Work Manager application:

      SAPWorkMgr6.1: Opening WebSockets servlet for sub-URL /SAPWM

This tells me the application endpoint for this application.


Question 1:

Why don't I see a corresponding line for the Inventory Manager application ?

I see the application is starting

    12:58:41 09/17/2014: Starting SAPInvMgr4.0_CWIM

But not the application endpoint !

I guessed that it should be /SAPIM, and it worked.

Problem 2:

Now I installed a second Inventory Manager.

Question 2:

What is the application Endpoint for this ?

/SAPIM is already in use !

I saw on the server that the Agentry Directory is now named com.sap.mobile.platform.server.agentry.application.<AppName>.

This makes really good sense, because this ensures uniques across applications.

However the application endpoint seems to be named from the Agentry Project name !

So what if you install the same application to support multiple backends, how do you ensure uniqueness of your application endpoints ?

I hope someone can answer this.

Thanks.

Søren Hansen

Accepted Solutions (1)

Accepted Solutions (1)

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Soren,

As Steve mentioned, if you don't see both endpoint references in the startup.log then there is an error somewhere with the application as it is failing to load.  I am also setting up my SP04 server and have two Agentry applications configured and on startup both endpoints show in the log and I am able to get to both "I am here!" messages from my browser.

--Bill

Former Member
0 Kudos

Bill and Steve.

As mentioned in the original post, I am able to connect to both Agentry Servers. Both application endpoints:

WM61:     https://<FQDN_smp>:8081/SAPWM

IM40:        https://<FQDN_smp>:8081/SAPIM

are responding with "I am here!", and I can connect via devices and do synchronizations. So from a user perspective everything works (when I only have one instance of each type WM/IM).

However when configuring two agentry servers of the same application type (in my case two Inventory Managers), I am unable to distinguish as the Agentry Project name is used for the endpoint to connect to the Agentry server. I was hoping to see some info in the startup log but that was not possible.

So I have two Agentry servers to which I should access via https://<FQDN_smp>:8081/SAPIM - but how do I distinguish between the two ?

Søren.https://<FQDN_smp>:8081/SAPWM

Message was edited by: Søren Hansen

Former Member
0 Kudos

The SubURL that is use is the name of the application defined in the editor.  If you change the name in the editor for one of the applications then you would will have two different subURLs.

Former Member
0 Kudos

Steve,

I get the point, and actually think that will work.

However I think it is very bad design, because not everybody will have the skills to do so.

Another thing:

When we do development cycles, it would be nice to be able to install the same Agentry application in multiple development instances on the same (development) server. Each used by indivdual developers. And then a production instance to be used by the testers.

With this limitation, we would have to rename our Agentry project every time we publish to a new instance, and each developer would have to use a unique name for his application version. It may be doable, but not very nice. Someone will surely screw up at some point in time !

Simply switching from a development publish to a production publish (two separate Agentry instances), would require you to rename the Agentry application name.

Also you may want to install multiple production servers, each serving a different SAP backend. If you don't have any Agentry development skills, this is not possible.

I think it is a bad design. The Application ID should have been used as the URL identifier, just as it is on the file system.

Søren.

Former Member
0 Kudos

Hi Steve,

I can confirm that your "workaround" is working.

I have deployed the second Agentry instance under a new Agentry application name, and now I can reference both instances independently.

But as outlined previously, I think the design is bad.

Who will listen to any good ideas for improvements on the platform ?

Søren.

Former Member
0 Kudos

You can always open a ticket with support and they can direct it to the development team.

Answers (1)

Answers (1)

Former Member
0 Kudos

Can you confirm the IM application is loading correctly?  Are there any errors in the Application's startup.log