This topic describes how to install the WebSphere Application Server Network Deployment product as the root user on an AIX operating system platform.
Before you begin
You cannot install the product correctly from a user ID that does not belong to the administrator group. Some steps of the installation procedure require the administrator group ID to have the following advanced user rights, Act as part of the operating system and Log on as a service.
If you encounter a problem such as not having enough space or not having the right prerequisite updates 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 |
Enterprise | Enterprise installation | Enterprise Application Server |
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.
If
you buy the Enterprise 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 Enterprise product that extends the Network Deployment product. You can
install the Enterprise product before the base product. The Enterprise product
can install the base product in what is known as an umbrella installation
but Enterprise cannot install the Network Deployment product. Some features
of the base product cannot be installed by Enterprise.
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:
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/wasv502nd_gs.pdf
Why and when to perform this task
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:
After using the launchpad to view product documentation, perform the following procedure. The procedure includes several preliminary steps before actually launching the installer program.
Steps for this task
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
To correct an existing problem:
lslpp -l | grep X11.base.rte
If you do not see details about the file set on your system, you must install the file set from the AIX 5.1 product CD-ROM. Install the file set before installing a fix pack for WebSphere Application Server products.
The Network
Deployment product requires the following disk space:
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 at least 150 MB of free space in the /tmp directory, and start the installation again.
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:
A user ID of the name mqm, with a primary group of mqm, owns the directories and files that contain the resources associated with the embedded messaging feature:
The recommended user ID for running the jmsserver process is root. If you do run the jmsserver 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 jmsserver for general JMS support and the WebSphere embedded broker for WebSphere Application Server topic connections.
su -In a normal root login, issue the command su. For a real root login, issue the command su -.
Display settings for a normal root login are automatic. For a real root login, you must set your display environment properly to successfully view the installation wizard. Otherwise, you see a message about Preparing Java(tm) Virtual Machine..., and seven rows of dots, but no installation GUI and no further messages. Refer to the documentation for your AIX platform to determine proper display settings.
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
Component | Base code | Broker code | Base data | Broker data |
---|---|---|---|---|
Path | /usr/ mqm | /usr/ opt/ wemps | /var/ mqm | /var/ wemps |
Client subfeature | 15 MB | 15 MB | 5 MB | N/A |
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 of the base Application Server. You can also install the WebSphere MQ product or another JMS provider after you install the WebSphere Application Server products.
On a machine where you want application servers to run messaging applications that use a JMS provider on another host, install IBM WebSphere Application Server or the deployment manager with the embedded messaging client feature.
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.
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 WebSphere Application Server detailed system requirements 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 you must 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.
The Installation wizard might display the Migration panel or the Coexistence panel even though you have uninstalled WebSphere Application Server Version 4.1. You can prevent the Installation wizard from recognizing a previously deleted V4.1 Application Server by removing the following entry from the /usr/bin/jitk.db file:
WebSphere Application Server 4.1
Remove other Version 4.x entries for WebSphere Application Server products that are no longer on your system.
If you have emacs or other freeware installed on your AIX operating platform, verify that the system cp command is being used.
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 Application Server product successfully.
Perform the following step to verify that the Java 2 SDK is working correctly.
cd /mnt/aix/WAS/jdk/java/bin
./java -version
The command completes successfully with no errors when the SDK is intact.
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, which is an InstallShield for MultiPlatforms (ISMP) application. This action launches the Installation wizard in the language of your machine locale unless no translation exists 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/aix/install command, where /cdrom is the mount point for the product CD-ROM and aix 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_HDD_pathname/responsefile # /cdrom/aix/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:
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
you must use an NFS mount, see the following installation tip:
Operating platform | Tip in Platform-specific tips for installing and migrating |
---|---|
All platforms | Platform-specific issues when dealing with network file systems |
fully_qualified_CD_pathname/install # /cdrom/aix/install
Readme link on the launchpad
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 the current version of the Getting Started document from:
ftp://ftp.software.ibm.com/software/webserver/appserv/library/wasv502nd_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.
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.
The license
that the Installation wizard displays can contain characters that display
incorrectly in Japanese. For example, the section labeled Part 1 does
not show the number 1. These missing characters do not significantly
affect the content of the license agreement.
The prerequisites checker program recognizes the official supported level for AIX 5.2 as ML1 + APAR IY44183. AIX 5.2 ML2 is also supported. If you receive a message from the prerequisites checker program that AIX 5.2 ML2 is an unsupported operating system, ignore the message and continue the installation.
Update your operating system if it is missing required file sets. If you receive a message that a file set is missing, such as file set X11.fnt.ucs.ttf, cancel the installation, update the operating system, and restart the installation.
As the base WebSphere Application Server product version changes, its prerequisites and corequisites change. Updating your database, Web server, Software Development Kit (SDK), and other software is probably necessary.
The base WebSphere Application Server product simplifies migrating product prerequisites, by providing the option to install a complimentary Web server and 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.
Migrating or coexisting with an existing WebSphere Application Server node that AIX does not recognize.
In some cases, the InstallShield for MultiPlatforms (ISMP) program might not detect a previously installed version of WebSphere Application Server because of a failure to read the registry keys on AIX. You can force the migration and coexistence panel to display, by starting the installation with an option on the /cdrom/aix/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.
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:
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:
See Installing WebSphere embedded messaging as the JMS provider
for
more information.
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), you must 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 Enterprise, if you
are planning to install Enterprise:
If you are planning to install these products: | Select the migration option while installing this product: | ||
---|---|---|---|
Network Deployment | Enterprise | Network Deployment | Enterprise |
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
Enterprise also migrates the product that Enterprise 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 Version 5 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.
In some cases, such as when installing a non-English version, the Installation wizard might not detect a previous version. You can force the Migration panel or the Coexistence panel to appear, by starting the installation with an option on the /cdrom/aix/install command, where mnt/cdrom is the mount point for the product CD-ROM and aix is the platform directory on the CD-ROM.
For example, use this command:
/cdrom/aix/install -W showPreviousVersionDetectedPanel.active="true"
You can also force the appearance of the Coexistence panel to change conflicting port number assignments. For example, the AIX WebSM system management server listens on port 9090 by default. To avoid a conflict with the administrative console port (HTTP_TRANSPORT_ADMIN) assignment, which is also 9090 by default, force the Coexistence panel to appear using this command:
/cdrom/aix/install -W showCoexistencePanel.active="true"
The AIX WebSM system management server listens on port 9090 by default. If you suspect you have a port conflict, verify it by shutting down WebSphere Application Server and issuing the following command:
netstat -an |grep 9090If you get a match, another process is already listening on port 9090. If you want the WebSM server and WebSphere Application Server to coexist, change the WebSphere Application Server administrative console port when installing WebSphere Application Server, or after installation. Although not recommended, you can also disable the WebSM server. To disable the WebSM server, issue the following command to permanently disable WebSM server startup:
/usr/websm/bin/wsmserver -disable
If you choose neither the migration option
nor the coexistence option, you can run Version 5.0.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, Version 4.0.x installation.
The field labeled "Configuration file" is valid only for WebSphere Application Server Advanced Edition Single Server Edition, Version 4.0.x. For the other versions of WebSphere Application Server that are supported by migration (Version 3.5 Standard Edition, Version 3.5 Extended Edition, and Version 4.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 Version 5 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.
Choose from these features:
See Developing Web services
for more information.
See IBM WebSphere UDDI Registry
for more information.
See Enabling Web services through the IBM Web Services Gateway
for
more information.
You can run the uninstaller program to remove all installed features.
Ensure
that the target directory has adequate space available. Also ensure that at
least 150 MB or more of free space exists in the /tmp 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.
The installer program does not let you install the base product during an umbrella installation if sufficient space is not available to apply Cumulative Fix 2 and Cumulative Fix 1 for SDKs.
Suppose the installer program installs the base product and then runs into an error during the installation of the cumulative fix because of an insufficient amount of temporary space. In such a case, cancel the installation, allocate enough temporary space to install the cumulative fix, and restart the installation. The installer program picks up the installation where it left off, installing the cumulative fix to the base product, which you can select at the beginning of the installation.
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.
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:
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.
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.
The wizard displays the Registration panel.
The Installation wizard starts the First Steps tool. See firststeps command.
Verify
the success of the installer by querying the response code:
echo $?The return code from the installer is "1" to indicate success; any other response code indicates failure.
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.
Always install the latest cumulative fixes as they are released. See Cumulative Fix Strategy for WebSphere Application Server V5.0 and V5.1 for more information.
Recommended updates for WebSphere Application Server products are listed on the Recommended updates for WebSphere Application Server Base and Network Deployment editions Web page.
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.
After uninstalling a WebSphere Application Server product, reinstalling into the same directory without first deleting all directory contents results in invalid XML configurations because of the retention of old files. To delete all of the files so that you can reinstall with a clean system, uninstall manually, as described in Uninstalling the product.
Miscellaneous tips for AIX platforms