Edit online

Deploying Content Fusion Enterprise on Ubuntu, RHEL, CentOS

If you want to use other platforms other than VMware vSphere (for example, Google Cloud Platform, Microsoft Azure or Microsoft Hyper-V), you can use an installation kit that has been built to run on Ubuntu 18.04, Red Hat Enterprise Linux (RHEL) 7, or CentOS 7. This topic contains information for the server administrator about how to install and configure the Oxygen Content Fusion Enterprise Server solution on those platforms.

Prerequisites

An Enterprise server solution requires the following:

One of the following fresh Linux distributions:
- Ubuntu 20.04 VM (https://cloud-images.ubuntu.com/)
- Red Hat Enterprise Linux 7 (https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux)
- CentOS 7 (https://www.centos.org/download/)
Root access to the machine
container-selinux version 2.95-2.el7_6 or higher (for CentOS 7 and Redhat 7.6)
Docker Engine Community Edition 20
Note: While Content Fusion might work with newer Docker versions, they are not officially supported.
iptables needs to be installed
8 GB of memory on the server (see Memory Limits).
2 CPUs

Firewall Notes

The Content Fusion Enterprise Virtual Machine should have the following ports accessible:

80, 443 - For HTTP/HTTPS access to the main application.
9080 - For access to the administration page (you may want to restrict access to only have this page available to certain computers).
22 - For SSH access.

Installing the Software

To install the Oxygen Content Fusion Enterprise Server solution on your machine::

Go to the Download page.
Go to the Other Platforms tab and download the Oxygen Content Fusion Enterprise Server installation kit.
Run the installer (the installation requires root privileges):
```
sudo bash Oxygen_Content_Fusion_Enterprise.sh
```
Follow the on-screen instructions.
Note: The installation log can be found in the content-fusion-install.log file, in the current directory.

Initial Oxygen Content Fusion Configuration

To configure Oxygen Content Fusion on the initial start of the VM, use the following procedure:

Access the administration web interface of Oxygen Content Fusion at: https://<server-address>:9080.
Note: By default, Oxygen Content Fusion uses a self-signed certificate, so the browser will display a security warning. Continue (for example, if you are using Edge, click Details and then Go on to the webpage).
Log in using the following credentials:
- user = fusion
- password = oxygenxml
Change the password.
In the General tab, configure the Domain Name of the server. To properly configure the server, you should associate a domain name for this server in your DNS.
You can also use the server IP address instead of the domain name. In this case, the server will run with several limitations:
- The e-mail messages generated by the server are more likely to be considered as SPAM.
- HTTPS support cannot be enabled.
Note: By default, the Domain Name is populated with one of the IP addresses associated with the server. It is recommended that you check this IP address to make sure it can be accessed by your end-users.
In the License tab:
- If you already have a license key, choose the Already have a license key option, paste your license key in the text field and click Activate.
- Otherwise, choose the Request a trial license key option and complete the request form.

Configuring Oxygen XML Editor/Author to Connect to Your Enterprise Server

All Content Authors in your organization that will be uploading tasks will need to configure Oxygen XML Editor/Author to connect to your Enterprise server. You need to provide them with your Enterprise server URL and then each of them will need to follow the procedure found in: Configuring Your Enterprise Server Address. Alternatively, if you want to impose the server URL for all Content Authors so that they do not need to do any manual configuration, you can create a properties file to impose the Enterprise server address.