2.9 Installation worksheet

 < Day Day Up > 

2.9 Installation worksheet

Table 2-3 summarizes all the installation steps which are listed in the README file. You can use it as a worksheet with our "to-do's" and comments, and add your own.

Table 2-3: Installation worksheet to use as a guide for your own installation

Step number and name


Variables used



1. Read package content


There are three main components of this installation, step (4-7) to complete the LDAP Server and it's TDBM, step (5,6,8-11) to complete the Portal Server, and step (12) to deploy the base portlets. Use a LDAP browser to validate the LDAP Server is working can save lots of troubleshooting times later.


Review Portal V4.1.2 Readme file


Verify that WebSphere Application Server V4.01 is up


Install Unicode code support


Re-IPL required to activate the Unicode support

2. Unpack WebSphere Portal files


2.1 base product

Complete SMP/E installation


Make sure the HFS file size is at least 600 cyls. Also the /tmp size is large enough for all the log files.


Unpack tar files


You should have six tar files

Run with UID=0

2.2 PTF2

Complete SMP/E steps for PTF2


Run with UID=0


Copy ejppiPTF.jcl to your install PDS lib <HLQ>.JOBS.C NTL.


Change all variables and submit ejppiPTF job


Check for rc=0

#WPS#: in JCL is the WPS HFS location (e.g. /usr/lpp/PortalServer);

#DRVNUM# is 4.1.2


See what directories have been created


Option: Use Oget to copy all the required JCLs from <WPS_PATH>/z osinst/jcl to <YourHLQ>.JO BS.CNTL now. Those JCLs will be needed for modification later.


EX: /usr/lpp/PortalServer/PortalS erver/zosinst/jcl

Run with UID=0

3. Save the log files

All jobs use and add to the same log file

<WPS_PATH> /Install.log


Make backups of log files for troubleshooting.


This job use two log files WPSADMIN

<WPS_PATH> /zosinst/scripts /wps.admin.lo g <WPS_PATH> /Install.log



This job uses two log files WPACONF

<WPS_PATH> /temp/jobs/log/ WPConversati on_date_time.l og <WPS_PATH> /Install.log


This job use two log files WPSUNINS

<WPS_PATH> /WPConversat ion_date_time. log <WPS_PATH> /Install.log


4. Edit Setup file

Oedit this setup file Refer to Appendix A.for environment variables

<WPS_PATH> zosinstall/scrip ts/wps.setup.in


Make backup of the original and save your changed setup to safe place UID=0 required


<WPS_PATH> : Installation path of WebSphere Portal Server (WPS), not the HFS location which is referenced as <WPS> or #WPS#. Ex. WSPORT

Compare your variables with Appendix A

You should spend enough time to assure all the variables are entered correctly. Because it will be very time-consuming to troubleshoot those errors or make changes later. Some of the variables need to match with what your installation use. Ex: WebSphere, JDK, SysplexID and DB2 environment variables.


<WPS_SERV ERNAME>: WPS Server region name

The WPS Server region's STC name. Both step 5 (WLM) and step 6 (RACF) steps will use it



<WPS_CTLR EGIONID>: WPS control region Server userid


Step 6 uses it


<WPS_PROC NAME>: WPS control region Procedure name. Ex: WSPORT

WPS Control region STC name.

WPS Server region Started Procedure name (STC) will have a suffix 'S' added Step (8.10) and step (11) use it.


<WPS_GROU P>: Racf Group name for WPS . EX: WSPORTS


Need to match with Step (6) RACF definition.



Goto Syslog, issue /D LOGGER,L . The logstream name should exist already.


<WS_PATH>: Installation path for WebSphere AS


Need to match your WebSphere AS installation path.


<JAVA_PATH> : It's should be /usr/lpp/java/IB M/J1.3

Validate the path

If does not exist, step(12) will have /usr/lpp/java/ not found error

5. Set up WLM



Goto SDSF syslog and issue command: /D WLM,APPLENV =<Your_Applenv _name>

Note that the Server region Procedure name is the Control region name plus "S". Ex: WSPORTS


