The ITWS Information Service is implemented as a JMS-P service. All access points to the service are wholly contained within NEMS. Hence, the data, transport, and message protocols as well as the network address detailed below are applicable to NEMS only.
a.Bindings 6.a.1Weblogic Binding
The ITWS Information Service data is published in an XML format [Reference 2.p].
The ITWS Information Service messages are bound to the NEMS JMS AP protocol through the use of a Weblogic implementation of the JMS provider specific client API, as described in Section 5.1. Data Protocol.
Messages published via the NEMS JMS-P SAP consist of three parts: headers, properties and payload.
The values in the header are provided by the ITWS Information Service when the message is written to the NEMS SAP. These headers and message payloads published are described in Sections 5.b.1 and 5.c.
The JMS property options are predetermined as part of the JMS-P on-ramping process. NEMS executes message routing to JMS-C by matching the Pub/Sub messaging properties of each message to the Pub/Sub messaging properties of interest to the JMS-C as defined by the ITWS Information Service.
The ITWS Information Service delivers messages to NEMS through a Weblogic JMS implementation interface to NEMS [Reference 2.q]. Messages are subsequently routed to JMS-Cs using Pub/Sub messaging. The ITWS Information Service (JMS-C portion) receives messages from NEMS through a Weblogic JMS implementation interface to NEMS.
Physical Layer
Presentation Layer
Session Layer
Transport Layer
Network Layer
Data Link Layer
Physical Layer
Application
Processes
JMS Provider
JMS Client
TCP
IEEE 802.3
(RJ45)
IEEE 802.3
(RJ45)
Application Layer
HTTP(S)
(optional for ActiveMQ)
Presentation Layer
Session Layer
Transport Layer
Network Layer
Data Link Layer
Application Layer
Application
Processes
IP
FTI
IP
SSL(optional)
Figure : JMS AP Transport
The ITWS Information Service delivers messages to NEMS through a Weblogic JMS implementation [Reference 2.q]. Messages are subsequently routed to consumers using Pub/Sub messaging.
None.
b.End Points
The ITWS Information Service has a single end point – NEMS. Information pertaining to this end point is detailed below.
6.b.1NEMS
Harris will provide network addresses (URLs) of NEMS OPS end points using the ITWS Publisher On-Ramping Form applicable for each location.
Appendix A:Information Service XML Schema Definition (XSD)
XSD Schemas for all messages in the same order as in Section 5.c.
The last schema is for ITWS_Globals which is included in all the other messages.
MicroburstTRACONMap Schema
Share with your friends: |