GATEWAY CONFIGURATION MANAGEMENT

Transcription

1 D GATEWAY CONFIGURATION MANAGEMENT COUNT: Page 1 of 17

2 DOCUMENT APPROVAL ROLE NAME SIGNATURE DATE AUTHOR Ben Haworth 20/03/2014 REVIEWER Mark Pearce DOCUMENT HISTORY ISSUE DATE ISSUED REASON FOR ISSUE DOCUMENT HISTORY TRUNCATED VERSION /07/2009 General update as part of overall Data Transfer Handbook review. VERSION /05/2011 General update following Technology Refresh VERSION /03/2013 Minor amendments and updates to appendices VERSION /05/2015 Document and branding refresh VERSION /02/2016 Reformatting NOTE: If this document is received in electronic format approved signatures will not appear. Users should refer to hard copy versions if necessary. COUNT: Page 2 of 17

3 CONTENTS Introduction 4 Configurable Items 5 Hardware 5 Software 5 Routing Information for Data Flows 5 Processes for Changing Routing Tables 6 Making Complex Changes using the Manual Process 8 Submit configuration change request 9 Acknowledge Receipt of Request 9 Provide Cost and/or Advice 9 Accept Costs 9 Implementation and Testing 10 User Acceptance 10 The Process for Changing Data Flow Configurations 10 Using the ACMT for Making Simple Changes 11 The ACMT Connection Procedure 11 The ACMT process for changing Gateway configuration tables 12 Market Participants configured for more than one Gateway 12 Gateways supporting more than one participant 12 ACMT Charges 13 ACMT Good practice 13 ACMT - Implementation 13 ACMT Cancellation of changes 13 Appendix A Gateway Configuration Table Good Practice Guide 14 Appendix B Data Flow Configuration Form 15 Appendix C Host Action Form 16 Appendix D Web Tools Client Form 17 COUNT: Page 3 of 17

4 INTRODUCTION 1. This section of the Data Transfer Handbook (DTH) describes the process by which configuration of DTS Gateways is managed. It details the various elements that can be configured and the procedures for making changes to configurations. COUNT: Page 4 of 17

5 CONFIGURABLE ITEMS 2. The three principal components of the DTS Gateway are hardware, software and routing information for data flows. Elements of these can be configured by the User or by the Service Provider on the User s behalf. Hardware 3. The hardware components of High Volume Gateways (HVG), Low Volume Gateways (LVG), Virtual High Volume Gateways (VHVG) and Virtual Low Volume Gateways (VLVG) are listed in Section 3 Part 1 of the DTH. With the following exceptions, none of these components can be modified by the User. 4. If a User s HVG fails and there is a need to engage the Central Backup Gateway (CBG), the standard procedure is to re-configure an element of the cabling within the Gateway cabinet. If such a change is required, Users will receive specific instruction from the Service Provider on how to reconfigure the physical cabling at the Gateway. Alternatively, if the User has provided two network access points, this process will be automated and will not require User intervention. 5. Users are responsible for performing a controlled start-up of their Gateway if their site power supply fails. This should be done under the direction of the Service Provider. 6. Unless explicitly advised by ElectraLink or the Service Provider no other hardware configuration changes should be initiated by Users. Software 7. Software components of the DTS are those which enable the transfer of messages across the DTS, for example message translation and encryption software. Some software elements are local to User Gateways while others are located centrally in the DTS. The configuration management of all software components is carried out by the Service Provider and requires no intervention by Users. 8. Requests to make software changes are processed according to the change procedure defined within section 4.4 of the DTH. ElectraLink manages installation of approved software changes. Routing information for data flows 9. The Service contains a configuration table which controls how incoming messages are routed to a Users host(s). 10. Changes to the configuration are managed according to the procedures described in this section of the DTH. 11. Depending on the method of operation of the Gateway (Host or Gateway initiated push/pull, ref. Section 3 part 2 Gateway Interface Specification), Users may have to request additions or changes to local communication host addressing information in order that messages are correctly routed to host applications. This would include network TCP/IP addresses, host usernames and host passwords. COUNT: Page 5 of 17

6 PROCESSES FOR CHANGING ROUTING TABLES 12. There are two methods for changing the data flow configuration, either by using the Automated Configuration Management Tool (ACMT) or by submitting change forms to Electralink (Manual process) or, in some circumstances, a combination of the two. 13. The ACMT, which is part of the Web Tools suite of applications, is the preferred method of carrying out routing changes and Users are recommended to use it wherever possible. Any User, regardless of their particular Gateway Option, can use the ACMT. There are, however, changes that cannot be made using the ACMT for example TCP/IP address changes, filename templates etc; in this case the Manual process should be used in conjunction with the ACMT. 14. Simple changes involving routing information can be carried out using the ACMT. These types of change comprise: a) Market Participant Role; b) Flow Identifier (Dnnnn); c) Flow version number; d) Test Data Flag; e) Destination Gateway and Host; f) File format variant (Fixed, Variable or Pool Transfer) on an individual flow basis; g) Initiating MPID; and/or h) Initiating Role Code. 15. Complex changes require the use of the current Manual process to ensure that ancillary information is properly configured on the Gateway. Once the Manual process has been completed, then the ACMT should be used to configure further routing information and flows according to paragraph 14 above. Complex changes involve either: a) a change to, or creation of a Gateway identifier; b) addition of a new market participant identifier for an existing participant (new participants should refer to DTH section 4.1); c) change to a TCP/IP address of a host; or d) change of a username or password of a host; COUNT: Page 6 of 17