WPS Server region procedure name must match with what WLM defines.

<Your_Applev_Name>: The WLM WPS Applenv name you selected.

6. Set up RACF

Verify all the related userids and groupids

<WPS_GROU P>, <WPS_SRVR EGIONID>, WPS_CTLRE GIONID>, <WPS_PROC NAME> and some your existing WebSphere RACF group names are used here too.

Server region procedure name should match with step(5) WLM setup.

Create a batch job RACF1 in <YourHLQ>.JOBS.CNTL and execute those RACF commands which are in /usr/lpp/PortalServer/PortalS erver/zosinst/jcl/racf.jcl. However, make sure all the commands are executed successfully. The batch job always returns rc=0.


The ADDUSER WSPORTSU line of the installation document has a typo error and will cause RACF syntax error on this line. Just delete the rest of the line starting from PW USER(WSPO RTCU) and replace it with NOPASSWOR D.


No need to redo this step unless you have changed RACF variables in wps.setup.in file.

7. Configure LDAP Server

Start the WebSphere Customization Dialog



This is a very critical step as it could overwrite your WebSphere Application Server customization datasets and saved CFG files.


Issue the following command: exec '<BBO_Hlq>.SB BOCLIB(BBOW STRT)'



Choose option 1. New Customization.



Load the saved customization variables for WebSphere Application Server.


The WPS LDAP customization need to be added to the existing WebSphere Application Server definitions.


Allocate a new set of target datasets. <YourHLQ>.CN TL and <YourHLQ>.DAT A. Enter all the selected LDAP variables.

<WPS_LDAP_ PORT>,EX: 2345, Enter the new LDAP Procedure name. EX: BBOLDAT


This will generate all the required JCLs and files in <YourHLQ>.CNTL and <YourHLQ>.DATA, which include those LDAP jobs BBOTDBMC, BBOLDGRT, and BBOLDAP.


Generate the customization jobs.


Will create two new <YourHLQ>.CN TL and <YourHLQ>.DAT A datasets.

Make a backup of those three newly created datasets. This will help you troubleshooting your installation problem after it's modified later.


Save the customization variables to a new dataset. EX: TEST.PORTAL. WPS4.SAVECF G


Do not overwrite your existing WebSphere Application Server saved SAVECFG PDS.

Document those three PDS datasets names.


Create the LDAP Procedure and copy them to SYS1.PROCLIC LIB.



Create BBOPOLDF in <YourHLQ>.DAT A Copy this file from <WPS_PATH>/z osinst/jcl and modify it. Change all dc=test,dc=com to your selected LDAP suffix. EX: "dc=ibm,dc=co m". The <WPS_LDAP_I D> variable in the wps.setup.in file should have the same suffix.


This file will be copied to /tmp as /tmp/portal.ldif in step (7.11 and 7.15) by BBOWMCPT job. This is an ldif file format, be careful with the spaces. EX: one space is required after the":" for each definition. One space is required for the next line in column 1 if the line continues. You should get familiar with some of the basics of LDAP such as ldif file format and how to prime the LDAP server, especially If you are running into problems at this step.


Change <YourHLQ>.DAT A(BBOWTMCP) . In the first line, insert the "portal" after the bboslapd.config. Also insert the fifth line as shown in the Portal installation readme file.

<WS_CONFI G_PATH>: EX: /WebSphere3 90/CB390

Review your input typing and validate the <WS_CONFIG_ PATH>/ <YourSysplexID >/etc/ldap directory is exist.

This data file is set up for step (7.15) job BBOWMCPT to copy those five files listed on the left to the directory indicated on the right. You should make a backup of this directory (that is, <WS_CONFIG_PATH>/<You rSysplexID>/etc/ldap) and be very careful of not to caused it to overwrite the current bboslapd.conf files. They are used by your other LDAP servers.


Change <YourHLQ>.DAT A(BBOLTDBM). Note that there are five lines. Validate the " -f /tmp/portal.ldif" is part of the data required by the ldapmodify command. It's on the same line.


