You install the Adapter Engine , including available adapters, so that you can then configure and use them to convert the respective message formats. You can install adapters individually or together as required, but always separately for inbound processing (sender adapter) and outbound processing (receiver adapter) by the Integration Engine.
To install adapters, you require the following:
http://java.sun.com/products/servlet/index.html
http://java.sun.com/products/jms/index.html
A JDBC driver installation (version 2.0) for the database product to be connected to. The required Java libraries are product-specific and can be obtained from either the database vendor or other providers. The Java libraries must be located in the Java CLASSPATH following installation so that the JDBC adapter can access the required Java classes at runtime.
service.sap.com
You must include both libraries in the Java CLASSPATH after installation.
https://http://
In UNIX operating systems, a bash shell must be installed to enable the run_adapter.sh script to be used. Otherwise, the run_adapter.cmd script can be used to start the Adapter Engine (Java SE).
The Java runtime (java.exe) is located in the search path, if installation was performed correctly.
The packed adapter-installation file has been unpacked in a directory of your choice and you have retained the path structure.
New Installation
Within the directory you used to unpack the installation file you will find the subdirectory tech_adapter with further subdirectories such as Administration, Configuration, and LogFiles. All configuration data for the Adapter Engine is stored in the tech_adapter directory or in sub directories of tech_adapter.
To install an adapter, switch to the directory tech_adapter.
These scripts generate the default configuration in the adapter menu for the respective adapter type. If you do not call any of the scripts then the default configurations for all adapters are found in the adapter menu. However, you can modify the configuration of the adapter menu in each case by using the functions available there.
After the Adapter Engine is installed, the x-bits for scripts such as install_fileadapter.cmd, run_adapter.sh, and run_adapter.cmd are not set. Change these using the following commands:
chmod 755 *.cmd
chmod 755 *.sh
http://<hostname>:8200SAPinit
If the standard port 8200 of the Adapter Engine is already in use, you must enter a free port under port= in the file GuiBrowserEngine.properties.
If this port is also already being used, the Adapter Engine displays the following error message in the window in which it was started and then it closes itself.
ERROR starting Adapter engine base service ´GUI´
Installation is now complete. On the Adapter Engine configuration screen you find two adapters (sender and receiver) for each of the installed adapter types (or one SOAP adapter) that you can configure there.
You define the difference between sender and receiver for the SOAP adapter during configuration. This means that following installation, there is only one SOAP adapter for which you must then configure two different instances, if necessary.
To run multiple adapters of the same adapter type or different adapter types simultaneously, or to start adapters automatically, go to the configuration screen of the Adapter Engine.
Upgrading the Installation
If you want to install a more recent adapter version, or want to repeat the installation, you have two options:
In this case, delete the existing installation beneath the installation directory completely and install the adapter as described above; the Adapter Engine does not contain any other data apart from this directory structure.
Use a tool that can work with ZIP files for this.
Microsoft Windows:save_configuration.bat
UNIX: save_configuration.cmd
Besides the directory tech_adapter, the system creates a new directory adapter_configuration.backup that contains all relevant files for adapter configuration and user management.
If you have also changed the configuration of services and if these configurations also need to be saved, execute the following file as well:
Microsoft Windows:save_baseconfiguration.bat
UNIX: save_baseconfiguration.cmd
If the backup of a component or configuration is not available because it has never been used or configured, you get a notification that the corresponding file or configuration is missing. The system proceeds with the back up of the pending configuration.
Microsoft Windows:restore_configuration.bat
UNIX: restore_configuration.cmd
This file reproduces the adapter configurations, including user management. The service configurations are also reproduced if you have also saved them. Otherwise the services are available in their original configuration, as is the case following a new installation.
Upgrading the Installation of an XI 2.0 Adapter Engine
If you want to apply the XI 2.0 adapter configuration to an XI 3.0 Adapter Engine, note that the XI 3.0 Adapter Engine recognizes configurations of the XI 2.0 Adapter Engine and handles them as follows:
XMB.SenderBusinessSystemXMB.ReceiverBusinessSystemXI.SenderServiceXI.ReceiverService
XI.InterfaceNamespaceXI.Interface
XMB.SenderAdapterForBusinessSystemXMB.ReceiverAdapterForBusinessSystemXI.SenderAdapterForServiceXI.ReceiverAdapterForService
XMB.ContentTypeXMB.ContentKindfile.typeXMB.ContentKindfile type
Continuous Operation
The following operating system-specific installation options are available to enable continuous operation of the Adapter Engine:
The program SAPAdapterService.exe, located in the directory tech_adapter in the Adapter Engine installation directory, is used to start the Adapter Engine as an NTService. To install or de-install the NTService, use the script install_service.bat or uninstall_service.bat. The call conventions are as follows:
The [ServiceName] is a logical name that the service is created under, and [JavaVM] is the name of the DLL of the Java Virtual Machine with a complete path specification. Corresponding examples can be found in the script.
All jar files (for example the JDBC or JMS driver) that may additionally be required by the adapters must be located in the Java classpath when install_service.bat is called. Subsequent changes to the classpath have no effect on the created NTService.
Once installation is complete, you must start the Adapter Engine as an NTService in the Windows services menu or configure it the same as each NTService (startup type, logon information, and so on).
The Windows results display displays information and error messages of the service under the corresponding service names in the application log. Adapter Engine console and error output is placed in the files stdout.log or stderr.logrespectively in the subdirectory LogFiles.
The script run_adapter.sh is located in directory tech_adapter for Unix operating systems. You must adjust the variable ADAPTER_HOME to the installation path in this script. In the variable EXTLIBS you can specify all Jar files that are additionally required by the Adapter Engine, for example to be able to load a JDBC or a JMS driver. For more information, refer to the USAGE section of the script. You can then insert the script in the boot procedure of the operating system.
Accessing the SAP System Landscape Directory
You can access the SAP System Landscape Directory (SLD) from the Adapter Engine. When the Adapter Engine starts, it can log on to the SLD, whereby the Runtime Workbench recognizes it as an SAP Exchange Infrastructure component, thus making it globally accessible.
Optionally, associations can also be created between individual receiver adapters and business systems if a business system is specified in the configuration of a receiver adapter. The addresses of the associated adapters are then automatically adopted as default values by the Integration Directory when end points are created for the business system.
Moreover, this enables information connected with business systems to be exported. For more information about configuring this service, see the section SLDaccessor in Services .
Note that this service is not mandatory and the Adapter Engine can function without being connected to the SLD.
Monitoring with the Runtime Workbench
XIPASS
If this user is deleted (for example, when an older configuration is implemented following installation), or if the Runtime Workbench requires another user, you must create this user manually. The user to be created only requires the authorization group Locked. For more information about creating users, see User Management .