Migration from 8.5.1x to 9.0.x
- iWD 9.0 requires Java 1.8. Support for Java 1.6 and 1.7 is withdrawn in release 9.0.
General Migration Procedure
- Backup all databases.
- Upgrade iWD dependencies to supported versions (see Preparing for Installation).
- Stop all iWD 8.5 components.
- iWD Manager's Tomcat.
- iWD Runtime Node.
- iWD Web.
- Install all components.
- Upgrade GAX plug-in to a new version (at least 9.0.002.07) by uninstalling the previous GAX plug-in and installing the new one (details here).
- Install History Node.
- Data Mart
- Migration of data from iWD Data Mart 8.5 to iWD Data Mart 9.0 is not supported due to schema changes—see History Node Limitations.
- History Node should be installed already.
- Create a new database for Data Mart.
- Complete a fresh installation of Data Mart as a separate application.
- Copy all necessary settings from the iWD Runtime Node 8.5 application.
- Copy all customized ETL scripts to the iWD Runtime Node 9.0 ETL directory (../iWD Runtime Node 9.0/etl). Note: If your Kettle plugins fail to work on an Oracle database, please set the following database parameters:
- JDBC URL: jdbc:evo:oracle:@//<databasename>:1521/<SID>
- JDBC Driver Class: evo.database.oracle.EvoDriver
- For more information about setting database parameters please refer to iWD GAX Plug-in Datamart help.
- Add the History Node application to the connections.
- Add the Configuration Server application to the connections.
- Create a Configuration Server database JDBC DAP with configuration option [iWD]/role = cfgserver and add it to the Runtime Node connections (details here).
- Add a jdbc section with options url and driver-class to all created DAPs listed in the connections (details here).
- Change or set the Data Mart application to a new one for all necessary solutions using GAX / iWD / Datamart / <Solution>.
- Using GAX, change the ETL Scripts Directory to a new one for each solution.
- Check that your Data Mart Business Structure Solution has a timezone set.
- Check that in the Data Mart application the schedules/historical and schedules/intraday are set as valid Quartz cron expressions.
- [Optional] Disable the EventLog as it was replaced by History Node and JMS event logger.
- Stat Server Extensions
- Install the new 9.0 version. No other changes are required.
- iWD Manager
- iWD GAX Plugin must be updated already.
- Make a fresh installation using the information and migration notes in Installing iWD Manager
- Make sure iWD Manager 8.5 is stopped. Disable its autostart.
- Import new the iWD Manager 9.0 application templates (App and Server) as described in Installing iWD Manager.
- Create new application and server configuration objects based on the imported templates.
- Install the iWD Manager 9.0 application itself to a separate folder.
- Create a connection from the iWD Manager application to the History Node application by using GAX.
- Copy the required settings from the old iWD Manager application.
- Check you've created connections from the iWD Manager Application to UCS (if needed) and Interaction Server.
- Add the necessary permissions for the iWD access group (to make users able to login, to read filter list, and so on).
- Make sure that host and port of the primary Configuration Server are presented in the General -> Command Line Arguments of the iWD Manager 9.0 Server.
- Run the separate iWD Manager Configuration Database to Configuration Server migration procedure.
- Open GAX and make sure that the Scripts -> iWD Manager folder is created and permissions to that folder are granted for the EVERYONE group.
- iWD Web
- Install a new iWD Web application as described in this series of topics.
- Start all iWD 9.0 components
iWD Manager Configuration Database to Configuration Server Migration Information
iWD Configuration Database migration is performed manually by a Python script similar to that used in 8.5.0 to 8.5.1 migration. To run the script, you need to provide the iWD Manager Configuration Database connection parameters (URL, login and password), and the GAX URL, username and password. The Python script takes the data from the IWD Configuration Database and sends it into the Configuration Server via the GAX API.
- Install Python 2.7.
- Add environment variables:
- For Linux users some additional libraries may be required. To resolve this please deploy the following RPMs with the version appropriate for your OS version:
- unixODBC-*.rpm (for example, for 64-bit RHEL6: unixODBC-2.2.14-14.el6.x86_64.rpm)
- freetds-*.rpm (for example, for 64-bit RHEL6: freetds-0.91-2.el6.x86_64.rpm)
- Download the required Instant Client packages for your platform. All installations require either the Basic or Basic Light package.
- Unzip the packages into a single directory such as '"instantclient_12_2'".
- Set your environment's library loading path (for example LD_LIBRARY_PATH on Linux, or PATH on Windows) to the directory created in Step 2.
- Start your application.
- Refer to any detailed instructions on the download page of your platform for more information. Note: Python and Oracle client versions must both be either 32- or 64-bit.
- If there are any data with Unicode charaters to be migrated, ensure that the GAX application is configured to support UTF-8 encoding. You can do the following:
- For Windows, add -Dfile.encoding=utf-8 to JavaServerStarter.ini under the [JavaArgs] section.
- For Linux, add export JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=utf-8 to setenv.sh.
- Restart GAX.
- Unzip the migration.zip file. This should be located under the config/ folder in iWD Manager's installation directory.
- Install dependencies.
- From the folder where migration.zip was unpacked, run the following command:
- pip install -–upgrade -r requirements.txt
- Run the migration script for each tenant, include the Environment tenant:
- python main.py -g <gaxurl> -u <gax username> -p <gax password> -t <tenant> -y <db type> -d <db host> -r <db port> -n <db name> -s <db user> -w <db user password> --verbose
- The script parameters are as follows:
- -g, --gaxurl—GAX URL address
- -u, --username—GAX user name
- -p, --password—GAX user password
- -t, --tenant—Tenant Name
- -y, --dbtype—iWD Configuration Database type (either Oracle or MSSQL)
- -d, --dbhost—iWD Configuration Database host
- -r, --dbport—iWD Configuration Database port
- -n, --dbname—iWD Configuration Database name
- -s, --dbuser—iWD Configuration Database user
- -w, --dbpass—iWD Configuration Database password
- --verbose—verbosity level
- Oracle example:
- python main.py -g http://192.168.123.132:8080/gax -u default -p password -t selenium -y oracle -d 192.168.123.123 -r 1521 -n xe -s iwd_user -w iwd_password --verbose
- MSSQL example:
- python main.py -g http://192.168.123.123:8080/gax -u default -p password -t selenium -y mssql -d 192.168.123.123 -r 1433 -n iwd_config -s iwd_user -w iwd_password --verbose
Post-installation—Configuring the Solution
Once you have installed iWD 9.0, for each configured Solution you must:
- Navigate to iWD GAX plugin -> Business Structure -> <Solution name>.
- Complete the Interaction Server JDBC URL and save the changes.
History Node Specific Migration Information
iWD Web Specific Migration Information
In a migration from iWD 8.5.1 to 9.0, you will need to manually move the following three configuration options from the [boot] section to the [security] section: