Guest User

Untitled

a guest
Jun 23rd, 2018
95
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.07 KB | None | 0 0
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <connection-factories>
  3.  
  4. <!-- MQ JMS Provider -->
  5. <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="org.jboss.jms:service=JMSProviderLoader,name=WSMQJMSProvider">
  6. <attribute name="ProviderName">WSMQJMSProvider</attribute>
  7. <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
  8. <attribute name="FactoryRef">ConnectionFactory</attribute>
  9. <attribute name="QueueFactoryRef">SIB2B02</attribute>
  10. <attribute name="TopicFactoryRef">SIB2B02</attribute>
  11. <attribute name="Properties">
  12. java.naming.factory.initial=com.ibm.mq.jms.context.WMQInitialContextFactory
  13. java.naming.provider.url=159.165.45.81:1414/SIB2B02
  14. java.naming.security.authentication=none
  15. </attribute>
  16. </mbean>
  17.  
  18. <!-- MQ Bridge -->
  19. <mbean code="org.jboss.jms.server.bridge.BridgeService"
  20. name="jboss.messaging:service=Bridge,name=DeltaWmqBridge"
  21. xmbean-dd="xmdesc/Bridge-xmbean.xml">
  22.  
  23. <!-- The JMS provider loader that is used to lookup the source destination - defined above -->
  24. <depends optional-attribute-name="SourceProviderLoader">
  25. org.jboss.jms:service=JMSProviderLoader,name=WSMQJMSProvider
  26. </depends>
  27.  
  28. <!-- The JMS provider loader that is used to lookup the target destination -->
  29. <depends optional-attribute-name="TargetProviderLoader">
  30. jboss.messaging:service=JMSProviderLoader,name=JMSProvider
  31. </depends>
  32.  
  33. <!-- The JNDI lookup for the source destination - as defined on MQ server -->
  34. <attribute name="SourceDestinationLookup">DLN.AIRCELL.FLIFO.Q</attribute>
  35.  
  36. <!-- The JNDI lookup for the target destination - this is set up as an normal JBoss queue -->
  37. <attribute name="TargetDestinationLookup">/queue/DAL_FIG_BG_STAGING</attribute>
  38.  
  39. <!-- The username to use for the source connection
  40. <attribute name="SourceUsername">bob</attribute>
  41. -->
  42.  
  43. <!-- The password to use for the source connection
  44. <attribute name="SourcePassword">BobSecur3</attribute>
  45. -->
  46.  
  47. <!-- The username to use for the target connection
  48. <attribute name="TargetUsername">mary</attribute>
  49. -->
  50.  
  51. <!-- The password to use for the target connection
  52. <attribute name="TargetPassword">MaryS3cur3</attribute>
  53. -->
  54.  
  55. <!-- Optional: The Quality Of Service mode to use, one of:
  56. QOS_AT_MOST_ONCE = 0;
  57. QOS_DUPLICATES_OK = 1;
  58. QOS_ONCE_AND_ONLY_ONCE = 2;
  59. -->
  60. <attribute name="QualityOfServiceMode">0</attribute>
  61.  
  62. <!-- JMS selector to use for consuming messages from the source
  63. <attribute name="Selector">specify jms selector here</attribute>
  64. -->
  65.  
  66. <!-- The maximum number of messages to consume from the source before sending to the target -->
  67. <attribute name="MaxBatchSize">10</attribute>
  68.  
  69. <!-- The maximum time to wait (in ms) before sending a batch to the
  70. target even if MaxBatchSize is not exceeded. -1 means wait forever
  71. -->
  72. <attribute name="MaxBatchTime">-1</attribute>
  73.  
  74. <!-- If consuming from a durable subscription this is the subscription name
  75. <attribute name="SubName">mysub</attribute>
  76. -->
  77.  
  78. <!-- If consuming from a durable subscription this is the client ID to use
  79. <attribute name="ClientID">myClientID</attribute>
  80. -->
  81.  
  82. <!-- The number of ms to wait between connection retrues in the event
  83. connections to source or target fail
  84. -->
  85. <attribute name="FailureRetryInterval">5000</attribute>
  86.  
  87. <!-- The maximum number of connection retries to make in case of failure,
  88. before giving up -1 means try forever
  89. -->
  90. <attribute name="MaxRetries">-1</attribute>
  91.  
  92. <!-- If true then the message ID of the message before bridging will be
  93. added as a header to the message so it is available to the
  94. receiver. Can then be sent as correlation ID to correlate in a
  95. distributed request-response
  96. -->
  97. <attribute name="AddMessageIDInHeader">false</attribute>
  98.  
  99. </mbean>
  100. </connection-factories>
Add Comment
Please, Sign In to add comment