SAP Moble Platform 3.0 with Agentry 7.0 application configuration

[Former Member]

Hi,

we try to migrate from SMP 2.3 to SMP 3.0.

• We installed the MobilePlatform3 as development server and the SDK 3.0 SP04 PL01.
• After that we import the 2.3 project in the new eclips with the agentry  editor plugin for 7.0.3. We checked if all transmit configurations are set to WebSockets over HTTPS as connect type.
• After that we create a application for Agnetry Apps in the management cockpit and found the agentry.ini in this directory: "SMPHome Directory/\Server\configuration\com.sap.mobile.platform.server.agentry.application. We publish the agentry app to this agentry.ini and see the BACK END configuration in the management cockpit. As authentication we use "no authentication challenge".
• Afte restart the SMP server we see in the logs no errors. In the agentry server log we see that the application was loaded. We test the agentry server in the browser with this adress https://{servername}:8081/{sub-url} prüfen and get the "I am here!" message

Now we try to connect from the ATE (version 7.0.3.605)(installed on the same server like the smp) to the agentry server with this adress:"{servername}:8081" and get this error:

Unexpected disconnection from server (11)

Connection failed

Ending transmission

if we try only the server without the port we get this message:

Requesting Public Key from Server

The printer queue is full.

Communications error (14)

Connection failed

Ending transmission

We check the smp3 server logs and the agentyr logs but nothing is in. We set the log level to debug but nothing.

We dont know where we could search for the error. What can we do or where is the error in our configuration.

Thanks,

André

Message was edited by: Michael Appleby

[Former Member · Accepted solution]

OK,

now we have the answer. in the Client we need to use the full quallified Serverstring to connect the agentry server: "https://SERVERNAME:8081/Appname" Without the "https://" dos the server not responds.

André

[Former Member]

Dear Andre Nehm , As per SAP Agnetry : Error 11 stands for : The connection that had been established between the client and server has been broken. This can be caused by a physical disruption in the network (ie,phone line unplugged), a network or MID Station timeout, or by terminating the server or client applications. And Error 14 stands for : This response is sent when the client is unable to contact the server (or MID station) for initial Handshaking. It usually occurs when the Agentry server is not running or when an invalid server name or port is specified. It also can happen when the network has been disrupted, as in Error 11. So , as per your error it looks like you dont have proper network connectivity or you need to check with network people with network fi settings . Thanks & Regards , Kunal Varaiya

[Former Member]

Dear Kunal Varaiya,

thanks for the explanation of the errors. But i think it could not be a network problem because the SMP3 Server and the ATE runs on the same machine. And the test with the webbrowser says that we have connection to the agentry server ("I am here!") or did we see something wrong.

André

[Former Member]

Dear Andre , I am Here message your are getting part of server(it means your server is running fine and client can communicate to server ) But when you are getting error 11 and 14 means when ATE try to connect to server in between might be problem with network . Also i would suggest can you reset your ATE once and try to connect to server . Thanks & Regards , Kunal Varaiya

[Former Member]

Can you post a copy of your Startup.log file for review?

Stephen

[Former Member]

Hi Stephen i do not know how to upload a file to the forum so here is the the startup.log file:

17:55:56 09/03/2014: Starting Agentry (64-bit Windows)

17:55:57 09/03/2014: Reading system ini file.

17:55:57 09/03/2014: Starting log file.

17:55:57 09/03/2014: Loading message groups.

17:55:57 09/03/2014: Starting threads.

17:55:57 09/03/2014:    1 initial threads.  Threads will auto-scale.

17:55:57 09/03/2014: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.

17:55:57 09/03/2014: Event: 0, 2, Key pair loaded successfully.

17:55:57 09/03/2014: Starting Agentry: Agentry Server Agent v7.0.3.159

17:55:57 09/03/2014: Event: 0, 2, Agentry Startup

17:55:57 09/03/2014: Loading 0 front ends

17:55:57 09/03/2014: Loading front end from angelvine

17:55:57 09/03/2014: WebSockets Front End: loading configuration

17:55:57 09/03/2014: Event: 17, 14, WebSockets Front End v7.0.3.159

17:55:57 09/03/2014: Starting Agentry Server Agent

17:55:57 09/03/2014: Agentry Server Agent: Starting threads.

17:55:57 09/03/2014:    1 initial threads.  Threads will auto-scale.

17:55:57 09/03/2014: Agentry Server Agent: Adding messages.

