Creating the JavaBE.ini File for SAP Systems

This procedure documents the steps necessary to create the JavaBE.ini configuration file for use by the Agentry Component.

Prerequisites

The following items must be addressed prior to performing this procedure:

The JavaBE.ini file is needed only when using the Agentry SAP Framework Foundation.
This file is needed by the Agentry Component. This component should be installed, per instructions found in the SAP Mobile SDK installation guide.
This file should NOT be manually placed within the SAP Mobile Platform Runtime environment. Rather it should be packaged and deployed per documented procedures for deploying Agentry applications.

Context

The SAPCommon-130881.jar processes the JavaBE.ini configuration file at runtime, and expects certain sections and settings to be present. These revolve primarily around connectivity and authentication to and with the SAP System.

In addition to these required sections, in some implementations developers choose to add additional configuration sections. These additional sections are valid, but are outside the scope of this document. Typically these settings are consumed by the synchronization logic built for a specific application.

Procedure

Create a new plain text file named JavaBE.ini and save it in the installation folder of the Agentry Component.
Using a plain text editor, open the JavaBE.ini file for editing.

Create the [HOST] section with the following settings:

[HOST]

server=<your sap host system’s network name>

APPNAME=<name of your mobile application>

Create the [CONFIG] section exactly as shown below. Note there are other options for the source setting listed in this section, but the default is sufficient for initial configuration. Further information on this is provided in development guides.
```
[CONFIG]
```
```
source=SAP
```

Create the [CLIENT_NUM] section with the following setting:

[CLIENT_NUM]

CLIENT=<client number for Agentry Server to communicate with SAP Application server>

Create the [SYSTEM_NUM] section with the following setting:

[SYSTEM_NUM]

SYSNUM=<system number for Agentry Server to communicate with the SAP Application Server>

Create the [LANGUAGE] section with the LANG option set to the two character SAP language key matching the language of the SAP system:
```
[LANGUAGE]
```
```
LANG=<two chracter SAP language key>
```
Create the [LOGGING] section, with the logging level set based on the information provided after the example:
```
[LOGGING]
```
```
Level=<logging level>
```
- 1 - Fatal Errors only
- 2 - Errors and above
- 3 - Warnings and above
- 4 - Informational messages and above
- 5 - Debugging messages and above
- 6 - Trace level debugging
Create the [LOGON_METHOD] section with the following settings, using the descriptions of settings provided below the example. The option set here will specify whether the [GLOBAL_LOGON] or [GROUP_LOGON] section is needed as well:
```
[LOGON_METHOD]
```
```
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.
If the LOGON_METHOD is set to USER_AUTH_GLOBAL, create a new section named [GLOBAL_LOGON] as shown next:
```
[GLOBAL_LOGON]
```
```
UID=<User ID shared by all users>
```
```
UPASSWORD=<Password shared by all users>
```
```
SHAREDCONNECTIONS=<number of connections created for the shared pool>
```

If the LOGON_METHOD is set to USER_AUTH_GROUP, create a new section named [GROUP_LOGON] as shown next:

[GROUP_LOGON]

MESSAGE_SERVER=<host name or IP of the SAP Message Server>

GROUP_NAME=<name of the SAP Application Server group>

SYSTEM_ID=<name or ID of the SAP system>

CLIENT=<client number to be used by the Agentry Server to connect to the SAP system>

Create the section [REQUIRED_BAPI_WRAPPER] with the settings and values listed exactly as shown next:

[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=/SYCLO/HR_EMPLOYEE_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.TransactionCommitBAPI=WFD_TRANSACTION_COMMIT

com.syclo.sap.bapi.SignatureCaptureBAPI=/SYCLO/CS_DOBDSDOCUMENT_CRT

Save and close the file to the installation location of the Agentry Component.

Results

With the completion of this procedure the JavaBe.ini configuration file for the Agentry Component is created, with settings to connect to the SAP system for which the mobile application will be developed.