Cloud Application Integration (On-Premises) : Integration Server Built-In Services : Event Folder : pub.event.nerv:subscribe
pub.event.nerv:subscribe
WmPublic. Deprecated - Replaced by pub.event.routing:subscribe.
Subscribes to a particular type of event on Network for Event Routing and Variation (NERV) and identifies the service that will act as the event handler.
Note:  
NERV is a framework that enables applications to communicate using events. It uses the Apache Camel integration framework for event routing, filtering, and variation. By default, NERV uses a Camel component that is configured for JMS as the transport layer and JNDI destinations as the endpoints. For more information about using NERV and configuring other providers, see webMethods Event Processing Help.
Input Parameters
eventTypeName
String Fully qualified name of the event type to which to subscribe. For example, {http://namespaces.softwareag.com/EDA/WebM/Sample/InventoryMgmt/1.0}PartInventoryLow is an event type identifier used for inventory management. Integration Server maintains a list of default event types in the directory Integration Server_directory /common/EventTypeStore on the machine where webMethods Universal Messaging is installed.
Integration Server does not check whether the specified event type exists in NERV.
serviceName
String Fully qualified name of the flow service that Integration Server should invoke when an event is received from NERV.
Integration Server does not check whether the service specified in serviceName exists until the service is invoked.

durable
Subscription
ClientId
String Optional. Unique client identifier that designates the subscription as a durable subscription on the messaging provider.
If you provide a value for this parameter, also provide a value for durableSubscriptionName.
Durable subscriptions enable subscribers to receive messages even when the subscriber is inactive, whereas non-durable subscriptions allow subscribers to receive messages only if those messages are published while the subscriber is active. For more information about how messages are received for durable and non-durable subscriptions, see Using webMethods Integration Server to Build a Client for JMS and webMethods Broker Messaging Programmer’s Guide.

durable
Subscription
Name
String Optional. Name of the durable subscription associated with the identifier specified in durableSubscriptionClientId.
user
String Optional. Name of the user who will invoke the service specified in serviceName. Integration Server validates the user name when the service specified in serviceName is executed.
If no user name is specified here, Integration Server uses the name specified in the server parameter watt.server.event.nerv.subscribeService.user. If no user is specified in that parameter, Integration Server uses the Administrator user to execute the service.
Note:  
The user specified in this parameter can be defined either internally or in an external directory but must belong to an existing group that has appropriate ACL permissions to invoke the specified service. For more information, see webMethods Integration Server Administrator’s Guide.

eventMessage
ToDocument
java.lang.Boolean Optional. Flag indicating how Integration Server should pass the event message received from NERV as input to the service specified in serviceName.
Set to:
*True to extract the message header and body and pass the header and body in IData format to the service. This is the default.
*False to pass the message in the format it was received from NERV.
Output Parameters
None.
Usage Notes
The pub.event.nerv:subscribe service creates a subscription to a particular event type on NERV. When NERV receives a matching event, NERV routes the event to Integration Server in the form of a Camel message. Integration Server then receives the event and executes the service specified in serviceName using the credentials for the user specified in user. Integration Server passes either the message header and body, in IData format, or the entire message as it was received from NERV as specified in eventMessageToDocument for further processing. Make sure that the input signature of the service specified in serviceName matches the content passed to that service.
See Also
pub.event.nerv:send
pub.event.nerv:unsubscribe
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback