Assumptions and Prerequisites

PTC Arbortext Content Delivery Deployment > Planning Your Deployment > Assumptions and Prerequisites

• It is recommended to set up and configure two internal LDAPs, one for Publisher and one for all the Viewers. If you must use a single LDAP, follow the Using a Single Windchill Directory Server for Publisher and Viewer steps to restrict the access to the Publisher applications (Task Manager and configurator).

• You must have the license server installed for PTC Arbortext Content Delivery to work.

• The configuration definitions specified in the configurator always override the definitions specified during the PTC Arbortext Content Delivery setup process. The configurations specified in the Viewers and Core setup processes do not synchronize and reflect in the configurator.

• All Viewer and Core setup components must refer to the same configurator file path located in the shared folder location, accessible to all the entities. Ensure that this link is accessible and not blocked by a firewall.

• PTC recommends that you keep PTC Arbortext Content Delivery installation directory including the Data directory out of any real time scanning antivirus and malware tools. Also this exclusion is applicable when you start PTC Arbortext Content Delivery either by running the startACD.bat script or by starting the services, assuming that the anti-virus provides that option.

• The standalone license server and standalone viewer should not be installed on same machine.

• To install PTC Arbortext Content Delivery, you must install JAVA SDK 1.8 (recommended 1.8.0_144 or higher). Extracted Java is not supported.

• If you plan to deploy a cluster environment with two internal LDAPs, one for publisher and one for the runtime viewers, PTC recommends that you must use a separate MongoDB (or separate database name) for the publisher and the runtime viewers.

• Internet connection is necessary to have the Performance Advisor configured for PTC Arbortext Content Delivery.

• For all the features to work properly, you must generate a new license file when upgrading to PTC Arbortext Content Delivery 7.1.4.0 release.

• The CreoView plugin is used as default for displaying graphics while using the Internet Explorer browser.

Linux Considerations

Installed Packages

• On Linux systems you must install the following package: glibc2.17 yum install glibc2.17

If you are using RHEL 7+ and the new CentOS versions, it will have a preinstalled package.

• The xterm utility must be installed prior to installing PTC Arbortext Content Delivery.

Pre-requisite

Before installing PTC Arbortext Content Delivery, set the following ulimit settings using root access:

vi /etc/sysctl.confset fs.file-max to 68157440vi /etc/security/limits.conf* soft nofile 65536* hard nofile 65536

Enabling CoreServer Crash Dump on Linux

Before installing PTC Arbortext Content Delivery, enable the CoreServer dump as follows:

1. In the coreCMIServer.sh and coreServer.sh files, set ulimit -c unlimited as follows:

ENIGMA_WORK_HOME=$ENIGMA_WORK_HOME/System/work/core/instance.ptc.com
export ENIGMA_WORK_HOME
ulimit -c unlimited

2. Browse to the /etc/abrt/abrt-action-save-package-data.conf file, and add or set ProcessUnpackaged = yes

3. Open the /etc/abrt/abrt.conf file and set the following parameters:

◦ DumpLocation= <path>For expample, DumpLocation = /appl/corefiles/

◦ MaxCrashReportsSize parameter to unlimit the core dump size.For example, MaxCrashReportsSize = 0

4. Provide appropriate rights to the DumpLocation directory.For example, if the corefiles directory is owned by the ACD admin user, the ACD admin user must have write access for the DumpLocation directory. If write access is not available, dumps are not generated in the directory.

5. Test the core dump configuration using the kill -3 PID command and check that core dumps are generated in the /appl/corefiles folder.

Setting JBOSS Heap

You can set the JBOSS heap depending on the size of the data. Set the JBOSS heap size in the deployment Configurator. For more information, see Editing Properties of the Configurator Entities

Prerequisite for Windows 2016 R2 Server

After you install monolithic, Publisher, or Viewer, you must set additional permissions for PTC Arbortext Content Delivery installation directory.

1. Right-click this directory and open the Properties dialog box.

2. In the Security tab, grant full permissions to the Users group.

Apply the same setting for the shared DATA directory in case of Cluster environment.

Dynamic Data (MongoDB) Database Prerequisites for Windows Installation

• To install a dynamic data database as a service on Windows, you must have administrator privileges, so that you can run the PTC Arbortext Content Delivery installer as administrator.

• As MongoDB is an input-output intensive database, it is recommended that you install it in a separate directory from the PTC Arbortext Content Delivery installation directory with read-write permissions and sufficient storage space.

• The latest Visual C++ Redistributable must be installed. Many of MongoDB modules are written in C++, hence they require the C++ libraries. Each one of these modules comes in debug and release versions. Each of these versions have various threaded and non-threaded flavors. Each flavor has several bug fix releases.

• PTC recommends that a hard disk space of 500 MB be available for MongoDB data.

Windows Server 2016

• Minimum requirement to install is latest Visual C++ Redistributable for Visual Studio (2017).

• Install all the latest windows patch updates.

Windows 10 for Offline Installation

Download and install the latest available Visual C++ Redistributable for Visual Studio. Tested and working with Visual C++ Redistributable 2017.

Java Compatibility

Per the new Oracle policy, applications cannot bundle Java software (including JRE) with their product. This policy change has resulted in removal of bundled Java from PTC Arbortext Content Delivery. A compatible Java version must be installed prior to the PTC Arbortext Content Delivery install, otherwise the installation will result in an error as it is not able to find proper Java path. PTC recommends that when you install PTC Arbortext Content Delivery, you provide a valid Java or JRE path (Java home) in the installer, without any spaces in it. If the Java version is not supported, the installation fails.

You can also subsequently update the Java home using the Configurator.

After installation and during JBoss start up, PTC Arbortext Content Delivery searches a for valid Java version. If it is not available, the server fails due to an unsupported version error.

Supported Java version: PTC Arbortext Content Delivery is based on Java 8 (1.8.0_144 and above).

Troubleshooting: If you specify an incorrect or unsupported Java home path, JBoss (or Application server) does not boot after the next server restart. You can see the error logs in SW/Log/System/Log/jBossConsole.

The installed Java version must be 1.8.0_144 or higher while installing PTC Arbortext Content Delivery on Windows Server 2016.

Removing Restrictions for Non-Supported Platform

To install PTC Arbortext Content Delivery on non-supported platforms, perform the following actions:

• For Windows platform, set the Windows system variable for the following parameter:SCI_RELAX_PLATFORM=1

• For Linux platform, run following command from the Terminal:export SCI_RELAX_PLATFORM=1

PTC does not recommend the use of non-supported Operating Systems (OS) platforms. If a non-supported OS platform is used, PTC is not responsible to address any issues observed.