Managing Oracle SOA Suite on IBM WebSphere 4-13
f.
Search for groups using the wildcard
g. Select the Administrators group to which the wasadmin user belongs.
h. Click OK.
i. Click the Save link.
j.
Restart the server.
4.2.6.2 EJB Client
1. Generate stubs for the EJB interfaces using the createEJBStubs.sh utility and
ensure that the stubs are in the client classpath.
4.2.6.3 EJB Reference Binding
You must include the EJB stubs for the external EJB interface in the composite SCA-INFclasses or SCA-INFlib directory.
4.2.7 AQ Technology Adapter and WebSphere 7.0
For the AQ Adapter to work correctly on the WebSphere 7.0 platform, you need to use the WebSphere Application Server Console to provide specific connection factory and
data source properties.
For the connection factory, you need to set the following custom property for the connection pool: defaultConnectionTypeOverride = unshared
For the AQ adapter dataSource, ensure that validate existing pooled connections is checked. The associated interval can be set to 0. See the following
screen shot.
4-14 Oracle Fusion Middleware Third-Party Application Server Guide
Also for the AQ adapter dataSource, you must define the same property as a custom property for the connection pool by setting the following:
defaultConnectionTypeOverride = unshared
See the following screen shot.
You also need to set the maximum connections value of AQadapter J2C connection factories to a higher value than the default of 10. You can find this entry in the
WebSphere Application Server J2C connection factories - Name of AQAdapter - Connection pools panel.
Managing Oracle SOA Suite on IBM WebSphere 4-15
4.2.8 JMS Technology Adapter on WebSphere 7.0
If you are developing composite applications to run on WebSphere 7.0, you need to use the Third Party option when modelling the JMS adapter with the Default
Messaging JMS provider. You can specify that the adapter uses a third-party JMS Provider, by supplying a value to the FactoryProperties parameter in the
weblogic-ra.xml file. Specifically, you can provide the ThirdPartyJMSProvider value to the FactoryProperties parameter.
When deployed on WebSphere 7.0, the JMS Adapter will not work with an AQJMS provider, unless you use the Adapter Configuration Wizard to set
defaultConnectionTypeOverride as unshared for both the adapter connection factory pool and for the queuetopic connection factory pool. See the following screen shot.
You also need to set the maximum connections value of JMS Adapter J2C factories to a higher value than the default of 10. You can find this entry in the WebSphere
Application Server J2C connection factories - Name of JMS Adapter - Connection pools panel.
4.2.9 Oracle Database Adapter on WebSphere 7.0