Installation and deployment options
There are two types of installation: full and base.
z/OS® only: The SMP/e installs the repository used by the IBM® Installation Manager to install the IBM WebSphere® Portal binaries. You then have a configuration option in the z/PMT to configure a base or full environment. There are also four deployment options to choose: stand-alone, federated unclustered, clustered, and multi-clustered.
Choose one of the following installation options:
Note: The bit architecture of the installation program
follows one of the following options:
- The bit architecture of the operating system
- The bit architecture of the existing WebSphere Application Server
- Base
- Select this option to deploy a base set of WebSphere Portal features. You can use this option to selectively add additional features, samples, and developed content after installation to create a deployment that meets your business needs.
- Full
- Select this option to deploy the full set of WebSphere Portal features and samples that are available for your offering. You can use this option to use and test a wide range of features or to develop a proof-of-concept deployment. Choose this option if you plan on utilizing the Managed Pages or syndication features.
Choose one of the following deployment options or move between
the different options:
- Stand-alone deployment
- Install a stand-alone production server if you do not require a robust clustered environment. You can also use this option to examine and test functions and features to decide how to accomplish your business goals. You can add this stand-alone production server to a federated IBM WebSphere Application Server Network Deployment cell. It creates a federated, unclustered production server.
- z/OS only: Federated unclustered deployment
- Install a federated, unclustered production server if you require
the robustness of a WebSphere Application Server Network Deployment cell
but do not require a clustered environment. You can also use this
option to examine and test functions and features in a managed but
unclustered node. After determining that the functions and features
work in a managed, unclustered node, you can create a clustered environment.Note: If you choose to install the federated, unclustered production server deployment option, you can install only one node, referred to as the primary node. You cannot install any additional portal nodes.
- Clustered deployment
- Install a clustered production environment to create a set of highly available production servers in a Network Deployment cell. The servers are managed by a WebSphere Application Server Network Deployment. After installing the primary node and creating the cluster, you can continue to add additional nodes as your business needs grow. You have a choice between a static and dynamic clustered environment. See "WebSphere Virtual Enterprise Dynamic Clusters" for more information about dynamic clusters.
- Multi-clustered deployment
- Multiple clusters are sets of servers that are managed together
within a single administrative domain known as a cell, and participate
in workload management. The single administrative domain creates a
centralized administration for your clusters. Applications are shared
within the cell. An application definition is cell-scoped, meaning
that a single application can be used by any server running on any
node or cluster within the cell. Only one application root can be
defined for the portal enterprise application across multiple clusters.
As a result, all clusters within the cell share the same context root,
for example: "/wps/portal". For additional information, see "Determining
application sharing between clusters".Note: You now have a choice between a static and dynamic multi-clustered environment. See "WebSphere Virtual Enterprise Dynamic Clusters" for more information about dynamic clusters.
WebSphere Portal provides a portal light mode which can improve portal startup time and reduce memory consumption in production environments; see for information.