JBoss Instance Configuration to Support Deployed EJB Client Contexts: Difference between revisions
No edit summary |
|||
| Line 24: | Line 24: | ||
=Procedure= | =Procedure= | ||
=Remoting Subsystem Configuration= | ==Remoting Subsystem Configuration== | ||
Declare remoting outbound connections corresponding to the "outbound-connection-ref" declared in the deployment descriptor: | |||
<pre> | <pre> | ||
<subsystem xmlns="urn:jboss:domain:remoting:3.0"> | <subsystem xmlns="urn:jboss:domain:remoting:3.0"> | ||
| Line 43: | Line 42: | ||
</properties> | </properties> | ||
</remote-outbound-connection> | </remote-outbound-connection> | ||
... | |||
</outbound-connections> | </outbound-connections> | ||
... | ... | ||
</subsystem> | </subsystem> | ||
</pre> | |||
. | An "ejb" ApplicationRealm user will have to be created on each of the remote JBoss nodes we intend to invoke into. The procedure is described here: [[]]. | ||
We also need to declare a local "ejb-security-realm" that ... | |||
==Declare the Corresponding Socket Bindings== | |||
For each remote outbound connection, declare the corresponding outbound socket binding: | |||
<pre> | |||
<socket-binding-group ...> | <socket-binding-group ...> | ||
<outbound-socket-binding name="remote-ejb-container-socket-1"> | <outbound-socket-binding name="remote-ejb-container-socket-1"> | ||
<remote-destination host=" | <remote-destination host="1.2.3.4" port="8080"/> | ||
</outbound-socket-binding> | |||
<outbound-socket-binding name="remote-ejb-container-socket-2"> | |||
<remote-destination host="1.2.3.5" port="8080"/> | |||
</outbound-socket-binding> | </outbound-socket-binding> | ||
... | |||
</socket-binding-group> | </socket-binding-group> | ||
</pre> | </pre> | ||
where remote-outbound-connection's "name" attribute should match the remoting-ejb-receiver's outbound-connection-ref declared in jboss-ejb-client.xml. For more details about EJB client contexts, see [[EJB_Concepts#EJB_Client_Context|EJB client context]]. For more details about jboss-ejb-client.xml, the deployment descriptor that configures the EJB client context, and which requires the above configuration changes, see [[Jboss-ejb-client.xml#Required_Server_Configuration|jboss-ejb-client.xml]]. | where remote-outbound-connection's "name" attribute should match the remoting-ejb-receiver's outbound-connection-ref declared in jboss-ejb-client.xml. For more details about EJB client contexts, see [[EJB_Concepts#EJB_Client_Context|EJB client context]]. For more details about jboss-ejb-client.xml, the deployment descriptor that configures the EJB client context, and which requires the above configuration changes, see [[Jboss-ejb-client.xml#Required_Server_Configuration|jboss-ejb-client.xml]]. | ||
Revision as of 20:41, 24 March 2017
Internal
Relevance
- EAP 7.0.4
Overview
This article describes the server-side configuration required to support deployed EJB client contexts, as declared in jboss-ejb-client.xml deployment descriptors. Assuming that jboss-ejb-client.xml content is the one listed below, the following configuration changes are necessary:
<jboss-ejb-client xmlns:xsi="urn:jboss:ejb-client:1.2" xsi:noNamespaceSchemaLocation="jboss-ejb-client_1_2.xsd">
<client-context>
<ejb-receivers>
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-container-1"/>
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-container-2"/>
</ejb-receivers>
</client-context>
</jboss-ejb-client>
Procedure
Remoting Subsystem Configuration
Declare remoting outbound connections corresponding to the "outbound-connection-ref" declared in the deployment descriptor:
<subsystem xmlns="urn:jboss:domain:remoting:3.0">
...
<outbound-connections>
<remote-outbound-connection name="remote-ejb-container-1"
outbound-socket-binding-ref="remote-ejb-container-socket-1"
username="ejb"
security-realm="ejb-security-realm"
protocol="http-remoting">
<properties>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
</properties>
</remote-outbound-connection>
...
</outbound-connections>
...
</subsystem>
An "ejb" ApplicationRealm user will have to be created on each of the remote JBoss nodes we intend to invoke into. The procedure is described here: [[]].
We also need to declare a local "ejb-security-realm" that ...
Declare the Corresponding Socket Bindings
For each remote outbound connection, declare the corresponding outbound socket binding:
<socket-binding-group ...>
<outbound-socket-binding name="remote-ejb-container-socket-1">
<remote-destination host="1.2.3.4" port="8080"/>
</outbound-socket-binding>
<outbound-socket-binding name="remote-ejb-container-socket-2">
<remote-destination host="1.2.3.5" port="8080"/>
</outbound-socket-binding>
...
</socket-binding-group>
where remote-outbound-connection's "name" attribute should match the remoting-ejb-receiver's outbound-connection-ref declared in jboss-ejb-client.xml. For more details about EJB client contexts, see EJB client context. For more details about jboss-ejb-client.xml, the deployment descriptor that configures the EJB client context, and which requires the above configuration changes, see jboss-ejb-client.xml.