- 5 -
• Downloaded and uncompress both parts of the installation kit for Universal Content
Management 10g R1 (184.108.40.206.0), called
This tutorial will guide you through the process to create a distributed installation of WebCenter and
Content Server components for development purposes only.
Architecture for Development Purposes vs. Enterprise Deployment
A development environment is used internally, that is, ‘in house,’ by a few developers only.
• Since we don’t expect many concurrent requests which would create heavy load on the system,
the system requires a relatively low set of resources. It is typical to use one or two host
machines with 4-8 GByte of memory.
• The system does not need to be scalable and failure-resilient, or highly available. We will not
use duplicate resources and clustering.
• Since it is used only internally and the system is not supposed to contain live, sensitive data, we
will not strengthen its security. We will not set up firewalls or configure encrypted
communication between the components, etc.
• We can use some software components which are only recommended for development
purposes. That saves us from installing large, enterprise-grade software components, for
example, for user repositories, or single sign-on.
A typical enterprise-wide WebCenter architecture, as recommended by Oracle, is documented in
Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter11g Release 1
(11.1.1), available at http://download.oracle.com/docs/cd/E21764_01/core.1111/e12037/toc.htm
Contrary to the above outlined characteristics, a WebCenter installation for the enterprise:
• involves several machines to provide adequate resources.
• uses redundant hardware resources, load balancing, and clustering to provide a scalable and
highly available system.
• contains several firewalls and relies on encrypted communication (HTTPS), where necessary.
• uses enterprise-strength additional components, like Oracle Internet Directory (OID) for
security repositories and Oracle Access Manager (OAM) for single sign-on.
In this tutorial we will describe the installation of a simple development environment, but with a twist
not typically explained in detail in the documentation: We will create a distributed architecture, where
the Content Server components are located on a second machine. Please note that this architecture does
not provide clustering, i.e., all of the components are running only on one node, but the combined
resources of the two hosts guarantee a better performance.
Although we use only two machines and relocate the Content Server components only, a similar
technique can be used to further distribute the software components to multiple machines.
Initial Software Configuration
First let’s analyze the details of the initial software setup, which is the prerequisite for the tutorial.
Below is a diagram depicting the initial software architecture, illustrating the ports and protocols being
used and the most important components.