Oracle Data Integrator Console Configuration Oracle Data Integrator Log Locations and Configuration

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

Oracle Data Integrator Console configuration consists of connection definitions to the master and work repositories that can be browsed using this web application. The list of connections is stored in the repositories.xml file in the following directory: user_projectsdomainsdomainNameconfigoracledi Connections can be added, edited, or deleted from the Oracle Data Integrator Console management pages.

7.2.5.4 Oracle Data Integrator Log Locations and Configuration

This section provides information about Oracle Data Integrator log locations and configuration.

7.2.5.4.1 Oracle Data Integrator Session Logs Oracle Data Integrator session execution

logs are stored in the work repositories against which the sessions are started. This session shows Oracle Data Integrator session details, such as the executed code and the number of processed rows. This log can be displayed from the Oracle Data Integrator Studios Operator Navigator, in the Session List accordion, or from Oracle Data Integrator Consoles Browse tab, under Run-Time Sessions.

7.2.5.4.2 Java EE Agent Log Files The operations performed by the Oracle Data

Integrator Java EE agent are logged by Oracle WebLogic Managed Server where the agent application is running. You can find these logs at the following location: DOMAIN_HOME serversWLS_ServerNamelogsoraclediodiagent.log The log files for the different Oracle WebLogic Server Managed Servers are also available from Oracle WebLogic Server Administration Console. To verify the logs, Note: Oracle Data Integrator Console is used as the entry point for Enterprise Manager to discover Oracle Data Integrator targets in a domain. The discovery process works in the following way: Enterprise Manager identifies Oracle Data Integrator Console. Using the Oracle Data Integrator Console configuration, Enterprise Manager identifies the master and work repositories as well as the run-time agents in the domain. 7-8 Oracle Fusion Middleware High Availability Guide access Oracle WebLogic Server Administration Console using the following URL: admin_server_host:portconsole. Click Diagnostics-Log Files. It is also important to verify the output of the Oracle WebLogic Managed Server where Oracle Data Integrator is running. This information is stored at the following location: DOMAIN_HOME serversWLS_ServerNamelogsWLS_ServerName.out Additionally, a diagnostic log is produced in the log directory for the managed server. This logs granularity and logging properties can be changed through the following file: DOMAIN_HOME configfmwconfigloggingoraclediagent-logging.xml

7.2.5.4.3 Standalone Agent Log Files The operations performed by the Oracle Data

Integrator standalone agent are logged by the lightweight container running the standalone agent. By default, logs are traced on the console and in the ODI_ HOMEoracledilog folder. The logging method and the logging level can be configured by editing the ODI_ HOMEoraclediagentbinODI-logging-config.xml file.

7.2.5.4.4 Oracle Data Integrator Console Log Files Oracle Data Integrator Console logging

operations are logged by Oracle WebLogic Managed Server where the agent application is running, like the Java EE agent log files described in Section 7.2.5.4.2, Java EE Agent Log Files.

7.3 Oracle Data Integrator High Availability and Failover Considerations

This section describes Oracle Data Integrator high availability and failover considerations.

7.3.1 Oracle Data Integrator Clustered Deployment

Figure 7–4 shows a two-node Oracle Data Integrator cluster running on two Oracle WebLogic servers. Oracle WebLogic Servers are front ended by Oracle HTTP Servers, which load balance incoming requests to them.