Configuring Event Routing in a Single Installation

You can provision Event Routing configuration in all runtime instances on a single installation. For example, in all Integration Server instances 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:
   # ...
  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.

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