Skip to content

Content Script

Installation procedure (Windows)

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

  • Deploy Content Server Modules

  • Run the Module Suite Master Installer and install the Content Script module and the desired Module Suite Extension packages

Step-by-step procedure

The following screens will guide you through the deployment of Content Script Module.

Action to take Installer's screen
Select “Next” when ready to start the installation. Welcome Screen
Acceptance of the end-user license agreement is mandatory.
Upon installation, a copy of the agreement will be available in: %OTCS\_HOME%/module/
amcontentscript\_X\_Y\_Z/
license/EULA
Accepting the End User Agreement is mandatory to proceed with the installation. Select “Next” when ready. 		EULA License Agreement
Script console is unselected by default because it is not a Content Server module. A standard Module Suite installation does not require this component to be installed.

More information regarding Script Console can be found here

Select “Next” when ready. 		Components selection
The installer will prompt you for the location where Content Server is installed. Browse to your OTCS_HOME and select “Next” when ready to start the installation. Installing
Follow the installation steps for each component to be installed. Welcome

The installer will automatically attempt to load a few libraries from Content Server.
In case of failure, a warning message could appear during this phase of the installation. In such case, the operation must be performed manually

Automatic import of Content Server dependencies
Module Suite Extension Packages
Select “Next” when ready.
Acceptance of the end-user license agreement is mandatory.
Upon installation, a copy of the agreement will be available in: %OTCS\_HOME%/module/
amcontentscript\_X\_Y\_Z/
license/EULA
Accepting the End User Agreement is mandatory to proceed with the installation. Select “Next” when ready. 		EULA License Agreement
Select all of the extension components that are to be installed
Select “Install” when ready.
Installation of the following extensions packages:
  • SAP
  • Zoho
  • Rendition

require additional configurations not covered by this guide. Deselect the corresponding checkboxes upon the installation or contact the AnswerModules support for assistance.
The installer will prompt you for the location where Content Server is installed. Browse to your OTCS_HOME and select “Next” when ready to start the installation. Installing
The unpacking of the module is complete.
Select “Finish” and return to the installation checklist to finalize the module setup. 		Complete

  • Install Content Server Modules

  • Login as Administrator and access the Module administration panel

  • Select “Install Modules”

  • From the available modules, select “AnswerModules Content Script 2.4.0”

  • Follow the installation steps and stop Content Server when prompted.

If an earlier version of Content Script module was installed, and you are performing an upgrade, it is mandatory once the upgrade is completed to check for the presence of the previous module version in %OTCS_HOME%/module. In the eventuality, the previous version of the module has not been removed automatically, stop Content Server service and remove it manually. The Content Server will fail to start if two versions of the Content Script module are present at the same time.

What to do if the installer raises the error: "Unable to automatically extract..."

Some Content Script extension packages require two Java libraries that are specific to the target Content Server environment and are not distributed with the module.

The required library files are:

  • csapi.jar
  • service-api-10.X.XX.jar

and can be found in the web app located in:

  • %OTCS_HOME%\webservices\java\webapps\cws.war (on CS 16.X)
  • %OTCS_HOME%\webservices\java\webapps\cws.war (on CS 10.5.X)
  • %OTCS_HOME%\webservices\java\webapps\les-services.war (on CS 10.0)

To retrieve the files:

  • copy the file named XXX.war to a temporary folder
  • rename the file XXX.war in XXX.
  • extract the zip archive contents locate the files in the WEB-INF/lib folder

Once the files have been located, copy them to the folder:

%OTCS_HOME\staging\anscontentscript_x_y_z\amlib

  • Post installation checks:

    Verify that the following optimization for the Java Server JVM has been added in opentext.ini

    Up to version 10.5 if the embedded JVM is JRE 1.7 : 

    JavaVMOption\_4=-XX:MaxPermSize=256m
JavaVMOption\_5=-Xmx2048m
JavaVMOption\_6=-Xms128m
JavaVMOption\_7=-XX:PermSize=256m
JavaVMOption\_8=-XX:+CMSClassUnloadingEnabled
JavaVMOption\_9=-XX:+UseConcMarkSweepGC
JavaVMOption\_10=-Dfile.encoding=UTF-8
JavaVMOption\_11=-Dlog4j.ignoreTCL=true

    Since version 16 or with version 10.5 if you upgraded the embedded JVM to JRE 1.8: 

    JavaVMOption\_4=-Xmx2048m
JavaVMOption\_5=-Xms128m
JavaVMOption\_6=-XX:+CMSClassUnloadingEnabled
JavaVMOption\_7=-XX:+UseConcMarkSweepGC
JavaVMOption\_8=-Dfile.encoding=UTF-8
JavaVMOption\_9=-Dlog4j.ignoreTCL=true

  • From the Administration Home, select AnswerModules Administration > Base Configuration, then enter the activation License in order to activate the product. License shall be entered in the amcs.core.license property

Since version 1.7.0, if the installation is performed on a multi-server architecture, the License Key must be made available on every single machine. License Key information is stored in the Content Script module anscontentscript.ini file.

In order to do so, there are two alternative options:

  • Edit the .ini file manually on each machine, adding the licensing information.
  • From the Administrative pages of each machine, perform the “save Base Configuration” operation.

Installation complete

The Content Script initial setup is complete