Member BBOLTDBM is used by step BBOMTDBM job to prime the LDAP TDBM database. The ldapmodify command is located in /usr/lpp/ldap/bin. It's used to prime those three listed ldif files to the new LDAP Server TDBM database. The fifth line has an "-a -h" instead of "-h" as the other lines. This means the ldapmodify command will add those entries in "/tmp/portal.ldif" to the LDAP TDBM.


Change <YourHLQ>.DAT A(BBOWSLPT). Make a backup of this file and change the securePort from 636 to a new one.


You can pick any number


Remove the bottom sections of suffix and add "suffix "dc=<YOURDO MAIN>, dc=<YOURDOM AINSUFFIX>" to the bottom line.

Those suffix dc=<YOURDO MAIN> and dc=<YOURDO MAINSUFFIX > should match the suffix that you have selected in <WPS_LDAP_ ID>. Also it is the same suffix as in step 7.19 and all the three ldif files listed in BBOWTMCP and later copied to /tmp as schema.user.l dif, schema.IBM.l dif and portal.ldif.


This suffix "dc=<YOURDOMAIN>, dc=<YOURDOMAINSUFFIX >" should match with the suffix specification in all the the three ldif files, /tmp/schema.user.ldif, /tmp/schema.IBM.ldif and portal.ldif used in step (7.15) BBOMTDBM job. This file will be copied to "<WPS_CONFIG_PATH>/Yo urSysplexID>/etc/ldap/<sysi d>.bboslapd.conf.protal". It will be used as the //CONFIG DD reference file in LDAP Server STC (EX: BBOLDAT).


Although it's not documented in the installation readme file, you should review and may need to modify those two members BBOWULDF and BBOWILDF its first line "dn: cn=schema, o=WASNaming, c=US" to match the suffix that you insert in step (7.12). Otherwise the schema.user.ldif and schema.IBM.ldif will not be primed. EX: "dc: cn=schema,dc=i bm,dc=com". No spaces between the ",".

Those suffix dc=<YOURDO MAIN> and dc=<YOURDO MAINSUFFIX > should match the suffix that you have selected in <WPS_LDAP_ ID>.

Portal server currently only support two level index of the suffix. Errors could happen If you choose more than two level index.suffix.

If you have more than two levels of index in your Domain name, convert them to two level. EX: "uni.eng.man.edu", use "dc=uni.eng.man,dc=edu"


Run this second set of RACF commands. This RACF job sets up the necessary permissions for the new LDAP Server Procedure BBOLDAT.


Create this RACF2 job and save it in <YourHLQ>.JOBS.CNTL lib.


BBOLDTBD is only required if you want to delete the LDAP TDBM database due to problems.


Need DB2SYSADM Authority and WPS LDAP Server should be down.


Create LDAP Server TDBM database


Need DB2SYSADM Authority and WPS LDAP Server should be down.


Grant access to the LDAP database


Need DB2SYSADM Authority


Copy bboslapd.conf.p ortal to <WS_CONFIG_ PATH>/SysplexI D/etc/ldap. Copy all the three ldif files to /tmp directory.


Review the directory and its current LDAP conf files. Refer to step (7.10)

This is a very critical step as it could overwrite your exist LDAP Server configuration files.

Make backup of this directory before running this job.




Check joblog for message GLD0122I Slad is ready for requests.



This job primes the LDAP database with the ldapmodify commands. Refer to step (7.11)


Look for the sysout messages of "adding new entry dc=<YOURDOM AIN>, dc=<YOURDOM AINSUFFIX>. EX: adding new entry cn=users,dc=tes t,dc=com. All the new entries in portal.ldif should be added here and should be validated.

Use USER=CBADMIN All the new entries specified in portal.ldif should be added here. If not or job return code NE 0, then go back to step (7.9 to 7-12). You can also try to manually execute the ldapmodify commands under USS as listed in <YourHLQ>.DATA(BBOLTDB M) file. Make sure the LDAP Server is primed correctly before you continue.


