Revised Trade Message Broadcast Architecture

7/27/2019 Revised Trade Message Broadcast Architecture

1/90

RESERVE BANK OF INDIA

PDO-NDS COMPUTERISATION PROJECT

UpgradationSetup and OperationsManualInstallationRevised Broadcast Architecture

Release Manual

PDO-PDONNDS Application Version 2.7.54For ClustereedServer

(Member End)

Manual Version: 1.0

Prepared by

July AugustOctober 2003APRILJullyne 20042


2/90

PDO-NDS Ver. 2.7.42.7.5Server - USetup andOperations ManualpgradationInstallationManual

PDO-NDS Computerisation Project

Version1.0PDONDS Application For ClustereedModeServer

Version 1.0

Confidential and controlled document.Unauthorised access or copying is prohibited.

Tata Consultancy Services Uncontrolled when printed Page 2 of81541


3/90




Version 1.0

Table of Contents

1. Introduction.................................................................................................................................... 6

1.1 Purpose of the Document.........................................................................................................61.2 Scope of the Document............................................................................................................... 6

1.3 Scope of the Document............................................................................................................... 6

1.4 Organization of the Document..................................................................................................72. Install Procedure for applying Patch on the Member Server ation Procedure...............................9

Procedure for installing the Member Server in Clustered mode.......................................................9

2.1 Pre-requisites for Software Installation.................................................................................... 92.2 Renaming and Backup of NDS Operating System Registry ....................................................92.3 onOn Server:............................................................................................................................ 92.4 The Operating System (OS) should be Windows 2000 Advanced Server..............................202.5 Windows 2000 service pack 2 should be installed..................................................................202.6 Deleting Com+ Component on Server....................................................................................202.7 Database Backup on Server:..................................................................................................21System Backup of Server (If possible) ........................................................................................222.8 Generation of Input file (.inp file) Oracle 8i Installation...........................................................222.10 Install Oracle 8i Enterprise Edition in clustered mode along with with Oracle Fail Safe(version. 3.1.2) installationapplication on both the servers nodes without creating creating adatabase. The steps for loading oracle in clustered mode ...........................................................23

2.11 (Please refer the separate document given along with) are not a part of this document andare covered in a separate manual(RBI Oracle config.doc)...........................................................232.12 The database needs to be created from one server only. (DB creation procedure is given inseparate document). Database SID name given should be noted down, as it will be usedbeused later during Net8 service creation........................................................................................232.13 Creating virtual server through Cluster Administrator (Refer the document - RBI OracleConfig.doc)................................................................................................................................... 232.14 The database needs to be created through Oracle Database Configuration Assistant fromone node only. (The database SID given should be noted down, as it will be used later duringNet8 service creation.). The steps for creating oracle database in clustered mode are not a part ofthis document and are covered in a separate manual (RBI Oracle config.doc)............................232.15 Adding the cluster resource through Oracle FailSafe Manager (Refer the RBI Oracleconfig.doc).................................................................................................................................... 23

2.16 Install the Oracle ODBC driver 8.01.73.00............................................................................232.17 Create a Net Service Name using Oracle Net8 Assistant. It will ask for the followinginformation while creating the Service Name: ..............................................................................232.19 Net Service Name: Specify the service name to be created.................................................232.20 Host Name: Specify the IP Address of the Oracle server ...................................................232.21 (Logical IP Address allocated to Oracle DB).........................................232.22 Port Number: The installation will give default port number. ..............................................232.23 Service Name: Database name/service name/ SID name. from step (a) above...................232.25 The newly created service should be tested using a valid user name and password fromboth the servers (Note: During testing control of all the resources defined in MSCS which arerelated to Oracle should be owned by the respective nodeserver)...............................................232.27 e) Oracle 8 ODBC Driver Configuration ...............................................................................232.28 Theis configuration needs to be done on both the nodes:server....................................23

2.30 Go to............................................................................................................................... 232.31 Start Menu->Settings -> Control Panel -> Administrative Tools -> Data Sources (ODBC). .23



4/90




Version 1.0

2.32 and create a System DSN (Nnamed P1A) using installed Oracle driver (step b) to connectto the Oracle database. Provide the value for TNS Service Name (give the name of servicecreated in step c) &and Database user Id. This Database user Id should have read/writepermissions to the database. (Note: Also wWhile configuring the DSN set the property pre-fetchin tab Oracle count to 0, which is 10 by default) (tab - Oracle).....................................................232.34 For flat file generation aAdd the following parameter line to oracle parameter file which ispresent in your \..\Admin\\Pfile\init.ora on the common storage boxwhere the DB is residing. .............................................................................................................232.36 UTL_FILE_DIR = *..............................................................................................................232.38 Note : Oracle Fail over test should be done by your respective Oracle vendor............... .....232.41 IBM MQ Series NDS Member Server Installation.................................................................242.5 Enable sharing on j) the following folders: -............................................................................312.42 Database Setup.................................................................................................................... 33

2.43 PKI Implementation On Member Server ..............................................................................332.44 Adding System Path on NDS Member Server :....................................................................352.45 Change RBIPDONDS Com+ Property: ............................................................................... 362.46 Generation of Info.txt:...........................................................................................................372.47 Copying the Report Files on the disk:...................................................................................382.48 Database Creation and Migration Script:..............................................................................382.49 :392.50 Q Manager Setup:................................................................................................................ 442.51 Verification:........................................................................................................................... 51

Table of Contents

1. Introduction.................................................................................................................................... 6

1.1 Purpose of the Document.........................................................................................................61.2 Scope of the Document............................................................................................................... 6

1.3 Scope of the Document............................................................................................................... 6

1.4 Organization of the Document..................................................................................................72. Install Procedure for applying Patch on the Member Server ation Procedure...............................9

Procedure for installing the Member Server in Clustered mode.......................................................9

2.1 Pre-requisites for Software Installation.................................................................................... 92.2 Renaming and Backup of NDS Operating System Registry ....................................................9

2.3 onOn Server:............................................................................................................................ 92.4 The Operating System (OS) should be Windows 2000 Advanced Server..............................202.5 Windows 2000 service pack 2 should be installed..................................................................202.6 Deleting Com+ Component on Server....................................................................................202.7 Database Backup on Server:..................................................................................................21System Backup of Server (If possible) ........................................................................................222.8 Generation of Input file (.inp file) Oracle 8i Installation...........................................................222.10 Install Oracle 8i Enterprise Edition in clustered mode along with with Oracle Fail Safe(version. 3.1.2) installationapplication on both the servers nodes without creating creating adatabase. The steps for loading oracle in clustered mode ...........................................................232.11 (Please refer the separate document given along with) are not a part of this document andare covered in a separate manual(RBI Oracle config.doc)...........................................................232.12 The database needs to be created from one server only. (DB creation procedure is given in

separate document). Database SID name given should be noted down, as it will be usedbeused later during Net8 service creation........................................................................................23



