Configuring Java Virtual Machine System Connections

Configure the Agentry Server to connect with a Java application server back end system using Java logic for synchronization.

Prerequisites

Before executing this procedure the following items must be addressed:

Obtain and record the numeric identifier for the Java Virtual Machine system connection definition from the Agentry Editor.
Obtain the following information on the back end system with which the Agentry Server is to connect:
- Host name and port numbers for the system hosting the Java application server.
- Java application server name or identifier.
Coordination with network administrators, as well as those with information regarding the back end system prior to performing configuration tasks is also recommended.
Note the full path of the installation folder for the Agentry Server. In the following instructions the path C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\<AppName> will be used.
Obtain any .jar or .class files containing business objects with which the application being implemented may use. These are normally provided with the back end system with which the Agentry Server is synchronizing. These files must be made accessible to the Agentry Server.
Location of and access to the JDK and JRE (installed previously).
Determine whether or not users will be authenticated using the JVM system connection. In such a situation, users will not be able to synchronize unless they are successfully authenticated. The proper user credentials must be established within the back end system prior to allowing users access to the system. This may be done before or after the following procedure.

Task

This procedure provides a typical implementation example. Certain settings within the [Java-n] section may be modified in relation to implementation-specific behaviors or needs.

This process begins by publishing the application project from the Agentry Editor to the Agentry Server. This will create the section [Java-n] for the Java Virtual Machine system connection. It will also automatically add the proper option to the [System Connections] section.
Start the SAP Control Center. Connect to the system where the SAP Mobile Platform with the running Agentry Server is installed.
In the navigation pane of SAP Control Center, expand the Applications node and select the Agentry application.
In the administration pane, click the Configurations tab.
Select the section Java-n, where n corresponds to the system connection definition in the Agentry application project. Click the Properties button.

This displays a list of the settings for the system connection to a database.
Edit the settings on this screen to allow the Agentry Server to connect to a system via a Java interface.
In this section many of the settings are set as shown in most cases, regardless of the implementation environment. The following lists those settings that are set specific to the environment, along with a description of their values:
- classPath: This setting contains several paths used by the Agentry Server in relation to processing Java logic for the application. The path information here is appended to the system variable CLASSPATH. Any values in either location are accessible to the JVM of the Agentry Server. The values for the classPath setting should represent the following information:
  - The location of the Java Development Kit lib\tools.jar file.
  - The location and file name of any .jar or .class files needed by the application’s Java logic.
  - The same path value as listed in the setting outputDirectory.
  - The full path of the installation folder for the Agentry Server, appended with the text Java, as in C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\<AppName>.
- outputDirectory: This is a path value that controls where the compiled output is stored for execution. These are the .class files resulting from compilation of the Steplet, ComplexTable, and DataTable classes defined within the application. This is normally the installation location of the Agentry Server, as in C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\<AppName>.
- sourceDirectory: This is a path value that specifies where the .java files for the application are to be placed when extracted from the definitions. These files are then compiled at run time by the JVM and the resulting .class files are stored in the outputDirectory location. This is normally the installation location of the Agentry Server, as in C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\<AppName>.
- deleteSource: This option is set to either true or false. When true, the .java files stored in the sourceDirecotry will be deleted after they have been compiled into the .class files stored in the outputDirectory. This is normally only set to true for a development environment, where the Java code is being modified regularly as a part of the development cycle.
- enableAuthentication: Setting this option to true will enable the back end authentication functionality, requiring users to be authenticated via means defined for the JVM system connection in order to perform synchronization. If multiple system connections are in use for an application, at least one must perform the back end authentication.
- Other options within this section include settings for the JVM itself, allowing for optimization of the environment for the specific application. These are normally set by developers, or at their direction. Specifics of these are covered in the sections on JVM system connection optimization.
If multiple JVM system connections are defined for the application, repeat the preceding steps for each such connection type.

Once this procedure is complete the Agentry Server will be configured to connect with a JVM System Connection. The Server will be able to perform synchronization tasks for both upstream and downstream processes through the target Java application server. Depending on configuration, users may also be authenticated through this system connection.

Next

Once this procedure has been completed the following tasks may need to be performed:

A connectivity test can be performed by starting the Agentry Server and then performing a transmit from an installed Agentry Client or the Agentry Test Environment. The Server does not open a connection to a Java application server upon startup, but rather waits until a Client attempts to synchronize.
Additional system connections of other types may need to be configured based on the needs of the application. This should be done before attempting to connect a client.