Configuration Options
The following sections cover the end-to-end flow for setting up the deployment configurations:
• Monolithic
• Split
• Multi-site
 |
• WildFly is no longer bundled with Arbortext Content Delivery. For WildFly install or update, see the Adding WildFly to the Arbortext Content Delivery Installer section in the Assumptions and Prerequisites topic.
• PTC strongly recommends that you use either Split or Multi-site deployment configuration for your production environments. You must not use Monolithic configuration for production.
• In case of split and multi-site configuration, you must specify a valid host name for dynamic data (MongoDB) entity in the configurator. This is a required step in case of split and multi-site configurations, where host name for the Publisher can be localhost, but for dynamic data the host name cannot be localhost.
|
Installing on Multiple Machines (Solution Installation)
Several components that make up a Arbortext Content Delivery solution are commonly installed on separate machines in a production environment. Some of those components require other components for a multi-machine installation to work. The following components can be installed on separate machines from the Arbortext Content Delivery solution:
|
Order of Installation
|
Component
|
Installation Considerations
|
|---|---|---|
|
1st
|
LDAP Server
|
None
|
|
2nd
|
Oracle
|
None
|
|
3rd
|
Arbortext Content Delivery Publisher
|
If installing with Viewer, Publisher should be installed first.
|
Prerequisites
In case of split, multi-site, and cluster configurations, (along with Disconnected) :
• For Windows:
1. Go to Registry (run > regedit).
2. Go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters folder.
3. In Parameters, add the DisabledComponents parameter and its DWORD value=ff.
4. Restart the machine.
