Moving Oracle Data Integrator to Exadata can provide a big boost in reliability and performance to your data integration processes. There are quite a few different ways that you can configure your ODI environment. Each configuration has its own pros and cons for each environment. You will have to play around with different configurations to find the right one for your environment and that meets your requirements for high availability, performance, security, organizational best practices and so on.
Below is a sample configuration of ODI on Exadata. In this configuration, the WebLogic ODI Agent is used for high availability and load balancing of ODI jobs. Because I want the actual jobs to run on the same server as the database instance I have put the ODI Standalone Agents on the DBMS servers in the Exadata rack. The is one ODI Standalone Agent on each node of the RAC cluster. The WebLogic ODI agent is configured to load balance between each ODI Standalone Agent in the cluster. The WL ODI Agent is also configured to not run any jobs itself. I don't want any data flowing across the network from the Exadata DBMS servers to the WL ODI Agent on the WebLogic server. My goal is to keep everything local to the Exadata rack.
Below is a sample configuration of ODI on Exadata. In this configuration, the WebLogic ODI Agent is used for high availability and load balancing of ODI jobs. Because I want the actual jobs to run on the same server as the database instance I have put the ODI Standalone Agents on the DBMS servers in the Exadata rack. The is one ODI Standalone Agent on each node of the RAC cluster. The WebLogic ODI agent is configured to load balance between each ODI Standalone Agent in the cluster. The WL ODI Agent is also configured to not run any jobs itself. I don't want any data flowing across the network from the Exadata DBMS servers to the WL ODI Agent on the WebLogic server. My goal is to keep everything local to the Exadata rack.
No comments:
Post a Comment