How To Automate the Start of The ODI 12c Standalone/Colocated Standalone Agent(s) on MS Windows Connecting to The Running NodeManager Windows Service (Doc ID 1997769.1)

Last updated on MARCH 18, 2024

Applies to:

Goal

 ODI 12.1.3 introduces the following types of standalone agents:

• A completely standalone agent (no WebLogic server is installed), it is created as a CAM component to the standalone domain with ODI 12c standalone installation
• A standalone colocated agent (WebLogic server is installed),  it is created as a CAM component to the WebLogic domain with ODI 12c enterprise installation

After successfully created, the above 2 types of ODI 12.1.3 standalone agents also can be started with agent.cmd from their <domain home>\bin dir on Windows commandline. This is similar to the ODI 11g standalone agents. However starting agents this way, the agent processes will run on their own without a watchdog/manager.

Questions arise from ODI 11g users that what the equivalent of OPMN in ODI 11g will be in ODI 12.1.3 for the standalone agents, answer to this is the WebLogic NodeManager. The NodeManager will be configured during the  domain creation for the standalone/colocated standalone agents.

Just like OPMN,  NodeManager also manages the ODI agent component process/JVM once it is started successfully, and restarts the agent component process if it crashed unexpectedly or gets killed.

Neither OPMN nor NodeManager will restart the agent component process if they were shutdown gracefully with the following commands:

• In OPMN, the command to stop/shutdown the component process gracefully is:  opmnctl stopproc ias-component=<agent component name>
• In NodeManager case, the command to stop/shutdown the running agent component process gracefully is:  stopComponent.cmd <component name>

The difference between OPMN and NodeManager is that OPMN starts its components (ODI standalone agent can be one of them) when the OPMN process/service starts automatically while Node Manager does not start standalone agent components automatically.

The reason is that NodeManager has no knowledge of topologies or configurations unless told by incoming connection. 

It only has knowledge of the set of domains that it will manage.  It simply receives commands to perform operations and executes them delivering the response.   The goal has always been to keep the NodeManager as simple as possible while delivering the basic watchdog capabilities.

In this ODI 12c architecture, NodeManager must be started and running first, then a standalone agent component needs to be started by connecting to the running NodeManager using WebLogic wlst utility/client (this is achieved by startComponent.cmd script comes with ODI 12c).

Note that this is a one time operation and once the standalone agent component is started successfully, the NodeManager will start watching/managing the standalone agent component process.

NodeManager can be set up as Windows service by using the installNodeMgrSvc.cmd  script comes with ODI 12c.

The purpose of this document is to show users how to  automate the start of the ODI 12c Standalone/Colocated Standalone Agent(s) on MS Windows connecting to the running NodeManager windows service by using Windows native utilities (as opposed to third party programs or utilities).

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.