7 16. The following diagram illustrates the combined use of Manual and ACMT processes for complex changes. ACMT Manual and Automated Flows What Change? Flow Information Use ACMT Host Information Follow Manual Process Finish Update Flows? Yes No Finish Figure 1: Use of Manual and ACMT processes for complex changes COUNT: Page 7 of 17

8 MAKING COMPLEX CHANGES USING THE MANUAL PROCESS 17. The Manual process for changing routing tables is required for complex changes to host and Gateway information defined in paragraph 15. The ACMT cannot be used to change this information. 18. The Manual Process will still be supported for simple changes to flow information defined in paragraph 14, but it is recommended to use the ACMT for simple changes. 19. Figure 2 illustrates the procedure by which manual changes to data flow configurations are managed: USER ELECTRALINK SERVICE PROVIDER Submits Data Flow Configuration Change Request Acknowledges Receipt of Request Accepts cost Provides cost Instructs Service Provider to execute change Executes change Accepts change Confirms change has been executed Figure 2: Overview of Manual configuration change process COUNT: Page 8 of 17

9 Submit configuration change request 20. Users should submit requests to change their local host configurations to the ElectraLink helpdesk. The helpdesk will allocate a Change Control Notice number (CCN) to the request, which will be used to track the request. Requests must be submitted on the appropriate form, by to the ElectraLink helpdesk. Pro-forma Host Action Forms for host information are included in Appendix C. Should Users require changes to be made to their data flow configuration, pro-forma Data Flow Configuration Forms are included in Appendix B. These forms must be submitted by the Contract Manager. Acknowledge Receipt of Request 21. ElectraLink will acknowledge receipt of the request, by , to the User who submitted the request and the relevant Contract Manager. Unless noted otherwise this acknowledgement is given to the sender of the request. 22. Enquiries regarding the use of these forms should be made to the ElectraLink helpdesk. Provide Cost and/or Advice 23. On receipt of the request, the ElectraLink administrator examines it to determine whether it is complete, or if additional information is required. The administrator checks to see if the request conforms to the guidelines given in the Gateway Configuration Table Good Practice Guide contained in Appendix A of this document. 24. If appropriate ElectraLink will liaise with the User to request further information or give advice on Gateway configuration. 25. Should the change involve a change to, or creation of a Gateway identifier, ElectraLink will provide a cost for the change within 10 working days. Accept Costs 26. A schedule of charges associated with different types of configuration change is presented in Section 6 of the DTH. 27. The cost of all changes submitted via Host Action Forms or Data Flow Configuration Forms are of a fixed cost which is defined in Section 6 of the DTH. It is assumed that the Contract Manager is aware of all the costs implicated in the request and that permission to carry out the request is implicit in its submission. 28. Should the change involve a change to, or creation of a Gateway identifier, the User should approve the costs by . ElectraLink will then authorise the work to proceed. COUNT: Page 9 of 17

10 Implementation and Testing 29. On receipt of an authorised instruction from ElectraLink, the Service Provider will make the data flow configuration change within 10 working days (or on a day after 10 days is specifically requested by the User). Note that once the change has been made, any incoming files which form part of the changes will be delivered to the new destination and in the new format, where relevant. 30. The Service Provider will notify ElectraLink by that the change has been implemented. These activities will be completed within the 10 working days specified in paragraph 29 above. User Acceptance 31. ElectraLink will send an to the User to confirm that they are satisfied that the work is completed. Users should confirm acceptance within 5 working days of receipt. Users who have not responded to the within 5 working days will be deemed to have accepted the change. The Process for Changing Data Flow Configurations 32. Once the User has received notification that the changes detailed on the Host Action Forms have been implemented, the ACMT can be used to configure the desired additions and changes to the Data Flow information. The details of the use of the ACMT are described in the following section Using the ACMT for making Simple Changes. 33. Use of the Manual process for requesting data flow configuration changes is discouraged. The Manual process should be used, however, to make changes to the local host configurations. The Data Flow Configuration Form is used for this and it is included in Appendix B. 34. The cost associated with making these changes manually is also detailed in section 6 of the DTH, Schedule of Charges. COUNT: Page 10 of 17

