C H A P T E R 2 |
Preparing Your Environment |
Before deploying the 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 the 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 the 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 the Content Delivery Server.
5 gigabytes disk space for system installation, database, and log files |
The following table shows the software required for hosts on which you plan to deploy components of the Content Delivery Server.
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 2 Platform, Standard Edition, (J2SE Note: If you are using Sun Java System Application Server, you must configure it to use the required SDK. See Section 2.2, Configure the Application Server. |
|
The following browsers are supported for the Developer Portal: The following browsers are supported for the Subscriber Portal:
The following browsers are supported for the Catalog Manager and Vending Manager administration consoles: Note: The browser that you use to administer the Catalog Manager or Vending Manager must use the Java Runtime Environment (JRE) software version 1.4.2_07 or higher if you want to use the bulk copy and move features. |
|
Some features of the Content Delivery Server have additional requirements, which are described in the following table.
A device library contains the APIs that an application uses. Several standard libraries are included with the Content Delivery Server. To support applications that use other APIs, you must first submit the library to the Content Delivery Server. For example, to support iAppli applications, the DoJa library is required. |
|
To integrate the 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. |
|
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. |
|
Gateway that handles WAP push messages. To deliver messages or digital rights objects using WAP push, you need a WAP PPG. |
|
Implementation of the Open Mobile Alliance Digital Rights Management (OMA DRM) 1.0 guidelines |
To protect content using the OMA DRM 1.0 guidelines, you need an application that implements the guidelines. For this release, support for SafeNet DRM Mobile is provided with the Content Delivery Server. See http://www.safenet-inc.com/products/sentinel/DRM_Mobile.asp for information on SafeNet DRM Mobile. |
One of the following database products 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.
If you are using Sun Java System Application Server, you must configure the application server before you deploy the Content Delivery Server.
By default, the application server uses J2SE 5.0. You must configure the application server to use J2SE 1.4.2 SDK. Instructions for this process are provided in the Sun Java System Application Server Enterprise Edition Release Notes, which are available at http://docs.sun.com/source/819-0214/relnotesEE.html#wp1059314.
In addition, to prevent the application server from displaying the directory listing for locations that do not have a welcome file, set the listings parameter in the following files to false:
See the Sun Java System Content Delivery Server 5.0 2005Q4 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 |
The 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 the 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:
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.