This document guides you through the new installation of an SAP agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host.
![]() |
1. |
Installing the Microsoft Visual C++ 2010 Redistributable Package (Windows) |
---|
This step is only relevant when installing the SAP Agent on Windows.
Starting with JCo 3.0.0, JCo running on Windows requires the Visual Studio 2005 C/C++ runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start). libraries. See SAP note 684106 for details on how to install them.
You can skip this step when the required version of the packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components. 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 listShows entities in a grid view is used.
![]() |
3. | Installing the Agent (UNIX) |
---|
![]() |
4. | Installing the Agent (Windows) |
---|
![]() |
5. | Installing the SAP Java Connector |
---|
![]() |
6. | Importing the AE Interface |
---|
![]() |
7. | Creating a CPIC User |
---|
![]() |
8. | Creating Connections Objects |
---|
SAP | Connection type |
---|---|
ABAP Basis | Remote Function Call |
Java Basis | Internet |
Process Integration | Internet |
System Landscape Directory | Internet |
![]() |
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.
Note that 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 |
---|
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |