Inbound Implementation - JMS

Inbound implementations take the form of modifying the UAC.xml file with a definition. The container will read this file to construct the connection to the target defined by the value of the Property java.naming.provider.

The following figure illustrates an example of this construction.

In the following examples:

Messages consumed from the topic or queue are written to the file system defined by the <sb:Directory> tag.
<sb:Filename> tag denotes the filename that is be written to the filesystem.
%Seq% defines an increment so that subsequent messages consumed from the topic do not collide with already existing filenames.

ActiveMQ Topic

The following figure illustrates an attachment to an Apache ActiveMQ dynamic topic.

Websphere Queue

The following figure illustrates an attachment to an IBM Websphere queue.

MQ Series Queue

The following figure illustrates an attachment to an IBM MQ Series Queue.

Triggering an Event

Once a file has been written to the file system, UEM could be used to trigger an event, as shown in the following figure.

This event, which would be loaded by UEMLoad, looks for files with an extension of txt. When it sees a file with that extension, UEM renames the file to the original name with an xml extension. It then executes the handler, which runs a system command to move the file.

The UDM script looks for all files that begin with a 2 and end with .xml on the local server. These file are then transferred to the destination server, overwriting any existing files on the destination server, and the session is closed.

Event Options

The Event options used in this example are:

Option	Description
event_id	Identifier that uniquely identifies an event definition record.
event_type	Type of system event represented by the event definition record.
comp_name	Event-driven UEM Server responsible for monitoring the event.
state	Event definitions that should be processed or ignored by UEM.
tracking_int	Event definitions that should be processed or ignored by UEM.
triggered_id	ID of an event handler record that UEM will execute when an event occurrence is triggered.
filespec	Name of a file to monitor.
min_file_size	Size a file must be in order to be considered complete by UEM.
rename_file	Specifies whether or not UEM should rename a monitored file when an event occurrence is triggered.
rename_filespec	Specifies how a file should be renamed when an event occurrence is triggered.
handler_id	Identifier that uniquely identifies an event handler record.
handler_type	Type of process executed for the event handler.
maxrc	Highest value with which a handler can exit to still be considered as having executed successfully.
userid	ID of a user account in whose security context the handler process will be executed.
pwd	Password for the user account specified by userid.
cmd	Command to execute on behalf of the event handler.

Contents of File udm.script

open dest_server=192.168.1.1 user=qatest pwd=qatest
attrib dest_server createop=replace
forfiles local=2*.xml
   copy local=$(_file)
end
close

Components

Universal Event Monitor

UEMLoad

Universal Event Monitor for SOA