How-to Build an Agentry Based Mobile App from Scratch Connecting to an SAP Back-end Part 1 (2)

[Former Member]

Hi All

I use next document

How-to Build an Agentry Based Mobile App from Scratch Connecting to an SAP Back-end Part 1

to understand How-to Build an Agentry Based Mobile App from Scratch Connecting to an SAP Back-end Part 1

I use

- Java 8 update 66

- Eclipse Version: 4.2.2

Build id: M20130204-1200

- Agentry Editor Plugin 70.10.0.9 com.syclo.agentry.editor.feature.feature.group SAP AG

from Agentry_70.11.0_EditorPlugin_x86_64.zip

Net framework 4.61

Version: 3.0.7.0SP Level: 07

On the page 109 it is read:

16. Save the Agentry.ini file

17. Start your Agentry Server (Restart if it is already running)

18. Your Agentry Server should now start without any error.

As I use SMP 3.0  instead of I used next Libraries in Eclipse Java Project

  ini4j.jar

  SAPCommon-133461.jar

  sapjco3.jar

  Agentry-v5.jar

I put jar files in

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.FlightBooking\

folder

.\sapjco3.jar

.\Java\ini4j.jar

.\Java\SAPCommon-133461.jar

.\Java\ZFlightBooking.jar

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.FlightBooking\Agentry.ini

contains next info

[Configuration]
developmentServer=true
enableOverrideFile=Enables.ini
clientStringsFile=ClientText.ini
applicationStringsFile=ApplicationText.ini
applicationGlobalsFile=Globals.ini
clientStringNamesFile=ClientStringNames.ini
overrideTypesFile=OverrideTypes.ini
transmitConfigurationFile=TransmitConfigurations.ini
enableTransactionFailureHandling=false
enableFailedTransactionLogging=true
failedTransactionsQueue=FailedTransactionsQueue
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
apnsEnabled=true
apnsCertificateDirectory=apnsCertificates
apnsCertificatePassword=Rzdrj~SwixoAqzmbVxgi
apnsCertificatePasswordEncoded=true
gcmEnabled=true
gcmServerLink=https://android.googleapis.com/gcm/send
gcmServerAuthorizationKey=Authorization:key=AIzaSyDi0qWQEewdbmNSV_o9QNtSQrlxPnBXtBM
trustedCertificateStore=


[SpinDoc]
facePath=sql\custom;sql


;Use this section to enter TimeZoneAlias values
[TimeZoneAlias]


[Java-1]
enableAuthentication=true
;classPath=./Java/ZFlightBooking.jar;ini4j.jar;sapjco.jar;SAPCommon-130881.jar;
classPath=./Java/ini4j.jar;./sapjco3.jar;./Java/SAPCommon-133461.jar;./Java/ZFlightBooking.jar;
serverClass=com/syclo/sap/sflight/server/Server

When I restarted the SMP I got next errors in the log files

C:\SAP\MobilePlatform3\Server\log\agentry\startup.log

