Configuring Event Routing in a Single Runtime
You can provision Event Routing configuration in a single runtime instance on a specified installation. For example, in an Integration Server profile on your installation, you can define a Universal Messaging service called “MyUniversalMessaging”, and configure the default service group to use it as a source and destination service. To do this, define the following Event Routing template:
templates:
is-esb:
# ...
er-config:
instance:
productId: integrationServer
name: ${is.instance.name} # You can also fix the name such as
IS_default in the template directly
configuration:
*-EventRouting:
COMMON-WMMESSAGING-ER:
COMMON-JMS-umdefault:
alias: MyUniversalMessaging,
enabled: true,
URL: nsp://${umhost}:${umport}
service-groups:
name: default
description: The default event group includes all event types
that are not added to other defined groups
services:
service-name: MyUniversalMessaging,
service-is-reliable: true
service-usage: SourceAndDestination
Note: | The example above contains variables that use the following format: ${parameterName}. In case you use variables instead of hard-coded values, make sure you create a properties file containing values for those variables, and provide it when applying your composite templates. |
Now add the newly created Event Routing template to all layers which include product instances where you want to provision the Event Routing configuration:
layers:
esb:
description: Enterprise Service Bus layer based on Integration Server
templates:
is-esb
er-config
bpm:
description: Business Process Management layer based on Integration Server
templates:
is-bpm
er-config