Install Network Deployment on Solaris platforms: WAS ND

Installing Network Deployment on Solaris platforms

This topic describes how to install the WebSphere Application Server Network Deployment product on a Solaris operating environment platform.

Overview

You cannot install the product correctly as a non-root user. If you back up the product CD-ROM, do so as root. Backup copies made from non-root users do not preserve the correct file attributes and do not work.

If you encounter a problem such as not having enough temporary space or not having the right packages on your system, cancel the installation, make the required changes, and restart the installation.

The installation uses InstallShield for Multiplatforms (ISMP) to perform the installation. You can use the Installation wizard or perform the installation from a command line, using the silent installation method.

Installation programs in WebSphere Application Server products

Product Link to installation procedure Label on product CD
(Base) WebSphere Application Server Base product installation Application Server, IBM HTTP Server
Network Deployment Network Deployment installation (which links to this procedure!) Deployment Manager
WebSphere Business Integration Server Foundation Integration Server installation Integration Server Disk 1 and Integration Server Disk 2

Use the Network Deployment installation image to manage a multimachine environment, where you have installed the base product on different machines and want to manage the Application Servers in a group, or cell. If you buy the Network Deployment product, you also get the base product in the package.

WebSphere Business Integration Server Foundation is the V5.1 level of the Enterprise product. WebSphere Business Integration Server Foundation, V5.1 extends the base WebSphere Application Server V5.1 product. After migrating the underlying product to V5.1, do not reinstall the V5.0.x Enterprise product. V5.0.x of the Enterprise product does not extend V5.1 of the base WebSphere Application Server product nor does it extend the V5.1 Network Deployment product.

If you buy the WebSphere Business Integration Server Foundation product, you also get the Network Deployment product and the base product in the package.

Creating multiple Application Servers on a single machine

Although you can create multiple servers on a base WebSphere Application Server node, the servers all share one set of configuration files. Changes that you make to one server affect the others. Configuration documents might become corrupted. The wsinstance command can create multiple configuration instances. Each instance is a stand-alone Application Server with its own set of configuration files. Or install the Network Deployment product to create and manage multiple base Application Servers.

Order of installation

Install the base product before installing the Network Deployment product when installing both products on the same machine. Install the Network Deployment product before the Integration Server product that extends the Network Deployment product. You can install the Integration Server product before the base product. The Integration Server product can install the base product in what is known as an umbrella installation but Integration Server cannot install the Network Deployment product. Some features of the base product cannot be installed by Integration Server.

The embedded messaging feature that is included in the default installation requires that you install base before Network Deployment when installing both on the same machine. Otherwise, the order does not matter. See the following installation tip for more information:
Installation tip

Operating platform Tip in Platform-specific tips for installing and migrating
All platforms Installing WebSphere Application Server products in order on the same machine, when installing the embedded messaging component

This topic is available in Adobe PDF format on the product CD-ROM and online in an information center. The information center always has the most current information. The information center displays in the language of your machine locale if possible.

The installation guide PDF is updated occasionally. Download a new installation guide from:

ftp://ftp.software.ibm.com/software/webserver/appserv/library/wasv51nd_gs.pdf

Overview
The Launchpad tool lets you access the product overview, the readme.html file, and the installation guide. See Using the Launchpad to start the installation.
You also use the Launchpad during the installation procedure to install the product. The installation program performs the following actions:

Checks prerequisites automatically

Looks for a previous WebSphere Application Server installation, to determine whether to display the Migration panel or the Coexistence panel during the installation

A known problem with the Launchpad can prevent it from using Netscape to open the documentation links.

If you use the Mozilla browser, some Launchpad links do not work. The Launchpad attempts to call the Netscape browser in the /usr/bin/netscape directory. Try a symbolic link to the Mozilla browser to fix the problem as shown in the following example:

ln -sf /usr/bin/mozilla /usr/bin/netscape

You can also launch the following links directly from your browser:

Product Overview

http://www.ibm.com/software/webservers/appserv/
It is possible that your security options might prevent redirection, such as to the http://www-306.ibm.com/software/info1/websphere/index.jsp?tab=products/appserv Web site. If so, you can identify the IBM Web site as a trusted site to allow the redirection. For example, on Internet Explorer, add http://www-306.ibm.com to the list of Trusted Sites by selecting Tools > Internet Options > Security (tab) > Trusted Sites.

Readme File

CD-ROM mount point/readme/readme_en.html

Installation Guide

CDROM/docs/InstallGuide_en.PDF
The Installation Guide is in Adobe PDF format. Viewing this document requires you to have Adobe Acrobat Reader, which is a free download from the Adobe Acrobat Web site .

After using the Launchpad to view product documentation, perform the following procedure. The procedure includes several preliminary steps before actually launching the installer program.

Log on as root.
You cannot install the product correctly as a non-root user on a Linux or UNIX-based operating system platform, or from a user ID on a Windows platform that is not part of the administrators group. If you back up the product CD-ROM on a Linux or UNIX platform, do so as root. Backup copies made from non-root users do not preserve the correct file attributes and do not work.

In addition, Linux and UNIX installers must verify that the umask setting is 022. To verify the umask setting, issue the following command:

umask

To set the umask setting to 022, issue the following command:

umask 022

Set a shadow password for the /etc directory.
Verify that the /etc directory contains a shadow password file. The shadow password file is named shadow and is in the /etc directory. If the shadow password file does not exist, an error occurs after enabling global security and configuring the user registry as local operating system.

