2 Oracle Data Integrator 11g for 10g Users

2.2.1 Upgrade Considerations

Before you begin the upgrade process, consider the following:

• Upgrading to ODI 11gR1 is performed using the Upgrade Assistant. It is not possible to upgrade repositories from the Oracle Data Integrator user interface.

• The database that contains the Oracle Data Integrator repositories must be supported by Oracle Fusion Middleware 11g. For the latest list of supported databases, see:

  http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

• For instructions on verifying that your database meets the requirements of Oracle Fusion Middleware 11g, see "Upgrading and Preparing Your Databases" in the Oracle Fusion Middleware Upgrade Planning Guide. Oracle recommends that you refer to your database-specific upgrade documentation for additional information.

• During the upgrade process Work Repositories must reside on the same database server as their Master Repository. The repositories can be manually redistributed after the upgrade.

  For more information on cloning repositories, see Task 4: Copy (Clone) Existing 10g Master and Work Repositories.

2.2.2 Changes in the Run-Time Agent

The run-time agent is available as a standalone agent or a Java EE agent. Both of these agents are now connected to a single Work Repository and act as schedulers. The agents connect systematically to the Master Repository at startup.

For these agents to start properly:

• For the standalone agent the connection configuration (using the odiparams file) must be performed. Running the agent.bat starts a scheduler agent.

• For the Java EE agent, the connection configuration is made in the agent template, and the agent connects to the repositories using JDBC data sources defined in the application server.

The agent now uses the HTTP protocol rather than its own protocol. In addition, the standalone agent is no longer started as a service using the Wrapper tool. To configure the agent for high availability, Oracle Process Manager and Notification Server (OPMN) is used and can be configured using some built-in scripts.

2.2.3 Other Changes

Oracle Data Integrator 10g users should also be aware of the following changes in Oracle Data Integrator 11g:

• Knowledge modules and technologies are available in a directory called /xml-reference.

• The demonstration environment is delivered separately from the ODI Installer on the ODI Companion CD.

• Host and Modules are removed from the Security. This entire feature is deprecated.

• The following scripts are deprecated: Jython, agentscheduler, agentweb, designer, topology, security, and operator.

• Repository creation for Oracle, DB2 and Microsoft SQL Server can be performed using Repository Creation Utility (RCU). This tool allows creation and management of schemas for multiple Oracle products.

• Repository creation and import is possible from the ODI Studio. The mimport and mupgrade scripts are deprecated.

• ODI is now shipped with DataDirect JDBC drivers to connect to technologies such as MSSQL and DB2. Note that the other ODI drivers can still be used to connect to the database. The additional drivers for the Standalone Agent are in the /drivers directory, but the drivers for the ODI Studio are in the /user_home directory.

  For more information, see "Add Additional Drivers and Open Tools" in Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.