This topic describes how to install on the Solaris operating platform.
Before you begin
Logging on as the root user is required to successfully install the product. 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 | Deployment Manager |
Enterprise | Enterprise installation (which links to this procedure!) | 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.
Download a new installation guide at ftp://ftp.software.ibm.com/software/webserver/appserv/library/wasv502ee_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:
A known problem with the Launchpad can prevent it from using Netscape to open the documentation links on certain platforms. You can launch the following links directly from your browser:
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.
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 .
Download a new installation guide at ftp://ftp.software.ibm.com/software/webserver/appserv/library/wasv502ee_gs.pdf
.
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
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
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.
Base product | Enterprise product extending base | Network Deployment | Enterprise extending Network Deployment | IBM HTTP Server | Tivoli Global Security Kit | Temp space | |
---|---|---|---|---|---|---|---|
Installation directory | /opt/ WebSphere/ AppServer | /opt/ WebSphere/ AppServer | /opt/ WebSphere/ Deployment Manager | /opt/ WebSphere/ Deployment Manager | /opt/ IBM Http Server | /opt/ ibm/ gsk7 | /tmp |
Minimum free space for installation | 539 MB | 539 + 82 MB | 539 MB | 539 + 90 MB | 21.2 MB | 23.1 MB (GSKit 7); 23.1 MB (GSKit 5) | At least 100 MB |
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:
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.
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
su -
Component | Base code | Broker code | Base data | Broker data |
---|---|---|---|---|
Path | /usr/ mqm | /usr/ opt/ wemps | /var/ mqm | /var/ wemps |
Server and client subfeature | 40 MB | 70 MB | 20 MB | 5 MB |
Client subfeature | 15 MB | 15 MB | 15 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 or install the WebSphere MQ product or another JMS provider later.
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.
If
you are installing the embedded messaging feature, follow the instructions
in Installing WebSphere embedded messaging as the JMS provider.
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 ...
If you attempt to install the embedded messaging feature when WebSphere MQ is already installed, the level of WebSphere MQ must be Version 5.3 with the required MQ features. Otherwise, the installation of the embedded messaging feature fails with prerequisite check 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:
mkdir /bigdisk/mqm ln -s /bigdisk/mqm /usr/mqm
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.
Solaris 9 SPARC workstations require the following patches:
Solaris 8 SPARC workstations require the following patches:
Refer to the WebSphere Application Server detailed system requirements 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 System requirements for IBM WebSphere Business Integration Server Foundation 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.
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 product successfully.
Perform the following step to verify that the Java 2 SDK is working correctly.
Perform the following steps to verify that the Java 2 SDK on the product CD-ROM is working correctly.
For example:
cd /mnt/sun/WAS/jdk/java/bin
Type the following command:
./java -version
The command completes successfully with no errors when the Java 2 SDK is intact.
If you are planning to extend a managed node, the installer program does not allow you to install certain features. The following features are always hidden and deactivated on a federated base node:
A managed node must have both the administrative console feature and the administrative scripting feature to install the following features:
Unfederate the managed node. When you install the product you can select any features. You can federate the base node again after the installation is complete.
Performing the installation with the wizard
You can start the Installation wizard in two ways. The default installation method is to open a command window to a read/write directory, issue the fully qualified command to start the Launchpad tool (Using the Launchpad to start the installation), and click the Install the product option. This option launches the Installation wizard in the language of your machine locale unless no translation is available 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. Start the installation from a read/write location and not from the CD-ROM.
If the Solaris machine is configured to auto mount CDROMs, Solaris automatically mounts the product CD as /cdrom/was_wbisf_sun_cd1 Close the File explorer window that Solaris automatically opens. Do not run the launchpad command or the install command using the automatically generated mount point as in this example of the /cdrom/was_wbisf_sun_cd1/sun/install command. Instead, start the installation using this mount point specification:
/cdrom/cdrom0/sun/install
The Launchpad copies certain files to your disk drive to avoid locking the CD during the installation, which requires you to change CDs. Expect a slight delay as you open the Launchpad while it copies the readme files and the installation document to disk.
Performing a silent installation
You can also perform a silent installation using the -options setup.response parameter (or the -options setup_nd.response parameter for use with the Network Deployment product) with the command method:
fully_qualified_CD_pathname/install -options fully_qualified_HDD_pathname/setup.response # /cdrom/cdrom0/sun/install -options /tmp/setup.response
Start the silent installation with a fully qualified path to the options response file. Otherwise, the Installation wizard starts. Start the silent installation from a read/write location and not from the CD-ROM or another read-only directory.
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 response
files before installing silently, as described in Customizing the Enterprise options response file.
After customizing one of the files, you can issue the command to silently install, as described in 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. If you copy both CDs to your disk drive, press Enter when the installation is complete to return to the command prompt. If you copy disk 2 only to your disk drive and you start the installation by issuing a fully qualified install command that refers to disk 1 in the CD drive, you can press Enter at any time to return from the background job to the command prompt. For more information, see the description of the asynchronous command line at the end of the next step.
You can change the -W launchPRTBean.active option 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, as described in Troubleshooting the installation, in the install_root/logs directory or in the /tmp directory.
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 setup.response and the setup_nd.response for more information. Comments in each file describe how to customize their options.
The Installation wizard might display the Migration panel or the Coexistence panel even though you have uninstalled WebSphere Application Server Enterprise Edition Version 4.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 Version 4.x entries for WebSphere Application Server products that are no longer on your system.
If the Solaris machine is configured to auto mount CDs, Solaris automatically mounts the product CD as the /cdrom/was_wbisf_sun_cd1 device. Close the File explorer window that Solaris automatically opens so that you can define a correct mount point.
Do not run the launchpad command or the install command from the automatically generated mount point as the /cdrom/was_wbisf_sun_cd1/sun/launchpad.sh command, for example. Instead, start the installation from a read/write directory using the mount point specification in the following command:
# /cdrom/cdrom0/sun/install
The readme link in the Launchpad is to the readme.html file in the CD root directory. The readme directory off the root of the CD has more detailed readme files. The Getting Started document that contains installation information is in the docs directory on the CD. Download the most current version of the Getting Started document from the Library Web page.
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 setup.response and the setup_nd.response for more information. Comments in each file describe how to customize the options.
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.
As
the WebSphere Application Server Enterprise product version changes, its prerequisites
and corequisites change. It is probably necessary to update your database,
Web server, Software Development Kit (SDK), and other software.
As mentioned in the introduction to this topic, the Enterprise
product can install the base WebSphere Application Server product. The base
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.
If you have both the base WebSphere Application Server product and the Network Deployment product on the same machine, the Installation wizard for the Enterprise product displays a panel for you to select which part of the Enterprise product to install.
When the installer program detects a previous installation at the same product level, a panel appears to let you add features to the existing installation or perform a new installation to another directory. When adding features, previously installed features are checked and grayed out with the term (Installed) at the end of the feature name.
You can add features on an unfederated base node or on a deployment manager node at any time, by running the Installation wizard again and choosing to add features.
If you are installing on a federated node, the installer program does not allow you to install certain features. These features are always hidden and deactivated on a federated base node:
Features that are not grayed out are available for installation on a federated base node. You do not have to unfederate the base node to add available features.
If the federated base node does not have the administrative console feature and the administrative scripting features, these additional features are hidden and deactivated:
To install any of these deactivated features, you must unfederate the managed node, install the product again, select the features you require, and add the node to the cell again as described in Installing deactivated Integration Server features on a base node.
You do not have to unfederate a managed base node to add features that appear in the list of available features. See Installing available Integration Server features on a base node for more information.
Install Enterprise features before installing interim fixes or fix packs to avoid component regression problems. Regression problems can occur when installing V5.0.0 or V5.0.1 Enterprise features from the product CD-ROM onto an Enterprise system where you have installed interim fixes or fix packs. As the product installer installs the new features, it also reinstalls related components at the V5.0.0 or V5.0.1 level, which regresses those components from the fix level back to the previous level.
If you intend to install additional features to the base product, use the following procedure to avoid component regression problems. It is important that you understand that no way exists to add features to a base node without unfederating it from its cell and losing its configuration. The configuration for the base node is restored back to its original configuration, before it was federated and before you changed it with the administrative console of the deployment manager. This means that you lose the configuration for any additional servers that you created on the base node from the deployment manager. (The additional servers do not exist any more.) You lose any other configuration you performed from the deployment manager administrative console.
Use the backupConfig command to save the Network Deployment configuration so that you can restore the configuration if necessary. Although you can use the backupConfig command to save the configuration, the restoreConfig command restores the configuration without any features you add to the base node. However, you can refer to the saved configuration after adding features and adding the base node back to the cell. Refer to the saved configuration as you use the administrative console of the deployment manager to reconfigure the base node.
Applicability of the following list: [5.0 only][Version 5.0.2]
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.0.2 (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.0.2 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:
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.
The
first rule of migration is to migrate after you install Enterprise:
If you are planning to install these products: | Select the migration option while installing this product: | ||
---|---|---|---|
Base product | Enterprise | Base product | Enterprise |
X | X | ||
X | X | X |
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 |
Migrating
Enterprise also migrates the product that Enterprise extends.
When you perform an umbrella installation of the base WebSphere Application Server product, you can choose to migrate applications and the configuration from a previous version, or to coexist with another version of the base WebSphere Application Server product, or to do neither.
You can also 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/cdrom0/sun/install command, where /cdrom/cdrom0 is the mount point for the product CD-ROM and sun is the platform directory on the CD-ROM.
For example, use this command:
# /cdrom/cdrom0/sun/install -W showPreviousVersionDetectedPanel.active="true"
You can also force the appearance of the Coexistence panel to change conflicting port number assignments using the following command:
# /cdrom/cdrom0/sun/install -W showCoexistencePanel.active="true"
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.
If you choose a typical installation, skip the next step.
After selecting a typical installation, the wizard prompts you to select the directory for the program code. After selecting a custom installation, the wizard displays a list of features.
Selecting certain features causes
the installation of other prerequisite features. The following table shows
this feature relationship.
If you select these features: | These Enterprise features are also installed: | |
---|---|---|
Embedded Messaging | ||
Sub-features: | Server and Client | |
Client Only | ||
Message-driven Bean Samples (for the server and not for the client) | ||
You can install the MDBSamples
application without installing the embedded messaging server and client feature.
Perhaps you have already installed the server and client feature. Or perhaps
you intend to reconfigure the MDBSamples to use messaging resources that WebSphere
MQ software provides. In any case, if you install the MDBSamples application and do not have the server and client feature installed, errors occur. The Application Server starts the MDBSamples application at start up. The MDBSamples application cannot start the required messaging resources in the Java Naming and Directory Interface (JNDI). Because of the lack of required resources, the message-driven beans fail to start, which causes an exception that the Application Server logs. The Application Server is not affected other than being unable to start the MDBSamples application. |
||
Business Rule Beans | ||
Sub-features: | Business Rule Beans Sample | |
Extended Messaging | ||
Sub-features: | Extended Messaging Sample | Embedded Messaging |
Dynamic Query | ||
Sub-features: | Dynamic Query Sample | |
Additional Enterprise Extensions | ||
Sub-features: | Additional Enterprise Extensions Samples | |
Scheduler and Asynchronous Beans | ||
Sub-features: | Scheduler and Asynchronous Beans Samples | Embedded Messaging |
Process Choreographer | Additional Enterprise Extensions | |
Scheduler and Asynchronous Beans | ||
Sub-features: | Process Choreographer Samples | Additional Enterprise Extensions |
Scheduler and Asynchronous Beans | ||
Configure a sample BPE container | Embedded Messaging | |
Additional Enterprise Extensions | ||
Scheduler and Asynchronous Beans | ||
CORBA C++ SDK (deprecated) | ||
Sub-features: | Interface Repository Support (Requires DB2) | |
CORBA C++ SDK Samples | ||
Javadocs |
If you do not have the prerequisite base WebSphere Application Server product installed, the Enterprise installation can install it for you. The Enterprise installation installs the base WebSphere Application Server product without these features:
If you already have an unfederated base node installed, but select an Enterprise feature that requires a base product feature that you have not installed, the Enterprise installation installs the feature on the unfederated base node. The following table describes which base features are required when you select an Enterprise feature.
If you select these features: | These base product features are also installed: | |
---|---|---|
Embedded Messaging | ||
Sub-features: | Server and Client | |
Client Only | ||
Message-driven Bean Samples (These samples are the MDBSamples application, which is for the server and not for the client.) | ||
Business Rule Beans | WebSphere Application Server | |
Admin Scripting | ||
Administrative Console | ||
Sub-features: | Business Rule Beans sample | Application Server samples |
Extended Messaging | WebSphere Application Server | |
Sub-features: | Extended Messaging sample | Application Server samples |
Embedded Messaging | ||
Messaging-driven Bean Samples | ||
Dynamic Query | WebSphere Application Server | |
Sub-features: | Dynamic Query Sample | Application Server samples |
Additional Enterprise Extensions | Application Server | |
Application Assembly Tool | ||
Administrative Console | ||
Sub-features: | Additional Enterprise Extensions samples | Application Server samples |
Scheduler and Asynchronous Beans | Application Server | |
Sub-features: | Scheduler and Asynchronous Beans Samples | Application Server samples |
Process Choreographer | Application Server | |
Admin Scripting | ||
Administrative Console | ||
Sub-features: | Process Choreographer samples | Application Server samples |
Configure a sample BPE container | Embedded Messaging | |
CORBA C++ SDK | ||
Sub-features: | Interface Repository Support (Requires DB2) | |
CORBA C++ SDK samples | Application Server samples | |
Javadocs |
You can run the uninstaller program to remove all installed features.
Ensure
that the target directory has adequate space available. Also ensure that approximately
100 MB or more of free space exists in the platform tmp directory,
or on the disk with the Windows temp directory.
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.
If you select the embedded messaging feature and prerequisites are missing, the Installation wizard displays the mq_prereq.log error log and takes you back to the Installation type panel. Choose Custom installation and clear the embedded messaging feature to continue. The mq_prereq.log file is in the system temp directory.
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 the /etc/hosts file or 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.
User ID to authenticate with the embedded messaging queue manager
This field is the JMS user ID who authenticates the connection to the JMS provider. This user ID must have administration rights for the messaging service.
The JMS user ID must be less than or equal to 12 characters.
You can create the user ID later and add the user to the mqm user group. Or specify the root user as the value for the field:
root
Password
Type the password for the user you specified as the JMS user ID in the first field.
Confirmation password
Repeat the password for the user you specified as the JMS user ID in the first field.
Security role for the business process system administrator
This field is the security role mapping. Specify the user or group from the domain user registry that is mapped onto the role of Business Process Administrator. The value to use depends on the local settings. For example, you can specify that the Administrator group is to perform the security role on some systems.
The user registry can be the local operating system, Lightweight Directory Access Protocol (LDAP), or custom registry. The user or group specified must already exist in the user registry being used.
You can register the product now by using the link on this panel or later, by using the Web address in the install_root/prt/readme_prt.txt file. The Web address in the file is encoded for your locale. A known problem for some locales corrupts the Web address so that it is similar to the following example. (The Web address is all one line in the file. The following example shows the address on two lines for clarity.)
http%3A%2F%2Fwww.ibm.com%2Fsoftware%2Fwebprt%2Fregister%2Fprodreg.nsf% 2Fcontact%3FOpenForm%26lang%3DENU%26pid%3D45P8842%26q2%3DWindows+2000
Use one of the following Web addresses if your install_root/prt/readme_prt.txt file is corrupt:
The Installation wizard starts the First Steps tool. See the firststeps command for more information.
If you are migrating a federated node as you install, close the First Steps tool. Migrated federated nodes have configuration differences that prevent you from using the First Steps tool.
Look for severe errors that the installer records in the /logs/WAS.PMI.install.log file in the installation root directory to verify that no file system or other unusual errors occurred during installation.
If the /logs/log.txt file and the /logs/WAS.PMI.install.log file do not contain a record of any problems but problems exist, verify or troubleshoot the installation, as described in Troubleshooting the installation and Installation component troubleshooting tips.
InstallShield Wizard Initializing InstallShield Wizard... Searching for Java(tm) Virtual Machine... .....Close the window after the installation completes.
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.
Results
The Installation wizard configures the product. It is not necessary to perform further configuration at this time.
You have now successfully installed WebSphere Application
Server Enterprise 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.
Miscellaneous tips for Solaris platforms
Operating platform | Tip in Platform-specific tips for installing and migrating |
---|---|
Solaris platforms | Solaris operating environment |
All platforms | All platforms |
All Linux and UNIX platforms | All Linux and UNIX-based platforms |