To create the shadow file, run the pwconv command (with no parameters). This command creates an /etc/shadow file from the /etc/passwd file. After creating the shadow file, you can configure local operating system security.

Stop all WebSphere Application Server-related Java processes on the machine where you are installing the product.

Stop any Web server process such as the IBM HTTP Server, if you are extending the base product.

Provide adequate disk space.
The Network Deployment product requires the following disk space:

460 MB for the /opt/WebSphere/DeploymentManager directory

The installation root directory includes the base product code.

150 MB for the /tmp directory

The temporary directory is the working directory for the installation program.
Verify that you have at least 100 MB of free space to avoid problems.

A message about free space occurs when less than 4 MB of free space remains after starting the installation. The InstallShield for MultiPlatforms (ISMP) program displays a message about using the -is:tempdir parameter to identify an alternate temporary space directory.

Ignore any -is:tempdir message. The -is:tempdir parameter is not supported. Cancel the installation, allocate a total of 100 MB of free space in the /tmp directory, and start the installation again.

610 MB total requirement without the embedded messaging feature

The total amount of space required includes the /tmp space, which is released after installation. Space requirements for the embedded messaging feature are described after the next few steps that describe setting up required users and user groups for the feature.

The Installation wizard displays required space for individual features on the Feature selection panel. The Installation wizard also warns you if you do not have enough space to install the product.

If you plan to migrate applications and the configuration from a previous version, verify that application objects have available disk space. As a rough guideline, plan for space equal to 110 percent of the size of the application objects:

For V3.5.x: The size of application Java archive (JAR) files, Web archive (WAR) files, and servlet files

For V4.0.x: The size of EAR files

For V5.0.x: The size of EAR files

Define the user groups and the user needed for the embedded messaging feature.

If you have not already done so, create the mqm and mqbrkrs user groups.

Create the mqm user.

Add the mqm and root users to the mqm group.

Add the user root to the mqbrkrs group.

The recommended user ID for running the JMS server process is root. If you do run the JMS server process under another user ID, add that user ID to the mqm and mqbrkrs groups. User IDs longer than 12 characters cannot be used for authentication with the embedded WebSphere JMS provider.

The mqm user starts the JMS server for general JMS support and the WebSphere embedded broker for WebSphere Application Server topic connections.

Put the user groups into effect when you next start WebSphere Business Integration Server Foundation. For example, either log off and on again with the process user ID or open a new shell in which to start WebSphere Business Integration Server Foundation.

Log off and back in as root to pick up the secondary user groups, mqm and mqbrkrs.Use the ssh command instead of the telnet command to log in. Or run the following command after logging on:

su -

Use the id -a command or the groups command to see defined groups for root. If mqm and mqbrkrs are not in the list that is returned, you cannot install the embedded messaging feature:

[root@wasdoc2 root]# id -a uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon), 3(sys),4(adm),6(disk),10(wheel),500(mqm),501(mqbrkrs) [root@wasdoc2 root]# groups root bin daemon sys adm disk wheel mqm mqbrkrs

Allocate adequate disk space for the embedded messaging feature if you are planning to install the feature.The installation locations for the embedded messaging feature are fixed as shown in the following table, which lists the locations for the base messaging functions and the messaging broker functions for publish/subscribe messaging.
Space requirements for the embedded messaging feature on Solaris

Component Base code Broker code Base data
Path /usr/ mqm /usr/ opt/ wemps /var/ mqm
Client subfeature 15 MB 15 MB 15 MB

Prepare to install the embedded messaging feature with WebSphere MQ.The embedded messaging feature is based on the IBM WebSphere MQ product. The feature and the product each provide a Java message service (JMS) function that supports queues for point-to-point messaging and topics for publish and subscribe messaging.
You can install the embedded messaging feature with or without the WebSphere MQ product on the same machine. To support both the embedded messaging feature and the WebSphere MQ product on the same machine, the WebSphere MQ product must be at a certain fix level and must have several of its features installed.

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

Even though you might decide now to install only the embedded messaging feature, you can install the WebSphere MQ product later and use the IBM WebSphere MQ product as the JMS provider instead.

Verify that you have upgraded to WebSphere MQ 5.3 with the CSD04 update to install embedded messaging on a machine where you already have WebSphere MQ installed.Determine if your WebSphere MQ 5.3 installation is at the required level by running the mqver utility provided by WebSphere MQ.
The required level as indicated by mqver is shown below:

Name: WebSphere MQ Version: 530.4 CSD04 ...

Verify that you have installed the required WebSphere MQ 5.3 features to install embedded messaging on a machine where you already have WebSphere MQ installed.When installing the embedded messaging client feature, the required MQ feature is Java messaging.

Create and mount a journalized file system called /var/mqm for your messaging working data.Use a partition strategy with a separate volume for embedded messaging or WebSphere MQ data to isolate system activity from the potentially high volume of messaging work that can build up in the /var/mqm directory.

Create separate file systems for log data in the var/mqm/log directory and error files in the var/mqm/errors directory. Store log files on a different physical volume from the embedded messaging queues, which are in the var/mqm directory. This ensures data integrity in the case of a hardware failure. If you are creating separate file systems, allow the following minimum free space:

30 MB

/var/mqm

20 MB

/var/mqm/log

4 MB

/var/mqm/errors

The /var file system stores all the security logging information for the system and stores the temporary files for e-mail and printing. Therefore, it is critical that you maintain free space in /var for these operations. If you do not create a separate file system for messaging data, and /var fills up, all security logging stops on the system until free space is available in /var. Also, e-mail and printing do not work without some available free space in /var.

