Smarter Work Management

Better understanding IBM Web Administration for i


IBM Web Administration for i has several definitions depending on who you ask. From a user perspective, the IBM Web Administration for i provides an easy-to-use Web interface for configuring and managing Web technologies found on the IBM i platform. From an IBM i system administrator perspective, IBM Web Administration for i represents a Web application running in an IBM integrated Web application server associated with an IBM HTTP server acting as a front-end Web server. From an IBM i work management perspective, IBM Web Administration for i consists of one subsystem (QHTTPSVR), one job queue (QZHBHTTP), and multiple active jobs responsible for running and managing the various Web related servers defined within the IBM Web Administration for i interface on a system.

This article will focus on IBM Web Administration for i from an IBM i system administrator and work management point of view. A better understanding of the jobs related to IBM Web Administration for i can prove to be very helpful while performing troubleshooting and problem determination of HTTP related servers, the IBM Web Administration for i GUI, IBM Systems Director Navigator or other Web-based administration interfaces on IBM i.

Basic Concepts You Need to Know

You should have a basic understanding of IBM i work management concepts, such as jobs, subsystems and job queues. To learn more about these concepts, reference the IBM i InfoCenter.

The following is a typical lifecycle of a batch job:

  1. When a job is submitted on an IBM i system, a new job with a unique qualified name gets created. This is also the time when the newly created job receives its job attributes (job description, user profile, job queue, library list, request data, etc.) that will be used during job processing.
  2. The job moves to a job queue, where it waits to enter a subsystem that can run it. A job queue can be thought of as a “waiting room” for a subsystem.
  3. When the job enters a subsystem from a job queue, it becomes active.
  4. The subsystem defines which memory pool the job will run in.
  5. The job processing completes and any job related printer files (also called spool files) are placed in an output queue where it waits to be sent to a printer or file.

Now, you’re armed with some basic knowledge of work management on IBM i. Next, let’s explain how it correlates to IBM Web Administration for i.

IBM HTTP Server Jobs

The ADMIN IBM HTTP server is the front-end Web server used to run IBM Web Administration for i. All HTTP related server jobs on IBM i go through job queue QZHBHTTP and get assigned to the QHTTPSVR subsystem once they become active. IBM Web Administration for i's HTTP-related server jobs can be started with the following CL command:


Note that when the ADMIN server instance is started using the STRTCPSVR command, the QHTTPSVR subsystem will be started if it is currently inactive.


Pi Guang Ming is part of the IBM i Web integration development team in China.

Ryan Watkins is a staff software engineer with the IBM Systems and Technology Group. During his career with IBM, he’s been involved in architecture, design and development of systems-management applications on IBM i in the areas of automation, monitoring, security compliance and client/server programming. Ryan can be reached at

Like what you just read? To receive technical tips and articles directly in your inbox twice per month, sign up for the EXTRA e-newsletter here.

comments powered by Disqus



2018 Solutions Edition

A Comprehensive Online Buyer's Guide to Solutions, Services and Education.

Dare to Compare

How integrated Web application server for i compares to WAS

IBM Systems Magazine Subscribe Box Read Now Link Subscribe Now Link iPad App Google Play Store
IBMi News Sign Up Today! Past News Letters