5/90




Version 1.0

2.13 Creating virtual server through Cluster Administrator (Refer the document - RBI OracleConfig.doc)................................................................................................................................... 232.14 The database needs to be created through Oracle Database Configuration Assistant fromone node only. (The database SID given should be noted down, as it will be used later duringNet8 service creation.). The steps for creating oracle database in clustered mode are not a part ofthis document and are covered in a separate manual (RBI Oracle config.doc)............................232.15 Adding the cluster resource through Oracle FailSafe Manager (Refer the RBI Oracleconfig.doc).................................................................................................................................... 232.16 Install the Oracle ODBC driver 8.01.73.00............................................................................232.17 Create a Net Service Name using Oracle Net8 Assistant. It will ask for the followinginformation while creating the Service Name: ..............................................................................232.19 Net Service Name: Specify the service name to be created.................................................232.20 Host Name: Specify the IP Address of the Oracle server ...................................................23

2.21 (Logical IP Address allocated to Oracle DB).........................................232.22 Port Number: The installation will give default port number. ..............................................232.23 Service Name: Database name/service name/ SID name. from step (a) above...................232.25 The newly created service should be tested using a valid user name and password fromboth the servers (Note: During testing control of all the resources defined in MSCS which arerelated to Oracle should be owned by the respective nodeserver)...............................................232.27 e) Oracle 8 ODBC Driver Configuration ...............................................................................232.28 Theis configuration needs to be done on both the nodes:server....................................232.30 Go to............................................................................................................................... 232.31 Start Menu->Settings -> Control Panel -> Administrative Tools -> Data Sources (ODBC). .232.32 and create a System DSN (Nnamed P1A) using installed Oracle driver (step b) to connectto the Oracle database. Provide the value for TNS Service Name (give the name of servicecreated in step c) &and Database user Id. This Database user Id should have read/write

permissions to the database. (Note: Also wWhile configuring the DSN set the property pre-fetchin tab Oracle count to 0, which is 10 by default) (tab - Oracle).....................................................232.34 For flat file generation aAdd the following parameter line to oracle parameter file which ispresent in your \..\Admin\\Pfile\init.ora on the common storage boxwhere the DB is residing. .............................................................................................................232.36 UTL_FILE_DIR = *..............................................................................................................232.38 Note : Oracle Fail over test should be done by your respective Oracle vendor............... .....232.41 IBM MQ Series NDS Member Server Installation.................................................................242.5 Enable sharing on j) the following folders: -............................................................................312.42 Database Setup.................................................................................................................... 332.43 PKI Implementation On Member Server ..............................................................................332.44 Adding System Path on NDS Member Server :....................................................................352.45 Change RBIPDONDS Com+ Property: ............................................................................... 36

2.46 Generation of Info.txt:...........................................................................................................372.47 Copying the Report Files on the disk:...................................................................................382.48 Database Creation and Migration Script:..............................................................................382.49 :392.50 Q Manager Setup:................................................................................................................ 442.51 Verification:........................................................................................................................... 51



6/90




Version 1.0

1. Introduction

The Reserve Bank of India (RBI) through its Public Debt Offices (PDOs) administers and managesthe Internal debt, the Issue and servicing of new loans of the Central and State Governments. Toaccomplish the task of administration and management of internal debt, primarily Dated Securities,RBI has decentralised its operations through 15 PDOs established at 14 centres. Theadministration and management of Treasury Bills is centralised at Mumbai and is part of the PublicAccounts Department (PAD), Mumbai.

The PDO-NDS application, which encapsulates the above, needs of RBI and the 15 PDOs isdesigned & developed by TCS. caters to the needs of RBI and the 15 PDOs.

1.1 Purpose of the Document

The objective of the document isaims to provide the step-by-step necessary instructionsprocedureforNDSapplying revised broadcast architecture release at member end. Application Upgradation toVer. 2.7.45 (herein after referred as set upinstallation) on Member Server and MemberClientvarious operations for loading the of the PDO-NDS member end application in clusteredservermode. If it is fresh installation of NDS 2.7.5, follow the 2.7.4 installation document.Thisprocess documented here has been tested and a pilot site has been implemented on aCOMPAQ based hardware cluster.

1.2 Scope of the Document

This document provides the guidelines forfor applying software patch on member server fordeployment of the revised format of NDS Trade Data Message Broadcastpatch to NDS applicationon member server. We assumed that NDS application is on C:\ProgramFiles\ . If it is stored in D orE drive, then make the changes accordingly in the batch program.

1.3 Objective

The objective is to Rrevisedthe architecture forof message flow from Host end to member-end,segregating flow ofmessages s pertaining to trade watch and market watch from flow of messagespertaining to deals. Henceforth, tTrade messages would be sent to an intermediate broadcastserver, which is responsible in outsourcing of the trade details to the market participants.

rade messages will flow to member server through a dedicated server at Host end.1.3 Scope of the Document

This document will provides the guidelines for installingapplying patch to , uninstalling the NDSapplication on member sservererver and client machinessoftware in a clustered servermode alongwith the daily administrative activities &and activities needs to be performed in case of failure ofprimary serverprimary node in clustered environment. The functionality and usage instructions forvarious business modules (such as secondary market operations etc) are not a part of thisdocument and are covered in separate user manuals.

1. ItThiswill be is thesinduringthe following document. In case it is installed in a driveother than C: drive, please alter the path suitably during the course of thesetup.dDdDAppliactionapplicationS113NDS If the database name or the databaseuser id is different than as mentioned in the document below, please replace thedatabase name and database userid suitably during the course of the setup.



7/90




Version 1.0

2. It is assumed that d rive where the database is located will hav e disk space more than1 GB and the drive on which the application has been installed will have minimum500 MB free disk space.

3. While entering/ inputting the variable values, it may be done in higher case(CAUTION: the pass phrase/password to be given in actual case).

4. In case of NDS Cluster server installation, specific additional activity required to beundertaken is given at respective stage in red. Please ensure the completion of suchactivity.

1.4 Organization of the Document

Theis document is organized as follows:

Section 1 contains the Introduction part

Section 2 contains the Member Server Installation ProcedureSection 3 contains the Member Client Installation Procedure

