Red Hat NETSCAPE MANAGEMENT SYSTEM 4.5 - COMMAND-LINE Manual do Utilizador descarregar pdf (Página 2)

1. Deployment Topology

Installing IBM® Connections in a network deployment to achieve optimum scaling, load balancing, and failover.

A network deployment can consist of a single server with all applications installed, or two or more sets of servers that are grouped

to share the workload. You must also configure an additional system with WebSphere® Application Server Network Deployment

Manager, which enables you to build, manage, and tune the clustered servers.

A network deployment provides the administrator with a central management facility, and it ensures that users have constant access

to data. It balances the workload between servers, improves server performance, and facilitates the maintenance of performance

when the number of users increases. The added reliability also requires a larger number of systems and the experienced

administrative personnel who can manage them.

Standard Enterprise Network Deployment Architecture

Figure 1 shows the enterprise-level network deployment of IBM Connections without any additional complexity. This topology shows

a two-node cluster of IBM Connections, in which the LDAP and database servers communicate with the cell controlled by the

Deployment Manager. The Tivoli Directory Integrator server sits between the database and LDAP, maintaining synchronization

between both.

IBM Connections is installed on the Deployment Manager machine and from there is pushed out to the nodes in the cell,

node01Node and node02Node. The shared data store is a shared space accessible from all nodes in the configuration and the

Deployment Manager. In this case the shared space is mounted on the Deployment Manager machine and shared with both nodes,

at the same location on those machines.

Sitting in front of the entire configuration is the Web server, from which the end user accesses IBM Connections.

Figure 1

In this Scenario and in the above Topology diagram the following apply:

 Cognos/Metric is not installed - Cognos install/configuration is covered in a separate document.

 IBM Connections Content Manager (Filenet) is not installed - Filenet install/configuration is covered in a separate document.

 the WAS Deployment Manager and the IHS server both co-exist on the same physical machine, but they are depicted (in the

diagram) as existing on different machines. This was done to help simplify understanding of this deployment - note the

hostname is the same for both.

 The Domino Mailin server is not integrated with the MS-AD2008 LDAP so that users are not automatically created as needed on

the Domino mail server; instead Domino mailin users were created manually (as needed) and the mapping between IC4 and

Domino users was based on the users email address. This is not typically how customers would configure Notifications and

Domino mail integration.

When installing IBM Connections there are three deployment options to choose from ie small, medium and large. This deployment

uses the Medium topology; see Deployment options for more details.

Topology: Medium deployment

Install a subset of applications in separate clusters. IBM Connections provides three predefined cluster names shared

among all 12 applications. Use this option to distribute applications according to your usage expectations. For instance, you

might anticipate higher loads for the Profiles application and install it in its own cluster, while other applications could be

installed in a different cluster. This option allows you to maximize the use of available hardware and system resources to

1 2 3 4 5 6 7 ... 127 128

Sem comentários

Red Hat NETSCAPE MANAGEMENT SYSTEM 4.5 - COMMAND-LINE Manual do Utilizador Página 2