Siebel Installation Guide for Microsoft Windows > Configuring Siebel Business Applications Server Modules > Configuring the Siebel Enterprise Cache >

Creating a Siebel Enterprise Cache Server Profile


This procedure describes how to configure a Siebel Enterprise Cache Server profile. You can create multiple profiles, but you can deploy only one instance of Siebel Enterprise Cache Server in your Siebel deployment. This task is part of Configuring the Siebel Enterprise Cache.

Related Topics

Running the Siebel Management Console

Deploying the Siebel Enterprise Cache Server

To create a Siebel Enterprise Cache Server profile

  1. Run the Siebel Management Console, as described in Starting the Siebel Management Console.
  2. Click Profiles in the navigation menu in the left panel, then click Enterprise Cache Server.

    Existing Siebel Enterprise Cache Server profiles are listed, if any.

  3. Click the plus sign (+) at the top of the overview section to add a new Siebel Enterprise Cache Server profile, or click the Clone button to clone an existing profile.
  4. Specify a name for the profile.
  5. Specify additional settings, as shown in Table 9.
  6. When you have specified all applicable settings, click Submit to save your changes to the profile.

Configuration Settings for a Siebel Enterprise Cache Server Profile

Table 9 describes the settings that are requested in the Siebel Management Console for configuring a new Siebel Enterprise Cache Server profile or modifying an existing Siebel Enterprise Cache Server profile. Required fields display an asterisk (*) next to the field label. For most of the options, pointing to the option displays tooltip text that provides a brief description of the field. Clicking the large plus sign (+) to the right of some options adds a new instance of a configurable item, which is represented in the second column using italics.

Most of the Siebel Enterprise Cache Server settings that you specify here correspond to Oracle Coherence settings. For more information about the Oracle Coherence settings, see Oracle Coherence documentation.

NOTE:  Siebel CRM provides existing configuration settings for Siebel Enterprise Cache Server and Siebel Enterprise Cache Client that work with Siebel Constraint Engine. See also Configuring the Siebel Constraint Engine.

NOTE:  You can click the Advanced button next to the Tango Coherence Override or Cache Configuration heading to edit the XML directly. You can use this as an alternative to specifying values for all of the individual fields in these sections.

Table 9. Settings for Configuring a Siebel Enterprise Cache Server Profile
Setting in Siebel Management Console
Section (Under Create Profile)
Comment or Description

Log Level

(Not applicable)

Specify the log level. Select one of the following options: Fatal, Error, Warning, Debug, Trace, Information, All

Security Profile

(Not applicable)

Specify the security profile that the Siebel Enterprise Cache Server uses to secure any cache operations.

Setup Coherence Server SSL

Tango Coherence Override > Coherence Server SSL

Check this option to enable SSL security settings for Siebel Enterprise Cache Server.

NOTE:  You must configure SSL security settings the same for both Siebel Enterprise Cache Server and Siebel Enterprise Cache Client.

Key Store

Tango Coherence Override > Coherence Server SSL

This option appears if you checked the option Setup Coherence Server SSL.

Provide the location of the keystore file.

Key Store Password

Tango Coherence Override > Coherence Server SSL

This option appears if you checked the option Setup Coherence Server SSL.

Provide the private key password for the keystore file.

Key Store Type

Tango Coherence Override > Coherence Server SSL

This option appears if you checked the option Setup Coherence Server SSL.

Specify the type of keystore instance you are using, such as a JKS file.

Cache Server TLS Port

Tango Coherence Override > Coherence Server SSL

Specify the TLS port that will be used to access the cache via socket APIs.

Cluster Name

Tango Coherence Override

Provide the Siebel Enterprise Cache Server cluster name, such as SiebelEnterpriseCacheCluster.

Cache Name

Cache Configuration > Cache Scheme Map > Cache Name

Specify the name of this cache.

Scheme Name

Cache Configuration > Cache Scheme Map > Cache Name

Specify the scheme name for this cache.

Service Name

Cache Configuration > Proxy Scheme

Specifies the name of the service.

Maximum Thread Count

