Agent URL

 1. Understanding the Agent URL Structure

An Agent URL consists of four main components:

1. Protocol: Specifies the communication protocol used for the connection.
• Possible values: http or https.
2. Host: The machine or server where the agent is running.
3. Port: The network port on which the agent listens for incoming connections.
4. Application Name: The name that identifies the agent running on the specified host and port.
• For standalone agents, this is always oraclediagent (this name cannot be changed).
• For Java EE agents, the application name can vary (e.g., oracledi).

 

2. Example of an Agent URL

• Standalone Agent Example:
• Suppose a standalone agent is started on port 8080 on a machine named odi_production.
• The agent will be reachable at the following URL:

o   http://odi_production:8080/oraclediagent

• Explanation:
• Protocol: http
• Host: odi_production
• Port: 8080
• Application Name: oraclediagent (this is fixed and cannot be changed).
• Java EE Agent Example:
• Suppose a Java EE agent is started as an application named oracledi on port 8000 in a WebLogic Server (WLS) deployed on a host named odi_wls.
• The agent will be reachable at the following URL:

o   http://odi_wls:8000/oracledi

• Explanation:
• Protocol: http
• Host: odi_wls
• Port: 8000
• Application Name: oracledi (this name can be customized).

 

3. Notes on the Agent URL

• Protocol (http or https):
• The protocol determines whether the connection is secure (https) or not (http).
• For secure connections, you would use https in the URL.
• Application Name:
• The application name for a standalone agent is always oraclediagent and cannot be changed.
• For Java EE agents, the application name can be customized, as shown in the example (oracledi).
• Port Number:
• Each agent is started on a specific port. The port number must be specified correctly in the URL to access the agent.
• Host Name:
• The host name is the machine or server where the agent is running. It can be either an IP address or a fully qualified domain name (FQDN).

 

4. How to Use the Agent URL

• Connection to the Agent:
• Use the constructed Agent URL to access or connect to the agent from Oracle Data Integrator or other client applications.
• Accessing the Agent:
• You will use the Agent URL in configuration files or when initiating operations that require the agent's URL, such as running integration tasks.

 

5. Summary of the Components in the Agent URL

Component	Description	Example (Standalone Agent)	Example (Java EE Agent)
Protocol	The communication protocol (http or https).	http	http
Host	The server or machine hosting the agent.	odi_production	odi_wls
Port	The network port where the agent is listening.	8080	8000
Application Name	The name identifying the agent.	oraclediagent	oracledi

 

6. Example URLs

Standalone Agent:

http://odi_production:8080/oraclediagent

Java EE Agent:

http://odi_wls:8000/oracledi