This document guides you through the new installationnull of an SAP agent.
1. |
Installing the Microsoft Visual C++ 2010 Redistributable PackageEin Package ist eine Instanz (eine Version, eine Revision, ein Tag, ...) Ihrer Applikation und definiert den Content, den Sie deployen möchten. Hier entscheiden Sie, ob Sie die gesamte Applikation oder nur einige spezifische Komponenten deployen möchten. (Windows) |
---|
This step is only relevant when installing the SAP Agent"Programm, das die Ausführung von Verarbeitungen auf Zielsystemen wie z.B. Rechner oder Geschäftslösungen ermöglicht. Auch ein eigener Objekttyp in der Automation Engine. [Früher ""Executor"" genannt.] Siehe auch ""Host""." on Windows.
Starting with JCo 3.0.0, JCo running on Windows requires the Visual Studio 2005 C/C++ runtime libraries. See SAP note 684106 for details on how to install them.
You can skip this step when the required version of the package is already installed. Refer to the Control Panel -> Add or Remove Programs to see if the package is available, and if so, which version.
2. | Installing the Java Runtime Environment (JRE) |
---|
If the required version of JRE is already available, you can skip this step.
java -version
If several JRE or Java SDK Versions are installed on the computer, the order of the directories indicated in the settings of %PATH% or $PATH is important. The Java Runtime Environment that is first in the list is used.
3. | Installing the Agent (UNIX) |
---|
4. | Installing the Agent (Windows) |
---|
5. | Installing the SAP Java Connector |
---|
A detailed configuration and installation guide is provided in the archive of the SAP Java Connector (<sapjco-install-path>/docs/jco/intro.html). Read this description carefully in order to ensure that everything works correctly.
To see which Java Connector version is supported, Refer to the requirements of the SAP agent.
Install the 32bit SAP JAVA Connector if you use 32bit Java. 64bit Java requires the 64bit SAP Java Connector.
The SAP note 636912 includes information that can be used to verify that the Java Connector has correctly been installed.
6. | Importing the AE Interface |
---|
This installation step is only required if you intend to use the AE interface.
7. | Creating a CPIC User |
---|
Note that you must create this CPIC user with the same password in each SAP client in which you want to run jobs.
8. | Creating Connections Objects |
---|
SAP | Connection type |
---|---|
ABAP Basis | Remote Function Call |
Java Basis | Internet |
Process Integration | Internet |
System Landscape Directory | Internet |
SAP distinguishes between uppercase and lowercase letters. Keep this in mind when you enter the password.
9. | Setting up the Agent Object |
---|
10. | Start the Agent |
---|
<path to java> -Xrs -Xmx256M -jar ucxjr3x.jar
If java is installed in a folder which contains spaces the command needs to be placed in quotes.
For example:
"C:\Program Files (x86)\Java\jre7\bin\java" -jar -Xrs -Xmx256M ucxjr3x.jar
<path to java> -Xmx256M -jar ucxjr3x.jar
Example:
/usr/bin/java -jar -Xmx256M ucxjr3x.jar
If the SAP Java Connector cannot load its native library the parameter -Djava.library.path can be used to point to a directory which contains the libsapjco3.so.
The agent can also be started by using the ServiceManager.
The storage limit should be set to at least 256MB (or 512MB) for starting Java agents (Databases, RA, JMX, SAP). You can specify a value for the storage limitation of Java applications by using the start parameter -XmX. Specifying a value that is too low can cause the agent to crash. The default value depends on the Java version that is used.
The Java parameter -Xrs ensures that the agent ends properly when a normal end is initiated. Automic recommends using this parameter. More detailed information is provided in the Java documentation.
11. | Function Test |
---|