Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
38.2.3. Dedicated Remote Server
Example 38.5. Remote JCA Server
In this example, the HornetQ live instance is stored on a remote server EAP1. The backup HornetQ instance is stored on EAP1(B). The JCA and the Applications are stored on a separate EAP2 instance.
When fail over occurs, the Application (via JCA) is serviced by a HornetQ server in its own JBoss Enterprise Application Platform instance.
Because both HornetQ instances are located on remote servers, you must configure the JCA connection factories on the EAP2 server to correctly serve applications to the live HornetQ server and the backup HornetQ server.
Procedure 38.12. Configure JCA Connection Factories
Follow this procedure to configure the Outbound and Inbound JCA connector elements in different configuration files. Ensure you copy the Key steps are identified by a step title.
- Copy the
productionserver profile, and rename it toEAP2. - On the EAP2 instance, navigate to
$JBOSS_HOME/server/EAP2/deploy/hornetq/jms-ds.xml - The default
jms-ds.xmlhas the following <config-property> configuration present in the <tx-connection-factory>.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Configure Outbound JCA Connector
Add extra <config-property> elements as described in the following code sample.Important
Substitute the [live_server_IP_address] and [live_server_port_number] with the network address locations for your live server.If you are using Discovery to set IP address/port combinations, ensure you set the appropriate parameters for <DiscoveryAddress> and <DiscoveryPort> to match your configured broadcast groups.Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Open
$JBOSS_HOME/server/EAP2/deploy/jms-ra.rar/META-INF/ra.xmlin a text editor. - In
ra.xml, search for <resourceadapter>. Configure the Inbound Connector
Replace the "The transport type" and "The transport configuration..." <config-property> elements, and their child elements with the following configuration:Important
Substitute the [live_server_IP_address] and [live_server_port_number] with the network address locations for your live server.If you are using Discovery to set IP address/port combinations, ensure you set the appropriate parameters for <DiscoveryAddress> and <DiscoveryPort> to match your configured broadcast groups.If you are using Auto Discovery, ensure you comment out ConnectorClassName and ConnectionParameters directives.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}