WEA: Hardware and software requirements

 

The WebSphere Everyplace Access has specific hardware and software requirements and component prerequisites that need to be understood prior to installation. These requirements were accurate at the time this information was published and reflects what was used during testing and quality assurance. As newer versions of software are supported, information will be provided in the WebSphere Everyplace Access support page. If you do not see the version listed that you require, contact IBM Support before proceeding.

1. Operating systems
2. Hardware
3. Prerequisite software
4. Additional Everyplace Access Services requirements
5. Additional Everyplace Synchronization Server requirements
6. Additional Intelligent Notification Services software requirements

 

Operating systems

WebSphere Everyplace Access has been tested with the following operating systems and other versions are not supported. If you do not see the version that you need, contact IBM Support. You can install WebSphere Everyplace Access across multiple computers, however you cannot mix the operating systems on which you install components. Meaning you cannot install Everyplace Synchronization on a Windows 2000 Server and install Device Manager on an AIX server. The only exception is where you install the database server. You can install all WebSphere Everyplace Access components on Windows 2000 servers, but install the database, or databases, on AIX.

• Windows 2000 Server Service Pack 4 (32-bit version only)
• Windows 2000 Advanced Server Service Pack 4 (32-bit version only)
• AIX 5.2 (32-bit version only)

Note: Windows 2000 Professional is supported for the InfoCenter but not for the project install.

Hardware

WebSphere Everyplace Access components and prerequisite software have unique hardware needs. The requirements below provide minimal guidelines for installing WebSphere Everyplace Access on a single computer. Disk space requirements are broken down by component to help you calculate requirements if you install the databases across multiple computers or install multiple components on a single computer.

• Processor: This is the minimum recommended processor for WebSphere Everyplace Access on a single computer.

  AIX: IBM eServer pSeries 1GHz or higher.

  Windows: Pentium 4 processor at 2 GHz or higher

• Disk space

  Table 1. AIX disk space requirements. Disk space requirements for WebSphere Everyplace Access prerequisites and components.

  	/	/usr	/var	/tmp	/home	Unique locations
  WebSphere Portal	0	350 MB	0	500 MB (500 MB additional space required during installation)	200 MB (/home/db_instance)
  WebSphere Portal Fix Packs	0	800 MB	0	10 MB	0
  WebSphere Application Server	0	Base: 539 MB Enterprise: 539 + 83 MB	0	100 MB	0
  WebSphere Application Server Fix Packs	0	500 MB	0	100 MB	0
  WebSphere Network Deployment Manager	0	Base: 539 MB Enterprise: 539 + 65 MB	0	100 MB	0
  WebSphere Network Deployment Manager Fix Packs	0	500MB	0	100 MB	0
  IBM HTTP Server	0	25.5 MB	0	100 MB	0
  DB2 Universal Database	0	300 - 500 MB	0	10 MB	200 MB (DB2 Control database)
  IBM Directory Server	0	160 MB	0	100 MB	100 MB (/home/ldapdb_instance)
  Everyplace Access Services	10 K	75 MB	0	20 MB	200 MB
  Everyplace Synchronization Server	0	175 MB	0	20 MB	300 MB (database installation) (estimate 45 MB per user for typical usage)
  DB2 Everyplace	0	110 MB	0	120 MB (during installation)	300 MB (includes data storage after configuration)
  Device Manager	0	165 MB	0	20 MB		35 MB in /db/db2 400 MB in user specified location, such as /dmsdb
  Intelligent Notification Services	64 K	145 MB (465 MB if using Notes RPC)	0	20 MB	200 MB
  Location Aware Services	0	120 MB	0	20 MB	80 MB
  WebSphere Everyplace Access InfoCenter	0	100 MB	0	20 MB	0

  Table 2. Windows disk space requirements. Disk space requirements for WebSphere Everyplace Access prerequisites and components.

  	Temporary space	Data space	Installation space	Default install location
  WebSphere Portal	500 MB	200 MB (used for the DB2 databases)	350 MB (350 MB additional space required during installation)	C:\Program Files\WebSphere\PortalServer
  WebSphere Portal Fix Packs	10 MB		800 MB	C:\Program Files\WebSphere\PortalServer
  WebSphere Application Server	100 MB	0	Base: 520 MB Enterprise: 520 + 83 MB	C:\Program Files\WebSphere\AppServer
  WebSphere Application Server Fix Packs	100 MB	0	500 MB	C:\Program Files\WebSphere\AppServer
  WebSphere Application Server Network Deployment Manager	100 MB	0	Base: 520 MB Enterprise: 520 + 65MB	C:\Program Files\WebSphere\DeploymentManager
  WebSphere Application Server Network Deployment Manager Fix Packs	100 MB	0	500 MB	C:\Program Files\WebSphere\DeploymentManager
  IBM HTTP Server	10 MB	0	18 MB	C:\Program Files\IBM HTTP Server
  DB2 Universal Database	10 MB	200 MB	300 - 500 MB	C:\Program Files\IBM\SQLLIB
  IBM Directory Server (not including DB2)	20 MB	100 MB	110 MB 25 MB database	C:\Program Files\IBM\LDAP
  Everyplace Access Services	20 MB	200 MB	350 MB	C:\Program Files\WebSphere\EAS
  Everyplace Synchronization Server	20 MB	540 MB (data storage)	580 MB (installation)	C:\Program Files\WebSphere\IBMSyncServer
  DB2 Everyplace	120 MB	200 MB (data storage, including Control and 2 sample databases)	90 MB (installation)	C:\Program Files\WebSphere\DB2Everyplace81
  Device Manager	20 MB	400 MB	175 MB	C:\Program Files\WebSphere\DMS16
  Intelligent Notification Services	20 MB	200 MB	330 MB (plus an additional 90 MB if using MCS Notes RPC)	C:\Program Files\WebSphere\INS
  Location Aware Services	20 MB	80 MB	120 MB	C:\Program Files\WebSphere\LAS
  WebSphere Everyplace Access InfoCenter	20 MB	0	100 MB	C:\Program Files\WebSphere\doc

  Description of the column headings used in the Windows disk space table:

  • Temporary space Typically found in C:\Documents and Settings\admin\Local Settings\Temp

  • Data space This space is used when configuring databases, typically found in C:\db2

  • Installation space This is the space required for the installation and configuration files. This space does not include the database.

  • Default install location This is the directory where the software is installed.

