Oracle Data Integrator Clustered Deployment

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. High Availability for Oracle Data Integrator 7-9 Figure 7–4 Oracle Data Integrator High Availability Architecture The main characteristics of this configuration are: ■ Oracle Data Integrator applications run on two clustered WebLogic Server managed servers. The WebLogic Server cluster synchronizes configuration for common artifacts of WebLogic Server used by Oracle Data Integrator, such as data sources. ■ To avoid duplicate schedule processing, only one of these agents behaves like a scheduler. A Coherence cache is used to handle scheduler service uniqueness and migration. The agent provides failover scheduling capabilities. For example, if a schedule is supposed to start at 9 AM, and the cycle is to run job X every hour for four hours, and the agent fails at 9:55 AM, it should compute where it was in the cycle and continue. However, if a single job is scheduled to start at 9 AM, and the agent fails at 8:59 AM, and then recovers at 9:01 AM, then it will not run the job that was scheduled at 9 AM. ■ Requests to the Oracle Data Integrator agent in a cluster must be routed via a load balancer or via an HTTP proxy server. The address of this fronting server is used by clients to connect transparently to any of the Oracle Data Integrator servers in Internet Load Balancer APPHOST1 APPHOST2 WLS Cluster: Coherence Cluster Firewall 1 Firewall 2 Java EE Agent Java EE Agent Oracle Data Integrator Console Oracle Data Integrator Console WEBHOST2 OHS WEBHOST1 OHS RAC 7-10 Oracle Fusion Middleware High Availability Guide the cluster. This address must be specified in the agent definition in the master repository. The scheduler singleton also routes all scheduled sessions startup requests to this address so that they are load balanced over the cluster. ■ Oracle Data Integrators master and work repositories database is configured with Oracle Real Application Clusters Oracle RAC to protect from database failures. Oracle Data Integrator components perform the appropriate reconnection and operations retries if database instance failure occurs.

7.3.2 Standalone Agent High Availability with OPMN