You have the same options for creating file systems for the embedded messaging feature as you do for WebSphere MQ. For example, if you cannot install the embedded messaging options in the required file system (for example, if it is too small), you can do one of the following before installing the Embedded Messaging options:

Create and mount a new file system for the installation directory.

Create a new directory anywhere on your machine, and create a symbolic link from the required installation directory to the new directory. For example:

mkdir /bigdisk/mqm ln -s /bigdisk/mqm /usr/mqm

Set kernel values to support the embedded messaging feature. Several Solaris kernel values are typically too small for the embedded messaging options. Starting the internal JMS server or client with insufficient kernel resources produces a First Failure Support Technology (FFST) file in the /var/mqm/errors directory.
Before installing embedded messaging, review the machine configuration:

sysdef -i

The kernel values are set in the /etc/system file, as shown in the following example.

set shmsys:shminfo_shmmax = 4294967295 set shmsys:shminfo_shmseg = 1024 set shmsys:shminfo_shmmni = 1024 set semsys:seminfo_semaem = 16384 set semsys:seminfo_semmni = 1024 set semsys:seminfo_semmap = 1026 set semsys:seminfo_semmns = 16384 set semsys:seminfo_semmsl = 100 set semsys:seminfo_semopm = 100 set semsys:seminfo_semmnu = 2048 set semsys:seminfo_semume = 256 set msgsys:msginfo_msgmap = 1026 set msgsys:msginfo_msgmax = 65535 set rlim_fd_cur=1024

You can change kernel values by editing the /etc/system file then rebooting the operating system. For more information about setting up the Solaris system, see the Solaris System Administration documentation . For example, the Solaris Tunable Parameters Reference Manual .

Queue managers are generally independent of each other. Therefore system kernel parameters, for example shmmni, semmni, semmns, and semmnu need to allow for the number of queue managers in the system.

Verify that prerequisites and corequisites are at the required release levels.Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WebSphere Application Server supported hardware, software, and APIs Web site if you have not already done so. Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
Solaris 9 SPARC workstations require the following patches:

112874-16 SunOS 5.9: patch libc

113319-12 SunOS 5.9: libnsl nispasswdd patch

115545-01 SunOS 5.9: nss_files patch

115542-01 SunOS 5.9: nss_user patch

115544-01 SunOS 5.9: nss_compat patch

Solaris 8 SPARC workstations require the following patches:

115827-01 SunOS 5.8: /sbin/sulogin and /sbin/netstrategy patch

115583-01 SunOS 5.8: /usr/lib/nss_user.so.1 patch

108820-02 SunOS 5.8: nss_compat.so.1 patch

113648-02 SunOS 5.8: /usr/sbin/mount patch

108993-27 SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch

108528-24 SunOS 5.8: kernel update patch

Refer to the IBM WebSphere Application Server supported hardware, software, and APIs Web site for a complete list of required patches.

Some operating systems that were not supported at the time that this product was shipped on CD-ROM might now be supported. You might receive a message from the prereqChecker program that an operating system is not supported when, in fact, the operating system is supported.

Always consult the IBM WebSphere Application Server supported hardware, software, and APIs Web site to determine whether your operating system is supported when you receive a message from the prereqChecker program. The Web site lists all supported operating systems and the operating system fixes and patches that install to have a compliant operating system. After confirming that your operating system is supported and that you have installed all necessary patches, you can click Next to continue an installation when you receive an error message from the prereqChecker program.

Verify the system cp command when using emacs or other freeware.
If you have emacs or other freeware installed on your HP-UX system, verify that the system cp command is being used.

Type which cp at the command prompt before running the installation program for the WebSphere Business Integration Server Foundation product.

Remove the freeware directory from your PATH if the resulting directory output includes freeware. For example, if the output is similar to this /opt/freeware/bin/cp message, remove the directory from the PATH.

Install the WebSphere Application Server Network Deployment product.

Add the freeware directory back to the PATH.

If you install with a cp command that is part of a freeware package, the installation might appear to complete successfully, but the Java 2 SDK that the product installs might have missing files in the install_root/java directory.

Missing files can destroy required symbolic links. If you remove the freeware cp command from the PATH, you can install the Network Deployment product successfully.

Perform the following step to verify that the Java 2 SDK is working correctly.

Verify the Java 2 SDK on the WebSphere Application Server Network Deployment CD. If you copied the product CD to back it up and are using a backup version, perform the following steps to verify that the Java 2 SDK on the product CD-ROM is working correctly.

Change directories to the /sun/WAS/jdk/java/bin directory on the product CD-ROM.
For example:

cd /mnt/sun/WAS/jdk/java/bin

Verify the Java 2 SDK version.
Type the following command:

./java -version

The command completes successfully with no errors when the Java 2 SDK is intact.

Select the Installation wizard method or the silent installation method but do not start the installation yet.The installer program has two interfaces, the Installation wizard and a silent command-line installation.
Performing the installation with the wizard

You can start the Installation wizard using the Launchpad or directly using the install command.

The default installation method is to open a command window and issue the command to start the Launchpad tool. Click the Install the product option on the Launchpad. (See Using the Launchpad to start the installation.)

This option launches the Installation wizard in the language of your machine locale unless there is no translation for your locale, in which case you receive the English version.

A short delay occurs before the ISMP wizard displays. You do not need to click the Install the product option more than once to cause the wizard to display. The delay is particularly noticeable on x-windows platforms.