Section 3 contains the Daily Startup and Shutdown operationsSection 4 contains the reference for Reverting NDS application to Old version. (NOTE: This optionis to be exercised only on specific instructions by RBI through NDS/Email/Telephone . Thissection is provided as separate document .)ther Operations



8/90




Version 1.0

Section 5 contains the Operations to be performed in case ofPrimary ServerPrimary node Failure



9/90




Version 1.0

2. Install Procedure for applying Patch on the MemberServer ation Procedure

This section provides the guidelines for installingapplyingand un-installing the software patch onPDONNDS application at the memberend.

It is assumed that NDS application is installed on drive C: of the NDS Server. In case theNDS application is installed on any other drive (e.g. D: or E:), then change the drive name inthe UNREG.bat file.(For changing the drive name in the batch file, select UNREG.bat file->Right click->Select Edit-

>Notepad. The batch file will open. In the batch file, replace drive C: with the desired name of driveat all places. Save the change and close the batch file).in a clustered servermode as well as the client (workstation).

Procedure for installing the Member Serverin Clustered mode

Pre-requisites for NDS Server Application Installation :

As precaution, please print Deal Report for Deals awaiting Dealer/ Settler Approval.

Log off the NDS Application .

Ensure that all the Messages ha ve been processed in MQ Series Queues.

(Current depth of all Queues except Query, input and Output log should be zero)

Stop all the Process es .

Perform EOD Operation.

Close the Host Connection window and Stop the MQ Series Queue Manager.

Kill DLLHOST.exe from Task manager.

Restart the NDS server.

2.1 Pre-requisites for Software Installation2.2 Renaming and Backup of NDS Operating System Registry2.3 on On Server:

2.1.1 Create folder BRDCST PatchNDSBackup_18102003160404NEWSMODLLS on ConC:\.

2.1.2 Copy the Zip NEWSMODLLS.ZIPfile to above created folder.

2.1.33Unregister following dllsComMsg_MS_SMO_dll.dllMS_SMO.dllExtract the Zip files on that folder itself.( NEWSMODLLS folder)

Go to Start RUN, type REGEDIT as shown in the following screen:

2.1.4 Ensure the following 4 files (3 dlls and 1 batch file) should be present in NEWSMODLLSfolder.

MS_SMO.dll,ComMsg_MS_SMO_dll.dllMC_Convert.dllUNREG.bat files.Rename following files in the folder C:\Program Files\RBIPDONDSSetUp\ServerDlls



10/90




Version 1.0

MC_Convert.dll to MC_Convert_old.dllComMsg_MS_SMO_dll.dll to ComMsg_MS_SMO_dll_old.dllMS_SMO.dll to Ms_SMO_old.dll

2.1.5 Extract zip to folder C:\Program Files\RBIPDONDSSetUp\ServerDlls2.1.6. Register following Dlls

ComMsg_MS_SMO_dll.dllMS_SMO.dll

2.1.75 Goto Start Settings Control Panel Administrative ToolsComponent

Services

Computers My Computer COM+ ApplicationsRBIPDONDSComponents .

Following screen will appear Computers My Computer COM+

ApplicationsRBIPDONDSComponents .Following screen will appear

2.3.1 Press Enter or Click on OK button, following screen will appear:



11/90




Version 1.0



12/90




Version 1.0

2.1.86 Right click on component MS_SMO.ComMS_SMOClass.1 as shown in figure below andclick Delete :



13/90




Version 1.0

2.1.97 Following dialog box will appear. Confirm delete by pressing Yes.

2.1.8 Double click on UNREG batch file from C:\NEWSMODLLS. This batch file willUunregister and , back up the old dlls and it will register the new SMO dlls.(ComMsg_MS_SMO_dll.DLL, & MS_SMO.dll).Please pPress OK button in response message box.

2.1.910 Right click on component in left hand side window as shown in figure Below:



14/90




Version 1.0

Then click NewComponent. Following screen will appear:



15/90




Version 1.0

Press Next Button.



16/90




Version 1.0

Click on first picture besides Install New Component. Then following screen will appear

Go to folder C:\Program Files\RBIPDONDSSetUp\ServerDlls and select MS_SMO.Dll andpress Open button. Following screen will appear:



17/90




Version 1.0

2.1.4 Go to My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\TCS as shown in the above figure

Press Next button. Then following screen will appear:



18/90




Version 1.0

Press Finish button.

2.1.5 Select TCS node and go to Registry Export Registry File as shown in figure givenbelow:



19/90




Version 1.0

The following screen will appear:



20/90




Version 1.0

2.1.6 Select the directory that you have created in Step 2.1(1) i.e.C:\NDSBackup_18102003160404 and type file name as shown in above screen. PressSave Button to save registry.

2.1.7 Similarly, take the back up of the following folder in registry: -My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL

2.1.8 Rename My Computers\HKEY_LOCAL_MACHINE\SOFTWARE\TCS toTCS_160404181003 as follows

Right Click on TCS Node and click on Rename

Rename TCS to TCS_16040418102003 and press enter

2.1.9 10. Rename My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL toMC_APPL_181003160404

Right Click on MC_APPL Node and click on Rename

Rename MC_APPL to MC_APPL _16040418102003 and press Enter

.

2.4 The Operating System (OS) should be Windows 2000 Advanced Server.2.5 Windows 2000 service pack 2 should be installed.

2.6 Deleting Com+ Com ponent on Server



21/90




Version 1.0

Existing Com+ component needs to be deleted as follows:

1. Go to Start Settings Control Panel Administrative Tools Component Services

Computers My Computer Com+ Applications RBIPDONDS

2. Right click on RBIPDONDS and press Delete

PLEASE ENSURE THAT ONLY RBIPDONDS IS DELETED.

2.7 Database Backup on Server :

Type the following command on DOS command prompt to take back up (Export dump) ofNDS UserS113NDS.

1. S113NDS EXP S113NDS /S113NDS@PDONDS FILE = C:\S113NDS.,S113.DMPFULL = Y2. For entire SystemEXP System /manager@PDONDS FILE =C:\FullDatabaseBkp,DMP

As a precautionary measure, if needed, you may copy the Export C:\S113.DMPsC:\UserS113NDS.DMP to any other machine or to Floppy/CD/Cartridge.

Rename the RBIPDONDSSetUp folder.



22/90




Version 1.0

Rename C\Program Files\RBIPDONDSSetUp to C\ProgramFiles\RBIPDONDSSetUp_160404

System Backup of Server (If possible)2.8 Generation of Input file (.inp file) Oracle 8i Installation

2.3.1 Create directory Generate on C:\2.3.2 Double Click on GenerateInputs.exe file on CDThe following screen will appear.

