Creating a WebSphere Portal environment suitable for cloning with

Creating a WebSphere Portal environment suitable for cloning with VMware Bill Barrus Gary Elliott John Ferenczi IBM Pervasive Computing September 2004 © Copyright International Business Machines Corporation 2004. All rights reserved.

Introduction .................................................................................................................................... 2

Background................................................................................................................................ 2 Audience .................................................................................................................................... 3 Minimum hardware and software requirements .................................................................. 3

Hardware................................................................................................................................ 3 Software ................................................................................................................................. 3

VMware overview ......................................................................................................................... 4 Before you begin........................................................................................................................... 5

Obtaining the software ............................................................................................................. 5 End configuration...................................................................................................................... 5 Time required ............................................................................................................................ 5

Step 1. Preparing the system ..................................................................................................... 6 Defining the guest virtual machine......................................................................................... 6 Installing the base O/S and configure the network adapter............................................... 6 Creating and configuring installation userids ....................................................................... 7 Disabling IIS .............................................................................................................................. 8

Step 2. Installing WebSphere Portal ......................................................................................... 9 Step 3. Installing WebSphere Application Server Fixpack................................................... 10 Step 4. Installing WebSphere Portal ....................................................................................... 11 Step 5. Installing DB2 and Fixpack 2 ...................................................................................... 13

Installing DB2 .......................................................................................................................... 13 Installing DB2 fixpack 2 ......................................................................................................... 14

Step 6. Migrating the portal system parameters.................................................................... 14 Step 7. Installing Directory Server ........................................................................................... 16 Step 8. Configuring WebSphere Portal for security .............................................................. 17 Step 9. Configuring remote access to the portal installation ............................................... 20 Step 10. Cloning the image to another computer.................................................................. 21 Summary...................................................................................................................................... 22 Resources.................................................................................................................................... 22 About the authors ....................................................................................................................... 23 Acknowledgements .................................................................................................................... 23

Introduction This article provides detailed directions for installing IBM® WebSphere® Portal Version 5 in a Windows 2000 Server environment in such a way that it can be easily copied to another computer without having to re-install.

Background WebSphere Portal is a premier platform for portal development. Other IBM products, such as WebSphere Voice Application Access, and WebSphere Everyplace Access, extend the functionality WebSphere Portal, which serves as the base. Even though the installation of WebSphere Portal is considerably simpler with Version 5, the time to install a full portal production-like environment, including all the prerequisite and co-requisite (such as IBM Tivoli Directory Server and DB2), can be significant.

Creating a WebSphere Portal environment suitable for cloning with VMware 2

Enterprises frequently need to install multiple complete environments. If there were a way to clone these environments, it would certainly reduce start up time, and make these enterprises more productive. The problem to be solved with cloning a portal environment is how to use a generic host and domain name and to be able to deploy the same image to other computers.

VMware™ is an Intel™ based product that lets operating systems run in a virtual environment, which makes cloning to another computer much easier. VMware provides isolation between the host computer and the guest virtual computers. VMware also provides translation of TCP/IP addresses from the host to the guest computer using network address translation (NAT) and port fowarding.

This article shows you how to install WebSphere Portal once in a Windows 2000 Server environment, isolating it with a generic hostname and domain behind a VMware image so that it can be easily copied to another computer, without re-installing the product set. As with any product installation, you must ensure that you have all the appropriate product licenses, for the operating system and for applications, when you either receive or deploy a VMware image.

Audience This article is for application developers and others interested in deploying a proof of concept environment. Some end products are only supported on the more advanced versions of VMware. The scenario in this article uses the VMware Workstation product.

To perform the tasks described here, you should a working knowledge of:

• WebSphere Portal administration • WebSphere Application Server • Web and Java technologies, such as HTML, XML, JSP

Minimum hardware and software requirements See the VMware documentation for the requirements of the VMware installation and each guest operating system. The following minimum system is suggested:

Hardware IBM-compatible PC: Intel Pentium III 1.5 GHz processor or better Memory: 2-3 GB RAM Disk space: 15 GB or more for Operating System and all product components CD-ROM drive Mouse or pointing device and keyboard Network communications adapter

Software Windows 2000 Server and Service Pack 4

If you plan to install additional products on top of WebSphere Portal (such as WebSphere Voice Application Access or WebSphere Everyplace Access) see the installation or InfoCenter document to determine additional requirements.


VMware overview VMware is software which enables multiple operating systems and their applications to run concurrently on a single physical machine. It provides a virtual machine environment abstraction layer by allowing each guest operating system to run independently with its own set of virtual devices (such as BIOS, memory, disk, network adapter, and video). A virtual memory manager intercepts I/O requests from the guest virtual machine, allowing the guest operating system to run as if it were the only operating system running on the machine. Device support is provided through translation to the host operating system’s real device drivers.