You can also start the Installation wizard using the /cdrom/cdrom0/sun/install command, where /cdrom/cdrom0 is the mount point for the product CD-ROM and sun is the platform directory.

Performing a silent installation

You can perform a silent installation using the -options responsefile parameter with the command method:

fully_qualified_CD_pathname/install -options fully_qualified_hard_disk_drive_path_name/responsefile # /cdrom/sun/install -options /tmp/my_responsefile

Start the silent installation with a fully qualified path to the options response file. Otherwise, the Installation wizard starts.

A silent installation causes the installation program to read your responses from the options response file, instead of from the wizard interface. You must customize the responsefile before installing silently. See Customizing the Network Deployment options response file.

After customizing the file, you can issue the command to silently install. See Installing silently.

After issuing the command, the following text displays:

# ................................... .InstallShield Wizard Initializing InstallShield Wizard... Searching for Java(tm) Virtual Machine...

The silent installation runs without displaying status to the window:

Press Enter when the installation is complete to return to the command prompt.

Press Enter at any time to return from a background job to the command prompt.

You can change the -W launchPRTBean.active option in the response file to display the Registration panel to indicate the completion of a silent installation on a local system with a graphical user interface.

To determine the status of the silent installation, review the installation logs in the install_root/logs directory or in the /tmp directory. See Troubleshooting the installation for more information about log files.

Silent installation is particularly useful if you install the product often.

The rest of this procedure assumes that you are using the Installation wizard. Corresponding entries in the response file exist for every prompt that is described as part of the wizard.

Review the description of the responsefile for more information. Comments in the file describe how to customize their options.

Asynchronous and synchronous command lines

After running the install command, the command line returns synchronously. A synchronous install command returns the command line after the installation is complete.

You can start the installation asynchronously with the installation process and its children processes all running as background processes. Consult your operating system documentation to learn how to issue asynchronous commands. After running the install command, the command line returns immediately.

Do not misinterpret an asynchronous command line to mean that the installation has finished when the command prompt returns. Although the command line returns, either the Installation wizard or a silent installation might still be in progress.

Installing with a network file system mount

If use an NFS mount, see the following installation tip:
Installation tip

Operating platform Tip in Platform-specific tips for installing and migrating
All platforms Platform-specific issues when dealing with network file systems

If you have uninstalled WebSphere Application Server Enterprise Edition V4.1, remove any entries from the /usr/bin/jitk.db file. Remove any remaining artifacts from an uninstalled Enterprise Edition V4.1 system to prevent the display of the Coexistence panel or the Migration panel during installation.
The Installation wizard for WebSphere Business Integration Server Foundation might display the Migration panel or the Coexistence panel even though you have uninstalled WebSphere Application Server Enterprise Edition V4.1. You can prevent the Installation wizard from recognizing a previously deleted version of Enterprise Edition by removing the following entry from the /usr/bin/jitk.db file:

WebSphere Enterprise Edition Server 4.1

Remove other V4.x entries for WebSphere Application Server products that are no longer on your system.

Insert the product CD-ROM labeled, Deployment Manager into a CD drive to automatically mount the drive.
If the Solaris machine is configured to auto mount CDs, Solaris automatically mounts the product CD.

Open a shell window if Solaris did not automatically mount the CD.Use the same shell window throughout the installation procedure.

Start the installation with the /cdrom/cdrom0/sun/launchpad.sh command, where /cdrom/cdrom0 is the mount point for the product CD-ROM and sun is the platform directory on the CD. You can also start the installation with the /cdrom/cdrom0/sun/install command:

# /cdrom/cdrom0/sun/install

The readme link in the Launchpad is to the readme.html file in the CD root directory. The Getting Started document that contains installation information is in the docs directory on the CD.

Download a new installation guide at ftp://ftp.software.ibm.com/software/webserver/appserv/library/wasv51nd_gs.pdf .

The rest of this procedure assumes that you are using the Installation wizard. Corresponding entries in the response file exist for every prompt that is described as part of the wizard. Review the description of the responsefile for more information. Comments in the file describe how to customize the options.

Click Next to continue.The license agreement displays.
The Installation wizard does not support hot keys, such as Alt-N. You can tab to Next and press Enter to select it, for example.

Click the radio button beside the I accept the terms in the license agreement message if you agree to the license agreement and click Next to continue.After you accept the licensing terms, the Installation wizard checks for prerequisites and for previous versions, with which it can either migrate or coexist.
As the Network Deployment product version changes, its prerequisites and corequisites change.

The Network Deployment product simplifies migrating product prerequisites, by providing the option to install a complimentary Java 2 SDK on your supported operating system. You can uninstall back-level prerequisites and let the Installation wizard install current versions.

If the wizard finds a previous version of WebSphere Application Server, it prompts you to migrate applications and the configuration from the previous version, or to coexist with it. If it finds more than one previous version, the Installation wizard lists them for you to select which one to migrate. As of V5.1, the Installation wizard also lists WebSphere Application Server - Express as a candidate for automatic migration, when detected.

Use the same cell name when migrating Network Deployment from V5.0.x to V5.1.x. If you use a different cell name, federated nodes cannot successfully migrate to the Network Deployment V5.1.x cell.

You can use a different node name, if you prefer, when migrating Network Deployment from V5.0.x to V5.1.x. However, use the administrative console after installation, to change the Secure Sockets Layer (SSL) settings that mention the node name.