2.3.3 Input the following in the above scree n.

o Enter Member ID of yourbankinstitution/ban k (e.g. BYA00055)

o Enter LUD ID of your institution/bankbank in LUD ID field (e.g. A17 8 )

o All other fields are static and non-editable .

2.3.4 Select Input file location as C:\Generate as shown in the above screen2.3.4.1 Click Ok button to generate the input parameter file.

2.3.4.2 Check that .inp file exist in c:\Generate directory. This file will be used in NDS

application setup.application setup.


YourMemberID


23/90




Version 1.0

2.92.10 Install Oracle 8i Enterprise Edition in clustered mode along with with Oracle Fail Safe

(version. 3.1.2) installationapplication on both the servers nodes without creatingcreating a database. The steps for loading oracle in clustered mode

2.11 (Please refer the separate document given along with) are not a part of this documentand are covered in a separate manual(RBI Oracle config.doc).

2.12 The database needs to be created from one server only. (DB creation procedure isgiven in separate document). Database SID name given should be noted down, as itwill be usedbe used later during Net8 service creation.

2.13 Creating virtual server through Cluster Administrator ( Refer the document - RBI OracleConfig.doc)

2.14 The database needs to be created through Oracle Database Configuration Assistantfrom one node only. (The database SID given should be noted down, as it will be used

later during Net8 service creation.). The steps for creating oracle database in clusteredmode are not a part of this document and are covered in a separate manual (RBIOracle config.doc).

2.15 Adding the cluster resource through Oracle FailSafe Manager (Refer the RBI Oracleconfig.doc).

2.16 Install the Oracle ODBC driver 8.01.73.002.17 Create a Net Service Name using Oracle Net8 Assistant. It will ask for the following

information while creating the Service Name:2.182.19 Net Service Name: Specify the service name to be created2.20 Host Name: Specify the IP Address of the Oracle server2.21 (Logical IP Address allocated to Oracle DB).2.22 Port Number: The installation will give default port number.

2.23 Service Name: Database name/service name/ SID name. from step (a) above.2.242.25 The newly created service should be tested using a valid user name and password

from both the servers (Note: During testing control of all the resources defined inMSCS which are related to Oracle should be owned by the respective nodeserver).

2.262.27 e) Oracle 8 ODBC Driver Configuration2.28 Theis configuration needs to be done on both the nodes:server.2.292.30 Go to2.31 Start Menu->Settings -> Control Panel -> Administrative Tools -> Data Sources

(ODBC)2.32 and create a System DSN (Nnamed P1A) using installed Oracle driver (step b) to

connect to the Oracle database. Provide the value for TNS Service Name (give thename of service created in step c) &and Database user Id. This Database user Idshould have read/write permissions to the database. (Note: Also wWhile configuringthe DSN set the property pre-fetch in tab Oracle count to 0, which is 10 by default) (tab- Oracle).

2.332.34 For flat file generation aAdd the following parameterline to oracle parameter file which

is present in your\..\Admin\\Pfile\init.ora on the commonstorage box where the DB is residing.

2.352.36 UTL_FILE_DIR = *2.372.38 Note : Oracle Fail over test should be done by your respective Oracle vendor.

2.392.40



24/90




Version 1.0

2.41 IBM MQ Series NDS Member Server Installation

2.4.1 Double click on Setup.exe on CD located in Folder Drive name:\MemberEnd\Setup. Following screen will appear

2.4.2 b) Click Ok button. Following screen will appear :



25/90




Version 1.0

2.4.3 Check the Install User Interface Application check box as shown in above screen. Keepthe Fresh Installation selected, as shown above.

2.4.4 Select .inp file, which you created in 2.1.5, by clicking on three dot buttons shown in redcircle in above screen. The following screen will appear:

2.4.5 Select .inp file created in C:\Generate folder and Click Open button.



26/90




Version 1.0

2.4.6 Now press Ok button in the following screen.

2.4.7 In the following screen, click on the computer picture s button to start the installation

2.4.8 ghFollowing screen will appear:

The existing user id is NDS but to protect your database against any modification duringinstallation, use different user id RBI as shown in the following figure.



27/90




Version 1.0

Enter the values same as shown in the above screen. Password value is RBINDS. ClickPress to submit the same..

Note: In case of different database name (other than PDONDS), enter that databasename as an input to the DB Server Name filed in the above screen.

2.4.9 hiClick Continue in the following screen:



28/90




Version 1.0

2.4.10 iAgain click Continue in the following screen:



29/90




Version 1.0

2.4.11jkThe following screen will appear

2.4.12 DOS screen will appear as shown below. Close it by clicking on the X button at the topright corner.



30/90




Version 1.0

2.4.12 The next screen will be as shown below. lClickk OK

2.4.13 mlThe screen showing completion of Installation will appear as follows. Press OK.



31/90




Version 1.0

2.4.14 Open C:\Program Files\RBIPDONDSSetUp folder, rename

PDONDS_MEMBER.exe as PDONDS_MEMBER_ORI.

2.4.15 Copy PDONDS_MEMBER.exe from CD and paste it in C:\ProgramFiles\RBIPDONDSSetUp folder.

2.5 Enable sharing onj) the following folders : -

ServerDlls folder in C:\Program Files\RBIPDONDSSetUp

MQSeries folder wherever installed on Server . In most cases, it is in C:\Program

Files\IBM folder. In case if you do not know the exact location of MQSeries folder, it canbe searched in local hard drives.

You can share the folder by right clicking on it in Windows Explorer and selecting Sharing.Select option Share this folder as shown below: -



32/90




Version 1.0

Click on OK to make the folder sharing.

2.5.1 Go to Start RUN, type REGEDIT as shown in the following screen:

2.5.2 Press Enter or Click on OK button, following screen will appear:



33/90




Version 1.0

2.5.3 Rename My Computers\HKEY_LOCAL_MACHINE\SOFTWARE\TCS to TCS_ORI asfollows


Rename TCS to TCS_ ORI and press enter

2.5.4 Rename My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL to MC_APPL_ORI


Rename MC_APPL to MC_APPL _ORI and press Enter

2.5.5 Select the directory that you have created in Step 2.1(1) i.e. C:\NDSBackup_160404

Double Click on TCS registry file.

Double Click on MC_APPL registry file.

2.42 Database Setup2.43 PKI Implementation On Member Server

1. Double click the file RegNewCert.reg present in the PKI Implementation folder on CD.The following message will pop up.



34/90




Version 1.0

Click on Yes.

2. Open the Registry Editor and check that the value data of the following keys (Registry Name) is04CC.

StartRun and then type Regedit