VMware has a variety of products that are designed to support an increasing complex environment. The scenario in this article uses the VMware Workstation product because the article is intended for the portal developer.

Figure 1. VMware hosted architecture


Before you begin In the instructions that follow, the placeholder items in angle brackets < > indicate that you need to substitute your installation specific parameters, without angle brackets.

Placeholder Example substitution <was_root> c:\Program Files\WebSphere\AppServer

<wps_root> c:\Program Files\WebSphere\PortalServer

<ids_root> c:\Program Files\IBM\LDAP

<your password> The password which you assigned

Obtaining the software The steps below assume you are using CD images downloaded from IBM Partnerworld Software Mall that are expanded onto your hard drive. The WebSphere Portal installation files used as a reference for this article were extracted from the WebSphere Voice Application Access v5.0 bundle, which includes several e-Assembly ( “eASSY”) groups of CD images. Only the CD images from the WebSphere Portal V5.0 group are used here; this group includes the additional required IBM products, such as IBM Tivoli Directory Server and DB2.

Alternatively, you could use the WebSphere Portal V5.0.2 - WebSphere Portal Enable for Multiplatforms, V5.0.2 e-Assembly.

End configuration The scenario below takes you through building this configuration on a Windows 2000 Server system:

IBM WebSphere Application Server V5.0.2 IBM WebSphere Portal V5.0.2 DB2 V8.1 FP2 IBM Tivoli Directory Server V5.1 with Fixpack 2 IBM HTTP Server 1.3.26

This procedure uses this generic server network name:

hostname = mywebsphere domain = localdomain.com

Important: If you use VMware and your host system uses multiple display support, switch to single display mode while performing this installation procedure.

Time required Plan at least 8-12 hours to complete the entire installation.


http://www.developer.ibm.com/welcome/softmall.html


Step 1. Preparing the system In this section, you create the initial VMware image, install the base Windows operating system, and initialize all system userids and parameters required for installing WebSphere Application Server and WebSphere Portal.

Defining the guest virtual machine 1. Start VMware Workstation.

2. From the Home tab, select New Virtual Machine.

3. Step through the Wizard using the following specifications:

• Custom Virtual machine configuration • Microsoft Windows 2000 Server • Enter Virtual machine name of your choice • Memory size of 1.5-2GB (guest memory)

Important: Setting the guest memory size larger than the amount of available memory in the host will have a negative affect on performance.

• Use Network address translation (NAT) Network Connection • Default I/O adapter type • Create a new virtual disk • Default Virtual Disk Type • 15GB Disk size. Check the box, Split into 2GB files (to aid movement of files) • Default Disk file

Installing the base O/S and configure the network adapter In this step you install Windows 2000 Server in the guest virtual machine and configure its network adapter so that it uses the NAT adapter of the VMware host machine. In the guest virtual machine:

1. Insert a Windows 2000 Server install CD into your CDROM drive and select Start this virtual machine from the VMware window.

2. Install Windows 2000 Server SP4 and all critical fixes from Windows Update. 3. Logon as Administrator. 4. Right-click on the My Computer desktop icon, select Properties-> Network

Identification-> Properties. 5. Enter computer name: mywebsphere 6. Select More... 7. In the Primary DNS suffix for this computer field, type: localdomain.com 8. Reboot the computer. 9. Logon as Administrator. 10. Determine the subnet address VMware has assigned to your NAT adapter.

VMware defaults VMnet8 as your NAT adapter (for example, 192.182.62.0). 11. From the VMware window, select Edit -> Virtual Network Settings.


12. Select an address for your guest between 3 and 127 (for example, 10). By default, VMware reserves address 1 for your Host machine, 2 for the subnet gateway, and 128-254 for DHCP addresses.

13. To set up your guest Network Adapter: a) On the Windows Taskbar, select Start-> Settings-> Network and Dial-up Connections. b) Right-click on Local Area Connection, and select Properties. c) Select Internet Protocol (TCP/IP), and click Properties. d) Select Use the following IP address e) Enter parameters relative to your VMware NAT adapter subnet. For example:

IP address 192.182.62.10

Subnet mask 255.255.255.0

Default gateway 192.182.62.2

f) Select Use the following DNS server addresses, and enter the main DNS that is used by your host machine.

g) Click Advanced, and select the DNS tab. h) Enter localdomain.com in the DNS suffix for this connection field. i) Click OK until the Local Area Connection Properties window closes.

14. Add an entry in <windows_root>\system32\drivers\etc\hosts file for your IP. Use either: 192.182.62.10 mywebsphere.localdomain.com or 192.182.62.10 mywebsphere mywebsphere.localdomain.com