Migrating or coexisting with an existing WebSphere Application Server node that Solaris does not recognize.

In some cases, the InstallShield for MultiPlatforms (ISMP) program does not detect a previously installed version of WebSphere Application Server because of a failure to read the registry keys on Solaris. You can force the migration and coexistence panel to display, by starting the installation with an option on the /cdrom/sun/install command.

For example, use this command:

./install -W previousVersionDetectedBean.previousVersionDetected="true"

You can also force the appearance of the coexistence panel to change conflicting port number assignments. For example, force the coexistence panel to appear using this command:

./install -W coexistenceOptionsBean.showCoexistence="true"

On either panel, identify the location of the existing product instance to cause it to be recognized.

Use the same cell name when migrating Network Deployment from V5.0.x to V5.1.x. If you use a different cell name, federated nodes cannot successfully migrate to the Network Deployment V5.1.x cell.

You can use a different node name, if you prefer, when migrating Network Deployment from V5.0.x to V5.1.x. However, use the administrative console after installation, to change the Secure Sockets Layer (SSL) settings that mention the node name.

Choose whether to install additional features or to install the product again, when there is a previous installation of the same level product.You can add features at any time, by running the installation wizard again.
This installation wizard panel appears when the installer program detects a previous installation at the same product level. The panel lets you select whether to add features to the existing installation, or perform a new installation to another directory.

If you intend to install additional features, follow this procedure to avoid component regression problems:

Uninstall any interim fixes.

Uninstall any cumulative fixes you installed, starting with the last one and finishing with the first one.

Uninstall any fix packs you installed, starting with the last one and finishing with the first one.

Log off as root and back on.

Install new features.

Install the most current fix pack.

Install the most current cumulative fix.

Install any interim fixes to bring the node back to its previous fix level.

Use the administrative console on the Network Deployment node to synchronize all node agents.

Choose to migrate applications and the configuration from a previous version, to coexist with another version, or to neither coexist or migrate. Click Next to continue.See Migrating and coexisting for more information.
All WebSphere Application Server products on a single machine share some of the code in the embedded messaging feature, if installed. The required level of the embedded messaging feature for V5.1 (CSD04) is not the same as for V5.0.0 or V5.0.1. The required level of the embedded messaging feature for V5.1 is the same as for V5.0.2.

If you attempt to install V5.1 on a machine where a version of the embedded messaging feature is at a release level earlier than CSD04, the installer program displays the message log in a panel. The message that you see is similar to one of the messages in the following example:

MQSeries or WebSphere MQ server at an earlier release than required to support embedded messaging is already installed on the system. Unsupported earlier maintenance level of MQSeries or WebSphere MQ detected. Unsupported earlier release of MQSeries client or WebSphere MQ client detected. Unsupported maintenance level of MQSeries client or WebSphere MQ client detected. Software conflict with MQSeries JMS SupportPac MA88 detected.

To correct the problem, perform one of the following actions:

Upgrade the full MQSeries or WebSphere MQ product to WebSphere MQ at the latest level that supports embedded messaging (CSD04).
See Installing WebSphere embedded messaging as the JMS provider for more information.

Uninstall the existing MQSeries or WebSphere MQ product if MQSeries or WebSphere MQ is not required on this system and reinstall the WebSphere Application Server product. Select the embedded messaging feature.
The MQSeries JMS SupportPac MA88 problem is slightly different. Uninstall the MQSeries JMS SupportPac MA88 and reinstall the WebSphere Application Server product, selecting the embedded messaging feature. The function provided by SupportPac MA88 is included in the embedded messaging feature.

You can upgrade the WebSphere Application Server product to V5.0.2 before migrating it to V5.1 to avoid any problem with an incorrect level of the embedded messaging feature. See Upgrading a V5.0.0 or V5.0.1 product to V5.0.2.

You can also perform the procedure for migrating V5.0.0 or V5.0.1 with embedded messaging to V5.1. See Migrating V5.0.0 or V5.0.1 of WebSphere Application Server with embedded messaging to V5.1.

To share embedded messaging in a coexistence environment, the node names for each installation must be unique, so that each installation has a message queue manager that is named uniquely. To migrate V5.0.2 to V5.1, the node names must be identical. Therefore, the queue manager names are also identical, if you are migrating from V5.0.2 to V5.1.

To prevent losing the queue manager when you uninstall V5.0.2 (or V5.1), create a dummy queue manager before uninstalling one of the WebSphere Application Server versions. A series of migration topics in Migrating and coexisting describe how to migrate after the installation.

The first rule of migration is to migrate after you install WebSphere Business Integration Server Foundation, if you are planning to install the Integration Server:

If you are planning to install these products: Select the migration option while installing this product:
Network Deployment Integration Server Network Deployment Integration Server
X

X

X X

X

The exception to the rule is to migrate V3.5.x to V5.1 during the installation of the base product or the Network Deployment product, before extending either product.

Migrating Integration Server also migrates the product that Integration Server extends.

You can perform a silent migration or configure for coexistence during a silent installation. Refer to Installing silently for a description of performing a silent installation, including the options that you can specify.

The migration prompt appears only when the Installation wizard detects a previous version. The coexistence prompt appears when the Installation wizard detects any other installation, including another Version 5 installation.

If you choose to coexist, the wizard displays a Port selection panel, where you can specify port assignments that do not conflict with existing ports. For example, you can change the HTTP transport port for coexistence, from 9081 (one more than the default V5 port number) to 9085 or higher, to avoid potential conflicts with port numbers that previous versions of WebSphere Application Server commonly use.

