Using Setup Manager

WebSphere Everyplace Access

Using Setup Manager

Overview
Setup Manager options
Response file
Example installation process
Setup Manager log files
Install properties file (wea.properties)
Related information

Setup Manager is an integrated installation program that enables you to install all Everyplace Access components. In addition, using Setup Manager, you can install the required software for Everyplace Access, such as WebSphere Application Server, IBM HTTP Server, WebSphere Portal, Directory Server and DB2.

Setup Manager does the following:

Requires IBM JRE Version 1.3.1 Fixpack 2 to run. Setup Manager automatically installs this level of the JRE, if it does not exist on the machine.
Checks for existing components in the environment.
- If you have a previous version of DB2, you must upgrade it to the required level, Version 7.2 Fixpack 7 , before running Setup Manager. Refer to CD contents to locate the fixpack for your environment.
- If WebSphere Application Server Version 4.0.4 , WebSphere Portal Version 4.2, or both are detected, Setup Manager will not apply the most current efixes and fixpacks, but the install will proceed. If you need to update WebSphere Application Server or WebSphere Portal, you should do so before running Setup Manager. If you are migrating from Everyplace Access 4.2.1 or if you have older versions of components such as WebSphere Application Server, refer to the Use existing software topic.
- If Setup Manager detects older versions of other components, the install will not proceed. In which case you must either remove or update the existing component. Setup Manager cannot detect third-party software versions. Therefore, it cannot verify the version of supported LDAP directories other than Directory Server. You must manually verify the version for these components.
Pre-installation verification of the following:
- Operating system and its prerequisites
- RAM requirements
- System paging settings
- Disk space available (done after selecting components)
Installs the following components and their corequisite components, based on your selection:
- Everyplace Access core services (When needed, this also installs WebSphere Application Server Advanced Edition, IBM HTTP Server, WebSphere Portal, DB2 Universal Database Enterprise Edition, and Directory Server.)
- Device Manager (When needed, this also installs WebSphere Application Server Advanced Edition, IBM HTTP Server, and DB2 Universal Database Enterprise Edition.)
- Everyplace Intelligent Notification Services (When needed, this also installs WebSphere Application Server Advanced Edition, IBM HTTP Server, and DB2 Universal Database Enterprise Edition.)
- Everyplace Synchronization Server (When needed, this also installs DB2 Everyplace if selected, WebSphere Application Server Advanced Edition, IBM HTTP Server, and DB2 Universal Database Enterprise Edition.)
- Location Aware Services (When needed, this also installs WebSphere Application Server Advanced Edition, IBM HTTP Server, and DB2 Universal Database Enterprise Edition.)
- IBM Directory Server (When needed, this also installs IBM HTTP Server and DB2 Universal Database Enterprise Edition.)
- WebSphere Portal (When needed, this also installs WebSphere Application Server Advanced Edition, IBM HTTP Server, and DB2 Universal Database Enterprise Edition.)
Creates the following user groups:
- dmadmins
  Members of this group have the ability to view, edit and manage Device Management and Everyplace Client Installer portlets. They can also log in to the Device Manager console.
- essadmins
  Members of this group have the ability to view, edit and manage Everyplace Synchronization user and administration portlets.
- essusers
  Members of this group have the ability to view and edit Everyplace Synchronization user portlets.
- insadmins
  Members of this group have the ability to view, edit and manage Notification Services user and administration portlets.
- insusers
  Members of this group have the ability to view and edit Notification Services user portlets.
- lasadmins
  Members of this group have the ability to view, edit and manage Location Aware Services administration portlets.

Note: The following components are not installed by Everyplace Access Setup Manager. Each of these components have a separate installation programs.

IBM Directory Server fix pack 1 and interim fix 1(Fixes are provided on the Everyplace Access CDs.)
IBM Everyplace Client
WebSphere Studio Site Developer Advanced
IBM WebSphere Studio Device Developer
DB2 Everyplace SDK

Setup Manager options

Setup Manager provides three installation options. You can choose the one that best meets your needs.

Silent installation
Quick installation
Standard installation

Silent installation

Silent installation is designed to install components using a supplied set of configuration parameters. A set of predetermined components are installed on a single host and component interdependencies and subcomponent selections are managed for you. Silent installation requires the use of configuration information stored in a response file to automatically install the components. Refer to the Response file topic for information on generating and customizing response file.

Quick installation

Quick installation is designed to install components with minimal configuration. This option works well for setting up proof of concept and development environments because all components are installed on one machine, while allowing you to connect to existing backend systems.

A single host install allows you to use remote or existing backend data storage, such as Lotus Domino and DB2. It is recommended that you gather the information required during installation before starting Setup Manager. If you do not have the access information for all your backend data stores, you can configure the access information for Synchronization Server adapters after the install. Record your access information in the Quick install checklist for future reference.

Standard installation

Standard installation is the similar to Quick installation, except it gives you more flexibility in the components you can choose to install. Standard installation has the ability to use information stored in a response file to automatically prefill all the setup information for the components. Refer to the Response file topic for more information.

It is recommended that you gather the information recommended during installation before starting Setup Manager. If you do not have the access information for all your backend data stores, you can configure the access information for Synchronization Server adapters after the install. Record your access information in the Standard install checklist for future reference.

Standard install options

If you select to use Standard install, you should be familiar with the following options. To install Everyplace Access in a production environment, you will run Setup Manager multiple times to install the appropriate components across multiple machines in your environment. Refer to Best practices for more information.

Portal extension
Portal extensions represent components that extend the portal or run as a portal service, such as portlets, Web services and portal service. For example, when you select Portal extensions for Everyplace Access core services, Setup Manager will install Offline, device management, productivity and PIM portlets. You cannot remotely install Portal extensions. For example, to install Synchronization Server Portal extensions, you need to run Setup Manager Standard install on the machine where WebSphere Portal is installed and select the Synchronization Server Portal extensions option.
Services
Services represent component application servers and enterprise applications. For example, if you select to install Client services for Everyplace Access core services, Setup Manager will install the Device Management configuration and Offline Portal Content servlets, and client users services.
Database setup
Database setup represents database or table creation. For example, if you select Database setup for Synchronization Server, Setup Manager will create the needed databases or tables. If you do not select Database setup, Setup Manager assumes you have already created the database and will only prompt for the information needed to catalog the existing database.

Response file

Setup Manager provides the ability to store responses to installation and configuration questions, asked during installation, in a file called a response file. For Standard installs, you can use this file as a template for performing another install on the same machine. Using a response file speeds up repeated installations on the same machine using the Silent install option and provides a template for similar installations on other machines using the Standard install option.

Default response file

Setup Manager provides a default response file that is used during Quick install and can be selected during Standard install. This response file provides default values that are prefilled into the installation fields to help you complete the configuration information. Setup Manager saves changes to a different response file after installation is complete. Response files must be modified using Setup Manager. Manual modification is not supported and may cause installation failure.

After installation Setup Manager saves the response file to the following file, so that the default response file is never overwritten:
Windows:
c:\Program Files\IBMWEA\wea_response.autosave.script

Unix:
usr/IBMWPO/script/wea_response.autosave.script

Note: Setup Manager must be used to modify a response file. Editing a response file outside of Setup Manager may cause installation failure.

Customize the default response file

Run Setup Manager in either Quick or Standard installation mode.
On the Load response file panel, browse to open the default response file. Leave the default response file name unchanged and continue.
The values stored in the default response file are displayed in the subsequent Setup Manager panels.
Customize the information with values specific to your environment (for example user ID, password and hostname).
After completing a Quick or Standard installation, you have a complete custom, for your environment, response file that can be used with Silent, Quick, or Standard installation.
- Silent install: When used with Silent installation all the values are defined so there is no information asked for during installation. This is very useful when reinstalling the same components on the same machine again.
- Standard install: When used with a Standard installation you are able to install a similar setup on additional machines. The information you have defined in the response file is displayed in the Setup Manager panels. Customize this information for the machine you are on.
It is recommended that you make a copy of your new custom response file to backup any changes that have been made. After installation, the default response file is located in the following directory:
C:\Program Files\IBMWEA\wea_response.autosave.script
Where C:\ is the drive where Everyplace Access is installed.

Example installation process

The table below shows the four installation types and how the installation process differs for each.

Installation step	Silent	Quick	Standard
License, information, and installation selection	Go through the initial installation panels for license acceptance and prerequisites. Setup Manager checks for existing components.
Installation type selection	Silent install Note: Quick or Standard install must have been used prior to doing a Silent install to customize a response file for your environment.	Quick install Note: Not supported if there are existing components on the machine.	Standard install
Response file	Use of a response file is required to continue.	Default response file is automatically chosen.	May use a response file to speed up information entry.
Component selection	Response file determines component selection.	Response file determines component selection.If you are using the default response file and have not altered it, all components are installed.	You are asked to select components to be installed.
Collect installation information	Response file contains information.	Prompt for basic configuration information only: Fully-qualified host name LDAP suffix DB2 install directory WebSphere install directory Administrator ID Administrator password The response file contains that rest of the information.	Collected in a series of Setup Manager panels.
Summary panel	None. Installation begins after selecting a response file to use and clicking Next.	None. Installation begins after selecting synchronization adapters and clicking Next.	A summary panel shows all the information collected and provides an opportunity for review and modification.
Native component installation panels	Not applicable
Installation begins	File installation begins.
Reboot for Windows Log out for AIX	If a Windows reboot is needed, for IBM HTTP Server, do not reboot. For all other components, for example as part of the DB2 installation, the installation program restarts the server and restarts Setup Manager automatically when reboot is done. For an AIX install, you should log out and log in.
Configuration during installation	During installation you are provided instructions for setting the AdminRole in WebSphere Application Server for use with WebSphere Portal. This must be completed before continuing the installation.
Change CDs	You are prompted to insert the appropriate CDs as needed.
Logs	When installation is complete, validate success by checking the installation log files.

Setup Manager log files

Setup Manager updates a parent log and generates a different child log for each component it attempts to install. In turn, each component may also generate additional logs. The Setup Manager parent log can be found in the following directory:

Windows:
C:\Program Files\IBMWEA\logs\IBMWEAdate.log

AIX:
/usr/IBMWPO/setupdate.log

For more information about logs, see Install logs.

Install properties file (wea.properties)

Setup Manager saves information about the components you selected to install in wea.properties. When you launch Setup Manager, this file is saved to the local drive. Each time you run Setup Manager on the machine, it references wea.properties to determine which components are already installed. You cannot select to install components that are already installed. The integrated uninstaller uses this file to determine which components are available to uninstall. The properties file can be found in the following default location:

Windows:
C:\Program Files\IBMWEA\conf\

AIX:
/usr/IBMWPO/conf/

Note:	Typically you should not edit this file. But if you do need to edit the file, make a backup copy of the file first.

Below is a sample wea.properties file. The sample indicates that none of the Everyplace Access components are installed, Installed=false. The file uses acronyms for each component, for example EAK represents Everyplace Access core services, ESS represents Synchronization Server, DB2E represents DB2 Everyplace, INS represents Intelligent Notification Services, DMS represents Device Manager and LAS represents Location Aware Services.

Sample wea.properties file

Sample wea.properties file
EAKServicesInstalled=false EAKServicesVersion=4.3.0.0 EAKDatabaseInstalled=false EAKDatabaseVersion=4.3.0.0 EAKPortalintInstalled=false EAKPortalintVersion=4.3.0.0 ESSServerInstalled=false ESSServerVersion=1.3.0 ESSDbInstalled=false ESSDbVersion=1.3.0 ESSPortletsInstalled=false ESSPortletsVersion=1.3.0 DB2EDbInstalled=false DB2EDbVersion=8.1 DB2ECoreInstalled=false DB2ECoreVersion=8.1 INSSubInstalled=false INSSubVersion=1.2.2 INSMSGInstalled=false INSMsgVersion=1.2.2 INSPortletsInstalled=false INSPortletsVersion=1.2.2 INSDbInstalled=false INSDbVersion=1.2.2 DMSDbInstalled=false DMSDbVersion=4.3 DMSCoreInstalled=false DMSCoreVersion=4.3 LASDatabaseInstalled=false LASDatabaseVersion=1.0.0.0 LASPortletsInstalled=false LASPortletsVersion=1.0.0.0 WEACoreLevel=4.3 BSCoreInstalled=false WEACoreInstalled=false BSOfflineDbInstalled=false EAKInstallLocation=C:\\WebSphere\\WEACoreServices

 

EAKServicesInstalled=false 
EAKServicesVersion=4.3.0.0
EAKDatabaseInstalled=false
EAKDatabaseVersion=4.3.0.0
EAKPortalintInstalled=false
EAKPortalintVersion=4.3.0.0

ESSServerInstalled=false
ESSServerVersion=1.3.0
ESSDbInstalled=false
ESSDbVersion=1.3.0
ESSPortletsInstalled=false
ESSPortletsVersion=1.3.0

DB2EDbInstalled=false
DB2EDbVersion=8.1
DB2ECoreInstalled=false
DB2ECoreVersion=8.1

INSSubInstalled=false
INSSubVersion=1.2.2
INSMSGInstalled=false
INSMsgVersion=1.2.2
INSPortletsInstalled=false
INSPortletsVersion=1.2.2
INSDbInstalled=false
INSDbVersion=1.2.2

DMSDbInstalled=false
DMSDbVersion=4.3
DMSCoreInstalled=false
DMSCoreVersion=4.3

LASDatabaseInstalled=false
LASDatabaseVersion=1.0.0.0
LASPortletsInstalled=false
LASPortletsVersion=1.0.0.0
WEACoreLevel=4.3
BSCoreInstalled=false
WEACoreInstalled=false
BSOfflineDbInstalled=false
EAKInstallLocation=C:\\WebSphere\\WEACoreServices

Related information
CD contents Use existing software Quick install checklist Standard install checklist Install logs Best practices