[AIX HP-UX Linux Solaris Windows]

Installing a CIP for Express

Install a IBM® WebSphere® Application Server - Express 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

Knowing which components to install and in what order to install them is important. Before starting this installation, read the "Planning the installation" topic in the WebSphere Application Server, Version 7.0 Information Center. The planning diagrams show typical topologies for the product. The solutions are also available through the Installation solution diagrams link in the launchpad. Also read the "Using the launchpad to start the installation" topic.

About this task

Perform the following installation to select available features for the WebSphere Application Server - Express product and to select characteristics for the application server profile.

Procedure

  1. Log on to the operating system. If you are installing as a non-root or non-administrative user, then there are certain limitations.
    [AIX] [HP-UX] [Linux] [Solaris] In addition, select a umask that allows the owner to read/write to the files, and allows 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 command:
    umask
    To set the umask setting to 022, issue the following command:
    umask 022
    [Windows] When installing as an administrative user on a Windows® operating system, a Windows service is automatically created to autostart the application server. The installer user account must have the following advanced user rights:
    • Act as part of the operating system
    • Log on as a service
    For example, on some Windows operating systems, click Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignments to set the advanced options. See your Windows operating system documentation for more information.

    [Windows] 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 restriction, install with a user ID that does not contain spaces.

  2. Access the root directory of your installation package on your hard disk, or insert the disc containing the installation package into the disc drive.
    If you are installing the product from CD and the CIP installer is spanned across multiple CDs, you will be prompted during the installation for the next CD.
    Best practice Best practice: To avoid being prompted for subsequent CDs, copy all installation CDs into the same directory on your hard disk, name them DISC1. DISC2, and so on for each disc, and run the installer from the DISC1 directory. You will not be prompted for the next CD during installation if you have followed this naming convention. If you are installing silently, then you must use this naming convention or the installation will not proceed.bprac

    [AIX] [HP-UX] [Linux] [Solaris] Mount the drive if necessary.

  3. Start the installation.
    Start the installation of a product image with the launchpad script.
    • [AIX] [HP-UX] [Linux] [Solaris] launchpad.sh
    • [Windows] launchpad.bat or launchpad.exe

    Or you can start the installation directly with the install command.

    • [AIX] [HP-UX] [Linux] [Solaris] /WAS/install
    • [Windows] \WAS\install
    Avoid trouble [Windows] Avoid trouble: There might be certain operating system policy restrictions if you are installing as a non-administrator on Windows 2003 on an AMD processor. You might not be able to run the install command by double-clicking the file in Windows Explorer. Run the command from a command prompt or rename the command to something other than install.exe or setup.exe and run the command.gotcha
    If an error occurs with the Java SE Runtime Environment 6 (JRE 6), force the installation to use the correct runtime environment with the following command, where downloaded_directory is the name of the directory in which you downloaded the image:
    • [AIX] [HP-UX] [Linux] [Solaris] ./install -is:javahome disc_mount_point/downloaded_directory/JDK/jre.pak/repository/package.java.jre/java/jre
    • [Windows] install -is:javahome disc_drive:\downloaded_directory\JDK\jre.pak\repository\package.java.jre\java\jre

    If you cannot start the launchpad, use the troubleshooting information in the "Using the launchpad to start the installation" topic in the WebSphere Application Server, Version 7.0 Information Center to correct the problem.

    When using the launchpad, launch the installation wizard for WebSphere Application Server.

  4. The installation wizard initializes and then displays the Welcome panel.

    Click Next to continue.

  5. The license agreement panel is displayed. Read the license agreement and accept its terms. After you accept the licensing terms, the installation wizard checks for a supported operating system and prerequisite patches.

    Although the installation wizard automatically checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the WebSphere Application Server detailed system requirements 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 you must install to have a compliant operating system.

    The installation process verifies that the minimum required version of a supported operating system is available. If you meet the minimum release requirements or are at a higher minor release of a supported operating system, then you will not encounter a prerequisite error. If you are not at the minimum version of a supported operating system, you can continue with the installation, but the installation or product operation might not succeed without applying maintenance. If you are at a higher major release of a supported operating system, or the operating system itself is not on the supported list, you might encounter the following warning:
    Warning: A supported operating system was not detected.
    
    Support for your operating system might have been added after the release of the product.
    See the WebSphere Application Server detailed system requirements Web pages for more information
    about supported operating systems. You can continue with the installation, but the installation
    or product operation might not succeed without applying maintenance. Go to the product support Web pages 
    to obtain the latest maintenance packages to apply after installation.

    Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.

    Click the radio button beside the message I accept both the IBM and the non-IBM terms to agree to the license agreement and click Next to continue.

  6. The systems prerequisite check panel is displayed. 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 application server installation at the same product level.
  7. If you are installing the product as a non-root user (or a non Administrator on Windows operating systems), then a panel is displayed indicating that a non-root user has been detected. This panel contains important information about installing as a non-root user. Read the "Non-root installation" topic in the WebSphere Application Server, Version 7.0 Information Center for more information. Click Next.
  8. 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 installation.

    If the wizard detects a previous installation, it displays the Existing installation panel, where you can:

    This procedure assumes that you do not have an existing installation that you intend to update.

  9. Select features to install and click Next.

    A CIP might not have all features available to install. You can install only what was included in the CIP.

    Note: If an existing installation is at a lower level than the CIP or at the same level as the CIP, the core product will be updated to the CIP level automatically. If an existing installation is at a higher level than the CIP, the core product will not be down leveled. The feature panel only shows the features you are missing, if you select to install the new feature from CIP, the installed features will be at the same level of CIP, which is lower than existing installation. Thus incremental install on a higher level of existing installation is not recommended.

    There are several features available:
    • Install the sample applications

      Installs the samples applications for learning and demonstration environments. The samples are not recommended for installation on production environments.

    • Install non-English language packages for the administrative console

      Installs all the non-English language files for using the administrative console from machines with non-English locales. If you do not select this option then only the English language pack is installed.

    • Install non-English language packages for the application server runtime environment

      Installs all the non-English language files that support the application server runtime environment such as the wsadmin tool and logging. If you do not select this option then only the English language pack is installed.

    The installation wizard displays a confirmation panel.

  10. 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 fix packs or interim fixes
    • Install another product that extends the product.

    The system-owned default app_server_root directories for installing as a root user or an administrator user are different than the user-owned default app_server_root directories when installing as a non-root installer.

    Restriction:
    • Deleting the default target location and leaving an installation directory field empty prevents you from continuing.
    • [AIX] [HP-UX] [Linux] [Solaris] Do not use symbolic links as the destination directory. Symbolic links are not supported.
    • [AIX] [HP-UX] [Linux] [Solaris] Spaces are not supported in the name of the installation directory on operating systems such as AIX® or Linux®.
    • [Windows] Do not use a semicolon in the directory name on Windows systems. WebSphere Application Server 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.

  11. Select an initial server environment on the WebSphere Application Server environments panel.
    The following values are valid:
    Table 1. Profile types
    Profile Type Description
    Management
    Create a management profile that provides the servers and services necessary to manage your WebSphere environment. You can select one of the following management profile types on the following panel:
    • Administrative agent

    Application server Create a standalone application server profile.
    None Do not create a profile during installation. However, if you do not create a profile during installation, then you must create a profile after installation to have an operational product.
  12. The administrative security panel is displayed. Choose whether to enable administrative security and click Next.

    The default setting is to enable administrative security. Clear the check box to disable security or supply an administrative ID and password. If you are installing the samples on an application server profile, you must specify the samples security information in the samples section below the administrative security section.

    Tip:
    • In environments where you plan to have multiple standalone application servers, the security policy of each application server profile is independent of the others. Changes to the security policies in one application server profile are not synchronized with the other profiles.
    • Write down the user name and password. You cannot log onto the administrative console without it. You cannot use the product at all unless you know the ID and password.
  13. Specify the node and host names for the application server and click Next.

    A good practice is to use unique names for each application server that you create. However, unique names are important only at the profile name level in the configuration directory.

    Reserved names: Avoid using reserved folder names as field values. The use of reserved folder names can cause unpredictable results. The following words are reserved: cell, nodes, servers, clusters, applications, and deployments.

    Field name Default value Constraints Description
    Node name DefaultNode

    Avoid using reserved folder names.

    Pick any name except for the reserved names. To help organize your installation, use a unique name if you plan to create more than one application server on the machine. However, a unique name for a standalone application server is not required.
    Host name DNS name of your machine See the following considerations for the host name field. Use the actual DNS name or IP address of your machine to enable communication with your machine. See additional information about the host name following this table.

    Node name considerations

    [Windows] The installation directory path must be no longer than 60 characters.

    See the topic Host name values for more information.

    [Windows] After specifying application server characteristics, the wizard displays the Windows service definition panel, if you are installing on a Windows platform.

  14. [Windows] Choose whether to run the application server as a Windows service on a Windows platform, then click Next.

    The installer attempts to start Windows services for application server processes started by a startServer command. For example, if you configure an application server as a Windows service and issue the startServer command, the wasservice command attempts to start the defined service.

    If you chose to install a local system service, you do not have to specify your user ID or password. If you create a specified user type of service, you must specify the user ID and the password for the user who is to run the service. The user must have Log on as a service authority for the service to run properly.

    To perform this installation task, the user ID must not have spaces in its name. The ID must also belong to the administrator group and must have the advanced user rights Act as part of the operating system and Log on as a service. The installation wizard grants the user ID the advanced user rights if it does not already have them, if the user ID belongs to the administrator group.

    You can also create other Windows services after the installation is complete, to start other server processes.

    The installation wizard shows which components are selected for installation in a pre-installation summary panel.

  15. The installation summary panel is displayed.
    • [AIX] [HP-UX] [Linux] [Solaris] If you are installing as a non-root user, you can choose to verify whether you have the correct permissions to install the product successfully. Select the Verify my permissions to perform the installation check box if you wish to verify your permissions to install the product. If the permission check fails, then review your user permissions and retry the installation. Read the "Non-root installation" topic in the WebSphere Application Server, Version 7.0 Information Center for more information.
    • [Windows] The verify permissions function is currently not available on Windows operating systems.

    Review the summary information. 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.

  16. The Installation results panel is displayed. Verify the success of the installer program by examining the completion panel and the app_server_root/logs/install/log.txt file to verify that there were no file system or other unusual errors while installing. If there are problems, correct them, and reinstall the product. Important information about the profile you created is also available in profile_root/logs/AboutThisProfile.txt. Read the "Troubleshooting installation" topic for more information on other installation logs and log locations.

    The slip install log for the Installation Factory is located in the app_server_root/logs/install/log.txt file, which is the same log file as for a normal installation. If the file already exists, a new log message is appended to the file.

    If problems occur, consult the following applicable logs:

    If the installation of the core product files fails, fix the error and reinstall.

    If the creation of a profile fails, fix the error and run the Profile Management Tool to recreate the profile.

    [AIX Solaris HP-UX Linux Windows] Troubleshoot the installation if the app_server_root/logs/install/log.txt file or the app_server_root/logs/manageprofiles/profile_name_create.log file does not contain a record of any errors, but errors exist.

    [IBM i] Troubleshoot the installation if the app_server_root/logs/install/log.txt file or the user_data_root/profileRegistry/logs/manageprofiles/create.log file does not contain a record of any errors, but errors exist.

    Read the "Troubleshooting installation" and the "Installation component troubleshooting tips" topics for more information.

    [Windows] Examine the Start menu entry. The menu is an indication of a successful installation:

    If problems exist that cause you to reinstall the product, correct the errors, uninstall the product in the same way as the regular application server product, reboot a Windows machine or log off and back on as root on a machine with an operating system such as AIX or Linux, and reinstall.

  17. Click Finish to close the installation wizard.

    If you did not create a profile during the installation, the option to launch the Profile Management Tool is displayed. Use the Profile Management Tool to create an operational environment that includes a profile.

    See the profiles documentation for more information.

    If you did create a profile, select the check box to open the First Steps console then click Finish.

Results

This procedure results in the installation wizard installing WebSphere Application Server into the installation root directory. The installation wizard creates a profile named default that provides the runtime environment for the server1 application server.

Further configuration is not necessary at this time. However, you can create additional standalone application servers with the Profile Management Tool. Each profile is created in the profile_root directory by default.

What to do next

See Fast paths for WebSphere Application Server to get started deploying applications.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 11:59:30 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=ifactory&topic=tins_custome_61_cip
File name: tins_custome_61_cip.html