Add a Content Server

You can deliver documents to Oracle WebCenter Content.

When you use a content server as a delivery destination:

• At runtime, the report consumer can tag the report with Security Group and Account metadata (if applicable) to ensure that the appropriate access rights are applied to the document when delivered.

Publisher communicates with Oracle WebCenter Content Server using the Remote Intradoc Client (RIDC). The connection protocols therefore follow the standards required by the RIDC. The protocols supported are:

• Intradoc: The Intradoc protocol communicates to the Content Server over the over the Intradoc socket port (typically 4444). This protocol requires a trusted connection between the client and Content Server and will not perform any password validation. Clients that use this protocol are expected to perform any required authentication themselves before making RIDC calls. The Intradoc communication can also be configured to run over SSL.

• HTTP and HTTPS: The HTTP protocol connection requires valid user name and password authentication credentials for each request. You supply the credentials to use for requests in the Publisher Administration page.

• JAX-WS: The JAX-WS protocol is supported only in Oracle WebCenter Content 11g with a properly configured Content Server instance and the RIDC client installed. JAX-WS is not supported outside this environment.

To set up a content server as a delivery destination:

1. From the Administration page, under Delivery, select Content Server, and then click Add Server.
2. Enter the Server Name, for example: contentserver01.
3. Enter the connection URI for your content server. The URI can take any of the following supported protocols:

   • HTTP/HTTPS — Specifies the URL to the Content Server CGI path.

     For example:

     • http://localhost:16200/cs/idcplg
     • https://localhost:16200/cs/idcplg

   • Intradoc — The Intradoc protocol communicates to the content server over the Intradoc socket port (typically 4444). The IDC protocol also supports communication over SSL. For example:

     • idc://host:4444

     • idcs://host:4443

   • JAX-WS — Uses the JAX-WS protocol to connect to the content server.

     For example:

     • http://wlsserver:16200/idcnativews
4. Optional: Enter the user name and password of the content server.
5. Optional: To deliver PGP encrypted documents to the content server:
   1. From the PGP Key list, select the PGP keys you uploaded in Security Center.
      This step updates the filter command in the Filter Command field.
   2. To sign the encrypted document, select Sign Output.
      This step adds a -s parameter to the existing filter command in the Filter Command field.
   3. If you want to deliver PGP encrypted document in ASCII armored format, select ASCII Armored Output.
      This step adds a -a parameter to the existing filter command in the Filter Command field.
6. In the Access Control section, deselect Public.
7. From the Available Roles list, select one or more roles you want to provide access to the delivery channel, and click Move to add them to the Allowed Roles list.
8. Click Test Connection.
9. Click Apply.