15. From a command line, enter: ping -a <your ip> (for example, ping -a 192.182.62.10) It should return: Pinging mywebsphere.localdomain.com [192.182.62.10] ......

Creating and configuring installation userids 1. Logon as Administrator. 2. Create a new directory in c:\Program Files\WebSphere\PortalServer and name it:

log directory (that is, c:\Program Files\WebSphere\PortalServer\log directory )

3. To create two new userids and add them to the Administrator’s group: a) Right-click on My Computer, and select Manage. b) Expand Local Users and Groups. c) Right-click on Users, select New User; then enter:

User name wpsadmin

Full name wpsadmin

Description wpsadmin

Password <temppwd>

Confirm password <temppwd>

d) Select Create, and enter the next user data: User name wpsbind

Full name wpsbind

Description wpsbind


Password <temppwd>

Confirm password

<temppwd>

e) Select Create -> Close. f) Select Users. g) Right-click on wpsadmin, select Properties. h) Select Member Of tab, and then click Add. i) Select Administrators->Add->Ok->Apply->Close. j) Repeat the three previous steps to add wpsbind to the Administrators group. k) Close the Computer Management window.

4. To give wpsadmin and wpsbind authority for system wide security (advanced user rights): a) On the Windows Task bar, select Start->Programs->Administrative Tools->Local

Security Policy. b) Double-click on Local Policies. c) Double-click on User Rights Assignments. d) Double-click on Act as part of the operating system. e) Select Add. f) Select wpsadmin. g) Hold the Ctrl key and select wpsbind (so that both userid's are highlighted). h) Select Add->OK->OK. i) Double-click on Log on as a service. j) Select Add. k) Select wpsadmin. l) Hold the Ctrl key and select wpsbind. m) Select Add->OK->OK. n) Close the Local Security Settings window.

Disabling IIS Windows Internet Information Services uses TCP/IP port 80. Therefore, you need to stop and disable that service so that it will not conflict with IBM HTTP Server. 1. Select Start->Programs->Administrative Tools->Services. 2. Right-click IIS Admin Service, and select Properties. 3. Change Startup Type to Disabled, and select Stop to stop the server. 4. Select Yes to stop any services stopped as a result. 5. Select Apply, and then click OK. 6. Right-click World Wide Web Publishing Service, and select Properties. 7. Change Startup Type to Disabled. 8. Select Apply, and then click OK. 9. Log off Administrator. 10. Log on to wpsbind, and then to wpsadmin, to set your final passwords. Log on to wpsadmin

last because you will use that id through out the installation and deployment process. 11. Open Internet Explorer to ensure your connectivity has been established; the Connection

Wizard establishes your connection setting the first time.


Step 2. Installing WebSphere Portal Plan about 3.5 hours for step 2. This step takes you through downloading the software images and starting to install the software. You start the main installation wizard, which in turn, calls other wizards to install WebSphere Application Server V5.0.1, then WebSphere Portal V5.0, and other, co-requisite products. The instructions assume you download the images from IBM Partnerworld Software Mall onto your hard file. You can arrange the downloaded files so that you won’t be prompted for CDs during the base Portal 5.0 install. Expand each zip or exe file into a cdXXX directory using the CD number in parenthesis from the download description. For example, suppose the description in the IBM PartnerWorld Software Mall entry is: Download 4 of 54: WebSphere Portal V5.0 - Certain Components of WebSphereApplication Server Enterprise for Windows,V5.0.1 (1-1)

Then, expand this image into a directory, called cd1-1 . Make sure all cdXXX directories are under one common directory; for example for WebSphere Portal V5.0, you might use:

WPSv5.0

cdSetupcd1-1cd1-2

During the installation of WebSphere Portal, you are asked to create several passwords and specify certain configuration parameters. If you use WebSphere Portal as a base for another product, some of these passwords and parameters are required during the installation of the other product. Therefore, it is important that you record this information now. Check the Installation Worksheet section in the target product’s Information Center.

Troubleshooting: If the installation fails, remove the files under this directory before you restart the installation: C:\Document and Settings\wpsadmin\Local Setting\Temp\ .

To begin the installation:

1. Login as wpsadmin. 2. From Window Explorer, double-click:

cdSetup\install (MS-DOS batch file) 3. Separate installation wizards are automatically invoked for WebSphere Application Server,

WebSphere Portal, and WebSphere Portal Content Publishing (WPCP). Accept the default parameters, and enter appropriate passwords when prompted, except as follows: a) In the (main) installer wizard, for Enter the Portal administrative user and password

window, enter wpsadmin for userid and <wpsadmin password> for password. b) In the WebSphere Portal Content Publishing installer wizard:

