WEA:Preparing a Windows operating system

Review this topic to make sure the Microsoft Windows operating system is ready for the WebSphere install.

Check the service pack version

WebSphere Everyplace Access requires Service Pack 4 for Windows 2000 Server and Advanced Server. Service Pack 4 must be installed before you begin the WebSphere Everyplace Access installation. To verify you have the correct service pack:

Click Start > Run.
Type winver and press Enter to display information about Windows.
Verify Service Pack 4 is installed.
If Service Pack 4 is not installed, refer to the Microsoft support site or Windows Update for Windows 2000 to download and install the service pack.

Verify msvcp60.dll is installed

The WebSphere Application Server embedded messaging feature requires a DLL file on Windows 2000 Server platforms. The DLL might not be installed on Windows 2000 Server and Advanced Server with Service Pack 4. Verify the DLL is installed on the computer.

If you select the Windows 2000 Support Tools during Windows 2000 Server installation, the installation program for Windows installs the DLL file in the C:\Program Files\Support Tools directory. The DLL file is installed during the installation of Windows 2000 Advanced Server in the C:\WINNT\system32 directory.

If you cannot find the DLL, download it from the Microsoft Web site.

If the DLL is not installed, you will encounter the following error during the WebSphere Application Server installation:

wempsdeletebroker.exe - Unable To Locate DLL The dynamic link library MSVCP60.dll could not be found in the specified path...

Check the network setup

This section describes the network setup requirements for WebSphere Everyplace Access. Proper network configuration is essential when installing WebSphere Everyplace Access.

Check for static IP address

WebSphere Everyplace Access requires the computer have a static IP address. Follow these instructions to determine if the computer's network is configured correctly.

Click Start > Sets > Network and Dial-up Connections.
Right-click the LAN connection for your network adapter and click Properties.
On the network adapter properties window, select Internet Protocol (TCP/IP) from the list of components used by the connection and click Properties. The Internet Protocol (TCP/IP) will display.
Verify that Use the following IP address is selected. If Obtain an IP address automatically is selected the computer has a dynamic IP address. If this is the case, contact your network administrator to obtain and configure a static IP address.

Check for a fully-qualified host name

WebSphere Portal also requires the use of a fully qualified host.name, which is typically the host.name of the server, along with its fully-qualified domain name (FQDN). To be sure that this is configured correctly, you can check with a simple ping before you start installation. For example, you could enter the following command at a command prompt:

ping yourserver.setgetwebmpany.com

If a fully-qualified host.name is not configured correctly, the request might time out.

Check port bindings

Specific ports are required to install WebSphere Everyplace Access. If two applications attempt to use the same port, a port conflict results.

Use the Netstat utility to ensure that port bindings are available:

Click Start > Programs > Accessories > Command Prompt to launch a command prompt.
Type netstat -an at the command prompt.
Look at the numbers listed in the Local Address column. The fifth number is the port number. For example, in the IP address 1.2.3.4:80, 80 is the port number.
Verify that the following list of port numbers, required by WebSphere Portal, are not in use. If any of these port numbers are in use you might experience port conflicts. The following ports are required by default for WebSphere Portal and its related applications:
- 443 (standard HTTPS port)
- 523 (DB2 Administration Server)
- 8008 (IBM HTTP Server Administration port)
- 9081 (existing WebSphere Portal)
- 50000 (DB2 instance connection port)
- 50001 (DB2 instance interrupt port)
- 50002 (DB2 Control Server)
- 55555 (WAS database port)

Create the WebSphere Everyplace Access Administrator ID

Before you install, create the Administrator ID for WebSphere Everyplace Access. During a Basic install, the administrator ID is a local Windows operating system administrator ID that is shared by all components and used to create WebSphere Everyplace Access databases, windows services. During a Component install, the administrator ID is used to install WebSphere Application Server. All installation methods require the ID to have system administrator permissions. In other words, it must be a member of the Administrators group.

The WebSphere Everyplace Access Administrator ID used for a Basic installation has the following requirements:

Can contain characters a-z, A-Z, 0-9
Cannot begin with a numeric character
Cannot be longer than 12 characters
Cannot include spaces, NON-ASCII characters, or diacritics (such as umlauts)
Cannot be users, admins, guests, public, local, or any SQL reserved word list in SQL Reference.
Cannot start with SQL, SYS or IBM (This also applies to the password.)

