Installing on z/OS
IBM® WebSphere® Portal provides flexible deployment options ranging from proof-of-concept where you can examine and test functionality to a highly available and scalable production environment.
About this task
Restriction: WebSphere Portal does
not support installing in console mode. You must either use an existing
response file or create your own response file using an operating
system that supports the graphical user interface.
- Enabling the IBM Subcapacity Reporting Tool
The IBM Subcapacity Reporting Tool (SCRT) is a no-charge IBM tool that reports required license capacity for subcapacity eligible products that run on IBM z/OS®. For information on SCRT, refer to http://www.ibm.com/servers/eserver/zseries/swprice/scrt/. For information on System z software pricing, refer to http://www.ibm.com/servers/eserver/zseries/swprice/. The input for SCRT tool is a sequential data set containing SMF 89 records, subtypes 1 and 2, for all the LPARs on the specified CPCs. At start up, IBM WebSphere Portal writes a string into SMF. Later, when the SCRT tool is invoked to process the SMF records, the tool recognizes that WebSphere Portal is installed in the LPAR(s) and is eligible for subcapacity pricing. - Worksheets
IBM WebSphere Portal provides worksheets that will assist you when defining variables within the Customization Dialog. The worksheets are available on the WebSphere Portal wiki. Choose the worksheet that matches the task within the Customization Dialog. - Installing and configuring your WebSphere Portal environment on z/OS
This section describes how to establish application-serving capability in new and existing environments. The information includes planning, preparing, completing, and maintaining product installations. - Using the Customization Dialog to configure WebSphere Portal using WebSphere Application Server
Customization is the process during which you make your installed IBM WebSphere Portal code work for you. This topic outlines the steps you follow to configure your WebSphere Portal using the Customization Dialog. Some of these tasks are completed during installation, as directed in the documentation, and other tasks are completed later when configuring the portal. - Preparing the z/OS operating system
The base z/OS environment and all of the subsystems associated with z/OS must be able to support your IBM WebSphere Portal installation. This topic provides information on prerequisite products and z/OS subsystem prerequisites with which you must comply before installation. - Obtaining an Installation Manager installation kit for installing the product on z/OS
The installation kit for the IBM Installation Manager is provided with the IBM WebSphere Portal product as FMID HGIN140. You can also download the IBM Installation Manager installation kit to your z/OS system. - Creating an Installation Manager for installing the product on z/OS
You can create one or more Installation Managers on your z/OS system to install and maintain software products. - Obtaining product repositories for installing the product on z/OS
IBM WebSphere Portal products are distributed as IBM Installation Manager repositories. These repositories contain the metadata and files that are required to create one or more levels of a particular product. - Installing WebSphere Portal on z/OS
Use the IBM Installation Manager to install the IBM WebSphere Portal product code. - Setting up a stand-alone production server on z/OS
Set up a stand-alone production environment when you do not need a robust clustered environment. A stand-alone server deployment is also useful to determine and validate the needs of your deployment. It enables you to examine and test the functions and features to decide how to accomplish business goals. - Setting up a federated unclustered production server
Set up a federated, unclustered production environment when you need a robust environment but do not require a clustered production environment. - Setting up a clustered production environment on z/OS
When creating a cluster of IBM WebSphere Portal servers, you can start with a standalone production server as your primary node or you can start with an existing IBM WebSphere Application Server managed server node. After creating the cluster with either option as the starting point, you can begin to add additional nodes to meet your business needs. - Configuring databases
Use the WebSphere Portal Customization Dialog to create, configure, and transfer databases. You can optionally configure database domains to share across separate portal instances and configure separate portal instances to use the same database subsystem.