Adding a Content Server

You can deliver documents generated by BI Publisher to your Oracle WebContent Server.

BI Publisher's integration with the content server provides the following features:

  • At run time, 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.

    See Adding Destinations in User's Guide for Oracle Business Intelligence Publisher.

  • For documents that require specific custom metadata fields (such as invoice number, customer name, order date), BI Publisher enables the report author to map the custom metadata fields defined in Content Profile Rule Sets to data fields in the data model.

    See Adding Custom Metadata for Oracle WebCenter Content Server in Data Modeling Guide for Oracle Business Intelligence Publisher.

BI 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 BI 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.

    For more information about these protocols, see Using RIDC to Access Content Server in Developing with Oracle WebCenter Content.


Description of GUID-E979E1F6-9663-407C-9155-AAA05C558A1B-default.gif follows
Description of the illustration GUID-E979E1F6-9663-407C-9155-AAA05C558A1B-default.gif

To set up a connection to a content server as a delivery destination:

  1. From the Administration page, under Delivery, click Content Server to display the list of servers that have been added. 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. To enable the inclusion of custom metadata with your report documents delivered to the content server, select the Enable Custom Metadata check box. This option must be selected to enable the custom metadata options in the Data Model Editor and the Scheduler.