WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Preparing Windows systems for installation

Learn how to prepare a Windows® system for installation of WebSphere® ESB.

Before you begin

The installation uses an InstallShield MultiPlatform (ISMP) wizard. You can also install the product silently. Silent mode is invoked at a command line with a parameter that identifies a response file, which you edit before installing.

Note: Installing WebSphere ESB from an unmapped network drive (such as \\hostname\sharename in Windows Explorer) or a virtual drive is not supported. You must first map the network drive to a Windows drive letter (for example, Z:) before attempting to install WebSphere ESB.

About this task

For Vista operating system Notes on WebSphere ESB support for Microsoft® Windows Vista and Windows Server 2008 operating systems:
  • The Windows Vista operating system is similar to the Microsoft Windows XP operating system in that it is not a server platform; but rather, it is geared towards client-side operation.
  • There are several differences in the Windows Vista and Windows Server 2008 operating systems from the Microsoft Windows 2003 and XP operating systems. From the standpoint of WebSphere ESB installation and operation, one of the most significant changes is the introduction of User Account Control (UAC). UAC is enabled by default in the Windows Vista and Windows Server 2008 operating systems.
    • Types of user account

      With previous versions of the Microsoft Windows operating systems, it was typical for a user to install WebSphere ESB using the built-in Administrator account. On the Windows Vista and Windows Server 2008 operating systems, however, the Administrator account is disabled by default and its use is discouraged. In place of the Administrator account, a user account with administrator group privileges is created whent he operating system is installed. However, even this account runs by default with standard user (non-administrative) privileges. This documentation refers to this account as the "administrator account."

      In addition to the initial administrator account, it is possible to create other accounts in the Windows Vista and Windows Server 2008 operating systems. These other accounts are not members of the administrator group by default. Both of these account types run by default with standard user privileges and do not execute with Administrator privileges. Under certain circumstances both account types can run with Administrator privileges, but in either case the user's privileges must be elevated in order to achieve this.

    • Administrator elevation
      When the Windows Vista operating system detects that an operation requires Administrator privileges, it might present the user with an elevation prompt for Administrator privileges that requests user confirmation before continuing with the operation.
      • When the elevation prompt is presented from the administrator account, the user is only required to confirm the operation.
      • When this happens from an account that is not a member of the administrators group, the user is required to provide the Administrator account's password before the operation is allowed to continue.
    • Registry and directory access
      • Certain areas of the operating system's registry require Administrator privileges before keys can be created, deleted, or modified.

        If a program needs to create or modify registry entries located in these protected areas, in order to configure a Windows Service, for example, that program must be running with Administrator privileges. It is not possible to perform such actions while running under standard user privileges.

      • Certain areas of the operating system's file system require Administrator privileges before program files can be created, deleted, or modified.

        The Program Files directory is one such area. If a program needs to modify files located under the Program Files directory (such as log files, profiles, or configuration files), that program must be running with Administrator privileges. It is not possible to perform such actions while running under standard user privileges.

Use the following procedure to prepare the operating system for installation of WebSphere ESB.

Procedure
  1. Log on to the system.
    Your user ID need not have Administrator privileges. However, installing the product as non-Administrator does create some restrictions. For example, you will not be able to create a Windows service for WebSphere ESB. Creating a Windows service requires the user to have the advanced user rights Act as part fo the operating system and Log on as a service.
    Tip: Windows service creation can be disabled by launching the graphical interface from the command line with the following option: install.exe -OPT PROF_winserviceCheck="false"

    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, you must restart the system to activate the proper authorizations for the user ID before you can perform a successful silent installation.

    When installing WebSphere ESB as a Windows service, do not use a user ID that contains spaces. A user ID with spaces cannot be validated and the installation cannot continue.

    Also, the program will not register with the operating system if you do not log onto the system as an Administrator. For more details on restrictions, see the following topic in the WebSphere Application Server Network Deployment, version 6.1.x information center: Limitations of non-root installers.

    For i5/OS operating system On i5/OS® platforms: If you plan to use the launchpad to install WebSphere ESB on an i5/OS system, sign onto a Windows system. You use the Windows system as a client machine to connect to the System i server while performing the interactive installation. The launchpad runs on the Windows client. To install on an i5/OS system, you must use a valid i5/OS user profile for that system. The user profile must have *ALLOBJ and *SECADM authorities. Without these authorities, the installation will fail.

  2. Optional: Download the latest supported version of Internet Explorer from the following location, so that you can use the Launchpad.

    Download Internet Explorer 6 Service Pack 1

  3. Optional: Download and install Mozilla 1.7.5 or later.
  4. Stop all Java™ processes related to WebSphere Application Server, WebSphere Application Server Network Deployment, WebSphere ESB, on the workstation on which you are installing the product.
  5. Stop any Web server process such as the IBM® HTTP Server.
  6. Stop all instances of the process_spawner.exe program.
  7. Provide adequate disk space. For the space required to install WebSphere ESB and related products, see WebSphere ESB detailed system requirements at http://www.ibm.com/support/docview.wss?uid=swg27006912 and select the link to your version of the product.
  8. Verify that prerequisites and corequisites are at the required release levels. Although the installation wizard checks for prerequisite operating system patches, review the prerequisite supported hardware and software for WebSphere ESB if you have not already done so. To access this information, see WebSphere ESB detailed system requirements at http://www.ibm.com/support/docview.wss?uid=swg27006912 and select the link to your version of WebSphere ESB.

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

  9. If needed, download Microsoft Windows Script Host version 5.6 to create Start menu items correctly on Windows operating systems.
    To check if you have this component already installed and to install it if you do not, open a command window and type cscript.
  10. Verify that the Java 2 SDK on your copies of the product discs is functioning correctly.

    If you created your own product DVD by copying the product DVD, or if you created your own DVD from the electronic download image, perform the following steps to verify that the Java 2 SDK is working correctly:

    1. On your created product disc, navigate to the /JDK/jre.pak/repository/package.java.jre/java/jre/bin directory. To do this, issue the following command:
      cd /JDK/jre.pak/repository/package.java.jre/java/jre/bin
    2. Verify the Java 2 SDK version. To do this, issue the following command:
      ./java -version
      The command completes successfully with no errors when the Java 2 SDK is intact.
    3. Repeat this procedure on all other created product discs.

Results

This procedure prepares the operating system for installation of WebSphere ESB.

What to do next

After preparing the operating system, you can install WebSphere ESB. See Installing the software for descriptions of the various installation alternatives available.


task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_windows_setup.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).