rmu-iti92 component
The rmu-iti92 component provides interfaces for actors of the Restricted Update Document Set IHE transaction (ITI-92), which is described in the (pending).
Actors
The transaction defines the following actors:
Producer side corresponds to the Update Initiator actor. Consumer side corresponds to the Update Responder actor.
Dependencies
In a Maven-based environment, the following dependency must be registered in pom.xml
:
<dependency>
<groupId>org.openehealth.ipf.platform-camel</groupId>
<artifactId>ipf-platform-camel-ihe-xds</artifactId>
<version>${ipf-version}</version>
</dependency>
Endpoint URI Format
Producer
The endpoint URI format of the rmu-iti92
component producers is:
rmu-iti92://hostname:port/path/to/service[?parameters]
where hostname is either an IP address or a domain name, port is a port number, and path/to/service represents additional path elements of the remote service. URI parameters are optional and control special features as described in the corresponding section below.
Consumer
The endpoint URI format of rmu-iti92
component consumers is:
rmu-iti92:serviceName[?parameters]
The resulting URL of the exposed IHE Web Service endpoint depends on both the configuration of the deployment container and the serviceName parameter provided in the Camel endpoint URI.
For example, when a Tomcat container on the host eHealth.server.org
is configured in the following way:
port = 8888
contextPath = /IHE
servletPath = /rmu/*
and serviceName equals to iti92
, then the rmu-iti92 consumer will be available for external clients under the URL
http://eHealth.server.org:8888/IHE/rmu/iti92
Additional URI parameters are optional and control special features as described in the corresponding section below.
Example
This is an example on how to use the component on the consumer side:
from("rmu-iti92:iti92?audit=true")
.process(myProcessor)
// process the incoming request and create a response
Basic Common Component Features
Basic Web Service Component Features
Basic XDS Component Features
Advanced Web Service Component Features
- Handling Protocol Headers
- Deploying custom CXF interceptors
- Handling automatically rejected messages
- Using CXF features