• Physical memory

  2 GB at a minimum

• Network connectivity

  To use Everyplace Access Services across a network, the following elements are required:

  • Network adapter and connection to a physical network that can carry IP packets. For example, Ethernet, Token Ring, ATM, and so on.
  • Static IP address Configured with a fully-qualified host.name. The portal system must be able to resolve an IP address from its fully qualified host name. To ensure that this is configured correctly, you can issue the ping command from a command line. An example command is: ping hostname.yourco.com, where hostname.yourco.com is the fully-qualified host.name.

• Other hardware
  • CD-ROM or access to a network drive where WebSphere Everyplace Access CD contents are located.
  • Mouse or pointing device and keyboard

Prerequisite software

Most WebSphere Everyplace Access components require the following software: DB2 Workgroup, WebSphere Application Server, WebSphere Portal Server, and an LDAP server. Depending on your network environment, you might already have some of the prerequisite software installed. If you do not have the prerequisite software, use the WebSphere Everyplace Access install program to install it. If you plan to using existing installations of prerequisite software, gather some information before you start the installation, such as Administrator IDs and passwords, host names, and more.

Note: Each component has additional software requirements, review the component software requirements before installing each component. Database server

The following components require a database server to store user and application data: DB2 Everyplace, Device Manager, Everyplace Access Services, Everyplace Synchronization Server, Intelligent Notification Services, and Location Aware Services. The database server can be on the same computer as the component or on another computer, such as a dedicated database server. If the database will be on another computer, install the database client. WebSphere Portal can also store custom user registry data in DB2 Workgroup, instead of in an LDAP server. If you do plan to store portal user data in IBM Directory Server, it is important to note that IBM Directory Server includes DB2 Express, but you can use DB2 Workgroup with it if needed. If you want to use DB2 Workgroup instead, install DB2 Workgroup on the computer first.

Note: During a Component Install, WebSphere Portal Server installs Cloudscape as the portal database. Instructions for migrating from Cloudscape to DB2 Workgroup are provided. Cloudscape is not installed during a Basic Install.

Supported databases:

• DB2 Universal Database Enterprise Edition V8.1.6
• DB2 Universal Database Workgroup Edition V8.1.6 (Included with WebSphere Everyplace Access)

If you want to use an existing installation of DB2, you will need to gather information about the installed database server before installing WebSphere Everyplace Access. Refer to the Plan worksheet for WebSphere Everyplace Access for prerequisites.

