|Oracle® Universal Content Management
10g Release 3 (10.1.3.3.3)
From this page you can update the configuration of an existing adapter. These settings are stored in the adapter configuration file (adapterconfig.xml).
These properties can be updated by selecting the appropriate tabs:
These properties can be set:
Name: The name of the adapter (e.g., myadapter).
Adapter Type: Type of communication transport.
Socket: Using a socket connection opens communication directly to your content server instance (typically port 4444). This implied that you have established a trust relationship between your client machine and the content server.
Web: Using Web Authentication, every call to the content server will require credentials (all communication with the content server must be authenticated). This allows CIS to call services on the content server without opening up port 4444. This also means that you can only perform an operation in content server with the authenticated ID; since there is no trust relationship to perform an operation as sysadmin you must have the credentials for the sysadmin user.
Host: The name or IP address of your content server instance.
Port: The content server port number (e.g., 4444).
Use Persistent Connections: Enable this checkbox if you want to keep the connection alive after a request is completed. If you enable persistent connections, you also need to configure them on your content server instance (via the providers interface). Refer to the Oracle Content Server administration documentation for more information.
Connection Timeout: When using persistent connections, this value is the maximum amount of time the connection will wait for response. Default is 20000 (in milliseconds).
Version: The content server version. Choose your version from the drop-down list. If your content server is version 7.6.x or 7.5.x you must make the appropriate selection when configuring your adapter.
Resource Pool Initial Size: The initial size of the adapter connection resource pool. Default is 10.
Resource Pool Initial Size: The maximum size of the adapter connection resource pool. Default is 20.
These options (Default, Web Transfer, and Mapped Vault) define the method for transferring files from the content server. In most instances the default option may be used. However, enabling mapped vault will result in a performance improvement.
Enables the web transfer method for transferring files from the content server. This method retrieve files via the content server web server.
Web Vault Prefix: The prefix for the web address (usually http://<servername>:<port>) to the content server vault directory.
Web Layout Prefix: The prefix for the web address (usually http://<servername>:<port>) to the content server weblayout directory.
Web Vault User Name: The username to use when retrieving files.
Web Vault Password: The password to use when retrieving files.
Enables the mapped vault method for transferring files from the content server (will improve performance, if used).
Mapped Server Vault: The path to the content server vault directory as seen from the application server. This needs to be accessible from the application server.
Mapped Server Weblayout: The path to the content server weblayout directory as seen from the application server. This needs to be accessible from the application server.
Content Server Vault: The path to the content server vault directory as seen from the content server.
The application server needs to have WRITE privileges to the Mapped Server Vault directory.
CIS supports Secure Socket Layer (SSL) communication with the content server. You must have completed the preliminary setup before proceeding:
You must have a valid KeyStore / TrustManager with signed trusted certificates on both the client (CIS) and server (content server).
You must have installed the Security Providers component and configured content server for SSL communication.
Enter the appropriate values (these will vary, depending on your configuration):
Enable SSL: Check this box to enable SSL communication for this adapter.
Keystore File Path: The absolute path to client-side keystore.
For example: /tmp/ssl/client_keystore
Keystore Alias: The alias to use when accessing keystore.
Keystore Password: The password used to access keystore.
Keystore Alias Password: The password to use when accessing keystore with specified alias.
Trust Manager File Path: The absolute path to the client-side trust manager.
Trust Manager Password: The password used to access the trust manager.
Encryption Algorithm: The encryption algorithm to use (e.g., sunx509).
These properties can be set:
Cache Enabled: Check this box to enable caching for this adapter.
User Cache Capacity: The capacity of the cache for each user. These are the cached items or responses from the server. Default is 1000.
Global Cache Capacity: The capacity of the global cache. These are the cached items or responses from the server. Default is 1000.
Click the View/Modify command cache policies link to modify command cache policies.
These properties can be set:
Enabled: Check this box to enable to enable the event polling system.
Polling Interval: The amount of time between content server cache update queries (in milliseconds).
User Authentication Type: The type of authentication to use for background process.
Basic: Perform user authentication via HTTP Basic User Authentication.
NTLM: Perform user authentication via the NTLM protocol. This protocol is supported by all versions of the Internet Explorer and is mainly useful for intranets. Depending on your preferences setting this will supply your windows logon credentials to the web server when the server asks for NTLM authentication. This saves the user to type in their password again.
NTLM authentication works only when KeepAlive is on.