Oracle Content Server Providers

Managing System Settings 4-61

4.5.1 About Providers

A provider is an Application Programming Interface API that establishes connection between the Oracle Content Server instance and outside entities. These entities can be: ■ Oracle WebLogic Server ■ LDAP servers ■ databases ■ server sockets ■ file store system ■ Inbound Refinery

4.5.1.1 Oracle Content Server Providers

By default, an Oracle Content Server instance has three system providers: ■ SystemDatabase: The system database. ■ SystemServerSocket: A server socket that listens for browser requests. ■ DefaultFileStore: A file store system. In addition, you can create the following types of providers: ■ Outgoing : A connection initiated to an outside entity. You can use this type to communicate between Oracle Content Server instances. If you want to use SSL with an outgoing provider, see details in Section 4.5.1.3, Security Providers. ■ Database : An information repository server that provides an API for connecting and communicating with it. This retrieves information and enables information to be changed in the database. Examples of this type are system databases. ■ Incoming : A connection initiated from an outside entity like a browser or client application. The provider listens on a specified port to be aware of incoming connections. If you want to use SSL with an incoming provider, see details in Section 4.5.1.3, Security Providers. ■ Preview : An outgoing provider connection to Oracle Content Publisher, for use with the optional HTML Preview feature. ■ LDAP : A connection initiated to an LDAP Lightweight Directory Access Protocol server for managing external user access to the Oracle Content Server instance. This type of provider is supported by the ActiveDirectoryLdap component, which is installed disabled by default during Oracle Content Server installation. As of 11g Release 1 11.1.1 its functionality is mostly superseded by JpsUserProvider, in particular for nested group support. ■ HTTP: A connection that allows communication between Oracle Content Server instances using the HTTP protocol. This type of provider requires the Proxy Credentials Extension component, which is installed enabled by default during Oracle Content Server installation. ■ JpsUserProvider : A connection to an Oracle WebLogic Server instance. This provider uses Java Platform Security JPS to perform user authentication, user authorization, and retrieval of user metadata through an Oracle WebLogic Server instance. This type of provider is supported by the JpsUserProvider component, which is installed enabled by default with the Oracle Content Server instance. 4-62 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server

4.5.1.2 Choosing an Appropriate Provider