Chapter 2   Configuring your Websites

Once you've installed and configured, this chapter shows you how you can configure your individual websites in preparation to running the System

Configuration prerequisites

---

Before configuring you must bring the individual components up and make sure that the system is actually running. Starting the system must be performed in a particular order otherwise components will fail to communicate properly. The order for starting the system is:

Order for starting the system

1. Oracle 8.1.7

2. nCipher HSMs on all machines

3. iMQ for Java 2.0 on both the Buyer and Seller Bank machines

4. Bank in a Box back end server on the Buyer and Seller Bank machines

5. Bank in a Box administration tool and iWS 6.0 SP1 on the Buyer and Seller Bank machines

6. iTPS on the Buyer and Seller machines
   1. iWS 6.0 SP1 on both the Buyer and Seller Bank machines

   2. iAS 6.0 SP3 on both the Buyer and Seller Bank machines

   3. iTTM 3.0.1on both the Buyer and Seller Bank machines

7. JMS Proxy on both the Buyer and Seller Bank machines

8. Buyer web site (BFI) Web server

9. Tooledup Seller web site Web server

10. Condition Management web site Web server

11. Obligation Management web site Web server

The following sections provide instructions for configuring your Websites.

iTTM First Time Start Procedure

The following procedure stops the system.

• Logon as root

  cd /opt/ittm/Scripts LOGNAME=nobody;export LOGNAME /opt/ittm/Scripts/stopias LOGNAME=root;export LOGNAME /opt/ittm/Scripts/stopias /opt/ias6/slapd-myhost/start-slapd /opt/iws6/https-myhost.mycompany.com/start /opt/iws6/https-admserv/start ./startias ./starttbase

  , under a separate window

iTTM Restart procedure

• Logon as root and run the following shell:

  /opt/ias6/slapd-myhost/start-slapd /opt/iws6/https-myhost.mycompany.com/start /opt/iws6/https-admserv/start cd /opt/ittm/Scripts ./startias ./starttbase

• Logon onto iTTM as follows:

http://myhost.mycompany.com/NASAdapter/logon.html

Steps to Configuring your websites

---

1. Configuring a Conditional Management Website
   1. Configure your Identrus-Compliant SmartCard.

   2. Utilise Userdbtool to define buyers. The issuer DN and subjectDN of the users should match those on their Smart Cards. For example,

      cd /opt/ittm/Scripts

      ./runuserdbtool

      newrole -role BUYER

      neworganisation -organisation "CM Website"

      newuser -issuer "CN=BuyerBank CA,OU=BuyerBank,O=BuyerBank,C=GB" -subject "CN=Buyer Cert,OU=Buyer,O=Buyer,C=GB" -organisation "CM Website" -email "buyerl@buyercompany.com" -role BUYER

   3. From the iTTM main login menu, Select <Services><Payments> <Condition Registry Details> to define Website location, e.g.

      http://myhost.mycompany.com:{condwebsite port Nr}/itps-cond/Webcr

   4. From the iTTM main login menu, Select <Services><Payments><Membership List> and Add appropriate F.I. members to the membership list

2. Configuring an Obligation Management Website
   1. Identrus Compliant SmartCard.

   2. Userdbtool Seller/Buyer where the issuer DN and subjectDN of the users should match those on their Smart Cards.

      telnet sellerbank.sellercompany.com

      cd /opt/ittm/Scripts

      ./runuserdbtool

      newrole -role SELLER

      neworganisation -organisation "OM Website"

      newuser -issuer "CN=SellerBank CA,OU=SellerBank,O=SellerBank,C=GB" -subject "CN=Seller Cert,OU=Seller,O=Seller,C=GB" -organisation "OM Website" -email "Sellerl@Sellercompany.com" -role SELLER

   Note. To allow a seller to log into the Obligation Management Website, one must ensure an organisation has been created that matches the SellerName element in the initial PaymentRequest.

   1. Select <Services><Payments><Membership List> and Add appropriate F.I. members to the membership list if not already present

3. Biab Admin tool. Go to Back End and use the adduser command to define a new user

   cd /opt/itps-biab/scripts

   ./biab -admin

   adduser <username> <password>

   exit

4. Tooled-Up
   1. An Identrus-Compliant Smart Card.

   2. From the ITTM logon screen Select <Services><Payments><Settlement Chain> and assign the appropriate currency to the appropriate F.I.

   3. Update CDP_Issuer_DN, CDP_DN and EMAIL used by the tooledup table CDPCERT manually to match the CDPs smartcard. For example,

      SQL> update CDPCERT set cdp_dn='CN=CDP1 User,OU=CDP

      Admin,O=CDP,C=GB',cdp_issuer_dn='CN=CA User,OU=CA Admin,O=CA,C=GB', email='cdpuser@mycdphost.com' where

      certid=1

   4. To add more CDPs one must insert new entries into CDPCERT with ascending CERTIDs and then associate required conditions to the specific CDPs by updating the CERTID column in the CONDITION table. i.e. One or more conditions may be associated with any one CDPCERT entry.

5. BFI
   1. Import Certificate Chain for Buyer in Browser

   2. Select <Services><Payments><Membership List> and Add appropriate F.I. members to the membership list if not already present

You are now ready to proceed to the next chapter "Running the Models"