i) For the Please enter WebSphere Application Server Information window (scroll down to see), Select No for Is WebSphere Application Server security enabled?

ii) For the Please specify the location of the WPCP database window, select Cloudscape from the Database Type list.



4. After the installation has completed, test the installation by opening the portal using a Web browser: http://mywebsphere.localdomain.com:9081/wps/portal

Figure 2. WebSphere Portal front page

Step 3. Installing WebSphere Application Server Fixpack Plan about 1 hour for step 3. In this step, you apply required fixes to bring the WebSphere Application Server up to the v5.0.2 level. 1. Stop WebSphere Application Server server1 and WebSphere Application Server

WebSphere_Portal by typing the following on Windows command line:

cd <was_root>\binstopServer server1stopServer WebSphere_Portal

2. To stop IBM HTTP Administration and IBM HTTP Server : a) In Windows, select Start->Programs->Administrative Tools->Services. b) Right-click on each entry and select Stop.

3. To stop any Java processes.

a) Right-click on the Task Bar. b) Select Task Manager, and then select the Processes tab. c) Check Show process from all users d) Select Image Name to sort by name. e) Right-click on any Java.exe process and select End Process.


http://mywebsphere.localdomain.com:9081/wps/portal

4. Enter the following on Windows command line, to start applying the fixes. Important: You must apply the fixes in this order: wasfp2, pmefp2, fixes.

cd <was_root>\binsetupCmdLinecd cd1-17\wasfp2\winupdateWizard

The Wizard launches as a separate process. Use the defaults, and select Finish when completed. Then enter the following: cd cd1-17\pmefp2\winupdateWizard

Use defaults, select Finish when complete.

cd cd1-17\fixes\winupdateWizard

Use defaults, except select Install fixes instead of the default Install fix packs, check all fixes under Install. Finally, enter:

cd <was_root>\binversioninfo

You should see both the base and Enterprise WebSphere Application Server at the 5.0.2 level). Figure 3: Confirming the fixes were installed

Step 4. Installing WebSphere Portal Plan about 1 hour for this step. In this step, you apply the fixes required to bring the WebSphere Portal Server up to the v5.0.2 level.


1. Stop server1 and WebSphere_Portal from the above Windows command line (one or both

may be stopped from the previous task):. server1WebSphere_Portal

2. Stop HTTP admin and HTTP servers from the Windows Services menu (one or both may be

stopped from the previous task): HTTP adminHTTP servers

3. Using the same Windows command line as above, enter this command. (If you use a new window, set up the environment variable by entering <was_root>\bin\setupCmdLine): cd cdFixpack

4. Enter the following on a single line, separated by blanks, and include the double quotes: updatePortal -fixpack -installDir "<wps_root>" -fixpackDir "cdFixpack"-install -fixpackID WP_PTF_502

5. If the WP-PTF-502 task is successful, start IBM HTTP Server: a) Select Start->Programs->Administrative Tools->Services. b) Right-click on IBM HTTP Server, and select Start. If the WP-PTF-502 task fails refer to the WebSphere Portal 5.0.2 FIX PACK README.

6. From same Windows command line (Be sure to specify the dashes in the fixpack id as indicated.): cd <wps_root>\configWPSconfig WP-PTF-502 -DPortalAdminPwd=<wpsadmin password>

7. Verify that <wps_root>\version\MP.product indicates that the version is 5.0.2.0. 8. Verify that WebSphere_Portal is started, by entering:

<was_root>\bin\serverStatus WebSphere_Portal

9. Verify you can log into portal, using the wpsadmin userid. Open the following in a Web

browser, as shown in Figure 4: http://mywebsphere.localdomain.com:9081/wps/portal


http://publib.boulder.ibm.com/pvc/wp/502/ent/en/readme/install_win_unix.html


Figure 4. Login to WebSphere Portal

Step 5. Installing DB2 and Fixpack 2 Plan about 15 minutes for this step. In this step, you install DB2 V8.1 to replace Cloudscape as the portal server database. DB2 is a prerequisite for many IBM add-on products.

Installing DB2 Important: You cannot install DB2 version 8 from a network mapped drive using a remote Windows 200 Terminal session.

1. To stop the servers, from a Windows command line enter cd <was_root>\binserverStop server1serverStop WebSphere_Portal

2. From Window Explorer, double-click cd5-1\setup. 3. Select Install Products 4. Throughout the process, accept all defaults except for the following:

a) On the Set user information for the DB2 Administration Server screen


i) Leave Domain blank (it will create a local user). ii) Enter the <db2admin password> for Password and Confirm Password.

b) On the Specify a contact for health monitor notification screen, select Defer the task until after installation is complete.

5. When install completes, select Finish. 6. Select Exit First Steps.

