Chapter 5. Installation and administration of WebSphere Host Publisher Server
5.2 Installing and uninstalling Host Publisher Server
5.2.2 Installing Host Publisher Server
Host Publisher Server is installed on the iSeries server. This section guides you through the required steps:
1. Preparing to install Host Publisher Server
2. Installing the Host Publisher Server program code 3. Starting the Web application server
4. Testing the installation of Host Publisher Server
During installation, the installation and configuration programs
install
and cfgHPsvr perform the following actions on your system:Install the Host Publisher Server program and documentation files.
Update the WebSphere configuration to include:
– A Host Publisher Application Server (Advanced Edition only) – The Host Publisher Administration application (HPAdmin.ear) – The Host Publisher Documentation application (HPDoc.ear) – The Host Publisher XML Gateway application (xmlLegacyGW.ear)
Modify the WebSphere configuration to define the Host Publisher Server Administration servlet and enable WebSphere to access your Host Publisher documents. Host Publisher is configured in the
WebSphere Administrative Server
of WebSphere Application Server you select.Uninstalling the previous version of Host Publisher
If a previous version of Host Publisher Server is installed on the iSeries server, you must uninstall it. Follow these steps to uninstall a previous version:
1. Sign on to the server using a profile that has *SECOFR authority.
2. Perform the following steps to ensure WebSphere Application Server is active: a. Run the following command:
WRKACTJOB SBS(QEJBSBS)
Note: Earlier versions of Host Publisher run with WebSphere Application Server
b. If the subsystem is not running, run the following command: STRSBS QEJB/QEJBSBS
c. Select option 5 for the QEJBADMIN job.
d. Select option 10 to view the job log, and verify that the WebSphere administrative server QEJBADMIN is readymessage is displayed.
3. Uninstall Host Publisher Server by running one of the following commands: – For Host Publisher V2.2.1:
DLTLICPGM LICPGM(5648D31) – For Host Publisher V3.5: DLTLICPGM LICPGM(5648E25)
4. Refresh the view of application servers in the WebSphere Administrative Console, and verify that the HostPubServer application server was deleted.
After you delete Host Publisher Server, your Host Publisher applications remain on the system. After you install Host Publisher Version 4.0, existing applications must be migrated to function with the new version of the product. The migration steps are outlined in 5.4,
“Migrating applications and XML Gateway sessions” on page 136.
Preparing to install Host Publisher Server
Host Publisher Server can be installed with WebSphere Host Publisher Server Advanced Edition 4.0 or with WebSphere Host Publishing Server Advanced Single Server Edition 4.0. The preparation depends on the version you use.
You must verify whether the required software is installed and WebSphere Application Server is up and running:
For installation with WebSphere Application Server Advanced Edition V4.0: a. Sign on to the server using a profile that has *SECOFR authority.
b. Verify that all the prerequisite software is installed by running the command: GO LICPGM
Select option 10 to display what is installed on the server.
c. Verify if WebSphere Application Server Advanced Edition is active:
i. Run the WRKACTJOB command, and look for the QEJBADV4 subsystem. See Figure 5-2.
Figure 5-2 Verifying if WebSphere Application Server Advanced Edition is active
ii. If the subsystem is not running, run the CL command: STRSBS QEJBADV4/QEJBADV4
iii. Select option 5 on the QEJBADMIN job or the ADMIN job listed for your administrative instance. If the ADMIN job is not listed, refer to the WebSphere documentation for starting administrative instances.
iv. Select option 10 and verify that the WebSphere administrative server QEJBADMIN is readymessage is displayed. Figure 5-3 shows an example of this message. Work with Active Jobs SYSTEMNAME 04/30/02 13:21:18 CPU %: .0 Elapsed time: 00:00:00 Active jobs: 367 Type options, press Enter. 2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message 8=Work with spooled files 13=Disconnect ... Opt Subsystem/Job User Type CPU % Function Status QBATCH QSYS SBS .0 DEQW QCMN QSYS SBS .0 DEQW QCTL QSYS SBS .0 DEQW QSYSSCD QPGMR BCH .0 PGM-QEZSCNEP EVTW QEJBADV4 QSYS SBS .0 DEQW DEFAULT_SE QEJB BCI .0 PGM-QEJBSVR JVAW ISERIESACC QEJB BCI .0 PGM-QEJBSVR JVAW QEJBADMIN QEJB BCI .0 PGM-QEJBADMIN JVAW
QEJBMNTR QEJB ASJ .0 PGM-QEJBMNTR EVTW
More... Parameters or command ===> F3=Exit F5=Refresh F7=Find F10=Restart statistics F11=Display elapsed data F12=Cancel F23=More options F24=More keys
Figure 5-3 QEJBADMIN is running
For installation with WebSphere Application Server Advanced Single Server Edition: a. Sign on to the server using a profile that has *SECOFR authority.
b. Verify that all the prerequisite software is installed by running the command: GO LICPGM
Select option 10 to display what is installed on the server.
c. Verify if WebSphere Application Server Advanced Single Server Edition is active: i. Run the WRKACTJOB command, and look for the QEJBAES4 subsystem. See
Figure 5-4.
Display Job Log System: SYSTEMNAME Job. . : QEJBADMIN User . . : QEJB Number . . . : 003512 Job 003512/QEJB/QEJBADMIN started on 04/05/02 at 09:17:59 in subsystem QEJBADV4 in QEJBADV4. Job entered system on 04/05/02 at 09:17:59. WebSphere server started with JDK 1.3.1. Job 002617/QUSER/QSQSRVR used for SQL server mode processing. Job 002616/QUSER/QSQSRVR used for SQL server mode processing. Job 002656/QUSER/QSQSRVR used for SQL server mode processing. >>>>WebSphere administrative server QEJBADMIN ready. Job 002662/QUSER/QSQSRVR used for SQL server mode processing. Job 002663/QUSER/QSQSRVR used for SQL server mode processing. Job 002661/QUSER/QSQSRVR used for SQL server mode processing. WebSphere application server job 003513/QEJB/ISERIESACC started.
Job 002617/QUSER/QSQSRVR used for SQL server mode processing.
Job 002656/QUSER/QSQSRVR used for SQL server mode processing. More... Press Enter to continue. F3=Exit F5=Refresh F10=Display detailed messages F12=Cancel F16=Job menu F24=More keys
Figure 5-4 Verifying if WebSphere Application Advanced Single Server Edition is active
ii. If the subsystem is not running, run the CL command: STRSBS QEJBAES4/QEJBAES4
iii. Select option 5 on the DEFAULT_SERVER job.
iv. Select option 10, and verify that the WebSphere Application Server Default Server readymessage is displayed (see Figure 5-5).
Figure 5-5 WebSphere Application Server Default server ready
WORK WITH ACTIVE JOBS SYSTEMNAME 05/01/02 22:02:33 CPU %: 1.9 ELAPSED TIME: 04:17:47 ACTIVE JOBS: 231 TYPE OPTIONS, PRESS ENTER. 2=CHANGE 3=HOLD 4=END 5=WORK WITH 6=RELEASE 7=DISPLAY MESSAGE 8=WORK WITH SPOOLED FILES 13=DISCONNECT ... OPT SUBSYSTEM/JOB USER TYPE CPU % FUNCTION STATUS QEJBAES4 QSYS SBS .0 DEQW DEFAULT_SE QEJB BCI .8 PGM-QEJBSVR JVAW QHTTPSVR QSYS SBS .0 DEQW ADMIN QTMHHTTP BCH .0 PGM-QZHBHTTP SIGW ADMIN QTMHHTTP BCI .0 PGM-QZSRLOG SIGW ADMIN QTMHHTTP BCI .0 PGM-QZSRHTTP SIGW ADMIN QTMHHTTP BCI .0 PGM-QYUNLANG TIMW APACHE4AE QTMHHTTP BCH .0 PGM-QZHBHTTP SIGW APACHE4AE QTMHHTTP BCI .0 PGM-QZSRLOG SIGW MORE... PARAMETERS OR COMMAND ===> F3=EXIT F5=REFRESH F7=FIND F10=RESTART STATISTICS F11=DISPLAY ELAPSED DATA F12=CANCEL F23=MORE OPTIONS F24=MORE KEYS
DISPLAY JOB LOG SYSTEM:SYSTEMNAME JOB. . : DEFAULT_SE USER . . : QEJB NUMBER . . . : 015121 JOB 015121/QEJB/DEFAULT_SE STARTED ON 05/01/02 AT 16:38:37 IN SUBSYSTEM QEJBAES4 IN QEJBAES4. JOB ENTERED SYSTEM ON 05/01/02 AT 16:38:37. SERVER STARTING WITH USER PROFILE QEJBSVR. WEBSPHERE SERVER STARTED WITH JDK 1.3.1. JOB 014912/QUSER/QSQSRVR USED FOR SQL SERVER MODE PROCESSING. JOB 014915/QUSER/QSQSRVR USED FOR SQL SERVER MODE PROCESSING. >>> WEBSPHERE APPLICATION SERVER Default Server READY. BOTTOM PRESS ENTER TO CONTINUE. F3=EXIT F5=REFRESH F10=DISPLAY DETAILED MESSAGES F12=CANCEL F16=JOB MENU F24=MORE KEYS
Installing the Host Publisher Server program code
These steps walk you through the installation:
1. Insert the Host Publisher Server CD-ROM into the CD driver on the server. 2. Run the qsh command.
3. In the QSH Command Entry session, follow these steps: a. Run the following command:
cd /QOPT/HP40
This takes you to the directory from which to run the install command (see Figure 5-6).
Figure 5-6 Command cd /qopt/hp40
b. Run the install command: install [-silent ]
Here the optional parameter -silent performs a silent installation.
Messages are logged to the file QIBM/ProdData/HostPublisher/Install/HPInstall.log. 4. When the install command completes, review the displayed messages (see Figure 5-7)
and follow any instructions that are displayed.
Note: This step is identical for WebSphere Application Server Advanced Edition
and Advanced Single Server Edition.
QSH Command Entry ===> cd /qopt/hp40 F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry
Figure 5-7 Completion of the install command
5. Verify the installation log, which is in QIBM/ProdData/HostPublisher/Install/HPInstall.log. Use the WRKLNK CL command to retrieve the log and DSPF command to display the log: WRKLNK OBJ('/QIBM/ProdData/HostPublisher/install/HPInstall.log')
DSPF STMF(‘/QIBM/ProdData/HostPublisher/install/HPInstall.log’)
See Figure 5-8 for the WRKLNK display. For more details on the HPInstall.log, see Example 8-1 on page 268.
Figure 5-8 Verifying the install log by selecting option 5 (Display)
QSH Command Entry $ > install Installing Host Publisher Server. Please wait. Copying stream file to save file. Restoring licensed program. Installation completed successfully. $ ===> F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry
Work with Object Links Directory. . . . : /QIBM/ProdData/HostPublisher/install Type options, press Enter. 2=Edit 3=Copy 4=Remove 5=Display 7=Rename 8=Display attributes 11=Change current directory ... Opt Object link Type Attribute Text 5 HPInstall.log STMF Bottom Parameters or command ===> F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel F17=Position to F22=Display entire field F23=More options
6. Run the cfgHPsvr command:
a. Run the QSH command, if you don’t have a QSH command entry screen. b. Change to the QIBM directory:
cd QIBM
c. Go to the ProdData directory: cd ProdData
d. Go to the HostPublisher directory: cd Hostpublisher
e. Enter the cfgHPsvr command. The format of the command is:
cfgHPsvr [-instance instance][-configFile AEs_config_file ][-was WAS_edition ][-iwa ][-silent ]
Note the following explanation:
• -instance instance: Specifies the name of the WebSphere Application Server administrative instance in which Host Publisher is to be configured. The default value is default.
• -configFile AEs_config_file(WebSphere Advanced Single Server Edition only): Specifies the name of the server-cfg.xml file. The default is the active configuration file in WebSphere Application Server, found in the admin.configFile property in /QIBM/UserData/WebASAEs4/instance/properties/admin.properties.
• -was WAS_edition: Specifies the edition of WebSphere Application Server in which Host Publisher is to be configured. This parameter is necessary only if both editions of WebSphere Application Server are installed on the iSeries server. Possible values for WAS_edition are:
• ADV4: WebSphere Advanced Edition Version 4.0 • AES4: WebSphere Advanced Single Server Edition 4.0 The default is ADV4, if installed.
• -iwa: Configures WebSphere Host Publisher for integration with iSeries Access for
Web. This option makes iSeries Access for Web handle the licensing for the WebSphere Host Publisher users.
• -silent: Runs cfgHPsvr silently.
In this example, cfgHPsvr is set up for use together with iSeries Access for Web, on the default server, which is WebSphere Application Server Advanced Edition:
cfgHPsvr -instance default -was ADV4 -iwa See Figure 5-9.
Figure 5-9 The cfgHPsvr command
7. When the cfgHPsvr command completes, review the displayed messages and follow the instructions that are displayed (Figure 5-10). Additional messages are logged into the install log file in /QIBM/ProdData/HostPublisher/Install/HPInstall.log. An extract of the log information is shown in Example 8-2 on page 269.
Figure 5-10 Completion of cfgHPsvr QSH Command Entry $ > cd qibm $ > cd proddata $ > cd hostpublisher $ ===> cfgHPsvr -instance default -was ADV4 -iwa F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry
QSH Command Entry $ > cd qibm $ > cd proddata $ > cd hostpublisher $ > cfgHPsvr -instance default -was ADV4 -iwa Host Publisher will be configured with WebSphere Application Server Advanced Edition Host Publisher will be configured with iSeries Access for Web
Configuration completed successfully. $ ===> F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry
8. If you use cfgHPsvr for WebSphere Application Server, Advanced Single Server Edition, the command can be:
cfgHPsvr -instance default -configfile
/QIBM//UserData/WebASAEs4/default/config/server-cfg.xml -was AES4 -iwa
Figure 5-11 shows the completion of the cfgHPsvr command for WebSphere Application Server Advanced Single Server Edition.
Figure 5-11 cfgHPsvr for AES4 completion
9. Press F3 to exit the QSH command entry session. 10.After the installation, you can see:
– The files are added into /QIBM/ProdData/HostPublisher (Figure 5-12) and into /QIBM/Userdata/HostPublisher (Figure 5-13).
QSH COMMAND ENTRY $ > cfghpsvr -instance default -configfile
/QIBM/UserData/WebASAEs4/default/config/server-cfg.xml -was AES4 -iwa Host Publisher will be configured with WebSphere Application Server Advanced Single Server Edition
Host Publisher will be configured with iSeries Access for Web Configuration completed successfully. $ ===> F3=EXIT F6=PRINT F9=RETRIEVE F12=DISCONNECT F13=CLEAR F17=TOP F18=BOTTOM F21=CL COMMAND ENTRY
Figure 5-12 Host Publisher files installed in QIBM/ProdData/HostPublisher
For both versions of WebSphere Application Server, you have identical files in QIBM/ProdData/HostPublisher and QIBM/UserData/HostPublisher.
– WebSphere Application Server Administrative Console information
You can see the
HostPubServ
as application server andHPAdmin, HPDoc,
andxmlGateway
as enterprise applications in the WebSphere Administrative Server. Figure 5-14 shows a view of the administrative console of the WebSphere Application Server, Advanced Edition.Figure 5-14 WebSphere Application Server console
Figure 5-15 shows the administrative console of the WebSphere Application Server Single Server Edition after installation.
Figure 5-15 WebSphere Application Server Advanced Single Server Edition after installation
To use the WebSphere Advanced administrative console, refer to the WebSphere installation and setup information documentation in the WebSphere for iSeries Documentation Center at:
http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/docs/doc.htm
Navigate to the installation and initial configuration sections for the version you use.
Starting Web application servers
You must restart the WebSphere Application Server after you install the Host Publisher Server:
If Host Publisher was configured for WebSphere Application Server Advanced Edition, start the HostPubServer application server:
a. Using the WebSphere Advanced Administrative Console, select the application server named HostPubServer (see Figure 5-14).
b. Click Start.
c. Check the Console Messages area to verify that the start command completed successfully.
If Host Publisher was configured for WebSphere Advanced Server, Single Server Edition, restart WebSphere:
a. Run the following command to stop the WebSphere Application Server: ENDSBS QEJBAES4/QEJBAES4
b. Run the following command to restart WebSphere: STRSBS QEJBAES4/QEJBAES4
c. Run the following command: WRKACTJOB SBS(QEJBAES4)
d. Select option 5 for the DEFAULT_SE job.
e. Select option 10 and verify that the Ready message is displayed.
f. If Host Publisher was configured for a WebSphere administrative server other than the default, start that administrative server now:
i. Select option 5 for your instance’s job.
ii. Select option 10 and verify that the Ready message is displayed.
Testing the installation of Host Publisher Server
After you install Host Publisher Version 4.0, you must test the installation. In your browser, load:
Host Publisher Server Administration: http://server/HPAdmin/main.jsp
Here server is the server name. The Host Publisher Server Administration page is shown in Figure 5-16.
Figure 5-16 Host Publisher Server Administration
ShowCfg configuration parameters: http://hostname/HPAdmin/showCfg
Troubleshooting
If either Host Publisher Server Administration or ShowCfg fails to load, check the Host Publisher Server configuration of WebSphere Application Server as explained in the following sections.
Testing with WebSphere Advanced Edition
To test the installation with WebSphere Advanced Edition, perform the following steps: 1. Confirm that HostPubServer application server is active:
a. Using the tree view in the WebSphere Administrative Console, expand WebSphere
Administrative Domain-> Nodes-> your node name. b. Select Application Servers.
c. Click Refresh. HostPubServer should be listed in the details view, with a status of Running.
2. If HostPubServer is inactive, perform the following steps to activate it:
a. Using the tree view in WebSphere Administrative Console, expand Application
Servers.
b. Select the application server named HostPubServer. c. Click Start, or select Console-> Start.
d. Check the Console Messages area to verify that the start command completed successfully.
3. Confirm that HPDoc, HPAdmin, and xmlGateway appear as installed Enterprise Applications in the WebSphere Application Server topology:
a. Using the tree view in the WebSphere Administrative Console, expand WebSphere
Administrative Domain.
b. Select Enterprise Applications.
c. Click Refresh. HPDoc, HPAdmin, and xmlGateway should display in the details view. 4. If WebSphere is not configured properly for Host Publisher, run the Host Publisher deploy
command:
a. Confirm that the WebSphere administrative server job is started and ready: i. Run the following server command:
WRKACTJOB SBS(QEJBADV4)
ii. If the subsystem is not running, run the following server command: STRSBS QEJBADV4/QEJBADV4
iii. Select option 5 on the QEJBADMIN job or the ADMIN job listed for your administrative server. If the ADMIN job is not listed, refer to the WebSphere for iSeries Documentation Center for starting administrative servers.
iv. Select option 10 and verify that the Ready message is displayed. b. Run the QSH command.
c. In the QSH command entry session, run the command: cd /QIBM/ProdData/HostPublisher
AEOS400Deploy
Figure 5-17 AEOS400deploy
d. Check for error messages in the /QIBM/UserData/HostPublisher/log/AEdeploy.log deploy log file as shown in Figure 5-18.
Figure 5-18 AEdeploy log
e. Press F3 to exit the QSH command entry session.
Testing with WebSphere Advanced Single Server Edition
To test the installation with WebSphere Advanced Single Server Edition, follow these steps: 1. Confirm that WebSphere is running by entering the following command:
WRKACTJOB SBS(QEJBAES4)
2. If WebSphere is not running, follow these steps: a. Run the following command to restart WebSphere:
STRSBS QEJBAES4/QEJBAES4 b. Run the following command:
WRKACTJOB SBS(QEJBAES4)
c. Select option 5 for the DEFAULT_SE job.
QSH Command Entry $ > cd /qibm/ProdData/HostPublisher $ > AEOS400Deploy Check /QIBM/UserData/HostPublisher/log/AEdeploy.log for the results of the
deployment. $ ===> F3=Exit F6=Print F9=Retrieve F12=Disconnect F13=Clear F17=Top F18=Bottom F21=CL command entry
d. Select option 10 and verify that the Ready message is displayed.
e. If Host Publisher was configured for a WebSphere administrative server other than the default, start that administrative server now.
f. Select option 5 for your server’s job.
g. Select option 10 and verify that the Ready message is displayed.
3. Confirm that HPDoc, HPAdmin, and xmlGateway display as installed Enterprise
Applications in the WebSphere Application Server topology for the server configuration file