Documentation » History » Revision 11
Revision 10 (chin-yeh, 10/25/2010 05:18 PM) → Revision 11/49 (chin-yeh, 10/27/2010 02:51 PM)
{{toc}}
h1. Documentation
h2. Load Test Result (prototype) on the prototype
[[Load Test Prototype|Click here]] to see the result.
h2. Create Queue
# edit the @deploy/hornetq.sar/hornetq-jms.xml@
<pre>
<queue name="RequestQueue">
<entry name="/queue/RequestQueue"/>
</queue>
<queue name="ResponseQueue">
<entry name="/queue/ResponseQueue"/>
</queue>
</pre>
# edit the @deploy/hornetq.sar/hornetq-configuration.xml@
<pre>
<address-settings>
<!--default for catch all-->
<address-setting match="#">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<max-size-bytes>10485760</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>BLOCK</address-full-policy>
</address-setting>
<address-setting match="jms.queue.RequestQueue">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<redelivery-delay>5000</redelivery-delay>
<max-delivery-attempts>3</max-delivery-attempts>
<max-size-bytes>10485760</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>BLOCK</address-full-policy>
</address-setting>
<address-setting match="jms.queue.ResponseQueue">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<redelivery-delay>5000</redelivery-delay>
<max-delivery-attempts>3</max-delivery-attempts>
<max-size-bytes>10485760</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>BLOCK</address-full-policy>
</address-setting>
</address-settings>
</pre>
h2. Components
h3. JMS Adaptor
This adaptor consists of 2 main components:
* produce JMS message
* consume JMS message
The adaptor must works with JDK 5.0 or above.
h3. SOAP Adaptor
This adaptor consists of:
* forward XML content to web service provider with no modification on the original content
This adaptor works with JDK 5.0 or above.
h3. Web Service (Dot Com)
All of the web service request will be received from the JMS component.
h3. Web Service Mimic
Act as a proxy by receiving the web service request on behalf of the actual web service provider.
This component works together with JMS adaptor to insert web service request into JMS queue.
h3. WS Status
This component transforms the web service's response and update the respective event log in the database.
h3. XML mapper
This component transform the bean into XML.