Cache Configuration > Proxy Scheme

Specifies the minimum number of daemon threads. Usage of daemon threads varies for different service types.

If the value is zero or negative, then the service does not use daemon threads and all relevant tasks are performed on the service thread.

Furthermore, if the value is negative, then tasks are performed on the caller's thread where possible.

Valid values are integers greater or equal to the Minimum Thread Count value.

Minimum Thread Count

Cache Configuration > Proxy Scheme

Specifies the minimum number of daemon threads. Usage of daemon threads varies for different service types.

If the value is zero or negative, then the service does not use daemon threads and all relevant tasks are performed on the service thread.

Furthermore, if the value is negative, then tasks are performed on the caller's thread where possible.

Valid values are integers less than or equal to the Maximum Thread Count value.

Cache Server Host

Cache Configuration > Proxy Scheme

Provide the Siebel Enterprise Cache Server host name.

Port

Cache Configuration > Proxy Scheme

Provide the Siebel Enterprise Cache Server service port.

Enable Cache Service Proxy

Cache Configuration > Proxy Scheme

Check this option to enable cache service proxy. If this option is disabled, then clients will not be able to access any proxied caches.

Auto Start Extended Service

Cache Configuration > Proxy Scheme

Check this option to automatically start this service at a cluster node.

Distributed Scheme

Cache Configuration > Scheme Configuration > Distributed Scheme

Specify the scheme name for a distributed scheme.

Type

Cache Configuration > Scheme Configuration > Distributed Scheme

Specify the type of distributed scheme. Specify one of the following:

  • Reference Scheme
  • Backup Scheme

Distributed Reference Scheme

Cache Configuration > Scheme Configuration > Distributed Scheme

This option appears if you selected Reference Scheme as the distributed scheme type.

Specify the scheme name that is configured in the distributed scheme section. It should be different from the scheme name provided in the Scheme Name field.

Service Name

Cache Configuration > Scheme Configuration > Distributed Scheme

This option appears if you selected Backup Scheme as the distributed scheme type.

Specify the name of the service that will manage caches created from this scheme.

Auto Start Distributed Service

Cache Configuration > Scheme Configuration > Distributed Scheme

This option appears if you selected Backup Scheme as the distributed scheme type.

Check this option to automatically start the cache services associated with this cache scheme at a cluster node.

Backup Scheme Configuration

Cache Configuration > Scheme Configuration > Distributed Scheme

Specify the scheme name already created in the Local Scheme section.

Local Scheme Name

Cache Configuration > Local Scheme Configuration > Local Scheme Name

Specify the scheme name of the local scheme.

Eviction Policy

Cache Configuration > Local Scheme Configuration > Local Scheme Name

Specify the type of eviction policy to use. Specify one of the following:

  • Least Recently Used (LRU). Chooses which objects to evict based on how recently they were last used, evicting those that were not accessed for the longest period first.
  • Least Frequently Used (LFU). Chooses which objects to evict based on how often they are being accessed, evicting those that are accessed least frequently first.
  • Hybrid. Chooses which objects to evict based on the combination (weighted score) of how often and how recently they were accessed, evicting those that are accessed least frequently and those that were not accessed for the longest period first.

Maximum Cache Size

Cache Configuration > Local Scheme Configuration > Local Scheme Name

Specify the maximum number of units that can be placed in the cache before pruning occurs.

Cache Unit Calculator

Cache Configuration > Local Scheme Configuration > Local Scheme Name

Specify the type of cache unit calculator. The cache unit calculator determines the cost, in units, of a given object. Specify one of the following:

  • Binary
  • Fixed

Cache Unit Factor

Cache Configuration > Local Scheme Configuration > Local Scheme Name

Specifies the factor by which the units (low units and high units) are adjusted. Using a cache unit calculator, for example, the factor of 1048576 could be used to count megabytes instead of bytes.

Cache Expiry

Cache Configuration > Local Scheme Configuration > Local Scheme Name

Specifies the amount of time from the last update that entries are kept by the cache before being marked as expired.

Siebel Installation Guide for Microsoft Windows Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices.