Skip Headers
Oracle® Fusion Middleware Upgrade Guide for Oracle Data Integrator
11g Release 1 (11.1.1)

Part Number E12642-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Oracle Data Integrator 11g for 10g Users

The following sections introduce some key concepts of the Oracle Data Integrator environment for 10g Release 3 (10.1.3.x) users:

2.1 Components of the Oracle Data Integrator Installation

Oracle Data Integrator 10g Release 3 (10.1.3) provided the following components:

Oracle Data Integrator 11g provides updates to all of these components, but not in a single installation. In Oracle Data Integrator 11g, Oracle Data Profiling and Oracle Data Quality components are packaged and installed separately, but they still provide the same resources and services.

Specifically, Oracle Data Integrator 11g provides the following installation options:

2.2 Important Changes for Oracle Data Integrator 10g Users

Although the overall product architecture has not changed, 10g users should be aware the following changes to plan for their updates.

2.2.1 Upgrade Considerations

Before you begin the upgrade process, consider the following:

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:

  • With ODI version 11.1.1.5.0, the names of the ODI binding variables must be uppercase. If you are using lower or mixed case variables, you can use double quotes as a workaround (SELECT 'odi 11' AS "txt" FROM dual ). Note, however, that you may have to redevelop your code as a result of this change.

  • The getObjectName method now automatically truncates object names to the maximum object length allowed for the technology. Prior to ODI 11g, object names were not truncated. To prevent object names from truncating and to reproduce the 10g behavior you must add the server a property OBJECT_NAME_LENGTH_CHECK_OLD and set its value to "true". This property can be added in the Properties tab of the data server.

    NOTE: If your object names continue to truncate after upgrading to 11g, consider changing the code and only use the method above as a temporary workaround.

  • The ODI login files snps_login_security.xml and snps_login_work.xml are now merged into a single file called snps_login_work.xml. The snps_login_work.xml file is located in the %APPDATA%/odi/oracledi directory for Windows operating systems and USER_HOME/.odi/oracledi on Unix operating systems.

  • With ODI version 11.1.1.5.0, ODI ships with a bundled HSQL database version 2.0. Previous versions of ODI shipped with a HSQL database version 1.7.3. The HSQL database is used for the memory engine, the demonstration environment, and the memory storage for the XML and LDAP drivers. You may have your own HSQL 1.7.3 database instances connected from ODI. If so, once you upgrade the HSQL database to version 2.0, ODI can no longer connect to HSQL database version 1.7.3 databases. You must upgrade your HSQL database version 1.7.3 to version 2.0 before upgrading to ODI 11.1.1.5.0.

    For more information on upgrading databases, see the HSQL database documentation at http://www.hsqldb.org/doc/2.0/guide/deployment-chapt.html#deployment_upgrade-sect

    See also the HSQL database Changelog at http://www.hsqldb.org/web/changelog.html

  • 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 DOMAIN_HOME.

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

Note:

For a detailed list of the new features in Oracle Data Integrator 11gR1, see "What's New In Oracle Data Integrator?", in Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.