Note: | Prior to deprecation, the pub.event.nerv:eventToDocument service had to be run to convert an incoming JMS message into an IS document before the service handler pub.event.nerv:subscribe could process the event. Now, the pub.event.routing:subscribe service, which replaces the deprecated pub.event.nerv:subscribe service, handles the conversion of the incoming JMS message into an IS document (IData). |
JMSMessage | Document A document reference to the IS document of type pub.jms:JMSMessage. | ||
documentTypeName | String Optional. Fully qualified name of the IS document type that specifies the structure to impose on the body of the event. By specifying a document type, you can identify: The order and dimensionality of elements. The prefix associated with each namespace in the instance document. The document type specified in documentTypeName does not need to specify every element that will appear in the resulting document. At a minimum, the document type needs to specify the elements whose structure you want to explicitly set and the elements that you want to use in pipeline mapping. If you do not specify documentTypeName, the structure of the event body is determined solely by the event document. |
evt:Event | Document A document reference to the pub.event.eda:event document type which specifies the structure of an event as a document (IData Object). |