CP-XJP
Full service legacy message switch and XML gateway
The CP-XJP™ is a dual purpose messaging component that provides full legacy switching and XML-based gateway services. CP-XJP™ pairs nicely with the CommPower CP-EXP to provide complete, end-to-end legacy to X.400/P772 services.
| As a legacy switch, the CP-XJP manages up to 256 individually configurable I/O channels through which a variety of legacy formats are sent/received/routed. |
|
|---|---|
| As a gateway, the CP-XJP translates outbound legacy messages to XML for transmission to external web or e-mail networks/systems (and vice versa). |
|
Within the CP-XJP, two subsystems exist: Legacy Services and XML Services. Each is responsible for messaging handling per its Legacy/XML framework, and also interfacing with each other in a seamless manner in support of Legacy to/from XML message flows.
Beginning with the Legacy to XML message flow, a suite of Mode I/II, SMTP, and/or file based channels are supported through which legacy messages (DD173, JANAP/ACP 128, ACP 126, NASCOP87, JJ/DD/II) are received and transmitted. Each channel is individually configurable with regard to protocol parameters, message format, security, and operational state.
As each message is received, full validation is performed in accordance with the underlying format rules that govern each message format type. Validation errors encountered result in either rejection of the message to the originator (via SVC) or submission of the erred message to the system error queue for servicing by the local operators.
Following reception, each message received is stored within the system archive where it is retained for a configurable number of days. From this archive, retrieval/rerelease operations can be requested.
Next, formal message routing is performed to determine the set of target destinations for the message. This is accomplished through analysis of the message addresses within format lines 2/7/8 (as applicable). Routing Indicators (RIs), Plain Language Addresses (PLAs), and collectives are supported. A local address book is maintained within the system to specify the action to be taken for each address the CP-XJP is responsible for.
Entries within this address book are populated manually (for local addresses, and channel assignments), and automatically via the external X.500 directory (for externally coordinated addresses).
During the message routing process, a received legacy message may be targeted for delivery to multiple channels, each of which may mandate a message format different from that received. For these destinations, the message will undergo a format translation to transform the message into a format that can be processed by the receiving system.
Following format conversion processing, the message is ready for transmission to the set of target destinations. These can be a combination of legacy and XML. Legacy transmission entails the output of the message via the applicable set of Mode I/II, SMTP, and/or file based output channels, whereas XML transmission entails the transfer of the message to a configurable directory for pickup/processing by a downstream system (such as the CP-EXP for X.400/P772 connectivity).
For the reverse processing path (XML to Legacy) a similar flow to that defined above is carried out.
In support of end-to-end message flow, the CP-XJP system supports a suite of control and service consoles for control/monitoring of the system and message correction services.