We build a Java EE application which is distributed to our customers. Depending the desired deployment environment it is possible that our application is deployed on a cluster with 2, 4, 7 ... nodes.
Our application consists of several tiers where tier A connects to tier B and thus needs the configuration of remote ejb receiver functionality.
The combination of these two facts requires us to adapt the 'jboss-ejb-client.xml' file for each deployment which is less than ideal.
To make deployment more maintainable for our customers we would like to see what the alternatives are to this approach.
Could this configuration be loaded via a code API for example, since we would be able to provide the cluster name and/or outbound connection names trough our app.
We are using JBoss EAP 6.4, this is an example of how we have the file now
<?xml version="1.0" encoding="UTF-8"?>
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection-node1" />
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection-node2" />
<property name="org.xnio.Options.SSL_ENABLED" value="true" />
<property name="org.xnio.Options.SASL_POLICY_NOANONYMOUS" value="false" />
Any guidance would be greatly appreciated.
We managed to resolve this by applying Deployment Overlay's, allowing us to not touch the packaged ear and override the included meta files to tune them to the specific server's needs.
Deployment Overlays - JBoss AS 7.2 - Project Documentation Editor
Retrieving data ...