Installing the Agent for SAP - Basics

Installing the Agent for SAP

Installing the Agent for Siebel (Windows)

---

Installing the Agent for SAP - Details

This document guides you through the new installation of an SAP agent.

	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++ 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.

• Host
• Install the package from the directory IMAGE:CRTS.

	2.	Installing the Java Runtime Environment (JRE)

If the required version of JRE is already available, you can skip this step.

• Admin computer and/or user computer
• Use the following command to check the version of the Java Virtual Machine (VM) that is currently installed:

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.

• Download the required Java Runtime Environment from http://java.sun.com and install it. The installation process includes the automatic installation of the Java Plug-in for Web browsers. You can deactivate it in the system control if you prefer; AE does not need it.

	3.	Installing the Agent (UNIX)

• Host
• Log on using the user AE
• Transfer the TAR file UCXJR3X.tar.gz to a directory (such as SAP) via FTP.
• Switch to the SAP directory:
  cd sap
• Unpack the TAR file:
  gzip -d UCXJR3X.tar.gz
  tar xvfo UCXJR3X.tar
  Through this process, the files are created. The TAR file can be deleted after unpacking.
• Note: Make sure that all files are correctly unpacked and be sure to note of all TAR messages, which can come from various owners.
• Check to make sure that all files have the correct owner and group entries. AE must be the owner. The group entry must correspond to the user AE. Modifications can only be made by a privileged user, such as root.
  chown UC4 * changes the owners of all files to AE.
  chgrpGroup name * changes the user group of all files.
• Rename the supplied INI file UCXJxxx.ori.ini to UCXJR3X.ini.
• Adjust the INI file to your system environment.

	4.	Installing the Agent (Windows)

• Switch to the subdirectory IMAGE:AGENTS\SAP\WINDOWS.
• Start the program SETUP.EXE.
• Adjust the INI file to your system environment.
• Adjust HEADER.SAP, TRAILER.SAP, RESTART.SAP or HEADER.SAPBW, TRAILER.SAPBW and RESTART.SAPBW, as necessary. See: Job - Execution.
• The SAP agent is an AE background program. It is generally started as a service in the Service Manager.

	5.	Installing the SAP Java Connector

• Host
• A detailed configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. 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.
• Download the SAP Java Connector from the SAP Service Marketplace and install it (Support Portal -> Downloads -> SAP Connectors -> SAP Java Connector -> Tools & Services).
• Copy the SAP Java Connector filesto the BIN directory of the agent.
• 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

• Host
•  This installation step is only required if you intend to use the AE interface.
• Copy the transport files.
• Import the transport.
• See also: Transporting the AE Interface.

	7.	Creating a CPIC User

• Host
• Log on to the SAP system using the SAP user administrator.
• Create an authorization profile either directly or with a role.
• Create the CPIC user and assign the authorization profile or role.
•  Note that you must create this CPIC user with the same passwordA secret combination of characters for a Automation Engine user. in each SAP client in which you want to run jobs.

	8.	Creating Connections Objects

• Admin computer or user computer

• The SAP agent requires login data to log on to the various SAP areas.
• Start the UserInterface and log on to system client 0000.
• Create an extra Connection object for the SAP areas to be used with the SAP agent (see table below). At least one Connection object for the SAP basis is required in which you specify the CPIC user. All other Connection objects are optional.
• In the Connection object, select the type and enter your login data.

•  SAP distinguishes between uppercase and lowercase letters. Keep this in mind when you enter the password. 

	9.	Setting up the Agent Object

• Admin computer or user computer
• Switch to the folder HOST.
• Create an Agent object.
• As agent name, use the same name as specified in the SAP agent's INI-file parameter name=.
• Open the Agent object and switch to the agent tab.
• Select the Connection objects you created previously.
• Store and close the Agent object.
•  You can choose to omit this installation step and start the agent immediately (see next step). In this case, an Agent object is automatically created, but it is necessary to end it afterwards. Select the Connection object and restart it.

	10.	Start the Agent

• Server computer
• The AE system must be running.
• Host
• Use the commands to start the agent via the command line for your operating system.
  • Windows:
    

  <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

  • UNIX:

  <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.

• If it does not already exist, an Agent object is automatically created in system client 0000 and stored in the folder HOST.
• Admin computer or Server computer

• Verify that the agent for SAP BW has logged on.
  • Call information about agents in the System Overview. Newly logged-on agents have not yet been assigned to a client, therefore they can only be viewed in client 0000. You can now assign the new agent to clients with the required rights by using the Agent object.

	11.	Function Test

• Admin computer/host
• Start a test job.
  The SAP computer is the host. Enter the appropriate UserID. Activate the job report deposit in AE.
  The script contains the following script lines:
  R3_ACTIVATE_REPORT REP=RSM04000_ALV,COVERPAGE=YES
  The current ABAP creates a list of actual users.
• Monitor the process in the UserInterface.
   It can take a couple of seconds for the system to register that the job is done. The agent checks at a regular interval whether the job is still running. This interval can be specified in the host characteristics.
• Check the job report.
• Check the agent logins in the log file.
• SAP System
• Check the log entries from the current period with the transaction RZ15 (only when using the standard interface).
• Shut down the agent.