This example is for users that are not familiar with the Web serving
environment. It describes all the steps necessary to get iSeries™ Access
for Web running in a WebSphere® Application Server - Express for iSeries V5.0
Web serving environment. It also describes how to verify that the setup is
working.
Configuring your Web serving environment consists of these steps:
- Start the IBM® Web
Administration for iSeries interface (also known as IBM HTTP Server
for iSeries).
See step 1.
- Create an HTTP web server and a WebSphere Application Server - Express
for iSeries V5.0
Web application server. See step 2.
- Configure iSeries Access
for Web. See step 3.
- Start the web environment. See step 4.
- Use a browser to access iSeries Access for Web. See step 5.
Steps to configure the Web serving environment:
- Start the IBM Web Administration for iSeries interface.
- Start a 5250 session to the server.
- Sign on with a user profile that has at least these special
authorities: *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM.
- Run the following server command to start the web administration
interface job: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
- Minimize the 5250 session.
- Create an HTTP web server and a WebSphere Application
Server - Express for iSeries V5.0 Web application server:
- Open a browser to: http://<server_name>:2001
- Log in with a user profile that has, at least these special
authorities: *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM.
- Select IBM Web Administration for iSeries.
- Select the Setup tabbed page.
- Under Common Tasks and Wizards, select Create Application
Server.
- The Create Application Server page opens. Select Next.
- Select WebSphere Application Server - Express V5.0 then
select Next.
- The Specify Application Server Name page opens. For Application
server name, specify iwa50exp. This will be the name of
the WebSphere Express
Web application server. Select Next.
- The Select HTTP Server Type page opens. Select Create
a new HTTP server (powered by Apache) then select Next.
- The Create a new HTTP server (powered by Apache) page
opens.
- For HTTP server name, enter IWA50EXP
- For Port, specify 2030.
Select Next.
- The Specify Internal Ports Used by the Application
Server page opens. For First port in range,
change the default value to 21030. Select Next.
- The Select Business and Sample Applications page
opens. Select Next until the Summary page
opens.
- Select Finish.
- The web page is re-displayed with the tabbed page active.
Under Instance/Server, iwa50exp/iwa50exp – WAS - Express,
V5.0 is listed with a status of Creating. From
this Web page, you can manage the WebSphere application server.
Use
the refresh icon next to the Creating status to refresh
the page, if the page does not periodically refresh.
- When the status is updated to Stopped,
select the green icon next to Stopped to start the WebSphere application
server. The status will be updated to Starting. Use
the refresh icon next to the Starting status to refresh
the page if the page does not periodically refresh. iSeries Access
for Web requires that the WebSphere application server is running before
it can be configured.
Important:
Wait for the status
to be updated to
Running before moving to the next
step.
- Configure iSeries Access for Web
- Restore the 5250 session window.
- To see the WebSphere application server running, run the server
command: WRKACTJOB SBS(QASE5)
- Verify that IWA50EXP is listed as a job running under the QASE5
subsystem. iSeries Access
for Web requires the WebSphere application server is running before
it can be configured.
- Verify the Web application server is ready:
- Enter option #5 on your IWA50EXP job.
- Enter option #10 to display the job log.
- Press F10 to display detailed messages.
- Verify the message Websphere application server iwa50exp ready is
listed. This message indicates that the application server is fully
started and is ready for Web serving.
- Press F3 until you return to a command line.
- iSeries Access
for Web provides commands to configure the product. Two different commands
are provided, a CL command and a QShell script command. Both commands
provide and perform the same function. Use whichever version you prefer.
- To use the CL command, follow these steps:
- Configure iSeries Access
for Web for your Web application server by using the following command:
QIWA2/CFGACCWEB2 APPSVRTYPE(*WAS50EXP) WASINST(iwa50exp)
These
are the parameters used: - APPSVRTYPE
- Tells the command which Web application server to configure.
- WASINST
- Tells the command which instance of the Web application server to configure.
For help on this command and the parameters, press F1. Migration Note: If you are already using iSeries Access
for Web within another Web application server, refer to
New
Web application server considerations. This topic discusses additional
CFGACCWEB2 command parameters that can be input to migrate user data from
an existing configuration to this new configuration.
- Several messages similar to these will be displayed:
- Configuring iSeries Access for Web.
- Preparing to perform the configuration changes.
- Calling WebSphere to perform the configuration changes.
- iSeries Access for Web command has completed.
- The WebSphere instance application server must be stopped and
then started to enable the configuration changes.
- Press F3 or Enter when the command completes to exit the display session.
- To use the QShell script command, follow these steps:
- Start the QShell environment using the following server command: QSH
- Make the iSeries Access
for Web directory the current directory. Run this server command:
cd /QIBM/ProdData/Access/Web2/install
- Configure iSeries Access
for Web for the Web application server previously created:
cfgaccweb2 -appsvrtype *WAS50EXP -wasinst iwa50exp
These
are the parameters used: - -appsvrtype
- Tells the command which Web application server to configure.
- -wasinst
- Tells the command which instance of the Web application server to configure.
For help on this command and the parameters, specify the -?
parameter.
- Several messages similar to these will be displayed:
- Configuring iSeries Access for Web.
- Preparing to perform the configuration changes.
- Calling WebSphere to perform the configuration changes.
- iSeries Access for Web command has completed.
- The WebSphere instance application server must be stopped and
then started to enable the configuration changes.
- Press F3 when the command completes to exit the QShell session.
- If the command were to fail or indicate an error, refer to the
log files:
- /QIBM/UserData/Access/Web2/logs/cmds.log
- High level, cause and recovery information; translated.
- /QIBM/UserData/Access/Web2/logs/cmdstrace.log
- Detailed command flow for IBM Software Service; English only.
- After successfully configuring iSeries Access for Web, the WebSphere application
server must be restarted to load the changes to its configuration. This
will be done later.
- Signoff the 5250 session window and close the window.
- Start the web environment
- Return to the browser window that is open to the IBM
Web Administration for iSeries server management page.
- The tabbed page should be active. Under Instance/Server
is listed iwa50exp/iwa50exp – WAS - Express V5 with
a status of Running. Stop and restart the WebSphere application
server:
- Select the red icon next to the Running status
to stop the WebSphere server.
Select the refresh icon next to the Stopping status
to refresh the page if the page does not periodically refresh.
- When the status is updated to Stopped, select the
green icon next to Stopped to start the WebSphere application
server.
- The status will be updated to Starting. Select
the refresh icon next to the Starting status to refresh the page if it does
not periodically refresh.
Important: Wait for the status to be
updated to Running before moving to the next step.
iSeries Access for
Web will load and start as the WebSphere application server starts.
- Select the HTTP Servers tabbed page.
- Under Server, select IWA50EXP - Apache.
The current status of this Apache HTTP server should be Stopped. Select the green icon next to the status to start the HTTP server. The
status is updated to Running.
- Close the browser window.
- Use a browser to access iSeries Access for Web
- Open a browser to either of the following addresses to access iSeries Access
for Web:
http://<server_name>:2030/webaccess/iWAHome
http://<server_name>:2030/webaccess/iWAMain
- Log in using an i5/OS™ user ID and password. The initial
load of iSeries Access
for Web might take a few seconds. WebSphere Application Server is loading Java™ classes
for the first time. Subsequent loads of iSeries Access for Web will be faster.
- The iSeries Access for Web Home or Main page displays.
- Close the browser window.
By following the above steps, you completed these tasks:
- Created a WebSphere Web
application server named iwa50exp.
- Created an HTTP server named IWA50EXP.
- Configured iSeries Access for Web for the WebSphere application
server.
- Stopped and restarted the WebSphere application server and HTTP
web server. iSeries Access for Web started when the WebSphere application
server started.
- Verified that iSeries Access for Web can be accessed from a Web
browser.
In this example, only the CFGACCWEB2 command
is used to configure iSeries Access for Web. For more information about
using all the iSeries Access
for Web CL commands, use the CL command finder.