このページの2つのバージョン間の差分を表示します。
両方とも前のリビジョン 前のリビジョン 次のリビジョン | 前のリビジョン | ||
spec:en:isv:connection [2023/09/29 16:55] editor |
spec:en:isv:connection [2024/01/22 10:04] (現在) editor |
||
---|---|---|---|
行 28: | 行 28: | ||
=== 2.1.1 Production Environment === | === 2.1.1 Production Environment === | ||
- | The production environment is for the purpose of using the system service, and available from 8 a.m. (JST) to 6 p.m. (JST) on trading days.The investor system logs on to CONNEQTOR during the available hours of the trading day. CONNEQTOR does not have a disaster recovery site. In the event of a broader disaster of CONNEQTOR (production), | + | The production environment is for the purpose of using the system service, and available from 8:00 a.m. (JST) to 6:30 p.m. (JST) on trading days.The investor system logs on to CONNEQTOR during the available hours of the trading day. CONNEQTOR does not have a disaster recovery site. In the event of a broader disaster of CONNEQTOR (production), |
\\ | \\ | ||
{{ :: | {{ :: | ||
行 37: | 行 37: | ||
\\ | \\ | ||
=== 2.1.2 Staging Environment === | === 2.1.2 Staging Environment === | ||
- | The staging environment is for testing purposes, and the test day is basically the same day as the trading day of the production environment. It is available from 8 a.m. (JST) to 9 p.m. (JST) on the day of testing. When the investor performs the test, the investor system will attempt to log in to CONNEQTOR during available hours on the day of the test. If the FIX session is disconnected during the test, the investor system may attempt to log in again. | + | The staging environment is for testing purposes, and the test day is basically the same day as the trading day of the production environment. It is available from 8:00 a.m. (JST) to 9:00 p.m. (JST) on the day of testing. When the investor performs the test, the investor system will attempt to log in to CONNEQTOR during available hours on the day of the test. If the FIX session is disconnected during the test, the investor system may attempt to log in again. |
In the case where investor selects a securities company that does not log in FIX, the test cannot be performed after RFQ sending. Therefore, TSE will prepare pseudo participants to enable investors to send RFQs. | In the case where investor selects a securities company that does not log in FIX, the test cannot be performed after RFQ sending. Therefore, TSE will prepare pseudo participants to enable investors to send RFQs. | ||
In the event of a broader disaster of CONNEQTOR (staging), network equipment at the primary center, or arrownet, shown in Figure 2.1.2, the test shall be stopped until the equipment is restored, in order to resume the service in this environment. Figure 2.1.2 shows the overall configuration image of the staging environment. Investors can connect to CONNEQTOR via the arrownet. | In the event of a broader disaster of CONNEQTOR (staging), network equipment at the primary center, or arrownet, shown in Figure 2.1.2, the test shall be stopped until the equipment is restored, in order to resume the service in this environment. Figure 2.1.2 shows the overall configuration image of the staging environment. Investors can connect to CONNEQTOR via the arrownet. | ||
行 385: | 行 385: | ||
When CONNEQTOR detects a sequence Gap in a message from the investor system at the receipt of a Logon request, CONNEQTOR shall first send a Logon response to the investor system, then send a ResendRequest to request the retransmission of the message. For example, if CONNEQTOR could not receive the message from the investor system due to the system down, this sequence shall be performed. | When CONNEQTOR detects a sequence Gap in a message from the investor system at the receipt of a Logon request, CONNEQTOR shall first send a Logon response to the investor system, then send a ResendRequest to request the retransmission of the message. For example, if CONNEQTOR could not receive the message from the investor system due to the system down, this sequence shall be performed. | ||
- | {{ :: | + | {{ :: |
;#; | ;#; | ||
** Figure 6.1.9 Gap Detection when Receiving Logon request ** | ** Figure 6.1.9 Gap Detection when Receiving Logon request ** |