Previous     Contents     DocHome     Index     Next     
iPlanet Trustbase Payment Services 2.0 Beta Systems Administration Guide



Chapter 3   Running the System


Once you've installed and configured, this chapter shows you how you can test your system is up and running correctly and processing payments requests as expected.


Starting the system



Before checking any particular component 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:

  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.1 on 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 checking that components are running, starting and stopping each component.


Oracle 8.1.7

Oracle 8.1.7 is a complex product and the instructions are intended as a quick list of items that are useful when trying to determine the status of the Oracle installation.

Table 1:


Information Type  

Example Set-up Value for Oracle 8.1.7  

Install directory  

Oracle program files: /opt/oracle/app/product/8.1.7/bin Oracle data files: /identrusdb/orcl  

Oracle user login  

Username: oracle, Password: oracle  

Sqlplus - dba admin  

Username: sys, Password: change_on_install  

Sqlplus - tbase user  

Username: tbase, Password: tbase  

Operational ports  

Oracle ports: 1521  

SID  

orcl  

Useful information to check on the installation and make a note of:

Useful commands for starting and stopping Oracle. Checking Oracle is running can be performed by looking at the running processes using the process grep or process list commands. If Oracle is not running then you will need to log in as the Oracle superuser and start the Oracle.

Table 2:

Action or check  

Command or output  

To start server  

As oracle user: svrmgrl; connect internal; startup; exit

lsnrctl; start; exit  

To stop server  

As oracle user: lsnrctl; stop; exit

svrmgrl; connect internal; shutdown; exit  

Processes grep  

ps -ef | grep oracle  

Tables of interest  

Auditdata: Contains internal audit information and indicates what the TC has processed.

Error: Shows unexpected errors e.g. cannot communicate with Certificate Authority

Error_support: Shows any java stack trace associated with the error table.  


nCipher

To check that the nCipher is running perform a process list on each machine. If no nFast process is in the list you will need to start the nFast hard server using the appropriate command.

Table 3:

Information Type  

Example Set-up Value nCipher  

Install directory  

/opt/nfast  

Operational ports  

9000  

To start server  

nfast start  

To stop server  

nfast stop  

Processes grep  

ps -ef | grep hard  

Process list  

nfast 4241 1 0 Mar 05 ? 0:22 ../sbin/hardserver -llogfile

nfast 4246 4241 0 Mar 05 ? 0:10 ../sbin/hardserver -llogfile

 

Documentation  

nCipher KeySafe 1.0
http://www.ncipher.com
 


iMQ for Java 2.0

iMQ for Java 2.0 needs to be started before iTPS can be run. If you have configured iMQ to start automatically upon reboot but have not yet re-started, use the following:

# /etc/init.d/jmq start

If it becomes necessary to clear out the contents of the queue then start the broker in the following way

# /etc/init.d/jmq stop

# /opt/SUNWjmq/bin/jmqbroker -reset store

Other commands regarding queue maintenance, can be found on Pages 109-111 of your iMQ for Java Administrator's guide:

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

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


Bank in a Box back End

To run the Bank in a Box back end, run the biab script located in the scripts directory. The script accepts the following arguments, although none are required for normal operation


Table 4:

-verbose  

verbose output  

-debug  

debug output  

-quiet  

only display warnings and errors  

-logfile <file>  

Specify the name of a file for log output  

-admin  

Enter user administration mode  

If the server was started in admin mode, user management may be performed at the BiaB command line. The following commands are accepted:

Table 5:

adduser <username> <password>  

Adds a user to the system  

enableuser <username>  

Enables a user account  

disableuser <username>  

Disables a user account  

listusers  

Displays a list of user accounts  

version  

Displays the version of the software  

Bank in a Box Back End can be started as follows:

bash-2.03# ./opt/itps-biab/scripts/biab -debug

[AUDIT] Starting BIAB [V1.0-1001500003703-18]


Bank in a Box administrator tool

The Bank in a Box administrator tool is a Web server application running on iAS 6.0. To check that the Web Server is running use the grep command given below. If the server is not running then start the admin server and use the tools within the adminserver to manage the web server