Use the netstat -a command to display all ports in use.

If you choose neither the migration option nor the coexistence option, you can run V5.1.x and the previous version, but not at the same time. Although it is possible that both versions might coexist without port conflicts, you can ensure that both versions run together by selecting the coexistence option and checking for conflicting port assignments.

The Migration panel lists all previous releases that it can identify. If you highlight a release, the text boxes labeled, "select previous version," show the location of the previous product. Select the product to migrate. If you do not see the previous version that you intend to migrate, click Select previous version to enter a location and configuration file name if you are migrating a WebSphere Application Server Advanced Edition Single Server Edition, V4.0.x installation.

The field labeled "Configuration file" is valid only for WebSphere Application Server Advanced Edition Single Server Edition, V4.0.x. For the other versions of WebSphere Application Server that are supported by migration (Version 3.5 Standard Edition, V3.5 Extended Edition, and V4.0 Advanced Edition), the admin.config file provides the host and port values for the administrative server. If you use a file name other than admin.config, issue the commands that call the migration tools instead of migrating while installing. Issuing the commands that call the migration tools is described in Migrating and coexisting.

Migrate V3.5.x to V5.1 during the installation of the base product or the Network Deployment product, before installing the Integration Server product.

You must start the administrative server of some previous versions so that the Installation wizard can export the configuration from the admin.config file.

Although you might select migration at this point in the installation process, the actual migration does not begin until after the V5 installation is complete. At that time, if the WASPreUpgrade tool fails, the Installation wizard does not call the WASPostUpgrade tool to complete the migration, but instead displays the WASPreUpgrade.log and WASPostUpgrade.log log files for you to diagnose the problem. After fixing the problem, such as starting the administrative server of a previous release, you can start the migration again, as described in Migrating and coexisting.

Select features to install and click Next to continue. A description of each feature appears at the bottom of the panel when you roll the cursor over the feature.
Choose from these features:

Deployment manager

Installs the product run time. It provides high performance and scalability across your deployment environment. It includes multiserver administration, server clustering, load balancing and workload management for hosting highly available e-business applications.

Web services

The UDDI registry and the IBM Web Services Gateway are enterprise applications that you can deploy to:

A base WebSphere Application Server product node federated within a Network Deployment cell

A stand-alone base WebSphere Application Server node
The Network Deployment product is not a stand-alone product for running enterprise applications. To deploy UDDI or the gateway, install the base WebSphere Application Server product. Although it is not installed by default, a copy of the base WebSphere Application Server product is packaged with the Network Deployment product.
See Developing Web services for more information.

UDDI Registry

Installs a V2 compliant universal description, discovery, and identification (UDDI) registry, accessible from the UDDI registry user console application, or from SOAP or EJB interfaces.
See IBM WebSphere UDDI Registry for more information.

Web Services Gateway

Includes a gateway between Internet and intranet environments so that clients can invoke Web services safely from outside a firewall. The gateway uses automatic protocol conversion for externalizing Web services.
See Enabling Web services through the IBM Web Services Gateway for more information.

Embedded messaging client

Includes the client necessary for the administration of WebSphere MQ Queues and the mapping of JMS resources into the deployment manager JNDI namespace. It is the same client that you can install as part of the base product embedded messaging feature.

You can run the uninstaller program to remove all installed features.

Specify a destination directory and click Next to continue. Deleting the default target location and leaving an installation directory field empty stops you from continuing the installation process. The Installation wizard does not proceed when you click Next. Enter the required target directory to proceed to the next panel. Non-ASCII special characters are not supported in the name of the installation directory. Spaces are also not supported in the name of the installation directory.
The installer program checks for required space at the beginning of the installation. If you do not have enough space, stop the installation program, free space by deleting unused files and emptying the recycle bin, and restart the installation.

If not enough space is available, cancel the installation, allocate the 150 MB of temporary space that is required, and reinstall. The actual space required depends on the features that you are installing.

If you have problems accessing the administrative console after installation, check the installAdminConsole.log file for a failure indication. Clean up the /tmp space and reinstall the administrative console using the wsadmin scripting facility.

If you must increase the /tmp allocation, stop the installation program, increase the allocation, and restart the installation.

Specify node information and click Next.Specify the node name and host name. Although the wizard inserts the machine name (of the installation platform) as the node name, you can specify any unique name. The node name is an arbitrary WebSphere Application Server-specific name that must be unique within a cell.
The host name is the network name for the physical machine on which the node is installed. The host name must resolve to a physical network node on the server. When multiple network cards exist in the server, the host name or IP address must resolve to one of the network cards. Remote WebSphere Application Server nodes use the host name to connect to and to communicate with this node. Selecting a host name that other machines can reach within your network is extremely important. Do not use the generic localhost identifier for this value.

If you define coexisting nodes on the same computer with unique IP addresses, define each IP address in a domain name server (DNS) look-up table. WebSphere Application Server configuration files do not provide domain name resolution for multiple IP addresses on a machine with a single network address.

The value that you specify for the host name is used as the value of the hostName property in WebSphere Application Server configuration documents. Specify the host name value in one of the following formats:

Fully qualified domain name servers (DNS) host name string, such as xmachine.manhattan.ibm.com

The default short DNS host name string, such as xmachine

Numeric IP address, such as 127.1.255.3

