User Guide > Objects > Alphabetical Listing > JMX

JMX

The document shown below explains the platform-specific settings for a JMX jobAn Automation Engine object type for a process that runs on a target system..

Description

Field/Control

Description

Job reportA report provides more detailed information about a task's execution or a component.

 

Database

The job report is managed in AE. When the job has been processed, the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. takes the process protocol which has been stored on the 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 computer and stores it to the AE databaseA database is an organized collection of data including relevant data structures..

File

The job report is managed in AE. After the execution of a job, the process protocol is available in the target system as a file.

On error only

The job report is stored in the AE database and/or a file in the target system only if the job has been canceled. This functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… is only available when "Database" and/or "File" have been selected.

Optional reports  
Agent log Activating this checkbox has the effect that a report including the agent's messages about the job execution is added to the taskAn executable object that is running. Tasks are also referred to as activities..

MBean Server

 

Local Java VM

The MBean Server is on the same computer as the JMX agent.

Use any existing MBean Server

The MBean Server is automatically retrieved.

Create new instance if not found

Setting for instance creation

Specify MBean Server

A given MBean Server is used.

Agent ID

An agent ID can be indicated if a particular agent should be used.

JNDI

The connection is established to a local MBean Server which is located in a SAP J2EE Server.

Name of the objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task

The name of the object that should be called.

Remote Java VM

The MBean Server can explicitly be indicated.

Initial Context Factory (optional)

It depends on the vendor of the MBean Server whether this connection parameter should be indicated.

Server URL

URL to the computer on which the MBean Server is found

Important Notes for Creating Jobs

Oracle WebLogic:

t3://name of the Weblogic server:port of the Weblogic server

IBM WebSphere:

Using the RMI connector:

Host name of the WebSphere:port of BOOTSTRAP_ADDRESS

Using the SOAP connector (Websphere with activated administrative security):

Host name of the WebSphere:SOAP port

The Soap Connector must be activated. Its port is in most cases 8880.

JBoss:

Oracle Containers for J2EE:

service:jmx:rmi://Host name of the Oracle J2EE server:port/oc4j

SAP Netweaver:

The JMX agent runs outside of an applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. server:

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH