Integration Strategy
The changes proposed to be done are in the following modules/projects
EPSOS-CLIENT-CONNECTOR, IHE Service Clients
Epsos CC Client Connector
ClientConnectorServiceMessageReceiverInOut
XCPD Service Client
RespondingGateway_ServiceStub (https://bitbucket.org/openncp/protocol-terminators/src/177468556504a3a9ae12dcf1084aa55a2a8f9502/epsos-ncp-client/epsos-xcpd-ws-client/src/main/java/tr/com/srdc/epsos/ws/xcpd/client/RespondingGateway_RequestSender.java?at=develop)
XCA Service Client
RespondingGateway_ServiceStub (https://bitbucket.org/openncp/protocol-terminators/src/177468556504a3a9ae12dcf1084aa55a2a8f9502/epsos-ncp-client/epsos-xca-ws-client/src/main/java/tr/com/srdc/epsos/ws/xca/client/RespondingGateway_ServiceStub.java?at=develop)
XDR Service Client
DocumentRecipient_ServiceStub (https://bitbucket.org/openncp/protocol-terminators/src/177468556504a3a9ae12dcf1084aa55a2a8f9502/epsos-ncp-client/epsos-xdr-ws-client/src/main/java/tr/com/srdc/epsos/ws/xdr/client/DocumentRecipient_ServiceStub.java?at=develop
EPSOS-WS-SERVER, EPSOS CC Web Services
XCPD_ServiceMessageReceiverInOut (https://bitbucket.org/openncp/protocol-terminators/src/177468556504a3a9ae12dcf1084aa55a2a8f9502/epsos-ncp-server/epsos-ws-server/src/main/java/_2009/xcpd/iti/ihe/XCPD_ServiceMessageReceiverInOut.java?at=develop)
XCA_ServiceMessageReceiverInOut (https://bitbucket.org/openncp/protocol-terminators/src/177468556504a3a9ae12dcf1084aa55a2a8f9502/epsos-ncp-server/epsos-ws-server/src/main/java/_2007/xds_b/iti/ihe/XCA_ServiceMessageReceiverInOut.java?at=develop, )
XDR_ServiceMessageReceiverInOut (https://bitbucket.org/openncp/protocol-terminators/src/177468556504a3a9ae12dcf1084aa55a2a8f9502/epsos-ncp-server/epsos-ws-server/src/main/java/_2007/xds_b/iti/ihe/XDR_ServiceMessageReceiverInOut.java?at=develop)
Code Integration Points
Action | NRR | NRO | WHO | STATUS |
---|---|---|---|---|
Portal sends request to NCP-B | √ (recommended) | National implementor | DONE | |
Message received by NCP-B (not xcpd, not xca, not xdr) | √ (non IHE compliant) | NCP implementor | DONE | |
Message sent to NCP-A | √ (at NCP-B side) | NCP implementor | DONE | |
Message received by NCP-A (xcpd,xca,xdr) | √ | NCP implementor | DONE | |
Message sent from NCP-A to NI | √ (at NCP-A side in core components) | NCP implementor | DONE | |
Message received by NI | √ (recommended) | National implementor | ||
Message sent from NI To NCP-A | √ (recommended) | National implementor | ||
Message receive by NCP-A | √ (recommended) | NCP implementor | DONE | |
Message sent from NCP-A to NCP-B (xcpd,xca,xdr) | √ (recommended) | NCP implementor | DONE | |
Message received by NCP-B | √ (recommended) | NCP implementor | DONE | |
Message sent from NCP-B to portal (not xcpd, not xca, not xdr) | √ (recommended) | NCP implementor | DONE | |
Message received by portal | √ (recommended) | National implementor | DONE |
Guidelines for the national implementors shall be provided.
Tokens Storage
It has to be checked if it is possible to store this tokem to Audit Repository. If not then a new repository has to be introduces. Although as Massi said it is proposed to be inside the Audit Repository.
As a first implementation they will be stored in filesystem
The tokens are stored under %EPSOS_PROPS_PATH%/obligation/nrr and %EPSOS_PROPS_PATH%/obligation/nro and the filename includes the submission timestamp, the creation timestamp, the event type and the uuid of the message
Case of SOAP messages
{SUBMISSION_TIME_GMT}_{MSGUUID}_{EVENTTYPE}.xml
Case of NON-SOAP messages
{SUBMISSION_TIME_GMT}_{ASSERTIONID_CREATIONTIME_GMT}_{EVENTTYPE}.xml
Release Planning
The project that will be changed to achieve this functionality is https://bitbucket.org/openncp/protocol-terminators
A new version will be introduced in pom.xml named 3.3.0-SNAPSHOT (the existing is 3.2.1)
The new openncp version will be 2.2.0 (2.2.0-RC1 Release Changelog and Notes)