How to configure EJB IIOP bindings to include the fully qualified path in JBoss EAP 7 / 6

Environment

• Red Hat JBoss Enterprise Application Platform (EAP)
  • 7.x
  • 6.x

Issue

• How to configure EJB IIOP bindings to include the fully qualified path in JBoss EAP 7.1

Resolution

Run this CLI command on the EJB3 subsystem:

/subsystem=ejb3/service=iiop:write-attribute(name=use-qualified-name,value=true)

It will set the attribute on the iiop element under the ejb3 subsystem:

        <subsystem xmlns="urn:jboss:domain:ejb3:5.0">
...
            <iiop enable-by-default="false" use-qualified-name="true"/>
...

For an example EJB HelloSessionBean when use-qualified-name=false, the IIOP client application would lookup HelloSessionBean. When use-qualified-name=true, the lookup would be iiop-eap7/HelloSessionBean

INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
...
	java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
	java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
...

Related Solutions:

How to expose an EJB via IIOP and call it in JBoss EAP 7 / 6

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.