You can use interoperable naming URLs for EJB 2.0 components and clients. EAServer versions prior to 6.0 required that you use interoperable naming URLs to enable the RMI/IIOP protocol, which is required for EJB 2.0 interoperability features such as caller credential propagation. EAServer 6.0 and later always use the RMI/IIOP protocol, and you can use the simplified URL formats described in “Connection URL formats”. Interoperable naming URLs are not required to connect to EAServer.
Interoperable naming URLs may be useful when integrating other vendor’s application servers into an EAServer application, for example, when pulling messages from another vendor’s JMS implementation.
To use RMI/IIOP as the network protocol, an EJB client
must specify a corbaname
interoperable
naming URL as the value of the JNDI context’s PROVIDER_URL
property. When using corbaname
URLs,
you must specify the user name and password using the JAAS API.
When using the EAServer EJB client runtime, the URL syntax is:
corbaname:iiop:ver@host:port/NameService[rmi]
Or to use the default IIOP version number:
corbaname:iiop:host:port/NameService[rmi]
Where:
ver |
Is an optional version number. Supported
versions are 1.1 and 1.2. The default version is 1.1, unless you
append the |
host |
Is the server host name. |
port |
Is the server’s IIOP port number. |
[rmi] |
Is the optional naming prefix If connecting to EAServer 5.x, you must specify append Using this option forces the IIOP version to 1.2. |
For example, this URL specifies a connection to the host moxy at port 2000, using IIOP 1.2:
corbaname:iiop:1.2@moxy:2000/NameService
To connect to an EAServer 5.x server, which does not use valuetype
semantics by default, append #rmi
to
the URL:
corbaname:iiop:1.2@moxy:2000/NameService#rmi:/
This URL identifies a connection to the host moxy at port 2000, using IIOP 1.1:
corbaname:iiop:moxy:2000/NameService
The string /NameService
is
optional in all corbaname
URLs.
For example:
corbaname:iiop:1.2@moxy:2000#rmi:/
Or:
corbaname:iiop:1.2@moxy:2000