IBM WebSphere Everyplace Access V5 Handbook for Developers and Administrators Volume IV: Advanced Topics

256 IBM WebSphere Everyplace Access V5, Volume IV: Advanced Topics

The variables in this command are as follows:

򐂰 was_home is the directory where WebSphere Application Server is installed.

򐂰 dm_host is the host name of the computer where you installed Deployment

Manager.

򐂰 dm_port is the Deployment Manager SOAP connector-address. The default

value is 8879.

򐂰 admin_user_id is the administrator ID that you used to administer the

application server and log in to the WebSphere Application Server

Administrative Console.

򐂰 admin_password is the password for the administrator ID used to administer

the application server.

The includeapps command transfers the complete set of applications installed

on this node into the master configuration for Deployment Manager. This should

be included only when adding the first node to the cell.

To avoid Web server plug-in configuration problems, the WpsAdminconsole

Enterprise Application must be removed from the master configuration of the cell.

7.5.2 Installing WebSphere Everyplace Access Services

The base component for WebSphere Everyplace Access is the WebSphere

Everyplace Access Services. All other servers should be installed only after

installing the WebSphere Everyplace Access Services. Installing WebSphere

Everyplace Access Services is a two-step process. The first step is to laydown

the installation file set and then configure the specific components, such as the

database, portal extensions, or the server on appropriate nodes. The install files

have to copied to the database machine, server machine, and the portal

machine.

Installing the WebSphere Everyplace Access Services file set

You must install the WebSphere Everyplace Access Services files on the

database node, WebSphere Portal node, and the WebSphere Application Server

nodes. Installing the WebSphere Everyplace Access Services file set copies the

files onto the local file system. You have to configure the WebSphere Everyplace

Access Services databases, portal integration services, and the client services

on appropriate nodes later. To lay down the install file sets:

1. Insert the Setup disc into the CD-ROM drive and run install.bat from the root

directory of the CD.

2. Select Component Install and click Next.

Chapter 7. Clustering WebSphere Everyplace Access nodes 257

3. Select Everyplace Access Services V5.0 from the list of WebSphere

Everyplace Access components. Click Next to continue.

4. Insert the CD for WebSphere Everyplace Access Services as instructed on

the panel. If you are using a network image or have copied the CD contents to

a network drive, click Browse and find the CD directory on the shared

network drive. Click Next to continue. If the install program can find the CD

automatically, you will not be prompted for a CD location, and the WebSphere

Everyplace Access Services install will start automatically.

5. Select the language for the installation, and click OK. The welcome panel of

the WebSphere Everyplace Access Services install program opens. Click

Next to continue.

6. Enter the directory where you want to install WebSphere Everyplace Access

Services. If the directory that you specify does not exist, it is created. Click

Next.

7. Review the summary information to validate the install directory. Click Next to

start copying files.

Configuring WebSphere Everyplace Access Services

databases

The WebSphere Everyplace Access Services database stores information about

Offline Portal Content and packages for Device Management.

After you lay down the install file set, you need to run the configuration tasks to

install the databases by running a configuration task. The input to this

configuration is through the file EASinstallconfig.properties file, which is in the

eas_install\config folder. You need to modify the properties shown in

Example 7-4 on page 258 to suite your environment.

258 IBM WebSphere Everyplace Access V5, Volume IV: Advanced Topics

Example 7-4 Modifying the EASinstallconfig.properties file

instDatabaseInstall=true

instServerInstall=false

instPortalIntegration=false

instNotesPortlets=false

instExchangePortlets=false

instDMS=false

instBlackBerry=false

instDBType=db2

instDBPath=C:/Program Files/IBM/SQLLIB

instDBAdminName=db2admin

instDBAdminPassword = {ENCODED}2747119a11d039

instJDBCDriverName=COM.ibm.db2.jdbc.app.DB2Driver

instJDBCImplementationClassname=COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource

instJDBCDriverPath=C:/Program Files/IBM/SQLLIB/java/db2java.zip

instDBServerHostname=spotest60.in.ibm.com

instDBLocalInstance=DB2

instWEASDB=WEASDB

instWPSHostname=spotest30.in.ibm.com

After you modify the configuration file, run the following command to configure

the WebSphere Everyplace Access Services database:

EASDBconfig.bat eas-db-config

Cataloging WebSphere Everyplace Access Services

databases Application Server and portal node

If the WebSphere Everyplace Access Services database is on a different

computer than application and portal servers, then you need to catalog the

WebSphere Everyplace Access Services databases on these nodes. By

cataloging, you are specifying database information such as which machine to

connect, which node to connect, which administrative ID should be used, and so

on.

To catalog the databases:

1. Log in as a user with administrative privileges.

2. Set DB2COMM to TCP/IP using the command:

db2set DB2COMM=tcpip

Note: After you have installed the WebSphere Everyplace Access Services

database, open the EASinstallconfig.properties file and set the

instDatabaseInstall property to false.