Java EE Agent Configuration Standalone Agent Configuration

High Availability for Oracle Data Integrator 7-5 sessions requests to start their processing, and is also able to start sessions based on its schedules.

7.2.3 Oracle Data Integrator External Dependencies

Oracle Data Integrator depends on the Oracle Data Integrator master repository and work repository database schemas. If advanced features are being used, these other dependencies may exist: ■ Other Oracle Data Integrator agents: If the load balancing feature is configured and the agent needs to delegate the execution of sessions to its child agents. ■ If External Password Storage is enabled for this agents master repository, the agent depends on the credential store for retrieving the source and target data servers passwords to connect these data servers during session execution. ■ If External Authentication is enabled for this agents master repository, the run-time agents as well as Oracle Data Integrator Console depend on the Identity Store service that stores the Oracle Data Integrator user accounts. These components must be available for the Oracle Data Integrator system to start and run properly.

7.2.4 Oracle Data Integrator Startup and Shutdown Process

The Oracle Data Integrator Java EE agent application is started by default whenever any Oracle WebLogic Managed Server to which it has been deployed is started. Normally, you should not need to stop Oracle Data Integrator or any of its components by themselves. Some operations may require the Oracle WebLogic Managed Server where Oracle Data Integrator runs to be rebooted. Only some patching scenarios should require stopping the application. You can use Oracle WebLogic Server Administration Console to verify the status and to start and stop Oracle WebLogic Server. You can also use the WebLogic Server WLST command line to control the application. Oracle Enterprise Manager Fusion Middleware Control also allows multiple operations and configuration of Oracle Data Integrator as well as monitoring its status.

7.2.5 Oracle Data Integrator Configuration Artifacts

This section describes Oracle Data Integrator configuration artifacts.

7.2.5.1 Java EE Agent Configuration

The configuration parameters for the Java EE agent are stored in both the agent application and in the master repository to which the agent is attached. As shown in Figure 7–3 , the agent configuration stored in the master repository can be edited from the Oracle Data Integrator Studio and includes the following key parameters: ■ Host ■ Port ■ Web Application Context 7-6 Oracle Fusion Middleware High Availability Guide Figure 7–3 Agent Configuration in the Master Repository Displayed in Oracle Data Integrator Studio Using this information and valid credentials, any component connecting the repository is able to request an execution from this agent on the host:portweb_ application_context URL. Several agents can be started on the same host and port pair by specifying a different Web application context value. In addition to this information, the Master Repository also contains: ■ The names of the data sources used by this agent to connect the source, target and repository database hosts. ■ The hierarchy of agents for the load balancing feature. Oracle Data Integrator Studio provides a feature to generate an Oracle WebLogic template for a given agent. This template contains the agent binaries, configuration and data source definitions. Oracle WebLogic administrators can use these templates to deploy pre-configured agents over a cluster. Other configuration options at the container level, such as creation or modification of data sources are available as WebLogic Server domain configuration, and are synchronized across a cluster of Oracle WebLogic Servers by the Oracle WebLogic Server core infrastructure. See the chapter on setting up the topology in Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for more information on the Java EE agent deployment options.

7.2.5.2 Standalone Agent Configuration

The configuration parameters for the standalone agent are stored both in the standalone agent configuration file as well as in the master repository to which this agent is attached. The repository part of the agent configuration is similar to the Java EE agent. The agent configuration differs as it is stored in a configuration file, stored in its installation folder: ■ For UNIX: ODI_HOMEoraclediagentbinodiparams.sh ■ For Windows: ODI_HOMEoraclediagentbinodiparams.bat This configuration file includes the following parameters that must be edited manually as part of the standalone agent configuration: ■ JDBC connection information to connect the master repository High Availability for Oracle Data Integrator 7-7 ■ ODI Supervisor user and encrypted password The agent started in standalone mode is also configured with the command line used to start it. This command line can include the following parameters: ■ Listening Port ■ Agent Name ■ Trace Level A component willing to send an execution request to this agent will send it on the following URL: host:portoraclediagent. Note that the standalone deployed application name is set to oraclediagent. As a consequence, to start several standalone agents on a single host, different ports must be used. See the chapter on setting up the topology in Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for more information on the agent configuration details.

7.2.5.3 Oracle Data Integrator Console Configuration