ODI技术问询：如何获取Agent名称及运行服务器并监控其状态

Great question—keeping tabs on ODI Agent health is super important, and there are several native ODI/DB-focused approaches you can use instead of shell scripts. Here are the most reliable methods to integrate directly into your monitoring package:

1. Query ODI Repository Database Tables Directly #

ODI stores all Agent metadata right in its repository tables, making this the simplest way to pull the info you need. Run this SQL against your ODI master repository:

SELECT 
  AGENT_NAME, 
  AGENT_HOST, 
  AGENT_PORT,
  AGENT_STATUS -- 0 = stopped, 1 = running
FROM SNP_AGENT;

Drop this into an ODI SQL Tool step in your package, then use the results to trigger alerts (like flagging agents where AGENT_STATUS is 0) or log details to a dedicated monitoring table.

2. Leverage ODI's Java API #

For more flexibility (like custom filtering or logic), use ODI’s built-in Java API in an ODI Procedure. Here’s a simplified snippet to fetch Agent details:

import oracle.odi.core.OdiInstance;
import oracle.odi.domain.topology.OdiAgent;
import oracle.odi.core.service.TopologyService;

// Initialize ODI Instance (use your repo connection config)
OdiInstance odiInstance = OdiInstance.createInstance(new File("odi_instance.xml"));
TopologyService topologyService = odiInstance.getTransactionalEntityManager().getTopologyService();

// Fetch and print Agent details
for (OdiAgent agent : topologyService.getAllAgents()) {
  System.out.println("Agent Name: " + agent.getName());
  System.out.println("Host Server: " + agent.getHost());
  System.out.println("Current Status: " + (agent.isRunning() ? "Running" : "Stopped"));
}

// Clean up resources
odiInstance.close();

Wrap this in an ODI Java Procedure and add it to your monitoring workflow. You can tweak the code to log results to a file or send notifications if an agent goes down.

3. Use ODI's REST API #

If your ODI environment is set up with REST services, call the Agent endpoint for real-time data. Send a GET request to:

/odirest/api/v3/agents

The JSON response will include each Agent's name, host, port, and status. Use ODI’s REST Client Tool to make this call directly in your package, parse the response, and act on any issues you find.

All these methods are native to ODI, so they avoid shell script dependencies and fit smoothly into your existing ODI workflows. Pick the one that aligns best with your monitoring needs!

内容的提问来源于stack exchange，提问作者Giacomo Giovannini