11:04:56 02/17/2016: Starting Agentry (64-bit Windows)
11:04:56 02/17/2016: Reading system ini file.
11:04:56 02/17/2016: Starting log file.
11:04:56 02/17/2016: Loading message groups.
11:04:56 02/17/2016: Starting threads.
11:04:56 02/17/2016:    1 initial threads.  Threads will auto-scale.
11:04:56 02/17/2016: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
11:04:56 02/17/2016: Event: 0, 2, Key pair loaded successfully.
11:04:56 02/17/2016: Starting Agentry: Agentry Server Agent v130.7.0.4
11:04:56 02/17/2016: Event: 0, 2, Agentry Startup
11:04:56 02/17/2016: Loading 0 front ends
11:04:56 02/17/2016: Starting Agentry Server Agent
11:04:56 02/17/2016: Agentry Server Agent: Starting threads.
11:04:56 02/17/2016:    1 initial threads.  Threads will auto-scale.
11:04:56 02/17/2016: Agentry Server Agent: Adding messages.
11:04:56 02/17/2016: Event: 1, 4, Agentry Server Agent v130.7.0.4
11:04:56 02/17/2016: Loading agent from ag3.dll
11:04:56 02/17/2016: Starting FlightBooking
11:04:56 02/17/2016: FlightBooking: reading config file
11:04:58 02/17/2016: Event: 20, 150, Loading Development application definitions
11:04:58 02/17/2016: Initializing Java-BackendSAPConnection from ag3javabe.dll
11:04:58 02/17/2016: BackendSAPConnection: Reading configuration information.
11:04:58 02/17/2016: BackendSAPConnection: Setting name to 'Java-1'.
11:04:58 02/17/2016: Java-1: Initialized.
11:04:58 02/17/2016: Java-1: Java Virtual Machine already initialized.
11:04:58 02/17/2016: Exception: 11:04:58 02/17/2016 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path), 
11:04:58 02/17/2016: Failed to init Java-1 (Java v130.7.0.4) from ag3javabe.dll
11:04:58 02/17/2016: Event: 20, 152, Loading Development application definitions for default localization
11:04:58 02/17/2016: Event: 20, 151, Finished loading Development application definitions
11:04:58 02/17/2016: FlightBooking: Starting threads.
11:04:58 02/17/2016:    1 initial threads.  Threads will auto-scale.
11:04:58 02/17/2016: Loading front end from angelvine
11:04:58 02/17/2016: FlightBooking: loading configuration
11:04:58 02/17/2016: Event: 17, 14, FlightBooking v130.7.0.4
11:04:58 02/17/2016: Event: 20, 4, FlightBooking v130.7.0.4
11:04:58 02/17/2016: Loading agent from ag3.dll
11:04:58 02/17/2016: Starting SAPWM62
11:04:58 02/17/2016: Event: 21, 4, SAPWM62 v130.7.0.4
11:04:58 02/17/2016: Loading agent from ag3.dll
11:04:58 02/17/2016: Starting SAPWM62_NEW
11:04:58 02/17/2016: Event: 22, 4, SAPWM62_NEW v130.7.0.4
11:04:58 02/17/2016: Starting front ends
11:04:58 02/17/2016: Starting front end FlightBooking
11:04:58 02/17/2016: FlightBooking: Opening WebSockets servlet for sub-URL /FlightBooking
11:04:58 02/17/2016: Event: 17, 10, FlightBooking v130.7.0.4
11:04:58 02/17/2016: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-02-17-110456
11:04:58 02/17/2016: Event: 0, 23, Agentry startup is complete.

C:\SAP\MobilePlatform3\Server\log\agentry\events.log