Installing DB2 fixpack 2 1. To open a DB2 Command prompt window:

Select Start->Programs->IBM DB2->Command Line Tools->Command Window. 2. Enter the following commands:

db2stopdb2admin stop

3. From Windows Explorer, double-click: cd5-7\db2fp\win\update 4. If you see a message indicating that several DB2 process are running, select Yes to shutdown

these processes. 5. Select Update to apply the DB2 fixpack.

Step 6. Migrating the portal system parameters

Plan about 45 minutes for this step. You migrate the WebSphere Portal system parameters from the Cloudscape data base to DB2.

1. From a Windows command line, make sure that the portal server is stopped (should be stopped from previous step). cd <was_root>\binserverStop WebSphere_Portal

2. Export the existing data from the Cloudscape database. This could take about 10 minutes. cd <wps_root>\configWPSconfig database-transfer-export

3. Make a backup copy of, and then edit: <wps_root>\config\helpers\transfer_db2.properties

4. Make these changes then save the file. DbLibrary C:/Program Files/IBM/SQLLIB/java/db2java.zip

DbUser db2admin

DbPassword <db2admin password>

WmmDbUser db2admin

WmmDbPassword <db2admin password>

WpcpDbUser db2admin

WpcpDbPassword <db2admin password>

FeedbackDbUser db2admin

FeedbackDbPassword <db2admin password>


5. To import the contents of transfer_db2.properties into the WebSphere Portal configuration file, type the following as one line, separated by blanks, and include the double quotes: WPSconfig

-DparentProperties="<wps_root>\config\helpers\transfer_db2.properties"-DSaveParentProperties=true

6. To create a local DB2 database, which creates WPS50, WPCP50, and FDBK50 databases in DB2, enter this command. (This can take about 5 minutes.) WPSconfig create-local-database-db2

7. Test databases connections (each response should end with BUILD SUCCESSFUL) WPSconfig validate-database-connection-wpsWPSconfig validate-database-connection-wmmWPSconfig validate-database-connection-wpcp

8. Import the data to the target database (can take 20 minutes). WPSconfig database-transfer-import

9. To improve performance, perform a DB2 reorg check: a) Open a DB2 Command prompt window:

Start->Programs->IBM DB2->Command Line Tools->Command Window. b) Enter the following commands

db2 connect to wps50 user db2admin using <db2admin password>db2 reorgchk update statistics on table alldb2 terminatedb2rbind wps50 -l db2rbind.out -u db2admin -p <db2admin password>

c) Repeat step 9b, changing the database name from wps50 to wpcp50. d) Repeat step 9b again, changing the database name to fdbk50.

10. Enter the following in a Windows command line to start server1; then, wait for the “..open

for e-business..” message: cd <was_root>\bin\startServer server1

11. In a Web browser, enter the following to open the WebSphere Application Server Admin console; then log in using wpsadmin id: http://mywebsphere.localdomain.com:9090/admin

12. Add DB2 to the class path on WebSphere Application Server: a) Select Servers->Application Servers from the left frame. b) Select WebSphere_Portal from the list of Application Servers. c) Select Process Definition from the list of Additional Properties (scroll down). d) Select Java Virtual Machine from the list of Additional Properties. e) In the Classpath field, under General Properties, enter the following new line after the

existing line: C:/PROGRA~1/IBM/SQLLIB/java/db2java.zip f) Scroll down, and select OK. g) Select Save at the top of the frame. h) Select Save under Save to Master Configuration.


http://mywebsphere.localdomain.com:9090/admin

i) Select Logout from the top of the Admin Console.

13. Type the following on a Windows command line to start the portal server; then, wait for “..open for e-business..” message. cd <was_root>\binstartServer WebSphere_Portal

14. Open WebSphere Portal in a Web browser, and logon using wpsadmin as the userid:


15. If successful, logout from WebSphere Portal. If not successful, check the following log files for errors, correct the problem, then re-attempt this step. c:\Program Files\WebSphere\AppServer\logs\WebSphere_Portal\startServer.logc:\Program Files\WebSphere\PortalServer\log\SystemOut.logc:\Program Files\WebSphere\PortalServer\log\wps_YYYY.MM.DD-HH.MM.SS,log (a current date and time stamped log file)

16. Log into the WebSphere Application Server Admin Console, using wpsadmin: http://mywebsphere.localdomain.com:9090/admin

17. Verify the database connections: a) Select Resources-> JDBC Providers from the left frame. b) Select wps50JDBC from the list of JDBC Providers. c) Select Data Sources from Additional Properties. d) Individually check each Data Source in the Name column; then, select Test Connection.

You should see a successful message at the top. e) Logout from the Admin Console.

