The figure below presents the general concept of the kdpw_stream production environment and test environment, which allows KDPW Participants to perform a range of tests independently of their on-going operations.
TST A test environment
The main test environment is TST A, which represents the current version of kdpw_stream used in the production environment. This environment is available to Participants, developers and other capital market institutions in order to perform compatibility tests of their software with the software available from KDPW. Access to the TST A environment is free of charge on business days and provided on request of Participants.
TST B test environment
The TST B environment is an additional environment initialised from time to time on KDPW initiative, which is notified to Participants in advance. This environment is designed to test new functionalities or new versions of existing functionalities without disrupting Participants’ tests of the existing kdpw_stream version in the TST A environment.
Communication between the Participant test environment and the kdpw_stream test environment is supported by a dedicated test communication channel secured with test security certificates issued by the Main Guarantor KDPW on execution of the SWI Agreement.
The organisation of the Participant’s IT system test environment interacting with the kdpw_stream test environment depends on the Participant’s requirements; KDPW recommends to build at least one test environment interacting with the kdpw_stream test environment.
The TST A or TST B test environment is selected individually by each Participant: the environment is reconfigured accordingly by the KDPW System Operator. By default, all Participants are connected by the TST B environment (after completion of tests in the TST A environment, the User is switched to the TST B environment). This helps to avoid the need for any technological modifications on User side. Unless the User has presented a written declaration on the selection of a test environment, each message received in SWI will trigger an additional message esdk.rjc.001.01 being sent to the User to report denial of access to the kdpw_stream test environment.
Rules for using the test environments
- The kdpw_stream TST A test environment is available to Participants from 08:30 to 18:00 on business days. Use of the TST A test environment on other days requires individual arrangements with KDPW.
- kdpw_stream test environments are available to Users who have signed an SWI Agreement with KDPW.
- Access to the kdpw_stream TST A test environment is normally closed. The intention to use the environment should be notified by sending the “Test Environment Access Application” to KDPW by e-mail (scan) at di_serwis@kdpw.pl or by fax at 022 6272345, no later than three business days before the requested date. In case of a sudden and unexpected need to access the test environment, please contact the System Operator directly.
- All arrangements concerning the availability of the test environments should be consulted with the System Operator, phone 022 537 94 15 (e-mail: di_serwis@kdpw.pl).
- Communication tests performed exclusively via the electronic communication channels ESDI/WEB, ESDK and The SWIFT Message Processing System are unlimited and free of charge. Use of the electronic communication channels ESDI/WEB and ESDK requires test security certificates issued by the Chief Guarantor KDPW under relevant agreements.
- KDPW will initialise the TST B test environment depending on tests of new functionalities or modifications to existing functionalities planned by KDPW, WSE, BondSpot or NBP, which is notified to the Users in advance. Use of this environment is free of charge. The agenda of planned tests is available on the KDPW website in the kdpw_stream section.
- The configuration parameters of the communication test environment (SWI TST) are provided to the authorised employee of the User, developer or another capital market institution by the Main Guarantor in the process of issuing security certificates. Updated technical information necessary to use the kdpw_stream test environment is available on the KDPW website www.kdpw.pl in the kdpw_stream section.
- In order to execute performance tests in a test environment, the details of the planned test should be agreed with the KDPW IT Systems Operation Department. The test environment is organised on a separate system platform whose performance parameters are not identical with the parameters of the production environment system platform.
Rules for the TST A environment datafeed
- Databases are copied from the production environment (PRD) to the TST A test environment once per month, as at the last business day of the month.
- Financial instrument databases: production instruments are copied, instruments used only in the test environment remain unchanged;
- Balances: all production balances are copied for production instruments. For test instruments, balances will be created automatically (10,000 instruments each) for all Users (both production and test Users) in the test database and a corresponding issue size on the issue account;
- User databases: copied in the same way as financial instrument databases. After copying, test Users only hold balances in test financial instruments except derivatives.
- All clearing instructions which are not cleared by the day of copying the databases will be deleted from the test environment.
Clearing day timetable – cash clearing and settlement
| Settlement session no. | Settlement session opening time | Types of cleared operations |
|
R |
9.00 |
Morning technical session |
|
1 |
12.00 |
Regular session – all operations |
|
2 |
14.00 |
Regular session – all operations |
|
3 |
16.00 |
Regular session – all operations |
|
W |
16.15 |
Afternoon technical session |
- Clearing and settlement in the real-time system (RTGS) are processed from 9:00 to 16:00.
- The scope of operations processed in the test environment corresponds to the scope set out in Appendix 2 to the KDPW Detailed Rules of Operation.
- Settlements are processed assuming full cash coverage: standard tests do not include operations with the clearing bank.
| Settlement session no. | Settlement session opening time | Types of cleared operations |
|
P |
10.00 |
Morning technical session |
|
N1 |
17.15 |
Regular session – all operations |
Clearing Fund:
- Forecasts payments – 17:45
- MtM payments – 13:00
Monthly Treasury bond reporting tests
Tests of monthly Treasury bond reporting (supporting messages semt.tr1 and semt.tr2) should be agreed with the Surveillance Department in advance of such tests in order to set the test period (reporting period) as the test environment is ready to support periods shorter than one month. The functionality can be tested several times during the month provided however that it does not cover days other than the reporting period.
Corporate actions tests
The scope of planned corporate actions tests should be agreed by the User before filing the “Test Environment Access Application” (Appendix 2). The User should send the proposed timetable of corporate actions tests (Appendix 3) by e-mail at di_serwis@kdpw.pl no later than 4 business days before the planned start date of the test. The application should be filed to confirm the feasibility of the test on the proposed date (within the timeline proposed by the User) and to configure test events in the TST A test environment.