17:55:57 09/03/2014: Event: 1, 4, Agentry Server Agent v7.0.3.159

17:55:57 09/03/2014: Loading agent from ag3.dll

17:55:57 09/03/2014: Starting Server

17:55:57 09/03/2014: Server: reading config file

17:55:58 09/03/2014: Event: 20, 150, Loading Development application definitions

17:56:01 09/03/2014: Initializing SQL-MietraSQLConnection from ag3sqlbe.dll

17:56:01 09/03/2014: MietraSQLConnection Back End: reading config information.

17:56:01 09/03/2014: MietraSQLConnection: name set to 'SQL-MietraSQLConnection'.

17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: reading query config information.

17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: initialized

17:56:01 09/03/2014: Event: 21, 4, Loaded SQL-MietraSQLConnection (SQL v7.0.3.159) from ag3sqlbe.dll

17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: connecting 'dba' to database 'CDB_SDRSUP2'

17:56:01 09/03/2014: Event: 21, 101, dB Connect

17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: started

17:56:01 09/03/2014: Event: 20, 152, Loading Development application definitions for default localization

17:56:01 09/03/2014: Event: 20, 153, Finished loading Development application definitions for default localization

17:56:01 09/03/2014: Event: 20, 151, Finished loading Development application definitions

17:56:01 09/03/2014: Server: Starting threads.

17:56:01 09/03/2014:    1 initial threads.  Threads will auto-scale.

17:56:01 09/03/2014: Event: 20, 4, Server v7.0.3.159

17:56:01 09/03/2014: Starting front ends

17:56:01 09/03/2014: WebSockets Front End: Opening WebSockets servlet for sub-URL /Mietra

17:56:01 09/03/2014: Event: 17, 10, WebSockets Front End v7.0.3.159

17:56:01 09/03/2014: Event: 0, 0, Old log files moved into C:\SMP\MobilePlatform3\Server\log\agentry\rolled\2014-09-03-175556

17:56:01 09/03/2014: Event: 0, 23, Agentry startup is complete.

[Former Member]

In the Management Cockpit do you have Enable Auth on your SQL connection?

Stephen

[Former Member]

Yes, enable Auth is checket. Here are the complete settings for the SQL-connection in the management cockpit:

[Former Member]

Thank you.   Next check, can you post the Events.log file error that happens when you connect.

Stephen

[Former Member]

There is the event log: (the mystery thing is that nothing is logged when we try to connect:

09/03/2014 17:55:57, 0,         0,         0, Thr       8992, New files opened events.log, messages.log

09/03/2014 17:55:57, 0,         0,         2, Thr       8992, Loading the Agentry Runtime's public/private key for password exchanges.

09/03/2014 17:55:57, 0,         0,         2, Thr       8992, Key pair loaded successfully.

09/03/2014 17:55:57, 0,         0,         2, Thr       8992, Agentry Startup

09/03/2014 17:55:57, 0,        17,        14, Thr       8992, WebSockets Front End v7.0.3.159

09/03/2014 17:55:57, 0,         1,         4, Thr       8992, Agentry Server Agent v7.0.3.159

09/03/2014 17:55:58, 0,        20,       150, Thr       5488, Loading Development application definitions

09/03/2014 17:56:01, 0,        21,         4, Thr       5488, Loaded SQL-MietraSQLConnection (SQL v7.0.3.159) from ag3sqlbe.dll

09/03/2014 17:56:01, 0,        21,       101, Thr       5488, dB Connect

09/03/2014 17:56:01, 0,        20,       152, Thr       5488, Loading Development application definitions for default localization

09/03/2014 17:56:01, 0,        20,       153, Thr       5488, Finished loading Development application definitions for default localization

09/03/2014 17:56:01, 0,        20,       151, Thr       5488, Finished loading Development application definitions

09/03/2014 17:56:01, 0,        20,         4, Thr       8992, Server v7.0.3.159

09/03/2014 17:56:01, 0,        17,        10, Thr       8992, WebSockets Front End v7.0.3.159

09/03/2014 17:56:01, 0,         0,         0, Thr       8992, Old log files moved into C:\SMP\MobilePlatform3\Server\log\agentry\rolled\2014-09-03-175556

09/03/2014 17:56:01, 0,         0,        23, Thr       8992, Agentry startup is complete.

09/03/2014 18:55:57, 0,         0,         7, Thr      10892,

André