Best Practices and Recommendations for Setting Up ODI 12c Standalone Agents (Doc ID 1679083.1)

NOTE: In this article, values (like agent name, webcontext, port#'s, service names, schema owners, nodemanger user etc.) used in images, instructions, and examples, are either default values or represent a fictitious sample for clarity.  These and any value placeholders including <> which surround the placeholders should all be replaced by the actual values used in your environment. Any similarity to actual environments, past or present, or users, living or dead, is purely coincidental and not intended in any manner.

Note Oracle Data Integrator (ODI) 12c offers three different types of Agents:

1. Java EE (J2EE) Agents
   
   A J2EE Agent is a JEE application that is deployed and runs on a Managed Server configured in a WebLogic domain.
       
2. Standalone collocated Agents
   
   A standalone collocated Agent is a Standalone Agent that is configured in a WebLogic domain and is managed by an Administration Server.
   
   The WebLogic domain makes Oracle Fusion Middleware Infrastructure services available for managing the Agent.
          
3. Standalone Agents
   
   A Standalone Agent runs as its own process and is managed by the WebLogic Management Framework.
   
   Typically, you would install a Standalone Agent so that it runs in any environment where the Agent process should be lightweight and local WebLogic Server operations are not supported.
   
   The location where to install Java EE Agent and standalone collocated Agent are defined by where you installed WebLogic Server.

This document exclusively refers to the Standalone Agent.