Oracle® Real-Time Decisions Installation and Administration Guide Version 3.0.0.1 Part Number E13856-02 |
|
|
View PDF |
Oracle RTD uses the J2EE industry standard Java Management Extensions (JMX) to configure and monitor the operation of Oracle RTD. You can use JConsole, a JMX management tool that comes with Java Development Kit 1.5.0.8+ or 1.6, to manage Oracle RTD. Third-party JMX implementations may also be used to manage Oracle RTD. This document assumes you are using JConsole.
Note:
Some of the management properties available through JConsole can also be set as system properties. For details, see Section 15.9, "System Properties."JMX MBeans manage various aspects of Oracle RTD, including logging and Inline Service configuration. They can also be used to assign Oracle RTD specific permissions to security roles and users. Security roles and users are both managed by the J2EE container.
Oracle RTD is comprised of three Services:
Decision Center Service: Supports the deployment of Inline Services by Decision Studio. It also provides a web interface, Decision Center, for displaying the structure and decisioning history of Inline Services..
Decision Service: Runs Inline Services and integrates to enterprise operational processes.
Learning Service: Maintains analytic, self-learning models that underlie Inline Services.
Deployments of Oracle RTD are often done across multiple servers as well as in clusters to enhance performance in high transaction environments. A relational database is used by each of these Services for retention of code, transactional data and configurations.
This chapter contains the following topics:
Section 15.3, "Oracle Real-Time Decisions Cluster-Level Management"
Section 15.4, "Oracle Real-Time Decisions Member-Level Management"
Section 15.5, "Oracle Real-Time Decisions Security Management"
The steps to access JConsole depend on which application server you are using.
This section contains the following topics:
To access JConsole for OC4J, Oracle Application Server, or WebLogic:
Run JDK_HOME
/bin/jconsole
.
For example:
C:\Program Files\Java\jdk1.5.0_08\bin\jconsole.exe
If you have more than one JDK on your computer, it does not matter which JDK_HOME
you use. You can run JConsole from any JDK.
Note:
If you are running JConsole on UNIX, you must first add JAVA_HOME/bin
to the beginning of the PATH
operating system environment variable.Click the Remote tab.
For Host, enter the name of the computer where Real-Time Decision Server is running.For Port, enter your JMX remote port number (for example, 12345
).For User Name and Password, enter the credentials you specified when you set up JConsole. See Section 3.9, "Setting Up JConsole Security for OC4J" and Section 5.14, "Setting Up JConsole Security for WebLogic" for more information.
To access JConsole for WebSphere:
On the computer where WebSphere is installed, run the batch script to start JConsole. See Section 4.12.2, "Setting Up a Batch File for JConsole" for more information.
Log in as the JConsole user you created when you set up JConsole (for example, jmx_admin
). See Section 4.12.3, "Creating a JConsole User" for more information.
Note:
When Oracle RTD is running on WebSphere, JConsole must be run on the same computer as the WebSphere server, by default. This requirement is due to WebSphere limitations.Oracle RTD MBeans can be accessed through the OracleRTD folder in the JConsole MBeans tab. These MBeans can be used to manage various aspects of Oracle RTD. Each MBean consists of attributes and operations that can be used for informational and administration purposes.
Attributes and operations at the SDCluster level are meant to manage cluster-level features. The organization of the MBeans is hierarchical. The attributes of SDCluster are:
Properties – SD Cluster Properties Configuration.
Members – Members of the cluster. Each Member is listed through this attribute. Member is used to manage local server level properties.
Security – Security allows management of various authentication attributes. Many of these are specific to one authentication type and will not appear for other authentication types.
InlineServiceManager – Manages deployed Inline Services.
DeploymentStates – Allows the setup and ordering of deployment states.
LearningService – Administers the Learning Service attributes.
BatchManager – Administers the Batrch Manager Service attributes.
Management at the cluster level is for items that impact the entire cluster of servers. Note that if you have only one server, there is still cluster-level management.
This section contains the following topics:
Section 15.3.1, "About OracleRTD > SDManagement > SDClusterPropertyManager"
Section 15.3.2, "About OracleRTD > SDClusterPropertyManager > Misc"
Section 15.3.3, "About OracleRTD > SDClusterPropertyManager > Cluster"
Section 15.3.4, "About OracleRTD > SDClusterPropertyManager > Deployment"
Section 15.3.5, "About OracleRTD > SDCluster > SDManagement"
The SDManagement > SDClusterPropertyManager MBean has the following attributes:
Attribute | Description |
---|---|
Cluster | Cluster configuration. |
Deployment | Configuration for deployment. |
Misc | Miscellaneous properties. |
The SDManagement > SDClusterPropertyManager MBean has the following operation:
java.lang.Void restoreDefault()
Restores the default installation settings to Oracle RTD. If this command is run on a cluster, then values are restored to cluster defaults.
The SDClusterPropertyManager > Misc MBean has the following attributes:
Attribute | Description |
---|---|
ArchivedModelCacheTimeToLive | Maximum time in seconds an archived model is preserved in memory. The cache of archived models is used by Discovery Explorer. |
ArchivedModelCatalogRefreshInterval | Refresh interval in seconds for a catalog of archived models. The catalog is used by Discovery Explorer. |
AutoFlushTimeout | Interval in seconds controlling auto flush of database write buffers. Fractional values are supported. |
DBOperationLogThresholdMilliSec | All database operations that take longer than the specified threshold are logged. |
DCOperationLogThresholdMilliSec | All decision center requests that take longer than the specified threshold are logged. |
DSEnforcesStrictSessionAffinity | When set to true, and DSManagesSessionAffinity is also true, the decision service instances assure that updates to the cluster's session key map are made transactionally, to avoid the possibility of two sessions existing on different hosts with common keys. When set to false, it is possible for sessions to exist on separate hosts with common keys if the initial requests arrive at the load balancer in close proximity. |
DSManagesSessionAffinity | Decision Service manages session affinity. When set to true, the decision service maintains a map of active session keys and, if necessary, will forward Integration Point requests to the cluster host owning the key's session. Should be disabled in single-host installations and in installations where session affinity is perfectly managed by the application server or external load balancer. |
DSSessionIdleTimeoutMillisec | Decision Service session idle timeout in milliseconds. |
DSStrictSessionAffinityConcurrency | How many concurrent DB requests can be outstanding, per Oracle RTD instance, to manage the strict Decision Service session directory. Keep this low for SQL Server to avoid DB-centric deadlocks. 0 means unlimited. |
DatabaseComponentCloseTimeoutSeconds | How long to wait for the database provider to close an individual component (for example, each BatchUpdater) before abandoning the effort. |
DatabaseShutdownTimeoutSeconds | How long to wait for the database provider to shutdown all its components before abandoning the effort. |
DecisionServiceAddress | Must be set for Decision Center to be able to test integration point requests from its Interactive Integration Map when Decision Center is not co-located with Decision Service. |
DisableBatchDBOperations | Boolean switch that controls batch database operations. |
IntegrationPointGuaranteed RequestTimeout | Guaranteed response time, in milliseconds, for Integration Point requests. (Service Level Guarantee). Zero means don't timeout Integration Point requests - suitable for debugging only. |
IntegrationPointMaxConcurrentJobs | The maximum number of concurrently executing Integration Point requests. This should normally be set to 0 , in which case the value is calculated as follows, where Math.ceil means "round up to the next higher integer:"
NumCPUs * Math.ceil(1/(1-DSRequestIOFactor)) + 5 |
IntegrationPointQueueSize | The maximum number of Integration Point requests that can wait to execute. If a request tries to exceed this number, the server terminates the request with a "Server Too Busy" error message. This setting should be less than or equal to the number of servlet threads allocated by the servlet container minus the configured or calculated value of IntegrationPointMaxConcurrentJobs. The calculated value of IntegrationPointMaxConcurrentJobs can be seen in SDConsole/Members/Decision Service. |
IntegrationPointRequestIOFactor | The percentage of time Integration Point requests spend doing IO, or otherwise waiting for systems external to this VM. |
ModelDSName | The JNDI name of the datasource used by the Learning Service. |
ModelSnapshotDSName | The JNDI name of the datasource for the model snapshots. |
ModelSnapshotMinAbsCorrelation | Controls whether to dump all correlation rows or to set a minimum correlation value for dumping. The default value of 0.000001 prevents the dumping of very small value correlation rows. Set the value to 0 to dump all correlation rows. |
ModelSnapshotNumberOfBins | Controls the number of bins for model snapshots. Numeric attribute values are automatically binned, or assigned to numeric ranges. The default number of bins is 5. To achieve greater resolution of your numeric data, increase the number of bins.
Note that for the same numeric attribute, Oracle RTD creates different bins in different time windows. Therefore, it is unlikely that you will be able to join numeric attribute values across time windows. |
SystemDSName | The JNDI name of the datasource. |
WorkerThreadPoolSize | The number of threads used for general purpose maintenance activities, not for normal Integration Point request processing. Maintenance activities include model maintenance, session timing, and timed-out request processing. |
The SDClusterPropertyManager > Cluster MBean has the following attributes:
Attribute | Description |
---|---|
BatchManagerInitialWait | The number of milliseconds to wait when the server first starts up before trying to start the Batch Manager Service. |
BatchManagerRestartWait | The number of milliseconds to wait after a computer fails or leaves the cluster before trying to restart the Batch Manager Service. |
ChoiceHistoryCleanupChunkSize | The chunk size to use when deleting old choice history records. |
ChoiceHistoryCleanupThrottle | A number between 0.1 and 1, inclusive. Higher throttle corresponds to higher speed. |
GenerateDSCookies | Generate Decision Server HTTP Cookies. Set to true to have Decision Server associate Integration Point requests with HTTP sessions, thus causing the Web container to generate container-specific session-affinity cookies. |
GenerateDSSessionIdCookie | Generate Decision Service Session-ID Cookies. Set to true to have Decision Service supply a cookie named ORTD_DS_SessionID identifying the DS session serving the current integration point request. |
JGroupsDSMulticastAddress | Gets merged into the JGroupsDSProtocols string as the multicast address used by the Decision Service forwarding channelups. |
JGroupsDSMulticastPort | Gets merged into the JGroupsDSProtocols string as the multicast port for the Decision Service forwarding channel. |
JGroupDSProtocols | Defines the JGroups protocols and properties used for the Decision Server forwarding channel. |
JGroupsMulticastAddress | Gets merged into the JGroupsProtocols string as the multicast address used by Oracle RTD cluster management. |
JGroupsMulticastPort | Gets merged into the JGroupProtocols string as the multicast port used by RTD cluster management. |
JGroupProtocols | Defines the protocols and properties used for the JGroups channel. |
LearningDataStorageCleanupChunkSize | The chunk size to use when deleting old learning data storage records. |
LearningDataStorageCleanupThrottle | A number between 0.1 and 1, inclusive. Higher throttle corresponds to higher speed. |
LearningServiceInitialWait | The number of milliseconds to wait when the server first starts up before trying to start the Learning Service. |
LearningServiceRestartWait | The number of milliseconds to wait after a computer fails or leaves the cluster before trying to restart the Learning Service. |
OperationalDataCleanupPeriod | The number of hours (fractions are allowed) between cleanup of the operational data (choice history, statistics, learning data storage) in the database. |
RestrictClusterMembers | True if the hosts that can be in the cluster is restricted to a fixed list of trusted IP addresses. |
RestrictDSClients | True if the hosts that can send Decision Service requests is restricted to a fixed list of trusted IP addressess. |
SDGroupName | The name of the Oracle RTD cluster, as recognized by Oracle RTD's JGroups cluster management. |
StatisticsCleanupChunkSize | The chunk size to use when deleting old statistic records. |
StatisticsCleanupThrottle | A number between 0.1 and 1, inclusive. Higher throttle corresponds to higher speed. |
TrustedClusterMembers | List of host IP addresses that can join the cluster. Port is optional, separated from IP by ':'. Entries are separated by ';'. |
TrustedDSClients | List of host IP addresses from which Decision Service requests will be accepted. Port is optional, separated from IP by ':'. Entries are separated by ';'. |
The SDClusterPropertyManager > Deployment MBean has the following attribute:
Attribute | Description |
---|---|
AppPollingInterval | How frequently, in seconds, the AppFactory polls the SDApps table to see if there are new apps. |
The SDCluster > SDManagement MBean has the following attributes:
Attribute | Description |
---|---|
BatchManager | Batch Manager configuration. |
DeploymentStates | Manage deployment states. |
InlineServiceManager: | Inline Service Manager. |
LearningService | Learning Service configuration. |
Members | Cluster members. |
Properties | Cluster properties configuration. |
Security | Security Manager. |
This section provides information about management at the member level.
This section contains the following topics:
Section 15.4.1, "About OracleRTD > SDManagement > SDLogging"
Section 15.4.2, "About OracleRTD > SDManagement > SDPropertyManager"
Section 15.4.3, "About OracleRTD > SDPropertyManager > Performance Monitoring"
Section 15.4.4, "About OracleRTD > SDPropertyManager > Misc"
Section 15.4.5, "About OracleRTD > Server > DecisionService"
The SDManagement > SDLogging MBean has the following attributes:
Attribute | Description |
---|---|
InlineServicePriority | Current logging priority for Inline Services. Valid values are DEBUG , ERROR , INFO , and WARN . |
LogFile | Location of the current log file. |
Priority | Current logging priority for the com.sigmadynamics category. Valid values are DEBUG , ERROR , INFO , and WARN . |
For more information about the values written to the log file, see:
Appendix A, "Development Error Messages" in Oracle Real-Time Decisions Platform Developer's Guide
The SDManagement > SDPropertyManager MBean has the following attributes:
Attribute | Description |
---|---|
PerformanceMonitoring | Performance counter properties. |
Misc | Miscellaneous properties. |
The SDPropertyManager > Performance Monitoring MBean has the following attributes:
Attribute | Description |
---|---|
DSPerfCounterAppend | If true, performance data is appended to an existing file, if any. Otherwise, any existing file is overwritten when the server restarts. |
DSPerfCounterEnabled | Enables the writing of DS performance counters. This should not be enabled indefinitely, because the file grows without limit. |
DSPerfCounterLogFile | The tab-separated CSV file into which DS performance counts are periodically appended. If MS Excel is available, ds_perf.xls , supplied in the installation's etc directory, provides a convenient view. |
DSPerfCounterLogInterval | The update interval in milliseconds for DS performance counts. |
For more information about using performance monitoring, see Chapter 14, "Performance Monitoring".
The SDPropertyManager > Misc MBean has the following attributes:
Attribute | Description |
---|---|
BatchAgentEnabled | Whether or not Batch Agent should run in this instance. |
BatchManagerEnabled | Whether or not Batch Manager should run in this instance. |
DecisionCenterEnabled | Whether or not Decision Center should run in this instance. |
DecisionServiceEnabled | Whether or not Decision Service should run in this instance. |
IntegrationPointMaxConcurrent Jobs | The maximum number of concurrently executing Integration Point requests. This should normally be set to 0 , in which case the value is calculated as follows, where Math.ceil means "round up to the next higher integer."
NumCPUs * Math.ceil(1/(1-DSRequestIOFactor)) + 5 |
IntegrationPointQueueSize | The maximum number of Integration Point requests that can wait to execute. If a request tries to exceed this number, the server terminates the request with a "Server Too Busy" error message. This setting should be less than or equal to the number of servlet threads allocated by the servlet container minus the configured or calculated value of IntegrationPointMaxConcurrentJobs. The calculated value of IntegrationPointMaxConcurrentJobs can be seen in SDConsole/Members/Decision Service . |
IntegrationPointRequestIOFactor | The percentage of time Integration Point requests spend doing IO, or otherwise waiting for systems external to this VM. |
LearningServiceEnabled | Whether or not Learning Service should run in this instance. |
WorkerThreadPoolSize | The number of threads used for general purpose maintenance activities, not for normal Integration Point request processing. Maintenance activities include model maintenance, session timing, and timed-out request processing. |
The Server > DecisionService MBean has the following read-only attributes:
Attribute | Description |
---|---|
CurrentRequestsQueued | Number of currently waiting requests, not yet running. |
CurrentRequestsRunning | Number of currently running requests. |
CurrentSessions | Number of Decision Service sessions still open. |
MaxAllowedConcurrentRequests | Maximum number of requests that can run concurrently. |
NumCPUs | Number of CPUs in this host. In Windows, for a hyper-threaded computer, use half the number of processors shown by Windows Task Manager. |
PeakRequestsQueued | Largest number of requests that have had to wait at any one time. |
RequestQueueCapacity | Maximum number of requests that can wait concurrently. |
RequestsForwarded | Total number of requests forwarded to another server in the cluster. |
RequestsQueued | Total number of requests that have had to wait before running. |
RequestsWhenQueueFull | Total number of requests rejected because the request queue was full. |
TimedOutRequests | Total number of requests that have timed out. |
TotalRequests | Total number of requests seen since the server started. |
TotalSessions | Total number of Decision Service sessions created. |
The Server > SDManagement MBean has the following attributes:
Attribute | Description |
---|---|
BatchAgent | Batch Agent configuration. |
DecisionService | Decision Service configuration. |
Logger | Logger configuration. |
Properties | Properties configuration. |
The Server > BatchAgent MBean has the following attributes:
Attribute | Description |
---|---|
ActiveBatches | List of all batch jobs currently running on this batch agent, paused, or waiting to run. The list could be empty. |
BatchNames | List of batches registered with this batch agent. |
The Server > BatchManager MBean has the following attributes:
Attribute | Description |
---|---|
ActiveBatches | List of brief status information for all batch jobs currently running, paused, or waiting to run. The list could be empty. |
BatchNames | List of batches registered with the batch framework. |
Security management MBeans impact authentication settings on the cluster. Different security settings are displayed, depending on the type set in Security Authenticator.
This section contains the following topic:
The SDManagement > SecurityManager MBean has the following operations:
Assigns the specified cluster permission. See Section 7.4, "Assigning Permissions" for more information. This operation accepts the following parameters:
UserOrGroup: The user name or group name to which you want to assign permissions.
permCode: The code of the permission.
Returns the permissions directly assigned to a specific user or group. This operation accepts the following parameter:
userOrGroup: The target user or group name.
listEveryoneHavingDirectPermissions()
Returns the names of users and groups that have directly assigned permissions.
Returns the localized name and integer code for all possible permission types. The codes are used as operands for various operations that require a permission type designation.
Removes all permissions directly assigned for the specified user or group. This operation accepts the following parameter:
userOrGroup: The target user or group name.
Removes the specified permission. This operation accepts the following parameters:
userOrRole: The target user name or role name.
permCode: The code of the permission you want to remove.
Reverts to the standard permissions.
Use Inline Service Manager to manage the Inline Services deployed on the cluster.
This section contains the following topics:
Each deployed Inline Service is displayed under the InlineServiceManager MBean.
The SDManagement > InlineServiceManager MBean has the following attribute:
Attribute | Description |
---|---|
InlineServices | List of deployed inline services. |
The SDManagement > InlineServiceManager MBean has the following operation:
Removes MBeans for applications no longer in the database, and creates MBeans for new ones.
Removes all Inline Services (loaded, loadable, failed).
InlineServiceManager MBeans can be viewed by choosing the name of an Inline Service, then choosing a Deployment State (for example, Development, QA, or Production), then choosing a particular flag (Failed, Inactive, or Loadable). For example: OracleRTD > InlineServiceManager > CrossSell > Production > Loadable.
The InlineServiceManager MBeans for a specific Inline Service have the following attributes:
Attribute | Description |
---|---|
DeploymentState | Development, QA, or Production. |
Flag | Failed, Inactive, or Loadable. |
LockStatus | The lock status for the Inline Service. |
ServiceId | The service ID for the Inline Service. |
The InlineServiceManager MBeans for a specific Inline Service have the following operations:
Unlocks this service.
Stops an Inline Service in this server and removes the service from the database.
Flushes all of the statistics for this service to the database.
Flushes and deletes all of the statistics for this service from the database.
Deletes all of the choice history for this service from the database.
Deletes all of the operational data for this service from the database. This includes choice history, statistics, and the study.
Removes the study for this service.
Maintenance Operations appear in the MBean tree under an Inline Service when both of the following conditions hold:
The Inline Service includes one or more Maintenance Operations
The Inline Service has the Deployment flag set to Loadable
Each Maintenance Operation appears in both of the BroadcastAsyncOperations and DirectBlockingOperations nodes, under the Loadable entry.
Operations listed in the DirectBlockingOperations node are invoked on the local server only, and they return only after the operation has completed. The returned value will be displayed to the JConsole user in a popup dialog. If the operation has return type "void," then "null" will appear. If the operation fails for any reason, a short error message will be displayed in a JConsole popup dialog, and a more detailed report can be found in the log of that server.
Operations listed in the BroadcastAsyncOperations node are invoked across every node of a cluster. The operation returns immediately with the number of cluster members who received the broadcast. If the cluster has just one node, the operation returns 1, and the invocation is still asynchronous.
The following run-time considerations apply for Maintenance Operations:
Oracle RTD does not guarantee that all cluster members are notified of Maintenance Operation invocations, although usually they will be.
For example, if one member of a cluster is down when a Maintenance Operation is invoked, there is no notification to indicate that the cluster member should run the Maintenance Operation when it comes back up.
Ordering of Maintenance Operations is not guaranteed. For example, if two Maintenance Operations A and B are invoked in sequence, an Inline Service may run B before it runs A, or it may even run them simultaneously.
By viewing the OracleRTD > DeploymentStates MBeans, you can see a list of deployment states that are available on the cluster.
This section contains the following topics:
Section 15.7.1, "About OracleRTD > SDManagement > DeploymentStates"
Section 15.7.2, "About OracleRTD > Deployment States > [State]"
The SDManagement > DeploymentStates MBean has the following attribute:
Attribute | Description |
---|---|
StateObjectNames | A listing of all deployment states available on the server. |
MBeans for a particular Deployment State can be viewed by choosing OracleRTD > Deployment States, then choosing a Deployment State (for example, Development, QA, or Production).
Each Deployment States > [State] MBean has the following attributes:
Attribute | Description |
---|---|
AllowHotSwapping | Allow hot swapping of Inline Services with this deployment state in Decision Service. |
Id | ID of the deployment state. |
Name | Name of the deployment state. |
Note:
If hot swapping is enabled for a deployment state, and an Inline Service is redeployed in the state, the existing Inline Service will remain active until all existing sessions close or timeout. New sessions will be created on the newly deployed Inline Service.Managing the Learning Service on the cluster allows you to check the status of the learning models and perform maintenance on them.
This section contains the following topics:
Section 15.8.1, "About OracleRTD > Server > LearningService"
Section 15.8.2, "About OracleRTD > Learning Server > [Study]"
Section 15.8.3, "About OracleRTD > Study > [Study Name] > [Model]"
The Server > LearningService MBean has the following attribute:
Attribute | Description |
---|---|
Studies | A list of all Studies running on the Learning Server. The models of a Study are viewed by clicking on a Study. |
The Learning Server > [Study] MBeans have the following attributes:
Attribute | Description |
---|---|
Models | Models belonging to this study. |
Name | The name of the study. |
The Learning Server > [Study] MBeans have the following operation:
Saves a snapshot of this study to the database (complete).
Deletes this study.
Removes this study's snapshot from the database.
Saves a snapshot of this study to the database (delta).
The Study > [Study Name] > [Model] MBeans have the following attributes:
Attribute | Description |
---|---|
Attributes | Names of the model attributes. The names listed here match the attribute names in the session for your Inline Service. |
Name | The name of the model. |
TimeWindows | List of the ranges of time that have been learned about by this particular model. |
The Study > [Study Name] > [Model] MBeans have the following operations:
Deletes this model.
Erases model data collected for a value of an attribute. This operation accepts the following parameters:
AttributeName: The name of an attribute.
Value: The value to be deleted.
Erases model data collected for a range of values of an attribute. This operation accepts the following parameters:
AttributeName: The name of an attribute.
HighestValue: The highest value to be deleted.
LowestValue: The lowest value to be deleted.
Closes the current time window and starts a new one. Do not use this operation in a production environment, because it may impair future model learning.
You can view and set the following system properties:
System Property | Description |
---|---|
JGroupsDSMulticastAddress | Gets merged into the JGroupsDSProtocols string as the multicast address used by the Decision Service forwarding channelups. |
JGroupsDSMulticastPort | Gets merged into the JGroupsDSProtocols string as the multicast port for the Decision Service forwarding channel. |
JGroupsMulticastAddress | Gets merged into the JGroupsProtocols string as the multicast address used by RTD cluster management. |
JGroupsMulticastPort | Gets merged into the JGroupProtocols string as the multicast port used by RTD cluster management. |
ModelDSName | The JNDI name of the datasource used by the Learning Service. Default=SDDS. |
ModelSnapshotDSName | The JNDI name of the datasource used by the Learning Service to perform snapshots of its learning models. Default=SDDS. |
RestrictClusterMembers | True if the hosts that can be in the cluster is restricted to a fixed list of trusted IP addresses. |
RestrictDSClients | True if the hosts that can send Decision Service requests is restricted to a fixed list of trusted IP addressess. |
SDGroupName | This is the name of the Oracle RTD cluster, as recognized by Oracle RTD's JGroups cluster management. |
SystemDSName | This is the name of the Oracle RTD system datasource. Default=SDDS. |
TrustedClusterMembers | List of host IP addresses that can join the cluster. Port is optional, separated from IP by ':'. Entries are separated by ';'. |
TrustedDSClients | List of host IP addresses from which Decision Service requests will be accepted. Port is optional, separated from IP by ':'. Entries are separated by ';'. |