Stand-alone server topology
The stand-alone scenario is different from the single-server since the database server, LDAP server, and Web server software are installed on different physical servers than the IBM® WebSphere® Portal. This configuration enables you to distribute the software in your network and therefore distribute the processing load.
For a stand-alone configuration, you can use an existing, supported database in your network and an existing, supported LDAP directory. You can configure IBM WebSphere Portal to authenticate with the LDAP server. The following illustration displays a common topology for a stand-alone server. The HTTP server, (also referred to as Web server) is installed on a server in a protected network. The LDAP server and database server are also installed on different servers. WebSphere Portal and WebSphere Application Server are installed on the same 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.