The WebSphere Everyplace Access Administrator ID used for a Component installation has the following requirements:

Can contain characters a-z, A-Z, 0-9, - (dash), _ (underscore), and . (dot)
Cannot be longer than 12 characters
Cannot include spaces, NON-ASCII characters, or diacritics (such as umlauts)

The installation program prompts you for this Administrator ID when you perform both the Basic installation and Component installation.

To create the ID:

Click Start > Programs > Administrative Tools > Computer Management.
Under System Tools, expand Local Users and Groups.
Right click Users and select New User.
On the New User dialog, enter a user name, password, and confirm password.
Deselect User must change password at next logon.
Click Create and then click Close.
Add the ID you just created to the Administrators group.
1. Right click the user you just created and select Properties.
2. Click the Member Of tab and click Add.
3. Select Administrators from the Name column and click Add. Click OK.
4. Click Apply and then click Close.

Check access rights for the logon user ID

The ID that you use to log on to the computer, the administrative user, must be a local user that is 12 characters or less. To be an administrative user it must belong to the Administrators group defined in Windows. You cannot use a domain user ID. In addition, it must have the following rights:

Act as part of the operating system
Create a token object
Increase quotas
Replace a process level token
Log on as a Service

To access the interface for editing user rights, do the following:

Click Start > Programs > Administrative Tools > Local Security Policy.
Expand Local Policies and click User Rights Assignment.
Locate each Policy listed above and verify that the logon ID is listed in the Local Setting column.
To add the user, right click the policy and select Security.

Disable Microsoft Internet Information Services (IIS)

If Microsoft Internet Information Services (IIS) Web server is running, you will have a port conflict with IBM HTTP Server. Both of these Web servers listen on port 80, unless otherwise configured. To prevent this conflict, disable the Microsoft IIS Web server.

To see if IIS is enabled:

Click Start > Sets > Control Panel > Add/Remove Programs.
Select Add/Remove Windows Components.
If IIS is selected it is enabled on the computer.

To disable IIS:

Click Start > Programs > Administrative Tools.
Open Services.
Locate and highlight IIS Admin Service.
Click on the Action menu. Click Properties. A window opens.
Change the Startup type to Disabled and click Stop to stop the server.
Click Yes to stop any services that are stopped as a result.
Locate the World Wide Web Publishing Service and also disable it at startup using the previous steps

Disable any firewall products

Before you start the WebSphere Everyplace Access install program, disable any firewall products that are running on the computer where portal will be installed. If the installation program detects a firewall, a warning message displays.

Prepare for WebSphere Application Services Embedded Messaging (optional)

Embedded Messaging is only required if you plan to install Intelligent Notification Services and it is not required if you are performing a Basic Install. It is an optional feature that you can choose to install when installing WebSphere Application Server. Embedded messaging is the messaging server for the WebSphere JMS provider. The WebSphere JMS provider supports both queues (for point-to-point messaging) and topics (for publish/subscribe messaging). If you plan to install Intelligent Notification Service now, or in the near future, perform the following steps to prepare the computer for embedded messaging. It is harder to install embedded messaging after you have installed WebSphere Application Server. If you already have WebSphere MQ installed, additional steps are needed. For details refer to the WebSphere Application Server documentation.

Note: This information was taken from the WebSphere Application Server InfoCenter. For more information and the most up-to-date instructions, refer to the WebSphere Application Server InfoCenter.

WebSphere Application Server InfoCenter: http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp

Ensure that there is enough space in the file systems where you want to install the Embedded Messaging options and store associated messaging data. You can specify the file system into which the Embedded Messaging options are installed. The following table lists the default locations for the base messaging functions and the messaging broker functions (for publish/subscribe messaging). The table also provides figures for the file system sizes on which you can base your own calculations.

Table 1. Installation directory and space needed for embedded messaging
	Base messaging	Messaging broker
Installation directory	C:\Program Files\IBM\WebSphere MQ	C:\Program Files\IBM\WebSphere MQ\WEMPS
Typical space needed	70 MB (server) or 15 MB (client)	45 MB (server)

If you are using the Installation wizard to install IBM WebSphere Application Server, you can specify an install location for the Embedded Messaging options during either a Full or Custom install.

