Standard distributed scenario

In a typical distributed installation scenario, you install the Content Cortex platform components on a system of networked servers. You can install some components as stand-alone applications, or install multiple instances of a single component.

In a standard distributed environment, you install Content Cortex on a number of servers, according to the way you plan to use your system. This configuration model can vary from a simple system with one stand-alone component per server to a complex system with multiple instances, virtual servers, and managed deployments.

Most Content Cortex platform components work with middleware applications such as web application servers, databases, and directory service applications. This guide provides additional considerations and preparation tasks by role for the administrators of these middleware applications. For details on which types and versions of these applications work together in a Content Cortex platform environment, see the Software Product Compatibility Reports External link opens a new window or tab.

You can choose to collocate some Content Cortex platform components. For details on collocation decisions, see the Software Product Compatibility Reports External link opens a new window or tab.

If you plan to use related add-on products with your Content Cortex platform environment, review the installation documentation for the add-ons before you install and configure Content Cortex.

Creating multiple instances of Content Cortex platform components

You can install or deploy multiple instances of Content Platform Engine on a single web application server.

Using multiple instances of Content Platform Engine means that you can provide a different repository of content for different areas within an organization. For example, you could create an instance for use by a Research and Development group, and create a separate instance for use by a Human Resources group.