About this task
WebSphere Application Server for z/OS uses
"application serving environments" to provide its functions. Configuring
these application serving environments after product installation
requires a fair amount of planning and coordination. If you have not
previously configured WebSphere Application Server
for z/OS, you should configure a "practice" standalone
application server using the default options then proceed to configure
the actual product configuration that you want.
Note: The configuration
files associated with a WebSphere Application Server
runtime environment are called profiles. On platforms other
than z/OS, profiles can be created, copied, and manipulated using
the manageprofiles command. In WebSphere Application
Server for z/OS, however, all profiles are created using
the Profile Management Tool (z/OS only) or the zpmt command.
With WebSphere Application Server for z/OS, you do not normally need
to invoke the manageprofiles command or use the
-profile option on other administrative commands. In fact, creating
a profile by running manageprofiles.sh directly
is not supported on z/OS.
Notes on changes in Version 8:
- When you use the WebSphere Customization
Toolbox or zpmt.sh command to configure an application
server or a management server, note the following changes:
- The name of the BBOxCPY1 job was changed to
BBOxPROC in order to express the function of the
customization job more accurately.
- The BBOxPROC job now must be run after the
BBOWWPFx job.
Carefully read and follow the customization instructions generated
by the WebSphere Customization
Toolbox or zpmt.sh command. Do not re-use customization
files or data created from a version earlier version of WebSphere Application Server for z/OS.
- In previous versions of IBM® WebSphere Application Server
for z/OS, certain native (non-UNIX)
files were provided in Multiple Virtual Storage (MVS) partitioned datasets such as SBBOJCL. In WebSphere Application for z/OS Version 8, these files are
distributed in the WebSphere Application
Server for z/OS product file
system. These files must be exported from the WebSphere Application Server for z/OS product file system into MVS partitioned datasets before they
can be used.
Use the copyZOS.sh script to export MVS native files into partitioned
datasets.
If the dataset does not already exist, it is allocated
by the
copyZOS.sh script. The
copyZOS.sh script
resides in the bin directory of the WebSphere Application Server for z/OS product file system (
/usr/lpp/zWebSphere/V8R0/bin).
copyZOS file_type data_set_name
Run
the
copyZOS.sh script without options to see a
list of supported file types and the required output dataset characteristics
for each file type.
Perform the tasks in this section to choose an application
serving environment configuration and plan the necessary details for
configuration.