Chapter 4   Migration

This chapter discusses how you can migrate your system from

iTTM 2.2.1 and iTPS 1.0

to

iTTM 3.0.1 and iTPS 2.0

Upgrade Procedure

---

To upgrade from an existing iTPS 1.0/iTTM 2.2.1 installation, the following procedure should be followed:

1. Follow the instructions in the iTTM 2.2.1 Installation and Configuration Guide on how to stop iTTM

2. Installation of iWS6.0 SP2. iWS must be upgraded to iWS6.0 SP2
   1. This requires a removal of your existing iWS and iAS. Before doing so it is advisable to stop the web servers from running.

   See http://docs.iplanet.com/docs/manuals/fasttrak/41/ig/unix.htm

   Or http://docs.iplanet.com/docs/manuals/enterprise/50/ig/unix.htm

   Go to the iWS install directory (typically /opt/netscape/server4 for iWS4.1 and /opt/iws6 for iWS6.0) and type

   cd /opt/iws6

   ./uninstall

   rm -rf /opt/iws6

   1. Now consult the iTTM 3.0.1 Installation and Configuration Guide for details on how to install iWS 6.0 SP2:

      http://docs.sun.com/source/816-6283-10/index.html

3. Installation of iAS 6.5
   1. Remove iAS6.0. Before doing so it is advisable to stop the application server from running. See

   http://docs.iplanet.com/docs/manuals/ias.html#sp3

   Go to the <ias_install_directory> (typically /opt/ias6) and type

   cd /opt/ias6

   ./uninstall

   rm -rf /opt/ias6

   1. Now consult the iTTM 3.0.1 Installation and Configuration Guide for details on how to install iAS 6.5:

      http://docs.sun.com/source/816-6283-10/index.html

4. iMQ for Java. You will need to reinstall and reconfigure iMQ for java with iAS. You should uninstall imq for java 2.0 using the instructions in the IMQ for java guide found in

   http://docs.sun.com/db/prod/s1.ipmsgquj

   http://docs.iplanet.com/docs/manuals/javamq/20/install.pdf

   and reinstall and reconfigure using the section in this manual "iPlanet Message Queue for Java 2.0 (step 2b)"

5. Application of the upgrade script itself

   cd /cdrom/cdrom0/upgrade

   ./upgrade

   This asks the following questions

[0] Install location [/opt/ittm]: /opt/ittm

[1] The root location of iPlanet Application Server ? /opt/ias6

[2] The root location of iPlanet Web Server documents directory? /opt/iws6/docs

[3] Enter the password to use for the tokenkeystore? password

[4] The user that will start iTTM ? tbase

[5] The group that this user belongs to ? iplanet

[6] On what host is your iTTM iPlanet Web Server ? [ myhost.uk.sun.com ]

[7] On what HTTP port is your iTTM iPlanet Webserver running ? [ 80 ]

the script will also ask for confirmation before converting the certificate store to the new token key store format. Type <y> and <return> to generate the token key store. Pressing <return> to accept the default <n> will require that you run the following script later:

/opt/ittm/Scripts/ncipherupgrade

Note also that the conversion of the certificate store will fail if the ncipher box is not available

6. SQL Scripts to update your database can be found in

   /opt/ittm/current/Config/sql/tbaseUpgrade3_0.sql

   /opt/ittm/current/Config/sql/PaymentsUpgrade2_0.sql

   There is no upgrade path for Biab and Tooledup as such these databases will have to be reconfigured from scratch. Remove the existing iTPS component database as follows:

   @Drop_biab

   commit;

   Now manually drop views and functions that were not dropped by the script (if any):

   drop view errorview

   drop view raw_data_payments_view

   drop function biab_req_insert

   commit;

   Log on as tdup user :

   @Drop_merchantAll

7. You should uninstall all existing iTPS 1.0 components and reinstall iTPS 2.0 components from the cdrom by following the instructions in this guide:
   1. Before you install any component you will also first need to reinstall a Web Server instance for that component: See"Installing the iWS 6.0 (step 4a)"

   2. "BiaB Back End office simulator (step 3c)"

   3. "BiaB Admin Tool (step 3d)"

   4. "Installing Buyers Bank Website (step 4b)"

   5. "Seller's Website TooledUp (step 4c)"

8. You should install all new iTPS 2.0 components from the cdrom by following the instructions in this guide:
   1. "Condition Management Website (step 3e)"

   2. "Obligation Management Website (step 3f)"

9. Follow the iTTM 3.0.1 Installation and Configuration guide on how to Install

10. OCSP Responder

11. JMSProxy.

10. If jmsproxy.properties was in existence previously, this will have been preserved. If not, defaults will have been installed and this may need configuring

11. You should consult the Installation chapter of the iTTM 3.0.1 Installation and Configuration Guide. The following needs to be configured:
    1. The section on secure properties.

    2. Configure the iWS for URL rewriting and SSL Decryption

12. The configuration settings that you had with iTTM 2.2.1 are set automatically. For new configuration, consult the iTTM 3.0.1 Installation and Configuration Guide.

Reverting

If an error occurs during the script the original installation can be recovered using the revert script. This will return the iTTM installation to its state before the first time the upgrade script was run.

cd /cdrom/cdrom0/upgrade

./revert

Numbered backups are made with each running of the upgrade script. However, revert will always restore from the last backup. Thus, to restore from an earlier backup, remove the first numbered backup after this version. Backups are named

<old ittm directory>.old.<version>

You can also revert your database using the following sql scripts

/opt/ittm/current/Config/sql/Drop_Payments2_0

/opt/ittm/current/Config/sql/Drop_tbase3_0

There is no revert procedure for Biab and TooledUp. Once you get the system to an old state it is then possible to run the upgrade script again.

Advanced Silent Install options

---

iTPS Silent install has been designed so that the following kinds of installations are possible:

• Reinstallation

• Installing a similar installation on other machines is facilitated by editing a file that contains a list of settings.

• Seamless upgrades and patches for future distributions are now also possible.

The procedure for performing these kinds of installations can be found below:

1. Gather appropriate information in order to assist a silent iTTM 3.0.1 install
   1. To ask for command line answers and place the answers to questions in the directory /outputdir that can then be edited and used to do installs on other machines.

      ./cdrom/cdrom0/itps/setup -k /outputdir

   2. To gather settings from existing packages and place the answers to questions in the directory /outputdir that can then be edited and used to do installs on other machines.

      ./cdrom/cdrom0/itps/setup -m /outputdir

2. Perform the actual iTPS Installation using one of the following procedures
   1. To perform a complete graphic install on the entire product (itps only and not itps components)

      ./cdrom/cdrom0/itps/setup -g

   2. To perform a complete command line install on the entire product entering answers to questions at the terminal

      ./cdrom/cdrom0/itps/setup -c

   3. To perform a complete command line install from a file created in /outputdir and read from /inputdir. The output will also be sent to a log file

      ./cdrom/cdrom0/itps/setup -k /outputdir

      ./cdrom/cdrom0/itps/setup -s /inputdir logfilename

   4. To perform a complete command line install from existing package settings in order to perform a new install on a different machine created in /outputdir and read from /inputdir. The output will be sent to a log file.

      ./cdrom/cdrom0/itps/setup -m /outputdir

      ./cdrom/cdrom0/itps/setup -s /inputdir logfilename