My Computer/HKEY_LOCAL_MACHINE/SOFTWARE/TCS/RBI-PDO/ SERIAL_NO

My Computer/HKEY_LOCAL_MACHINE/SOFTWARE/TCS/RBI-PDO/

SECURITY/SERIAL_NO

3. Setting the Password Phrase in the registry:

Run the utility.exe by double clicking it (this will be present available in the folder

PKI Implementation on CD).

Now select the Radio Button for Set Pass phrase (as displayed in following

Screen Shot) and type the pass phrase in the textbox labeled as Own Pass Phrase.(Refer the following Screen Shot)

Press Ok button to save it (Please ensure that you enter the exact pass

phrase, which you had given while generating the private key and request file.Also ensure that you enter the pass phrase in the correct case, as it is casesensitive).

The following message will pop up after clicking on OK.



35/90




Version 1.0

Click OK.

After making the Registry Entries Successfully, Click Cancel button to close theWindow.

Note: It is assumed that Certificate Folder is present on C:\

2.44 Adding System Path on NDS Member Server : ( If System path is already existing in environment variables, do not follow the belowprocedure):

Add the path C:\Program Files\RBIPDONDSSetUp\ServerDlls to system path as shownbelow: -

2.6.1. My ComputersRight ClickPropertiesAdvancedEnvironment VariablesSystem

variablesPath.



36/90




Version 1.0

2.6.2. Click on Edit Button and the following screen will appear.the against the

2.6.3. Press End to go to the end of the string in the variable value. Append the following string asit is

C:\Program Files\RBIPDONDSSetUp\ServerDlls2.6.44. Check that the existing path i.e. the variable value is not changed but is only appended withthe abovementioned text.2.6.55. Click OK.2.6.6. Click OK again in the screen of Environment Variables.2.6.7. Click OK again in the screen of System Properties.

2.45 Change RBIPDONDS Com+ Property :

In Component Services, go to Properties of the installed RBIPDONDS application

(Start Settings Control Panel Administrative ToolsComponent Services Computers

My Computer COM+ ApplicationsRBIPDONDSRight ClickProperties Advanced) and change the Minutes until idle shutdown property to 1440 as shownbelow:



37/90




Version 1.0

Click on OK.Then close the Component Services window.

2.46 Generation of Info.txt :

Go to StartPrograms PDONDS Server AdministratorGetApplicationIDSFollowing screen will appear

Please enter the following values in the corresponding fields:i. Application Name :- RBIPDONDSii. Full Path of Config file with Name as info.txt Type the following text as it is

C:\Program files\RBIPDONDSSETUP\info.txt (please ensure that there is no space orspecial characters in this field)



38/90




Version 1.0

iii. Server Name Please enter the IP address of NDS Member Server.

After entering all these values click on OK. Following screen will appear:

Click on Ok. Click on Cancel in the next screen to exit the application.

2.47 Copying the Report Files on the disk:

Copy Reports folder from the C:\Program Files\RBIPDONDSSetup_160404\CD toC:\Program Files\RBIPDONdsDSSetup\

2.48 Database Creation and Migration Script :shouldare be

1. Copy the file mem_ins.dmp from the CD to C:\

2. Rename the folderMemberEndUpdates located at C:\Program Files\RBIPDONdsSetup toMemberEndUpdatesOld

3. Copy the folder MemberEndUpdates from the CD to C:\ProgramFiles\RBIPDONdsSetup.

4. If the user name of the P1A Oracle database is not S113 then edit the fileDB_MIGRATION.BAT located in the following folder: -

C:\Program Files\RBIPDONdsSetup\MemberEndUpdates

to replace S113 with the NDS database user id on your server.

Important:

[Following additional Steps to be followed on the Cluster server installationonly.Perform the database migration from one of the nodes only. This step has to be carried outafter the application is installed on both the nodes of cluster server.First edit the Createuser.sql file located at C:\ProgramFiles\RBIPDONDSSetUp\MemberEndUpdates. Provide the absolute path of the datafile in thestatement Create tablespace NDS..

E.G. CREATE TABLESPACE NDS DATAFILE 'I:\OraHome1\oradata\PDONDS\NDS.dbf' SIZE1024M reuse DEFAULT STORAGE ( INITIAL 50K NEXT 50K MINEXTENTS 5 MAXEXTENTSUNLIMITED PCTINCREASE 0);

After making this change, save the file at the same location and then proceed for the databasemigration as per point number 5. ]

5. Open the command prompt and go to the location C:\ProgramFiles\RBIPDONdsSetup\MemberEndUpdates and type the following commandDB_MIGRATION



39/90




Version 1.0

e.g. DB_MIGRATION PDONDS6. This command will migrate the P1A database to P1B. At one stage , it will ask the user to

provide the password for the Oracle System user. Please input the correct password.

7. Note that this activity will take some time to complete. Wait for some time.

8. At the end it will prompt the message Migration completed successfully. This will end thedatabase migration.

2.49 : (If in System DSN the name is NDS and Driver is

Oracle in OraHome92 is present , then do not follow the procedure given below)2.10.Source(Source (screen willscreen will:



40/90




Version 1.0

2.10.8192 and and.:



41/90




Version 1.0



42/90




Version 1.0

2.10.:



43/90




Version 1.0

2.10.figurescreen

2.10.CYou can cthe vityvity button.



44/90




Version 1.0

. the the .2.10.Click on OK. Once again Click on OK in ODBC Data Source Administrationwindow.

Press Ok to exit the above screen.

2.11 Importing Codeval and Operation table on PDONDS database.

2.11.1 Please execute the following queries on your SQL prompt (UserName :NDSPassword:NDS Host String : PDONDS)

a) RENAME M_CODEVAL_T TO M_CODEVAL_T_160404;b) RENAME M_OPERATION_T TO M_OPERATION_T_160404;

2.11.2 Copy CODE_OPER.dmp from CD and paste it to your C drive.

2.11.3 Type the following command on DOS command prompt to import the dump.

IMP NDS/NDS@PDONDS FILE='C:\CODE_OPER.DMP' FULL=Y

2.50 Q Manager Setup :



45/90




Version 1.0

1. Go to MQ Series Explorer and check whether Q ManagerNDS1P.LUDID.QMGR is created or not.

2. If Q manager is not created during Set up, create it fromDos prompt .

Go to StartRUN and Type CMD , press enter to go toDOS prompt

3. Change the directory to C:\ProgramFiles\RBIPDONDSSetUp\StartUp and executeMqsetUp.bat file from DOS prompt as shown below:

C:\Program Files\RBIPDONDSSetUp\StartUp> MQSetUp.bat