Table 6:

Information Type  

Example Set-up Value iws6  

Install directory  

/opt/iws6  

Administration logon  

Username: iwsadmin, Password: *******  

Operational ports  

Server: 80, Admin: 8888  

To start server  

/opt/iws6/https-myhost.mycompany.com/start  

To stop server  

/opt/iws6/https-myhost.mycompany.com/stop  

To start admin server  

/opt/iws6/https-admin/start  

To stop admin server  

/opt/iws6/https-admin/stop  

Processes grep  

ps -ef | grep iws  

Process list  

nobody 9876 1 0 12:52:08 0:00 ./uxwdog -d /opt/iws6/https-myhost.mycompany.com/config

nobody 9877 9876 0 12:52:08 0:01 ns-httpd -d /opt/iws6/https-myhost.mycompany.com/config

also /opt/iws6/https-admin/config if the admin is running  

Install logs  

/opt/iws6/setup/WebServer/  

Log directory  

/opt/iws6/https-myhost.mycompany.com/logs  

Document root  

/opt/iws6/docs  

Installation and Configuration Documents  

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

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

To access the site  

http://myhost.mycompany.com/itps-tdup/logon.html  


iTPS

The iTPS is reliant on three components running:

  • iWS 6.0 SP1

  • iAS 6.0 SP3

  • iTTM 3.0.1

If all these components have been started correctly then the iTPS component should be available. To check to ensure that the components are running, use the grep commands shown in the tables below. If iTTM is running, but iAS is not, shutdown the iTTM and restart the components starting with iAS 6.0.


iWS 6.0 SP1


Table 7:

Information Type  

Example Set-up Value iWS6 SP1  

Install directory  

/opt/iws6  

Administration logon  

Username: iwsadmin, Password: identrus  

Operational ports  

Server: 80, Admin: 8888  

To start server  

/opt/iws6/https-myhost.mycompany.com/start  

To stop server  

/opt/iws6/https-myhost.mycompany.com/stop  

To start admin server  

/opt/iws6/https-admin/start  

To stop admin server  

/opt/iws6/https-admin/stop  

Processes grep  

ps -ef | grep iws  

Process list  

nobody 9876 1 0 12:52:08 0:00 ./uxwdog -d /opt/iws6/https-myhost.mycompany.com/config

nobody 9877 9876 0 12:52:08 0:01 ns-httpd -d /opt/iws6/https-myhost.mycompany.com/config

also /opt/iws6/https-admin/config if the admin is running  

Install logs  

/opt/iws6/setup/WebServer/  

Log directory  

/opt/iws6/https-myhost.mycompany.com/logs  

Document root  

/opt/iws6/docs  

Installation and Configuration Documents  

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


iAS 6.0


Table 8:

Information Type  

Example Set-up Value for iAS6.0  

Install directory  

/opt/ias6  

Administration logon  

Username: admin, Password: password  

Operational ports  

Directory Admin: 20000, kas admin:10817, Directory server: 389  

To start server  

/opt/ittm/Scripts/startias  

To stop server  

/opt/ittm/Scripts/stopias  

Installation logs  

/opt/ias6/setup/  

Processes grep  

ps -ef | grep ias

To get just the 'kiva' processes (the ones that do the jvm work) do a ps -ef | grep k.s  

Process list  

root 10066 10064 0 14:33:21 0:03 /opt/ias6/ias/bin/.kjs -cset CCS0

root 10059 9504 0 14:33:16 pts/6 0:00 /opt/ias6/ias/bin/.kas

root 9504 1 0 12:47:38 pts/6 0:00 /bin/sh /opt/ias6/ias/bin/kas

root 10070 1 0 14:33:25 0:00 /bin/sh /opt/ias6/ias/bin/kcs -cse t CCS0 -eng 2

root 10064 1 0 14:33:21 ? 0:00 /bin/sh /opt/ias6/ias/bin/kjs -cset CCS0 -eng 1

