blank back end tab after restarting SMP 3.0

[Former Member]

Hi,

atm I'm facing a strange problem during the deployment process of an agentry app on SMP 3.0 Installation.

Everytime the SMP is restarted the application back end configuration tab is either blank or reset to default value.

After deploying my Agentry application zip file in the app specific settings I can configure the back end settings without any issues. Also I can log off from Management Cockpit and log back on without loosing theses settings. But as soon as I am restarting the SMP Service the settings are gone.

Maybe as a result of this issue I am not able to sync with the server using ATE. I used the correct url https://{FQDN}:8081/{app} to sync but the ATE instantly shows the following error:

There aren't any errors inside the smp-server.log or the agentry logs files so I do not realy have a clue.

Would be great if someone has an idea.

Regards,

Daniel

[Former Member · Accepted solution]

I found the solution:

1. The reason for the blank back end tab was the missing Agentry-v5.jar inside the server. It is important to add this .jar to the .zip file when publishing the agentry application. Additionally the .jar hast to be included in the class path of the application. As Alternative you can copy the file to the following folder without having it inside the class path: \MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry
   
   
2. The reason for the second error concerning Communication Error 14 which instantly popped up was a wrong url.
   
   https://<FQDN-SMP-host>:8081/<application name>
   
   It is important to understand that the application name is not the name which was used when creating the new agentry application inside the smp management cockpit. You have to use the name of the agentry application how it is defined in the agentry editor.
   
   Also note that the url is case sensitive.
   

I hope this will help others facing the same issues.

Regards,

Daniel

[agentry_src · Accepted solution]

Thanks for posting the solution!

[former_member188433 · Accepted solution]

Thanks Daniel - this is a very helpful post!

[bill_froelich · Accepted solution]

1. The agentry-v5.jar is now bundled into the server and does not need to be packaged into your deployment file.

2. You can configure the urlPath in the Cockpit now to set the <application name> to anything you want.  It no longer matches the editor value.

--Bill

[Former Member]

Please check the Startup.log file.

Does it show Loading Application XXXX?

If no application is loaded then the backend Tab will be blank.

Stephen

[Former Member]

yes I can see that the application is loaded successfully.

I did the following steps:

1. created the new Agentry application in SMP Management Cockpit
2. deployed agentry.zip file in app specific settings (app was deployed successfully)
3. added the security profile default
4. specified the back end configuration in the back end tab
5. hit save
6. checked the log files and copied it to this post (see below)
7. switched back to SMP Management Cockpit and recognized that I was logged off
8. I logged back on and opened the new agentry application
9. Now I see the following back end configuration:

My entire configuration on this tab is reset to default values (this time even without restarting the smp).

I did the same procedure a few times but always with the same result. Either the Back End tab is blank or reset to default like this time.

How can this happen?

Regards,

Daniel

log file from step 6:

10:00:01 08/05/2014: Starting Agentry (64-bit Windows)

10:00:01 08/05/2014: Reading system ini file.

10:00:01 08/05/2014: Starting log file.

10:00:01 08/05/2014: Loading message groups.

10:00:01 08/05/2014: Starting threads.

10:00:01 08/05/2014:    1 initial threads.  Threads will auto-scale.

10:00:01 08/05/2014: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.

10:00:01 08/05/2014: Event: 0, 2, Key pair loaded successfully.

10:00:01 08/05/2014: Starting Agentry: Agentry Server Agent v7.0.3.159

10:00:01 08/05/2014: Event: 0, 2, Agentry Startup

10:00:01 08/05/2014: Loading 0 front ends

10:00:01 08/05/2014: Loading front end from angelvine

10:00:01 08/05/2014: WebSockets Front End: loading configuration

10:00:01 08/05/2014: Event: 17, 14, WebSockets Front End v7.0.3.159

10:00:01 08/05/2014: Starting Agentry Server Agent

10:00:01 08/05/2014: Agentry Server Agent: Starting threads.

10:00:01 08/05/2014:    1 initial threads.  Threads will auto-scale.

10:00:01 08/05/2014: Agentry Server Agent: Adding messages.

10:00:01 08/05/2014: Event: 1, 4, Agentry Server Agent v7.0.3.159

10:00:01 08/05/2014: Loading agent from ag3.dll

10:00:01 08/05/2014: Starting Server

10:00:01 08/05/2014: Server: reading config file

10:00:03 08/05/2014: Event: 20, 150, Loading Production application definitions using file "MAD4Mobile-v1-0-0-app"

10:00:03 08/05/2014: Event: 20, 152, Loading Production application definitions for default localization

10:00:03 08/05/2014: Initializing File-FileSystem from ag3filebe.dll

10:00:03 08/05/2014: FileSystem: reading configuration information.

10:00:03 08/05/2014: FileSystem: name set to 'File-FileSystem'.

10:00:03 08/05/2014: File-FileSystem Back End: initialized

10:00:03 08/05/2014: Event: 22, 4, Loaded File-FileSystem (File v7.0.3.159) from ag3filebe.dll

10:00:03 08/05/2014: Initializing Java-MaximoJavaServer from ag3javabe.dll

10:00:03 08/05/2014: MaximoJavaServer: Reading configuration information.

10:00:03 08/05/2014: MaximoJavaServer: Setting name to 'Java-MaximoJavaServer'.

10:00:03 08/05/2014: Java-MaximoJavaServer: Initialized.

10:00:03 08/05/2014: Java-MaximoJavaServer: Java Virtual Machine already initialized.

10:00:03 08/05/2014: Java-MaximoJavaServer: Initialized.

10:00:03 08/05/2014: Event: 23, 4, Loaded Java-MaximoJavaServer (Java v7.0.3.159) from ag3javabe.dll

10:00:03 08/05/2014: Event: 20, 153, Finished loading Production application definitions for default localization

10:00:03 08/05/2014: Event: 20, 151, Finished loading Production application definitions using file "MAD4Mobile-v1-0-0-app"

10:00:03 08/05/2014: Server: Starting threads.

10:00:03 08/05/2014:    1 initial threads.  Threads will auto-scale.

10:00:03 08/05/2014: Event: 20, 4, Server v7.0.3.159

10:00:03 08/05/2014: Starting front ends

10:00:03 08/05/2014: WebSockets Front End: Opening WebSockets servlet for sub-URL /MAD4Mobile

10:00:03 08/05/2014: Event: 17, 10, WebSockets Front End v7.0.3.159

10:00:03 08/05/2014: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-08-05-100001

10:00:03 08/05/2014: Event: 0, 23, Agentry startup is complete.

[Former Member]

1) If no application is loaded then the backend tab will be blank.

2) The Name of the Backends are different then prior version of the Agentry.ini.  You will need to copy the values of the old Agentry.ini into the correct locations for your backend setting tab.

Stephen