A.38 Content Server Connection Content Server Settings Page
Specify the details of the Content Server repository to connect to on the Content Server Settings page. It is accessed by clicking Next on the Content Server Connection Basic Information Page when creating a new connection, or directly using the navigation train on any repository connection page for an existing connection.
The following table describes the elements available on the page.
Name of the repository proxy. The repository proxy is a user created in Content Server when Oracle I/PM is installed. The proxy is given rights to Content Server that allows it to fulfill requests to Content Server on behalf of I/PM users who may not have the necessary rights in Content Server to perform the required tasks. For example, a user may have the rights in I/PM to create an application and add metadata fields, but may not have the rights in Content Server to create metadata fields to support the application. When the application is created, the request to Content Server to create the necessary metadata fields is made by the repository proxy. By default, the repository proxy name is fmwadmin. This field is required.
Enable connection using Secure Socket Layer (SSL). Additional steps must be taken to configure SSL on Content Server and ensure proper credentials. For detailed information, see the full Oracle Fusion Middleware Administrator's Guide for Oracle Imaging and Process Management.
Specifies the host name or names used for the connection. If the BPEL server is a single instance, it is the name or IP of the server. If the server is operating within a cluster, this parameter value can be a comma-separated list of machine names or IP addresses of servers in the cluster, or it can be the cluster name for the cluster. The default and most common value is “localhost” which connects I/PM to the Content Server sharing the computer.
Specifies the Content Server's remote API (RIDC) connection port. If the SSL option is checked, then the port provided must be the SSL listening port for the server.
In clustered configurations it is necessary to provide the connection information to each of the Content Servers in the cluster. The Machine Name and Server Port values are the same as described above.