Define a local Windows user ID with these authorizations:
- Assign the user ID to the Administrators group.
- Give the user ID the advanced user right, Act as part of the operating system.
- Give the user ID the advanced user right, Log on as a service.
User IDs longer than 12 characters cannot be used with the embedded WebSphere JMS provider. For example, the default Windows 2000 Server user ID, Administrator, is not valid for use with embedded WebSphere messaging, because it contains 13 characters. Use the same user ID that will be specified as the WebSphere Administrative ID when installing WebSphere. The installation wizard grants the specified Windows user ID the advanced user rights listed above, if the user ID belongs to the Administrative group.
The embedded WebSphere JMS Provider is utilized by the Intelligent Notification Services appserver and is started automatically when you start the Intelligent Notification Services server. The Intelligent Notification Services appserver must run under a user ID with the length limitations and authorizations described in the previous paragraph. On Windows, this user ID is associated with the Intelligent Notification Services appserver, when it is started from the Windows services menu; otherwise, the server runs under the logged on user when started from the command line.

Install and configure Lotus Notes Client

If you are using the Domino Server mail databases and want to synchronize PIM and e-mail data or receive Mail notifications, install and configure a Notes Client. Everyplace Synchronization and Intelligent Notification Services use the Notes Client to communicate with the Domino Server.

Note: If you are performing a Basic Install, refer to the instructions in the Performing a Basic Install topic for instructions to configure the Notes Client.

If you are performing a Component Install, the Notes Client should be installed on the same computer as Everyplace Synchronization Server and Intelligent Notification Services. This means if you are installing the features on different computers, you need to install the Notes Client on both computers. If you are installing the features on one computer, you need one installation of the Notes Client.

Note: If you are installing Intelligent Notification Services in a distributed environment where WebSphere Portal is on a different computer than the Intelligent Notification Services server components, also install the Notes Client on the WebSphere Portal computer. On the WebSphere Portal computer, you only need to perform the steps that apply to Intelligent Notification

Before you begin, obtain a Domino Server Notes ID. You can share the Notes ID between the Everyplace Synchronization Server and Intelligent Notification Services, but this is not recommended. The Intelligent Notification Services Notes ID must have Read access to the Domino databases. The Everyplace Synchronization Server must have Manager access to the Domino databases. If you plan to share the ID, it must have Manager access to accommodate both features.

If you plan to install both Intelligent Notification Services and Everyplace Synchronization Server on the same computer, complete all of the steps below. If you are only installing one feature, Intelligent Notification Services or Everyplace Synchronization Server, you only need to complete the steps that apply to the feature you are installing. These instructions assume you are installing both Everyplace Synchronization Server and Intelligent Notification Services and that you will install the features in the default location.

