Chapter 6. Portlet development and deployment 195
To deploy portlets in WebSphere Portal on z/OS and OS/390 platform, you
perform the following steps.
1. Administrative tasks on WebSphere Portal using the administration portlets
for installing portlets. These require a user with portal administrative rights to
login via a browser from the portal home page. This portlet deployment step
generates job files in the z/OS Portal HFS directory structure for further
administration steps to be done to WebSphere Application Server. Changes
to the portal configuration are effective immediately but the portlets are not
operational until the second step is performed.
2. Administrative tasks on WebSphere Application Server, where you install,
update or delete portlets by running script WPAConfig and the jobs created in
Step 1. The WPAConfig script searches for the jobs and executes them one
by one in the sequence of their generation. After this step the portlets are
operational on WebSphere Portal server.
6.3.1 Portlet deployment jobs
When the administration portlets in WebSphere Portal server are used to install,
delete, or update a portlet they generate portlet deployment job files on the HFS
file system on z/OS. These files contain descriptions of further administrative
steps to be done in WebSphere Application Server. There is one file for each
configuration step, which is referred to as a job. Usually this file is accompanied
by further resources, such as a file containing the portlet binaries. The job
descriptions in the job files consist of name-value pairs that are recognized by
the WPAConfig script. The generated job files only support application type or
apptype of war.
Note: This is different from portlet deployment on a distributed platform
which does not have the second step.
Tip: If the Portal Server is running during Step 2 when executing script
WPAConfig, it is stopped and restarted for each of the portlet deployment jobs it
finds. Therefore, if you are deploying a large number of portlets from within a
WAR file, we recommend you stop the Portal Server first, execute WPAConfig
using one of the methods described later in this chapter, and then restart the
Note: Although the ear apptype is recognized by WPAConfig script, it is
officially not supported.