Step 7. Installing Directory Server Plan about 5 minutes for this task. You install the IBM Directory Server (LDAP) product which will be used as the user repository. LDAP support is a prerequisite for many IBM add-on products. 1. From Window Explorer, double-click cd3-1\ids_ismp\setup. 2. Throughout the process, accept all defaults except for the following:

a) On the Choose the setup type that best suits your needs screen, select Custom. b) On the Select the Features to Install screen, de-select IBM WebSphere Application

Server - Express 5.0 (114M). 3. After the installation completes and your system reboots, the IBM Directory Server

Configurations Tool starts. 4. Choose File->Close to terminate the tool and let the system startup to complete.



http://mywebsphere.localdomain.com:9090/admin

Step 8. Configuring WebSphere Portal for security Plan about one hour for this task. You configure WebSphere Portal V5.0.2 for LDAP use and you turn on WebSphere Application Server security. 1. Start Directory Server Configurations Tool by either entering ldapxcfg on a command line,

or selecting Start->Programs->IBM Directory Server 5.1->Directory Configuration.

2. To set IDS Administrator DN and password: a) Select Administrator DN/password from the left frame. b) Keep the default Administrator DN of cn=root. c) In the Administrators password and confirm password fileds, enter:

<Administrator password> d) Click OK.

3. To configure a directory database (10 minutes):

a) Select Configure Database from the left frame. b) Keep the default option Create a new database. c) Enter User ID as db2admin and Password as <db2admin password>. d) Enter Database name as ldapdb2. e) Keep default option Create a universal DB2 database (UTF-8/UCS-2). f) Keep default Database location of C. g) Select Finish. h) Select Close when complete.

4. To load a sample database (5 minutes):

a) Select Manage Suffixes from the left frame. b) Enter o=ibm,c=us in the SuffixDN field. c) Select Add. d) Select OK. e) Select Import LDIF data from the left frame. f) In the Path and LDIF file name field, enter (or browse to locate):

<ids_root>\examples\sampleldif g) Select Import. h) Select Close when you see the message:

ldif2db: 50 entries have been successfully added out of 50 attempted.

5. From a Windows command line, start IDS

Ibmslapd

6. Stop IDS by entering ctrl-C once you see the message IBM Directory (SSL), Version 5.1 Server started.

7. Start the Directory Server Configurations Tool by entering ldapxcfg from a command line or using Start->Programs->IBM Directory Server 5.1->Directory Configuration.

8. Enter your specific location SuffixDN. Important: IDS defaults to a generic suffix of dc=yourco, dc=com (equating to a domain of


yourco.com). For this procedure, we use dc=localdomain,dc=com. Your own domain may include more parameters like yourco.yourlocation.com, which equates to a SuffixDN of dc=yourco,dc-yourlocation,dc=com. a) Select Manage Suffixes from the left frame. b) In the SuffixDN field, type: dc=localdomain,dc=com c) Select Add. d) Select OK.

9. To add your specific location updates to the PortalUsers.ldif file:

a) Copy cdSetup\PortalUsers.ldif to c:\temp. b) Edit c:\temp\PortalUsers.ldif as follows:

i) Change all references of yourco to localdomain (leave any uid or cn parameters as is).

ii) Change the userpassword: line for wpsadmin and wpsbind to <your password>. c) Save c:\temp\PortalUsers.ldif .

10. To import the PortalUsers.ldif file, using the IBM Directory Server Configuration Tool:

a) Select Import LDIF data in the left frame. b) Select Clear results to enable field entry (you may have to scroll right). c) Enter (or browse to) c:\temp\PortalUsers.ldif in the Path and LDIF file name

field. d) Select Import. e) Select Close when you see the message:

ldif2db: 6 entries have been successfully added out of 6 attempted.

11. From a Windows command line, start IDS: Ibmslapd

12. From another Windows command line, verify you can do an LDAP query to your LDIF entries, by entering the following as one line, separated by blanks, and include the double quotes: ldapsearch

-b "dc=localdomain,dc=com"-h mywebsphere.localdomain.com-D "uid=wpsbind,cn=users,dc=localdomain,dc=com"-w "<wpsbind password>""(&(uid=wpsadmin)(objectclass=inetOrgPerson))"

13. Repeat the above query, changing wpsadmin to wpsbind. If either of these queries produces errors, see the Directory Server documentation to remove the LDIF data and correct the ldif file.

14. Make a backup copy of the WebSphere Portal configuration template file: <wps_root>\config\helpers\security_ibm_dir_server.properties

15. Edit the WebSphere Portal configuration template file as follows: WasUserid uid=wpsbind,cn=users,dc=localdomain,dc=com


WasPassword <wpsbind password>

WpsHostName mywebsphere.localdomain.com

