Go to primary content
Oracle Agile Engineering Data Management Enterprise Integration Platform Installation and Upgrade Guide
Release e6.2.0.0
E52570-02
  Go To Table Of Contents
Contents

Previous
Previous
 
 

9 Upgrade Tool


Note:

This chapter describes the upgrade of the configuration file eai_ini.xml from one major version to the next one. For changes in minor versions please refer to the respective Release Notes document.

The Upgrade tool allows upgrading previous versions of the configuration file eai_ini.xml to the current EIP version.

The tool can be started with the script upgrade.cmd (Windows) and upgrade.sh (UNIX) in the bin directory.

The following startup options are available (you will get this by adding the --help option to the startup script):

Usage: Enterprise Integration Platform Upgrade [-c <conf-dir> ] [-h] -i <in> -o <out> [-p <props-file> ] [-x <xsl> ]
Options:
   -c | --conf-dir     Specifies the configuration directory
   -h | --help         Shows this help
   -i | --in           Input file (REQUIRED)
   -o | --out          Output file (REQUIRED)
   -p | --props-file   Specifies the properties file
   -x | --xsl          XSL file (default: upgrade.xsl)

This is an example on how the tools might be called on Windows:

bin\upgrade.cmd -i C:\eigner\eip-old\conf\eai_ini.xml -o C:\eigner\eip-new\conf\eai_ini.xml

The Upgrade tool may provide the following output:

[<date>] FORCE (Upgrade) - Input file (2.1.1) : C:\eigner\eip-old\conf\eai_ini.xml
[<date>] FORCE (Upgrade) - Transformation file: C:\eigner\eip-new\conf\upgrade.xsl
[<date>] FORCE (Upgrade) - Output file (2.1.2): C:\eigner\eip-new\conf\eai_ini.xml
[<date>] FORCE (Upgrade) - Transformation done in 0 h 00 min 00 s 297 ms

9.1 EIP 2.1 to 2.2

9.1.1 General Information

Here you can find information about the installation of the Enterprise Integration Platform Version 2.2 (EIP for Agile e6.2.0.0) on top of EIP 2.1.


Note:

Please keep in mind, that additional customizing of the Enterprise Integration Platform (e.g. XSL Mapping) and Agile EDM (e.g. additional Query Forms) will not be upgraded automatically.

9.1.2 Installation

Due to the fact that libraries and configuration files changed between the versions EIP 2.1 and EIP 2.2, we recommend installing EIP 2.2 in a directory separate from EIP 2.1. Additional mapping files and configuration should be incorporated into the EIP 2.2 installation one by one.

9.1.3 Configuration and Customizing

9.1.3.1 Configuration Settings

The structure of the configuration file eai_ini.xml has changed. Therefore, please copy your 2.1 configuration settings carefully one by one to the 2.2 eai_ini.xml file.


Note:

The usage of the Upgrade tool is highly recommended. Some manual work might also be required.

Following portions of the eai_ini.xml file have changed:

The webserver configuration in the controller area is now deactivated by default. If a network connector is used it must be activated and the port needs to be configured properly to not conflict with another process already running on the same port (e.g. a Tomcat installation).

For an Oracle non-RAC databases, it is advised to not use the OCI driver (which is enabled by default) but the JDBC thin driver. This behavior could be altered by the following line in the eip.conf file:

wrapper.java.additional.9=-Deip.oracle.thin=false

When set to "false", the OCI driver is used that is required for RAC, otherwise the JDBC thin driver is used.

9.1.3.2 Password Encryption

The password encryption had been changed to be compliant with the Oracle Security Guidelines. It will now use the same method as Agile EDM uses (e.g. for the encryption of the database password). Therefore, all passwords in the eai_ini.xml file need to be re-generated.


Note:

New passwords are now prefixed with {PLM-AES-128}. And there will be different passwords generated from the same input to make it harder to guess or recognize previously used passwords. It is therefore advised to generate separate encrypted passwords for the same input.

The command line tool "encrypt" does not allow specifying the password to be encrypted on the command line anymore. It is recommended to paste the plain password into the system's clipboard before running the tool. The encrypted password will be stored into the clipboard again. Or you may choose to use the UI tool named "crypt".