Install on z/OS

IBM WebSphere Portal provides flexible deployment options ranging from proof-of-concept where we can examine and test functionality to a highly available and scalable production environment.

Select the type of setup you need from the list of options. Follow the scenario to install and configure WebSphere Portal.

• Enable the IBM Subcapacity Reporting Tool
  The IBM Subcapacity Reporting Tool (SCRT) is a no-charge IBM toon 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 zSeries 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.
• Install and configuring the 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.
• Use the Customization Dialog to configure WebSphere Portal using WAS
  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.
• Prepare the z/OS operating system
  The base z/OS environment and all of the subsystems associated with z/OS must be able to support the 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. We can also download the IBM Installation Manager installation kit to the z/OS system.
• Create an Installation Manager for installing the product on z/OS
  We can create one or more Installation Managers on the 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 file required to create one or more levels of a particular product.
• Install WebSphere Portal on z/OS
  Use the IBM Installation Manager to install the IBM WebSphere Portal product code.
• Set 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 the deployment. It enables you to examine and test the functions and features to decide how to accomplish business goals.
• Set 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.
• Set up a clustered production environment on z/OS
  When creating a cluster of IBM WebSphere Portal servers, we can start with a standalone production server as the primary node or we can start with an existing IBM WAS managed server node. After creating the cluster with either option as the starting point, we can begin to add additional nodes to meet the business needs.
• Configure databases
  Use the WebSphere Portal Customization Dialog to create, configure, and transfer databases. We can optionally configure database domains to share across separate portal instances and configure separate portal instances to use the same database subsystem.

Parent: Installing