Chapter 3   Backup, Uninstall, Reinstall and Restore

This chapter discusses how you can reinstall your system.

Overview

---

We now discuss a procedure for backing up key configuration data and installation settings prior to uninstalling, reinstalling and restoring saved parameters. This procedure can be applied for as many or as few packages or components as you wish.

1. Uninstall iTPS

1. iTTM Uninstall

   Consult the iTTM manual

2. Save your itps component settings. The following options illustrate how to save the settings you used for itps-biab. For example,

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

3. Remove iTPS components. For instance,

   /cdrom/cdrom0/itps-biab/setup -u

4. iWS 6.0 SP2Uninstall

   For those versions of software placed on an iWS 6.0 it may be possible to reinstall iTPS without having to reinstall the entire Web Server and all its instances. See

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

5. iTPS 2.0 Reinstall. Repeat the instructions in this manual. Note, however, In this case it is possible to reinstall the components using previous settings

   cd /opt

   /cdrom/cdrom0/itps-biab/setup -s /outputdir/itps-biab

6. You may need to remove your iTPS Oracle database. In some cases scripts are provided for you.

Example walkthrough

---

Reinstallation splits into four main steps

1. Backup

2. Uninstall

3. Reinstall

4. Restore

   Stop the jmqbroker using <CTRL-C> . This will have a knock on effect of correctly stopping the biab and jmsproxy processes. Stop ias using the script /opt/ittm/Scripts/stopias. It is assumed that a directory called /temp exists for storing config info required during the re-install:

Backup

Backup should be done from the user account. For instance user: tbase group: iplanet.

Step	Description of backup steps
1	Backup TokenKeystore cert databases (Only need *.db and identrus.domain but copy the whole hostname directory for simplicity): cp /opt/ittm/store /temp cp /opt/ittm/myhost/* /temp From the configuration screen select <config><export>
2	Backup the component website configurations to allow a quick and accurate re-install e.g.: ./cdrom/cdrom0/itps-biab/setup -m /outputdir/itps-biab
3	Backup TooledUp table cdpcert and CDP_issuer_DN, email, and CDP_DN entries: cd /temp Logon to database as TooledUp user and: spool cdpcerts.txt select * from cdpcert;
4	Backup userdb users to a text file: ./runuserdbtool lookupusers In another window, vi /temp/userdbusers.txt Paste in all user info from other window and save file.
5	Backup Membership details: Access each membership entry and copy each required line to a text file (e.g. /temp/config.txt) to aid with adding them back accurately.
6	Backup Authorisation cert details to /temp/config.txt To aid adding it back accurately.

Uninstall

Step	Description of uninstall steps
1	Run uninstall script for iTTM: ./cdrom/cdrom0/ittm/setup -u ./cdrom/cdrom0/itps/setup -u
2	Remove the install directory: rm -r /opt/ittm
3	Make sure that all the /opt/{package} directories are gone and that the deploy directories from the webserver root are also gone. If not, then remove manually. for instance, ./cdrom/cdrom0/itps-biab/setup -u Also delete all jsps from each webserver instance e.g. cd /{server_root}/{instance}/ClassCache/https-{instance} rm -r *
4	Log on to database as user for iTTM and run Drop scripts: @Drop_PaymentsAll @Drop_tbaseAll @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

Uninstall should be done from the root account.

Reinstall

Reinstall should be done from the root account

Step	Description of Re-installation steps
1	Tidy up SLAPD processes. Kill any running and then cd /ias_root/start-myhost ./start-slapd
2	Reinstall ittm using the settings you saved /cdrom/cdrom0/ittm/setup -s /outputdir/ittm or using a graphical or command line install, for instance: cp /cdrom/cdrom0/ittm/* . ./setup -g The settings you used previously can be found in /temp/myhost/*.properties
3	Select all three components iTTM OCSPResponder JMSProxy
5	Now install itps: . ./cdrom/cdrom0/itps/setup -s /outputdir/itps
6	Re-install the component websites. For instance, ./cdrom/cdrom0/itps-biab/setup -s /outputdir/itps-biab

Restore

Step	Description of restore steps
1	Copy your tokenkeystore cert database back into ittm: cp /temp/*.properties /opt/ittm/host cp -r /temp/store/* /opt/ittm/store cp -r /temp/xmlconfig /opt/ittm/myhost From the iTTM configuration screen select <config><import>
2	Now re-instate database tables for ittm, itps, biab and tdup: ftp ALL the sql files from the installation to your database host machine. Required Files are in: /opt/ittm/current/Config/sql /opt/itps-biab/config/sql /opt/itps-tdup/SQLscripts Logging on to database host as applicable users for each component if they are different: Logon as ittm user: @tbaseNew @PaymentsNew @biabNew commit; Logon as TooledUp database user (if different): @install_merchant_oraUpgradeNew Use DBVisualiser OR Logon as TooledUp database user: Re-instate CDPCERT entry (saved to a text file /temp/cdpcert.txt for use by TooledUp, e.g. Update table CDPCERT set CDP_ISSUER_DN='CN=??????', CDP_DN='CN=?????', email='CDPUser@cdphost.com'
3	Now add admin user to BiaB: cd /opt/itps-biab/scripts ./biab -admin adduser admin admin exit
4	Re-instate userdb users: cd /opt/ittm ./runuserdbtool Add roles for SELLER, BUYER, BANK and organisation of "SPD:seller.name" Then adduser, for each saved set of user info from the uninstall process. .
5	Restart all your webserver instances If they fail then you might need to manually kill them first. If they still fail then you may need to check the contents of /{server_root}/{instance}/config/web-apps.xml and magnus.conf, and the back-up copies in the webservers.
6	Now restart your F.I. using different open windows: cd /opt/itps-biab/scripts /biab -debug cd /opt/ittm/Scripts (assuming you are using the provided SSL Proxy) ./starttbase cd /opt/ittm/Scripts ./startias
7	Log in to tbase and Re-instate all Configuration info from text file /temp/config.txt Add Authorisation Cert Add Membership details Add Settlement Chain Add Condition Registry URL And recheck any settings that are not required to be default. Restart ias because Authorisation setting is NOT dynamic.
8	Use TooledUp to do a quick integrity check. Send a Conditional Payment Request and check that no emails were sent. Then go to BiaB to do a PayInst Ack and check that the correct emails have been sent. Then go to CR website at BFI and Discharge the condition, check again for email acknowledgements.

Restore should be done from the user account. For instance user: tbase group: iplanet.

Patches (for future use)

To Add/Patch a package (For future use only). This will patch all packages it finds in the distribution directory. From user: root

./cdrom/cdrom0/<itps_component_install_directory>/setup -p

Where <itps_componet_install_directory> is the location of the installed software that needs patching. For example:

/cdrom/cdrom0/itps-biab/setup -p