RBICRTMQOBJ.in



46/90




Version 1.0

4. Wait till command prompt appears again. The display onthe screen will be seen as follows

5. Go to MQ Series ExplorerStartPrograms IBM MQSeriesMQSeries Explorer

Open MQ Series Services (NDS1P.LUDID.QMGR (Right

Click) All Tasks Services)and do the following:

Note: 1. Do not use SSS1P. LUDID.QMGR. Use the newlycreated Q Manager

NDS1P.LUDID.QMGR



47/90




Version 1.0

2. LUDID refers to your bank lud id. (e.g. A138)

i. Add a listener to your queue manager.

(NDS1P.LUDID.QMGR (Right Click) New Listener)After adding the service listener, enter the port value1414, Click on OK as shown in the following screen.

ii. Add channel initiator.

(NDS1P.LUDID.QMGR (Right Click) New ChannelInitiator)

After adding the service channel initiator, enter theinitiation queue as SYSTEM.CHANNEL.INITQ under theparameter by selecting the properties of channel initiatorservice as shown in the below screen:



48/90




Version 1.0

Click on OK

iii. In MQ Service window, Click on the properties of

Queue Manager (NDS1P.LUDID.QMGR (Right Click)

Properties Click Channels Tab Put the tick-markin front of AdoptNewMca (ALL) and

AdoptNewMCACheck (ALL) as shown in followingscreen



49/90




Version 1.0

Click on OK.

6. In MQ Series explorer, set the sender channel disconnect

interval to 0 (NDS1P.LUDID.QMGR Advanced

ChannelsSender ChannelRight

ClickPropertiesExtended tab->Disconnect Interval field)and click on OK

Important:

[Following steps to be followed on the Cluster serverinstallation only. This step has to be carried out after theapplication is installed on both the nodes of clusterserver.



50/90




Version 1.0

1. Install the Q manager on only one of the nodes of thecluster serverand then move it to the common storagebox as follows.

2. Move the Queue manager NDS1P.LUDID.QMGR to thevirtual drive say J. (This is the logical drive on thecluster box. If you have decided to choose any otherdrive letter, move the queue to that drive). To move the

queue you have to run the following command from thecommand prompt.

hamvmqm /m qmname /dd J:\mqseries /ldJ:\mqseries\logs where qmname will beyourqueue manager name (e.g. NDS1P.LUDID.QMGR) andJ: is your shared disk drive letter mqseries andmqseries\logs are folders that will be automatically created.

3. Upon successful completion of this step you will bereturned back to the command prompt without errors.

4. Now start the windows cluster administrator.5.Add a resource to the Mqseries group (The group in

which your previous Q manager resides i.e.SSS1P.LUDID.QMGR)

6. Select the resource type as IBM MQ Series for MSCS7. The resource name should be the same as the name of

the Queue Manager created by us(NDS1P.LUDID.QMGR)

8. NOW The MQSeries Explorer on both the nodes willshow the queue managerNDS1P.LUDID.QMGR (activeon N1 and passive on N2)]



51/90




Version 1.0

Imp Note: With this installation, you have successfullyinstalled NDS Server and NDS Member Client on servermachine. No separate NDS Client installation is requiredon server.

2.51 Verification :

Stop the NDS1P.LUID.QMGR and start again.

Minimize the MQ Series explorer and Servicewindows.

You will not able to login to NDS by using old

NDS application icons (Sshort Ccuts).

BOD / Connect to RBI: StartProgramsPDONDS

Server Administrator Server Admin GUI.Logging into NDS application:

Start

Programs

PDONDS Application -Member Member

Regular Log in screen will appear. Enter the user

name and password as usual.

Password ofuser ADMIN is reset to admin( note

the small case letters of the password).

All other NDS operations will remain same.

Log in NDS application with user id ADMIN

(password: admin) and do yield calculation. Place a call over NDS to RBI Central PDO.

The yield calculation and the call placement verifiessuccessful setup.



52/90




Version 1.0

Procedure forinstallingapplying patch on the Member Client:

Please refer the steps given in a separate document (RBI-Mq configdoc.doc) to Install the IBM MQSeries application & creating queue manager, queues & channels required for NDS application.Server

5.1/5.2 on both the Server Machines. ( Please refer the separate document given along with)Pre-requisites for NDS Client Application Installation:

Log off from NDS Application and close all the applications.Restart the NDS Client machine.

Copying and Registering Dll3.2 1.MSMQ Disconnecting the mapped drive:

Unregister ComMsg_MS_SMO_dll.dll.

There Rename ComMsg_MS_SMO_dll.dll in C:\Program Files\RBIPDONDSSetUp\ClientDlls could be

two mapped drives on your client machine. One drive to ServerDlls folder of the server machine andanother to MQSeries/bin folder of the server machine. You can disconnect ServerDlls folder mapped

to your old Member sever by right clicking on mapped drive in windows explorer and click onDisconnect as shown in below screen:

Copy ComMsg_MS_SMO_dll.dll to C:\Program Files\RBIPDONDSSetUp\ClientDlls

Register ComMsg_MS_SMO_dll.dll .



53/90




Version 1.0

In case the folders are not mapped, skip this step.

3.2.1 Map a drive from client machine to the ServerDlls folder of Member Server. The path on theMember server is C:\Program Files\RBIPDONDSSetUp\ServerDlls. You can map the drive as follows:

3.2.2.a. Open Windows Explorer window and Click on Tools-> Map Network Drive .The following

screen will appear:



54/90




Version 1.0

(Note: Drive Letter E: may be different in your case).

3.2.32.b.Click on Browse button and select Member Server then ServerDlls folder as shown in thescreen.

Note: Your Server Name may be different. Select your server name and then ServerDlls which isshared on Server.

Click on OK and then Finish on Map Network Drive window.

3.3. Following procedure will map the MQSeries\Bin Folder:



55/90




Version 1.0

(This would have already been done in most NDS members client machines. So please verify, if itsalready mapped, you may skip this step. You can check mapped network drives in My Computer

in Windows Explorer window)

Map the Bin Folder as follows:3.3.1a) Share the MQSeries folder on NDS server machine (which might have already been done).

3.3.2b) Open windows explorer window and Click on ToolsMap Network Drive (The drive will beselected by default as shown in the following Map Network Drive screen) window:



56/90




Version 1.0

Please note down the drive name. It is required in later steps

c)3.3.3. Click on browse button to select MQSeries\bin folder from NDS server. Refer the followingscreen: (In screen select NDS server Name then MQSeries\Bin folder as shown below)

Click on OK and the Finish in Map Network Drive screen.