Note: To synchronize data from your enterprise databases, use DB2 Everyplace. DB2 Everyplace supports synchronizing data with DB2 data sources or any data sources with a JDBC interface. Directory server

WebSphere Everyplace Access supports a number of directory servers which are listed below. IBM Directory Server is included on the WebSphere Everyplace Access product CDs. You should not install the directory server on the same computer as WebSphere Portal. For a Basic Install you can also store user data in a DB2 database, referred to as a custom user registry.

Supported directory servers:

• IBM Directory Server 5.1(Included with WebSphere Everyplace Access)
• Microsoft Active Directory 2000
• Lotus Domino Directory Server 5.0.12, 6.0.x, and 6.5.x

If you already have an LDAP server installed, collect information about the LDAP server before installing WebSphere Everyplace Access. You also need to configure the LDAP server for portal server before installing WebSphere Portal Server. Use the Planning worksheet for prerequisites to gather information about your LDAP server. Refer to the Configuring the LDAP server topic in this InfoCenter to learn more about configuring the LDAP for WebSphere Everyplace Access.

Note: If you are using Microsoft Active Directory, you cannot use WebSphere Portal to create and users and groups unless you configure WebSphere Application Server to use LDAP over SSL. This is described in the topic Configuring the portal for Microsoft Active Directory. create the users and groups required for WebSphere Everyplace Access before you install the Everyplace Access components. WebSphere Application Server

The following components require WebSphere Application Server to run enterprise applications: DB2 Everyplace, Device Manager, Everyplace Access Services, Everyplace Synchronization Server, Intelligent Notification Services, and Location Aware Services. WebSphere Portal also requires the WebSphere Application Server.

If you plan to install WebSphere Everyplace Access components on multiple computers, install and configure Deployment Manager.

Supported WebSphere Application Servers:

• WebSphere Application Server Base V5.0.2.3 (included with WebSphere Everyplace Access)
• WebSphere Application Server Enterprise V5.0.2 (included with WebSphere Everyplace Access)

WebSphere Portal Server

All WebSphere Everyplace Access components require WebSphere Portal Server, except Device Manager server. However, Device Management portlets included with Everyplace Access Services require WebSphere Portal. If you want to install using an existing installation of a supported version of WebSphere Portal Server, refer to Install with an existing WebSphere Portal.

Supported WebSphere Portal Servers:

• WebSphere Portal Enable 5.0.2.1(Included with WebSphere Everyplace Access)
• WebSphere Portal Extend 5.0.2.1

Web server

If you are behind a firewall, need a dedicated network dispatcher, or both, install the Web server on a different computer than WebSphere Everyplace Access components and prerequisite software. Decide where you will install the Web server.

Supported HTTP Servers:

• IBM HTTP Server V1.3.26 (Included with WebSphere Everyplace Access)

Supported Web browsers

A Web browser is required to use administration and end-user portlets. You can only work with administration portlets using a desktop browser.

The following desktop browsers are supported:

• Windows:
  • Microsoft Internet Explorer 5.5, 5.5 SP2, or 6.0 SP1,
  • Mozilla 1.0.2, 1.2.1, 1.3, or 1.4
  • Netscape Communicator 6.2 or 7.0
  • Opera Web Browser 7.11 (or higher)

• AIX:
  • Netscape Communicator 6.2 or 7.0

The following browsers are supported on handheld devices:

