Universal Event Monitor for SOA Configuration

Owned by
Former user (Deleted)
Mar 03, 2015
2 min read


Universal Event Monitor for SOA Configuration

Depending on which message exchange pattern (MEP) you are using - and, in the case of JMS, what JMS Provider you are using - there are several operations that may need to be configured before you can use Universal Event Monitor for SOA.

Inbound Transactions

To transact an inbound operation, you first must configure Universal Event Monitor for SOA for inbound transactions via the UAC.xml configuration file. This file specifies the listening attributes of UAC for SOAP, JMS, and MQ inbound operations, such as connection and destination information, as well as information regarding the name and location of the output file.
 

AIX

The UAC.xml file is located in /etc/universal/UAC.xml.

Linux

The UAC.xml file is located in /etc/universal/UAC.xml.

Windows

The UAC.xml file is located in %ALLUSERSPROFILE%\Application Data\Universal\conf\UAC.xml.

 

Insert new text between the line beginning with <sb:UAC and the last line, which must terminate with </sb:UAC>. An error will occur if </sb:UAC> appears in the file anywhere other than the last line.

The XML is just text; no special tools are required to create or modify an XML document.

Also, if you are using JMS or MQ for inbound operations, you must have a JMS or MQ Provider with a queue or topic configured on which UAC can listen.

Required Order of Inbound Transactions

The UAC.xml file can contain multiple definitions for inbound transactions for multiple providers. When multiple different types of inbound transactions are defined, it is important to note that there is a required order in which these definitions occur.

Multiple Types of Providers

The required order when defining multiple types of providers is:

  1. JMS providers
  2. SOAP transactions
  3. MQ Providers

Subsets

It is entirely acceptable to define a subset of these providers (including just a single provider). However, the order is still imperative.

For example:

  1. JMS providers
  2. MQ providers

or

  1. SOAP transactions
  2. MQ providers

Unacceptable Order

The following scenario(s) are not allowed:

  1. MQ providers
  2. JMS providers
  3. SOAP transactions

or

  1. SOAP transactions
  2. JMS providers

Additional Information

The following pages provide additional detailed information for Universal Event Monitor for SOA configuration: