Installing a CIP for Network Deployment
Install a IBM WAS Network Deployment customized installation package (CIP) using the Installation wizard on distributed operating system platforms. You install from a CIP image created with the Installation Factory.
Before you begin
You can install a customized installation package (CIP) that includes a WAS product and one or more maintenance packages and other customizations. The Installation Factory must create a CIP before install the CIP. See Developing and installing customized installation packages for more information about creating a customized installation package (CIP).
This topic describes one of the available installation procedures.
- Installing a Network Deployment CIP, which is this topic
- Installing CIP features on an existing Network Deployment product
- Installing a CIP silently
If this topic does not describe the procedure that you meant to select, click the link to the description of the appropriate installation procedure before you issue the install command.
Knowing what component to install and in what order to install the component is an important consideration. Before starting this installation, see Planning to install Network Deployment . The diagrams show typical topologies for the product. The solutions are also in the Installation solution diagrams in the launchpad. See Using the launchpad to start the installation .
About this task
Use the following installation procedure to install the WAS Network Deployment product.
- Log on to the operating system.
Log on as root on an operating system such as AIX or Linux, or as a member of the administrator group on a Windows system.
In addition, select a umask that would allow the owner to read/write to the files, and allow others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users a umask of 002 or 022 could be used, depending on whether or not the users share the group. To verify the umask setting, issue the following commandTo set the umask setting to 022, issue the following commandumaskumask 022
When installing on a Windows system, a Windows service is automatically created to autostart the application server if your installer user account has the following advanced user rights:
- Act as part of the operating system
- Log on as a service
For example, on some Windows systems, click Administrative Tools > Local Security Policy > User Rights Assignments to set the advanced options. See your Windows documentation for more information.
The installation wizard grants your Windows user ID the advanced user rights, if the user ID belongs to the administrator group. The silent installation does not grant these rights. If you create a new user ID on a Windows platform to perform a silent installation, restart the system to activate the proper authorizations for the user ID before you can perform a successful silent installation.
If you plan to run the application server as a Windows service, do not install from a user ID that contains spaces. A user ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To work around this problem, install with a user ID that does not contain spaces.
- Insert the CD or DVD with the CIP into the disc drive, or access the directory where the CIP is located.
Mount the drive if necessary as described in Mounting disc drives on operating systems such as AIX or Linux .
- Start the installation directly with the install command.
If a problem occurs with the Java Runtime Environment (JRE), use the WAS JRE in the /java/jre/bin directory of an installation image to start the installation.
After launching the installation wizard from the command line, the installer wizard initializes and then displays the Welcome panel.
- Click Next to continue.
The license agreement displays.
- Click the radio button beside the I accept the terms in the license agreement message to agree to the license agreement and click Next to continue.
Although the installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the Supported hardware and software Web site if you have not already done so.
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, click Next to continue.
The Installation wizard checks for a previous installation at the same product level.
Specifically, the wizard looks for an existing v6.x installation.
If the wizard detects a previous installation, it displays the Existing installation panel, where you can:
- Add features to the existing installation
- Perform a new installation to another directory
- Add maintenance from a CIP to the existing installation
- Add files, directories, enterprise application archive (EAR) files, and a configuration archive (CAR) file from a CIP to the existing installation
- Use scripts in a CIP to configure the existing system
See Installing CIP features on an existing Network Deployment product for more information about the scenario that adds features.
This procedure assumes that you do not have an existing installation that you intend to update.
- Select features to install and click Next.
A CIP might have from zero to all of the product features. You can install only what was included in the CIP.
Table 1. Features for the WAS Network Deployment product Feature Description Core product files Installs the product binary code. Application Server Samples Installs the Samples Gallery and Plants By WebSphere applications. Javadoc Installs the application programming interface (API) and system programming interface (SPI) documentation for WAS classes.
For better performance in either a development or production environment, do not install the Samples. By omitting the Samples, you can improve application server startup time by 60 percent and save 15 percent of disc space. You can save up to 30 percent of process footprint (based on a maximum heap size of 256 MB).
The installation wizard displays a confirmation panel.
- Specify the destination of the installation root directory and click Next.
Specify the location of the installation root directory for the product binaries, which are also known as the core product files or system files.
The core product files do not change unless you:
Install a CIP
- Add a feature
- Install service, such as refresh packs, fix packs, or interim fixes
- Install another product that extends the Network Deployment product.
- Delete the default target location and leaving an installation directory field empty prevents you from continuing.
Do not use symbolic links as the destination directory. Symbolic links are not supported.
Spaces are not supported in the name of the installation directory on operating systems such as AIX or Linux.
Do not use a semicolon in the directory name on Windows systems. WAS cannot install properly on a Windows platform if the target directory includes a semicolon. A semicolon is the character used to construct the class path on Windows systems.
The installer program checks for required space before calling the installation wizard. 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.
- Review the summary information, then click Next to install the product code or Back to change your specifications.
The installation wizard creates the uninstaller program and then displays a progress panel that shows which components are being installed. At the end of the installation, the wizard displays the Installation completion panel.
- Click Finish to close the installation wizard.
Select the check box to launch the Profile Creation wizard, then click Next to close the installation wizard and launch the Profile Creation wizard.
See Creating profiles through the graphical user interface for more information.
The installation wizard installs the product files into the installation root directory.
You must create a profile that defines a deployment manager, a managed node, or a stand-alone application server to have an operational environment.
After installing a CIP, create an application server profile using the special Profile Creation wizard to restore a configuration archive customization. See Creating customized CIP profiles from the command line .
What to do next
Create a deployment manager profile and an application server profile.
Use the Profile Creation wizard to create profiles in the default profile_root directory or in a directory that you select.
Deploy an application to get started!
After creating an application server profile, you can deploy an application. See Fast paths for WebSphere Application Server to get started deploying applications.
Installing a CIP Developing and installing customized installation packages
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
AIX is a trademark of the IBM Corporation in the United States, other countries, or both.