The fully qualified DNS host name has the advantage of being totally unambiguous and also flexible. You have the flexibility of changing the actual IP address for the host system without having to change the WebSphere Application Server configuration. This value for host name is particularly useful if you plan to change the IP address frequently when using Dynamic Host Configuration Protocol (DHCP) to assign IP addresses. A format disadvantage is being dependent on DNS. If DNS is not available, then connectivity is compromised.

The short host name is also dynamically resolvable. A short name format has the added ability of being redefined in the local hosts file so that the system can run WebSphere Application Server even when disconnected from the network. Define the short name to 127.0.0.1 (local loopback) in the hosts file to run disconnected. A format disadvantage is being dependent on DNS for remote access. If DNS is not available, then connectivity is compromised.

A numeric IP address has the advantage of not requiring name resolution through DNS. A remote node can connect to the node you name with a numeric IP address without DNS being available. A format disadvantage is that the numeric IP address is fixed. You must change the setting of the hostName property in WebSphere Application Server configuration documents whenever you change the machine IP address. Therefore, do not use a numeric IP address if you use DHCP, or if you change IP addresses regularly. Another format disadvantage is that you cannot use the node if the host is disconnected from the network.

Review the summary information and click Next to install the product code or Back to change your specifications.The Summary panel displays the directory for the embedded messaging feature incorrectly on all Linux and UNIX-based platforms, as /opt/IBM/WebSphere MQ. Actual installation locations are /usr/mqm on AIX systems, and /opt/mqm on Linux and all UNIX-based platforms except AIX. When the installation is complete, the wizard displays the install_root/logs/mq_install.log installation log if you selected the embedded messaging feature and errors occur with its installation.

Review the mq_install.log installation log if it displays. Click Next to continue.The wizard displays the Registration panel.

Click Next to register the product, or clear the check box and click Next to register at a later time.The Installation wizard starts the First Steps tool. See firststeps command.

Verify the success of the installer program by examining the Exit summary panel and the install_root/logs/log.txt for installation status. ISMP records a success message in the install_root/logs/log.txt file: "INSTFIN: The installation is complete." The log is the only source of status information for a silent installation.
Look for severe errors that the installer records in the install_root/logs/log.txt file in the installation root directory to verify that no file system or other unusual errors occurred during installation.

If the install_root/logs/log.txt file does not contain a record of any problems but problems exist, verify or troubleshoot the installation, as described in Troubleshooting the installation and in Installation component troubleshooting tips.

If problems exist, correct them, uninstall the product, as described in Uninstalling the product, log off as root and back on, and reinstall.

When installing WebSphere Application Server with embedded messaging from the CD-ROM, the following warning messages are issued despite successful installation:

MQSERIES.MQM-CL-HPUX: A test command parameter is not valid." and "* "hostname:/cdrom/hpux/messaging/images": Cannot open the logfile on this target or source. Possibly the media is read-only or there is a permission problem." on mq_install.log.
You can ignore the warning messages, because the problem does not affect the successful installation of WebSphere Application Server with embedded messaging.

Click Finish to close the Installation wizard.

Close the terminal window that remains open after the installation finishes.When installing WebSphere Application Server from the product CD onto a Solaris system, the ISMP installation wizard launches a terminal window, which remains open after the installation is complete. This window contains the following text:

InstallShield Wizard Initializing InstallShield Wizard... Searching for Java(tm) Virtual Machine... .....
Close the window after the installation completes.

Restrict access to the /var/mqm/errors directory and messaging logging files.After installing the embedded messaging feature, restrict access to the /var/mqm directory and to log files that are needed for embedded messaging, such that only the mqm user or members of the mqm user group have write access. For detailed information, see Installing WebSphere embedded messaging as the JMS provider and Securing messaging directories and log files.

Install the most current fix pack and cumulative fix for the Network Deployment product.See Recommended updates for WebSphere Application Server for information about downloading and installing the upgrades.

Tune your system for performance.For best performance on any platform, see Tuning performance.

(Optional) Create a monitored process for one or more Application Server processes or for the HTTP Server, as described in Automatically restarting server processes.
You can create monitored processes after the installation is complete.

Processes started by a startManager.sh command are not running as monitored processes, regardless of how you have configured them. You must start the deployment manager process with a shell script based on the example rc.was file, to have the deployment manager running as a monitored process.

Results

The Installation wizard configures the product. It is not necessary to perform further configuration at this time.

You have now registered and successfully installed WebSphere Application Server Network Deployment and the features that you selected.

What to do next

Uninstalling and reinstalling

See Uninstalling the product for information about uninstalling any WebSphere Application Server product.

Reinstalling a V5.1 instance on a Solaris platform after uninstalling and leaving the embedded messaging feature installed

If you uninstall a V5.1 instance but leave the embedded messaging feature because of other WebSphere Application Server instances, clean up the /var/sadm/pkg directory before reinstalling V5.1.

If you uninstall all WebSphere Application Server products on the machine and are now reinstalling, follow the procedure in Manually uninstalling on Solaris platforms instead of the following procedure.

You must perform this procedure before you can reinstall the product into the same installation root directory on Solaris platforms. Otherwise reinstall the product into another directory and you might have a problem reinstalling the embedded messaging feature.

Assume that V5.0.x base exists in /opt/WebSphere/AppServer50 with the embedded messaging server and client feature. You then install V5.1 base to the following directory, /opt/WebSphere/AppServer51, but later you uninstall the V5.1 base product and leave the embedded messaging feature installed. And now you decide to reinstall the V5.1 base product.