It executes the /tmp/schema.us er.ldif first, then /tmp/schema.IB M.ldif next and /tmp/portal.ldif last. The schema.user.ldif need to be primed first.


You can use ldap browser (that is, DMT tool) to connect this LDAP Server and verify if all the portal.ldif entries are added.

8. Create the DB2 database for the Portal Server


This step starts the Portal Server configuration.


Create database for Portal Server. For DB2 V7.1, the plan name is "DSNTIA71".

Add LIB(<DB2HLQ>. RUNLIB.LOAD) for locating this plan.

Replace #DB2PRFX#, the DB2 HLQ, #DB2SUB#, the DB2 Subsystem name, #PLAN# the DB2 plan name, #WPS# the WPS HFS location, #YOURHLQ# the <YourHLQ>.J OBS.CNTL. Do this for the four jobs.


You may need to add the UNIT=VIO to your sysprint DD for the first job step of the job.


Initialize DB2 fields

See above



Create fields and perform DB2 grant.

See above



Drop database. Only needed if this step need to be rerun.

See above


Resolve all the problems before continue. #WPS_SRVREGIONID# should be the same as specified in wps.setup.in (step 4).

Create WSPORT and WSPORTS Procedures

Create both procedures and copy them to SYS1.PROCLIB

Control Region Server name <WPS_PROC NAME> and Server region name in WLM.


Review all the Portal Server related RACF definitions.

9. Configure WPS on WebSphere Application Server

Oget all the 5 jcl's from <WPS_PATH>/z osinst/jcl to <YourHLQ>.JO BS.CNTL


Portal Server WSPORT should be down.


Replace the following variables for all five files: <BBOLIB>, #WPS#, HFS location of the WPS and #INPUTFILE#.


If you have moved the wps.setup.in to a new location, then #INPUTFILE# is the new location of the wps.setup.in file. Delete it if you choose the default location



Replace variables and submit the job


Review joblog

Uid=0 required.

If job fails, fix the problem and rerun the job. All the shell scripts are located in <WPS_PATH>/zosinst/script s directory. Review those scripts and compare it with the error messages of the job output.


WebSphere Application Server need to be up. Replace variables and submit the job.


Review Joblog


Use TIME=1440

This job also need more time to run.


Replace variables and submit the job.


Review joblog

Use UID=0

The shell script wpspost.root.in uses grep cmd to locate both 'wpsPre.root.sh finished successfully' and wpsAdmin.root.sh finished successfully' messages from the <WPS_PATH>/Install.log before continue.

11. Start WebSphere Portal




Point your browser to: http//<WPS_HO ST>:<WPS_PO RT>/wps/<WPS _PUBLIC_HOM E>. EX: http://here.there. everywhere:808 2/wps/portal


You will see a page with a message stating that your portal contains no page groups yet. Logon to WebSphere Portal as the user wpsadmin and verify that the login was successful.

This complete the Portal Server Configuration.

12. Deploy the base portlets


WPS should be running.


Replace variables and #JOBCOUNT#. Submit the job.


WebSphere Portal Server should be up.

Use UID=0

Resolve all problems before continue.


Replace variables and #JOBCOUNT#. submit the job.


Use UID=0

Resolve all problems before continue.

WebSphere Portal Server should be down.


Restart the Portal Server


Point your browser to: http//<WPS_HO ST>:<WPS_PO RT>/wps/<WPS _PUBLIC_HOM E>. EX: http://here.there. everywhere:808 2/wps/Portal


You should see the complete Portal Welcome page.

If fails, determine which steps may have had problem and restart from that step. Restart from step (4), (7), (8) or (9) accordingly.


After any changes, should you need to delete a conversation you can use the <yourHLQ>.jobs.cntl(wpsunions). This job runs the shell script WPUninstall to create a new conversation under SMEUI, deletes Portal and its datasource, and then commits the conversation. See step two of Uninstalling PTF2 in the README file for further information.

 < Day Day Up > 

Websphere Portal on Z. OS
Websphere Portal on Z/OS
ISBN: 0738499382
EAN: 2147483647
Year: 2003
Pages: 90

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net