Revised Trade Message Broadcast Architecture

RESERVE BANK OF INDIA
PDO-NDS COMPUTERISATION PROJECT UpgradationSetup and Operations ManualInstallationRevised Broadcast Architecture Release Manual PDO-PDONNDS Application Version 2.7.54For Clustereed Server
(Member End)
Manual Version: 1.0 Prepared by
July AugustOctober 2003APRILJullyne 20042
PDO-NDS Ver. 2.7.42.7.5Server - USetup and Operations ManualpgradationInstallation Manual Version 1.0PDONDS Application For Clustereed ModeServer
PDO-NDS Computerisation Project
Version 1.0
Confidential and controlled document. Unauthorised access or copying is prohibited.
Tata Consultancy Services
Uncontrolled when printed
Page 2 of 81541
Version 1.0
Table of Contents
1. Introduction.................................................................................................................................... 6 1.1 Purpose of the Document......................................................................................................... 6 1.2 Scope of the Document............................................................................................................... 6 1.3 Scope of the Document............................................................................................................... 6 1.4 Organization of the Document.................................................................................................. 7 2. 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....................................................................................9 2.2 Renaming and Backup of NDS Operating System Registry ....................................................9 2.3 onOn Server:............................................................................................................................ 9 2.4 The Operating System (OS) should be Windows 2000 Advanced Server..............................20 2.5 Windows 2000 service pack 2 should be installed..................................................................20 2.6 Deleting Com+ Component on Server....................................................................................20 2.7 Database Backup on Server:.................................................................................................. 21 System Backup of Server (If possible) ........................................................................................ 22 2.8 Generation of Input file (.inp file) Oracle 8i Installation...........................................................22 2.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 a database. 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 and are covered in a separate manual(RBI Oracle config.doc)...........................................................23 2.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 usedbe used later during Net8 service creation........................................................................................23 2.13 Creating virtual server through Cluster Administrator (Refer the document - RBI Oracle Config.doc)................................................................................................................................... 23 2.14 The database needs to be created through Oracle Database Configuration Assistant from 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 clustered mode are not a part of this document and are covered in a separate manual (RBI Oracle config.doc)............................23 2.15 Adding the cluster resource through Oracle FailSafe Manager (Refer the RBI Oracle config.doc).................................................................................................................................... 23 2.16 Install the Oracle ODBC driver 8.01.73.00............................................................................23 2.17 Create a Net Service Name using Oracle Net8 Assistant. It will ask for the following information while creating the Service Name: ..............................................................................23 2.19 Net Service Name: Specify the service name to be created.................................................23 2.20 Host Name: Specify the IP Address of the Oracle server ...................................................23 2.21 (Logical IP Address allocated to Oracle DB).........................................23 2.22 Port Number: The installation will give default port number. ..............................................23 2.23 Service Name: Database name/service name/ SID name. from step (a) above...................23 2.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 in MSCS which are related to Oracle should be owned by the respective nodeserver)...............................................23 2.27 e) Oracle 8 ODBC Driver Configuration ...............................................................................23 2.28 Theis configuration needs to be done on both the nodes:server....................................23 2.30 Go to............................................................................................................................... 23 2.31 Start Menu->Settings -> Control Panel -> Administrative Tools -> Data Sources (ODBC). .23
Page 3 of 81541
Version 1.0
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 the name of service created 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-fetch in tab Oracle count to 0, which is 10 by default) (tab - Oracle).....................................................23 2.34 For flat file generation aAdd the following parameter line to oracle parameter file which is present in your <o Oracle\racle home>\..\Admin\<SID>\Pfile\init.ora on the common storage box where the DB is residing. ............................................................................................................. 23 2.36 UTL_FILE_DIR = *.............................................................................................................. 23 2.38 Note : Oracle Fail over test should be done by your respective Oracle vendor....................23 2.41 IBM MQ Series NDS Member Server Installation.................................................................24 2.5 Enable sharing on j) the following folders: -............................................................................31 2.42 Database Setup.................................................................................................................... 33 2.43 PKI Implementation On Member Server ..............................................................................33 2.44 Adding System Path on NDS Member Server :....................................................................35 2.45 Change RBIPDONDS Com+ Property: ...............................................................................36 2.46 Generation of Info.txt:........................................................................................................... 37 2.47 Copying the Report Files on the disk:...................................................................................38 2.48 Database Creation and Migration Script:..............................................................................38 2.49 :39 2.50 Q Manager Setup:................................................................................................................ 44 2.51 Verification:........................................................................................................................... 51
Table of Contents
1. Introduction.................................................................................................................................... 6 1.1 Purpose of the Document......................................................................................................... 6 1.2 Scope of the Document............................................................................................................... 6 1.3 Scope of the Document............................................................................................................... 6 1.4 Organization of the Document.................................................................................................. 7 2. 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....................................................................................9 2.2 Renaming and Backup of NDS Operating System Registry ....................................................9 2.3 onOn Server:............................................................................................................................ 9 2.4 The Operating System (OS) should be Windows 2000 Advanced Server..............................20 2.5 Windows 2000 service pack 2 should be installed..................................................................20 2.6 Deleting Com+ Component on Server....................................................................................20 2.7 Database Backup on Server:.................................................................................................. 21 System Backup of Server (If possible) ........................................................................................ 22 2.8 Generation of Input file (.inp file) Oracle 8i Installation...........................................................22 2.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 a database. 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 and are covered in a separate manual(RBI Oracle config.doc)...........................................................23 2.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 usedbe used later during Net8 service creation........................................................................................23
Page 4 of 81541
Version 1.0
2.13 Creating virtual server through Cluster Administrator (Refer the document - RBI Oracle Config.doc)................................................................................................................................... 23 2.14 The database needs to be created through Oracle Database Configuration Assistant from 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 clustered mode are not a part of this document and are covered in a separate manual (RBI Oracle config.doc)............................23 2.15 Adding the cluster resource through Oracle FailSafe Manager (Refer the RBI Oracle config.doc).................................................................................................................................... 23 2.16 Install the Oracle ODBC driver 8.01.73.00............................................................................23 2.17 Create a Net Service Name using Oracle Net8 Assistant. It will ask for the following information while creating the Service Name: ..............................................................................23 2.19 Net Service Name: Specify the service name to be created.................................................23 2.20 Host Name: Specify the IP Address of the Oracle server ...................................................23 2.21 (Logical IP Address allocated to Oracle DB).........................................23 2.22 Port Number: The installation will give default port number. ..............................................23 2.23 Service Name: Database name/service name/ SID name. from step (a) above...................23 2.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 in MSCS which are related to Oracle should be owned by the respective nodeserver)...............................................23 2.27 e) Oracle 8 ODBC Driver Configuration ...............................................................................23 2.28 Theis configuration needs to be done on both the nodes:server....................................23 2.30 Go to............................................................................................................................... 23 2.31 Start Menu->Settings -> Control Panel -> Administrative Tools -> Data Sources (ODBC). .23 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 the name of service created 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-fetch in tab Oracle count to 0, which is 10 by default) (tab - Oracle).....................................................23 2.34 For flat file generation aAdd the following parameter line to oracle parameter file which is present in your <o Oracle\racle home>\..\Admin\<SID>\Pfile\init.ora on the common storage box where the DB is residing. ............................................................................................................. 23 2.36 UTL_FILE_DIR = *.............................................................................................................. 23 2.38 Note : Oracle Fail over test should be done by your respective Oracle vendor....................23 2.41 IBM MQ Series NDS Member Server Installation.................................................................24 2.5 Enable sharing on j) the following folders: -............................................................................31 2.42 Database Setup.................................................................................................................... 33 2.43 PKI Implementation On Member Server ..............................................................................33 2.44 Adding System Path on NDS Member Server :....................................................................35 2.45 Change RBIPDONDS Com+ Property: ...............................................................................36 2.46 Generation of Info.txt:........................................................................................................... 37 2.47 Copying the Report Files on the disk:...................................................................................38 2.48 Database Creation and Migration Script:..............................................................................38 2.49 :39 2.50 Q Manager Setup:................................................................................................................ 44 2.51 Verification:........................................................................................................................... 51
Page 5 of 81541
Version 1.0
1. Introduction
The Reserve Bank of India (RBI) through its Public Debt Offices (PDOs) administers and manages the Internal debt, the Issue and servicing of new loans of the Central and State Governments. To accomplish the task of administration and management of internal debt, primarily Dated Securities, RBI has decentralised its operations through 15 PDOs established at 14 centres. The administration and management of Treasury Bills is centralised at Mumbai and is part of the Public Accounts Department (PAD), Mumbai. The PDO-NDS application, which encapsulates the above, needs of RBI and the 15 PDOs is designed & 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 instructionsprocedure for NDSapplying revised broadcast architecture release at member end. Application Upgradation to Ver. 2.7.45 (herein after referred as set upinstallation) on Member Server and Member Clientvarious operations for loading the of the PDO-NDS member end application in clustered servermode. If it is fresh installation of NDS 2.7.5, follow the 2.7.4 installation document.This process documented here has been tested and a pilot site has been implemented on a COMPAQ based hardware cluster. 1.2 Scope of the Document
This document provides the guidelines forfor applying software patch on member server for deployment of the revised format of NDS Trade Data Message Broadcastpatch to NDS application on member server. We assumed that NDS application is on C:\ProgramFiles\ . If it is stored in D or E drive, then make the changes accordingly in the batch program. 1.3 Objective
The objective is to Rrevised the architecture forof message flow from Host end to member-end, segregating flow of messages s pertaining to trade watch and market watch from flow of messages pertaining to deals. Henceforth, tTrade messages would be sent to an intermediate broadcast server, 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 NDS application on member sserver erver and client machinessoftware in a clustered server mode along with the daily administrative activities &and activities needs to be performed in case of failure of primary serverprimary node in clustered environment. The functionality and usage instructions for various business modules (such as secondary market operations etc) are not a part of this document and are covered in separate user manuals. 1. ItThiswill be is thesinduringthe following document. In case it is installed in a drive other than C: drive, please alter the path suitably during the course of the setup.dDdDAppliactionapplicationS113NDS If the database name or the database user id is different than as mentioned in the document below, please replace the database name and database userid suitably during the course of the setup.
Page 6 of 81541
Version 1.0
2. It is assumed that drive where the database is located will have disk space more than 1 GB and the drive on which the application has been installed will have minimum 500 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 be undertaken is given at respective stage in red. Please ensure the completion of such activity.
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 Procedure Section 3 contains the Member Client Installation Procedure Section 3 contains the Daily Startup and Shutdown operations Section 4 contains the reference for Reverting NDS application to Old version. (NOTE: This option is to be exercised only on specific instructions by RBI through NDS/Email/Telephone. This section is provided as separate document.)ther Operations
Page 7 of 81541
Version 1.0
Section 5 contains the Operations to be performed in case of Primary ServerPrimary node Failure
Page 8 of 81541
Version 1.0
2. Install Procedure for applying Patch on the Member Server ation Procedure
This section provides the guidelines for installingapplying and un-installing the software patch on PDONNDS application at the member end. It is assumed that NDS application is installed on drive C: of the NDS Server. In case the NDS application is installed on any other drive (e.g. D: or E:), then change the drive name in the 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 drive at 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 Server in 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 have been processed in MQ Series Queues. (Current depth of all Queues except Query, input and Output log should be zero) Stop all the Processes. 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 2.2 2.3 Pre-requisites for Software Installation Renaming and Backup of NDS Operating System Registry onOn Server: 2.1.1 Create folder BRDCST PatchNDSBackup_18102003160404NEWSMODLLS on Con C:\. 2.1.2 Copy the Zip NEWSMODLLS.ZIP file to above created folder. 2.1.33 Unregister following dlls ComMsg_MS_SMO_dll.dll MS_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 NEWSMODLLS folder. MS_SMO.dll, ComMsg_MS_SMO_dll.dll MC_Convert.dll UNREG.bat files. Rename following files in the folder C:\Program Files\RBIPDONDSSetUp\ServerDlls
Page 9 of 81541
Version 1.0
MC_Convert.dll to MC_Convert_old.dll ComMsg_MS_SMO_dll.dll to ComMsg_MS_SMO_dll_old.dll MS_SMO.dll to Ms_SMO_old.dll 2.1.5 Extract zip to folder C:\Program Files\RBIPDONDSSetUp\ServerDlls 2.1.6. Register following Dlls ComMsg_MS_SMO_dll.dll MS_SMO.dll 2.1.75 Goto Start Settings Control Panel Administrative ToolsComponent Services Computers My Computer COM+ ApplicationsRBIPDONDSComponents . Following screen will appear ApplicationsRBIPDONDSComponents . Following screen will appear Computers My Computer COM+
2.3.1
Press Enter or Click on OK button, following screen will appear:
Page 10 of 81541
Version 1.0
Page 11 of 81541
Version 1.0
2.1.86 Right click on component MS_SMO.ComMS_SMOClass.1 as shown in figure below and click Delete :
Page 12 of 81541
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 will Uunregister 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:
Page 13 of 81541
Version 1.0
Then click NewComponent. Following screen will appear:
Page 14 of 81541
Version 1.0
Press Next Button.
Page 15 of 81541
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 and press Open button. Following screen will appear:
Page 16 of 81541
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:
Page 17 of 81541
Version 1.0
Press Finish button.
2.1.5 Select TCS node and go to Registry Export Registry File as shown in figure given below:
Page 18 of 81541
Version 1.0
The following screen will appear:
Page 19 of 81541
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. 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 TCS_160404181003 as follows Right Click on TCS Node and click on Rename Rename TCS to TCS_16040418102003 and press enter Rename My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL
to
2.1.7 2.1.8
to
2.1.9
10.
MC_APPL_181003160404
Right Click on MC_APPL Node and click on Rename Rename MC_APPL to MC_APPL _16040418102003 and press Enter .
2.4 2.5 2.6
The Operating System (OS) should be Windows 2000 Advanced Server. Windows 2000 service pack 2 should be installed. Deleting Com+ Component on Server
Page 20 of 81541
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) of NDS User S113NDS. 1. S113NDS EXP S113NDS /S113NDS@PDONDS FILE = C:\S113NDS.,S113.DMP FULL = Y2. For entire SystemEXP System /manager@PDONDS FILE = C:\FullDatabaseBkp,DMP
As a precautionary measure, if needed, you may copy the Export C:\S113.DMPs C:\UserS113NDS.DMP to any other machine or to Floppy/CD/Cartridge.
Rename the RBIPDONDSSetUp folder.
Page 21 of 81541
Version 1.0
Rename C\Program Files\RBIPDONDSSetUp to C\Program Files\RBIPDONDSSetUp_160404 2.8 System Backup of Server (If possible) 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 CD The following screen will appear.
Your Member ID
2.3.3
Input the following in the above screen. o o o Enter Member ID of your bankinstitution/bank (e.g. BYA00055) Enter LUD ID of your institution/bankbank in LUD ID field (e.g. A178) All other fields are static and non-editable.
2.3.4
Select Input file location as C:\Generate as shown in the above screen 2.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.
Page 22 of 81541
Version 1.0
2.9 2.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 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 document and 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 is given in separate document). Database SID name given should be noted down, as it will be usedbe used later during Net8 service creation. 2.13 Creating virtual server through Cluster Administrator ( Refer the document - RBI Oracle Config.doc) 2.14 The database needs to be created through Oracle Database Configuration Assistant from 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 clustered mode are not a part of this document and are covered in a separate manual (RBI Oracle config.doc). 2.15 Adding the cluster resource through Oracle FailSafe Manager (Refer the RBI Oracle config.doc). 2.16 Install the Oracle ODBC driver 8.01.73.00 2.17 Create a Net Service Name using Oracle Net8 Assistant. It will ask for the following information while creating the Service Name: 2.18 2.19 Net Service Name: Specify the service name to be created 2.20 Host Name: Specify the IP Address of the Oracle server 2.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.24 2.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 in MSCS which are related to Oracle should be owned by the respective nodeserver). 2.26 2.27 e) Oracle 8 ODBC Driver Configuration 2.28 Theis configuration needs to be done on both the nodes:server. 2.29 2.30 Go to 2.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 the name of service created 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-fetch in tab Oracle count to 0, which is 10 by default) (tab - Oracle). 2.33 2.34 For flat file generation aAdd the following parameter line to oracle parameter file which is present in your <o Oracle\racle home>\..\Admin\<SID>\Pfile\init.ora on the common storage box where the DB is residing. 2.35 2.36 UTL_FILE_DIR = * 2.37 2.38 Note : Oracle Fail over test should be done by your respective Oracle vendor. 2.39 2.40
Page 23 of 81541
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:\Member End\Setup. Following screen will appear
2.4.2
b) Click Ok button. Following screen will appear:
Page 24 of 81541
Version 1.0
2.4.3 Check the Install User Interface Application check box as shown in above screen. Keep the 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 red circle in above screen. The following screen will appear:
2.4.5 Select .inp file created in C:\Generate folder and Click Open button.
Page 25 of 81541
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 pictures 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 during installation, use different user id RBI as shown in the following figure.
Page 26 of 81541
Version 1.0
Enter the values same as shown in the above screen. Password value is RBINDS. Click Press to submit the same.. Note: In case of different database name (other than PDONDS), enter that database name as an input to the DB Server Name filed in the above screen. 2.4.9 hiClick Continue in the following screen:
Page 27 of 81541
Version 1.0
2.4.10 iAgain click Continue in the following screen:
Page 28 of 81541
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 top right corner.
Page 29 of 81541
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.
Page 30 of 81541
Version 1.0
2.4.14 2.4.15
Open C:\Program Files\RBIPDONDSSetUp folder, rename PDONDS_MEMBER.exe as PDONDS_MEMBER_ORI. Copy PDONDS_MEMBER.exe from CD and paste it in C:\Program Files\RBIPDONDSSetUp folder.
2.5
Enable sharing on j) 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 can be 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: -
Page 31 of 81541
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:
Page 32 of 81541
Version 1.0
2.5.3 Rename My Computers\HKEY_LOCAL_MACHINE\SOFTWARE\TCS to TCS_ ORI as follows Right Click on TCS Node and click on Rename Rename TCS to TCS_ORI and press enter
2.5.4 Rename My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL to MC_APPL_ORI Right Click on MC_APPL Node and click on Rename 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 Setup 2.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.
Page 33 of 81541
Version 1.0
Click on Yes. 2. Open the Registry Editor and check that the value data of the following keys (Registry Name) is 04CC. 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 case sensitive). The following message will pop up after clicking on OK.
Page 34 of 81541
Version 1.0
Click OK. After making the Registry Entries Successfully, Click Cancel button to close the Window. 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 below procedure): Add the path C:\Program Files\RBIPDONDSSetUp\ServerDlls to system path as shown below: 2.6.1. My ComputersRight ClickPropertiesAdvancedEnvironment VariablesSystem variablesPath.
Page 35 of 81541
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 as it is C:\Program Files\RBIPDONDSSetUp\ServerDlls 2.6.44. Check that the existing path i.e. the variable value is not changed but is only appended with the 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 Click Properties Advanced) and change the Minutes until idle shutdown property to 1440 as shown below:
Page 36 of 81541
Version 1.0
Click on OK. Then close the Component Services window. 2.46 Generation of Info.txt: Go to StartPrograms PDONDS Server AdministratorGetApplicationIDS Following screen will appear
Please enter the following values in the corresponding fields: i. Application Name :- RBIPDONDS ii. 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 or special characters in this field)
Page 37 of 81541
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 to C:\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 folder MemberEndUpdates located at C:\Program Files\RBIPDONdsSetup to MemberEndUpdatesOld 3. Copy the folder MemberEndUpdates from the CD to C:\Program Files\RBIPDONdsSetup. 4. If the user name of the P1A Oracle database is not S113 then edit the file DB_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 installation only.
Perform the database migration from one of the nodes only. This step has to be carried out after the application is installed on both the nodes of cluster server. First edit the Createuser.sql file located at C:\Program Files\RBIPDONDSSetUp\MemberEndUpdates. Provide the absolute path of the datafile in the statement Create tablespace NDS.. E.G. CREATE TABLESPACE NDS DATAFILE 'I:\OraHome1\oradata\PDONDS\NDS.dbf' SIZE 1024M reuse DEFAULT STORAGE ( INITIAL 50K NEXT 50K MINEXTENTS 5 MAXEXTENTS UNLIMITED PCTINCREASE 0); After making this change, save the file at the same location and then proceed for the database migration as per point number 5. ] 5. Open the command prompt and go to the location C:\Program Files\RBIPDONdsSetup\MemberEndUpdates and type the following command DB_MIGRATION <Database Name>
Page 38 of 81541
PDO-NDS Ver. 2.7.42.7.5Server - USetup and Operations ManualpgradationInstallation Manual Version 1.0PDONDS Application For Clustereed ModeServer e.g. DB_MIGRATION PDONDS
Version 1.0
6. 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 the database 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:
Page 39 of 81541
Version 1.0
2.10.8192 and and.:
Page 40 of 81541
Version 1.0
Page 41 of 81541
Version 1.0
2.10.:
Page 42 of 81541
Version 1.0
2.10. figurescreen 2.10.CYou can cthe vityvity button.
Page 43 of 81541
Version 1.0
. the the .2.10.Click on OK. Once again Click on OK in ODBC Data Source Administration window. 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 :NDS Password: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:
Page 44 of 81541
Version 1.0
1. Go to MQ Series Explorer and check whether Q Manager NDS1P.LUDID.QMGR is created or not.
2. If Q manager is not created during Set up, create it from Dos prompt . Go to StartRUN and Type CMD , press enter to go to DOS prompt
3. Change the directory to C:\Program Files\RBIPDONDSSetUp\StartUp and execute MqsetUp.bat file from DOS prompt as shown below: C:\Program Files\RBIPDONDSSetUp\StartUp> MQSetUp.bat RBICRTMQOBJ.in
Page 45 of 81541
Version 1.0
4. Wait till command prompt appears again. The display on the screen will be seen as follows
5. Go to MQ Series Explorer StartPrograms IBM MQSeries MQSeries 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 newly created Q Manager NDS1P.LUDID.QMGR
Tata Consultancy Services Uncontrolled when printed Page 46 of 81541
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 value 1414, Click on OK as shown in the following screen.
ii. Add channel initiator. (NDS1P.LUDID.QMGR (Right Click) New Channel Initiator) After adding the service channel initiator, enter the initiation queue as SYSTEM.CHANNEL.INITQ under the parameter by selecting the properties of channel initiator service as shown in the below screen:
Page 47 of 81541
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-mark in front of AdoptNewMca (ALL) and AdoptNewMCACheck (ALL) as shown in following screen
Page 48 of 81541
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 server installation only . This step has to be carried out after the application is installed on both the nodes of cluster server.
Tata Consultancy Services Uncontrolled when printed Page 49 of 81541
Version 1.0
1. Install the Q manager on only one of the nodes of the cluster server and then move it to the common storage box as follows. 2. Move the Queue manager NDS1P.LUDID.QMGR to the virtual drive say J. (This is the logical drive on the cluster box. If you have decided to choose any other drive letter, move the queue to that drive). To move the queue you have to run the following command from the command prompt. hamvmqm /m qmname /dd J:\mqseries /ld J:\mqseries\logs where qmname will be your queue manager name (e.g. NDS1P.LUDID.QMGR) and J: is your shared disk drive letter mqseries and mqseries\logs are folders that will be automatically created. 3. Upon successful completion of this step you will be returned 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 MSCS 7. 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 will show the queue manager NDS1P.LUDID.QMGR (active on N1 and passive on N2)]
Page 50 of 81541
Version 1.0
Imp Note: With this installation, you have successfully installed NDS Server and NDS Member Client on server machine. No separate NDS Client installation is required on server. 2.51 Verification: Stop the NDS1P.LUID.QMGR and start again. Minimize the MQ Series explorer and Service windows. 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: StartProgramsPDONDS Application Member Member Regular Log in screen will appear. Enter the user name and password as usual. Password of user 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 verifies successful setup.
Page 51 of 81541
Version 1.0
Procedure for installingapplying patch on the Member Client: Please refer the steps given in a separate document (RBI-Mq configdoc.doc) to Install the IBM MQ Series 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 and another 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 on Disconnect as shown in below screen: Copy ComMsg_MS_SMO_dll.dll to C:\Program Files\RBIPDONDSSetUp\ClientDlls Register ComMsg_MS_SMO_dll.dll .
Page 52 of 81541
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 the Member 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:
Page 53 of 81541
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 the screen. Note: Your Server Name may be different. Select your server name and then ServerDlls which is shared on Server.
Click on OK and then Finish on Map Network Drive window. 3.3. Following procedure will map the MQSeries\Bin Folder:
Page 54 of 81541
Version 1.0
(This would have already been done in most NDS members client machines. So please verify, if its already 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 be selected by default as shown in the following Map Network Drive screen) window:
Page 55 of 81541
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 following screen: (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.
Page 56 of 81541
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:
Page 57 of 81541
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.dll iv. MS_Instru.dll v. MS_Mmbr.dll vi. MS_PMO.dll vii. MS_Serv.dll viii. MS_Settle.dll ix 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 the following message. The same way you can register all the dlls.
If following window appears when you Double click on first DLL:
Page 58 of 81541
Version 1.0
Then check the Check Box Always use this program to open these files and press Other to select 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:
Page 59 of 81541
Version 1.0
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:
Page 60 of 81541
Version 1.0
Page 61 of 81541
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 Rename Rename TCS to TCS_160404 and press enter 3.6.8 RenameMy Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL to MC_APPL_160404 Right Click on MC_APPL Node and click on Rename 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:
Page 62 of 81541
Version 1.0
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:
Page 63 of 81541
Version 1.0
Page 64 of 81541
Version 1.0
Select the directory that you have created in Step 3.2(1) i.e. C:\NDSBackup_18102003 and 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 Right Click on TCS Node and click on Rename 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 Rename Rename 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 :
Page 65 of 81541
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.
Page 66 of 81541
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:
Page 67 of 81541
Version 1.0
3.7.6 Click on Continue button. 3.7.7 Click on Continue button again.
Page 68 of 81541
PDO-NDS Ver. 2.7.42.7.5Server - USetup and Operations ManualpgradationInstallation Manual Version 1.0PDONDS Application For Clustereed ModeServer The following screen will appear :
Version 1.0
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.
Page 69 of 81541
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. If When 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 service v. Keep on cClicking next till you reach Finish. Note: During iInstallation may ask for of Windows 2000 Advanced Server in the . : Startup Type for Message Queuing service needs to be definedselect as an AutomaticAutomatic on both the serversNodes..
Open C:\Program Files\RBIPDONDSSetUp folder,rename PDONDS_MEMBER.exe as
Page 70 of 81541
PDO-NDS Ver. 2.7.42.7.5Server - USetup and Operations ManualpgradationInstallation Manual Version 1.0PDONDS Application For Clustereed ModeServer PDONDS_MEMBER_ORI.
Version 1.0
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 QManager 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 RBIPDONDS Server 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 by the 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 be created on the Member located on common storage box (select any drive).Server
Page 71 of 81541
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 the ownership 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 & MQSeries resources 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 box is 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 of Oracle & MQ resources defined in MSCS. This step needs to be performed only if you are loading the PDO-NDS software first 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 &and MQSeries 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
Page 72 of 81541
Version 1.0
Add the MQSeries services fter executing this command successfully, per asform the follows from the node which is holding the ownership of 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.INITQ under 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 <destination_directory>/ServerDlls &and <destination_directory>/Startup directory paths in the Environment Variable path (Control Panel/ System/ Advanced/ Environment Variables/Path) on both nodes. Destination directory is as specified during setup step 2.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 (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: . 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:
Page 73 of 81541
Version 1.0
Setting the Minutes until idle shutdown property of the COM+ package Running 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 the path 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 Programs PDONDS Client Administration Client Com+. On clicking this, the client COM+ screen would be opened.
Page 74 of 81541
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:
Page 75 of 81541
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 following screen:
Page 76 of 81541
Version 1.0
3.9.3. The screen shown below will appear:
Page 77 of 81541
Version 1.0
3.9.4. Enter the values as shown in above screen: Data Source Name: NDS TNS Service Name: PDONDS User ID : NDS Prefetch Count : 0 (Zero) 3.9.5. Check the database connectivity by clicking Test Connection button. Enter the password as NDS. You should get the message Connection Successful. 3.9.6. Click on OK. Once again Click on OK in ODBC Data Source Administration window.
1. Go to Start Settings Control Panel Administrative Tools Data Source(ODBC) System DSN. Following screen willscreen will appear
Page 78 of 81541
Version 1.0
Press Add button in above screen. 2. Following screen will appear. Select Driver Oracle OraHome 81 and Press Finish in following screen:.
Page 79 of 81541
Version 1.0
3. The screen shown below will appear :
Page 80 of 81541
Version 1.0
4. Enter the following inputs to the fields:values as shown in above figure : Data Source Name: NDS TNS Service Name: PDONDS User ID : NDS Prefetch Count : 0 (Zero) 5. Check the You can check database connectivity by clicking Test Connection . Enter the password as NDS. You should get message Connection Successful 6. Press Ok to exit the above screen. Verification of Setup: You will not able to login to NDS by using old NDS application icons (Short Cuts) You will have to go to Start Programs PDONDS Application Member Member to start NDS application. All other NDS application will remain same. Verify the following things on both nodes the Servers , once the setup is successful: Required DLLs are registered on the Severthe Sever Go to COM+ (Start Menu-> Settings-> Control Panel-> Administrative Tools-> Component Services-> Computers-> My Computer-> COM+ Applications->RBIPDONDS) and verify the components installed under package named RBIPDONDS. Components are GnrtEvnt.clsGnrtEvnt MC_COM_UTIL.MC_COM_FACTORY.1
Page 81 of 81541
PDO-NDS Ver. 2.7.42.7.5Server - USetup and Operations ManualpgradationInstallation Manual Version 1.0PDONDS Application For Clustereed ModeServer MS_AppSupport.ComMS_AppSupportClass.1 MS_Instru.ComMS_InstruClass.1 MS_Mmbr.ComMS_MmbrClass.1 MS_SMO.ComMS_SMOClass.1
Version 1.0
MQ series Queue manager are created along with the two channels (one receiver and one sender) and queues. A folder Trace is created on common storage box. In registry trace folders path is defined properly. setup in the <destination_directory> of the member server. This is where trace files will be created by RBIPDONDS system. Registry entries are created under HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL with proper DB related information (MC_CON, MC_USR, MC_PWD). Registry entries are created under HKEY_LOCAL_MACHINE\SOFTWARE\TCS\RBI-PDO with proper Member ID, LUDID and DB Server name. In the registry, verify that the security related information is there under HKEY_LOCAL_MACHINE\SOFTWARE\TCS\RBI-PDO\Security. The value of OwnCertificate should be <LUDID>cert.cert and OwnPrivateKey should be <LUDID>private.pem. These should be checked with respect to your LUD ID. Also check the value of Certs_Dir in the registry (default value is C:\\Certificates\\). Existence of the following files should be checked under the directory mentioned in Certs_Dir in the registry. i. RBI certificate (Receiver.cert) ii. Members own certificate (<LUDID>cert.cert) iii. Members Private key (<LUDID>private.pem) iv. CA certificate file (cacert.pem) v. Certificate revocation list (crl.pem) Note: Registry editor can be opened using regedit command on command line prompt. Making the Member Server Up Refer to Section 5.1.
Procedure for installing Client

Pre-requisite software Operating System The Operating System (OS) should be Windows 2000 professional on the Client machine Windows 2000 service pack 2 should also be installed. Oracle 8i Installation Install Oracle 8i Client. Install the Oracle ODBC driver 8.01.73.00 Create a Net Service Name using Oracle Net8 Assistant and provide . It will ask for the following information while creating the Service Name: Net Service Name: Specify the service name to be created Host Name: Specify the logical IP Address of the Oracle server. Port Number: The installation will give default port number. You may use the same. Service Name: Database name/service name/ SID name from step (a) above.
Page 82 of 81541
Version 1.0
Note: The newly created service should be tested using a valid user name and password. Go to Start Menu->Settings->Control Panel->Administrative Tools->Data Sources (ODBC) and create a System DSN (Name P1A) using installed Oracle driver (step b) to connect to the Oracle database. Provide the value for TNS Service Name (give the name of service created in step c) &and Database user Id. The Database user Id needs to have at least read access to the database. This user Id is used during generation of reports. Also while configuring the DSN set property pre-fetch count to 0, which is 10 by default (tab - Oracle). MSMQ Installation 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. Select Independent client as the message queuing type. iv. When prompted for Message Queuing Server, select the option Message queuing will not access a directory service v. Click next till you reach Finish. Note: Installation may ask for Windows 2000 Server/Professional CD. Application Installation IMPORTANT: If the Member Client application is being setup on the same machine where the Member Server (On both the Serversnodes) is setup then, while executing 2.2.4(a) In the field Local IP Address enter the value of Logical IP aAddress which is given to MQSeries which is the logical IP address to Local IP Address. Also in this case, steps 2.2.4 (b), (c), (d), (e) and (f) are not required to be executed. But If the Member Client application is being setup on the separate machine (other than member server) then all the following steps need to be executed. Run the setup.exe for installing RBIPDONDS Client application from the RBIPDONDS Client 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 by the following information: DSName: Name of the DSN created in step 2.2.2 (d) DB User ID/Password: The user ID and Password that will be used by the application for connecting to the database Local IP address: The IP address of the machine where the client is being installed. Reports Path: The path name where the installation program will save the reports. You may use the default value displayed or specify an alternate path.
Page 83 of 81541
Version 1.0
Share the directory on one of the nodeserver machine where the Server DLLs are stored with the Client machine (ServerDlls directory under the destination_directory> specified during server installation in earlier step.) Map a network drive (e.g. E:\) to the MQ Series Bin directory of oneof one of the nodeServer and include it in the system PATH variable on the client machine as registering the application DLLs requires some MQSeries DLLs in the path The network drive mapping can be removed after the application installation is completed. Register the following DLLs using regsvr32 dll_name command from command prompt or select each of the following DLL &and double click on it. GnrtEvnt.DLL MC_COM_UTIL.DLL MS_AppSupport.DLL MS_Instru.DLL MS_Mmbr.DLL MS_SMO.DLL Run getAppIDCLSID.exe on the one of the nodeServer (Member Server in clustered env.). It resides under the UTIL sub-directory under the directory where the server application is installed (destination_directory specified during server installation in earlier step). This will ask for the following information: Application Name: the name of the Application (COM+ package) installed on the Server i.e. RBIPDONDS Path of configuration file: file name must be info.txt. Specify the full path to store the info.txt file Server Name: Enter the Logical IP Address assigned to MQSeries Application. The information will get stored into info.txt file under the specified path (default: UTIL directory). Copy info.txt &and ClientCOM+.exe file from the server to a directory (e.g. create a UTIL directory under the destination_directory specified during client installation in earlier step) on client machine. Run the ClientCOM+.exe file on the Client. Verification of Setup Verify the following things once the setup is successful:
Page 84 of 81541
Version 1.0
The registry entries are created under HKEY_LOCAL_MACHINE\SOFTWARE\TCS\RBI-PDO containing the Report related settings (REPORTPATH). The registry entries are created under KEY_LOCAL_MACHINE\SOFTWARE\MC_APPL with the proper DB information (MC_CON, MC_USR, MC_PWD). Procedure for un-installation PDO-NDS application The PDO-NDS application can be uninstalled from any one of theof the nodeserver in clustered or from both the nodeservers by the procedure given below. The procedure ensures that all the necessary components of the application are removed in a proper manner so that any subsequent installation of the same application can be done smoothly. 2.3.1 Un2.3.1 Un-installation Procedure for Member Server Pre-requisite software RegClean.exe Before un-installing the PDO-NDS application Close all the applications related to PDO-NDS i.e. HostConn.exe etc. 2.3.1.2 Go to Un-Installing the PDO-NDS application
Start Menu-> Settings-> Control Panel-> Administrative Tools-> Component Services-> Computers-> My Computer-> COM+ Applications->RBIPDONDS and shutdown the RBIPDONDS application by choosing Shutdown on the right-click menu. Note: If shutdown is not done properly system may give an error while uninstalling saying Component cannot be removed and as a result some components may remain on the HDD with their registry entries even after un-installation is complete. Remove the COM+ components from the RBIPDONDS application manually (path as in step 2.1.6(b)). Delete the RBIPDONDS application package. Go to Settings/ Add-Remove Programs and remove the member server application installed. Manually delete the application folder from the location where you had originally installed it. . Run RegClean.exe. Take the backup of Trace folder &and remove the Trace folder from common the common storage box. 2.3.1.3 Remove Registry Entries Run regedit utility from the command prompt. Manually delete the following keys from the registry: My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MC_APPL My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\TCS\RBI-PDO Remove IBM MQ Series Manager Go to IBM MQ Series Explorer. Stop the Queue Manager created for PDO-NDS application, if it is already in running state. Delete the Queue Manager.
Page 85 of 81541
Version 1.0
(To create the Q-manager/queues/channels before subsequent NDS installation, please refer the MQ installation document given separately) 2.3.2 Un-installation Procedure for PDO-NDS Client 2.3.2.1 BeforeBefore un-installing the PDO-NDS Client application Close the PDO-NDS application, if already running. Go to Settings/ Add-Remove Programs and remove the PDO-NDS client application installed. Manually delete the application folder from the location where you had originally installed it. This is the <destination_directory> that was specified during the installation in earlier step. d) Run RegClean.exe 2.3.2.2 Removeing Registry Entries Run regedit utility from the command prompt. Manually delete the RBI-PDO folder from TCS folder in the HKEY_LOCAL_MACHINE\SOFTWARE registry entry. ==================================================================
NOTE: - All the market participants have to intimate their

LOGICAL IP Address assigned to MQSeries to RBI. ======================================================
Page 86 of 81541
PDO-NDS Ver. 2.7.42.7.5Server - USetup and Operations ManualpgradationInstallation Manual Version 1.0PDONDS Application For Clustereed ModeServer Daily Startup &and Shutdown operations
Version 1.0
This section will provide detailed guidelines for the daily start-up and shut-down operations to be performed at the nodeserver which holdsis holding the ownership of all the resources i.e. Oracle &and MQSeries resources defined in MSCS. before the PDO-NDS application can be started by the end users and at the day end, respectively. Daily Startup operations These operations need to be performed before the end user starts using the PDO-NDS application to perform their regular activities. At Member Server Start the MQ series explorer on the server which is currently holding the ownership of MQ Series resources (Check through Cluster Administrator). Start the Receiver and Sender channels individually in similar manner. The status will change to Running. If the channels do not change status to 'Running' then that means there is some problem in communication between host and member server. Note: The channel status can be monitored using the MQMonitor.exe. Refer Section 6 Appendix A. Run HostConnection.exe (Start Menu->Programs->RBIPDONDS Member Server->Startup). The following screen will open. Click on Begin Of Day to run the day beginning operations. Click on Connect for handshake between Mainframe and Member End. The status bar at the bottom will display message Connected to host.. Click on Processes> Start to begin the polling process on Transaction and Negotiation queues. The Process Information section will display Process started successfully message for the Transaction and Negotiation queues as well as for ErrMsgToAdmin along with the date and time stamp.
Page 87 of 81541
Version 1.0
NDS Server Administration screen used to connect to host start the polling processes 3.1.2 Day Beginning Operation
This operation needs to be performed on the Primary ServerPrimary node i.e. nodeServer which is holding the Ownership of all the Oracle &and MQSeries resources defined in MSCS. 3.1.3 Triggered during the day by operator Generate deal slip flat file A comma (,) separated flat file can be generated &and saved on local drive or on common storage box. 3.2 Daily Shutdown operations These operations need to be performed only after all the end users have finishes their days activities. 3.2.1 At Member Server Go to NDS Server Administration window and click on Processes-> Stop button. It will terminate all the polling processes. The Process Information will display the Process stopped successfully message for the Transaction and Negotiation queues as well as for ErrMsgToAdmin along with the date and time stamp. Note: The Log files show the txt files generated in Trace directory.
Page 88 of 81541
Version 1.0
Now click Disconnect button to disconnect from host.. The status bar at the bottom will display message Disconnected from host.. Click on End Of Day button. This will empty the transmit queue to ensure that no old messages are sent to Host on the next working day. At the end of everyday, there will be a shutdown message from the host compelling all the members to disconnect. This message updates the HOST_CONNECTION flag in the registry to N, thus disallowing the members to connect to host. Other Operations System personUser can check the status of connection with the host by clicking on the Host Connection icon. The application will ping and get the correct status. System person User can process the messages in the UNPROC queue by selecting the option Process Messages from UNPROCQ in Processes section from NDS Administrator Screen. User will have to first move all messages from UNPROC queue to another Temp queue by using the MQ Utility or by running the following command onfrom DOS command prompt and then select the process message from UNPROQ option from the Host Connection Screen to start the processing of unprocessed messages. C:\Program Files\RBIPDOServerSetup\Startup > PollOnMsg.exe SSS1P.HL.LUDID.UNPROCQ SSS1P.LUDID.QMGR (LUDID Your LUD ID) User can also refresh the names of the log files displayed by clicking on Refresh File View button i.e. if a new file is generated the refresh will get the name of that file. SSS1P.HL.LUDID.TEMP_UNPROCQ
Operations to be performed in case of Primary ServerPrimary node Failure. At Member Server (On In Clustered Servermode) After failure of the primary serverprimary node all the resources defined in MSCS (cluster application) would get switch to secondary serversecondary node automatically &and thus secondary serversecondary node will become the owner of all the resources (this can be checked through Cluster Administrator). Ensure that Message Queuing Service is started. Navigation: Start Menu-> Settings-> Control Panel-> Administrative Tools-> Services-> Check the status of Message Queuing Confirm the state of the sender channel, which should be Running, Receiver channel maymight show the status Inactive, still you can try to connect to the Host. Go to NDS Server Administrator screen &and establish the connection to the Host. Start the processesPollOnMsg processes.
Page 89 of 81541
PDO-NDS Ver. 2.7.42.7.5Server - USetup and Operations ManualpgradationInstallation Manual Version 1.0PDONDS Application For Clustereed ModeServer 5.2 At Member Client
Version 1.0
On the Client machine user will get following error message after Fail over. The remote server machine does not exist or is unavailable All the users have to relogin the application. Note: that System takes little more time while logging off.
NOTE: - All the market participants have to intimate their

LOGICAL IP Address assigned to MQSeries to RBI. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------xxxxxxxxxxxx END xxxxxxxxxx ---------x--x--x-----------
Page 90 of 81541

Revised Trade Message Broadcast Architecture

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Revised Trade Message Broadcast Architecture

Hochgeladen von

Copyright:

Verfügbare Formate

RESERVE BANK OF INDIA

Manual Version: 1.0 Prepared by

July AugustOctober 2003APRILJullyne 20042

PDO-NDS Computerisation Project

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

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Organization of the Document

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Procedure for installing the Member Server in Clustered mode

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

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

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Then click NewComponent. Following screen will appear:

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Press Next Button.

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

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

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

Press Finish button.

Tata Consultancy Services

Uncontrolled when printed

PDO-NDS Computerisation Project

The following screen will appear: