Skip to content

Module Suite installation guide: Deploy Modules with OpenText System Center

Overview

This guide covers the Deployment phase that is part of the Module Suite installation guide.

  • Deployment
  • Installation
  • Activation
  • Configuration
  • Post-installation patching

This phase covers the deployment of the software binaries on the target system.

We will refer to the Content Server main installation directory as %OTCS_HOME% .

Important change starting from Module Suite 4.0.0

Starting from Module Suite 4.0.0, AnswerModules is no longer releasing dedicated Windows (.exe) or Unix/Linux (.bin) click-through installers.

From this version onward, Module Suite components (Content Script, Beautiful WebForms, Smart Pages, Script Console, all Module Suite Extension packages) are delivered exclusively as OpenText System Center compatible installation packages.

The legacy platform-specific guides for Deploying on Windows and Deploying on Unix/Linux remain available as a reference for users still operating on Module Suite 3.x or earlier.

Installation packages

The guide assumes that the required Module Suite System Center installation packages have been provisioned and are ready to be uploaded to your OpenText System Center deployment.

What is OpenText System Center

OpenText System Center is the standard OpenText platform for the centralized deployment, monitoring and lifecycle management of OpenText products and add-ons across one or more Content Server environments (single-node, clustered, on-premise or containerized).

By aligning Module Suite distribution with the OpenText System Center packaging format, AnswerModules ensures that:

  • Module Suite components are deployed using the same tooling and procedures that OpenText customers already use to manage their Content Server environments.
  • Deployments can be automated, repeatable and auditable, with a centralized view of versions and patches across all managed nodes.
  • Clustered and containerized environments are supported out-of-the-box, without the need for separate manual procedures on each node.
  • Upgrades and patching follow the standard OpenText lifecycle, simplifying coordination with OpenText Content Server releases.

Next Steps

Please proceed to the Installation phase.