The minimal hardware configuration you need to run the Sun Java System Content Delivery Server consists of a single server configured with one CPU (two CPUs is preferred), 1 GByte RAM (2 GBytes are preferred), and 5 GBytes of free disk space, running Sun Solaris
9.0 Operating System or HP-UX 11i, and Oracle 9i. This configuration is sufficient for an initial product evaluation, but not for an actual deployment.
This chapter describes a few sample Content Delivery Server configurations:
4.1 Trial Configuration
An initial trial of a content delivery system that supports a few thousand highly active subscribers might have a hardware configuration that looks like the one depicted in FIGURE 4-1:
FIGURE 4-1 Simple Two Server Configuration
The configuration employs two dual CPU servers for the Content Delivery Server Service and Database Modules. A simple router switch provides connectivity between these servers and to your private and public networks.
FIGURE 4-2 shows a sample configuration of the Content Delivery Server components (X indicates which applications are included).
FIGURE 4-2 Sample Application Configuration for Small Size Deployment
This configuration defines a single service domain including all the Content Delivery Server application components (running services as needed). There is only one host (cdssrv) in the Content Delivery Server Service Module and you only need to configure a single deployment.
While this configuration might be sufficient for an initial content delivery system, be sure you understand the security risks inherent in combining the internal administrative services and the external subscriber and developer services in a single service domain. Service availability can also be a concern while deploying the Content Delivery Server to a single host. Finally, this configuration raises concerns about database availability and data security.
The hardware requirements for this deployment are:
- Two Netra 20 servers, each with two 900 MHz CPUs, 2 GB RAM, and internal disk.
Alternatively, you can use the Sun Fire 280R server in a similar configuration.
- A simple router switch depending on your connectivity requirements.
4.2 Small to Medium Deployment
As you move beyond the initial trial, you might want to consider a configuration such as the one depicted in the following diagram:
FIGURE 4-3 Configuration for a Small to Medium Size Deployment
This configuration employs two to eight dual CPU servers for the externally facing services (four are shown in the figure) and one additional server for an administrative service domain. The database module is configured with two Sun Fire V480 or V880 servers configured in a cluster configuration with shared mirrored disk arrays for database storage. The Sun Fire V880 has an integrated FC-A1 storage subsystem with up to 874 GBytes of storage capacity.
FIGURE 4-4 shows a sample configuration of the Content Delivery Server components:
FIGURE 4-4 Sample Application Configuration for Medium Deployment
The Content Service Module contains three service domains:
- Administration Domain - A single deployment on the host, cdsadm, contains both the Catalog Manager and Vending Manager administration consoles and relevant service applications. This deployment uses a private JMS broker.
- Developer Domain - A deployment containing the Developer Portal and relevant service applications is replicated across the servers cds1 and cds2, mainly for the sake of availability. To avoid conflicts with the subscriber domain, it is necessary to change the default port assignments. Each copy of the deployment uses a private JMS broker. The distribution module defines the virtual address, cdsdev:80, and implements sticky server load balancing.
- Subscriber Domain - A deployment containing the Subscriber Portal, the Fulfillment Manager, and all the service components, except notification, which is in the administrative domain. A single deployment configuration is replicated across the four servers, cds1 through cds4. To avoid conflicts with the Developer Domain, the default port assignments must be changed. Each copy of the deployment uses a private JMS broker. The distribution module defines the virtual address, cds:80, and implements sticky server load balancing.
Following are hardware requirements for this deployment:
- Three to nine Netra 20 servers, each with two 900MHz CPUs, 2 GBytes RAM, and an internal disk.
Alternatively, you can use the Sun Fire 280R server in a similar configuration.
- Two Sun Fire V480 or Sun Fire V880 servers, with two to eight CPUs and 2-8 GBytes RAM each. Count one CPU per server assigned to the subscriber service domain.
- Two 100 Mbit Ethernet load-balancing switches or some other redundant server load-balancing solution.
- Two cabinets with redundant power and cooling.
4.3 Multivending Deployment
If you plan to make use of the multivending feature you can use a configuration similar to the one described in Section 4.2, Small to Medium Deployment. However, if you plan to deploy more processes, use servers that can be configured with more CPUs. For instance, you can use either the Sun Fire V480 or Sun FireV880 server, which can be configured with up to four and eight CPUs, respectively. This provides a configuration that is easily scalable with respect to both subscribers and Vending Managers.
FIGURE 4-5 Configuration for Multivending Deployment
The illustrated configuration employs four Sun Fire V480 servers for the externally facing service domains and one additional server for the administrative service domain. The database module consists of two clustered Sun Fire V880 servers with mirrored disk arrays for database storage.
FIGURE 4-6 shows a deployment configuration with four Vending Managers.
FIGURE 4-6 Sample Application Configuration for Multivending Deployment
The Content Service Module consists of nine service domains:
- Catalog Administration Domain - This deployment contains the Catalog Manager administration console and the Developer Portal. It is configured as a single deployment on a single host, cdsadm. In this example, the Developer Portal is considered as an internal function. The only service included is the Monitoring Service. This deployment is configured to share the JMS broker (and event services) of the Vending Administration Domain for the first Vending Manager.
- Vending Administration Domains (4) - These deployments contain the Vending Manager administration console and all the service applications. For each Vending Manager, a deployment is replicated over the four hosts, cds1 through cds4. Each domain provides a JMS broker that it shares with the corresponding subscriber domains. The JMS broker for the first Vending Manager is also shared with the Catalog Administration Domain. The distribution module defines convenient external virtual addresses.
- Subscriber Vending Domains (4) - This deployment contains the Subscriber Portal, the Fulfillment Manager, and the Monitoring Service. For each Vending Manager, a deployment is replicated over the four hosts, cds1 through cds4. Each copy of this deployment shares the JMS broker of the corresponding Vending Administration Domain. The distribution module defines the external virtual addresses and implements sticky server load balancing.
Following are hardware requirements for this deployment:
- Five Sun Fire 480 servers, each with four 900 MHz CPUs, 4 GBytes RAM, and an internal disk.
- Two Sun Fire V880, with eight CPUs and 8 GBytes RAM each. Count one CPU per every two CPU assigned to the subscriber service domain.
- Two 100 Mbit Ethernet load-balancing switches or other redundant server load-balancing solution.
- Two cabinets with redundant power and cooling.
4.4 Large Deployment
You can easily scale the configurations described in the Section 4.2, Small to Medium Deployment and Section 4.3, Multivending Deployment by adding more servers and by providing additional resources for the database module. However, for large deployments you might consider using fewer large servers. FIGURE 4-7 uses the Sun Fire 6800 mid-range data-center server, which can be configured with up to 24 1200 MHz processors.
FIGURE 4-7 Configuration for Large Deployment
This configuration employs five Sun Fire 6800 servers. For the externally facing service domains, two servers are used, each partitioned into two system domains. For the internal administration domains, a third server is used, also partitioned into two system domains. The last two servers, clustered and configured with associated storage arrays (installed in Sun Fire 6800 cabinets), provide a highly available database server.
This hardware configuration works well for both single-vending and multivending content delivery systems. FIGURE 4-8 illustrates a single-vending configuration with multiple subscriber service domains.
FIGURE 4-8 Sample Application Configuration for Large Size Deployment
The Content Service Module consists of five domains:
- Administration Domain. The Administration Domain includes the Catalog Manager and Vending Manager administration consoles and all the service applications. This domain also provides a JMS broker that all deployments in this content delivery system share. The Administration Domain is replicated across two clustered system domains (adm-1 and adm-2). Clustering provides automatic restart and fail-over of the services in this domain. Clustering agents are not included with the Content Delivery Server. Contact Sun Professional Services for more information.
- Developer Domain. The developer domain is replicated across two system domains in each of two servers. This domain includes the Developer Portal and the Monitoring Service. It uses the shared JMS broker provided by the Administration Domain.
- WAP Domain. The WAP domain, also replicated, includes a Subscriber Portal configured for HTTP header-based device authentication. It also includes the Monitoring Service. It uses the shared JMS broker provided by the Administration Domain.
- Internet Domain. The Internet Domain, also replicated, includes the Subscriber Portal configured for username and password authentication. It also includes the Monitoring Service. It uses the shared JMS broker provided by the Administration Domain.
- Fulfillment Domain. The Fulfillment Domain, also replicated, includes the Fulfillment Manager and the Monitoring Service. It uses the shared JMS broker provided by the Administration Domain.
Following are hardware requirements for this deployment:
- Five Sun Fire 6800 servers, each with up to 24 1200 MHz CPUs
- Two to four Sun StorEdge T3 arrays (factory installed in Sun Fire 6800 cabinets)
- Gigabit network cards and cables
- Two gigabit load-balancing switches or other redundant server load balancing solution.
| Capacity Planning Guide
|
819-3211-10
|
    |
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.