Documentation » History » Version 11
chin-yeh, 10/27/2010 02:51 PM
| 1 | 8 | chin-yeh | {{toc}} |
|---|---|---|---|
| 2 | |||
| 3 | 1 | chin-yeh | h1. Documentation |
| 4 | |||
| 5 | 11 | chin-yeh | h2. Load Test Result (prototype) |
| 6 | 6 | chin-yeh | |
| 7 | [[Load Test Prototype|Click here]] to see the result. |
||
| 8 | |||
| 9 | 1 | chin-yeh | h2. Create Queue |
| 10 | |||
| 11 | # edit the @deploy/hornetq.sar/hornetq-jms.xml@ |
||
| 12 | <pre> |
||
| 13 | <queue name="RequestQueue"> |
||
| 14 | <entry name="/queue/RequestQueue"/> |
||
| 15 | </queue> |
||
| 16 | 9 | chin-yeh | <queue name="ResponseQueue"> |
| 17 | <entry name="/queue/ResponseQueue"/> |
||
| 18 | </queue> |
||
| 19 | 2 | chin-yeh | </pre> |
| 20 | 9 | chin-yeh | # edit the @deploy/hornetq.sar/hornetq-configuration.xml@ |
| 21 | <pre> |
||
| 22 | <address-settings> |
||
| 23 | <!--default for catch all--> |
||
| 24 | <address-setting match="#"> |
||
| 25 | <dead-letter-address>jms.queue.DLQ</dead-letter-address> |
||
| 26 | <expiry-address>jms.queue.ExpiryQueue</expiry-address> |
||
| 27 | <redelivery-delay>0</redelivery-delay> |
||
| 28 | <max-size-bytes>10485760</max-size-bytes> |
||
| 29 | <message-counter-history-day-limit>10</message-counter-history-day-limit> |
||
| 30 | <address-full-policy>BLOCK</address-full-policy> |
||
| 31 | </address-setting> |
||
| 32 | <address-setting match="jms.queue.RequestQueue"> |
||
| 33 | <dead-letter-address>jms.queue.DLQ</dead-letter-address> |
||
| 34 | <expiry-address>jms.queue.ExpiryQueue</expiry-address> |
||
| 35 | <redelivery-delay>5000</redelivery-delay> |
||
| 36 | <max-delivery-attempts>3</max-delivery-attempts> |
||
| 37 | <max-size-bytes>10485760</max-size-bytes> |
||
| 38 | <message-counter-history-day-limit>10</message-counter-history-day-limit> |
||
| 39 | <address-full-policy>BLOCK</address-full-policy> |
||
| 40 | </address-setting> |
||
| 41 | <address-setting match="jms.queue.ResponseQueue"> |
||
| 42 | <dead-letter-address>jms.queue.DLQ</dead-letter-address> |
||
| 43 | <expiry-address>jms.queue.ExpiryQueue</expiry-address> |
||
| 44 | <redelivery-delay>5000</redelivery-delay> |
||
| 45 | <max-delivery-attempts>3</max-delivery-attempts> |
||
| 46 | <max-size-bytes>10485760</max-size-bytes> |
||
| 47 | <message-counter-history-day-limit>10</message-counter-history-day-limit> |
||
| 48 | <address-full-policy>BLOCK</address-full-policy> |
||
| 49 | </address-setting> |
||
| 50 | 1 | chin-yeh | |
| 51 | 9 | chin-yeh | </address-settings> |
| 52 | </pre> |
||
| 53 | 1 | chin-yeh | |
| 54 | 9 | chin-yeh | h2. Components |
| 55 | |||
| 56 | h3. JMS Adaptor |
||
| 57 | |||
| 58 | 2 | chin-yeh | This adaptor consists of 2 main components: |
| 59 | * produce JMS message |
||
| 60 | * consume JMS message |
||
| 61 | |||
| 62 | 7 | chin-yeh | The adaptor must works with JDK 5.0 or above. |
| 63 | 3 | chin-yeh | |
| 64 | h3. SOAP Adaptor |
||
| 65 | |||
| 66 | This adaptor consists of: |
||
| 67 | 5 | chin-yeh | * forward XML content to web service provider with no modification on the original content |
| 68 | 3 | chin-yeh | |
| 69 | This adaptor works with JDK 5.0 or above. |
||
| 70 | 4 | chin-yeh | |
| 71 | 10 | chin-yeh | h3. Web Service (Dot Com) |
| 72 | |||
| 73 | All of the web service request will be received from the JMS component. |
||
| 74 | |||
| 75 | 4 | chin-yeh | h3. Web Service Mimic |
| 76 | |||
| 77 | Act as a proxy by receiving the web service request on behalf of the actual web service provider. |
||
| 78 | |||
| 79 | 1 | chin-yeh | This component works together with JMS adaptor to insert web service request into JMS queue. |
| 80 | 9 | chin-yeh | |
| 81 | h3. WS Status |
||
| 82 | |||
| 83 | This component transforms the web service's response and update the respective event log in the database. |
||
| 84 | |||
| 85 | h3. XML mapper |
||
| 86 | |||
| 87 | This component transform the bean into XML. |