02/17/2016 11:04:56, 0,         0,         0, Thr       4684, New files opened events.log, messages.log
02/17/2016 11:04:56, 0,         0,         2, Thr       4684, Loading the Agentry Runtime's public/private key for password exchanges.
02/17/2016 11:04:56, 0,         0,         2, Thr       4684, Key pair loaded successfully.
02/17/2016 11:04:56, 0,         0,         2, Thr       4684, Agentry Startup
02/17/2016 11:04:56, 0,         1,         4, Thr       4684, Agentry Server Agent v130.7.0.4
02/17/2016 11:04:58, 0,        20,       150, Thr       2548, Loading Development application definitions
02/17/2016 11:04:58, 1,        20,        18, Thr       2548, JAVA EXCEPTION CAUGHT: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
02/17/2016 11:04:58, 0,        20,       152, Thr       2548, Loading Development application definitions for default localization
02/17/2016 11:04:58, 0,        20,       151, Thr       2548, Finished loading Development application definitions
02/17/2016 11:04:58, 0,        17,        14, Thr       4684, FlightBooking v130.7.0.4
02/17/2016 11:04:58, 0,        20,         4, Thr       4684, FlightBooking v130.7.0.4
02/17/2016 11:04:58, 0,        21,         4, Thr       4684, SAPWM62 v130.7.0.4
02/17/2016 11:04:58, 0,        22,         4, Thr       4684, SAPWM62_NEW v130.7.0.4
02/17/2016 11:04:58, 0,        17,        10, Thr       4684, FlightBooking v130.7.0.4
02/17/2016 11:04:58, 0,         0,         0, Thr       4684, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-02-17-110456
02/17/2016 11:04:58, 0,         0,        23, Thr       4684, Agentry startup is complete.
02/17/2016 11:05:01, 0,        21,         5, Thr       4684, SAPWM62
02/17/2016 11:05:02, 0,        21,       150, Thr       4116, Loading Production application definitions using file "SAPWM-v1-0-0-app"
02/17/2016 11:05:02, 0,        21,       152, Thr       4116, Loading Production application definitions for default localization
02/17/2016 11:05:07, 0,        24,         4, Thr       4116, Loaded HTTP-XML Back End (HTTPXML v130.7.0.4) from ag3httpxmlbe.dll
02/17/2016 11:05:12, 0,        23,         4, Thr       4116, Loaded Java Back End (Java v130.7.0.4) from ag3javabe.dll
02/17/2016 11:05:13, 0,        21,       153, Thr       4116, Finished loading Production application definitions for default localization
02/17/2016 11:05:13, 0,        21,       151, Thr       4116, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
02/17/2016 11:05:13, 0,        17,        14, Thr       4684, SAPWM62 v130.7.0.4
02/17/2016 11:05:13, 0,        21,         4, Thr       4684, SAPWM62 v130.7.0.4
02/17/2016 11:05:13, 0,        17,        10, Thr       4684, SAPWM62 v130.7.0.4
02/17/2016 11:06:06, 0,        22,         5, Thr       4684, SAPWM62_NEW
02/17/2016 11:06:09, 0,        22,       150, Thr       1008, Loading Production application definitions using file "SAPWM-v1-0-0-app"
02/17/2016 11:06:10, 0,        22,       152, Thr       1008, Loading Production application definitions for default localization
02/17/2016 11:06:35, 0,        24,         4, Thr       1008, Loaded HTTP-XML Back End (HTTPXML v130.7.0.4) from ag3httpxmlbe.dll
02/17/2016 11:06:48, 0,        23,         4, Thr       1008, Loaded Java Back End (Java v130.7.0.4) from ag3javabe.dll
02/17/2016 11:06:51, 0,        22,       153, Thr       1008, Finished loading Production application definitions for default localization
02/17/2016 11:06:51, 0,        22,       151, Thr       1008, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
02/17/2016 11:06:51, 0,        22,       150, Thr       1008, Loading Production application definitions using file "SAPWM-v1-0-5-app"
02/17/2016 11:06:51, 0,        22,       152, Thr       1008, Loading Production application definitions for default localization
02/17/2016 11:07:16, 0,        22,       153, Thr       1008, Finished loading Production application definitions for default localization
02/17/2016 11:07:18, 0,        22,       151, Thr       1008, Finished loading Production application definitions using file "SAPWM-v1-0-5-app"
02/17/2016 11:07:19, 0,        22,       150, Thr       1008, Loading Production application definitions using file "SAPWM-v1-0-6-app"
02/17/2016 11:07:19, 0,        22,       152, Thr       1008, Loading Production application definitions for default localization
02/17/2016 11:07:37, 0,        22,       153, Thr       1008, Finished loading Production application definitions for default localization
02/17/2016 11:07:40, 0,        22,       151, Thr       1008, Finished loading Production application definitions using file "SAPWM-v1-0-6-app"
02/17/2016 11:07:40, 0,        22,       150, Thr       1008, Loading Production application definitions using file "SAPWM-v1-0-7-app"
02/17/2016 11:07:40, 0,        22,       152, Thr       1008, Loading Production application definitions for default localization
02/17/2016 11:07:54, 0,        22,       153, Thr       1008, Finished loading Production application definitions for default localization
02/17/2016 11:07:55, 0,        22,       151, Thr       1008, Finished loading Production application definitions using file "SAPWM-v1-0-7-app"
02/17/2016 11:07:55, 0,        22,       150, Thr       1008, Loading Production application definitions using file "SAPWM-v1-0-8-app"
02/17/2016 11:07:55, 0,        22,       152, Thr       1008, Loading Production application definitions for default localization
02/17/2016 11:08:16, 0,        22,       153, Thr       1008, Finished loading Production application definitions for default localization
02/17/2016 11:08:21, 0,        22,       151, Thr       1008, Finished loading Production application definitions using file "SAPWM-v1-0-8-app"
02/17/2016 11:08:21, 0,        22,       150, Thr       1008, Loading Production application definitions using file "SAPWM-v1-0-9-app"
02/17/2016 11:08:21, 0,        22,       152, Thr       1008, Loading Production application definitions for default localization
02/17/2016 11:08:40, 0,        22,       153, Thr       1008, Finished loading Production application definitions for default localization
02/17/2016 11:08:41, 0,        22,       151, Thr       1008, Finished loading Production application definitions using file "SAPWM-v1-0-9-app"
02/17/2016 11:08:42, 0,        22,       150, Thr       1008, Loading Production application definitions using file "SAPWM-v1-0-11-app"
02/17/2016 11:08:42, 0,        22,       152, Thr       1008, Loading Production application definitions for default localization
02/17/2016 11:08:58, 0,        22,       153, Thr       1008, Finished loading Production application definitions for default localization
02/17/2016 11:09:02, 0,        22,       151, Thr       1008, Finished loading Production application definitions using file "SAPWM-v1-0-11-app"
02/17/2016 11:09:09, 0,        17,        14, Thr       4684, SAPWM62_NEW v130.7.0.4
02/17/2016 11:09:09, 0,        22,         4, Thr       4684, SAPWM62_NEW v130.7.0.4
02/17/2016 11:09:11, 1,         2,        48, Thr       1008, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn
02/17/2016 11:09:12, 1,         2,        48, Thr       1008, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn
02/17/2016 11:09:12, 1,         2,        48, Thr       1008, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn
02/17/2016 11:09:12, 1,         2,        48, Thr       1008, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn
02/17/2016 11:09:12, 1,         2,        48, Thr       1008, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn
02/17/2016 11:09:12, 1,         2,        48, Thr       1008, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn
02/17/2016 11:09:18, 0,        17,        10, Thr       4684, SAPWM62_NEW v130.7.0.4