PortalAdminId uid=wpsadmin,cn=users,dc=localdomain,dc=com

PortalAdminPwd <wpsadmin password>

PortalAdminGroupId cn=wpsadmins,cn=groups,dc=localdomain,dc=com

LTPAPassword <Administrators password>

SSoDomainName localdomain.com

LDAPHostName mywebsphere.localdomain.com

LDAPAdminUId cn=root

LDAPAdminPwd <Administrators password>

LDAPBindID uid=wpsbind,cn=users,dc=localdomain,dc=com

LDAPBindPassword <wpsbind password>

LDAPSuffix dc=localdomain,dc=com

16. From a Windows command line, start the Application Server service and stop the portal service: cd <was_root>\binstartServer server1stopServer WebSphere_Portal

17. Import the WebSphere Portal configuration template file into wpconfig.properties: cd <wps_root>\config\ Enter the following on a single line, separated by blanks, and include the double quotes: WPSconfig-DparentProperties="<wps_root>\config\helpers\security_ibm_dir_server.properties"

-DSaveParentProperties=true

18. Test connections to the directory (Directory Server should already be started). WPSconfig validate-ldap

19. Enable Portal security (5 minutes) WPSconfig enable-security-ldap

20. Stop and restart the servers: cd <was_root>\binstopServer server1startServer server1stopServer WebSphere_Portal -user wpsbind -password <wpsbind password>startServer WebSphere_Portal -user wpsbind -password <wpsbind password> Important: Now you always have to start and stop WebSphere_Portal using the wpsbind id and password.

21. To install the existing system portlets, enter on the command line (15 minutes): cd <wps_root>\config\installportlets <wpsadmin password> mywebsphere.localdomain.com 9081

22. From a Web browser, logon to WebSphere Portal using the wpsadmin id: http://mywebsphere.localdomain.com:9081/wps/portal

23. Create a new user to verify LDAP is working:



a) Logout from WebSphere Portal wpsadmin id. b) Select Sign up. c) Enter data for the new user. d) Try logging in as that user.

You have just completed the WebSphere Portal V5.0.2 installation !

Step 9. Configuring remote access to the portal installation Perform the following if you want to access the portal installation from a Web browser on your host computer or on another client computer. This procedure configures VMware to forward network requests that are made to your host computer onto your guest computer’s WebSphere Portal installation.

1. Configure port forwarding in VMware for the desired ports. From your VMware window: a) Select Edit -> Virtual Network Settings. b) Look at the Summary information to determine the NAT Virtual Network (defaults to

VMnet8). c) Select the NAT tab. d) Select the NAT adapter (for example, VMnet8) from the VMnet Host pulldown. e) Click the Edit button. f) Click the Port forwarding button. g) Click the Add button from the Incoming TCP window. h) Enter Host port = 9081. i) Enter Forwarding IP address = 192.182.62.10 9081

The target port field has no label; it is to the right of the IP field. j) Enter a Description of your choosing. k) Click OK. l) Repeat the above 5 steps for additional ports as needed (for example, 80) m) Click OK until you return to the NAT tab window. n) Select the Restart service button.

2. Add an entry in <windows_root>\system32\drivers\etc\hosts for your host computer

or client computer IP on your intranet (not the virtual address of the guest machine). For example: 9.3.28.44 mywebsphere.localdomain.com

3. From a browser on your Host or Client computer, Logon to Portal using wpsadmin id http://mywebsphere.localdomain.com:9081/wps/portal

4. Log off from the portal and sign up a new user: a) Select Sign up. b) Fill in data. c) Select Continue.

5. Verify you can logon to WebSphere Portal using the new id.



Step 10. Cloning the image to another computer In this section you deploy the complete WebSphere Portal V5.0.2 VMware image to a VMware installation on a different computer.

1. Shutdown your WebSphere Portal installation by selecting Start->Shutdown from with your guest computer.

2. Optionally, shrink your WebSphere Portal installation’s virtual disk, to significantly reduce the size of the image you are cloning. See VMware Help-> Users Manual. From the Contents section, select Using Disks-> Configuring Hard Disk Storage in a Virtual Machine-> Defragmenting and Shrinking Virtual Disks).

3. From the VMware window (with your WebSphere Portal installation tab displayed), look at the Configuration file line.

4. Copy the entire directory that includes the configuration file to the new computer that also has VMware installed. The default target directory is My Documents-> My Virtual Machines.

5. On the new computer, start VMware, and select Open Existing Virtual Machine. 6. Select the Configuration file (.vmx) from the new directory. 7. Select Open. 8. Select VM-> Setting from the VMware window. 9. To improve performance, adjust the Virtual Memory setting below what is available on your

