Configuring Event Routing in Multiple Installations
You can provision Event Routing configuration in all runtime instances on multiple installations. For example, in all Integration Server instances on several installations, 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, you must:
Define the installations in your composite template
Add the following code snippet:
nodes:
default:
default:
port: 8093
secure: true
credentials:
username: Administrator
password: manage
envType1:
node1:
host: localhost
port: 8192
node2:
host: localhost
port: 8292
Define the layers and list the templates that should be applied
Add the following code snippet:
layers:
esb:
templates:
is-esb
er-config
bpm:
templates:
is-bpm
er-config
Define the environments
Add the following code snippet:
environments:
envType1:
param2: someValue
envType2:
param1: v1
param3: v3
Map the layers to the nodes.
This is done separately for each environment. The example below shows that the nodes for the envType2 environment are not hard-coded directly in the template, but are resolved by using input parameters.
provision:
envType1:
bpm: [node1,node2]
esb: [node2,node3]
envType2:
bpm: ${bpm.hosts}
esb: ${is.hosts}
Define the following
Event Routing template that applies to all product instances in the installation.
templates:
is-esb:
# ...
is-bpm:
# ...
er-config:
instance:
productId: * # Use * to have unified Event Routing configuration
across the installation, you can be selective if necessary
name: * # Use * again (any instance)
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.