Make the /var/backupForWAS51Reinstall backup directory.

Change directories to /var/sadm/pkg, and type ls -lt | grep WSBAA51 to find packages that contain the base WebSphere Application Server.
(The directory for Network Deployment is WSNAA51.)

If the WSBAA51 directory exists, change directories to the WSBAA51 directory and read the pkginfo file in the /var/sadm/pkg/WSBAA51 directory.
Find the installation location for V5.1. If the location is the same installation location as the V5.1 product you uninstalled, move the /var/sadm/pkg/WSBAA51 folder to /var/backupForWAS51Reinstall.

The following example shows how to display the pkginfo file:

# pwd /var/sadm/pkg/WSBAA51 # ls -lt total 6 -rw-r--r-- 1 root other 591 Oct 27 15:46 pkginfo drwxr-xr-x 2 root other 512 Oct 27 15:46 install drwxr-xr-x 2 root other 512 Oct 27 15:46 save # cat pkginfo # VPD created by InstallShield MultiPlatform Edition # Mon Oct 27 15:46:34 EST 2003 ARCH=sparc BASEDIR=/opt/WebSphere/AppServer51 CATEGORY=application CLASSES=none DESC= ISJE_INSTALL_STATUS=3 ISJE_IS_ACTIVE=true ISJE_IS_PUBLICLY_SHAREABLE=false ISJE_NAME=IBM WebSphere Application Server ISJE_PARENTS=WSBAA51:5.1.0.0.DSP=:1 ISJE_PRODUCT_NUMBER=5.1.0.0 ISJE_REQUIRED_COUNT=0 ISJE_SOURCES= ISJE_UID=WSBAA51 ISJE_UNINSTALLER="_uninst" "uninstall.jar" "uninstall.dat" "" ISJE_VPD_VERSION=4.5 ISJE_WEB= NAME=WebSphere Application Server PKG=WSBAA51 PKGINST=WSBAA51 VENDOR= VERSION=5.1.0.0.DSP=

When two instances of V5.1 WebSphere Application Server exist, for example, with one installed and one uninstalled, two files exist in the /var/sadm/pkg directory. One is the /var/sadm/pkg/WSBAA51 file; the other is the /var/sadm/pkg/WSBAA51.2 file. For example:

# ls -lt | grep WSBAA drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBAA51.2 drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBAA51 drwxr-xr-x 3 root other 512 Oct 21 13:32 WSBAA

Verify that you are moving the correct file to the backup directory.
You can do this by examining the pkginfo files. Do not touch entries for other WebSphere Application Server products that might be present on the platform, such as WS entries for existing WebSphere Application Server V5.0.x.

Run the ls -lt | grep WSBM command to get all of the embedded messaging packages.
For example:

# # ls -lt | grep WSBM drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMQ1AA.2 drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMQ2AA.2 drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMS4AA.2 drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMS6AA.2 drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMQAA.2 drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMS4AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMS6AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMQ1AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMQ2AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMQ3AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMQAA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMSAA

Identify entries that are related to the V5.1 product that you uninstalled.
Examine the pkginfo file for each entry. In the previous example, ".2" entries relate to the product you uninstalled, which was originally in the /opt/WebSphere/AppServer51 directory. Use a command to move all the ".2" entries into the backup directory. For example, run the following command from the /var/sadm/pkg/ directory:

mv WSBM*.2 /var/backupForWAS51Reinstall
For V5.1 of Network Deployment, all related embedded messaging entries start with WSNM. Run the following command to show the Network Deployment entries:

ls -lt | grep WSNM

For V5.1, all related embedded messaging entries are related to the base product or to the Network Deployment product. No embedded messaging entries start with WSEM.

Rename /opt/WebSphere/AppServer51 to /opt/WebSphere/AppServer51_bk before reinstalling V5.1.

Miscellaneous tips for Solaris platforms

Installation and migration tips

Operating platform Tip in Platform-specific tips for installing and migrating
Solaris platforms Solaris operating environment

Using the unzip function, not the jar command, to decompress downloaded files

Configuring the converter.properties file to use EUC-JP (Japanese) encoding

Configuring the Domino Server plug-in

Avoiding problems starting appservers in zh_TW.EUC locale on Solaris

All platforms All platforms
All Linux and UNIX platforms All Linux and UNIX-based platforms

Installing the product
Using the Launchpad to start the installation
Installing silently
Customizing the Network Deployment options response file
Automatically restarting server processes

Platform-specific tips for installing and migrating
Tips for installing the embedded messaging feature
responsefile

Product	Link to installation procedure	Label on product CD
(Base) WebSphere Application Server	Base product installation	Application Server, IBM HTTP Server
Network Deployment	Network Deployment installation (which links to this procedure!)	Deployment Manager
WebSphere Business Integration Server Foundation	Integration Server installation	Integration Server Disk 1 and Integration Server Disk 2

Component	Base code	Broker code	Base data
Path	/usr/ mqm	/usr/ opt/ wemps	/var/ mqm
Client subfeature	15 MB	15 MB	15 MB

Operating platform	Tip in Platform-specific tips for installing and migrating
Solaris platforms	Solaris operating environment Using the unzip function, not the jar command, to decompress downloaded files Configuring the converter.properties file to use EUC-JP (Japanese) encoding Configuring the Domino Server plug-in Avoiding problems starting appservers in zh_TW.EUC locale on Solaris
All platforms	All platforms
All Linux and UNIX platforms	All Linux and UNIX-based platforms