Configuring the Transport Layer for NERV
When you install NERV, the default transport layer for NERV is defined as nsp://<host_name>:9000.
You can configure the NERV transport layer in two ways:
By modifying the
Default JMS Provider configuration property in
Command Central.
When NERV starts, it instantiates the transport layer, as defined by the value of the Default JMS Provider property. If no such property exists, or if it has an empty value or contains an invalid configuration, NERV displays a warning message. Every time your EDA applications try to emit events using the default emit logic or to subscribe to event types, NERV produces a warning message in the log file of the corresponding Common Platform profile and any existing subscriptions to default endpoints are deleted. You must provide a valid property for the NERV transport layer and subscribe again to the endpoints.
By deploying a user-defined
NERV component bundle, which defines a Camel JmsComponent, called
nervDefaultJMS. When activated in the
Common Platform, this bundle takes precedence over the default behavior.
If a user-defined NERV component bundle is activated in the Common Platform, it takes precedence over the default transport layer defined by the value of the Default JMS Provider configuration property in Command Central. This means that all modifications to the Default JMS Provider configuration property will be ignored. If the user-defined component bundle is stopped or uninstalled, NERV re-instantiates the default component configured using the Default JMS Provider configuration property in Command Central.