11 USING THE ACMT FOR MAKING SIMPLE CHANGES 35. The ACMT is an automated tool to allow data flow configuration changes (i.e. simple changes as specified in paragraph 14) to be made in real time to the live service. The process for submitting changes mimics as far as possible the Manual process it is designed to replace. It also provides extra capabilities which are unavailable via the Manual process. In particular, Users should be aware of the following functionality: a) Extracts from the routing tables can be automatically generated by ACMT. These show the current routing configuration. b) A deferred implementation capability, which allows changes to be submitted in advance for implementation at a future date. c) The ability to cancel a request that is awaiting implementation (called a Pending request ). The ACMT information exchange process uses a standard web browser to connect to the ACMT Database Server. Users make changes in real time to the routing tables using a web browser. The ACMT Database Server:- 36. validates and implements the changes for the relevant Gateway or Gateways, within the central configuration database. 37. Full instructions on how to use the ACMT to make changes to data flow configurations are contained in the Web Tools User Guide, which is available from ElectraLink. The ACMT Connection Procedure 38. Access to the ACMT and other Web Tools applications is provided as part of the new User connection procedure. At this point, a username and password are provided to the User representative who is responsible for establishing the connection. 39. If the User is not new, they must contact the Contract Manager who will either provide the existing username and password details or endorse a request for a new account to be created. 40. Users may also setup their own new username and passwords using an existing Web Tools client if they have been enabled to do so. Please contact the ElectraLink helpdesk for further information. COUNT: Page 11 of 17

12 The ACMT process for changing Gateway configuration tables 41. Figure 3 gives an overview of the communications process over the DTS for configuration changes that are generated via the ACMT. If required, further details can be obtained from the Web Tools User Guide. PC USER Web Browser (IE5 or later) ACMT HTTP session MDNS MDNS Gateway USER S NETWORK Figure 3: Use of the DTS by the ACMT Market Participants configured for more than one Gateway 42. The Market Participant is responsible for managing the delegation of authority for carrying out changes to its configuration data. 43. It is possible to make changes on a subset of a Market Participant s configuration data without overwriting the remainder. 44. Market Participants who wish to delegate authority for making configuration changes to more than one User (i.e. ACMT Client) are strongly advised to read the relevant sections of the Web Tools User Guide and to develop the necessary management processes to support this. The Electralink Helpdesk will be happy to advise if required. 45. When the data of a Market Participant is on more than one Gateway, and there is an Industry change (say to the DTC) which requires a simultaneous update of all or multiple Gateways, it will be necessary to allow one party to update the Gateway configuration for the MPID on all Gateways holding that MPID s data. The ElectraLink helpdesk will manage this on an individual basis or Users can manage this themselves if they have access rights to all relevant Gateways. Gateways supporting more than one participant 46. Any User may be authorised to modify data for more than one Market Participant (provided the Market Participant(s) agree). This ability is independent of the location of the User, and the Gateway to which the User is affiliated. 47. Users may choose to manage each Participant via a separate ACMT Client, or by the use of one ACMT Client. The ElectraLink Help Desk helpdesk will be happy to advise if required. COUNT: Page 12 of 17

13 ACMT Charges 48. A schedule of charges associated with the different types of configuration change is presented in Section 6 of the DTH. Users should note that there is no charge for creating, modifying, deleting, viewing or validating data flows via the ACMT. ACMT Good practice 49. The User must ensure that the request conforms to the guidelines given in the Gateway Configuration Table Good Practice Guide in Appendix A of this document. This equates to the current Manual process. ACMT - Implementation 50. The Service Controller will implement configuration changes via the ACMT with a typical turnaround time of 1 day. An exception is a configuration change that has been scheduled for implementation at some time in the future via a deferred implementation request. ACMT Cancellation of changes 51. Users may cancel an Action Request either by submitting a Remove Pending Action Request or by submitting a second Action Request. COUNT: Page 13 of 17

14 APPENDIX A Gateway Configuration Table Good Practice Guide 52. Please see the separate document S04P8 Appendix A whose pages provide the Gateway Configuration Table Good Practice Guide. COUNT: Page 14 of 17

15 APPENDIX B Data Flow Configuration Form 53. Please see the separate document S04P8 Appendix B whose pages provide the pro-forma Data Flow Configuration Form. COUNT: Page 15 of 17

16 SECTION 4 (PART 1) USER CONNECTION PROCEDURE APPENDIX C Host Action Form 54. Please see the separate document S04P8 Appendix C whose pages provide the pro-forma Host Action Form. COUNT: Page 16 of 17

17 SECTION 4 (PART 1) USER CONNECTION PROCEDURE APPENDIX D Web Tools Client Form 55. Please see the separate document S04P8 Appendix D whose pages provide the pro-forma Web Tools Client Form. COUNT: Page 17 of 17