Edit online

This topic contains information for the server administrator about how to install and configure an Oxygen Content Fusion Enterprise Server using VMware vSphere.


An Enterprise server solution requires the following prerequisites:

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.

Downloading the Oxygen Content Fusion Enterprise Virtual Machine Software

To use your own server with VMware vSpere, you need to go to the Download page, and in the VMware tab, download the virtual machine software package. The download package includes an OVA file that defines the virtual machine.

Importing the Oxygen Content Fusion Virtual Machine Software

To import the Oxygen Content Fusion Enterprise virtual machine software in VMware vSphere:
  1. Start VMware vSphere.
  2. Select File / Deploy OVF Template and choose the OVA file.
  3. Select the Power on after deployment option in the final step.
  4. After powering on the virtual machine, click Launch Virtual Machine Console.

Initial Command Line/SSH Access Configuration

To configure the command-line/SSH access to the VM, use the following procedure:
  1. On the first start of the server, the VM console will display the IP address (you will need this), and the SSH access administrator user name and password (these will be changed). The fingerprint of the HTTPS self-signed certificate is also displayed. If you do not see this information, press Enter and it will be displayed.
  2. Log in to the machine using the credentials displayed in step 1. You can do this either directly in the virtual machine console or by using SSH.
  3. After you log in, you will be prompted to change the default password for the administration account. This password can be used to log in to the VM using SSH or the VM console.
  4. Exit the console by typing exit.

Initial Oxygen Content Fusion Configuration

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

  1. 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 or Internet Explorer, click Details and then Go on to the webpage).
  2. Login using the following credentials:
    • user = fusion
    • password = oxygenxml
  3. Change the password.
  4. 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.
  5. 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 press 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.