Adapter for Enterprise JavaBeans 6.5 SP3 | webMethods Adapter for Enterprise JavaBeans Documentation | webMethods Adapter for Enterprise JavaBeans Installation and User’s Documentation | Application Server Configuration Notes | WebLogic Server | Encryption
 
Encryption
Integration Server has built-in support for validating server certificates generated by the most widely-used certificate authorities. Adapter for Enterprise Javabeans can take full advantage of this capability for the purpose of establishing SSL connections to those WebLogic application installations that require it.
All supported versions of WebLogic can be configured to use SSL between the server and an EJB client. Additionally, SSL ports can be configured for either the HTTPS or T3S protocols. An EJB client may choose which of these protocols to connect with. This choice is explicitly set in the mandatory java.naming.provider.url property which must be present in the JNDI property file.
*If using HTTPS, the value of this property has the form:
java.naming.provider.url = https://WebLogic_server:port_number
where WebLogic_server and port_number are site-defined values.
*If using T3S, the value of this property has the form:
java.naming.provider.url = t3s://WebLogic_server:port_number
Though the adapter supports the use of either protocol, we recommend using the proprietary T3/T3S for performance reasons. T3 is highly optimized and multiplexes all of a client's network traffic with WebLogic over a single socket connection. This is important when using SSL because it guarantees that both JNDI and RMI packets will be encrypted.
Configuring the WebLogic server for SSL is fairly straightforward on all supported versions, though there are some minor variations in the steps taken. For configuration information, see the Oracle web site.
Note:
All versions of WebLogic support services of EJB 2.1 and earlier standards. Services of the EJB 3.0 and 3.1 standards are supported only by WebLogic 10.3 and 12c.