| Sun Java System Content Delivery Server Installation Guide |    
|
| C H A P T E R 1 |
|
Installation Overview |
Installing Sun Java
System Content Delivery Server consists of making sure that you have the prerequisite hardware and software, deploying the components, and setting up your system.
The section presents the following topics:
Planning is essential to ensuring a successful installation of Content Delivery Server. This section describes some of the items to consider in planning your deployment and provides some tips on capacity planning.
You can deploy all of the product components on a single application server or across multiple application servers, either on the same hosts or on multiple hosts. Installing components of Content Delivery Server, the web server, application server, and database on several hosts adds fault tolerance and improves system performance.
One way to begin planning is to determine the number of Vending Managers that you want to deploy. You can provide all content managed by a Catalog Manager to all subscribers by deploying a single Vending Manager, or provide content targeted to different audiences by deploying several customized Vending Managers.
Content Delivery Server is optimized for use with multi-CPU machines, such as a UNIX® system four-way server. Using multihoming, you can install more than one Vending Manager on a single host. See the documentation for the application server you are using for information on setting up multihoming.
Content Delivery Server is a fully scalable system. To increase system capacity, additional instances of the components can easily be added. The Content Delivery Server architecture also supports clustering. Clustering is a technique for setting up multiple servers to act as a single server. In a cluster, each server is equivalent to the other servers in the cluster.
To begin capacity planning for Content Delivery Server, start with the number of Catalog Managers and Vending Managers required. In planning for the capacity, it is important to consider future growth. For example, your subscriber base might grow exponentially. In addition, one very popular application might represent a demand spike that applies stress to the system.
Consider capacity estimates for the following system characteristics:
For example, Content Delivery Server provides better than one-second response time under typical circumstances, and response degrades linearly as the number of concurrent clients spikes.
The peak number of downloads per second possible depends on several factors, including the performance of your web server, application server, and Oracle database. Content Delivery Server maintains subscriber state in the database and therefore has virtually no overhead for transaction-time messaging, unlike other systems.
For additional information on capacity planning, see the Sun Java System Content Delivery Server Capacity Planning Guide.
The Content Delivery Server architecture supports a wide variety of deployment scenarios from deploying all components on the same server to deploying each component on its own server. The deployment configuration file that you create for each deployment determines how the components are deployed.
The basic configuration consists of deploying all components on the same server. This represents the minimum setup required to run Content Delivery Server and is the configuration generally used for the initial deployment. The following figure illustrates the basic configuration.
FIGURE 1-1 Basic Configuration
If your business model includes a centrally managed Catalog Manager that supplies remote Vending Managers, you might not need a local Vending Manager. In the Catalog Manager configuration, only the Catalog Manager, Developer Portal, Event Service, Messaging Service, Monitoring Service, and Catalog Search Service are deployed. All Vending Managers are deployed separately in Vending Manager configurations.
The following figure illustrates the Catalog Manager configuration.
FIGURE 1-2 Catalog Manager Configuration
One of the strengths of Content Delivery Server is the ability to serve different subscriber segments with customized Vending Managers. In this configuration, a Vending Manager is deployed and configured to receive content from an existing Catalog Manager. The Vending Manager can be colocated with the Catalog Manager or deployed at a remote location.
Each Vending Manager has its own billing manager, postpaid processor, and set of subscribers. An instance of the Subscriber Portal and Fulfillment Manager and each Content Delivery Server service, except the Catalog Search Service, is deployed with the Vending Manager.
The following figure illustrates the Vending Manager configuration.
FIGURE 1-3 Vending Manager Configuration
The deployment configuration file supports the deployment of any combination of components to a server. For example, the Catalog Manager could be deployed on one server, the Vending Manager deployed on a second server, and the service components deployed on a third server. You might want customized deployments in the following situations:
| Sun Java System Content Delivery Server Installation Guide | 820-1943-10 |
|
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.