...
The following figure illustrates an example of this construction.
Panel |
---|
<sb:Property>
<sb:Name>java.naming.provider.url</sb:Name>
<sb:Value>tcp://soatest2:61616</sb:Value>
</sb:Property> |
In the following examples:
...
The following figure illustrates an attachment to an Apache ActiveMQ dynamic topic.
Panel |
---|
<sb:JMSConnection>
<sb:Name>JMS ActiveMQ Topic Listener - soatest2/</sb:Name>
<sb:InitialContextProperties>
<sb:Property>
<sb:Name>java.naming.factory.initial</sb:Name>
<sb:Value>org.apache.activemq.jndi.ActiveMQInitialContextFactory</sb:Value>
</sb:Property>
<sb:Property>
<sb:Name>java.naming.provider.url</sb:Name>
<sb:Value>tcp://soatest2:61616</sb:Value>
</sb:Property>
</sb:InitialContextProperties>
<sb:ConnectionFactory>ConnectionFactory</sb:ConnectionFactory>
<sb:Listeners>
<sb:JMSListener>
<sb:Destination>dynamicTopics/UemsoaStartTopicA</sb:Destination>
<sb:Actions>
<sb:JMSFileWriter>
<sb:Directory>filesystem</sb:Directory>
<sb:FilenamePattern>ActiveMQ_Topic_%Seq%.txt</sb:FilenamePattern>
<sb:StartSequenceNumber>1</sb:StartSequenceNumber>
<sb:WriteProperties>false</sb:WriteProperties>
</sb:JMSFileWriter>
</sb:Actions>
</sb:JMSListener>
</sb:Listeners>
</sb:JMSConnection>
</pre> |
Websphere Queue
The following figure illustrates an attachment to an IBM Websphere queue.
Panel |
---|
<sb:JMSConnection>
<sb:Name>JMS WebSphere Queue Listener - soatest2</sb:Name>
<sb:InitialContextProperties>
<sb:Property>
<sb:Name>java.naming.factory.initial</sb:Name>
<sb:Value>com.ibm.websphere.naming.WsnInitialContextFactory</sb:Value>
</sb:Property>
<sb:Property>
<sb:Name>java.naming.provider.url</sb:Name>
<sb:Value>iiop://soatest2:2809</sb:Value>
</sb:Property>
<sb:Property>
<sb:Name>com.ibm.CORBA.ORBInit</sb:Name>
<sb:Value>com.ibm.ws.sib.client.ORB</sb:Value>
</sb:Property>
</sb:InitialContextProperties>
<sb:ConnectionFactory>jms/SBSConnectionFactory</sb:ConnectionFactory>
<sb:Listeners>
<sb:JMSListener>
<sb:Destination>jms/Soatest2TestQueue3</sb:Destination>
<sb:Actions>
<sb:JMSFileWriter>
<sb:Directory>filesystem<sb:Directory>
<sb:FilenamePattern>Websphere_Queue_%Seq%.txt</sb:FilenamePattern>
<sb:StartSequenceNumber>1</sb:StartSequenceNumber>
<sb:WriteProperties>false</sb:WriteProperties>
</sb:JMSFileWriter>
</sb:Actions>
</sb:JMSListener>
</sb:Listeners>
</sb:JMSConnection> |
MQ Series Queue
The following figure illustrates an attachment to an IBM MQ Series Queue.
Panel |
---|
<sb:MQConnection>
<sb:Name>MQ Series Listener - soatest2</sb:Name>
<sb:Host>soatest2</sb:Host>
<sb:QueueManagerName>MyQueueManager</sb:QueueManagerName>
<sb:Channel>UpsQaChannel</sb:Channel>
<sb:Port>1414</sb:Port>
<sb:Listeners>
<sb:MQListener>
<sb:QueueName>UpsQaQueue</sb:QueueName>
<sb:Actions>
<sb:MQFileWriter>
<sb:Directory>filesystem</sb:Directory>
<sb:FilenamePattern>MQSeries_Queue_%Seq%.txt</sb:FilenamePattern>
<sb:StartSequenceNumber>0</sb:StartSequenceNumber>
<sb:WriteProperties>false</sb:WriteProperties>
</sb:MQFileWriter>
</sb:Actions>
</sb:MQListener>
</sb:Listeners>
</sb:MQConnection> |
Anchor | ||||
---|---|---|---|---|
|
...
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.
Panel |
---|
begin_event
event_id "JMS_MESSAGE_TRIGGER"
event_type FILE
comp_name uems
state enable
tracking_int 10
triggered_id "JMS_MESSAGE_HANDLER"
filespec "filesystem/*.txt"
min_file_size 0
rename_file yes
rename_filespec "filesystem/$(origname).xml"
end_event
begin_handler
handler_id "JMS_MESSAGE_HANDLER"
handler_type CMD
maxrc 0
userid username
pwd user_password
cmd "udm -s udm.script"
end_handler |
Anchor | ||||
---|---|---|---|---|
|
...
Contents of File udm.script
Panel |
---|
openclose 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
...