for Use with z/OS V.10
or higher
WebSphere Application Server for
z/OS Version 8.0.0 Version 8 Release 0 Modification 0
for Use with z/OS V.10 or higher
Document Number GI11-9850-01
Printed in USA
|
Note
|
|
Before using this information and the product it supports, be sure to read
the general information under "Notices".
|
A form for reader's comments appears at the back of this publication. When
you send information to IBM, you grant IBM a nonexclusive right to use or
distribute the information in any way it believes appropriate without incurring
any obligation to you.
© Copyright International Business Machines Corporation 2011, 2012. All rights reserved.
Note to U.S. Government Users -- Documentation related to restricted rights --
Use, duplication or disclosure is subject to restrictions set forth in GSA ADP
Schedule contract with IBM Corp.
Introduction
· WebSphere Application
Server for z/OS Description
· WebSphere Application
Server for z/OS V8.0 FMIDs
Program
Materials
· Basic Machine-Readable
Material
· Optional Machine-Readable
Material
· Program Publications
· Basic Program Publications
· Optional Program
Publications
· Program Source Materials
· Publications Useful During
Installation
Program
Support
· Program Services
· Preventive Service Planning
· Statement of Support Procedures
Program
and Service Level Information
· Program Level Information
· Service Level Information
Installation
Requirements and Considerations
· Driving System Requirements
· Machine Requirements
· Programming Requirements
· Target System Requirements
· Machine Requirements
· Programming Requirements
· DASD Storage Requirements
· FMIDs
Deleted
· Special Considerations
Installation
Instructions
· Installing WebSphere Application Server for z/OS V8.0 base
· Sample Jobs for WebSphere Application Server for z/OS V8.0 base
· Create SMP/E zones
(optional)
· Perform SMP/E RECEIVE
· Allocate SMP/E Target and
Distribution Libraries
· Allocate File system Paths
· Create DDDEF Entries
· Perform SMP/E APPLY
· Perform SMP/E ACCEPT
· Mount the WebSphere Application Server for z/OS V8.0 product
repository
· Create a file system for
installing the WebSphere Application Server for z/OS
V8.0 base product
· Install the WebSphere Application Server for z/OS V8.0 base
· Installing WebSphere Application Server for z/OS V8.0 DMZ secure proxy
server
· Create a file system for
installing the WebSphere Application Server for z/OS
V8.0 DMZ secure proxy server product
· Install the WebSphere Application Server for z/OS V8.0 DMZ secure proxy
server code
· Installing WebSphere Application Server for z/OS V8.0 Web server
plug-ins
· Create a file system for
installing the Web server plug-ins product
· Installing the Web server plug-ins
code
· Installing IBM HTTP Server
· Create a file system for
installing the IBM HTTP Server V8.0 product
· Install the IBM HTTP
Server V8.0 code
· Activating WebSphere Application Server for z/OS V8.0
Notices
· Trademarks
Reader's
Comments
--> size=2 width="100%" align=center>
This program directory is intended for system programmers who are
responsible for program installation and maintenance. It contains information
about the material and procedures associated with the installation of WebSphere Application Server for z/OS V8.0. This
publication refers to WebSphere Application Server
for z/OS V8.0 as WebSphere Application Server for
z/OS and highlights WebSphere Application Server for
z/OS as Version 8 when necessary to adequately explain installation procedures.
The Program Directory contains the following sections:
- "Program
Materials" identifies the basic and optional program materials
and documentation for WebSphere Application
Server for z/OS.
- "Program
Support" describes the IBM support available for WebSphere Application Server for z/OS.
- "Program
and Service Level Information" lists the APARs
(program level) and PTFs (service level) that
have been incorporated into WebSphere
Application Server for z/OS.
- "Installation
Requirements and Considerations" identifies the resources and
considerations that are required for installing and using WebSphere Application Server for z/OS.
- "Installation
Instructions" provides detailed installation instructions for WebSphere Application Server for z/OS V8.0. It also
describes the procedures for activating the functions of WebSphere Application Server for z/OS V8.0, or refers
to appropriate publications.
Before installing WebSphere Application Server for
z/OS, read the CBPDO Memo To Users and
the CBPDO Memo To Users Extension that are supplied with this
program in softcopy format and this Program Directory; then keep them for
future reference. Section "Preventive Service Planning" tells you how to find any updates to the
information and procedures in this Program Directory.
WebSphere Application Server for z/OS is supplied
in a Custom-Built Product Delivery Offering (CBPDO, 5751-CS3). The Program
Directory that is provided in softcopy format on the CBPDO tape is identical to
the hardcopy format that is provided with your order. All service and HOLDDATA
for WebSphere Application Server for z/OS V8.0 are
included on the CBPDO tape.
Do not use this program directory if you install WebSphere
Application Server for z/OS with a SystemPac or ServerPac. When you use these offerings, use the jobs and
documentation supplied with the offering. This documentation may point you to
specific sections of this Program Directory as required.
WebSphere Application Server
for z/OS
WebSphere Application Server for z/OS is a proven,
high-performance transaction engine that can help you build, run, integrate,
and manage dynamic business applications.
This product excels as the foundation for a service-oriented architecture
with the following main benefits:
- Broad programming model and
standards support
WebSphere Application
Server for z/OS supports the following for leading open standards and
programming models:
- Java Enterprise
Edition standards support
Use continued programming model productivity and
ease-of-use enhancements through support for portions of key Java Platform,
Enterprise Edition (Java EE) 6.0, including the following:
- Support for key
elements in the Enterprise JavaBeans (EJB) 3.1 specification.
- Support for Contexts and
Dependency Injection (CDI) for the Java EE platform (JSR 299). CDI
provides a programming model suitable for rapid development of
applications without sacrificing the full power of the Java EE 5
platform.
- Support for key
elements of the Java Connector Architecture (JCA) Version 1.6
specification.
- Apache OpenJPA 2.0 implementation of the Java Persistence
API (JPA) with IBM® enhancements.
Enhancements include the Type-safe Criteria API
and associated Metamodel API, object relational
mapping enhancements with associated JPQL updates, and runtime enhancements,
such as pessimistic lock manager, second level (L2) cache, and performance.
- Dynamic cache JPA L2
cache provider for OpenJPA 2.0
- Support for key
elements of Web Application Technologies.
- Support for the
JAX-WS Version 2.2 specification.
- Support for the JAXB
Version 2.2 specification
- Simplified
development of server-side REST applications using Java API for RESTful Web Services (JAX-RS)
- Support for RESTful views of EJB applications that declare a
local business interface and no-interface view enterprise beans using
JAX-RS.
- Support for using
Java Contexts and Dependency Injection (JCDI) with JAX-RS.
You can use JAX-RS root resources and providers in
a JCDI-enabled web application archive. As part of Java Platform, Enterprise
Edition (Java EE) 6, you can take advantage of the JCDI feature to make
applications easier to develop while increasing maintainability.
- Support for using Web
Application Description Language (WADL) documents that describe the
services available to users.
You can develop clients to dynamically understand RESTful services by inspecting the WADL document
- Support for JSR 196 -
Java Authentication SPI for Containers (JASPI) specification, which
enables third-party security providers to handle the Java Platform,
Enterprise Edition (Java EE) authentication of HTTP request and response
messages destined for web applications.
- Support for java:global, java:app, and java:module
Java Naming and Directory Interface (JNDI) names in applications that
are deployed on stand-alone servers or managed servers where the entire
application is deployed on one server.
- OSGi
applications programming model
The OSGi applications
programming model helps you develop and deploy modular applications that use
both Java EE and OSGi technologies. You can design
and build applications and suites of applications from coherent, multiversion, reusable OSGi
modules that are accessed only through well-defined interfaces. This reduces
complexity, and provides the greatest flexibility to maintain and evolve an
application after its first release. The OSGi
applications support includes the following major features:
- Use the OSGi Enterprise Specification 4.2 Blueprint
Container for declarative assembly of components.
This support simplifies unit test outside of the
application server.
- Use extensions to the
Blueprint component model for declarative transactions and
container-managed Java Persistence API (JPA).
- Develop OSGi application projects using IBM Rational®
Application Developer, which enforces OSGi
visibility rules so that projects can only access packages from other
projects that explicitly declare them as part of the project externals.
This provides environmental support to development
best practices.
- Compose isolated
enterprise applications using multiple, multiversion
bundles that have a dynamic life cycle.
- Deploy an application
archive file that need not contain all the resources required by the
application, but can contain just the application-specific content plus
metadata that points to shared libraries (bundles).
This means that application archive files can be
smaller. It also means that, when a library is shared by several OSGi applications, only one copy of the library is loaded
into memory.
- Use an integrated
bundle repository, and configure the locations of external repositories,
to support the provisioning of bundles to applications.
- Deploy existing web
application archives (WAR files) as web application bundles (WAB).
This allows web applications to use the OSGi module system.
- Simultaneously load
multiple versions of classes in the same application, using standard OSGi mechanisms
- Administratively
update deployed applications in a modular way, at the bundle level.
- Support for
applications that use their own versions of common utility classes,
distinct from the versions that are used by the server runtime
environment. Do this without needing to configure application Java EE
application class loader policies, such as PARENT_LAST mode.
- Use federated lookup
mechanisms between the local Java Naming and Directory Interface (JNDI)
and the OSGi service registry.
- XML programming model
Use the XML support provided with this product to
work with web applications that process data using standard XML technologies
like Extensible Stylesheet Language Transformations
(XSLT), XML Path Language (XPath), and XML Query
Language (XQuery).
- Service Component
Architecture (SCA) programming model
SCA offers a simple and powerful way to construct
applications based on Service-Oriented Architecture (SOA).
SCA uses the Apache Tuscany open source technology
to provide an implementation of the published SCA specifications.
- Communications Enabled
Applications (CEA) programming model
CEA support provides REST and Web Service
interfaces to enable existing applications to quickly take advantage of
communications features involving phone calls and web collaboration.
- Session Initiation
Protocol (SIP) programming model
Integrated SIP servlet
support speeds development of converged communications applications.
- Fast, flexible, and
simplified application foundation
WebSphere Application
Server for z/OS includes the following highlights to improve productivity and
help deliver improved total cost of ownership benefits:
- Simplified
installation and maintenance
Achieve faster value through a simplified product
installation, update, and uninstallation with
integrated prerequisite and interdependency checking by using IBM Installation
Manager.
- Installation Manager
is a single installation program that loads and installs product
components from a structured collection of files that is called a repository.
- Easily determine
available product and maintenance packages, easily install selected
packages after prerequisite and interdependency checking, and uninstall
and roll back previously installed packages.
- Use remote or local
repositories to install, modify, or update WebSphere
Application Server for z/OS products and related components such as:
- WebSphere
Application Server for z/OS base
- WebSphere
Application Server for z/OS DMZ secure proxy server
- IBM HTTP Server
- WebSphere
Customization Toolbox
- Improved productivity
Increase your return on investment and improve the
flexibility of your business by making application services more reusable and
accessible to new users in an enterprise environment using the following
enhancements:
- Support for
connecting to multi-instance WebSphere MQ queue
managers.
You can provide host and port information in the
form of a connection name list, which a connection factory or activation
specification uses to connect to a multi-instance queue manager.
- Support for singleton
session enterprise beans as Java API for XML Web Services (JAX-WS)
endpoints.
- Specify a policy set
and bindings for a service reference that is different from the policy
set attachment for the service.
- Specify CustomProperties policy and binding to set generic
properties that are not supported in other policy types.
The CustomProperties
policy provides an alternative way to set a binding property instead of using
the JAX-WS programming model to set the property on the BindingProvider
object.
- Simplified
development of server-side REST applications using Java API for RESTful Web Services (JAX-RS).
- Support for using
Java Contexts and Dependency Injection (JCDI) with JAX-RS.
You can use JAX-RS root resources and providers in
a JCDI-enabled web application archive. As part of Java Platform, Enterprise
Edition (Java EE) 6, you can take advantage of the JCDI feature to make
applications easier to develop while increasing maintainability.
- Extend the
interactivity of Enterprise and Web commerce applications with
Communications Enabled Applications (CEA) for integrated telephony and
collaborative web services.
Using a single core application, you can enable
multiple modes of communication. The CEA capability delivers call control,
notifications, and interactivity and provides the platform for more complex
communications.
- Install, uninstall,
and update enterprise application files by adding them to a monitored
directory.
This feature is now supported when running the
application server on z/OS as well as the application server on other operating
systems.
- Support for both
client affinity and client reroute for applications that use DB2
databases. Use client affinity functions to control the order of servers
that are tried during initial connection processing or the client
reroute functions to specify alternate server locations when connections
to a database server fails.
- Connect your
applications to the latest versions of a wide array of industry-leading
databases to enable maximum deployment flexibility. WebSphere
Application Server Version 8.0 has been tested with the following new
databases and JDBC drivers:
- Derby 10.5
- DataDirect
Connect for Java Database Connectivity (JDBC) driver V4.1
- Improved security
You can securely build and deliver applications
and environments that use new capabilities in WebSphere
Application Server Version 8.0 including the following features:
- Support for OASIS Web
Services Security SAML Token Profile 1.1 usage scenarios that use SAML
Assertions as security tokens in web services SOAP security to exchange
client identity and other security information across security domains.
- Support for JSR 196:
Java Authentication SPI for Containers (JASPI) specification, which
enables third-party security providers to handle the Java Platform,
Enterprise Edition (Java EE) authentication of HTTP request and response
messages destined for web applications.
- Support for
configuring federated repositories at the domain level in a multiple
security domain environment.
Now, when you copy a security domain from the
global level, the users and groups defined at the global level are also copied
to the security domain. This is also true when copying from an existing domain.
A newly created security domain that uses the file-based VMM repository
requires that the user populate the repository with users and groups.
- Propagate an
LtpaToken2 cookie to downstream web single sign-on applications using an
application programming interface (API).
- Generate SAML tokens
and to propagate SAML tokens in SOAP messages using the Web Services
Security application programming interfaces (WSS API). For web services
clients, this is an alternative solution to using policy set
attachments.
Both SAML bearer subject confirmation method and
SAML sender-vouches subject confirmation methods are supported.
- Request SAML tokens
from an external Security Token Service (STS) and then propagate the
SAML token in web services request messages from a web services client
using WSS APIs.
Both SAML bearer subject confirmation method and
SAML sender-vouches subject confirmation methods are supported.
- Manage self-issue
SAML token configuration using wsadmin
commands.
- Support for all
security updates as defined in the Java Servlet
3.0 specification (JSR-315), including the new servlet
security annotations, use of new programmatic security APIs, and the
dynamic updating of the servlet security
configuration.
- Generate and consume
tokens using WS-Trust Issue and WS-Trust Validate requests for JAX-WS
web services that use Web Services Security.
As a result of these requests, the login module
issues, validates, or exchanges tokens with a WS-Trust Security Token Service,
such as the service that is provided with the IBM Tivoli® Federated Identity
Manager.
- Enhancements to the
security auditing service to assist with audit compliance.
- Security
configuration report now includes information about session security,
web attributes, and the HttpOnly setting to
enable you to get a more complete view of your server security settings
- More security
features of the server are enabled by default for enhanced security
hardening.
- New browser attribute
for single sign on (SSO) to prevent client-side applications (such as
Java scripts) from accessing cookies to prevent some cross-site
scripting vulnerability
- High performance
Achieve total cost of ownership benefits through
unmatched performance and scalability characteristics including the following
advantages:
- Provide high
availability for a WebSphere MQ queue manager
that is connected to WebSphere Application
Server by specifying multiple connection names in your WebSphere Application Server definition for the WebSphere MQ link sender channel.
If the active gateway queue manager fails, the
service integration bus can use this information to reconnect to a standby
gateway queue manager.
- Enhance performance
by disabling WebSphere MQ functionality in WebSphere Application Server, provided you do not
need to take advantage of any WebSphere MQ
functionality.
By default, when a WebSphere
Application Server process or an application client process starts, and while
this process is running, an amount of processing is done to support WebSphere MQ-related function, regardless of whether any WebSphere MQ-related function is ever used.
- Cutting-edge
performance for real applications in commercial environments.
- A unified clustering
framework that brings workload balancing, dependability, and other
benefits to the application servers in your heterogeneous environment.
- Extensive Deployment
Environments
WebSphere Application
Server for z/OS V8.0 includes the following highlights to improve
administration as you migrate existing applications
and infrastructures to virtual and Cloud deployments:
Focus resources on innovation instead of
maintenance, and reduce the costs of managing your environment with effective
and simplified management tools.
- Complete job manager
actions and run jobs from a deployment manager. The deployment manager
administrative console has "Jobs" navigation tree choices
similar to those in the job manager administrative console.
- Collect Java dumps
and core files using the administrative console to help diagnose
memory-related or application server CPU utilization problems.
- Use the Reliability
Availability and Serviceability (RAS) granularity capabilities to assign
different RAS attribute values to different sets of requests within the
same application server.
This capability improves the reliability,
availability, and serviceability of the application server and the requests it
processes.
- Take advantage of
batch processing capabilities provided in the application server to
accommodate applications that must perform batch work alongside
transactional applications.
- Store and access log,
trace, System.err, and System.out
information produced by the application server or your applications
quickly and conveniently using the High Performance Extensible Logging
(HPEL) log and trace framework.
HPEL logs can also be viewed with the new
administrative console log viewing functionality, which uses Web 2.0 technology
to provide a powerful tabular view and simple mechanisms to filter logs that
are local or remote.
- Quickly recover a
damaged node using the -asExistingNode parameter
of the addNode command.
- Access data from
multiple components without causing timeouts or other unwanted
situations by sharing locks between transaction branches.
You can share locks between transaction branches
when accessing data where multiple DB2 Java Database Connectivity (JDBC)
connections to the same database exist that are in the same transaction, from
the same or different servers.
- Define and register a
remote host target with the job manager using the registerHost
command.
Unlike targets that are WebSphere
Application Server profiles and are registered using the registerWithJobManager
command at the deployment manager or administrative agent, a remote host target
is not required to have any WebSphere Application
Server products installed.
- Enhance the output of
application properties files by running the AdminTask
extractConfigProperties command with the UseNewApplicationOutput option.
The option enables you to easily locate and edit
application property values.
- Use the new enableClientModule option to specify to deploy
client modules.
- View an SCA composite
definition by exporting it to a file using scripting, in addition to
viewing the SCA composite definition in the administrative console.
By exporting an SCA composite definition, you can
preserve information about the composite.
- Export WSDL and XSD
documents that are used by an SCA composition unit using the
administrative console, in addition to using wsadmin
scripting.
- Submit a job to
manage profiles using the manageprofiles job
of the job manager to create, augment, or delete a WebSphere
Application Server profile.
- Improve the
reliability, availability, and serviceability of the application server
and the requests it processes by using the request-level RAS granularity
capabilities.
- Create and manage
target groups using the TargetGroup command
with the wsadmin tool.
- Simplified migration
Migrate your application
server environment using the WASPreUpgrade and WASPostUpgrade command-line tools or the Migration
Management tool graphical user interface (GUI). You can migrate from WebSphere Application Server Version 6.0, 6.1, and 7.0 to WebSphere Application Server for z/OS V8.0
Accelerate developer productivity through
integrated and optimized developer tooling. Rational Application Developer
Version 8.0 provides capabilities for you to develop applications, assemble and
deploy your applications to WebSphere Application
Server for z/OS and includes a rapid-deployment feature for testing
applications in the Version 8.0 runtime environment.
DMZ secure proxy server
The DMZ secure proxy server for WebSphere
Application Server for z/OS can be used to provide a secure platform for your
proxy server.
The DMZ Secure Proxy Server for IBM WebSphere
Application Server installation allows you to install your proxy server in the
demilitarized zone (DMZ), while reducing the security risk that might occur if
you choose to install an application server in the DMZ to host a proxy server.
The risk is reduced by removing any functionality from the application server
that is not required to host the proxy servers, but that could pose a security
risk. Installing the secure proxy server in the DMZ rather than the secured
zone presents new security challenges. However, the secure proxy server is
equipped with capabilities to provide protection from these challenges.
The following capabilities are available to harden the security of the DMZ
Secure Proxy Server for IBM WebSphere Application
Server and to determine the level of security to assign.
- Startup user permissions
- Routing considerations
- Administration options
- Error handling
- Denial of service protection
Websphere Application Server
plug-ins V8.0
WebSphere Application Server for z/OS works with a
web server to route requests for dynamic content, such as servlets,
from web applications. The web servers are necessary for directing traffic from
browsers to the applications that run on an application server. The web server
plug-in uses the XML configuration file to determine whether a request is for
an application server.
The WebSphere Application Server for z/OS Web
server plug-ins are used to establish and maintain persistent HTTP and HTTPS
connections to application servers.
When the plug-in is ready to send a request to the application server, it
first checks its connection pool for existing connections. If an existing
connection is available the plug-in checks its connection status. If the status
is still good, the plug-in uses that connection to send the request. If a connection
does not exist, the plug-in creates one. If a connection exists but has been
closed by the application server, the plug-in closes that connection and opens
a new one.
IBM HTTP Server V8.0
IBM HTTP Server for WebSphere Application Server
for z/OS provides advanced web server capabilities with consistent management
and security in a WebSphere Application Server for
z/OS environment. IBM HTTP Server for WebSphere
Application Server for z/OS is based on Apache HTTP Server.
WebSphere Application Server for z/OS consists of
the following FMIDs:
|
Table 1. Basic FMIDs
|
|
FMID
|
Description
|
|
HBBO800
|
WebSphere Application Server for
z/OS V8.0 repository
|
An IBM program is identified by a program number. The program number for WebSphere Application Server for z/OS V8.0 is 5655-W65.
Basic Machine-Readable Materials are materials that are supplied under the
base license and feature numbers, and are required for the use of the product.
Optional Machine-Readable Materials are orderable under separate feature
numbers, and are not required for the product to function.
The program announcement material describes the features supported by WebSphere Application Server for z/OS V8.0. Ask your IBM
representative for this information if you have not already received a copy.
The distribution medium for this program is magnetic tape or downloadable
files. This program is in SMP/E RELFILE format and is installed by using SMP/E.
See "Installation Instructions" for more
information about how to install the program.
You can find information about the physical tape for the basic
machine-readable materials for WebSphere Application
Server for z/OS V8.0 in the CBPDO Memo To Users
Extension.
WebSphere Application Server for z/OS V8.0 has no
optional machine-readable materials.
The following sections identify the basic and optional publications for WebSphere Application Server for z/OS V8.0.
Please note that the main documentation distribution medium for WebSphere Application Server for z/OS V8.0 is the
Information Center, which can be accessed via the product documentation page at
http://www-306.ibm.com/software/webservers/appserv/was/library
In addition to the Information Center, relevant WebSphere
Application Server for z/OS product documentation is available in PDF format at
the same URL.
Table 2 identifies the basic unlicensed program
publications for WebSphere Application Server for
z/OS V8.0. One copy of each of these publications is included when you order
the basic materials for WebSphere Application Server
for z/OS V8.0. Additional copies can be obtained from the IBM Publications Web
Site at URL: http://www.ibm.com/shop/publications/order/. For additional
information contact your IBM representative.
|
Table 2. Basic
Material: Unlicensed Publications
|
|
Publication Title
|
Form Number
|
|
Program Directory for WebSphere
Application Server for z/OS V8.0
|
GI11-9850-01
|
|
License Information WebSphere
Application Server for z/OS V8.0
Carefully read the WebSphere Application Server
for z/OS V8.0 IBM International Program License Agreement GA32-0896-00, a
copy of which will be provided to you with the order (Hardcopy or Electronic
format); The License Agreement may contain terms that supersede the Licensed
terms included with this program component.
|
GA32-0896-00
|
Basic unlicensed or licensed publications are available for download at the WebSphere Application Server for z/OS library page:
http://www-306.ibm.com/software/webservers/appserv/was/library/
Table 3 identifies the basic licensed program
publications for WebSphere Application Server for
z/OS V8.0. The first copy is available at no charge to the licensees of the
basic material by ordering the 800 feature number. Order
additional copies by using the 8xxx feature number. A fee is charged for
additional copies.
|
Table 3. Basic
Material: Licensed Publications
|
|
Publication Title
|
Form Number
|
Feature Number
|
|
WebSphere Application Server for
z/OS V8.0 Installing your application serving environment
|
GA32-0897
|
Library page
|
|
WebSphere Application Server for
z/OS V8.0 Migrating, coexisting, and interoperating
|
GA32-0899
|
Library page
|
|
WebSphere Application Server for
z/OS V8.0 Setting up the application serving environment
|
GA32-0898
|
Library page
|
|
WebSphere Application Server for
z/OS V8.0 Developing and deploying applicaitons
|
SA23-1356
|
Library page
|
|
WebSphere Application Server for
z/OS V8.0 Securing applications and their environment
|
SA23-1357
|
Library page
|
|
WebSphere Application Server for
z/OS V8.0 Administering application and their environment
|
SA23-1358
|
Library page
|
|
WebSphere Application Server for
z/OS V8.0 Tuning guide
|
SA23-1360
|
Library page
|
|
WebSphere Application Server for
z/OS V8.0 Troubleshooting and support
|
GA32-0900
|
Library page
|
All of the documents listed here are available for use at the WebSphere Application Server for z/OS V8.0 Information
Center.
WebSphere Application Server for z/OS V8.0 has no
optional publications provided.
No program source materials or viewable program listings are provided for WebSphere Application Server for z/OS V8.0.
You might want to use the publications listed in Table 4
during the installation of WebSphere Application
Server for z/OS V8.0. To order copies, contact your IBM representative or visit
the IBM Publications Center at
http://ehone.ibm.com/publications/servlet/pbi.wss?CTY=US.
|
Table 4. Publications
Useful During Installation
|
|
Publication Title
|
Form Number
|
|
IBM SMP/E for z/OS User's Guide
|
SA22-7773
|
|
IBM SMP/E for z/OS Commands
|
SA22-7771
|
|
IBM SMP/E for z/OS Reference
|
SA22-7772
|
|
IBM SMP/E for z/OS Messages, Codes, and Diagnosis
|
GA22-7770
|
|
IBM Software Delivery Standard Packaging Rules for
z/OS-Based Products
|
SC23-3695
|
|
z/OS MVS JCL Reference
|
SA22-7597
|
|
z/OS System Codes
|
SA22-7626
|
|
Installation Manager for z/OS V1.4 Program Directory
|
GI11-9852-01
|
This section describes the IBM support available for WebSphere
Application Server for z/OS.
Contact your IBM representative for specific information about available
program services.
Before you install WebSphere Application Server
for z/OS, make sure that you have reviewed the current Preventive Service
Planning (PSP) information. The PSP Buckets maintain current lists (which have
been identified since the package was created) of any recommended or required
service for the installation of this package. This service includes software
PSP information that contains HIPER and required PTFs
against the base release.
If you obtained WebSphere Application Server for
z/OS as part of a CBPDO, HOLDDATA is included.
If the CBPDO for WebSphere Application Server for
z/OS is older than two weeks old by the time you install the product materials,
you should contact the IBM Support Center or use S/390 Software Xcel to obtain
the latest PSP Bucket information. You can also obtain the latest PSP Bucket
information by going to the following Web site:
http://www14.software.ibm.com/webapp/set2/psearch/search?domain=psp
For program support, access the Software Support Web site at
http://www-01.ibm.com/software/support/.
PSP Buckets are identified by UPGRADEs, which
specify product levels; and SUBSETs, which specify
the FMIDs for a product level. The UPGRADE and SUBSET
values for WebSphere Application Server for z/OS V8.0
are shown as follows:
|
Table 5. PSP
Upgrade and Subset ID
|
|
UPGRADE
|
SUBSET
|
Description
|
|
WASAS800
|
HBBO800
|
WebSphere Application Server for
z/OS V8.0
|
You should also consult the following PSP bucket for information related to
the IBM Installation Manager.
Table
6. PSP Upgrade and
Subset ID
|
Table 6. PSP
Upgrade and Subset ID
|
|
UPGRADE
|
SUBSET
|
Description
|
|
IIMZOSV1
|
HGIN140
|
Installation Manager for z/OS V1.4
|
Report any problems which you feel might be an error in the product
materials to your IBM Support Center. You may be asked to gather and submit
additional diagnostics to assist the IBM Support Center in their analysis.
Table 7 identifies the component IDs (COMPID) for WebSphere Application Server for z/OS V8.0.
|
Table 7. Component
IDs
|
|
FMID
|
COMPID
|
Component Name
|
RETAIN
Release
|
|
HBBO800
|
5655I3500
|
WebSphere Application Server for
z/OS V8.0
|
800
|
|
HBBO800
|
5655N0212
|
DMZ secure proxy server V8.0
|
800
|
|
HBBO800
|
5655I3511
|
Web server plug-ins V8.0
|
800
|
|
HBBO800
|
5655I3510
|
IBM HTTP Server V8.0
|
800
|
This section identifies the program and relevant service levels of WebSphere Application Server for z/OS. The program level
refers to the APAR fixes that have been incorporated into the program. The
service level refers to the PTFs that have been
incorporated into the program.
No APARs have been incorporated into WebSphere Application Server for z/OS V8.0.
No PTFs against this release of WebSphere Application Server for z/OS have been
incorporated into the product tape.
It is highly recommended that you frequently check the WebSphere
Application Server for z/OS V8.0 PSP Bucket for HIPER and SPECIAL Attention PTFs against all FMIDs that you
must install.
The following sections identify the system requirements for installing and
activating WebSphere Application Server for z/OS
V8.0. The following terminology is used:
- Driving system:
the system used to install the program; where SMP/E executes.
The program might have specific operating system or
product level requirements for using processes, such as binder or assembly
utilities during the installation.
- Target system:
the system on which the program is configured and run.
The program might have specific product level
requirements, such as needing access to the library of another product for
link-edits. These requirements, either mandatory or optional, might directly
affect the element during the installation or in its basic or enhanced
operation.
In many cases, you can use a system as both a driving system and a target
system. However, you can make a separate IPL-able clone of the running system
to use as a target system. The clone must include copies of all system
libraries that SMP/E updates, copies of the SMP/E CSI data sets that describe
the system libraries, and your PARMLIB and PROCLIB.
Use separate driving and target systems in the following situations:
- When you install a new level
of a product that is already installed, the new level of the product will
replace the old one. By installing the new level onto a separate target
system, you can test the new level and keep the old one in production at
the same time.
- When you install a product
that shares libraries or load modules with other products, the
installation can disrupt the other products. By installing the product
onto a separate target system, you can assess these impacts without
disrupting your production system.
This section describes the environment of the driving system that is
required to install WebSphere Application Server for
z/OS V8.0.
The driving system can run in any hardware environment that supports the
required software.
|
Table 8. Driving
System Software Requirements
|
|
Program
Number
|
Product
Name
|
Minimum
VRM
|
Minimum
Service Level
will satisfy
these
APARs
|
Included
in this
product's
shipment?
|
|
5694-A01
|
z/OS
|
V01.10.00
|
N/A
|
No
|
|
APAR OA34228 must be applied to the z/OS driving system
|
|
5655-G44
|
IBM SMP/E for z/OS
|
V03.5
|
N/A
|
No
|
|
Any one of the following:
|
|
5655-N98
|
IBM 31-bit SDK for z/OS, JAVA 2 Technology Edition,
Version 5
|
V01.05.00
|
N/A
|
No
|
|
-- OR --
|
|
5655-N99
|
IBM 64-bit SDK for z/OS, JAVA 2 Technology Edition, V5
|
V01.05.00
|
N/A
|
No
|
Note: Installation may require migration to new z/OS releases to be
service supported. See
http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html.
This section describes the environment of the target system that is required
to install and use WebSphere Application Server for
z/OS V8.0.
The target system can run in any hardware environment that supports the
required software.
Installation requisites identify products that are required by and must
be present on the system or products that are not required by but should
be present on the system for the successful installation of this product.
Mandatory installation requisites identify products that are required on the
system for the successful installation of this product. These products are
specified as PREs or REQs.
|
Table 9. Target
System Mandatory Installation Requisites
|
|
Program
Number
|
Product
Name
|
Minimum
VRM
|
Minimum
Service Level
will satisfy
these
APARs
|
Included
in this
product's
shipment?
|
|
5694-A01
|
z/OS
|
V01.10.00
|
N/A
|
No
|
|
APAR OA34228 must be applied to the z/OS target system
|
|
5655-G44
|
IBM SMP/E for z/OS
|
V03.5
|
N/A
|
No
|
|
5655-W65
|
IBM Installation Manager or above
|
V1.4
|
N/A
|
No
|
|
Any one of the following:
|
|
5655-N98
|
IBM 31-bit SDK for z/OS, JAVA 2 Technology Edition,
Version 5
|
V01.05.00
|
N/A
|
No
|
|
-- OR --
|
|
5655-N99
|
IBM 64-bit SDK for z/OS, JAVA 2 Technology Edition, V5
|
V01.05.00
|
N/A
|
No
|
Note: Installation may require migration to new z/OS releases to be
service supported. See
http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html.
Conditional installation requisites identify products that are not
required for successful installation of this product but can resolve such
things as certain warning messages at installation time. These products are
specified as IF REQs.
WebSphere Application Server for z/OS V8.0 has no
conditional installation requisites.
Operational requisites are products that are required by and must be
present on the system or products that are not required by but should be
present on the system for this product to operate all or part of its functions.
Mandatory operational requisites identify products that are required for
this product to operate its basic functions. These products are specified as PREs or REQs.
|
Table 10. Target
System Mandatory Operational Requisites
|
|
Program
Number
|
Product Name and
Minimum VRM/Service Level
|
|
5694-A01
|
z/OS V01.10.00 or later
|
Conditional operational requisites identify products that are not
required for this product to operate its basic functions but are required at
run time for this product to operate specific functions. These products are
specified as IF REQs.
WebSphere Application Server for z/OS V8.0 has no
conditional operational requisites.
Toleration/coexistence requisites identify products that must be present on
sharing systems. These systems can be other systems in a multisystem
environment (not necessarily sysplex), a shared DASD
environment (such as test and production), or systems that reuse the same DASD
environment at different time intervals.
WebSphere Application Server for z/OS V8.0 has no
toleration/coexistence requisites.
Negative requisites identify products that must not be installed on
the same system as this product.
WebSphere Application Server for z/OS V8.0 has no
negative requisites.
WebSphere Application Server for z/OS V8.0
libraries can reside on all supported DASD types.
Table 11 lists the total space that is required
for each type of library.
|
Table 11. Total
DASD Space Required by WebSphere Application Server
for z/OS V8.0
|
|
Product
|
Library
Type
|
Total Space
Required
(3390 Trks)
|
File System Requirements
|
|
WebSphere Application Server
base HBBO800
|
|
|
Target
|
20
|
|
|
|
Distribution
|
45000
|
|
|
|
File Systems
|
|
|
|
|
|
45000
|
Installation Manager repository
|
|
|
|
52000
|
For each copy of base WebSphere
Application Server for z/OS code
|
|
|
|
21000
|
For each copy of DMZ secure proxy server code
|
|
|
|
1200
|
For each copy of Web server plug-ins code
|
|
|
|
1200
|
For each copy of IBM HTTP Server V8.0 code
|
Notes:
- For non-RECFM U data sets,
IBM recommends using system-determined block sizes for efficient DASD
utilization. For RECFM U data sets, IBM recommends using a block size of
32760, which is most efficient from the performance and DASD utilization
perspective.
- Abbreviations used for data
set types are shown as follows.
|
U
|
Unique data set, allocated by this product and used by
only this product. This table provides all the required information to
determine the correct storage for this data set. You do not need to refer to
other tables or program directories for the data set size.
|
|
S
|
Shared data set, allocated by this product and used by
this product and other products. To determine the correct storage needed for
this data set, add the storage size given in this table to those given in
other tables (perhaps in other program directories). If the data set already
exists, it must have enough free space to accommodate the storage size given
in this table.
|
|
E
|
Existing shared data set, used by this product and other
products. This data set is not allocated by this product. To determine
the correct storage for this data set, add the storage size given in this
table to those given in other tables (perhaps in other program directories).
If the data set already exists, it must have enough free space to accommodate
the storage size given in this table.
|
3. If
you currently have a previous release of this product installed in these
libraries, the installation of this release will delete the old release and
reclaim the space that was used by the old release and any service that had
been installed. You can determine whether these libraries have enough space by
deleting the old release with a dummy function, compressing the libraries, and
comparing the space requirements with the free space in the libraries.
4. For
more information about the names and sizes of the required data sets, see "Allocate SMP/E Target and Distribution Libraries".
- Abbreviations used for the
file system path type are as follows.
|
N
|
New path, created by this product.
|
|
X
|
Path created by this product, but may already exist from a
previous release.
|
|
P
|
Previously existing path, created by another product.
|
- All target and distribution
libraries listed have the following attributes:
- The default name of
the data set may be changed.
- The default block size
of the data set may be changed.
- The data set may be
merged with another data set that has equivalent characteristics.
- The data set may be
either a PDS or a PDSE.
- All target libraries listed
have the following attributes:
- These data sets can be
SMS-managed, but they are not required to be SMS-managed.
- These data sets are
not required to reside on the IPL volume.
- The values in the
"Member Type" column are not necessarily the actual SMP/E
element types that are identified in the SMPMCS.
- All target libraries that are
listed and contain load modules have the following attributes:
- These data sets can be
in the LPA, but they are not required to be in the LPA.
- These data sets can be
in the LNKLST.
- These data sets are
not required to be APF-authorized.
|
Table 12. Storage
Requirements for SMP/E Work Data Sets
|
|
Library
DDNAME
|
T
Y
P
E
|
O
R
G
|
R
E
C
F
M
|
L
R
E
C
L
|
No.
of
3390
Trks
|
No.
of
DIR
Blks
|
|
SMPWRK1
|
S
|
PDS
|
FB
|
80
|
120
|
10
|
|
SMPWRK2
|
S
|
PDS
|
FB
|
80
|
30
|
10
|
|
SMPWRK3
|
S
|
PDS
|
FB
|
80
|
9500
|
150
|
|
SMPWRK4
|
S
|
PDS
|
FB
|
80
|
80
|
10
|
|
SMPWRK5
|
S
|
PDS
|
FB
|
80
|
45000
|
400
|
|
SYSUT1
|
U
|
SEQ
|
--
|
--
|
24000
|
0
|
|
SYSUT2
|
U
|
SEQ
|
--
|
--
|
30
|
0
|
|
SYSUT3
|
U
|
SEQ
|
--
|
--
|
30
|
0
|
|
SYSUT4
|
U
|
SEQ
|
--
|
--
|
30
|
0
|
The following table provides an estimate of the storage needed in the SMP/E
data sets for WebSphere Application Server for z/OS
V8.0. You must add the estimates to those of any other programs and service
that you install to determine the total additional storage requirements. *
If the table indicates that the SMPLTS data set must be a PDSE and your
existing SMPLTS is a PDS, you must allocate a new PDSE and copy your SMPLTS into it; then change the SMPLTS DDDEF entry to
indicate the new PDSE data set.
|
Table 13. Storage
Requirements for SMP/E Data Sets
|
|
Library
DDNAME
|
T
Y
P
E
|
O
R
G
|
R
E
C
F
M
|
L
R
E
C
L
|
No.
of
3390
Trks
|
No.
of
DIR
Blks
|
|
SMPLTS
|
E
|
PDS
|
U
|
0
|
50
|
1
|
|
SMPMTS
|
E
|
PDS
|
FB
|
80
|
15
|
5
|
|
SMPPTS
|
E
|
PDS
|
FB
|
80
|
5000
|
500
|
|
SMPSCDS
|
E
|
PDS
|
FB
|
80
|
15
|
2
|
|
SMPSTS
|
E
|
PDS
|
FB
|
80
|
15
|
2
|
The following tables describe the target and distribution libraries and file
system paths required to install WebSphere
Application Server for z/OS V8.0. The storage requirements of WebSphere Application Server for z/OS must be added to the
storage required by other programs having data in the same library or path.
Note: The data in these tables should be used when determining which
libraries can be merged into common data sets. In addition, since some ALIAS
names may not be unique, ensure that no naming conflicts will be introduced
before merging libraries.
|
Table 14. Storage
Requirements for Target Libraries
|
|
Library
DDNAME
|
Member
Type
|
Target
Volume
|
T
Y
P
E
|
O
R
G
|
R
E
C
F
M
|
L
R
E
C
L
|
No.
of
3390
Trks
|
No.
of
DIR
Blks
|
|
SBBOEXEC
|
EXEC
|
TVOL1
|
U
|
PDS
|
VB
|
255
|
10
|
5
|
|
SBBOJCL
|
Sample
|
TVOL2
|
U
|
PDS
|
FB
|
80
|
10
|
5
|
|
Table 15. File
System Paths
|
|
DDNAME
|
T
Y
P
E
|
Path Name
|
|
SBBOIMR
|
N
|
/usr/lpp/InstallationManagerRepository/HBBO800/IBM
|
|
SMPJHOME
|
N
|
/usr/lpp/java/J5.0
|
|
Table 16. Storage
Requirements for Distribution Libraries
|
|
Library
DDNAME
|
T
Y
P
E
|
O
R
G
|
R
E
C
F
M
|
L
R
E
C
L
|
No.
of
3390
Trks
|
No.
of
DIR
Blks
|
|
ABBOEXEC
|
U
|
PDS
|
VB
|
255
|
10
|
5
|
|
ABBOIMR
|
U
|
PDS
|
VB
|
255
|
45000
|
1000
|
|
ABBOJCL
|
U
|
PDS
|
FB
|
80
|
10
|
5
|
WebSphere Application Server for z/OS requires
several thousand additional tracks (3390 tracks) for run-time data sets. The
amount of space depends on the application server structure to be used, the
applications to be run, and the amount of data storage the applications
require.
Installing WebSphere Application Server for z/OS
might result in the deletion of other FMIDs. To see
which FMIDs will be deleted, examine the ++VER
statement in the SMPMCS of the product.
If you do not want to delete these FMIDs at this
time, install WebSphere Application Server for z/OS
into separate SMP/E target and distribution zones.
Note: These FMIDs are not automatically
deleted from the Global Zone. If you want to delete these FMIDs
from the Global Zone, see the SMP/E manuals for instructions.
WebSphere Application Server for z/OS V8.0 has no
special considerations for the target system.
This chapter describes the installation method and the step-by-step
procedures to install and to activate the functions of WebSphere
Application Server for z/OS V8.0.
WebSphere Application Server for z/OS V8.0 base is
installed using the IBM Installation Manager and a repository containing the WebSphere Application Server for z/OS product code.
You must first create an Installation Manager on your z/OS system. To create
an the Installation Manager, follow the instructions
presented in the Installation Manager information center located at the
following URL.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp
A summary of using the Installation Manager is located in the Installation
Manager for z/OS V1.4 Program Directory, GI11-9852-01, which can be accessed
here:
http://www-306.ibm.com/software/webservers/appserv/was/library/
Install the IBM Installation Manager repository for WebSphere
Application Server for z/OS using SMP/E as explained in section "Sample Jobs for WebSphere
Application Server for z/OS V8.0 base" through "Perform
SMP/E ACCEPT".
The use of the Installation Manager to create the product code for WebSphere Application Server for z/OS base is explained in "Mount the WebSphere
Application Server for z/OS V8.0 product repository" through "Install the WebSphere
Application Server for z/OS V8.0 base".
The following sample installation jobs are provided as part of the product
to help you install WebSphere Application Server for
z/OS:
|
Table 17. Sample
Installation Jobs - HBBO800
|
|
Job Name
|
Job Type
|
Description
|
RELFILE
|
|
BBOCSICR
|
SETUP
|
Sample job to create an SMP/E global zone and required
data sets
|
IBM.HBBO800.F1
|
|
BBOZNRT
|
SETUP
|
Sample job to create an SMP/E target zone and dlib zone, and required data sets
|
IBM.HBBO800.F1
|
|
BBORECEV
|
RECEIVE
|
Sample job to receive SMP/E deliverables for the WebSphere Application Server for z/OS product repository
|
IBM.HBBO800.F1
|
|
BBOALLOC
|
ALLOCATE
|
Sample job to allocate target and distribution libraries
for the WebSphere Application Server for z/OS
product repository
|
IBM.HBBO800.F1
|
|
BBOISMKD
|
MKDIR
|
Sample job to allocate the system paths for the WebSphere Application Server for z/OS product repository
|
IBM.HBBO800.F1
|
|
BBODDDEF
|
DDDEF
|
Sample job to define SMP/E DDDEFs
for the WebSphere Application Server for z/OS
product repository
|
IBM.HBBO800.F1
|
|
BBOAPPLY
|
APPLY
|
Sample APPLY job for the WebSphere
Application Server for z/OS product repository
|
IBM.HBBO800.F1
|
|
BBOACCEP
|
ACCEPT
|
Sample ACCEPT job for the WebSphere
Application Server for z/OS product repository
|
IBM.HBBO800.F1
|
|
BBO1CFS
|
ALLOCATE
|
Sample job to allocate a file system for the WebSphere Application Server for z/OS base product
|
IBM.HBBO800.F1
|
|
BBO1INST
|
INSTALL
|
Sample job to install the WebSphere
Application Server for z/OS base product with the Installation Manager for
z/OS V1.4
|
IBM.HBBO800.F1
|
|
BBO1UNIN
|
UNINSTALL
|
Sample job to uninstall the WebSphere
Application Server for z/OS base product
|
IBM.HBBO800.F1
|
|
BBO2CFS
|
ALLOCATE
|
Sample job to allocate a file system for the DMZ secure
proxy server product
|
IBM.HBBO800.F1
|
|
BBO2INST
|
INSTALL
|
Sample job to install the DMZ secure proxy server product
with the Installation Manager for z/OS V1.4
|
IBM.HBBO800.F1
|
|
BBO2UNIN
|
UNINSTALL
|
Sample job to uninstall the DMZ secure proxy server
product
|
IBM.HBBO800.F1
|
|
BBO3CFS
|
ALLOCATE
|
Sample job to allocate a file system for the WebSphere Application Server for z/OS Web server plug-ins
|
IBM.HBBO800.F1
|
|
BBO3INST
|
INSTALL
|
Sample job to install the Web server plug-ins V8.0 product
with the Installation Manager for z/OS V1.4
|
IBM.HBBO800.F1
|
|
BBO3UNIN
|
UNINSTALL
|
Sample job to uninstall the Web server plug-ins V8.0
product
|
IBM.HBBO800.F1
|
|
BBO4CFS
|
ALLOCATE
|
Sample job to allocate a file system for the IBM HTTP
Server product
|
IBM.HBBO800.F1
|
|
BBO4INST
|
INSTALL
|
Sample job to install the IBM HTTP Server product with the
Installation Manager for z/OS V1.4
|
IBM.HBBO800.F1
|
|
BBO4UNIN
|
UNINSTALL
|
Sample job to uninstall the IBM HTTP Server product
|
IBM.HBBO800.F1
|
You can access the sample installation jobs by performing an SMP/E RECEIVE
and then copying the jobs from the relfiles to a work
data set for editing and submission. See Table 17 to find
the appropriate relfile data set.
You can also copy the sample installation jobs from the tape or product
files by submitting the following job. Depending on your distribution medium,
use either the //TAPEIN or the //FILEIN DD statement and comment out or delete
the other statement. Before you submit the job, add a job card and change the
lowercase parameters to uppercase values to meet the requirements of your site.
//STEP1 EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//TAPEIN DD DSN=IBM.HBBO800.F1,UNIT=tunit,
// VOL=SER=volser,LABEL=(x,SL),
// DISP=(OLD,KEEP)
//FILEIN DD DSN=IBM.HBBO800.F1,UNIT=SYSALLDA,DISP=SHR,
// VOL=SER=filevol
//OUT DD DSNAME=jcl-library-name,
// DISP=(NEW,CATLG,DELETE),
// VOL=SER=dasdvol,UNIT=SYSALLDA,
// SPACE=(TRK,(primary,secondary,dir))
//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSIN DD *
COPY INDD=xxxxIN,OUTDD=OUT
/*
See the following information to update the statements in
the previous sample:
TAPEIN:
tunit is the unit value that matches the
product tape.
volser is the volume serial that matches the
product tape.
x
is the tape file number that indicates the location of the data set name on the
tape.
See the documentation that is
provided by CBPDO for the location of IBM.fmid.Fy on
the tape.
FILEIN:
filevol is the volume serial of the DASD
device where the downloaded files reside.
OUT:
jcl-library-name
is the name of the output data set where the sample jobs are stored.
dasdvol is the volume serial of the DASD
device where the output data set resides.
SYSIN:
xxxxIN is either TAPEIN or FILEIN depending on
your input DD statement.
You can install the WebSphere Application Server
for z/OS repository using an existing SMP/E global zone, or create a new one.
To create a new SMP/E global zone, edit and submit sample job BBOCSICR.
You can install the WebSphere Application Server
for z/OS repository into existing target and distribution zones, or create new
ones.
To create new SMP/E target and distribution zones, edit and submit sample
job BBOZNCRT.
Note: The Installation Manager repository for WebSphere
Application Server for z/OS is only required when building the WebSphere Application Server for z/OS code. Therefore, you
may want to store them separately, apart from software libraries that must be
replicated on each system in your data center.
If you have obtained WebSphere Application Server
for z/OS as part of a CBPDO, use the RCVPDO job in the CBPDO RIMLIB data set to
receive the WebSphere Application Server for z/OS repository
FMID, service, and HOLDDATA that are included on the CBPDO tape. For more
information, see the documentation that is included in the CBPDO.
The FMID for the WebSphere Application Server for
z/OS repository is HBBO800.
Expected Return Codes and Messages: You will receive return code of 0
if the job runs correctly.
Edit and submit sample job BBOALLOC to allocate the SMP/E target and
distribution libraries for the WebSphere Application
Server for z/OS repository. Consult the instructions in the sample job for more
information.
Expected Return Codes and Messages: You will receive return code of 0
if the job runs correctly.
Edit and submit sample job BBOISMKD to mount the file system for the WebSphere Application Server for z/OS repository at mountpoint
-PathPrefix-/usr/lpp/InstallationManagerRepository/HBBO800
and create required subdirectories.
Consult the instructions in the sample job for more information.
Expected Return Codes and Messages: You will receive return code of 0
if the job runs correctly, unless some of the required directories already
exist, in which case you will receive a return code of 4.
Edit and submit sample job BBODDDEF to create DDDEF entries for the SMP/E
target and distribution libraries for the WebSphere
Application Server for z/OS repository. Consult the instructions in the sample
job for more information.
Expected Return Codes and Messages: You will receive return code of 0
if the job runs correctly.
Edit and submit sample job BBOAPPLY to perform an SMP/E APPLY CHECK for the WebSphere Application Server for z/OS repository. Consult
the instructions in the sample job for more information. After you take actions
that are indicated by the APPLY CHECK, remove the CHECK operand and run the job
again to perform the APPLY.
Note: The GROUPEXTEND operand indicates that SMP/E applies all
requisite SYSMODs. The requisite SYSMODS might be
applicable to other functions.
Expected Return Codes and Messages from APPLY CHECK: You will receive
a return code of 0 if this job runs correctly, unless one or more HOLDs was bypassed, in which case you will receive a return
code of 4.
Expected Return Codes and Messages from APPLY: You will receive a
return code of 0 if this job runs correctly, unless one or more HOLDs was bypassed, in which case you will receive a return
code of 4.
Edit and submit sample job BBOACCEP to perform an SMP/E ACCEPT CHECK for WebSphere Application Server for z/OS repository. Consult
the instructions in the sample job for more information.
After you take actions that are indicated by the ACCEPT CHECK, remove the
CHECK operand and run the job again to perform the ACCEPT.
Note: The GROUPEXTEND operand indicates that SMP/E accepts all
requisite SYSMODs. The requisite SYSMODS might be
applicable to other functions.
Expected Return Codes and Messages from ACCEPT CHECK: You will
receive a return code of 0 or 4 if this job runs correctly, unless one or more HOLDs was bypassed, in which case you will receive a return
code of 4.
Expected Return Codes and Messages: from ACCEPT You will receive a
return code of 0 or 4 if this job runs correctly, unless one or more HOLDs was bypassed, in which case you will receive a return
code of 4.
The SBBOIMR file system now contains the Installation Manager repository files for the WebSphere
Application Server for z/OS product. If PTFs were
applied, it may also contain additional fix packs for WebSphere
Application Server for z/OS - any of which can be installed.
Unmount the SBBOIMR file system and remount it read-only
at a location of your choice. The recommended location is:
/usr/lpp/InstallationManagerRepository/HBBO800
Edit and submit sample job BBO1CFS to allocate and mount a file system for
the WebSphere Application Server for z/OS base
product code. Consult the instructions in the sample job for more information.
Mount this file system at the location where the IBM Installation Manager
will install, uninstall, or apply maintenance to the products in the file
system. The mount location does not need to be the same location at which the
file system is mounted in production.
Expected Return Codes and Messages: You will receive a return of 0 if
the job runs correctly.
Edit and submit sample job BBO1INST to install the WebSphere
Application Server for z/OS. Consult the instructions in the sample job for
more information.
By default, the latest version of the product is installed from the product
repository with the default list of optional features.
To install a particular level of the product from the repository, see the
instructions in the sample job.
You can also specify optional features and national language to be
installed. See the WebSphere Application Server for
z/OS V8.0 information center for the details.
Expected Return Codes and Messages: You will receive a return of 0 if
the job runs correctly.
When the installation is complete, unmount the
product file system and remount it on your target system at the location at
which it is to be accessed.
WebSphere Application Server for z/OS DMZ secure
proxy server is installed using the Installation Manager and a repository
containing the WebSphere Application Server for z/OS
product.
You must first create an IBM Installation Manager on your z/OS system if you
have not already done so. Follow the instructions in the IBM Installation
Manager information center located here:
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp
A summary of using the Installation Manager is located in the Installation
Manager for z/OS V1.4 Program Directory, GI11-9852-01, which can be accessed
here:
http://www-306.ibm.com/software/webservers/appserv/was/library/
The following instructions assume that the repository is mounted at:
/usr/lpp/InstallationManagerRepository/HBBO800
Edit and submit sample job BBO2CFS to allocate and mount a file system for
the WebSphere Application Server for z/OS DMZ secure
proxy server product. Consult the instructions in the sample job for more
information.
Mount this file system at the location where the Installation Manager will
install the product code. The file system must be mounted read/write at this
location whenever the Installation Manager will install, uninstall, or apply
maintenance to the products in the file system. The mount location does not
need to be the same location at which the file system is mounted in production.
Expected Return Codes and Messages: You will receive return code of 0
if the job runs correctly.
Edit and submit sample job BBO2INST to install the WebSphere
Application Server for z/OS DMZ secure proxy server product. Consult the
instructions in the sample job for more information.
By default, the latest version of the product is installed from the product
repository.
To install a particular level of the product from the repository, see the instructions
in the sample job.
Expected Return Codes and Messages: You will receive return code of 0
if the job runs correctly.
When the installation is complete, unmount the
product file system and remount it on your target system at the location at which
it is to be accessed.
Web server plug-ins are installed using the
Installation Manager and a repository containing the WebSphere
Application Server for z/OS product.
You must first create an IBM Installation Manager on your z/OS system if you
have not already done so. Follow the instructions in the IBM Installation
Manager information center located here:
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp
A summary of using the Installation Manager is located in the Installation
Manager for z/OS V1.4 Program Directory, GI11-9852-01, which can be accessed
here:
http://www-306.ibm.com/software/webservers/appserv/was/library/
The following instructions assume that the repository is mounted at
/usr/lpp/InstallationManagerRepository/HBBO800
Edit and submit sample job BBO3CFS to allocate and mount a file system for
the Web server plug-ins. Consult the instructions in the sample job for more
information.
Mount this file system at the location where the Installation Manager will
install the product code. The file system must be mounted read/write at this
location whenever the Installation Manager will install, uninstall, or apply
maintenance to the products in the file system. The mount location does not
need to be the same location at which the file system is mounted in production.
Expected Return Codes and Messages: You will receive return code 0 if
the job runs correctly.
Edit and submit sample job BBO3INST to install the Web server plug-ins.
Consult the instructions in the sample job for more information.
By default, the latest version of the product is installed from the product
repository. To install a particular level of the product from the repository,
see the instructions in the sample job.
When the installation is complete, unmount the
product file system and remount it on your target system at the location at
which it is to be accessed.
WebSphere Application Server for z/OS IBM HTTP
Server V8.0 is installed using the Installation Manager and a repository
containing the WebSphere Application Server for z/OS
product.
You must first create an IBM Installation Manager on your z/OS system if you
have not already done so. Follow the instructions in the IBM Installation
Manager information center located here:
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp
A summary of using the Installation Manager is located in the Installation
Manager for z/OS V1.4 Program Directory, GI11-9852-01, which can be accessed
here:
http://www-306.ibm.com/software/webservers/appserv/was/library/
The following instructions assume that the repository is mounted at:
/usr/lpp/InstallationManagerRepository/HBBO800
Edit and submit sample job BBO4CFS to allocate and mount a file system for
the IBM HTTP Server product code. Consult the instructions in the sample job
for more information.
Mount this file system at the location where the Installation Manager will
install the product code. The file system must be mounted read/write at this
location whenever the Installation Manager will install, uninstall, or apply
maintenance to the products in the file system. The mount location does not
need to be the same location at which the file system is mounted in production.
Expected Return Codes and Messages: You will receive a return code of
0 if the job runs correctly.
Edit and submit sample job BBO4INST to install the the
IBM HTTP Server product code. Consult the instructions in the sample job for
more information.
By default, the latest level of the product in the repository is installed.
To install a specific level, see the instructions in the sample job.
Expected Return Codes and Messages: You will receive return code of 0
if the job runs correctly.
When the installation is complete, unmount the
product file system and remount it on your target system at the location at
which it is to be accessed.
For instructions on how to activate and use WebSphere
Application Server for z/OS, including DMZ secure proxy server, and Web server
plug-ins V8.0 see the WebSphere Application Server
for z/OS V8.0 information center, accessible from this URL:
http://www-306.ibm.com/software/webservers/appserv/was/library/
For instructions on how to activate and use IBM HTTP Server, see the IBM
HTTP Server V8.0 information center, accessible from this URL:
http://www-306.ibm.com/software/webservers/appserv/was/library/
At this URL, click the V8.0 tab, then find either the WebSphere
Application Server for z/OS V8.0 or IBM HTTP Server V8.0 information centers
and click "view page".
References in this document to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe on
any of IBM's intellectual property rights may be used instead of the IBM
product, program, or service. Evaluation and verification of operation in
conjunction with other products, except those expressly designated by IBM, is
the user's responsibility.
APAR numbers are provided in this document to assist in locating PTFs that may be required. Ongoing problem reporting may
result in additional APARs being created. Therefore,
the APAR lists in this document may not be complete. To obtain current service
recommendations and to identify current product service requirements, always
contact the IBM Customer Support Center or use S/390 SoftwareXcel
to obtain the current "PSP Bucket".
IBM may have patents or pending patent applications covering subject matter
in this document. The furnishing of this document does not give you any license
to these patents. You can send license inquiries, in writing, to the
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, New York 10504-1785
USA
For online versions of this book, we authorize you to:
- Copy, modify, and print the
documentation contained on the media, for use within your enterprise,
provided you reproduce the copyright notice, all warning statements, and
other required statements on each copy or partial copy.
- Transfer the original
unaltered copy of the documentation when you transfer the related IBM
product (which may be either machines you own, or programs, if the
program's license terms permit a transfer). You must, at the same time,
destroy all other copies of the documentation.
You are responsible for payment of any taxes, including personal property
taxes, resulting from this authorization.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow the exclusion of implied warranties, so the
above exclusion may not apply to you.
Your failure to comply with the terms above terminates this authorization.
Upon termination, you must destroy your machine readable documentation.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
CBPDO
CICS
DB2
IBM
IBMLink
IMS
Language Environment
MQSeries
MVS/ESA
OS/390
RACF
RETAIN
SP
SystemPac
VTAM
WebSphere
z/OS
z/VM
z/Architecture
zSeries
System z
The following terms are trademarks of other companies as follows:
|
JAVA
|
Java and all Java-based trademarks and logos are
trademarks or registered trademarks of Sun Microsystems, Inc. in the United
States and/or other countries.
|
|
UNIX
|
UNIX is a registered trademark of The Open Group in the
United States and other countries.
|
Program Directory for WebSphere Application
Server for z/OS Version 8.0.0, June 2011
You may use this form to comment about this document, its organization, or subject
matter with the understanding that IBM may use or distribute whatever
information you supply in any way it believes appropriate without incurring any
obligation to you.
For each of the topics below please indicate your satisfaction level by
circling your choice from the rating scale. The rating scale is 1, 2, 3, 4, 5, where "1" is very satisfied and "5"
is very dissatisfied. If a statement does not apply, please
circle N.
|
|
Satisfaction
|
|
Ease of product installation
|
1
|
2
|
3
|
4
|
5
|
N
|
|
Contents of Program Directory
|
1
|
2
|
3
|
4
|
5
|
N
|
|
Installation Verification Programs
|
1
|
2
|
3
|
4
|
5
|
N
|
|
Time to install the product
|
1
|
2
|
3
|
4
|
5
|
N
|
|
Readability and organization of Program Directory tasks
|
1
|
2
|
3
|
4
|
5
|
N
|
|
Necessity of all installation tasks
|
1
|
2
|
3
|
4
|
5
|
N
|
|
Accuracy of the definition of the installation tasks
|
1
|
2
|
3
|
4
|
5
|
N
|
|
Technical level of the installation tasks
|
1
|
2
|
3
|
4
|
5
|
N
|
|
Ease of getting the system into production after
installation
|
1
|
2
|
3
|
4
|
5
|
N
|
How did you order this product?
CBPDO
CustomPac
ServerPac
Independent
Other
Is this the first time your organization has installed this product?
Yes
No
Were the people who did the installation experienced with the installation
of z/OS products?
Yes
No
If yes, how many years? __
If you have any comments to make about your ratings above, or any other
aspect of the product installation, please list them below:
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
Please provide the following contact information:
____________________________________________________________
Name and Job Title
____________________________________________________________
Organization
____________________________________________________________
____________________________________________________________
Address
____________________________________________________________
Telephone
Thank you for your participation.
Please send the completed form to (or give to your IBM representative who
will forward it to the WebSphere Application Server
for z/OS Version 8.0.0 Development group):
International Business Machines Corporation
Department 55JA, Mail Station P384
2455 South Road
Poughkeepsie, NY 12601-5400
Internet e-mail: wasdoc@us.ibm.com