The Content Gateway is an enterprise integration component that acts as a secure and effective medium for end users to access corporate content. The Content Gateway settings page is used to configure the Content Gateway component.

  • Current Setting – Select whether to Inherit or Override the displayed settings. Inherit means use the settings of the current organization group's parent OG, while Override enables the settings for editing so you can modify the current OG's settings directly.
Settings Description
Enable the Content Gateway Set Enable the Content Gateway to Enabled. You might need to select Override to unlock Content Gateway settings.
Add Select Add to begin configuring the Content Gateway. You must choose the Installation Type, enter the Content Configuration details and enable the Content SSL Certificate settings.
Installation Type Select the Operating System for the Content Gateway server.
Content Configuration
  • Configuration Type - Select either Basic or Relay. Basic is the endpoint configuration with no relay component. Relay is the Endpoint configuration with a relay component.
  • Name- Provide a unique name used to select this Content Gateway instance when attaching it to a Content Repository, Repository Template, or RFS Node.
  • Content Gateway Relay Address - If implementing a relay configuration, enter the URL used to access the Content Gateway Relay from the Internet.
  • Content Gateway Relay Port- If implementing a relay configuration, enter the relay server port.
  • Content Gateway Endpoint Address - Enter the host name of the Content Gateway endpoint. The Public SSL certificate bound on the configured port must be valid for this entry.
  • Content Gateway Endpoint Port - Enter the endpoint server port.
Content SSL Certificate
  • Public SSL Certificate (required for Linux requirements) - If necessary, upload a PKCS12 (.pfx) certificate file with a full chain for the Content Gateway Installer to bind to the port. The full chain includes a password, server certificate, intermediates, root certificate, and a private key. Requirements vary by platform and SSL configuration.
  • Ignore SSL Errors (not recommended) - If using a self-signed certificate, consider enabling this feature. If enabled, Content Gateway ignores certificate trust errors and certificate name mismatches.