Add a Custom Connection to Content Server

You can use a custom connection for Oracle WebCenter Content server to deliver files from Publisher to Oracle WebCenter Content server.

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.

FA_UCM_PROVISIONED, a provisioned connection to Oracle WebCenter Content server, uses a provisioned FUSION_APPS_OBIA_BIEE_APPID user to connect to Oracle WebCenter Content server with security groups and accounts to support the most common use cases. You can't delete or modify the FA_UCM_PROVISIONED connection, but you can disable the connection.

Configure a custom connection to Oracle WebCenter Content server using user credentials other than FUSION_APPS_OBIA_BIEE_APPID, if you want to access Oracle WebCenter Content server or to deliver PGP encrypted files from Publisher.

The custom connection to Oracle WebCenter Content server must use the same Uniform Resource Identifier (URI) as the provisioned connection, but should have its own user name and password.

1. In the Publisher Administration page, navigate to the Content Server tab in the Delivery section, and click Add Server.
2. Enter the same URI used by the provisioned FA_UCM_PROVISIONED Oracle WebCenter Content server.
   Every time you upgrade, verify the URI of the provisioned FA_UCM_PROVISIONED Content Server, and make sure the URI of the custom connection is similar to the URI of the provisioned FA_UCM_PROVISIONED Content Server.
3. Enter the server name, user name, and password.
4. Leave Enable Custom Metadata deselected. Custom metadata isn't used.
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. Optional: Select Use Logged in user as Author to set the logged in user as the author of the report sent to the Content Server. If Use Logged in user as Author isn't selected, the reports sent to the Content Server contain the name of the report author.
7. In the Access Control section, deselect Public, if selected.
8. 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.
9. Click Test Connection to ensure that you can connect to Oracle WebCenter Content server.
10. Click Apply.