Tips for installing the embedded messaging feature

When installing IBM WebSphere Application Server the embedded messaging feature, selected by default, can be used as the JMS provider. To install the embedded messaging feature successfully, complete several other actions first as described in the installation procedure.

For Linux/UNIX, to use only WebSphere MQ as the JMS provider, deselect the embedded messaging feature, which installs the WAS without embedded messaging. Do installed the embedded messaging client.

If you already have WebSphere MQ installed, you can configure it as the JMS provider. Otherwise, you can install the embedded messaging feature, the WebSphere MQ product, or another JMS provider later, after you install the WAS.

The WAS embedded messaging feature provides a JMS provider that supports both queues (for point-to-point messaging) and topics (for publish and subscribe messaging). You can install the WebSphere Application Server with the embedded messaging feature on the same host with the WebSphere MQ product. To support this combination, several WebSphere MQ product features must be at a certain level.

After installing the WAS with the embedded messaging feature, you can install the WebSphere MQ product and use it as the JMS provider instead.

This topic provides an index to tips for installing and migrating the embedded messaging feature that are described in Platform-specific tips for installing and migrating.

 

Tips for all platforms

• Migrating from embedded messaging to WebSphere MQ requires setting the MQ_INSTALL_ROOT variable to the location of the installation root of WebSphere MQ

• Installing WebSphere Application Server products in order on the same machine, when installing the embedded messaging component

• Recovering from an InvalidExecutableException while starting jmsserver

• Applying fixes and fix packs to the embedded messaging feature

• Providing adequate space for installation

• Avoiding the installation of the server and client feature or the client feature more than once

• Installing the embedded messaging server feature if WebSphere MQ V5.3 is already installed

• Logging off and back on, or rebooting a Windows machine, after uninstalling the embedded messaging feature

• Planning not to use terminal services with the embedded messaging feature

• Avoiding a coexistence problem between embedded messaging, IBM WebSphere Studio Application Developer Integration Edition, and IBM WAS

• Locating more information about the embedded messaging feature or WebSphere MQ

 

Tips for all Linux and UNIX platforms

• Preparing a Linux or UNIX operating platform for the embedded messaging feature

• Installing to fixed locations on UNIX-based operating systems

• Restricting access to the /var/mqm/errors directory and messaging logging files

 

Tips for AIX platforms

• Installing the prerequisite Java130.rte.lib V1.3.0 on AIX V4.3.3 or AIX V5

• Correcting directory permissions on AIX platforms before reinstalling WAS with the embedded messaging feature

 

Tips for Linux platforms

• Ignoring YAST2 dependency conflicts for embedded messaging packages

 

Tips for Windows platforms

• Providing the required msvcp60.dll file for Windows 2000 Server

• Planning for the default installation path

---

Related tasks

1. Installing the product
2. Installing WebSphere embedded messaging as the JMS provider
3. Installing and configuring a JMS provider
4. Installation: Resources for learning

 

---