Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Use JMS from stand-alone clients to interoperate with service integration resources > Use JMS to connect to a WAS default messaging provider messaging engine > Configure the Thin Client for JMS with WAS
Configure the Thin Client for JMS with WAS in an OSGi environment
Use this information to install and configure the Thin Client for JMS with WAS in an OSGi environment.
To use the Thin Client for JMS with WAS in an OSGi environment import the required plug-ins into your development environment and add them to the list of required plug-ins in your product configuration.
A list of all packages exported by system.bundle can be obtained from the Execution Environment Profile being used. For example if the Execution Environment is J2SE-1.5 then the list of all packages exported by system.bundle can be obtained from the property org.osgi.framework.system.packages in the Execution Environment Profile file named J2SE-1.5.profile contained in the bundle org.eclipse.osgi_ <version>.jar
Procedure
- Application plug-ins which use the Thin Client for JMS with WAS plug-ins must import the javax.jms packages in an OSGi environment.
- If you are using connection factories that are programmatically created, the application plug-in must import the com.ibm.websphere.sib.api.jms package.
- Alternatively, if you are using JNDI lookups via the Thin Client for EJB in WebSphere Application server then the application plug-in must import the com.ibm.websphere.naming package.
- When performing JNDI lookups it is necessary that the following system property be specified: -Dorg.osgi.framework.system.packages=sun.io,com.ibm.wsspi.channel.framework, com.ibm.CORBA.channel,com.ibm.CORBA.channel.giop,com.ibm.channel.orb, com.ibm.CORBA.poa,com.ibm.CORBA.ras,com.ibm.CORBA.iiop,com.ibm.CORBA.transport