3.3.4d). Now add the path of mapped bin folder to the System path of your client machine. You can add

the path as follows,

My Computers Right Click Properties Advanced Environment Variables System

variables Path.



57/90




Version 1.0

3.3.5e). Press Edit Button, following screen will appear.

Press End to go to the end of the string in the variable value.

Append the path E:\;E:\bin in the field Variable Value: as shown in above and click

OK. (Please give the drive name correctly; in your case the drive letter could be different if you

have mapped the MQ Series\Bin folder to some other drive.)

Check that the existing path i.e. the variable value is not changed but is only

appended.Click OK.

Click OK again in the screen of Environment Variables.

3.44. Mapping of MQ Series\Bin and ServerDlls:



58/90




Version 1.0

Check that both the mapping of MQ series/bin folder and ServerDlls on Member server. If the mapping

was disconnected, please map it again.

(Go to Windows Explorer, in My Computer there should be ServerDlls on .. and Bin on . .This will appear along with various drives in My Computer)

3.5. Register the Server Dlls:Access the mapped ServerDlls folder of the NDS Server by clicking on it in Windows explorer.

Register the following dlls by double clicking them (Some dlls may take few seconds to get registered).

i. GnrtEvnt.dll

ii. MC_COM_UTIL.dll

iii. MS_AppSupport.dlliv. MS_Instru.dllv. MS_Mmbr.dll

vi. MS_PMO.dllvii. MS_Serv.dll

viii. MS_Settle.dllix MS_SMO.dll

For Example, suppose E drive of the client machine is mapped to the ServerDlls folder of Member

Server, then on registering GnrtEvnt.dll( i.e. Double clicking on the GnrtEvnt.dll) you should get thefollowing message. The same way you can register all the dlls.

If following window appears when you Double click on first DLL:



59/90




Version 1.0

Then check the Check Box Always use this program to open these files and press Other toselect Regsvr32.exe from C:\WinNT\System32 as shown in the figure below

Press Open Button and then press Ok button in previous window.

Then register remaining Dlls by double clicking on each individually as stated above.Renaming and Backup of NDS Registry on Client:

3.6.1. Create folder NDSBackup_160404 on C:\.

3.6.2. Go to Start

RUN, type REGEDIT as shown in the following screen:



60/90




Version 1.0

Press Enter or Click on OK button, following screen will appear:

3.6.3 Go to My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\TCS as shown in the above figure

3.6.4 Select TCS node and go to Registry Export Registry File as shown in figure given below:



61/90




Version 1.0




62/90




Version 1.0

3.6.5 Select the directory that you have created i.e. C:\NDSBackup_160404 and type file name as

shown in above screen. Press Save Button to save registry.

3.6.6 Similarly, take the back up of the following folder in registry: -My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL

3.6.7 Rename My Computers\HKEY_LOCAL_MACHINE\SOFTWARE\TCS to TCS_160404 as

follows

Right Click on TCS Node and click on RenameRename TCS to TCS_160404 and press enter

3.6.8 RenameMy Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL to MC_APPL_160404


Rename MC_APPL to MC_APPL _160404 and press Enter

Create folder NDSBackup_18102003 on C:\.

Go to Start RUN, type REGEDIT as shown in the following screen:



63/90




Version 1.0

Press Enter or Click on OK button, following screen will appear:

Go to My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\TCS as shown in the above figure

Select TCS node and go to Registry Export Registry File as shown in below figure:



64/90




Version 1.0




65/90




Version 1.0

Select the directory that you have created in Step 3.2(1) i.e. C:\NDSBackup_18102003and type file

name as shown in above screen. Press Save Button to save registry.

Similarly, take the back up of the following folder in registry: -My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL

Rename My Computers\HKEY_LOCAL_MACHINE\SOFTWARE\TCS to TCS_181003 as follows


Rename TCS to TCS_18102003 and press enter

10. Rename My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL to MC_APPL_181003

Right Click on MC_APPL Node and click on RenameRename MC_APPL to MC_APPL _18102003 and press Enter.