host machine. 10. Click OK. 11. Select Start this Virtual Machine. 12. Accept the default Create a new identifier to the prompt The location of the virtual

machine has changed since it was last powered on. 13. Click OK. 14. Determine the subnet address VMware has assigned to your NAT adapter (because it is

probably different on the new computer). VMware defaults VMnet8 as your NAT adapter (for example, 192.168.225.0) From your VMware window, select Edit -> Virtual Network Settings.

15. Update your guest Network Adapter to the new subnet: a) Select Start-> Settings-> Network and Dial-up Connections. b) Right-click on Local Area Connection, and select Properties. c) Select Internet Protocol (TCP/IP), and click the Properties button. d) Select Use the following IP address. e) Enter parameters relative to your VMware NAT adapter subnet; for example:

IP Address 192.168.225.10

Subnet Mask 255.255.255.0

Default Gateway 192.168.225.2

f) Select Use the following DNS server addresses. g) Enter the main DNS that is used by your host machine. h) From your VMware window, select Edit->Virtual Network Settings. i) Look at the Summary information to determine the NAT Virtual Network (defaults to

VMnet8). j) Select the NAT tab.


k) Select the NAT adapter (for example, VMnet8) from the VMnet Host pulldown, and click the Edit button.

l) Click the Port forwarding button. m) Click the Add button from the Incoming TCP window. n) Enter Host port = 9081. o) Enter Forwarding IP address = 192. 168.225.10 (tab) 9081. p) Enter a Description of your choosing. q) Click OK. r) Repeat the above 5 steps for additional ports as needed (for example, 80). s) Click OK until you return to the NAT tab window. t) Click the Restart service button.

16. Add an entry in <windows_root>\system32\drivers\etc\hosts file for your IP; for example: 192. 168.225.10 mywebsphere.localdomain.com

17. From a command line, enter ping -a <your ip> (for example, ping -a 192. 168.225.10) It should return Pinging mywebsphere.localdomain.com [192. 168.225.10] ......

18. Update your Host computer’s or any Client computer’s hosts file to point to the new computer’s Host intranet IP address.

Summary This article walked you through installing an isolated WebSphere Portal installation using the VMware product. You built an image using all the required components to obtain a WebSphere Portal V5.0.2 installation that uses LDAP, DB2, and has security enabled. After the installation, you cloned (copy) this image to another VMware installation, and invoke the WebSphere Portal server with a minimal amount of re-configuration of network addresses.

Resources • IBM Partnerworld Software Mall


• VMware product website http://www.vmware.com

• IBM WebSphere Portal for Multiplatforms Version 5.0.2 InfoCenter

http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html

• WebSphere Portal and Lotus Workplace Catalog http://catalog.lotus.com/wps/portal/portalworkplace

• developerWorks WebSphere http://www.ibm.com/developerworks/websphere



http://www.vmware.com/

http://publib.boulder.ibm.com/pvc/wp/502/ent/en/InfoCenter/index.html

http://catalog.lotus.com/wps/portal/portalworkplace

http://www.ibm.com/developerworks/websphere


• WebSphere Portal zone http://www.ibm.com/developerworks/websphere/zones/portal

About the authors Bill Barrus is a Senior Solution Architect in IBM Software Group's Business Development and Partner Enablement function. He has worked with numerous business partners involved with the integration of solutions ranging from service provider billing and rating services to field service applications and portlets. Bill is currently focusing on the integration of IBM's Extension Services for WebSphere Everyplace with a major supplier of insurance company applications, and integration of voice partner applications with IBM's voice technologies. Gary Elliott is a Solution Architect in IBM Pervasive Computing. He has worked with numerous business partners in various industries related to the integration of pervasive solutions for enterprises. His experience includes integrations with WebSphere Voice Application Access and integrations including new device enablement with WebSphere Everyplace Access. John Ferenczi is a Senior Solutions Architect in IBM Pervasive Computing. He has worked with a wide range of business partners in virtually all business sectors. He is currently involved with a number of partners who are integrating their voice products with IBM's voice and portal technologies. You can reach the authors by sending a note to [email protected].

Acknowledgements The authors would like to thank these individuals for their contributions to this article:

• Adam Orentlicher, Jing Fu, Kevin Henson – WebSphere Voice Application Access • Sung-Ik Son – WebSphere Portal

Trademarks

• DB2, IBM, and WebSphere are trademarks or registered trademarks of IBM Corporation in the United States, other countries, or both.

• Windows and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

• Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

• Other company, product, and service names may be trademarks or service marks of others. IBM copyright and trademark information: http://www.ibm.com/legal/copytrade.phtml

http://www.ibm.com/developerworks/websphere/zones/portal

mailto:[email protected]

http://www.ibm.com/legal/copytrade.phtml