[bill_froelich]

Based I the error I suspect the problem is related to the other Jco support files.  Did you also put the other jco files in the same directory as the sapjco3.jar?  Jco needs three files in the same directory.

sapjco3.jar

librfc32.dll

sapjco3.dll

Please confirm they are in place.

I also see an unrelated Work Manager error in your log.  EADDRINUSE, Attempt to listen on an address in use.  This indicates you have multiple applications with HTTPXML backends that are all attempting to listen on the same port.  You should make sure the port numbers for each application are unique.

--Bill

[Former Member]

I copied sapjco3.dll

to

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.FlightBooking\

The librfc32.dll  is in the C:\Windows\SysWOW64\

Don't know how it got there but it must be accessible from anywhere.

Restarted SMP

Text of error changed

19:00:20 02/17/2016: Starting Agentry (64-bit Windows)
19:00:29 02/17/2016: Reading system ini file.
19:00:29 02/17/2016: Starting log file.
19:00:29 02/17/2016: Loading message groups.
19:00:29 02/17/2016: Starting threads.
19:00:29 02/17/2016:    1 initial threads.  Threads will auto-scale.
19:00:29 02/17/2016: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
19:00:29 02/17/2016: Event: 0, 2, Key pair loaded successfully.
19:00:29 02/17/2016: Starting Agentry: Agentry Server Agent v130.7.0.4
19:00:29 02/17/2016: Event: 0, 2, Agentry Startup
19:00:29 02/17/2016: Loading 0 front ends
19:00:29 02/17/2016: Starting Agentry Server Agent
19:00:29 02/17/2016: Agentry Server Agent: Starting threads.
19:00:29 02/17/2016:    1 initial threads.  Threads will auto-scale.
19:00:29 02/17/2016: Agentry Server Agent: Adding messages.
19:00:29 02/17/2016: Event: 1, 4, Agentry Server Agent v130.7.0.4
19:00:29 02/17/2016: Loading agent from ag3.dll
19:00:29 02/17/2016: Starting FlightBooking
19:00:29 02/17/2016: FlightBooking: reading config file
19:00:30 02/17/2016: Event: 20, 150, Loading Development application definitions
19:00:31 02/17/2016: Initializing Java-BackendSAPConnection from ag3javabe.dll
19:00:31 02/17/2016: BackendSAPConnection: Reading configuration information.
19:00:31 02/17/2016: BackendSAPConnection: Setting name to 'Java-1'.
19:00:31 02/17/2016: Java-1: Initialized.
19:00:31 02/17/2016: Java-1: Java Virtual Machine already initialized.
19:00:32 02/17/2016: Exception: 19:00:32 02/17/2016 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: serialNumber is null in SERVICE_LOGON section), 
19:00:32 02/17/2016: Failed to init Java-1 (Java v130.7.0.4) from ag3javabe.dll
19:00:32 02/17/2016: Event: 20, 152, Loading Development application definitions for default localization
19:00:32 02/17/2016: Event: 20, 151, Finished loading Development application definitions
19:00:32 02/17/2016: FlightBooking: Starting threads.
19:00:32 02/17/2016:    1 initial threads.  Threads will auto-scale.
19:00:32 02/17/2016: Loading front end from angelvine
19:00:32 02/17/2016: FlightBooking: loading configuration
19:00:32 02/17/2016: Event: 17, 14, FlightBooking v130.7.0.4
19:00:32 02/17/2016: Event: 20, 4, FlightBooking v130.7.0.4
19:00:32 02/17/2016: Loading agent from ag3.dll
19:00:32 02/17/2016: Starting SAPWM62
19:00:32 02/17/2016: Event: 21, 4, SAPWM62 v130.7.0.4
19:00:32 02/17/2016: Loading agent from ag3.dll
19:00:32 02/17/2016: Starting SAPWM62_NEW
19:00:32 02/17/2016: Event: 22, 4, SAPWM62_NEW v130.7.0.4
19:00:32 02/17/2016: Starting front ends
19:00:32 02/17/2016: Starting front end FlightBooking
19:00:32 02/17/2016: FlightBooking: Opening WebSockets servlet for sub-URL /FlightBooking
19:00:32 02/17/2016: Event: 17, 10, FlightBooking v130.7.0.4
19:00:32 02/17/2016: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-02-17-190019
19:00:32 02/17/2016: Event: 0, 23, Agentry startup is complete.

