Follow this procedure to prepare a Windows system for installation
of WebSphere Process Server.
Before you begin
The installation uses an InstallShield for Multiplatforms (ISMP)
wizard. You can also install the product silently. Silent mode is invoked
at a command line with a parameter that identifies an options response file,
which you edit before installing.
Why and when to perform this task
Use the following procedure to prepare the operating system for
installation of WebSphere Process Server.
Steps for this task
- Log on with a user ID that belongs to the Administrator group.
To successfully install the product, your user ID must be a member
of the Administrator group. You cannot create Windows services with a user
ID that does not belong to the Administrator group. The creation of Windows
services requires the user to have the advanced user rights Act as part
of the operating system and Log on as a service. These services
are accessible by selecting Administrative Tools > Local Security Policy
> Local Policies > User Rights Assignments. 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, 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
Process Server as a Windows service, do not use 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.
- Optional: Download the latest supported version of
Internet Explorer so that you can use the Launchpad. Download Internet
Explorer 6 Service Pack 1 from the following location:
http://www.microsoft.com/windows/ie/default.mspx
- Stop all Java processes on the machine on which you are installing
the product that are related to WebSphere Application Server, WebSphere Application
Server Network Deployment, or WebSphere Process Server.
- Stop any Web server process such as the IBM HTTP Server.
- Stop all instances of the process_spawner.exe program.
- Provide adequate disk space. See Required disk space for the space required to install WebSphere
Process Server and related products.
- 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 Process Server if
you have not already done so. To access this information, see WebSphere Process Server detailed
system requirements at http://www.ibm.com/support/docview.wss?uid=swg27006205 and
select the link to your version of WebSphere Process Server.
Refer
to the documentation for non-IBM prerequisite and corequisite products to
learn how to migrate to their supported versions.
- 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.
- If the component is installed, the usage and options information for it
appear. Proceed to step 9.
- If the component is not installed, you must download and install it from
one of the following Microsoft Web pages:
- Verify that the Java 2 SDK on your
copies of the product CDs is functioning correctly.
If you created
your own product CDs from ISO images or by copying the actual CDs, perform
the following steps to verify that the Java 2 SDK is working correctly.
- Change directories to the \JDK\repository\prereq.jdk\java\bin directory
on your copy of WebSphere Process Server CD
1. Type the following command:
cd CD_Drive:\JDK\repository\prereq.jdk\java\bin
- Verify the version of the Java 2 SDK. Type the following
command:
.\java -version
The command completes successfully with no errors when the Java
2 SDK is intact.
- Perform the same procedure on your copy of WebSphere Process
Server CD 2.
- Installing WebSphere Process Server from
an unmapped network drive (such as \\hostname\sharename in Windows
Explorer) is not supported. You must first map the network drive to a Windows
drive letter (for example, Z:) before attempting to install WebSphere Process Server.
Result
This procedure prepares the operating system for installation
of WebSphere Process Server.
What to do next
After preparing the operating system, you can install WebSphere
Process Server. See Installing the product for
descriptions of the various installation alternatives available.