root 1061 1 0 14:33:19 ? 0:00 /bin/sh /opt/ias6/ias/bin/kxs -cset CCS0 -eng 0

root 10072 10070 0 14:33:25 ? 0:00 /opt/ias6/ias/bin/.kcs -cset CCS0 -eng 2

root 10062 10061 0 14:33:19 ? 0:01 /opt/ias6/ias/bin/.kxs -cset CCS0 -eng 0

nobody 8174 1 0 12:45:04 ? 0:04 ./ns-slapd -f /opt/ias6/slapd-unix

d02/config/slapd.conf -i /opt/ias6/slapd-<Machine-name> (check?)  

Logged processes  

kxs_0_CCS0: Contains information about the incoming message and the plugin start and stop

kjs_0_CCS0: Contains the standard out from any running java process - can contain some debug information.  

Installation Document  

http://www.iplanet.com/products/infrastructure/app_servers/index.html  


iTTM 3.0.1


Table 9:

Information Type  

Example Set-up Value for iTTM 3.0.1  

Install directory  

/opt/ittm  

Administration logon via web  

Username: administrator, Password: administrator  

Certificate manager  

/opt/ittm/Scripts/runtokenkeytool  

Operational ports  

Admin via web: 80 (http://myhost.mycompany.com/NASAdapter/logon.html)  

To start server  

/opt/ittm/Scripts/starttbase  

To stop server  

/opt/ittm/Scripts/stoptbase  

Property file location  

/opt/ittm/myhost/*.properties  

Processes grep  

ps -ef | grep java  

Process list  

root 9658 1 0 12:47:48 pts/6 0:04 /usr/bin/../java/bin/../jre/bin/../bin/sparc/native_threads/java uk.co.jcp.app.

root 9713 1 0 12:47:53 pts/6 0:08 /usr/bin/../java/bin/../jre/bin/../bin/sparc/native_threads/java uk.co.jcp.tbas

root 9790 1 0 12:48:03 pts/6 0:12 /usr/bin/../java/bin/../jre/bin/../bin/sparc/native_threads/java uk.co.jcp.secu  

Installation Document  

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

http://docs.iplanet.com/docs/manuals/trustbase/3.0.1/icg/contents.htm  


Enabling iMQ for Java

  1. If not already running, in a separate window start the iMQ message queue:

    /opt/SUNWjmq/bin/jmqbroker -tty

    Other commands, such as resetting the queue, can be found on Pages 109-111 of your iMQ for Java Administrator's guide:

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


Buyer and Seller Web applications

These Web applications are both deployed on top of the iWS 6.0 installations on the Buyer and Seller Web site machines. In order to check that these applications are available, use a browser to go to the appropriate URL.

Table 10:

Information Type  

Example Set-up Value iWS6.0 SP1  

Install directory  

/opt/iws6  

Administration logon  

Username: iwsadmin, Password: identrus  

Operational ports  

Server: 80, Admin: 8888  

To start server  

/opt/iws6/https-myhost.mycompany.com/start  

To stop server  

/opt/iws6/https-myhost.mycompany.com/stop  

To start admin server  

/opt/iws6/https-admin/start  

To stop admin server  

/opt/iws6/https-admin/stop  

Processes grep  

ps -ef | grep iws  

Process list  

nobody 9876 1 0 12:52:08 0:00 ./uxwdog -d /opt/iws6/https-myhost.mycompany.com/config

nobody 9877 9876 0 12:52:08 0:01 ns-httpd -d /opt/iws6/https-myhost.mycompany.com/config

also /opt/iws6/https-admin/config if the admin is running  

Install logs  

/opt/iws6/setup/WebServer/  

Log directory  

/opt/iws6/https-myhost.mycompany.com/logs  

Document root  

/opt/iws6/docs  

Installation and Configuration Documents  

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

Accessing the Buyer Website  

http://myhost.mycompany.com/itps-bfi/logon.html  

Accessing the Seller Website  

http://myhost.mycompany.com/itps-tdup/logon.html  

If the Web Servers are not running then use the process grep (on the host machine) to check that the web server is running. If the Web Server process is not running then start the webserver using the admin console.


Running the Models



We now describe how to run the system for each main kind of Payment Model


Running the Three Corner Model

In this situation the Buyer's Bank is the same as the Seller's Bank, i.e. the buyer and the seller have both been issued with certificates from the same Financial Institution.

  1. User interfaces with the Seller's Website, in this case TooledUp, and initiates a payment

  2. Payment Message gets sent to the iPlanet Trustbase Payment Services Server

  3. iPlanet Trustbase Transaction Manager informs its backend system or in this example Bank in a Box.

  4. Bank in a Box then sends confirmation of payment to TooledUp

  5. The status of this payment initiation is returned back to the seller and hence buyer.


Running the Four Corner Model (SFIM)

  1. Buyer interfaces with Seller's Website, in this particular instance TooledUp, and initiates a payment.

  2. Payment Message gets sent to iPlanet Trustbase Payment Services Server at the Seller's Bank informs its back end systems that in turn informs the Buyers Bank.

  3. Buyers Bank informs back end system, in this case Bank in a Box.

  4. A response is returned to its financial institution

  5. The SFI on receiving the response from the BFI informs its back end systems and response gets sent to the Sellers Website confirming payment.


Making a Payment via the Buyers Bank (BFIM)

  1. If the Subscriber signed data is signed by the Buyer then

    1. Buyer initiates payment from the Buyers Bank Website

    2. Payment Message is sent to iPlanet Trustbase Payment Services that in turn informs the Buyers Bank back end systems.

    3. Response gets returned to Buyers Bank Website

  2. If the seller has signed the subscriber signed data then

    1. Buyer initiates payment from the Buyers Bank Website

    2. Payment Message is sent to iPlanet Trustbase Payment Services that in turn informs the Buyers Bank back end systems.

    3. The BFI informs the seller's SFI

    4. The SFI informs its back end systems

    5. Response sent back to the BFI

    6. BFI responds back to the buyer



    Note More Information about how each payment scheme defines its Models and Payment products can be found at http://www.identrus.com

    Example supported Schemes include:

    Eleanor Payment Reference Specification




Initiating Payment via Sellers Website TooledUp



You can test the system has been installed correctly by going to the Tooledup Website and initiating a payment as follows.

  1. Go to TooledUp e.g. http://myhost.mycompany.com:80/itps-tdup/logon.html

Figure 3-1    TooledUp Main Menu


  1. Insert Your Smart Card and login. The following menu appears

Figure 3-2    TooledUp Ltd Catalogs


  1. Select a product to purchase

Figure 3-3    TooledUp Category Selection


  1. Add it to the Shopping Basket

Figure 3-4    Add to Shopping Basket


  1. Shopping Basket Details

Figure 3-5    Shopping Bag Details


  1. Make delivery Details

Figure 3-6   

Enter Delivery Details

  1. Make payment. Select Submit at the bottom of the Delivery screen menu

  1. Confirm Delivery Details and Payment type. Choices are

    1. Eleanor Payment Order

    2. Eleanor Payment Obligation

    3. Eleanor Certified Payment Obligation

    4. Eleanor Conditional Payment Obligation

    5. Eleanor Conditional Payment order

    6. Eleanor Certified Conditional Payment Obligation

Figure 3-7    Payment Type


You should the opening chapter in your iTPS Installation Guide for details about what each of these payment types actually mean. Once the user selects <submit>, the following page will be displayed unless a conditional payment product is selected. If a conditional payment product is selected there are screens to allow the user to add conditions before progressing to the next screen. For a worked example of how conditions are actually added see for instance the next chapter "Running the Four Corner Model" and the section "Conditional Payment Order"

  1. Confirm Delivery Details

Figure 3-8    Confirm Delivery Details


  1. Payment Accepted

Figure 3-9    Payment Accepted


  1. Payment Confirmation

    The XML message from this transaction can be confirmed in a number of different ways:

    1. Via your API com.iplanet.trustbase.initiator.cpi

    2. Viewing the Identrus raw_data log (see your iPlanet Trustbase Transaction Manager Developer Guide )

    3. Editing IWS6 startup UNIX script

      /opt/iws6/https-myhost.mycompany.com/start

    by adding a debug feature as follows:

    case $arg in

             -debug)

    ./ns-httpd -d $PRODUCT_SUBDIR/config

    exit 0

    ;;

    -start)

    ./$PRODUCT_BIN -d $PRODUCT_SUBDIR/config $@

    if test $? -ne 0 ; then

    exit 1

    fi

    then run the script as

    ./start -debug

  2. Check Order List. Finally there is a Tooled Up screen to display confirmed payment requests.

Figure 3-10    Order List


If the user wishes to cancel a payment request then they should select the specific payment they wish to cancel. A cancellation screen should then appear.


Running Bank in a Box Back End

  1. Once the classpath is correct and the queue properties are set, restart the server instance. For instance:

    /opt/iws6/https-admserv/start

    /opt/iws6/https-myhost.mycompany.com/start

  2. Start the bank in a box back end in a separate window:

    ./opt/itps-biab/scripts/biab

  3. Once deployed successfully, the Web Site can be accessed from the browser with the following url. For example,

    http://myhost.mycompany.com:80/itps-biab/logon.html


Running Bank in a Box Admin Tool

The Bank in a Box (BiaB) has been expanded to allow it to present a user interface permitting examination of messages received, and sending of response messages. This allows a standard installation of iTPS to be used in a live system, by requiring manual intervention between the BiaB interface and the real bank back end infrastructure. Clearly, this approach is only feasible for very low transaction volumes, but does allow evaluation of the product prior to full scale integration with the existing back end infrastructure. The system also allows you to acknowledge Payments. The following provides a walkthrough of this operation

  1. Make Sure your BiaB Backend Server is running and a username and password has been allocated to. This can be changed by starting the BiaB in Admin mode and typing:

    cd /opt/itps-biab/scripts/

    ./biab -admin

    adduser <username> <password>

    exit

    ./biab -debug

    Note there is a help command available within this script

  2. Load the following URL in your browser:

    http://myhost.mycompany.com:80/itps-biab/logon.html

Figure 3-11    Bank in a Box Main Menu


Enter your username and password, set up by your administrator, as described on the previous page.

  1. Type in the username and the password. The following menu appears

Figure 3-12    Bank in a Box Admin Tool Homepage


  1. There are two selections possible here

    1. Messages in progress. Displays messages that have not been acknowledged with the appropriate response messages yet.

    2. Completed Messages. These are messages that have had the required acknowledgements issued. For Payment Request messages, when the PaymentExecution acknowledgement is sent the message is moved from <Messages in progress> to <Completed Messages>. For PaymentCancellationRequest messages, as soon as a cancellation acknowledgement is sent the cancellation message is moved to the <Completed messages> screen.

  2. Select <messages in progress>

  3. An example screen containing some messages now follows. Clearly the first time there will be no messages.

Figure 3-13    BiaB Message Screens


  1. There are three options for viewing a message

    1. Select <re-sort> to reorder messages

    2. Select <Create Search> to restrict the number of messages displayed on the screen

Figure 3-14    BiaB message searching


    1. Select an individual message to view and the following screen appears:

Figure 3-15    BiaB Message Details


This screen displays details of the original message, plus any acknowledgements that have been sent in conjunction with the message.

  1. Below are listed the acknowledgments that could be sent from the BiaB

    1. Complete

    2. Execution

    3. PayInst

    4. Cancellation

    5. Obligation

      Depending on the type of the request message some options may not be available. The precise definitions of each of these options can be found in the Eleanor Technical Specification.

Figure 3-16    Acknowledging a message


  1. Each individual message can be viewed in more detail by selecting the <XML> tag

Figure 3-17    An XML Message


  1. Options are available to sort and retrieve messages from an index.


Initiating Payment via Buyers Bank Website

This example is of a Web Site hosted by the Buyer's bank accessed by Buyers who belong to the Eleanor Payment Scheme. It provides the ability for the buyer to initiate payment requests and cancellations directly with its bank.

  1. Type in the URL of the Buyer's Bank Website. For example

    http://myhost.mycompany.com:80/itps-bfi/logon.html

Figure 3-18    Buyers Bank Website Homepage


  1. Select <Make Payment>

Figure 3-19    Initiate Payment


Details of what each of these fields mean can be found in your payment Scheme Specification

  1. Check the details you have entered are correct and sign the payment using your buyers certificate you configured in the previous chapter

Figure 3-20    Sign Payment


  1. Finally when the payment has been initiated a Payment message will be sent to the URL of the Buyers Bank in which you installed iPlanet Trustbase Payment Services on. The following steps take place:

    1. Buyer Website sends Payment to CPI Library located on the Buyers Website Webserver

    2. CPI Library forwards this to iPlanet Trustbase Payment Services

    3. iPlanet Trustbase Payment Services processes the message and forwards the reply to the Buyers CPI Library located on the Buyers Webserver

Figure 3-21    Payment Initiation completed successfully


  1. Information appears on the Buyers Screen confirming payment. Select <List Payment> to check the information that you have entered has been processed as a payment.

Figure 3-22    List Payment



Condition Management Website

This website will be used by users to alter the status of conditions.

We now illustrate a typical interaction with the Condition Management Website involving a simple purchase by a buyer from the tooledup Website using a Condition payment Order. We introduce two users, each with their own smartcards acting as the following:

  • A buyer purchasing a product from Tooled Up on Seller's Website

  • A Conditional Discharge Party

  • We then assign Users (by issuer and subject on their Smart Cards) Organisations and roles. In this case, we only have one user that needs assignment, the buyer.

    telnet buyerbank.buyercompany.com

    cd /opt/ittm/Scripts

    ./runuserdbtool

    newrole -role BUYER

    neworganisation -organisation BFI

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

  • Buyer goes to the TooledUp Web Site hosted by the seller

    http://myhost.mycompany.com/itps-tdup/logon.html

    1. Insert your Buyers SmartCard

    2. Login to TooledUp

    3. Select a product

    4. Enter Buyer Delivery Details

    5. Select <Payment Type>

    6. Select <Conditional Payment Order>

Figure 3-23    Conditional Payment Order


    1. Select <submit>

    2. Select the condition <Payment has been approved>

Figure 3-24    Approve Payment


    1. Set Discharge by date to be sometime in the future. This date represents the final day that the CDP will be able to discharge a condition. By "discharge we mean that the CDP has successfully completed the specified condition.

    2. Set the Waive by date to be sometime after the Discharge date. This date represents the last date by which the Buyer can "waive" the requirement that the CDP must discharge the condition. This basically allows the buyer to tell the system to ignore the specified condition.

    3. Select <Add Condition>

      Note: for the pilot, conditional payments request messages should only contain one discharge-by-date and one waive-by-date. This can be accomplished by either of the following steps:

    4. The user enters only one condition per payment request message in TooledUp

    5. If multiple conditions are included in a payment request, then the discharge-by-dates assigned to each condition must all be the same, and the waive-by-dates assigned to each condition must all be the same

Figure 3-25    A condition has been created


    1. Select <Next>

Figure 3-26    Payment Details


    1. Select <Submit> and Sign it

    2. Make a note of the Payment Reference number to aid in identifying this transaction later.

Figure 3-27    Payment Reference Details


  1. In order to confirm that the conditional Payment order had reached the bank's back end system, Go to the Biab Admin Screen

    http://myhost.mycompany.com/itps-biab/logon.html

    1. Select Messages in Progress

    2. View the corresponding Payment Reference

  2. The CDP will be sent an email indicating that they have been allocated a condition. A URL of the Condition Management Website is included in this email.

  3. Discharge the Condition as follows. Insert CDP Smart Card and go to the Condition Management Website on the BFI.

    http://myhost.mycompany.com/itps-cond/logon.html

    1. Logon to the system and if successful, Select <Active Conditions>

Figure 3-28    Payment Reference


    1. Select the condition relating to your reference number. The status can be change to "CDP Processing", "Discharged" or "Failed".

    2. "CDP processing" indicates that the CDP has accepted this condition.

    3. "Discharged" indicates that the CDP has successfully fulfilled the condition.

    4. "Failed" indicates that the CDP has not accepted or cannot fulfill the condition.

    5. It is possible to attach additional documentation with a condition update message. The limit on this attachment size is 2GB

      Select <Associate>

      Note the Smartcard Web browser plug-in normally has a much lower restriction on data size than the 2GB the condition Website provides

    6. Select <Discharged>

    7. Select <ok>

    8. Sign it

    9. Send it

  1. Finally, since the condition has now been discharged the Buyers Bank makes the payment by returning to the biab website

    http://myhost.mycompany.com/itps-biab/logon.html

    1. Select Message

Figure 3-29    Make the Payment


    1. Select <send>


Obligation Management Website

This website is used to transfer Obligation Payment products, from the seller to either the BFI or SFI. This website can either be installed at the SFI or BFI. At the SFI, the two roles that can access the site are seller/SFI bank operator. If at BFI, then the only role is BFI bank operator (BANK)

We now illustrate a typical interaction with the Obligation Management Website involving a simple obligation transfer from the Seller to the Buyers bank after a payment is initiated by a buyer from the tooledup Website using a Payment Obligation. There are two roles that need to be assigned

  • The Seller

  • The Buyers Bank

As before,

  1. Assign Users, Organisations and Roles

    telnet Sellerbank.sellercompany.com

    cd /opt/ittm/Scripts

    ./runuserdbtool

    newrole -role SELLER

    neworganisation -organisation SFI

    newuser -issuer "CN=BuyerBank CA,OU=BuyerBank,O=BuyerBank,C=GB" -subject "CN=Buyer Cert,OU=Buyer,O=Buyer,C=GB" -organisation SFI -email "sellerl@sellercompany.com" -role SELLER

    telnet buyerbank.buyercompany.com

    cd /opt/ittm/Scripts

    ./runuserdbtool

    newrole -role BANK

    neworganisation -organisation BFI

    newuser -issuer "CN=BuyerBank CA,OU=BuyerBank,O=BuyerBank,C=GB" -subject "CN=Buyer Cert,OU=Buyer,O=Buyer,C=GB" -organisation BFI -email "buyerbank1@buyerbank.com" -role BANK

  2. Initiate Obligation Payment

    1. Go to Tooled Up

      http://myhost.mycompany.com/itps-tdup/logon.html

    2. Insert your Buyers SmartCard and Login to TooledUp

    3. Select a product

    4. Enter Buyer Delivery Details

    5. Select <Payment Type>

    6. Select <Payment Obligation>

Figure 3-30    Making a Payment Obligation


    1. Make a note of the reference

  1. BFI accepts Obligation to make payment.

    1. Log onto Biab

      http://myhost.mycompany.com/itps-biab/logon.html

    2. View Sellers Active Messages

Figure 3-31    Biab Active Messages Screen


    1. Select Messages that match the reference

    2. Select SFI or Seller

    3. Send an Obligation Acknowledgment

Figure 3-32    Send Acknowledgement


    1. Fill in details

    2. Send Obligation Acknowledgement

Figure 3-33    Send Obligation Acknowledgement Screen


  1. Seller transfers obligation from seller to either BFI or SFI

    1. Logon to Obligation Management Website Enter your SmartCard

      http://myhost.mycompany.com/itps-om/logon.html

    2. Select <Active Obligation>

    3. Select Correct Message

    4. Make the transfer by selecting the <obligation transfer> page

Figure 3-34    Transfer Obligation


    1. Fill in details of where the transfer should take place including the bank code, account and currency of the FI

    2. Select <ok>


Running the CPI Test program

Please refer to the Developer Guide


Previous     Contents     DocHome     Index     Next     
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.

Last Updated October 22, 2002