The ag3javabe.dll  file is in the

C:\SAP\MobilePlatform3\Server\configuration\org.eclipse.osgi\bundles\213\data\

folder now.

Can I disable othe applocations from loading to see only log for FlightBooking?

[Former Member]

You current issue is in the JavaBE.ini in the [SERVICE_LOGON]  section you need to fill out SERVERSERIALNUM field.  You can put in "FlightBooking"

[bill_froelich]

Unfortunately no there isn't a way to disable applications from loading via the Cockpit. 

On my development system I will move the agentry folders for apps I don't want to load to a temporary location.  When the server starts it will re-create a default folder for the app id again but since there isn't the definitions nothing loads.  When I want to use the app again I move the folder back overwriting the re-created files and restart.

--Bill

[Former Member]

This error is gone, but the new has come

13:55:10 02/18/2016: Starting Agentry (64-bit Windows)
13:55:10 02/18/2016: Reading system ini file.
13:55:10 02/18/2016: Starting log file.
13:55:10 02/18/2016: Loading message groups.
13:55:10 02/18/2016: Starting threads.
13:55:10 02/18/2016:    1 initial threads.  Threads will auto-scale.
13:55:10 02/18/2016: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
13:55:11 02/18/2016: Event: 0, 2, Key pair loaded successfully.
13:55:11 02/18/2016: Starting Agentry: Agentry Server Agent v130.7.0.4
13:55:11 02/18/2016: Event: 0, 2, Agentry Startup
13:55:11 02/18/2016: Loading 0 front ends
13:55:11 02/18/2016: Starting Agentry Server Agent
13:55:11 02/18/2016: Agentry Server Agent: Starting threads.
13:55:11 02/18/2016:    1 initial threads.  Threads will auto-scale.
13:55:11 02/18/2016: Agentry Server Agent: Adding messages.
13:55:11 02/18/2016: Event: 1, 4, Agentry Server Agent v130.7.0.4
13:55:11 02/18/2016: Loading agent from ag3.dll
13:55:11 02/18/2016: Starting FlightBooking
13:55:11 02/18/2016: FlightBooking: reading config file
13:55:13 02/18/2016: Event: 20, 150, Loading Development application definitions
13:55:13 02/18/2016: Initializing Java-BackendSAPConnection from ag3javabe.dll
13:55:13 02/18/2016: BackendSAPConnection: Reading configuration information.
13:55:13 02/18/2016: BackendSAPConnection: Setting name to 'Java-1'.
13:55:13 02/18/2016: Java-1: Initialized.
13:55:13 02/18/2016: Java-1: Java Virtual Machine already initialized.
13:55:25 02/18/2016: Exception: 13:55:25 02/18/2016 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Error validation user password), 
13:55:25 02/18/2016: Failed to init Java-1 (Java v130.7.0.4) from ag3javabe.dll
13:55:25 02/18/2016: Event: 20, 152, Loading Development application definitions for default localization
13:55:25 02/18/2016: Event: 20, 151, Finished loading Development application definitions
13:55:25 02/18/2016: FlightBooking: Starting threads.
13:55:25 02/18/2016:    1 initial threads.  Threads will auto-scale.
13:55:25 02/18/2016: Loading front end from angelvine
13:55:25 02/18/2016: FlightBooking: loading configuration
13:55:25 02/18/2016: Event: 17, 14, FlightBooking v130.7.0.4
13:55:25 02/18/2016: Event: 20, 4, FlightBooking v130.7.0.4
13:55:25 02/18/2016: Loading agent from ag3.dll
13:55:25 02/18/2016: Starting SAPWM62
13:55:25 02/18/2016: Event: 21, 4, SAPWM62 v130.7.0.4
13:55:25 02/18/2016: Loading agent from ag3.dll
13:55:25 02/18/2016: Starting SAPWM62_NEW
13:55:25 02/18/2016: Event: 22, 4, SAPWM62_NEW v130.7.0.4
13:55:25 02/18/2016: Starting front ends
13:55:25 02/18/2016: Starting front end FlightBooking
13:55:25 02/18/2016: FlightBooking: Opening WebSockets servlet for sub-URL /FlightBooking
13:55:25 02/18/2016: Event: 17, 10, FlightBooking v130.7.0.4
13:55:25 02/18/2016: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-02-18-135510
13:55:25 02/18/2016: Event: 0, 23, Agentry startup is complete.