• Pocket Internet Explorer (on Pocket PC 2002 and Windows Mobile 2003
• Web Pro Browser V2 (on Palm Tungsten C and updated Tungsten W devices)
• Opera 7.25 (included on Sharp SL-6000)
• Opera 6.02 browser (on Sony Ericsson P900)
• Netfront Browser (on Windows Mobile Software 2003 for viewing xHTML and X+V portlets)
• Blazer 3.0 (on Treo 600)

Additional Everyplace Access Services requirements

Everyplace Access Services includes portlets that have been enhanced to render correctly on supported handheld devices. To deliver portal content to BlackBerry devices, have the following installed and configured:

• A BlackBerry Enterprise Server must be installed and configured for the supported BlackBerry devices in your network. The BlackBerry Enterprise Server must include the Mobile Data Service V1.1.3.5
• BlackBerry devices must be configured. Use the BlackBerry Desktop Manager to associate the device with an e-mail accounts and with the BlackBerry Enterprise Server.
• The BlackBerry device must be in range of the network.
• The WebSphere Everyplace Access portal server must be started.

Additional Everyplace Synchronization Server requirements

WebSphere Everyplace Access provide Lotus Notes and Microsoft Exchange portlets so users can work with PIM and e-mail data from anywhere using a supported Web browser. Everyplace Synchronization Server provides PIM and e-mail data synchronization between supported handheld devices and supported mail servers. Intelligent Notification Services supports sending notifications to e-mail accounts on supported mail servers. The following mail servers are supported in a WebSphere Everyplace Access environment for both AIX and Windows operating systems. To communicate with the mail database, a mail client is required.

Supported mail servers:

• Lotus Domino V5.0.12 to 6.5.1 (versions 6.0.4 or 6.5.1 or higher are recommended)

  For Windows, a Lotus Notes Client 6.0.1 is required on the same computer as the Lotus Domino Adapter for Everyplace Synchronization Server.

  For AIX, install a Domino Server V6.01 on the same computer as the Everyplace Synchronization Server.

  1 MB of free disk space is required for the Everyplace Synchronization Field Conversion Database.

  Note: A Lotus Domino server and Microsoft Exchange Server should not be installed on the same computer.
• Microsoft Exchange 2000 Service Pack 2

  A Web-based Distributed Authoring and Versioning (WebDAV) compliant HTTP server (such as the Microsoft Internet Information Services ) is required on the same computer as the Microsoft Exchange 2000 Adapter for Everyplace Synchronization Server.

  Note: To avoid port conflicts, do not install the WebSphere Application Server and Microsoft Exchange server on the same computer.
• Microsoft Exchange 5.5

  Outlook 98, 2000 with Workgroup option, or 2002 SP 3 is required on the same computer as the Microsoft Exchange 5.5 Adapter for Everyplace Synchronization Server.

  Microsoft Extended Messaging Application Programming Interface (MAPI) is required to communicate with the Exchange 5.5 Server. The Simple MAPI interface is installed with Windows, and the Extended MAPI is installed with Outlook. MAPI is only available on Windows, so the Microsoft Exchange 5.5 adapter is only available on Windows.

Additional Intelligent Notification Services software requirements

WebSphere embedded JMS provider or WebSphere MQ

WebSphere embedded JMS provider or WebSphere MQ are required for high volumes of subscriptions or notifications.

Lotus Notes Client or Domino Server V6.0.1 CF3

Mail and Calendar Services requires you to install Lotus Notes Client 6.0.1 CF3 on a Windows operating systems and Domino Server Version 6.0.1 CF3 on AIX operating systems. The Notes Client or Domino Server must be installed on the same computer as Intelligent Notification Services. If you install WebSphere Portal on a different computer from Intelligent Notification, install the Lotus Notes Client (Windows) and Lotus Domino Server (AIX) on both the Intelligent Notification and WebSphere Portal computers.

WebSphere Everyplace Connection Manager (optional)

WebSphere Everyplace Connection Manager is a distributed, scalable, multipurpose UNIX communications platform that supports optimized, secure data access by both Wireless Application Protocol (WAP) and non-WAP clients over a wide range of international wireless network technologies, as well as local area (LAN) and wide area (WAN) wireline networks. WebSphere Everyplace Connection Manager allows access to enterprise applications from networks outside the enterprise using a virtual private network (VPN) tunnel.

Both Everyplace Client and Mobility Clients can be installed on the same handheld device and can be operated at the same time to provide a secure connection with the WebSphere Everyplace Access server.

Supported WebSphere Everyplace Connections Manager versions:

• WebSphere Everyplace Connection Manager 5.0
• WebSphere Everyplace Connection Manager 5.1

Sametime Server (optional)

Sametime Server with Sametime Server extensions for Mobile Access provides instant messaging services for mobile devices. Current Sametime customers can download Sametime Server extensions for Mobile Access from the Passport Advantage Web site.

Supported Sametime Server:

• Lotus Sametime Server 3.0
• Sametime Server extensions for Mobile Access (required for integration with WebSphere Everyplace Access)

WebSphere Voice Server and WebSphere Voice Response, Version 3.1.1 (optional)

WebSphere Voice Server and WebSphere Voice Response, V3.1.1 are required for voice notifications.

Next Steps

Now that you understand the WebSphere Everyplace Access requirements, you are ready to review the Plan worksheet for prerequisite software. Use the worksheet to either gather information about your existing network or to gather information as you install and configure the prerequisites.

 

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.