`

:NDS Member Client Installation

3.7.1 Double click on Setup.exe on CD located in Folder Drive name:\Member End\Setup. Following

screen will appear :



66/90




Version 1.0

3.7.2 Click OK in above screen, then following screen will appear

3.7.3 Select the option button Client Setup, shown in the red circle in the above screen. Select the Input

file from server (.inp) kept in C:\Generate folder on NDS Server.



67/90




Version 1.0

3.7.4 Click on Ok button in the above screen, then following screen will appear:

3.7.5 Click the computer picture button shown in the above screen:



68/90




Version 1.0

3.7.6 Click on Continue button.

3.7.7 Click on Continue button again.



69/90




Version 1.0

The following screen will appear :

3.7.8 10. Wait till progress bar reaches to 100%. Then following screen will appear:

3.7.9 11. Enter the values as shown in the above figure. The input to Password is NDS.

Note: In case database name is other than PDONDS, please enter it in DB Server Name.



70/90




Version 1.0

3.7.10 12. Click on Ok button, the following screen will appear:

Click on OK.Install MSMQ as below:

i. Click on Add/Remove Windows Components (Control panel / AddRemove Programs)ii. Follow wizard for installation. Tick the checkbox Message Queuing Services.

iii. IfWhen prompted for message queuing type, select Independent client.iv. IfWhen prompted for Message Queuing Server, select the option Message queuing will not access

a directory servicev. Keep on cClicking next till you reach Finish.

Note: During iInstallation may ask forof Windows 2000 Advanced Server in the .

: Startup Type for Message Queuing service needs to be definedselect as

an AutomaticAutomatic on both theserversNodes..

Open C:\Program Files\RBIPDONDSSetUp folder,rename PDONDS_MEMBER.exe as



71/90




Version 1.0

PDONDS_MEMBER_ORI.

Copy PDONDS_MEMBER.exe from CD and paste it in

C:\Program Files\RBIPDONDSSetUp folder.

Application Installation

PDONDS Application needs to be installed on both the Servers nodes without running MQSeries Q-Manager creation part.

Before starting the application installation, ensure the following information is available (to be obtained

from RBI):

LUD Id (a four character value)Member Id (an eight character value)Prefix to be used for Queue manager, local and remote queue names (e.g. SSS1P)

Host IP Address

a) Run the setup.exe for installing RBIPDONDS Member Server application from the RBIPDONDSServer CD (root directory on CD). The setup will ask for the destination directory for installing the

application (please note down the destination directory you specified for future reference) followed bythe following information:

Database Information

DB Server Name: This is the name of the service created in step 2.1.2 step 2.1.2(f) (d).

DSN: This is the DSN name created in step 2.1.2 step 2.1 (e)..2(g).

DB User ID/Password: User Id and password that the PDO-NDS application will use for connecting to

the member-end oracle database.

Member Information

LUD ID: LUD ID assigned to the member.

Member ID: Member ID assigned to the member by RBI.

QM Name: Specify the prefix to be used for queue manager and queue names (e.g. SSS1P).

Host IP address: The IP address of the host server.

Trace File Path: User Sspecify theied location whereof T trace folder. It should be files will becreated on the Memberlocated on common storage box (select any drive).Server



72/90




Version 1.0

Member end Database objects creation: This step needs to be executed from one Server only.

Depending on the stage of installation you need to run step I or II only.

This step This step needs toshould not be performed if you already have created a database during an

earlier installation of PDO-NDS software on standalone machine.

In this case, Take user (eg. S113) specific export dump needs to be takenfrom the existing member

server. & imported it in the clustered server from one of the server which is currently holding theownership of group (this group holds all the resources related to Oracle) defined in MSCS.Login to

the DB using userid & password system/manager through SQL*PLUS utility & execute the following

scripts from one the node in clustered server, which holds the ownership of Oracle & MQSeriesresources defined in MSCS.

SQL>Create tablespace s113 datafile I:\Oracle\oradata\PDONDS\s113_1.dbf size 100M;

SQL>create user s113 identified by s113;

SQL>grant dba,resource,connect to s113;

SQL>alter user s113 default tablespace s113;

SQL> exit;

(In above-mentioned queries we have used userid as S113, drive for Oracle DB on common storage boxis I & size 100M. In your case all these parameters may differ depending on space / database load.

Please confirm the same with your oracle DBA).

Import the export dump in clustered server from the node, which is currently holding the ownership ofOracle & MQ resources defined in MSCS.

This step needs to be performedonly if you are loading the PDO-NDS softwarefirst time.

Run the Member.bat file included in the DBSetup subdirectory of the destination directory specified in

Step 2.1.5(a) from the node,Server, which is currently holding the ownership of the Oracle &andMQSeries resources defined in MSCS.

The command is:

DOS> member.bat service_name

The service name should be the name of the service created in earlier step.The following information should be entered when asked for:

Tablespace: (specify the database user ID as specified in earlier step)

Service name: (specify the name of the service created in earlier step)

Member ID: (8 character member ID should be entered)

Lud ID: (4 character LUD ID should be entered).

Follow the steps given below to create MQSeries Q Manager, Channel&Go to DOS command prompt

Go to directory C:\Program Files\RBIPDOServerSetup & run the following command

C:\Program Files\RBIPDOServerSetup> MQNEWSETUP.bat NEWMQOBJ.in



73/90




Version 1.0

Add the MQSeries services fter executing this command successfully, perasform the follows from the

node which is holding the ownershipof MQSeries resources defined in MSCSing steps,

Open MQ Series Services (QMGR -> (Right Click) All Tasks -> Services) and do the following:

i. Add a listener to your queue manager.(QMGR -> (Right Click) New -> Listener)

After adding the service listener, enter the port value 1414 under the option parameter by selecting the

properties of listener service.

ii. Add channel initiator.

(QMGR -> (Right Click) New -> Channel Initiator)After adding the service channel initiator, enter the initiation queue as SYSTEM.CHANNEL.INITQunder the parameter by selecting the properties of channel initiator service.

iii. Adding a channel . channel.

(QMGR -> (Right Click) New -> Channel)After adding the service channel, enter the channel name as SSS1P.LH.LUDID (This is a name of your

sender channel, LUDID Your LUD ID) by selecting the option parameteroption parameter.

iv.Clickiv. Click on the properties of Queue Manager Click Channel Put the tick-mark in front of

AdoptNewMca (ALL) &and AdoptNewMCACheck (ALL)

In MQ Series explorer, set the sender channel disconnect interval to 0 (QMGR-> Advanced-> Channels-

>Sender Channel->RightCLick->Properties->Extended tab->Disconnect Interval field).

After performing steps c & d, to get the access of Q manager, Channels & Queues from the other

server, move them to common storage box using the procedure listed in the document given separately.

Include the /ServerDlls &and /Startup directorypaths in the Environment Variable path (Control Panel/ System/ Advanced/ Environment Variables/Path)

on both nodes. Destination directory is as specified during setup step2.1.5 (a). This step needs to be executed on both the Server

In Component Services on both nodes, go to Properties of the installed RBIPDONDS application (StartMenu-> Settings-> Control Panel-> Administrative Tools-> Component Services-> Computers-> My

Computer-> COM+ Applications->RBIPDONDS-> Right Click -> Properties -> Advanced) and change

the Minutes until idle shutdown property to 1440 as shown below:

.

In Component Services, go to Properties of the installed RBIPDONDS application

(Start Menu-> Settings-> Control Panel-> Administrative Tools-> Component Services-> Computers->My Computer-> COM+ Applications->RBIPDONDS-> Right Click ->

Properties -> Advanced)and change the Minutes until idle shutdown property to 1440 as shown below:



74/90




Version 1.0

Setting the Minutes until idle shutdown property of the COM+ packageRunning ClientCom+:

3.8.11. Copy info.txt file from server to client machine (this file needs to be created first on the server

machine). You will find this file in thepath C:\Program Files\RBIPDONDSSETUP on the server.

Paste the info.txt into the C:\Program Files\RBIPDONDSSETUP folder of the client machine.

3.8.2. Go to Start ProgramsPDONDS Client AdministrationClient Com+.

On clicking this, the client COM+ screen would be opened.



75/90




Version 1.0

3.8.3 Click the OK button.

You should get a message Registry entries done.

Then click on Cancel to exit the application.

Copying the Report Files from CD to the client machine:

Copy Reports folder from the CD to C:\Program Files\RBIPDONdsSetup\

System DSN Configuration:

System DSN Configuration:

(If in System DSN the name is NDS and Driver is Oracle in OraHome92 is present , then do

not follow the procedure given below)

3.9.1. Go to Start Settings Control Panel Administrative Tools Data Source (ODBC)

System DSN. Following screen will appear:



76/90




Version 1.0

Press Add button in above screen.

3.9.2. Following screen will appear. Select Driver Oracle OraHome 92 and Press Finish in followingscreen:



77/90




Version 1.0

3.9.3. The screen shown below will appear:



78/90




Version 1.0

3.9.4. Enter the values as shown in above screen:

Data Source Name: NDSTNS

Documents

Revised Trade Message Broadcast Architecture