JavaBE.ini contains the following data.

[HOST]
server=192.168.0.192
APPNAME=Z00_FLIGHTBOOKING


[CONFIG]
source=SAP


[CLIENT_NUM]
CLIENT=100


[SYSTEM_NUM]
SYSNUM=00


[SERVICE_LOGON] 
ENABLED=true
UID=HERE_IS_MY_SAP_USER_NAME
UPASSWORD=HERE_IS_MY_SAP_USER_PASSWORD
SERVERSERIALNUM=FlightBooking


[LANGUAGE]
LANG=EN


[LOGGING]
Level=4


[LOGON_METHOD]
LOGON_METHOD=USER_AUTH


;LOGON_METHOD=<logon method to SAP system>
;USER _AUTH - Standard User ID and password authentication is used.
;USER_AUTH_GLOBAL - Pooled connections using a single user ID and password; requires the section [GLOBAL_LOGON] to also be created.
;USER_AUTH_GROUP - User ID and password authentication with the SAP Message Server (load balancing) is used; requires the section [GROUP_LOGON] to also be created.


[GLOBAL_LOGON]
UID=
UPASSWORD=
SHAREDCONNECTION=100


[GROUP_LOGON]
MESSAGE_SERVER=
GROUP_NAME=
SYSTEM_ID=
CLIENT=


