Installing the Agent for Java EE/JMX (SAP NetWeaver)

The following guide describes how to install an agent in an AE system in which authentication is not used. Additional installation steps are required before the agent can be started and used, if you intend to use one of the available authentication methods. For more information, see Agent Authentication.

The agent creates an additional log file in SAP format. This file is automatically stored in the agent's sub-folder "log" in the installation directory. It can easily be processed with SAP Tools.

As of this version, the Automation Engine and the Windows, UNIX, and Java Agents communicate using TLS. These agents establish a connection with the Java communication process (JCP), which uses trusted certificates to prove their identity to other communication partners.

You can use the trustedCertFolder=, agentSecurityFolder=, and keyPassword= parameters in the respective INI file to point to the relevant certificates. If the trustedCertFolder= parameter is not set, the certificates should be installed in the respective store; that is the Java trust store for Java Agents, the Windows OS store for Windows Agents, or the SSL store for UNIX Agents. UNIX agents additionally require you to define the SSLCertDir= and SSLCertFile= parameters to load the certificates from the SSL store.

For more information, see TLS Configuration.

Important!

  • If you use SAP Netweaver 7.50 SPS0 or SPS1, SAP note 2069317 must be implemented. Otherwise, the Agent produces the error java.security.InvalidKeyException: PublicKey algorithm not implemented: ECPublicKey.
  • If the version of the cryptography provider (IAIK) is 5.2 or lower, you must store trusted certificates in the cacerts file of the JVM. For more information, see SAP note 1877723. In SAP systems in which executables are replicated with sapcpe, make sure to do the changes in the central SAP JVM directory and not only in the instance-specific directories. Otherwise, your changes are overwritten any time the SAP system is restarted.
  • If the version of the cryptography provider (IAIK) is higher than 5.2, the trusted certificate path can be configured in the configuration file of the agent. For more information, see Agent JMX

Installing the Agent for Java EE/JMX (SAP NetWeaver)

  1. Create a role for the JMX agent in the SAP Identity Management.

    • In the General Information tab of the Details section, assign the unique name administrators (as defined in the supplied web.xml file) and a description.
    • Click Save.

    • In the Assigned Actions tab, type in "jmx" in the Get: section and click Go.

    • Select the line that shows the Name "JmxManageAll" and click Add and Save. The result is shown in the screenshot below:

  2. Set up the JMX agent

    • Copy the file ucxjjmc.sca to the computer where SAP NetWeaver is installed

  3. Deploy the JMX agent

    • Open a telnet to localhost port 50008 if your generated instance is 00, or localhost port 50108 if your instance is 01, and log in as administrator (type: Isc, jump 0)
      For more information about telnet ports, see the
    • Deploy c:\Automic_JMX\ucxjjmx.sca

  4. Undeploy the JMX agent

    • Open a telnet to localhost port 50008 or localhost port 50108, and log in as administrator (type undeploy name=JMXAgent vendor=automic.com)

  5. Configure the JMX agent.

    • Open the browser http://<sap-host>:50000/uc4jmx (instance 00), or http://<sap-host>:50100/uc4jmx (instance 01), and fill in the relevant configuration data.

    • Adjust the JMX agent settings to your system environment. The most important settings are:

      • Name of the agent

      • Name of the computer on which the Java communication process is available

      • Port number of the Java communication process

  6. Important notes the creating jobs:

    • Select JNDI in the JMX tab of the Job object. Enter "jmx" as the object name.