| Sun Java System Content Delivery Server Installation Guide |    
|
| C H A P T E R 2 |
|
Preparing Your Environment |
Before deploying Sun Java System Content Delivery Server, you must first set up your environment.
This section presents the following topics:
Before you start the installation process for Content Delivery Server, make sure that you have the hardware required and that the required software is installed on each server to which you intend to deploy components of Content Delivery Server. Software required for optional features that you want to use must also be installed.
This section describes the following requirements:
The following table shows the minimum hardware required for all hosts on which you plan to deploy components of Content Delivery Server.
|
One of the following platforms:
|
|
|
Twice the size of memory, for example, if you have 2 gigabytes of RAM, the recommended swap size is 4 gigabytes. See the documentation for your operating system for information on setting the size of the swap space. |
|
|
Minimum of 5 gigabytes disk space for system installation, database, and log files. Need for additional space depends on the amount and size of content managed. |
The following table shows the software required for hosts on which you plan to deploy components of Content Delivery Server.
|
Oracle Database 10g Release 1 (10.1.0.2) or later, Standard Edition or Enterprise Edition |
|
|
Bash shell version 2.0.5 or later, which can be obtained from the following location: http://www.gnu.org/software/bash/bash.html Note - The bash shell must be installed in the /bin directory. |
|
|
Java Platform, Standard Edition Development Kit 5.0 Update 11 (1.5.0_11). |
|
|
The following browsers are supported: For the device-based Subscriber Portal, any device browser that supports wireless markup language (WML) 1.0, compact HTML (cHTML,) or extensible HTML (XHTML) is also supported. |
|
Some features of Content Delivery Server have additional requirements, which are needed only if you intend to use the feature. These requirements are described in the following table.
|
A device library contains the APIs that an application uses. Several standard libraries are included with Content Delivery Server. To support applications that use other APIs, you must first submit the library to Content Delivery Server. For example, to support iAppli applications, the DoJa library is required. |
|
|
To integrate Content Delivery Server with an existing subscriber database that is stored in an LDAP directory, you need an LDAP server such as the Sun Java System Directory Server 5.2. |
|
|
Server that handles the transmission of wireless data. To deliver content using over-the-air (OTA) technology, you need a WAP gateway. |
|
|
Gateway that handles WAP push messages. To deliver messages or digital rights objects using WAP push, you need a WAP PPG. |
|
|
To send or receive messages using SMPP, you need the Java SMPP API library version 0.3.7 from SourceForge.net. |
|
|
Server that handles short messaging service (SMS) messages. To provide SMS services or deliver content in an SMS message, you need an SMSC. To use SMS push to deliver digital rights objects, you need an SMSC that supports this type of content. |
|
|
Server that handles multimedia message service (MMS) messages. To provide MMS services, you need an MMSC. |
|
|
Implementation of the Open Mobile Alliance Digital Rights Management (OMA DRM) 1.0 guidelines |
To protect content according to the OMA DRM 1.0 guidelines, you need an application that implements the guidelines. Support for SafeNet DRM Fusion Toolkit 2.1.1 is provided with Content Delivery Server. See http://www.safenet-inc.com/digital_rights_management/DRM_Fusion_Toolkit.asp for information on SafeNet DRM Fusion Toolkit. |
|
Server that stores and delivers on-demand and live streamed content. To support streamed content in Content Delivery Server you need a streaming server. |
|
|
Plug-ins to the Java Image I/O Framework for reading, writing, and streaming image formats. To use the watermarking utility provided with Content Delivery Server, you need version 1.1. |
|
|
Implementation of the X Server, which provides display resources to other systems. To use the watermarking utility provided with Content Delivery Server, see Appendix C for the list of packages needed. |
Oracle Database 10g Release 1 (10.1.0.2) or later, Standard Edition or Enterprise Edition is required. To set up Oracle Database, follow these steps:
1. Verify that you have a valid installation of Oracle Database.
Documentation (including installation and upgrade details) can be found on Oracle’s TechNet web site at http://technet.oracle.com/. Set the character set for the database to AL32UTF8.
2. Follow the preinstallation steps mentioned in the Oracle documentation.
3. Ensure that you have the following information for your Oracle Database installation:
You need this information later when you configure the database.
See the Sun Java System Content Delivery Server 5.1 Release Notes for information on the files that you received. Create a home directory and extract the product files from the Zip file as described in the release notes. The following directories are created under the home directory:
/$CDS_HOME /bin /cfg /deployment /dist /Documentation /external /javadoc /LicenseReadme /ReleaseNotes /tools |
Content Delivery Server requires that environment variables are set correctly on each machine that hosts Content Delivery Server components. You must create a variable named CDS_HOME that points to the directory that contains Content Delivery Server product files. Also, the PATH variable must include the directory that contains the executable files.
For example, if you extracted the product files to a directory named /cds, the following commands correctly set the environment variables:
| Sun Java System Content Delivery Server Installation Guide | 820-1943-10 |
|
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.
9 Operating System on SPARC® processors