Install the Notes Client 6.01. Note the install location. The default client executable code is installed in C:\Program Files\Lotus\Notes and the data directory is C:\Program Files\Lotus\Notes\Data. The following steps will assume you used the default directories. If you installed to a custom location, substitute your directory paths for the defaults used here. If the Notes Client is already installed and configured, uninstall the client, install it again and then follow the steps below.
1. For English, German, Spanish, French, and Italian insert CD 9-1 and for Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese, insert CD 9-2.
2. Navigate to the win directory and open the appropriate language directory.
3. Run setup.exe.
4. Click Next on the welcome panel.
5. Accept the terms of the license agreement and click Next.
6. Specify the User Name and Organization.
7. Select Only for me (Single User Install) and click Next.
8. Specify the installation location and click Next. Accepting the default location is recommended.
9. Accept the default features to install on the Custom Setup panel. Click Next.
10. On the Ready to Install the Program panel click Install.
Create the appropriate directory structure for the features being installed.
Note: Make sure you backup each NotesData directory you create. In the event of having to reconfigure a component, the remove configuration task will remove all files in the NotesData directory.
- If you are installing Everyplace Synchronization Server, create the following directory: ess_home\NotesData, where ess_home is the location where you will install the Everyplace Synchronization Server. The default location is C:\Program Files\WebSphere\IBMSyncServer
- If you are installing Intelligent Notification Services, create the following directory: ins_home\NotesData, where ins_home is the location where you will install Intelligent Notification Services. The default location is C:\Program Files\WebSphere\INS
Copy the contents of the Notes Client data directory (C:\Program Files\Lotus\Notes\Data) to the new directories you created in the previous step.
- If you are installing Everyplace Synchronization Server, copy the contents of C:\Program Files\Lotus\Notes\Data to the: ess_home\NotesData directory, where ess_home is the location where you will install the Everyplace Synchronization Server. The default location is C:\Program Files\WebSphere\IBMSyncServer
- If you are installing Intelligent Notification Services, copy the contents of C:\Program Files\Lotus\Notes\Data to the: ins_home\NotesData directory, where ins_home is the location where you will install Intelligent Notification Services. The default location is C:\Program Files\WebSphere\INS
Add the Notes client directory to the system PATH variable.
Note: If you do not add this to the system PATH, you will encounter problems when you attempt to setup subscriptions. The Intelligent Notification Subscription Administration portlet will not be able to save the Lotus Domino Administrator ID or password and other server values. .
1. Right-click the My Computer icon and select Properties.
2. Select the Advanced tab.
3. Click Environment Variables.
4. In the System variables region, select the Path variable and click Edit.
5. In the Variable Value field, add the Notes client installation directory to the end of the variable. Remember to type a semicolon at the end of the Variable Value before adding the Notes client path. For example, add the following:
```
;C:\Program Files\Lotus\Notes
```
6. Click OK to close the Environment Variables dialog box.
7. Click OK to close the System Properties dialog box.
Rename the notes.ini file to notes.save. You will find the notes.ini file in the following location: C:\Program Files\Lotus\Notes.
For Everyplace Synchronization Server, perform the following steps:
1. Copy the C:\Program Files\Lotus\Notes\notes.save file to ess_home\NotesData\notes.ini
2. Open the ess_home\NotesData\notes.ini file in a text editor and edit the Directory parameter to point to the ess_home\NotesData\ directory. For example:
```
Directory=C:\Program Files\WebSphere\IBMSyncServer\NotesData
```
3. Open a command prompt.
4. Within this command prompt, from the ess_home\NotesData directory, launch the Notes Client by typing notes.exe
5. Configure the Notes Client to use the Notes ID that you obtained for the Everyplace Synchronization Server. You need the Domino Server Notes ID file in order to perform this configuration:
  1. At the Welcome screen, click Next.
  2. Enter the Domino Server Notes ID in the Your name field.
  3. Enter the Domino server and check the I want to connect to Domino Server check box.
  4. Click Next.
  5. Click Browse to locate the Notes ID file, and click Next.
  6. Click Yes to copy the Notes ID file to the data directory.
  7. Enter your Password, and click OK.
  8. In the Additional Services panel, leave the default selections and click Finish.
6. Close the Notes Client after configuring.
7. Close the command prompt.
For Intelligent Notification Services, perform the following steps. Note, if you are installing both Intelligent Notification Services and Everyplace Synchronization Server, you will configure the Notes Client twice, once for each feature.
1. Copy the C:\Program Files\Lotus\Notes\notes.save file to ins_home\NotesData and rename it to notes.ini.
2. Open the ins_home\NotesData\notes.ini file in a text editor and edit the Directory parameter to point to the ins_home\NotesData\ directory. For example:
```
Directory=C:\Program Files\WebSphere\INS\NotesData
```
3. Open a command prompt.
4. Within this command prompt, from the ins_home\NotesData directory, launch the Notes Client by typing notes.exe
5. Configure the Notes Client to use the Notes ID that you obtained for the Intelligent Notification Services. You need the Domino Server Notes ID file in order to perform this configuration:
  1. At the Welcome screen, click Next.
  2. Enter the Domino Server Notes ID in the Your name field.
  3. Enter the Domino server and check the I want to connect to Domino Server check box.
  4. Click Next.
  5. Click Browse to locate the Notes ID file, and click Next.
  6. Click Yes to copy the Notes ID file to the data directory.
  7. Enter your Password, and click OK.
  8. In the Additional Services panel, leave the default selections and click Finish.
6. Close the Notes Client after configuring.
7. Close the command prompt.

Next steps

The next step is to prepare for specific components.

If you are installing Everyplace Synchronization Server, see Preparing to install the adapters.
If you are installing Intelligent Notification Services see, Preparing to install Mail & Calendar Services

Parent topic: Preparing to install

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. :