[REQUIRED_BAPI_WRAPPER]
com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK
com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT
com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET
com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET
com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD
com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD
com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET
com.syclo.sap.bapi.GetEmployeeDataBAPI=/SMERP/HR_DOEMPLOYEE_DATA_GET
com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL
com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET
com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD
com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT
com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL
com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT
com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL
com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.SignatureCaptureBAPI=/SMERP/CORE_DOBDSDOCUMENT_CRT

I checked my logon

UID=HERE_IS_MY_SAP_USER_NAME

UPASSWORD=HERE_IS_MY_SAP_USER_PASSWORD

with SAP Logon client.

It is correct.

[Former Member]

I tried to use next connectTest.bat file

@echo off
rem --- clear the screen
cls
rem ---- copy the classPath from the agentry.ini file or change below as required
;set classPath=./Java;./Java/workmanager-6.2.1.0.jar;./Java/common-20150514.jar;./sapsso.jar;./sapjco3.jar;./ini4j.jar;;
set classPath=./Java/ini4j.jar;./sapjco3.jar;./Java/SAPCommon-133461.jar;./Java/ZFlightBooking.jar;
;set serverClass=com/syclo/sap/sflight/server/Server
rem --- run the simple ConnectTest class
java -cp %classpath% com.syclo.sap.ConnectTest

but it raise an error

INI file: C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application.FlightBooking\JavaBE.ini
*** Caught exception: com/syclo/agentry/Server
release::releasing connection
release::complete.

[bill_froelich]

I would recommend taking your JavaBE.ini from Work Manager and using that with the appropriate changes.  For Connect test there may be missing entries it is looking for and it has been problematic depending on which version / variant of the SAPCommon you are using.

--Bill

[Former Member]

I took JavaBE.ini from Work Manager and changed next paramaters

[HOST]
APPNAME=Z00_FLIGHTBOOKING

[SERVICE_LOGON] 
SERVERSERIALNUM=FlightBooking

Now the text of error changed

startup.log

