Applications running inside client containers

Some Java EE environments, such as WebSphere® Application Server, provide a client container that can be used to run Java SE applications.

Applications running inside of these environments use a JMS connection factory to connect to an IBM® MQ queue manager.

For applications running inside client containers:
  • CONNECTIONNAMELIST and CCDTURL are fully supported
  • CLIENTRECONNECTOPTIONS is fully supported

CONNECTIONNAMELIST property

If the Java EE environment provides a connection pool for JMS connections, see Using CONNECTIONNAMELIST or CCDT in a connection pool for information on how this affects the behavior of the CONNECTIONNAMELIST property.

If the Java EE environment does not provide a JMS connection pool. the application uses the CONNECTIONNAMELIST property in the same way as Java SE applications.

CCDTURL property

If the Java EE environment provides a connection pool for JMS connections, see Using CONNECTIONNAMELIST or CCDT in a connection pool for information on how this affects the behavior of the CCDTURL property.

If the Java EE environment does not provide a JMS connection pool. the application uses the CCDTURL property in the same way as Java SE applications.