Agentry Client Not connected with dev server

[mohanasundaram_ganesan]

Hi All,

I seek if any one could help on the agentry architecture part of SMP and its infrastructure setup. Currently we are doing some POC with agentry components of SMP 2.3 server. We have installed all 64 bit version of SMP and Agentry tools in 64 bit version of windows 8 PC. But I don’t see Agentry Test Environment is available for 64 bit windows. Is it so? Because whenever I start the ATE tool, it gets hanged and says “Agentry Client for Win32 is not responding”. Is there any specific reason to be so?

Also after we export agentry app as jar file and copy it to dev server along with ini, jar and dlls and also modifying some configuration parameters in Agentry.ini and JavaBE.ini files, agentry admin client gives log as below.

18:48:01 11/11/2013: Starting server (64-bit Windows)

18:48:02 11/11/2013: Administration client command port is 13271, status port is 13272

18:48:02 11/11/2013: Looking for initial status connection...

18:48:02 11/11/2013: Reading system ini file.

18:48:02 11/11/2013: ID: Agentry, Name: ???, Location: ???

18:48:02 11/11/2013: Starting log file.

18:48:02 11/11/2013: Loading message groups.

18:48:02 11/11/2013: Starting threads.

18:48:02 11/11/2013:    1 initial threads.  Threads will auto-scale.

18:48:02 11/11/2013: Starting Server: Agentry v6.1.0.3

18:48:02 11/11/2013: Event: 0, 2, System Startup

18:48:02 11/11/2013: Loading 1 front ends

18:48:02 11/11/2013: Loading front end from angelvine.dll

18:48:02 11/11/2013: ANGEL Front End: reading init files.

18:48:02 11/11/2013: Event: 17, 14, ANGEL Front End v6.1.0.3

18:48:02 11/11/2013: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.

18:48:02 11/11/2013: Event: 0, 2, Key pair loaded successfully.

18:48:02 11/11/2013: Starting Server Agent.

18:48:02 11/11/2013: Agentry: Starting threads.

18:48:02 11/11/2013:    1 initial threads.  Threads will auto-scale.

18:48:02 11/11/2013: Agentry: Adding messages.

18:48:02 11/11/2013: Event: 1, 4, Agentry v6.1.0.3

18:48:02 11/11/2013: Loading 1 agents

18:48:02 11/11/2013: Loading agent from ag3.dll

18:48:02 11/11/2013: Starting Server

18:48:02 11/11/2013: Server: reading ini file

18:48:02 11/11/2013: Event: 0, 30, Admin client 192.168.5.132:13273 authenticated successfully.

18:48:02 11/11/2013: Event: 0, 27, Admin client 192.168.5.132:13273 has connected

18:48:02 11/11/2013: Initializing 1-Java from ag3javabe.dll

18:48:02 11/11/2013: SystemConnection-1: Reading configuration information.

18:48:02 11/11/2013: SystemConnection-1: Setting name to 'Java Back End'.

18:48:02 11/11/2013: Java Back End: Initialized.

18:48:02 11/11/2013: Exception: 18:48:02 11/11/2013 : 25 (General), Unknown Exception (Java Back End - java.lang.UnsupportedClassVersionError: com/syclo/agentry/internal/AgentryManagedObject (Unsupported major.mino, ), javaBE.cpp#445:JavaBackEnd::init

18:48:02 11/11/2013: Failed to init Java Back End (Java v6.1.0.3 (JVM version 1.4.2_38, AJAPI version  build )) from ag3javabe.dll

18:48:02 11/11/2013: Event: 20, 150, Loading Development application definitions

18:48:02 11/11/2013: Event: 20, 152, Loading Development application definitions for default localization

18:48:02 11/11/2013: Event: 20, 153, Finished loading Development application definitions for default localization

18:48:02 11/11/2013: Event: 20, 151, Finished loading Development application definitions

18:48:02 11/11/2013: Event: 20, 4, Server v6.1.0.3

18:48:02 11/11/2013: Starting front ends

18:48:02 11/11/2013: ANGEL Front End: Starting threads.

18:48:02 11/11/2013:    3 initial threads.  Threads will auto-scale.

18:48:02 11/11/2013: ANGEL Front End: opening listen socket on port 7003

18:48:02 11/11/2013: Event: 17, 10, 0.0.0.0:7003 open

18:48:02 11/11/2013: Event: 17, 10, ANGEL Front End v6.1.0.3

18:48:02 11/11/2013: Event: 0, 0, Old log files moved into Logs-Rolled\2013-11-11-184801

18:48:02 11/11/2013: Event: 0, 23, 1

18:48:02 11/11/2013: Event: 0, 2, Server startup is complete.

18:48:02 11/11/2013: Agentry Application startup complete

Is there any exception in my deployment or infrastructure setup?.  App details are also configured with required BAPI wrappers in the SAP addon configuration panel.

Could any body help to sort this and run the app in ATE?

Tags edited by: Michael Appleby

[atif_bhatti]

A small important parameter which you may needed later to debug your java code is

under Agentry.ini file

section

add the following parameter.

[Java-1]

nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7090,server=y,suspend=n

thanks