19:04:34 02/18/2016: Starting Agentry (64-bit Windows)
19:04:41 02/18/2016: Reading system ini file.
19:04:41 02/18/2016: Starting log file.
19:04:41 02/18/2016: Loading message groups.
19:04:41 02/18/2016: Starting threads.
19:04:41 02/18/2016:    1 initial threads.  Threads will auto-scale.
19:04:41 02/18/2016: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
19:04:41 02/18/2016: Event: 0, 2, Key pair loaded successfully.
19:04:41 02/18/2016: Starting Agentry: Agentry Server Agent v130.7.0.4
19:04:41 02/18/2016: Event: 0, 2, Agentry Startup
19:04:41 02/18/2016: Loading 0 front ends
19:04:41 02/18/2016: Starting Agentry Server Agent
19:04:41 02/18/2016: Agentry Server Agent: Starting threads.
19:04:41 02/18/2016:    1 initial threads.  Threads will auto-scale.
19:04:41 02/18/2016: Agentry Server Agent: Adding messages.
19:04:41 02/18/2016: Event: 1, 4, Agentry Server Agent v130.7.0.4
19:04:41 02/18/2016: Loading agent from ag3.dll
19:04:41 02/18/2016: Starting FlightBooking
19:04:41 02/18/2016: FlightBooking: reading config file
19:04:42 02/18/2016: Event: 20, 150, Loading Development application definitions
19:04:43 02/18/2016: Initializing Java-BackendSAPConnection from ag3javabe.dll
19:04:43 02/18/2016: BackendSAPConnection: Reading configuration information.
19:04:43 02/18/2016: BackendSAPConnection: Setting name to 'Java-1'.
19:04:43 02/18/2016: Java-1: Initialized.
19:04:43 02/18/2016: Java-1: Java Virtual Machine already initialized.
19:04:45 02/18/2016: Exception: 19:04:45 02/18/2016 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: 18.02.2016 19:04:45  - Data Object Assignment for BAPI /SYCLO/CORE_MDW_SESSION1_CRT Not Found!), 
19:04:45 02/18/2016: Failed to init Java-1 (Java v130.7.0.4) from ag3javabe.dll
19:04:45 02/18/2016: Event: 20, 152, Loading Development application definitions for default localization
19:04:45 02/18/2016: Event: 20, 151, Finished loading Development application definitions
19:04:45 02/18/2016: FlightBooking: Starting threads.
19:04:45 02/18/2016:    1 initial threads.  Threads will auto-scale.
19:04:45 02/18/2016: Loading front end from angelvine
19:04:45 02/18/2016: FlightBooking: loading configuration
19:04:45 02/18/2016: Event: 17, 14, FlightBooking v130.7.0.4
19:04:45 02/18/2016: Event: 20, 4, FlightBooking v130.7.0.4
19:04:45 02/18/2016: Loading agent from ag3.dll
19:04:45 02/18/2016: Starting SAPWM62
19:04:45 02/18/2016: Event: 21, 4, SAPWM62 v130.7.0.4
19:04:45 02/18/2016: Loading agent from ag3.dll
19:04:45 02/18/2016: Starting SAPWM62_NEW
19:04:45 02/18/2016: Event: 22, 4, SAPWM62_NEW v130.7.0.4
19:04:45 02/18/2016: Starting front ends
19:04:45 02/18/2016: Starting front end FlightBooking
19:04:46 02/18/2016: FlightBooking: Opening WebSockets servlet for sub-URL /FlightBooking
19:04:46 02/18/2016: Event: 17, 10, FlightBooking v130.7.0.4
19:04:46 02/18/2016: Event: 0, 0, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-02-18-190434
19:04:46 02/18/2016: Event: 0, 23, Agentry startup is complete.

[bill_froelich]

I would double check your settings in the config panel as the next step.

--Bill

[Former Member]

According to instructions

I had to assign Z00_FLIGHTBOOKING Mobile Application to the

BAPI Wrapper Name: /SYCLO/CORE_MDW_SESSION_CRT

but in the JavaBE.ini

com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT

some parameter as assign by /SYCLO/CORE_MDW_SESSION without "1"

only two parameter with "1"

com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT

com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL

com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL

Agentry SAP Framework Configuration have both wrappers

as /SYCLO/CORE_MDW_SESSION_CRT

as /SYCLO/CORE_MDW_SESSION1_CRT

What is the correct one?

[bill_froelich]

For my mapping of the session I used /SYCLO/CORE_MDW_SESSION1_CRT  and /SYCLO/CORE_MDW_SESSION1_DEL.

--Bill