| Oracle® Beehive Administrator's Reference Guide Release 2 (2.0.1.8) Part Number E16649-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Administrator's Reference Guide Release 2 (2.0.1.8) Part Number E16649-04 |
|
|
PDF · Mobi · ePub |
This module contains the following topics:
This section contains the following topics:
Table 4-1, "Component Management beectl Commands" lists beectl commands you are likely to use when managing Oracle Beehive components.
Note:
For complete descriptions and syntax for these
beectl commands, see Chapter 2, "Oracle Beehive Command Line Utility".Table 4-1 Component Management beectl Commands
| Command | Description |
|---|---|
|
Lists the components in the configuration repository |
|
|
Lists available connection pools in the system |
|
|
Fetches the value of the given property name for the given component ID. If property name is not specified then all the properties are listed |
|
|
Lists all ports in use (by the current Oracle Beehive server), including which component and property is using the port, and the protocol in use by that port |
|
|
Changes the port through which a service communicates. You must specify the protocol. If your port change affects a privileged port, you must take the additional steps in "Modifying Oracle Beehive Ports using Privileged Port Numbers" when using this command |
|
|
Lists the metadata about all the properties of a component |
|
|
Updates the value(s) for the named property for the component identified by |
|
|
Updates the sensitive property of the object identified by the |
|
|
Lists collected statistical information about the functioning of a given type of component |
|
|
Clears the value of specified property in the configuration object identified by specified ID |
This section describes beectl commands that are used for managing component parameters.
This section contains the following topics:
Many Oracle Beehive components have lists of associated properties which are not directly exposed in an beectl command. Instead, you can set them by using the following common commands.
A subset of components are services. Each of the Oracle Beehive services has a system defined alias. The system defined alias is a unique name that you can use with most commands to identify a service for the purposes of configuration. All of the system defined aliases for Oracle Beehive services begin with an underscore character (_). For example, the E-Mail Service has a system defined alias of _EmailService.
In some cases, you may see a property which is itself used to contain properties (sub-properties). You can use the beectl list_properties command with the alias of the service or the name of the component and the name of such a property, with a colon character between them, to list the sub-properties.
For example, the E-mail Service has a property called "SMTPProperties". You can list its properties by using the beectl list_properties command:
beectl> list_properties --component _EmailService:SMTPProperties
You can review the names of all Oracle Beehive components by using the beectl list_components command:
beectl> list_components
All of the Oracle Beehive components are listed.
For each service, prepend an underscore to the Component Type to get the service system alias. For example, the Component Type "EmailService" has a system alias of _EmailService.
Note:
The list_properties command works on any Oracle Beehive system object. The --component value is case-insensitive, and will take as valid any identifier of a system object, any system object alias, or any user-defined alias.
User-defined aliases are modifiable properties of any system object, with the property name of Alias. Generally in Oracle Beehive documentation the system defined alias or component ID is used in examples, but you may always substitute a user defined alias in the --component of a beectl command
To set a property using beectl, use the following procedure:
Use the beectl list_properties command to get the list of all properties for the component you want to configure. Each property is listed by name, along with its current value:
beectl> list_properties --component _EmailService:SMTPProperties
In this example, the name of the E-Mail Service SMTP component is entered, with the E-mail Service system alias, to get properties for the SMTP Server component.
Use the beectl modify_property or delete_property commands to make the desired change to the property you specify:
beectl> modify_property --component _EmailService:SMTPProperties --name <property_name> --value <new value>
In this example, the value of an SMTP Server property is modified to a new value. It is an absolute replacement of the property value.
However, if it is a list of values that is to be changed, the syntax should be:
beectl modify_property --component <oc4j>:StartJavaExecutionArguments --name AdditionalOptions --value=<value1> --value=<value2> --value=<value3> --value=<valueNNN> --activate_configuration
Note:
Line breaks have been inserted in the following example for better readability.beectl modify_property
--component _CURRENT_SITE:Database
--name AffinityServiceNames
--value "(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=host1.example.com)(PORT=1521)))
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=afserv1.example.com)))"
--value "(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=host2.example.com)(PORT=1521)))
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=afserv2.example.com)))"
--value "(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=host3.example.com)(PORT=1521)))
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=afserv3.example.com)))"
--value "(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=host4.example.com)(PORT=1521)))
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=afserv4.example.com)))"
Note:
Running the following command will clear all existing values for the additional options, including theXX:CompileCommand=exclude,oracle/ocs/cspi/OcsExceptionMetadata.bind type values
beectl modify_property –component <oc4j>:StartJavaExecutionArguments --name AdditionalOptions -revert_to_default
Caution:
If you are changing any port number to a privileged port (a port number below 1024) on a UNIX or Linux installation, you must first perform a special procedure, and then change the port. First follow the special procedure in "Modifying Oracle Beehive Ports using Privileged Port Numbers", and then follow the procedure below to change the port.Whenever you change a property in Oracle Beehive, you are making an alteration to the proposed configuration. You must activate a proposed configuration before changes you have made are actually applied to the running Oracle Beehive deployment. When you are done making configuration changes, activate the proposed configuration using the beectl activate_configuration command:
beectl> activate_configuration
This command saves your proposed configuration, performs a background validation of the configuration, and then activates it.
You can also append the --activate_configuration option to any beectl command, causing the system to perform these steps automatically on command completion. The syntax is:
beectl append_value --component <component> --name <property name> --value=<value1> --activate_configuration
Above command will add on to the existing property value. You can review information about various proposed and applied system configurations by using the beectl list_configuration_versions command
If you modify any of the properties in Table 4-2, "Properties Requiring beectl modify_local_configuration_files when changed" , you must also run the beectl modify_local_configuration_files command.
In the following cases, you must also restart a service, component, or the entire deployment, using the beectl restart command:
Changing the database connection pool requires a full restart of Oracle Beehive (bug 6335906)
Changing the Instant Message Service's XmppPort or XmppSslPort properties requires that you restart the affected component
Changing the DeliveryPoolSize parameter of the Message Delivery Service requires you to restart all affected Message Delivery Service instances
See also:
For a reference on using thebeectl command-line interface, see Chapter 2, "Oracle Beehive Command Line Utility".Table 4-2 Properties Requiring beectl modify_local_configuration_files when changed
| Component | Property |
|---|---|
|
SsoType SsoLogoutUrl UseJazn WnaEnabled WnaKeytab WnaPrincipal OssoConfigFile AuthStoreType SsoType LoginAttempts LockoutTime UseSecureCookie WsSecuritySamlEnabled WsSecuritySigKeyAlias WsSecuritySigKeyPwd WsSecurityExpiry |
|
|
LogBaseDir WalletDir WalletPassword KeystoreFile KeyStoreFilePassword |
|
|
ControlPort (CtrlPort) Status StartJavaExecutionArguments StopJavaExecutionArguments |
|
|
ConnectDescriptor XaServiceNames OnsNodeConfiguration |
|
|
UserName Password |
|
|
ConnectionProperties MaxConnections MinConnections InitialConnections MaxStatementsLimit ConnectTimeout InactivityTimeout TimeToLiveTimeout AbandonedConnectionTimeout PropertyCheckInterval ConnectionWaitTimeout LowerThresholdLimit |
|
|
HttpSslListenPort HttpListenPort OsUser OsGroup Timeout ServerAdmin MaxClients ServerRoot DocRootLimitExcept KeepAliveTimeout SSLLogLevel LogLevel Status |
|
|
HttpServerSslEnabled SslTerminatedByLoadBalancer |
|
|
LdapServerHostName LdapServerPort LdapServerSslPort SslEnabled LdapServerUser LdapServerPassword UserSearchBase GroupSearchBase UserObjectClass GroupObjectClass PrimaryAuthenticationAttribute DirectoryType |
|
|
AdminPassword Status AjpPortMaxValue AjpPortMinValue RmiPortMaxValue RmiPortMinValue RmisPortMaxValue RmisPortMinValue JmsPortMaxValue JmsPortMinValue JGroupPortMaxValue JgroupPortMinValue StartJavaExecutionArguments StopJavaExecutionArguments |
|
|
AjpsEnabled AdminPassword OrmisEnabled |
|
|
RequestPort RemotePort LocalPort |
|
|
NotificationServerSslEnabled Opmns |
|
|
PrimaryHostName SipListenerIPAddress |
|
|
SipPortMaxValue SipPortMinValue SipEnabled |
|
|
LanguagePack ClusteringEnabled SsoKeyAlias |
|
|
HttpPort HttpSslPort ServerName |
You may export the entire system model configuration data into an XML file for any given configuration version with the beectl export_configuration_data command.
You may provide your Oracle support representative the output from this command. This will help your representative investigate any problems with your Oracle Beehive deployment faster. You may also use the output of from this command to compare the configuration between different Oracle Beehive deployments, such as between a test and a production deployment.
Note:
For security reasons, secure values do not appear in the output of thebeectl export_configuration_data command.You have the option of configuring various Oracle Beehive components to use privileged ports (ports below 1024) on UNIX and Linux based deployments. For example, the standard port for the IMAP service is port 143.
Any time you modify a port, and the new port number is a privileged port, you must perform the following procedure. Perform this procedure first, and then make the port change. You must perform this procedure when you change from a non-privileged port to a privileged port, and when you change from one privileged port to another privileged port.
If you have previously performed this procedure, you can skip to step 4:
From the command line, navigate to the following file:
$ORACLE_HOME/beehive/bin/hasbind
Using the sudo command, set the owner of the file to root, and modify the permsissions on the file:
sudo chown root hasbind sudo chmod a+sx hasbind
The file should have the following permissions (the file date and group will be different):
-rws--s--x 1 root g900 31395 Jun 18 14:01 hasbind
Then create a file /etc/cap.ora. It must be owned by root and should be read-only for everybody except root:
-rw----r-- 1 root root 34 Jun 18 14:05 /etc/cap.ora
Edit the /etc/cap.ora file, so that it contains a single line, like the following:
cat /etc/cap.ora +user <user>: bind port 25,143
Replace <user> with the software owner (the user used to install Oracle Beehive). List each privileged port you will configure an Oracle Beehive service to use, separated by commas. If you are changing from one privileged port to another privileged port, you can delete the port number that will become unused, to release it.
You may now configure Oracle Beehive components to use the privileged ports you have designated in the cap.ora file. Follow the procedure for changing ports as normal.
This module describes the properties for the following components:
The following properties are common to all components:
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
not applicable |
May not start with an underscore ( |
Yes |
No |
Each SystemObject in the configuration has a Universally Unique Identifier (UUID) assigned by the system. An example UUID is f477dfe5-400d-41a2-b2a5-394ebba67293. You can assign an easier to remember Alias to a SystemObject and use the Alias in place of the UUID, for example, as the component identifier in beectl commands. Aliases must be unique, so you may not assign the same Alias to multiple SystemObjects. The validation performed on the proposed configuration at activation time ensures that no two SystemObjects have been assigned the same Alias. If duplicate Aliases are detected, the activation will fail and you must correct the situation before retrying the activation operation. |
|
|
Integer |
not applicable |
Minimum = 0, maximum = 9223372036854775807 |
yes |
No |
Lightweight thread count for the service. A lightweight thread provides no guarantees on the thread context being used. |
|
|
LoggingConfigurable.LoggingProperties (Structural property) |
not applicable |
No |
No |
Yes |
A reference to a SystemObject that holds the property settings that configure logging behavior. You do not directly modify the value of this property. You configure logging behavior by modifying the properties of the referenced LoggingProperties object. |
|
|
ApplicationImage (Structural property) |
not applicable |
No |
No |
Yes |
The application image for the service. The application image models the EAR file that gets deployed to create service instances for the service. |
|
|
Set<ServiceInstance> (Structural property) |
not applicable |
No |
Yes |
No |
The list of ServicesInstances associated with the service. |
|
|
Site (Structural property) |
not applicable |
No |
No |
No |
The site with which this service is associated. |
|
|
StatusManageable.Status (Legal values: |
|
No |
Yes |
No |
The Status, either |
The following properties are common to all ServiceInstances:
Table 4-5 Common Properties for ServiceInstances
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
not applicable |
No |
No |
No |
J2EE application name. |
|
|
Integer |
5 |
Minimum=1, Maximum=10 |
Yes |
No |
Priority of lightweight threads for the service. |
|
|
String |
not applicable |
No |
No |
No |
The Oc4j instance associated with the BeehiveJ2eeApplication. |
This section lists the properties for each Oracle Beehive component. If a component has only common properties, the table of properties is omitted. Refer to "Common Properties", and "Common Properties for ServiceInstances", for details about common properties.
The tables listing properties for components have the following columns:
Name: The property name
Data Type: One of the following types:
Integer: A whole number
Int: A whole number
String: Alphanumeric characters
Boolean: True or false, used to enable or disable a feature
Long: A whole number (allows larger values than Int or Integer)
Structural Property: A special type, usually unique to the component, that can contain a string in a specified format
SecureString: Alphanumeric characters, stored as an encrypted value
File: A logical path to a file or directory
List: A comma-delimited list of text values
Map: A set of key:value pairs
Level: Used for setting log levels; accepts one of a listed set of keywords
<Component>.<Property> Legal Values (): A unique property which accepts one from a list of legal values. For example: AuthenticationService.AuthStoreType (Legal values: db, ldap)
CollabID: An Oracle Beehive CollabID
Default Value: If the property is seeded with a default value during installation of Oracle Beehive, that value is listed
Accepted Values: If the range or set of values is constrained (beyond that allowed by its type), the constraint is shown
Mutable: Mutable properties can change over time from one version of the configuration to the next. When Mutable is set to No, the value can only be changed when it belongs to a new configuration object created in the proposed configuration. Once the proposed configuration is activated, all immutable properties will never change again.
Read Only: You can only use the beectl modify_property command to change the value of properties with Read Only set to No. You cannot use this command to modify properties with Read Only set to Yes.
Internal Oracle Beehive code can still modify Read Only properties.
Description: A brief description of the property's function
The following properties are available for AccessControlService:
Table 4-6 AccessControlService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for AlarmService:
Table 4-7 AlarmService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Long |
259200 |
All permitted values |
Yes |
No |
The amount of time (in seconds) that will elapse by default before an alarm expires. Applies in cases where no expiry value is explicitly set when the alarm is created. Alarms are used internally by some Oracle Beehive services, which can explicitly set an expiry that will override this default value. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for ApplicationImage:
Table 4-8 ApplicationImage Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
No |
Yes |
The file name of the enterprise archive (.ear) for a service or application image. |
|
|
String |
n/a |
All permitted values |
No |
Yes |
The name of the service's interface, which is used by the management model to cull service properties and statistics. |
The following properties are available for AuditService:
Table 4-9 AuditService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
480 |
Min=1, Max=6000 |
Yes |
No |
Specifies the logon record life time in minutes. Stale logon records are purged periodically by the purge process. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Specifies the whether the audit record purging enabled or disabled. If the purging is enabled , records get purged if they are older than retention period. |
|
|
int |
60 |
Min=1, Max=2147483647 |
Yes |
No |
Specifies the audit record retention period in days. Audit record is guaranteed to stay in the system until the retention period. Audit records get purged after the retention period. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for AuthenticationService:
Table 4-10 AuthenticationService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
AuthenticationService.AuthStoreType (Legal values: db, ldap) |
db |
All permitted values |
Yes |
No |
Specifies the authentication repository type. Valid values: db, ldap |
|
|
List<AuthenticationPlugin> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Authentication plugins for the external authentication, only one such plugin can be in enabled state. |
|
|
String |
Authorized_Users |
All permitted values |
Yes |
No |
Specifies the default authentication realm for Oracle Beehive. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Integer |
7200 |
All permitted values |
Yes |
No |
SSO session timeout (in seconds) when the SSO Provider is JavaSSO. Note that this is a hard timeout, not an inactivity timeout. The session will timeout after this amount of time no matter what. |
|
|
Integer |
7200 |
All permitted values |
Yes |
No |
Specifies the duration (in seconds) that a user account will be locked out of the system if the maximum allowable login attempts is reached. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Integer |
-1 |
All permitted values |
Yes |
No |
Specifies the number of failed login attempts allowed before a user account gets locked out of the system. -1 = No limit |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the configuration file for Oracle Single Sign-On (OSSO). |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Specifies whether updates to Client Session Information should be disabled or not after authentication. Valid values: true, false |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
String[] |
n/a |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.AuthenticationServiceBundle, key DESC_LONG_S2S_IDENTITIES |
|
|
Map<String,SAMLIdentity> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Specifies the SAML registration map, which contains trusted assertion issuers and service providers. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the logout URL for single sign-on deployments. This is the URL to which users will be redirected after logging out of the system. |
|
|
AuthenticationService.SsoType (Legal values: jsso, osso) |
jsso |
All permitted values |
Yes |
No |
Specifies the single sign-on type. Valid values: jsso, osso |
|
|
Integer |
300 |
All permitted values |
Yes |
No |
Specifies the amount of time (in seconds) that an authentication token will remained timed out. 0 = Indefinitely |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Specifies whether or not Oracle Internet Directory should be configured natively with Oracle Application Server using Java Authorization (JAZN). If disabled, Oracle Internet Directory is configured as an external LDAP server (recommended). Valid values: true, false |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Specifies whether or not the JavaSSO cookie should be sent over a Secure Socket Layer (SSL) connection. If enabled, JavaSSO is not supported over non-SSL connnections. Valid values: true, false |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Specifies whether or not the configured secure hash value (in the LDAP server) should be used for the digest authentication when the authentication repository is an LDAP server. If disabled, the password value is used to calculate the digest. Valid values: true, false |
|
|
Integer |
3600 |
All permitted values |
Yes |
No |
Specifies the amount of time (in seconds) that will elapse before inbound and outbound message signatures expire for Security Assertions Markup Language (SAML) Web services ports. |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Specifies whether or not Security Assertions Markup Language (SAML) authentication is enabled for Oracle Beehive Web services. Valid values: true, false |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the key alias of outbound message signatures for Security Assertions Markup Language (SAML) Web services ports. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Specifies the key password of outbound message signatures for Security Assertions Markup Language (SAML) Web services ports. |
The following properties are available for AuthenticationService.AuthenticationPlugin:
Table 4-11 AuthenticationService.AuthenticationPlugin Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
AuthenticationService.AuthenticationPlugin.AuthenticationType (Legal values: FORM) |
n/a |
All permitted values |
Yes |
No |
Authentication type of the plugin. |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Status of the authentication plugin, specifies whether the plugin is enabled for authentication. |
|
|
Map<String,String> |
n/a |
All permitted values |
Yes |
No |
Map of properties required by the authentication plugin. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Package qualified class name of the authentication plugin implementation. |
The following properties are available for BdkService:
Table 4-12 BdkService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
n/a |
All permitted values |
No |
Yes |
description bundle not set |
||
|
n/a |
All permitted values |
No |
Yes |
description bundle not set |
||
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for BdkService.RestProperties:
The following properties are available for BdkService.RestProperties.PrivateProperties:
Table 4-14 BdkService.RestProperties.PrivateProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
100 |
Min=1, Max=1000 |
Yes |
No |
description bundle not set |
|
|
int |
8192 |
Min=1, Max=2147483647 |
Yes |
No |
description bundle not set |
|
|
String |
../../beehive/restspool/temp |
All permitted values |
Yes |
No |
description bundle not set |
The following properties are available for BdkService.RestProperties.PublicProperties:
Table 4-15 BdkService.RestProperties.PublicProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
true |
All permitted values |
Yes |
No |
description bundle not set |
|
|
int |
100 |
Min=1, Max=2147483647 |
Yes |
No |
description bundle not set |
|
|
int |
2000 |
Min=10, Max=10000 |
Yes |
No |
description bundle not set |
|
|
int |
100 |
Min=10, Max=1000 |
Yes |
No |
description bundle not set |
|
|
int |
60 |
Min=10, Max=1800 |
Yes |
No |
description bundle not set |
|
|
int |
2 |
Min=0, Max=10 |
Yes |
No |
description bundle not set |
The following properties are available for BdkService.SoapProperties:
The following properties are available for BeeCentralService:
Table 4-17 BeeCentralService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Map<String,String> |
n/a |
All permitted values |
Yes |
No |
Customizable explanation that describes the correct phone number format for the voice mail transfer option. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
When set to TRUE, the Download Center is rendered in BeeCentral UI. When set to FALSE, the Download Center is hidden. |
|
|
String |
http://www.oracle.com/technology/products/beehive/beehive_users/2_0/central.htm |
All permitted values |
Yes |
No |
A configurable link to help text for Beehive clients. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
Map<String,String> |
n/a |
All permitted values |
Yes |
No |
Customizable explanation about the delivery of SMS notifications to mobile devices. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for BeehiveConferencingService:
Table 4-18 BeehiveConferencingService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
//www.java.com/js/deployJava.js |
All permitted values |
Yes |
No |
Parameter to set the deployJava.js URL to be used for launching javafx client. The default value for this parameter will be "//www.java.com/js/deployJava.js", which is fetched from the external java site. For intranet deplopyment of confctr, the value must be "DMS://deployJava.js", which will fetch the deployjava.js file from the internal package in DMS. |
|
|
String |
confjavafx.jnlp.template |
All permitted values |
Yes |
No |
Parameter to set the jnlp template to be used for javafx. The default value for this parameter will be "confjavafx.jnlp.template". which has javafx runtime jars fetched from external java site. For intranet deplopyment of confctr, the value must be "confjavafx.intranet.jnlp.template", which will fetch the required runtime files from the internal package in DMS. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Set the Conference Client download location for Macintosh. The default value for this parameter will be null. If it is null, then the URL for conference client will be fetched through Beehive Central. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Set the Conference Client download location for Windows. The default value for this parameter will be null. If it is null, then the URL for conference client will be fetched through Beehive Central. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
When set to TRUE, the Download Center is rendered in WebConference UI. When set to FALSE, the Download Center is hidden. |
|
|
String |
http://www.oracle.com/technology/products/beehive/beehive_users/2_0/conferencing.htm |
All permitted values |
Yes |
No |
A configurable link to help text for Beehive clients. |
|
|
String |
http://www.java.com |
All permitted values |
Yes |
No |
URL for downloading the Java Runtime Environment (JRE) required to launch the JavaFX client. Default URL http://www.java.com downloads the latest JRE. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for BeehiveInstance:
Table 4-19 BeehiveInstance Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
1 |
This property has a customized constraint. |
Yes |
No |
The number of processors committed for the current Oracle Beehive instance. This figure is used by the sizing algorithm to calculate the number of server and client Beehive Transport Infrastructure (BTI) workers, as well as the Oracle Containers for Java (OC4J) instances, required to support the current Oracle Beehive instance. |
|
|
Integer |
n/a |
This property has a customized constraint. |
Yes |
No |
The amount of physical memory in megabytes (MBs) committed for the current Oracle Beehive instance. This figure is used by the sizing algorithm to calculate the number of Oracle Containers for Java (OC4J) instances required for the current Oracle Beehive instance. |
|
|
String |
n/a |
All permitted values |
Yes |
Yes |
The name of the current Oracle Beehive instance. |
|
|
n/a |
All permitted values |
Yes |
No |
The Oracle Beehive Transport Infrastructure (BTI) associated with the current Oracle Beehive instance. |
||
|
n/a |
All permitted values |
Yes |
No |
A reference to a SystemObject that holds the properties used to configure diagnosability functionality. You do not directly modify the value of this property. You modify the properties of the referenced DiagnosabilitySettings object. |
||
|
n/a |
All permitted values |
Yes |
No |
A reference to the HttpServer SystemObject for the current Oracle Beehive instance. You do not directly modify the value of this property. You configure the HTTP Server by modifying the properties of the referenced HttpServer object. |
||
|
File |
n/a |
All permitted values |
Yes |
No |
Path of the keystore file associated with the current Oracle Beehive instance. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Password for the keystore file associated with the current Oracle Beehive Instance. |
|
|
File |
beehive/logs |
All permitted values |
Yes |
No |
The base directory where Oracle Beehive will store its log files. |
|
|
Set<ManagedOc4j> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of references to the SystemObjects that configure the OC4J instances deployed in the current Oracle Beehive instance. The system automatically manages the value of this property. You must never directly modify the value. |
|
|
n/a |
All permitted values |
No |
No |
This is a reference to the SystemObject that configures OPMN for the current Oracle Beehive instance. The system automatically manages the value of this property. You must never directly modify the value. |
||
|
String |
n/a |
All permitted values |
No |
Yes |
The Oracle home for the current Oracle Beehive instance. |
|
|
n/a |
All permitted values |
No |
No |
This is a reference to the SystemObject that represents the Server associated with the current Oracle Beehive instance. The system automatically manages the value of this property. |
||
|
String |
n/a |
All permitted values |
Yes |
No |
Directory path of the Oracle Wallet associated with the current Oracle Beehive instance. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
The password for the Oracle Wallet associated with the current Oracle Beehive instance. |
No other properties exist for BeehiveJ2eeApplication .
The following properties are available for BeekeeperService:
Table 4-20 BeekeeperService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for Bti:
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
long description key not set |
||
|
int |
60 |
All permitted values |
Yes |
No |
Timeout for pings between btimon and BTI native processes. When this timeout is exceeded the native BTI processes is restarted. |
|
|
n/a |
All permitted values |
No |
No |
long description key not set |
||
|
int |
5959 |
Network Port, Min=1, Max=65536 |
Yes |
No |
TCP port for internal communications between components of BTI. This port is also used by opmn for pinging BTI. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Log directory for all BTI components |
|
|
n/a |
All permitted values |
No |
No |
long description key not set |
||
|
int |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
TCP port for communications between midtiers via OMB. |
|
|
n/a |
All permitted values |
No |
No |
long description key not set |
||
|
n/a |
All permitted values |
Yes |
No |
Arguments for the Java Virtual Machine when starting this component |
||
|
n/a |
All permitted values |
Yes |
No |
Arguments for the Java Virtual Machine when starting this component |
The following properties are available for BtiClientWorker:
Table 4-22 BtiClientWorker Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String[] |
n/a |
All permitted values |
Yes |
No |
Additional command line arguments to be passed to the BTI native process. |
|
|
n/a |
All permitted values |
Yes |
No |
long description key not set |
||
|
int |
1 |
All permitted values |
Yes |
No |
Number of MX processes in each BTI instance (midtier or DMZ). |
The following properties are available for BtiComponent:
The following properties are available for BtiGlobal:
Table 4-24 BtiGlobal Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
BtiGlobal.SecurityMode (Legal values: NONE, AUTH_ONLY, AUTH_AND_ENCRYPT) |
NONE |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
description bundle not set |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
description bundle not set |
The following properties are available for BtiRedirector:
The following properties are available for BtiServerWorker:
Table 4-26 BtiServerWorker Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String[] |
n/a |
All permitted values |
Yes |
No |
Additional command line arguments to be passed to the BTI native process. |
|
|
n/a |
All permitted values |
Yes |
No |
long description key not set |
||
|
int |
1 |
All permitted values |
Yes |
No |
Number of BP processes in each midtier. |
The following properties are available for CalDAVService:
Table 4-27 CalDAVService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the Oracle Beehive CalDAV Companion Web Access interface. If disabled, trying to access a CalDAV URL in a Web browser will return an error. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Long |
124 |
Min=0, Max=10950 |
Yes |
No |
The upper limit (in days) of the range for which date-based entities will be returned by Oracle Beehive if no range is explicitly provided by a CalDAV client. This value is represented as a positive integer. Oracle Beehive uses this value to determine whether or not to return certain date-based entities. For example, if this value is set to 30 and no time range is supplied by a CalDAV client, Oracle Beehive will return all date-based entities, such as meetings and tasks, that occur between today and the next 30 days. In this example, entities that occur on the 31st day from today and beyond will not be returned. |
|
|
Long |
31 |
Min=0, Max=10950 |
Yes |
No |
The lower limit (in days) of the range for which date-based entities will be returned by Oracle Beehive if no range is explicitly provided by a CalDAV client. This value is represented as a negative integer. Oracle Beehive uses this value to determine whether or not to return certain date-based entities. For example, if this value is set to -30 and no time range is supplied by a CalDAV client, Oracle Beehive will return all date-based entities, such as meetings and tasks, that occurred in the the previous 30 days only. In this example, entities that occurred on the 31st day prior to today and earlier will not be returned. |
|
|
n/a |
All permitted values |
No |
No |
The iSchedule service can be confifured using all the properties defined in this system object. |
||
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for CalDAVService.ISchedule:
Table 4-28 CalDAVService.ISchedule Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the Oracle Beehive iSchedule service. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
Specifies the list of hosts and ip addresses for which the proxy should not be used. Each entry can be either a complete host name (e.g. "www.oracle.com"), a domain name beginning with a dot (e.g. ".oracle.com"), an IP address (e.g. "12.34.56.78"), an IP subnet, specified as an IP address and a netmask separated by a "/" (e.g. "34.56.78/255.255.255.192"). |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the authentication name to use if the proxy requires authentication. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Specifies the key to use if the proxy requires authentication. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies a proxy hostname to use when the iSchedule service connects to remote iSchedule receivers. |
|
|
Integer |
80 |
All permitted values |
Yes |
No |
Specifies a proxy port to use when the iSchedule service connects to remote iSchedule receivers. |
|
|
CalDAVService.ISchedule.IScheduleProxyType (Legal values: HTTP, SOCKS4, SOCKS5) |
HTTP |
All permitted values |
Yes |
No |
Specifies the iSchedule proxy type, can be either HTTP, SOCKS4 or SOCKS5. |
|
|
List<Server> (Structural property) |
n/a |
This property has a customized constraint. |
Yes |
No |
Specifies the list of configured remote iSchedule servers |
The following properties are available for CalDAVService.ISchedule.Server:
Table 4-29 CalDAVService.ISchedule.Server Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
This property has a customized constraint. |
Yes |
No |
The iSchedule server domain regular expression is used for associating external email addresses to this iSchedule server configuration. |
|
|
String |
n/a |
This property has a customized constraint. |
Yes |
No |
Regular expression of allowed host names. Remote servers not matching this regular expression will not be able to send requests to the local server. |
|
|
String |
n/a |
This property has a customized constraint. |
Yes |
No |
Regular expression of allowed IP addresses. Remote servers not matching this regular expression will not be able to send requests to the local server. |
|
|
String |
n/a |
This property has a customized constraint. |
Yes |
No |
Specifies the name the remote server should use. If the remote server does not specify the good name, all requests sent from this remote server will be denied |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Specifies the key the remote server should use. If the remote server does not specify the good key, all requests sent from this remote server will be denied |
|
|
CalDAVService.ISchedule.Server.AuthMethod (Legal values: HTTP_BASIC) |
HTTP_BASIC |
All permitted values |
Yes |
No |
Authentication method to use for incoming remote server requests. |
|
|
String |
n/a |
This property has a customized constraint. |
No |
No |
The iSchedule server name is used to uniquely identify an iSchedule server configuration. |
|
|
String |
n/a |
This property has a customized constraint. |
Yes |
No |
Specifies the name to use when authenticating to the remote server. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Specifies key to use when authenticating to the remote server. |
|
|
String |
n/a |
This property has a customized constraint. |
Yes |
No |
The iSchedule server outgoing URL is used to specify the remote iSchedule receiver URL for this iSchedule server configuration. |
The following properties are available for ClientManagementService:
Table 4-30 ClientManagementService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
50 |
This property has a customized constraint. |
Yes |
No |
description bundle not set |
|
|
int |
100 |
This property has a customized constraint. |
Yes |
No |
description bundle not set |
|
|
int |
32768 |
Min=1, Max=65535 |
Yes |
No |
description bundle not set |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
int |
30000 |
This property has a customized constraint. |
Yes |
No |
description bundle not set |
|
|
int |
131072 |
This property has a customized constraint. |
Yes |
No |
description bundle not set |
|
|
int |
131072 |
This property has a customized constraint. |
Yes |
No |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for CoexistenceService:
Table 4-31 CoexistenceService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the Coexistence Service. If enabled and a coexistence connector is configured, the Coexistence Service will send and receive requests to and from the coexistence connector. |
|
|
n/a |
All permitted values |
No |
No |
Properties that are specific to the Oracle Coexistence Connector. This is a subcomponent. |
||
|
n/a |
All permitted values |
No |
No |
Properties that are specific to contacts in coexistence deployments. This is a subcomponent. |
||
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
n/a |
All permitted values |
No |
No |
Properties that are specific to free/busy time in coexistence deployments. This is a subcomponent. |
||
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
n/a |
All permitted values |
No |
No |
Properties that are specific to meetings in coexistence deployments. This is a subcomponent. |
||
|
n/a |
All permitted values |
No |
No |
Properties that are specific to e-mail messages in coexistence deployments. This is a subcomponent. |
||
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the request sender. If disabled, the Coexistence Service will not send any requests to the connector but will still process incoming requests. Propagation of changes also requires the CoexistenceEnabled property to be enabled. When disabled, the Coexistence Service will only process requests sent by the coexistence connector. |
|
|
n/a |
All permitted values |
No |
No |
Properties that are specific to tasks in coexistence deployments. This is a subcomponent. |
||
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
No other properties exist for CoexistenceService.ClusteredTaskProperties .
The following properties are available for CoexistenceService.ConnectorProperties:
Table 4-32 CoexistenceService.ConnectorProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the SMTP server host name used by the Oracle Coexistence Connector. If this property is not set, the virtual server name will be used. |
|
|
int |
25 |
This property has a customized constraint. |
Yes |
No |
Specifies the SMTP server port used by the Oracle Coexistence Connector. If this property is not set, the virtual server port will be used. |
The following properties are available for CoexistenceService.ContactProperties:
Table 4-33 CoexistenceService.ContactProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
2048 |
This property has a customized constraint. |
Yes |
No |
The maximum size allowed (in kilobytes) of an attachment. If an attachment is larger than this size, the attachment is ignored by the coexistence solution. Increasing this value can cause scalability issues in some flows. It is not recommended to increase this value above 10240. The recommended value is 2048. |
The following properties are available for CoexistenceService.ContainerSpecificProperties:
Table 4-34 CoexistenceService.ContainerSpecificProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
2048 |
This property has a customized constraint. |
Yes |
No |
The maximum size allowed (in kilobytes) of an attachment. If an attachment is larger than this size, the attachment is ignored by the coexistence solution. Increasing this value can cause scalability issues in some flows. It is not recommended to increase this value above 10240. The recommended value is 2048. |
The following properties are available for CoexistenceService.DominoProperties:
Table 4-35 CoexistenceService.DominoProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the SMTP server host name used by the Oracle Coexistence Connector. If this property is not set, the virtual server name will be used. |
|
|
int |
25 |
This property has a customized constraint. |
Yes |
No |
Specifies the SMTP server port used by the Oracle Coexistence Connector. If this property is not set, the virtual server port will be used. |
The following properties are available for CoexistenceService.ExchangeProperties:
Table 4-36 CoexistenceService.ExchangeProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the SMTP server host name used by the Oracle Coexistence Connector. If this property is not set, the virtual server name will be used. |
|
|
int |
25 |
This property has a customized constraint. |
Yes |
No |
Specifies the SMTP server port used by the Oracle Coexistence Connector. If this property is not set, the virtual server port will be used. |
The following properties are available for CoexistenceService.ExpertiseProfilingProperties:
Table 4-37 CoexistenceService.ExpertiseProfilingProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
2048 |
This property has a customized constraint. |
Yes |
No |
The maximum size allowed (in kilobytes) of an attachment for expertise profiling. If an attachment is larger than this size, the attachment is ignored by the coexistence solution. |
The following properties are available for CoexistenceService.FreeBusyProperties:
Table 4-38 CoexistenceService.FreeBusyProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
120 |
This property has a customized constraint. |
Yes |
No |
Specifies the upper limit (in days from today) of the range Oracle Beehive will use to publish free/busy information of coexisting users. This value can be any positive integer. For example, if this value is set to 60, Oracle Beehive will publish all free/busy information that occurs from the time of the request and for the following 60 days. This property is used in conjunction with PastTimePeriodInDay, which specifies the lower limit (in days) of the range for publishing free/busy information. |
|
|
int |
7 |
This property has a customized constraint. |
Yes |
No |
Specifies the lower limit (in days from today) of the range Oracle Beehive will use to publish free/busy information of coexisting Oracle Beehive users. This value can be any positive integer. For example, if this value is set to 30, Oracle Beehive will publish all free/busy information that occurs from the time of the request and for the previous 30 days. This property is used in conjunction with FutureTimePeriodInDay, which specifies the upper limit (in days) of the range for publishing free/busy information. |
No other properties exist for CoexistenceService.InstanceTaskProperties .
The following properties are available for CoexistenceService.MeetingProperties:
Table 4-39 CoexistenceService.MeetingProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
2048 |
This property has a customized constraint. |
Yes |
No |
The maximum size allowed (in kilobytes) of an attachment. If an attachment is larger than this size, the attachment is ignored by the coexistence solution. Increasing this value can cause scalability issues in some flows. It is not recommended to increase this value above 10240. The recommended value is 2048. |
|
|
int |
-1 |
All permitted values |
Yes |
No |
Specifies the upper limit (in days from today) of the range Oracle Beehive will use to request an initial import of meeting data from the Oracle Coexistence Connector. This value can be any positive integer or -1, which is used to specify that there is no upper limit. For example, if this value is set to 60, Oracle Beehive will import all meeting data that occurs from the time of the import and for the following 60 days. This property is used in conjunction with ImportDataPastTimePeriodInDay, which specifies the lower limit (in days) of the range for importing meeting data. |
|
|
int |
30 |
All permitted values |
Yes |
No |
Specifies the lower limit (in days from today) of the range Oracle Beehive will use to request an initial import of meeting data from the Oracle Coexistence Connector. This value can be any positive integer or -1, which is used to specify that there is no lower limit. For example, if this value is set to 30, Oracle Beehive will import all meeting data that occurs from the time of the request and for the previous 30 days. This property is used in conjunction with ImportDataFutureTimePeriodInDay, which specifies the upper limit (in days) of the range for importing meeting data. |
The following properties are available for CoexistenceService.MessageProperties:
Table 4-40 CoexistenceService.MessageProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
2048 |
This property has a customized constraint. |
Yes |
No |
The maximum size allowed (in kilobytes) of an attachment. If an attachment is larger than this size, the attachment is ignored by the coexistence solution. Increasing this value can cause scalability issues in some flows. It is not recommended to increase this value above 10240. The recommended value is 2048. |
|
|
int |
-1 |
All permitted values |
Yes |
No |
Specifies the upper limit (in days from today) of the range Oracle Beehive will use to request an initial import of e-mail data from the Oracle Coexistence Connector. This value can be any positive integer or -1, which is used to specify that there is no upper limit. For example, if this value is set to 60, Oracle Beehive will import all e-mail data that occurs from the time of the import and for the following 60 days. This property is used in conjunction with ImportDataPastTimePeriodInDay, which specifies the lower limit (in days) of the range for importing e-mail data. |
|
|
int |
30 |
All permitted values |
Yes |
No |
Specifies the lower limit (in days from today) of the range Oracle Beehive will use to request an initial import of e-mail data from the Oracle Coexistence Connector. This value can be any positive integer or -1, which is used to specify that there is no lower limit. For example, if this value is set to 30, Oracle Beehive will import all e-mail data that occurs from the time of the request and for the previous 30 days. This property is used in conjunction with ImportDataFutureTimePeriodInDay, which specifies the upper limit (in days) of the range for importing e-mail data. |
No other properties exist for CoexistenceService.ServiceManagerProperties .
The following properties are available for CoexistenceService.TaskProperties:
Table 4-41 CoexistenceService.TaskProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
2048 |
This property has a customized constraint. |
Yes |
No |
The maximum size allowed (in kilobytes) of an attachment. If an attachment is larger than this size, the attachment is ignored by the coexistence solution. Increasing this value can cause scalability issues in some flows. It is not recommended to increase this value above 10240. The recommended value is 2048. |
|
|
int |
-1 |
All permitted values |
Yes |
No |
Specifies the upper limit (in days from today) of the range Oracle Beehive will use to request an initial import of task data from the Oracle Coexistence Connector. This value can be any positive integer or -1, which is used to specify that there is no upper limit. For example, if this value is set to 60, Oracle Beehive will import all active task data from the time of the import and for the following 60 days. This property is used in conjunction with ImportDataPastTimePeriodInDay, which specifies the lower limit (in days) of the range for importing task data. |
|
|
int |
30 |
All permitted values |
Yes |
No |
Specifies the lower limit (in days from today) of the range Oracle Beehive will use to request an initial import of task data from the Oracle Coexistence Connector. This value can be any positive integer or -1, which is used to specify that there is no lower limit. For example, if this value is set to 30, Oracle Beehive will import all active task data from the time of the request and for the previous 30 days. This property is used in conjunction with ImportDataFutureTimePeriodInDay, which specifies the upper limit (in days) of the range for importing task data. |
No other properties exist for CompositeStateManageable .
The following properties are available for ConferenceMonitoringService:
Table 4-42 ConferenceMonitoringService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
Yes |
description bundle not set |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for ConferenceService:
Table 4-43 ConferenceService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Integer |
3600000 |
All permitted values |
No |
No |
description bundle not set |
|
|
String |
audio/IP-MR-VBR |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Integer |
3600 |
All permitted values |
No |
No |
description bundle not set |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Integer |
1800000 |
All permitted values |
No |
No |
description bundle not set |
|
|
Integer |
30000 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
String |
owc-ms-host-service |
All permitted values |
Yes |
No |
description bundle not set |
|
|
String |
balance |
All permitted values |
Yes |
No |
description bundle not set |
|
|
String |
owc-roster-service |
All permitted values |
Yes |
No |
description bundle not set |
|
|
String |
balance |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Integer |
5060 |
Network Port, Min=1, Max=65536 |
Yes |
No |
description bundle not set |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for ConferenceSessionService:
Table 4-44 ConferenceSessionService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
No other properties exist for ConnectionPoolConsumer .
The following properties are available for CustomService:
Table 4-45 CustomService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for Database:
Table 4-46 Database Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
List<AccessSchema> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The database access Schemas. |
|
|
n/a |
All permitted values |
Yes |
Yes |
The affinity ConnectionPool. |
||
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The list of services that require database affinity. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The database name for business data service. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The database name for configuration store. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The connect descriptor for the database. |
|
|
n/a |
All permitted values |
Yes |
Yes |
The database access Schema. |
||
|
n/a |
All permitted values |
Yes |
Yes |
The default non-XA connectionPool. |
||
|
n/a |
All permitted values |
Yes |
Yes |
The default XA connectionPool. |
||
|
String |
n/a |
All permitted values |
Yes |
No |
The database name for diagnosibility service. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The database name for event listener service. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The list of ONS node configuration. |
|
|
n/a |
All permitted values |
No |
Yes |
long description key not set |
||
|
String |
n/a |
All permitted values |
Yes |
No |
The database name for read-only business data service. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The database name for search service. |
The following properties are available for Database.AccessSchema:
Table 4-47 Database.AccessSchema Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
If business data is supported. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If configuration data is supported. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If Diagnostic data is supported. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If event data is supported. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
The password of the access schema. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If read only DB is supported. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If search data is supported. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If user data is supported. |
|
|
String |
BEE_CODE |
All permitted values |
Yes |
No |
The username of the access schema. |
The following properties are available for Database.AffinityPool:
Table 4-48 Database.AffinityPool Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The timeout for abandoned connection. |
|
|
int |
10000 |
Min=1, Max=2147483647 |
Yes |
No |
The limit of the maximum retry attempt. |
|
|
Map<String,String> |
n/a |
All permitted values |
Yes |
No |
Time out for establishing a DB Connection. |
|
|
int |
300 |
Min=0, Max=2147483647 |
Yes |
No |
The timeout for connection wait. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The timeout for inactive connection. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The initial connection count of this connection pool. |
|
|
int |
20 |
Min=0, Max=100 |
Yes |
No |
The limit of LowerThreshold. |
|
|
int |
20 |
Min=0, Max=2147483647 |
Yes |
No |
The maximum connection count of this connection pool. |
|
|
int |
3 |
Min=0, Max=2147483647 |
Yes |
No |
The limit of the maximum retry attempt. |
|
|
int |
30000 |
Min=0, Max=2147483647 |
Yes |
No |
The limit of the maximum retry time. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The maxium statement count of this connection pool. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The minimum connection count of this connection pool. |
|
|
int |
900 |
Min=1, Max=2147483647 |
Yes |
No |
The interval to check property. |
|
|
int |
300000 |
Min=1, Max=2147483647 |
Yes |
No |
Time out for Read operation. |
|
|
int |
60 |
Min=1, Max=2147483647 |
Yes |
No |
Time interval (in seconds) between two consecutive affinity service status checks. |
|
|
int |
30 |
Min=1, Max=2147483647 |
Yes |
No |
While fetching the DB Connections, Number of consecutive SQLException exception tolerate before updating the affinity service status as down. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The timeout for timeToLive. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If the connectionPool needs to validate a connection. |
The following properties are available for Database.ConnectionPool:
Table 4-49 Database.ConnectionPool Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The timeout for abandoned connection. |
|
|
int |
10000 |
Min=1, Max=2147483647 |
Yes |
No |
The limit of the maximum retry attempt. |
|
|
Map<String,String> |
n/a |
All permitted values |
Yes |
No |
Time out for establishing a DB Connection. |
|
|
int |
300 |
Min=0, Max=2147483647 |
Yes |
No |
The timeout for connection wait. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The timeout for inactive connection. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The initial connection count of this connection pool. |
|
|
int |
20 |
Min=0, Max=100 |
Yes |
No |
The limit of LowerThreshold. |
|
|
int |
20 |
Min=0, Max=2147483647 |
Yes |
No |
The maximum connection count of this connection pool. |
|
|
int |
3 |
Min=0, Max=2147483647 |
Yes |
No |
The limit of the maximum retry attempt. |
|
|
int |
30000 |
Min=0, Max=2147483647 |
Yes |
No |
The limit of the maximum retry time. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The maxium statement count of this connection pool. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The minimum connection count of this connection pool. |
|
|
int |
900 |
Min=1, Max=2147483647 |
Yes |
No |
The interval to check property. |
|
|
int |
300000 |
Min=1, Max=2147483647 |
Yes |
No |
Time out for Read operation. |
|
|
int |
0 |
Min=0, Max=2147483647 |
Yes |
No |
The timeout for timeToLive. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If the connectionPool needs to validate a connection. |
No other properties exist for DeletedSystemObject .
The following properties are available for DeviceManagementService:
Table 4-50 DeviceManagementService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Collection<BlockedDevice> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of devices that will not be allowed to access Oracle Beehive services. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Whether or not Oracle Beehive will allow uncertified devices to access the system. |
The following properties are available for DeviceManagementService.BlockedDevice:
The following properties are available for DiagnosabilitySettings:
Table 4-52 DiagnosabilitySettings Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
Yes |
The default properties used by Error Code DB Persistence and Error Code log records |
||
|
n/a |
All permitted values |
Yes |
Yes |
Subobject with properties for the Diagnosability Context |
||
|
Boolean |
false |
All permitted values |
Yes |
No |
When enabled, some error code occurrences will be persisted to the database, based on the the values of the sub-objects BaseErrorCodeProperties and ErrorCodeDBProperties. |
|
|
n/a |
All permitted values |
Yes |
No |
If exists, this object overrides the values in BaseErrorCodeProperties for Error Code Database persistence. |
||
|
n/a |
All permitted values |
Yes |
No |
If exists, this object overrides the values in BaseErrorCodeProperties for Error Code log records. |
||
|
Boolean |
false |
All permitted values |
Yes |
No |
Enable the instrumentation of requests with the diagnosability probe. |
|
|
n/a |
All permitted values |
Yes |
Yes |
description not found Can't find resource for bundle oracle.ocs.management.model.SystemModelBundle, key DIA_CFG_PROBE_PROPS_LONG |
The following properties are available for DiagnosabilitySettings.ContextProperties:
Table 4-53 DiagnosabilitySettings.ContextProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
If enabled, Stack traces within each service will be propagated to any callee services |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Enable Diagnosability Context propagation. If disabled, ECID, service instance stacks, and caller stacks will not be propagated over CSI calls or to the Database. |
The following properties are available for DiagnosabilitySettings.ErrorCodeProperties:
Table 4-54 DiagnosabilitySettings.ErrorCodeProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
If set, none of these error codes listed will be reported, in conjunction with ReportingSeverityThreshold. This property and IncludedErrorCodes cannot be set at the same time. |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
If enabled, stack traces will be included with each reported Error Code occurrence. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
If set, only the list of error codes here will be persisted. It is not recommended that this property be set. This property and ExcludedErrorCodes cannot be used at the same time. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
FINER |
All permitted values |
Yes |
No |
All error codes reported to log files, will be written at this severity level. This property is ignored by Error Code database persistence. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
INFO |
All permitted values |
Yes |
No |
Minimum Error Code severity required to report an Error Code occurrence, to the applicable persistence type |
|
|
int |
30 |
This property has a customized constraint. |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.SystemModelBundle, key DIA_CFG_EC_UPLOAD_INTERVAL_LONG |
The following properties are available for DiagnosabilitySettings.ProbeProperties:
Table 4-55 DiagnosabilitySettings.ProbeProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
true |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.SystemModelBundle, key DIA_PROBE_LW_LONG |
|
|
int |
10485760 |
This property has a customized constraint. |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.SystemModelBundle, key DIA_PROBE_MAX_SIZE_LONG |
|
|
int |
60 |
This property has a customized constraint. |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.SystemModelBundle, key DIA_PROBE_PERSISTENCE_INTERVAL_LONG |
|
|
String |
n/a |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.SystemModelBundle, key DIA_PROBE_STORAGE_LOC_LONG |
The following properties are available for DiscussionsService:
Table 4-56 DiscussionsService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for EmailService:
Table 4-57 EmailService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
No |
Yes |
A group of properties associated with Email CSI interface implementation behavior. Email CSI performance and memory footprint can be tuned via these properties. |
||
|
boolean |
false |
All permitted values |
Yes |
No |
If true, Coexisting users (sometimes referred to as users with a remote Inbox) will have their email forwarded to another server via the routing rules of the system. If false, the property indicating that the Inbox is remote is ignored. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
long |
60000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
Maximum time (in milliseconds) that an address will remain cached within the server. Note that this becomes the maximum time for a change to a users information (email address) or a group membership before changes are seen. |
|
|
String |
default |
All permitted values |
Yes |
No |
The domain name used throughout the system. Note: This value may be overridden in certain parts of the system. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Specifies whether or not Oracle Beehive's native Internet Message Access Protocol (IMAP) services are enabled. Valid values: true, false |
|
|
n/a |
All permitted values |
No |
Yes |
A group of properties associated with the IMAP server component. IMAP server is responsible for serving user requests to read and manage emails in their mailboxes. |
||
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The list of valid e-mail address patterns for users of the system |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
8192 |
Min=0, Max=2147483647 |
Yes |
No |
The maximum number of resolved e-mail addresses that the system will cache in memory |
|
|
long |
50000000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
The maximum size of an e-mail allowed by the system. The system will reject e-mail messages that exceed this threshold. Note this value is invlusive of the entire message (headers, attachments, etc). |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The list of valid e-mail address patterns to which the system will forward e-mail messages. Typically, this property is used to specify patterns for e-mail addresses that are hosted on other systems. |
|
|
n/a |
All permitted values |
No |
Yes |
A group of properties associated with email service persistence cache. Persistence cache is responsible for managing email message content cache in the middle tier. |
||
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Specifies whether or not Oracle Beehive's native Simple Mail Transport Protocol (SMTP) service is enabled. Valid values: true, false |
|
|
n/a |
All permitted values |
No |
Yes |
A group of properties associated with SMTP server component. SMTP server is responsible for accepting email traffic from remote hosts and commit delivering responsibility for email messages. |
||
|
boolean |
false |
All permitted values |
Yes |
No |
Specifies whether or not the system will save e-mail messages that it cannot parse. The system will save unparsed e-mail messages in a local directory under the persistent storage root. Valid values: true, false |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Whether senders should be sorted by email address without the displayed name portion in the web client. With this value set to false, senders will be sorted by the displayed name instead |
|
|
List<String> |
[(^\[[fF][wW][dD]:( )*)((.)*)(\]$), 3] |
All permitted values |
Yes |
No |
List of regular expressions and group numbers, interleaved so item i+1 denotes group to be returned for matched expression i where i = sequence 0, 2, 4,... etc. |
|
|
List<String> |
[[\t\n\r], , ^( )+, , ( )+$, , ( )+, , ^([rR][eE]|[fF][wW][dD]?):, , \([fF][wW][dD]\)$, ] |
All permitted values |
Yes |
No |
List of regular expressions and replacement strings, interleaved so item i+1 denotes replacement string for matched expression i where i = sequence 0, 2, 4,... etc. |
|
|
long |
60000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
The best resolution (precision) for any timeout in the email system. Applies to several protocols and facilities. This is the tolerance band for any email-related timeout. |
|
|
n/a |
All permitted values |
No |
Yes |
A group of properties associated with email service transport component. Transport component is responsible for processing and delivering email messages to their detinations. |
||
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for EmailService.CSIProperties:
Table 4-58 EmailService.CSIProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
20000 |
Min=0, Max=500000 |
Yes |
No |
Max number of items to load in a single CSI load request if the load is requested with any projection other than EMPTY. Otherwise the number is unlimited. This prevents client requests to cause out of memory errors on the server side. It is recommended that this parameter to be tuned assuming each item takes approximately 10KB of memory footprint. |
|
|
int |
8192 |
Min=0, Max=2147483647 |
Yes |
No |
The size (in bytes) of the buffered streams used for CSI based streaming |
|
|
int |
16384 |
Min=0, Max=2147483647 |
Yes |
No |
CSI based stream max read chunk size in bytes |
|
|
int |
16384 |
Min=0, Max=2147483647 |
Yes |
No |
CSI based stream max write chunk size in bytes |
|
|
int |
0 |
Min=-1, Max=2147483647 |
Yes |
No |
CSI based stream pre-fetch buffer size in bytes |
|
|
long |
300000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
Timeout (in relative milliseconds) until an inactive stream of mail data is abandoned, under the assumption the client has lost connectivity with the server or has crashed. |
|
|
String |
OutboundVMS |
All permitted values |
Yes |
No |
Use this VMS Properties object as a policy to enforce upon all CSI email requests. In particular all CSI Email request will be subject to the limit placed by the VMS Properties MaxRcptsPerTx and MaxSzAbortTxn. |
The following properties are available for EmailService.EndpointProperties:
Table 4-59 EmailService.EndpointProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
default |
All permitted values |
Yes |
No |
Name of the endpoint, it can be any arbitrary descriptive string identifying the endpoint |
|
|
String |
default |
All permitted values |
Yes |
No |
Scheme for this endpoint. It is a colon-delimited string containing protocol of the endpoint and port number. The format of the scheme is PROTOCOL:*:PORT, for example, MX:*:25 represent a beehive MX endpoint connection on port 25. Available protocols are MX, MXS (MX over SSL), TCP and BUS. |
The following properties are available for EmailService.IMAPProperties:
Table 4-60 EmailService.IMAPProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
true |
All permitted values |
Yes |
No |
If this property is true, the Port property will be used as the listening port. This is a simplification over the more complex list of Endpoints which permit multiple ports for a single instance. |
|
|
long |
12 |
Min=1, Max=9223372036854775807 |
Yes |
No |
Property giving the approximate size in bytes of each message cached in memory |
|
|
long |
10000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
Get the interval after which some unsolicited response is sent to a client to keep it active (in millseconds) |
|
|
List<EndpointProperties> (Structural property) |
n/a |
All permitted values |
Yes |
No |
If Assume Single Endpoint is false, this property defines a list of listening endpoints. |
|
|
String |
../../beehive/mailspool/temp/imap |
All permitted values |
Yes |
No |
The IMAP folder cache directory. IMAP will store temporary files in this directory |
|
|
int |
1000 |
Min=1, Max=2147483647 |
Yes |
No |
Property controlling the batch size IMAP uses to drain the cursor while opening a folder for SELECT or EXAMINE. Setting a small number will reduce memory usage but will impact performance |
|
|
long |
20000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
The interval by-which the database is polled for changes to the currently selected IMAP folder |
|
|
int |
50 |
Min=1, Max=2147483647 |
Yes |
No |
Get the batch size used for checking updates to folders |
|
|
int |
3 |
Min=0, Max=2147483647 |
Yes |
No |
Get the number of login errors tolerated before the connection is forcibly closed. |
|
|
long |
52428800 |
Min=0, Max=2147483647 |
Yes |
No |
Property controlling the maximum amount of memory available for IMAP folder caching |
|
|
int |
1024 |
Min=0, Max=2147483647 |
Yes |
No |
Maximum number of IMAP sessions server will permit per service instance |
|
|
int |
50 |
Min=0, Max=100 |
Yes |
No |
Property controlling the batch size IMAP uses to load messages from the database. Setting a small number will reduce memory usage but will impact performance. A larger number will improve performance but will increase memory usage per selected folder |
|
|
int |
3 |
Min=0, Max=2147483647 |
Yes |
No |
The number of consecutive parser errors tolerated before the connection is forcibly closed. |
|
|
int |
143 |
Network Port, Min=1, Max=65536 |
Yes |
No |
If the property Assume Single Endpoint is enabled (true), then this is the port which the IMAP server will use to accept new connections. If Assume Single Endpoint is false, this property is ignored. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Whether IMAP protocol logging is enabled. If enabled, IMAP protocol exchange will be captured and logged under logger oracle.ocs.mail.IMAPLogger with log level INFO. |
|
|
int |
23 |
Min=1, Max=2147483647 |
Yes |
No |
Max number of concurrent sessions which can be serviced as a given moment |
|
|
long |
1800000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
The duration in millseconds after which inactive IMAP sessions are automatically logged out and closed. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Show IMAP server instance ID in protocol banner display, it identifies a specific application server process that hosts the IMAP server. This can be enabled to help diagnostics when problem arises. |
|
|
int |
32768 |
Min=1, Max=2147483647 |
Yes |
No |
Size of temp buffer used when reading from a client stream |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, IMAP allows surrogate authentication during login |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, when UseTls is enabled IMAP makes STARTTLS mandatory. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, IMAP advertises STARTTLS capability. |
The following properties are available for EmailService.PersistenceProperties:
Table 4-61 EmailService.PersistenceProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
1000 |
Min=1, Max=1000 |
Yes |
No |
Batch size for copy operation. This parameter controls how many messages to copy at a time when the request is huge. Breaking the operation in chunks put less strain on the database |
|
|
String |
1000,5000,9000 |
All permitted values |
Yes |
No |
Attempts to retry a database operation on connection failure. This is employed to support automatic fail-over on clustered database systems. The value is a comma delimited list of successive retry intervals in miliseconds. |
|
|
int |
100 |
Min=1, Max=100 |
Yes |
No |
Batch size for delete operation. This parameter controls how many messages to delete at a time when the request is huge. Breaking the operation in chunks put less strain on the database |
|
|
String |
../../beehive/mailspool/perm |
All permitted values |
Yes |
No |
Root directory under which problematic emails will be saved. This directory should be visible only to the operating system user of the instance, as it contains sensitive data (emails). If a relative path is used rather than absolute, it will be relative to the home directory of the instance |
|
|
int |
1000 |
Min=1, Max=1000 |
Yes |
No |
Batch size for move operation. This parameter controls how many messages to move at a time when the request is huge. Breaking the operation in chunks put less strain on the database |
|
|
long |
180000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
Time (in milliseconds) for an unreferenced record to linger in the cache |
|
|
int |
86400 |
Min=0, Max=2147483647 |
Yes |
No |
Interval (in seconds) for performing payload store cleanup |
|
|
int |
2000 |
Min=0, Max=2147483647 |
Yes |
No |
Maximum number of memory cached records for payload store |
|
|
int |
1000 |
Min=0, Max=2147483647 |
Yes |
No |
Maximum number of open file descriptors used as cache of files being read/written by payload store |
|
|
int |
50000 |
Min=0, Max=2147483647 |
Yes |
No |
Size of a cached payload record (in bytes). |
|
|
int |
8192 |
Min=0, Max=2147483647 |
Yes |
No |
The size (in bytes) of the buffered streams used for file-cached records |
|
|
String |
../../beehive/mailspool/temp |
All permitted values |
Yes |
No |
Root directory under which temporary emails will be written to disk. This directory should be visible only to the operating system user of the instance, as it contains sensitive data (emails). If a relative path is used rather than absolute, it will be relative to the home directory of the instance. |
|
|
int |
1000 |
Min=1, Max=1000 |
Yes |
No |
Batch size for undelete operation. This parameter controls how many messages to undelete at a time when the request is huge. Breaking the operation in chunks put less strain on the database |
|
|
int |
1000 |
Min=1, Max=1000 |
Yes |
No |
Batch size for update operation. This parameter controls how many messages to update at a time when the request is huge. Breaking the operation in chunks put less strain on the database |
The following properties are available for EmailService.SMTPProperties:
Table 4-62 EmailService.SMTPProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
true |
All permitted values |
Yes |
No |
If this property is true, the Port property will be used as the listening port. This is a simplification over the more complex list of Endpoints which permit multiple ports for a single instance. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, the system will advertise the SMTP AUTH extension. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
If true Delivery Status Notifications are sent when requested by client or by protocol convention |
|
|
List<EndpointProperties> (Structural property) |
n/a |
All permitted values |
Yes |
No |
If Assume Single Endpoint is false, this property defines a list of listening endpoints. |
|
|
int |
25 |
Network Port, Min=1, Max=65536 |
Yes |
No |
If the property Assume Single Endpoint is enabled (true), then this is the port which the SMTP server will use to accept new connections. If Assume Single Endpoint is false, this property is ignored. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Whether SMTP protcol exchange is logged. If enabled, SMTP protocol exchange will be captured and logged under logger oracle.ocs.mail.SMTPLogger with log level INFO |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Whether SMTP outbound protcol exchange is logged. If enabled, SMTP outbound exchange will be captured and logged under logger oracle.ocs.mail.SMTPRelayLogger with log level INFO |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, SMTP outbound sends mail even if remote server doesn't support TLS or STARTTLS command fails. |
|
|
int |
23 |
Min=1, Max=2147483647 |
Yes |
No |
SMTP server thread pool size |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, the system will advertise the SMTP STARTTLS extension. |
|
|
String |
default |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.EmailServiceBundle, key SMTP_VMS_EVALUATOR_TOPLEVEL_LONG_DESC |
|
|
List<VMSProperties> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of virtual mail servers for this instance. |
The following properties are available for EmailService.SMTPProperties.VMSProperties:
Table 4-63 EmailService.SMTPProperties.VMSProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
If true and Authentication is enabled, SMTP requires authentication before accepting mail. |
|
|
String |
server |
All permitted values |
Yes |
No |
The custom name of the server, as will be seen on the initial salutation of the SMTP protocol. Note that this property is not read unless Use Default Display Name is set to false. |
|
|
String |
default |
All permitted values |
Yes |
No |
A domain name for this virtual mail server which differs from the system-wide domain name. This property is not used unless Use Default Domain Name is set to false. |
|
|
String |
default |
All permitted values |
Yes |
No |
A custom version of the product, different than that which shipped from Oracle. This property is not used unless Use Custom Default Product Version is set to false. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Should all exceptions be logged. Setting to false prevents reporting of the (many types of) problems that can occur with remote clients (esp in the Internet). |
|
|
int |
100 |
Min=1, Max=2147483647 |
Yes |
No |
Maximum number of aborted transactions per session before the client is assumed to be engaging in some form of denial-of-service attack and is terminated. |
|
|
int |
20 |
Min=1, Max=2147483647 |
Yes |
No |
Maximum number of illegal (out of sequence) SMTP commands before the session is assumed to be an attacker and is closed. |
|
|
int |
2048 |
Min=1, Max=2147483647 |
Yes |
No |
Maximum size (in bytes) of a single SMTP line. Note that this value should not be set to the minimum defined in the SMTP specification, as some legitimate mail servers violate that specification. Rather, this value is intended to be large enough to accept mails from poor-conforming mail servers yet reject attempts at denial of service or buffer overflow attacks. |
|
|
int |
101 |
Min=1, Max=2147483647 |
Yes |
No |
Maximum number of recipients per transaction. It is advised to set this number above 100 as per the SMTP specification. When this number is exceeded, subsequent RCPT TO commands will receive an error. |
|
|
int |
1000 |
Min=0, Max=2147483647 |
Yes |
No |
Maximum number of rejected recipients before a given session is assumed to be illegitimate, and it terminated. This is useful to prevent address-harvesting by senders of unwanted email. |
|
|
long |
1000000000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
Maximum email size received before the client is assumed to be engaged in a denial of service attack. Once this threshold is crossed, the client session is abruptly terminated. Note that this differs from Max Mail Size in that mails exceeding that value do not result in termination of the entire session. |
|
|
long |
10000000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
Maximum size for an email on this virtual mail server. Note that Use Default Max Size must be set to false for this property to be read. |
|
|
int |
5000 |
Min=0, Max=2147483647 |
Yes |
No |
Maximum number of commands with no effect (e.g. NOOP) per session before we assume that the client is engaged in some form of denial of service attack. |
|
|
int |
301000 |
Min=1, Max=2147483647 |
Yes |
No |
Inactivity timeout (in milliseconds) for clients between issuing commands. Note that this does not include the SMTP DATA command. |
|
|
int |
301000 |
Min=1, Max=2147483647 |
Yes |
No |
Timeout (in milliseconds) waiting for next packet during the receive portion of the DATA command. |
|
|
int |
60000 |
Min=1, Max=2147483647 |
Yes |
No |
Timeout (in milliseconds) waiting for remote client to consume the ACK of the QUIT command |
|
|
String |
default |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.EmailServiceBundle, key VMS_RECIPIENT_MATCHER_TOPLEVEL_LONG_DESC |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, this virtual mail server will reject all connections. |
|
|
String |
default |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.EmailServiceBundle, key VMS_SENDER_MATCHER_TOPLEVEL_LONG_DESC |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Show SMTP server instance ID in protocol banner display, it identifies a specific application server process that hosts the SMTP server. This can be enabled to help diagnostics when problem arises. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, the client IP/hostname will not be embedded in the RECEIVED header added to email headers. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, SMTP responses to not carry the debugging information in addition to the SMTP codes. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true and UseTls is enabled, SMTP requires TLS. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If false, the Custom Display Name is used. Otherwise, the original product name is used. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
If false, this virtual mail server will advertise a domain different than the rest of the system. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
If false, the global maximum email size will not be used and instead the Max Email Size defined for this virtual mail server will be used. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If false, the Custom Product Version is returned as part of the SMTP salutation |
|
|
String |
default |
All permitted values |
Yes |
No |
The administrator-assigned name of this virtual mail server. |
The following properties are available for EmailService.TransportProperties:
Table 4-64 EmailService.TransportProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
Indicates if non-existant local users should be accepted by the system and treated as remote recipients. Should be set to true when users for a single domain exist in this and another email system. |
|
|
int |
5 |
Min=1, Max=2147483647 |
Yes |
No |
The maximum number of concurrent threads which will be dedicated to delivering a given email. This is employed when a single email is destined for a large number of recipients, and serves to prevent high-recipient emails from consuming excessive system resources. |
|
|
String |
default |
All permitted values |
Yes |
No |
XML encoded delivery routing rules. This includes both properties settable from beekeeper and possible freelance groovy scripts. These rules are applied to determine the next stop for any given mail being relayed. |
|
|
int |
250 |
Min=0, Max=2147483647 |
Yes |
No |
Maximum number of emails received at a given instance which have yet to be processed. This can be thought of as a backlog of emails. Should this value be exceeded, emails will be received but not processed at the current instance. |
|
|
long |
300000 |
Min=60000, Max=9223372036854775807 |
Yes |
No |
Time (in milliseconds) between server registration to signal its alive status by the email service instance. |
|
|
int |
100 |
Min=1, Max=2147483647 |
Yes |
No |
Number of recipients in a batch of local recipients. Local recipients are those who maintain an inbox within the current system. |
|
|
int |
25 |
All permitted values |
Yes |
No |
Max number of "Received:" allowed in a message before it is discarded. A high number of this header present in a message signals a possible routing loop. |
|
|
long |
432000000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
Time (in milliseconds) after receipt of an email that delivery is no longer attempted. |
|
|
int |
80 |
Min=0, Max=100 |
Yes |
No |
Maximum percentage of queue size reserved for retry and recovery. An idle system with relatively high server restart requirements or relatively high temporary delivery failure (such as due to quota overflow) can increase this value to improve efficiency of the system. |
|
|
int |
20 |
Min=0, Max=100 |
Yes |
No |
Minimum percentage of queue size reserved for retry and recovery. An idle system with relatively high server restart requirements or relatively high temporary delivery failure (such as due to quota overflow) can increase this value to improve efficiency of the system. |
|
|
String |
default |
All permitted values |
Yes |
No |
XML encoded message terminus rules. This includes both properties settable from beekeeper and possible freelance groovy scripts. These rules are applied when a given message ends its lifecycle in the email transport system, including successful delivery or permanent failure of all its recipients. |
|
|
String |
default |
All permitted values |
Yes |
No |
XML encoded pre-resolution rules including both properties settable from beekeeper and possible freelance groovy scripts. These rules are to be applied during message processing before any of the recipients are resolved |
|
|
boolean |
true |
All permitted values |
Yes |
No |
If this value is false, it has the effect of preventing any received/delayed emails from being delivered. |
|
|
long |
120000 |
Min=0, Max=9223372036854775807 |
Yes |
No |
Time (in milliseconds) between retry and recovery queue polling by the transport system. |
|
|
String |
default |
All permitted values |
Yes |
No |
If the property Simple Relay Mode is true, then this is the name of the relay server to be used. |
|
|
String |
default |
All permitted values |
Yes |
No |
XML encoded post-resolution rules including both properties settable from beekeeper and possible freelance groovy scripts. These rules are to be applied during message processing after all the recipients are resolved. |
|
|
int |
1800000 |
Min=-1, Max=2147483647 |
Yes |
No |
Time (in milliseconds) between delivery attempts for an email which has at least one undeliverable recepient. |
|
|
int |
100 |
Min=1, Max=2147483647 |
Yes |
No |
The maximum number of recipients within a given SMTP transaction. As per the specifications for SMTP, this value should not exceed 100. |
|
|
int |
5 |
Min=1, Max=2147483647 |
Yes |
No |
This value controls how often the status of recipients is recorded during delivery of messages to large number of recipients/domains. If this value is small, there is less of a chance of duplicate mail in the event of a system crash. However, smaller settings for this value result in more system load. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If true, emails are scanned as they are uploaded to the system. Upload includes IMAP APPEND as well as API calls which insert, rather than send, emails. Scanning on send is controlled by the pre/post resolution rules. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Whether plug-ins are enabled to be executed after a mail is received. These are internal bookkeeping plugins designed for record management or auditing. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
If true, the XML-based Delivery Rules are not used. Instead, a simpler configuration is assumed where the administrator need only supply a relay host (via the Relay Server property). If this value is true yet the Relay Server is unset, an error will be issued and email delivery will be prevented. |
|
|
int |
10 |
Min=1, Max=2147483647 |
Yes |
No |
Number of threads within the processing thread pool |
The following properties are available for Enterprise:
The following properties are available for EventService:
Table 4-66 EventService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
5 |
All permitted values |
Yes |
No |
The Event Service will retry the specified number of times when the action handler fails to process the event. The Event Service moves the event to the failed queue after it has retried the specified number of times. Also see AsyncActionRetryInterval parameter. |
|
|
int |
5 |
All permitted values |
Yes |
No |
Time interval in minutes between retries of failed action. Also see AsyncActionRetryCount parameter. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
WARNING |
All permitted values |
Yes |
No |
The log level is used by the Business Event processing engine to determine the detail of the logs written. The log level of FINEST will write the most detailed log messages, and SEVERE will log the least. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
10 |
All permitted values |
Yes |
No |
A correctly sized thread pool will be able to keep up with the load of the java action queue. If the action queue keeps growing, and the Event Service is not able to keep up with the load, then this value should be increased. Be aware a larger pool size may require more database and mid-tier resources to keep up with the load. |
|
|
int |
1000 |
All permitted values |
Yes |
No |
The purpose of this parameter is to tune the overall system performance in regards to event processing. The threshold number is in relationship to the total number of subscription conditions (or rules) per event type (such as DOCUMENT, EMAIL, CALENDAR, etc.). If this number is smaller than the total number of rules, and the total number of rules is very large, it is possible that pre-evaluating the rules can take more time. If this number is larger than the total number of rules, the Event Service will not pre-evaluate any rules. It will automatically queue all events which may not have any matching subscriptions, and therefore not be very efficient. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for ExpertiseService:
Table 4-67 ExpertiseService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
List<String> |
[English] |
This property has a customized constraint. |
Yes |
No |
This property specifies the list of languages which are active. Currently, the supported languages are English, French and German |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Flag to enable periodic expiration of ExpertiseRequests. A request is said to expire if there has been no activity (posts to dicsussion forum) prior to the expiration interval. Expired requests will be periodically purged from the system. The allowed values are true or false. |
|
|
int |
90 |
This property has a customized constraint. |
Yes |
No |
Interval in days after which an Expertise Request is said to expire, if there has been no activity (posts to dicsussion forum) for it. The interval must be somewhere between 30 days and 180 days. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
15728640 |
This property has a customized constraint. |
Yes |
No |
This property specifies the maximum size of an artifact that would be profiled. The default value is 15728640 bytes which is equivalent to 15 megabytes. |
|
|
int |
100 |
This property has a customized constraint. |
Yes |
No |
This property specifies the maximum number of public terms a user can have in her profile. This is a global setting applicable to all users. The default value is 100 |
|
|
int |
10000 |
This property has a customized constraint. |
Yes |
No |
This property specifies the maximum number of terms a user can have in her profile. This is a global setting applicable to all users. A valid value is anything between 500 and 10000. The default value is 10000 |
|
|
int |
50 |
This property has a customized constraint. |
Yes |
No |
This property specifies the maximum number of size to whom brokered requests would be sent. The default value is set at 50. Any positive value upto 100 is acceptable. |
|
|
int |
90 |
This property has a customized constraint. |
Yes |
No |
This property specifies the number of days to go back in time to fetch content (messages) for profiling for bootstrapped users. The default value is set at 90 days. Any value upto 365 days is acceptable. |
|
|
int |
10 |
This property has a customized constraint. |
Yes |
No |
This property specifies the number of threads of the profiler that could run. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for ExternalJ2eeApplication:
Table 4-68 ExternalJ2eeApplication Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
the password of the oc4j admin user |
|
|
String |
oc4jadmin |
All permitted values |
Yes |
No |
the name of the oc4j admin user |
|
|
String |
n/a |
All permitted values |
Yes |
No |
the hostname used for generating urls to access the application. |
|
|
String |
n/a |
All permitted values |
No |
No |
the name of the oc4j |
|
|
int |
n/a |
All permitted values |
Yes |
No |
the opmn request port for generating urls to access the application. |
The following properties are available for FaxMessageService:
Table 4-69 FaxMessageService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Integer |
n/a |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for FtpService:
Table 4-70 FtpService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.FtpBundle, key FTP_ENABLE_ACTIVE_LONG_DESC |
|
|
String |
PLAIN_AND_TLS |
All permitted values |
Yes |
No |
Specifies the types of connections the system will accept.Valid values are TLS, PLAIN and PLAIN_TLS. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Collects DMS statistics if the value is set to TRUE. |
|
|
int |
21000 |
Network Port, Min=1, Max=65536 |
Yes |
No |
Starting port number from which FTP data connections are created in passive mode. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
String |
UTF-8 |
All permitted values |
Yes |
No |
Default command character set used to interpret FTP commands and arguments. |
|
|
int |
2120 |
Network Port, Min=1, Max=65536 |
Yes |
No |
The default data port number from which the FTP server will make outbound connections in PORT mode.. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Specifies whether or not the BEEHIVE FTP server is enabled. If enabled (true), the FTP server accepts client requests. Valid values: true, false. |
|
|
String |
DEFAULT |
All permitted values |
Yes |
No |
This parameter gives the IP address that needs to be returned as response to PASV command for DMZ deployments. |
|
|
String |
DEFAULT |
All permitted values |
Yes |
No |
Listening points (network interface groups) that the system's FTP server will support. Valid values are : INTERNAL, EXTERNAL, DEFAULT and INTERNAL_EXTERNAL. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
1000 |
All permitted values |
Yes |
No |
The maximum number of ports the FTP service can use for passive listening. |
|
|
int |
2121 |
Network Port, Min=1, Max=65536 |
Yes |
No |
The port at which the FTP server listens for client requests. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
int |
900000 |
All permitted values |
Yes |
No |
The amount of time (in milliseconds) that the FTP server will wait for a request from a connected client before terminating the session.. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
int |
260096 |
Min=16384, Max=1048576 |
Yes |
No |
The buffer size, in bytes, used while uploading stream data. Deployments that typically stream small files, as well as those with limited midtier memory, may improve performance by setting this value below the default. Deployments with a large amount of midtier memory may likewise improve performance by setting this value above the default. |
The following properties are available for HasHelpLink:
The following properties are available for HttpServer:
Table 4-72 HttpServer Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
No |
No |
The BeehiveInstance with which this HttpServer is associated. |
||
|
String |
GET POST |
All permitted values |
Yes |
No |
Restrict access controls to all HTTP methods except the named ones. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The port to which the http server listens. This port is used when starting without SSL |
|
|
n/a |
All permitted values |
Yes |
No |
Each httpserver is associated with a cluster and each site typically has atleast one and only cluster. A HttpServerCluster has properties common to all httpserver's in the cluster. |
||
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The port to which the http server listens when ssl is enabled. This port is used when starting with SSL |
|
|
Integer |
15 |
All permitted values |
Yes |
No |
Idle connection to the server will be alive until this timeout limit |
|
|
File |
apache/httpd.lock |
All permitted values |
Yes |
No |
The lockfile is used when the server needs to lock the accept call. It must be stored on a local disk. |
|
|
HttpServer.HttpServerLogLevel (Legal values: emerg, alert, crit, error, warn, notice, info, debug) |
notice |
All permitted values |
Yes |
No |
Controls the verbosity of the ErrorLog. The following levels are available, in order of decreasing significance:emerg, alert, crit, error, warn, notice, info and debug. |
|
|
Integer |
150 |
All permitted values |
Yes |
No |
Limit on the number of clients who can simultaneously connect. if this limit is ever reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW. It is intended mainly as a brake to keep a runaway server from taking the system with it as it spirals down. |
|
|
String |
n/a |
All permitted values |
No |
Yes |
The group to run httpd as. |
|
|
String |
n/a |
All permitted values |
No |
Yes |
The user to run httpd as. |
|
|
HttpServer.HttpServerSSLLogLevel (Legal values: none, error, warn, info, trace, debug) |
warn |
All permitted values |
Yes |
No |
Controls the verbosity of the SSL ErrorLog. The following levels are available, in order of decreasing significance:none, error, warn, info, trace, and debug. |
|
|
String |
" " |
All permitted values |
Yes |
No |
Your address, where problems with the server should be e-mailed. This address appears on some server-generated pages, such as error documents. |
|
|
String |
n/a |
All permitted values |
No |
Yes |
The top of the directory tree under which the server's configuration, error, and log files are kept. |
|
|
Integer |
60 |
All permitted values |
Yes |
No |
The number of seconds before receives and sends time out. |
The following properties are available for HttpServerCluster:
Table 4-73 HttpServerCluster Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
true |
All permitted values |
Yes |
No |
If Http ssl is enabled in this HttpServer Cluster. |
|
|
Set<HttpServer> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of HttpServer's associated with this cluster. |
|
|
Integer |
1 |
All permitted values |
Yes |
No |
Oc4jSet MaxErrors in mod_oc4j.conf. |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
If Http ssl is terminated by the load balancer. |
The following properties are available for IdMap:
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Map<String,String> |
n/a |
All permitted values |
Yes |
No |
Specifies the map of identity format to identity mapping attribute. Valid identity format values include: unspecified; email_addr; x509_subject; windows_dqn. Valid identity mapping attribute could be any User Directory Service address attribute. |
The following properties are available for IdentityProviderService:
Table 4-75 IdentityProviderService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
n/a |
All permitted values |
Yes |
No |
Specifies the alias to the key and/or certificate of the Oracle Beehive SAML identity provider listed in the Oracle Wallet. |
||
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the URL of the SAML identity provider for system. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
n/a |
All permitted values |
Yes |
No |
Specifies the alias to the key and/or certificate of the Oracle Beehive SAML service provider listed in the Oracle Wallet. |
||
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the URL of the SAML service provider. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for ImService:
Table 4-76 ImService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
Set this parameter to true to enable organisation level archiving. If this is set to false, user level archiving preference has no effect. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Set this to true if chatroom conversations need to be archived. False otherwise(default). |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Set this to true if XHMTL formatting needs to be enabled in chat rooms(default). Set to false otherwise. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
int |
500000 |
Min=100000, Max=3000000 |
Yes |
No |
This value defines the maximum size of the buffer to keep instant messages in memory before they are written into database as transcripts. The default value is 500Kb. Please note that the instant messages can be written to db before this maximum is reached. This is possible on account of expiration of im_purging_period_timer. |
|
|
int |
5 |
Min=5, Max=300 |
Yes |
No |
This property allows the admin to set the time interval at which the ImServiceInstance should send KEEP_ALIVE packets to the IPAs. This enables the IPAs to detect any ImService instance going down. The value is in seconds with a default of 5 s. |
|
|
int |
5 |
Min=2, Max=120 |
Yes |
No |
This value allows the admin to set the maximum time for which offline instant messages can be buffered in memory before they are written to DB in chunks. The default is 5 secs. Please note that the instant messages can be written to db even before this timer expires. This is possible on account of 100 offline buffered messages. |
|
|
int |
300 |
Min=60, Max=600 |
Yes |
No |
This value allows the admin to set the maximum time for which instant messages can be buffered in memory before they are written to DB in chunks. The default is 300 secs. Please note that the instant messages can be written to db even before this timer expires. This is possible on account of the buffer reaching its maximum size limit as defined by the im_buffer_stage_size property. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
10000 |
Min=0, Max=100000 |
Yes |
No |
This is the maximum number of rooms that are allowed by the server. Initial value is set to 10000 |
|
|
int |
100 |
Min=2, Max=500 |
Yes |
No |
This is the maximum number of users allowed in any room on the server. Initial value is set to 100. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Set this parameter to true if only password protected rooms are to be allowed in the server. If set to false (default) non password protected rooms are also allowed. |
|
|
int |
1100 |
Min=11, Max=2147483647 |
Yes |
No |
This value sets the limit on the number of pending messages on the bus session before the send operation blocks. This is used for flow control of messages. The default value is of 1100. A larger value allows for more concurrency and lower value allows for less concurrency. This value also effects the memory usage determined by the pending messages in the session buffer. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Set this to true if all messages exchanged in the room since the first user joined the room are to be replayed, Set to false otherwise (default). |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for IrmService:
Table 4-77 IrmService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CID_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CLD_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CLNM_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CLL_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CSID_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CCLD_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CCLL_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CCLN_L_DESC |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_DURI_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_DURI_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_ENDPT_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_ENDPT_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_UNAME_L_DESC |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
IRM_UPWD_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_KEYSETID_L_DESC |
|
|
int |
30 |
All permitted values |
Yes |
No |
IRM_LIC_EXP_L_DESC |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.IrmServiceBundle, key IRM_AUTH_L_DESC |
|
|
boolean |
false |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.IrmServiceBundle, key IRM_HTTPS_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CCLD_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CCLL_L_DESC |
|
|
String |
n/a |
All permitted values |
Yes |
No |
IRM_CCLN_L_DESC |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for JavaExecutionArguments:
Table 4-78 JavaExecutionArguments Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The set of additional options for the system's Java Virtual Machine (JVM). Each option must be a legal option supported by the JVM, for example -Dproperty=value to set a system property value. This an ADVANCED property which you do not typically need to modify. |
|
|
Integer |
n/a |
This property has a customized constraint. |
Yes |
No |
The initial heap size in megabytes (MBs) of the Java Virtual Machine (JVM). |
|
|
Integer |
n/a |
This property has a customized constraint. |
Yes |
No |
The initial permanent generation size in megabytes (MBs) of the Java Virtual Machine (JVM). |
|
|
Integer |
n/a |
This property has a customized constraint. |
Yes |
No |
The maximum heap size in megabytes (MBs) of the Java Virtual Machine (JVM). |
|
|
Integer |
n/a |
This property has a customized constraint. |
Yes |
No |
The maximum permanent generation size in megabytes (MBs) of the Java Virtual Machine (JVM). |
The following properties are available for JcrServletService:
Table 4-79 JcrServletService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
BASIC |
This property has a customized constraint. |
Yes |
No |
Specifies the JCR server's authentication scheme. Valid values: basic, digest. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Specifies whether or not the BEEHIVE Java Content Repository (JCR) server is enabled. If enabled (true), the JCR server accepts client requests else it throws an appropriate exception. Valid values: true, false |
|
|
int |
960 |
This property has a customized constraint. |
Yes |
No |
The amount of time (in minutes) that the JCR server will wait for a request from a connected client before terminating the session. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
261888 |
Min=16384, Max=1048576 |
Yes |
No |
The buffer size, in bytes, used while downloading stream data. Deployments that typically stream small files, as well as those with limited midtier memory, may improve performance by setting this value below the default. Deployments with a large amount of midtier memory may likewise improve performance by setting this value above the default. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
int |
260096 |
Min=16384, Max=1048576 |
Yes |
No |
The buffer size, in bytes, used while uploading stream data. Deployments that typically stream small files, as well as those with limited midtier memory, may improve performance by setting this value below the default. Deployments with a large amount of midtier memory may likewise improve performance by setting this value above the default. |
The following properties are available for LdapServer:
Table 4-80 LdapServer Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String[] |
n/a |
All permitted values |
Yes |
No |
Specifies the LDAP attributes to be used for the various digest authentication protocols. The attribute entry format is [attribute type]:[attribute name]'. The valid attribute types are DEFAULT, SASL.DIGEST_MD5, and HTTP.DIGEST. e.g. DEFAULT:userPassword;SASL.DIGEST_MDS:mySaslDigestAttribute |
|
|
LdapServer.DirectoryType (Legal values: ORACLE_INTERNET_DIRECTORY, MICROSOFT_ACTIVE_DIRECTORY, SUN_ONE_DIRECTORY, IBM_TIVOLI_DIRECTORY, OPENLDAP_DIRECTORY, OTHER) |
n/a |
All permitted values |
Yes |
No |
Specifies the LDAP directory type. The valid values are ORACLE_INTERNET_DIRECTORY, MICROSOFT_ACTIVE_DIRECTORY, SUN_ONE_DIRECTORY, IBM_TIVOLI_DIRECTORY, and OTHER. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the LDAP group object class. e.g. groupOfUniqueNames |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the LDAP group search base DN. |
|
|
int |
25 |
All permitted values |
Yes |
No |
long description key not set |
|
|
int |
120 |
All permitted values |
Yes |
No |
long description key not set |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the LDAP server hostname. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Specifies the password of the user that is used to bind to the LDAP server. |
|
|
int |
389 |
Network Port, Min=1, Max=65536 |
Yes |
No |
Specifies the LDAP server port. |
|
|
int |
636 |
Network Port, Min=1, Max=65536 |
Yes |
No |
Specifies the LDAP server secure port. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the user that should be used to bind to the LDAP server. The user must have read access to the attributes of all Beehive users. |
|
|
String |
All permitted values |
Yes |
No |
Specifies the LDAP attribute that stores the primary principal in LDAP. e.g. uid |
||
|
String |
not applicable |
All permitted values |
No |
No |
Specifies the LDAP attribute that stores the secret for the primary authentication attribute. |
|
|
String |
not applicable |
All permitted values |
No |
No |
Specifies the LDAP attribute that stores the ASCII (7-bit) principal for the clients that do not support multi-byte string. |
|
|
String |
not applicable |
All permitted values |
No |
No |
Specifies the LDAP attribute that stores the secret for the ASCII (7-bit) principal used for the authentication of clients that do not support multi-byte string. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Specifies whether or not SSL should be used to connect to the LDAP server. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the LDAP user object class. e.g. inetOrgPerson |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the LDAP user search base DN. |
|
|
String |
not applicable |
All permitted values |
No |
No |
Specifies the LDAP attribute that stores the voice principal in LDAP (used by voice clients). |
|
|
String |
not applicable |
All permitted values |
No |
No |
Specifies the LDAP attribute that stores the secret for the authentication of voice clients. |
The following properties are available for LoggingConfigurable.LoggingProperties:
Table 4-81 LoggingConfigurable.LoggingProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
WARNING |
All permitted values |
Yes |
No |
Base Log Level is the default when the log level is not configured through Module Log Level. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Long |
10485760 |
All permitted values |
Yes |
No |
Maximum log file size in bytes. A new log file is opened when the current file exceeds this size. |
|
|
Long |
104857600 |
All permitted values |
Yes |
No |
Maximum log size in bytes. It is the maximum total size of all log files combined. |
|
|
Map<String,Level> |
n/a |
All permitted values |
Yes |
No |
Module Log Level. You will use this advanced property under the guidance of a trained consultant who will explain the correct usage details. Each Logger can have it's log level configured through Module Log Level. It is a map from logger name to log level. |
|
|
LoggingConfigurable.RotationFrequency (Legal values: HOURLY, DAILY, WEEKLY) |
DAILY |
All permitted values |
Yes |
No |
The log file rotation frequency. Log files are rotated when they exceed the maximum log size and they are also rotated periodically according to the rotation frequency. Valid values are HOURLY, DAILY, and WEEKLY. |
The following properties are available for ManagedOc4j:
Table 4-82 ManagedOc4j Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
the password of the oc4j admin user |
|
|
String |
oc4jadmin |
All permitted values |
Yes |
No |
the name of the oc4j admin user |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The maximum value for ajp port range |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The minimum value for ajp port range. |
|
|
Set<BeehiveJ2eeApplication> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of BeehiveJ2eeApplications associated with the Oc4j instance. |
|
|
n/a |
All permitted values |
No |
No |
The BeehiveInstance with which this ManagedOc4j is associated. |
||
|
n/a |
All permitted values |
Yes |
No |
This database holds the configuration data and holds business data for any Enterprise that does not have its own dedicated storage. |
||
|
Oc4jThreadPool (Structural property) |
n/a |
All permitted values |
No |
No |
The HTTP Oc4jThreadPool with which this ManagedOc4j is associated. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The maximum value for jgroup port range |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The minimum value for jgroup port range |
|
|
Oc4jThreadPool (Structural property) |
n/a |
All permitted values |
No |
No |
The JCA Oc4jThreadPool with which this ManagedOc4j is associated. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The maximum value for jms port range |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The minimum value for jms port range |
|
|
n/a |
All permitted values |
Yes |
No |
The Oc4jCluster which this ManagedOc4j belongs to. Each managedOc4j is associated with a cluster. An ManagedOc4jCluster has properties common to all oc4j's in the cluster. |
||
|
String |
n/a |
All permitted values |
No |
No |
the name of the oc4j |
|
|
boolean |
false |
All permitted values |
Yes |
No |
A Boolean flag that is used to enable/disable the pseudo-translation in Beehive Resource Bundle. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The class name of pseudo translation algorithm that will be used for translation process by Beehive Resource Bundle. |
|
|
Set<ResourceAdapterInstance> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of ResourceAdapterInstances associated with the Oc4j instance. |
|
|
int |
1200 |
Min=1, Max=2147483647 |
Yes |
No |
RMI client timeout value (in seconds) for this Oc4j. |
|
|
Oc4jThreadPool (Structural property) |
n/a |
All permitted values |
No |
No |
The RMI-Connection Oc4jThreadPool with which this ManagedOc4j is associated. |
|
|
int |
5000 |
Min=1, Max=10000 |
Yes |
No |
RMI lookup timeout value (in milliseconds) for this Oc4j. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The maximum value for rmi port range |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The minimum value for rmi port range |
|
|
Oc4jThreadPool (Structural property) |
n/a |
All permitted values |
No |
No |
The RMI-Request Oc4jThreadPool with which this ManagedOc4j is associated. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The maximum value for rmis port range |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The minimum value for rmis port range |
|
|
n/a |
All permitted values |
Yes |
No |
The SipContainer with which this ManagedOc4j is associated. |
||
|
n/a |
All permitted values |
Yes |
No |
Arguments for the Java Virtual Machine when starting this component |
||
|
n/a |
All permitted values |
Yes |
No |
Arguments for the Java Virtual Machine when starting this component |
||
|
Oc4jThreadPool (Structural property) |
n/a |
All permitted values |
No |
No |
The System Oc4jThreadPool with which this ManagedOc4j is associated. |
The following properties are available for ManagedOc4jCluster:
Table 4-83 ManagedOc4jCluster Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
the password of the oc4j admin user |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If Ajps is enabled for this Oc4j cluster. |
|
|
Set<ManagedOc4j> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of Oc4j associated with this cluster. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
If ormis is enabled for this Oc4j Cluster. |
No other properties exist for ManagedOc4jCluster.HealthMonitorProperties .
The following properties are available for ManagementService:
Table 4-84 ManagementService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
25 |
All permitted values |
Yes |
No |
The interval (in seconds) after which the background task to synchronize any pending configuration changes to local configuration files will be invoked. |
|
|
int |
20 |
All permitted values |
Yes |
No |
The interval (in seconds) after which batched local configuration file changes will be saved and necessary actions like restarting processes initiated to effect the changes. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the configuration export background task. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
When set to true, the management service detects changes to the system model and automatically updates local configuration files to be in sync. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Integer |
n/a |
All permitted values |
Yes |
No |
Maximum number of records returned when searching for logs. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Sets whether the background task for log synchronization is enabled. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Filter for selecting the log files or directories to upload to the central repository so that they can be viewed or searched in the log viewer user interface. |
|
|
int |
6 |
All permitted values |
Yes |
No |
Frequency (in minutes) of the background log upload task. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
n/a |
All permitted values |
No |
Yes |
long description key not set |
||
|
n/a |
All permitted values |
Yes |
No |
long description key not set |
||
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
Log records of this or higher level are uploaded to the configuration database. |
The following properties are available for ManagementService.StabilityMonitorProperties:
The following properties are available for ManagementService.SystemDataCollectorProperties:
Table 4-86 ManagementService.SystemDataCollectorProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
300 |
Min=1, Max=2147483647 |
Yes |
No |
Time interval between executions of system data collector background task |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables the system data collector background task. |
|
|
int |
180 |
Min=1, Max=525600 |
Yes |
No |
System data collector will rotate file after this interval |
|
|
int |
100 |
Min=1, Max=1024 |
Yes |
No |
Rotation size for the file generated by system data collector |
The following properties are available for MimService:
Table 4-87 MimService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
86400 |
Min=600, Max=86400 |
Yes |
No |
When client is in disconnected mode and in 'away' state, this time would specify in sec when server would set 'offline' and cleanup everything including backend Instant Messaging sessions. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
3 |
Min=1, Max=5 |
Yes |
No |
Maximum number of LOGIN attempts before server closes the client connection. After opening a new connection, client can make only a certain maximum number of attempt to successfully LOGIN. If the maximum attempt reached and client fails then server closes the connection. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
int |
60 |
Min=30, Max=120 |
Yes |
No |
After client connects it has to finish authentication with in a specified amount time, otherwise server will cleanup the connection. This property would specify in second. how much time it would wait before closing the connection. |
The following properties are available for MobileDmService:
Table 4-88 MobileDmService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
1000 |
Min=100, Max=5000 |
Yes |
No |
Maximum number of concurrent mobile clients connections per Mobile DM Server instance. |
|
|
int |
3 |
Min=3, Max=10 |
Yes |
No |
Maximum number of invalid command attempts before the server closes the connection. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
int |
30 |
Min=15, Max=60 |
Yes |
No |
Timeout for authenticated sessions in minutes. |
|
|
int |
1 |
Min=1, Max=10 |
Yes |
No |
Timeout for non-authenticated sessions in minutes. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for NamedSystemObject:
The following properties are available for NotificationDeliveryService:
Table 4-90 NotificationDeliveryService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.NotificationDeliveryServiceBundle, key ACTION_ASK_SETTINGS_LONG_DESCRIPTION |
||
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
int |
20 |
Min=1, Max=100 |
Yes |
No |
This value defines how many threads will be used for the delivery processing thread pool. The default value is 20. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
15 |
Min=1, Max=365 |
Yes |
No |
This value defines how long delivery records will be retained in the system. The default value is 15 days. |
|
|
int |
15 |
Min=1, Max=365 |
Yes |
No |
Age to keep notification history to avoid duplicate notifications. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
n/a |
All permitted values |
Yes |
No |
Defines SMS settings. |
||
|
String |
SYSTEM |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.NotificationDeliveryServiceBundle, key SYSTEM_USER_NAME_LONG_DESCRIPTION |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
n/a |
All permitted values |
Yes |
No |
Defines the XMS credential settings used for SMS delivery when SmsMode is set to XMS. |
The following properties are available for NotificationDeliveryService.ActionAskSettings:
Table 4-91 NotificationDeliveryService.ActionAskSettings Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
Disables actionable notification E-Mails. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Disables actionable notification Instant Messages. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Disables actionable notification responses. |
|
|
CollabId |
n/a |
All permitted values |
Yes |
No |
Defines the actionable notification user identifier. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Disables actionable notification SMS. |
|
|
int |
20 |
Min=1, Max=100 |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.NotificationDeliveryServiceBundle, key ASK_PROCESSINGPOOL_SIZE_LONG_DESCRIPTION |
|
|
int |
512 |
Min=1, Max=2147483647 |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.NotificationDeliveryServiceBundle, key ASK_USER_CACHE_LONG_DESCRIPTION |
The following properties are available for NotificationDeliveryService.SmsSettings:
Table 4-92 NotificationDeliveryService.SmsSettings Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
5 |
Min=1, Max=255 |
Yes |
No |
This value defines the maximum number of chunks a single SMS can be broken into before it is truncated. The default value is 5. |
|
|
String |
All permitted values |
Yes |
No |
Defines the SMS shortcode used for outbound SMS deliveries. |
||
|
NotificationDeliveryService.SmsSettings.ShortCodeType (Legal values: INTERNATIONAL, NATIONAL, NETWORK, SUBSCRIBER, ALPHANUMERIC, ABBREVIATED) |
INTERNATIONAL |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.NotificationDeliveryServiceBundle, key SMS_SHORT_CODE_TYPE_LONG_DESCRIPTION |
|
|
int |
1000 |
Min=500, Max=10000 |
Yes |
No |
This value defines the maximum number of chunks a single SMS can be broken into before it is truncated. The default value is 5. |
|
|
NotificationDeliveryService.SmsSettings.SmsMode (Legal values: XMS, SMPP) |
SMPP |
All permitted values |
Yes |
No |
This value defines how the built-in SMS delivery handler will process SMS delivery requests. Possible values: XMS, SMPP. The default value is XMS. |
The following properties are available for NotificationDeliveryService.WebProxySettings:
Table 4-93 NotificationDeliveryService.WebProxySettings Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables the usage of the web proxy settings for http/https requests. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Defines a hostname to be used as a proxy for all HTTP/HTTPS communication. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Defines a password to be used for the web proxy. |
|
|
int |
8080 |
All permitted values |
Yes |
No |
Defines a port number to be used for all proxied HTTP/HTTPS communication. Default value: 8080 |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Defines a username to be used for the web proxy. |
The following properties are available for NotificationDeliveryService.XmsSettings:
Table 4-94 NotificationDeliveryService.XmsSettings Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Defines the HTTP proxy which is used for SOAP based communications. |
||
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Password for XMS communication. |
|
|
String |
All permitted values |
Yes |
No |
XMS service URL. |
||
|
String |
n/a |
All permitted values |
Yes |
No |
Username for XMS communication. |
The following properties are available for ObjectEventPublisherService:
Table 4-95 ObjectEventPublisherService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for Oc4j:
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
the password of the oc4j admin user |
|
|
String |
oc4jadmin |
All permitted values |
Yes |
No |
the name of the oc4j admin user |
|
|
Set<BeehiveJ2eeApplication> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of BeehiveJ2eeApplications associated with the Oc4j instance. |
|
|
n/a |
All permitted values |
Yes |
No |
This database holds the configuration data and holds business data for any Enterprise that does not have its own dedicated storage. |
||
|
String |
n/a |
All permitted values |
No |
No |
the name of the oc4j |
|
|
boolean |
false |
All permitted values |
Yes |
No |
A Boolean flag that is used to enable/disable the pseudo-translation in Beehive Resource Bundle. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The class name of pseudo translation algorithm that will be used for translation process by Beehive Resource Bundle. |
|
|
Set<ResourceAdapterInstance> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of ResourceAdapterInstances associated with the Oc4j instance. |
|
|
int |
1200 |
Min=1, Max=2147483647 |
Yes |
No |
RMI client timeout value (in seconds) for this Oc4j. |
|
|
int |
5000 |
Min=1, Max=10000 |
Yes |
No |
RMI lookup timeout value (in milliseconds) for this Oc4j. |
The following properties are available for OmaService:
Table 4-97 OmaService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables calendar synchronization. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables contacts synchronization. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
int |
7 |
Min=1, Max=2147483647 |
Yes |
No |
Number of days to keep the session log and SyncML message log in the database. Log entries older than this will be purged automatically. |
|
|
int |
10000 |
Min=1, Max=2147483647 |
Yes |
No |
Maximum devices to cache. |
|
|
int |
1000 |
Min=1, Max=2147483647 |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.OmaServiceResourceBundle, key DSSESSION_CACHE_SIZE_LONG_DESCRIPTION |
|
|
int |
200 |
Min=1, Max=2147483647 |
Yes |
No |
The maximum number of e-mails that may be downloaded to a device. Together with the MaxSyncRangeBack property, the number of e-mails to download is restricted. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables e-mail synchronization. |
|
|
int |
25 |
Min=1, Max=1000 |
Yes |
No |
Maximum entities per bulk load. |
|
|
int |
25 |
Min=1, Max=1000 |
Yes |
No |
Maximum entities per contact bulk load. |
|
|
int |
25 |
Min=1, Max=1000 |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.OmaServiceResourceBundle, key ENTITIES_PER_EMAIL_BULK_LOAD_LONG_DESCRIPTION |
|
|
int |
25 |
Min=1, Max=1000 |
Yes |
No |
Maximum entities per event bulk load. |
|
|
int |
25 |
Min=1, Max=1000 |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.OmaServiceResourceBundle, key ENTITIES_PER_TASK_NOTE_LOAD_LONG_DESCRIPTION |
|
|
int |
25 |
Min=1, Max=1000 |
Yes |
No |
Maximum entities per task bulk load. |
|
|
int |
51 |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.OmaServiceResourceBundle, key THRESHOLD_WHERE_SYNC_RANGE_VALIDATION_STARTS_TO_OCCUR_FOR_EVENTS |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
String |
All permitted values |
Yes |
No |
Log SyncML for the these users. Specify a comma delimited list of user identifiers. |
||
|
int |
100 |
Min=1, Max=2147483647 |
Yes |
No |
The maximum number of concurrent requests that can be supported by a Oracle Mobile Data Sync Service instance. When this number is reached, subsequent synchronization requests will be refused until the number of concurrent requests drops below this number. |
|
|
int |
400 |
Min=1, Max=2147483647 |
Yes |
No |
The maximum number of concurrent Sync sessions that can be supported by a Oracle Mobile Data Sync Service instance. When this number is reached, subsequent requests to start a Sync will be refused until the number of ongoing Syncs drops below this number. |
|
|
int |
20 |
Min=1, Max=2147483647 |
Yes |
No |
The maximum number of concurrent slow syncs that can be supported by a Oracle Mobile Data Sync Service instance. When this number is reached, subsequent synchronization requests for a slow sync will be refused until the number of all ongoing slow Syncs becomes less than number. |
|
|
int |
60000 |
Min=1000, Max=2147483647 |
Yes |
No |
Upper limit of the size of the messages exchanged between client and server in bytes. This value will be used if the MaxMessageSize value in a device profile exceeds this limit. Otherwise, the value in the device profile will be used. |
|
|
int |
5000000 |
Min=1000, Max=2147483647 |
Yes |
No |
Upper limit of the size of the large objects exchanged between client and server in bytes. This value will be used if the MaxObjectSize value in a device profile exceeds this limit. Otherwise, the value in the device profile will be used. |
|
|
int |
365 |
Min=1, Max=2147483647 |
Yes |
No |
The number of days previous to the current date to synchronize. |
|
|
int |
365 |
Min=1, Max=2147483647 |
Yes |
No |
The number of days from the current date to synchronize. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Determines whether MD5 authentication is required (true) or if BASIC authentication is also allowed (false). |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables support for MD5 authentication. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables Outlook Notes synchronization. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the Oracle Mobile Data Sync Service. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables support for "Suspend and Resume" synchronization after incomplete or failed syncs. Improves performance with clients who support Resume for syncs. |
|
|
String |
1000,5000,9000 |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.OmaServiceResourceBundle, key RETRIES_WHEN_DB_UNAVAILABLE_DELAY_IN_MILLISEC |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the logging of synchronization sessions in the database. |
|
|
int |
6000 |
Min=1, Max=2147483647 |
Yes |
No |
A synchronization session will timeout if it does not receive a client request after this number of minutes. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables logging of SyncML messages in the database. |
|
|
int |
51 |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.OmaServiceResourceBundle, key THRESHOLD_WHERE_SYNC_RANGE_VALIDATION_STARTS_TO_OCCUR_FOR_TASKS |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for OmsResourceAdapter:
Table 4-98 OmsResourceAdapter Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
No |
Yes |
ResourceAdapterImage associated with the ResourceAdapter |
||
|
Set<ResourceAdapterInstance> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Set of instances of ResourceAdapter |
The following properties are available for OmsResourceAdapterInstance:
The following properties are available for Opmn:
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
BeehiveInstance associated with the OPMN |
||
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
OPMN local port |
|
|
n/a |
All permitted values |
Yes |
No |
OpmnCluster associated with the OPMN |
||
|
int |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
OPMN remote port |
|
|
int |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
OPMN request port |
The following properties are available for OpmnCluster:
Table 4-101 OpmnCluster Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables Secure Socket Layers (SSL) for the notification server. |
|
|
Set<Opmn> (Structural property) |
n/a |
All permitted values |
Yes |
No |
OPMNs associated with the OpmnCluster |
The following properties are available for OwcStreamingService:
Table 4-102 OwcStreamingService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Integer |
1954 |
Network Port, Min=1, Max=65536 |
Yes |
No |
description bundle not set |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Integer |
100 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Integer |
100 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Integer |
100 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Integer |
1935 |
Network Port, Min=1, Max=65536 |
Yes |
No |
description bundle not set |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Integer |
1554 |
Network Port, Min=1, Max=65536 |
Yes |
No |
description bundle not set |
|
|
String |
DANGSServer/2.0.1 |
All permitted values |
Yes |
Yes |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for PolicyService:
Table 4-103 PolicyService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for PresenceService:
Table 4-104 PresenceService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
300000 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
int |
1024 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
5 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
boolean |
true |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for PushMailService:
Table 4-105 PushMailService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
int |
300 |
Min=60, Max=600 |
Yes |
No |
Interval in seconds to send a keep-alive command to the IMAP Mail Server to keep the IMAP connection alive. |
|
|
int |
720 |
Min=5, Max=1440 |
Yes |
No |
Backend IMAP connection live time, in minutes after a device connection dies. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
2000 |
Min=2, Max=5000 |
Yes |
No |
Maximum number of concurrent mobile clients connections per Mobile Mail Server instance. |
|
|
int |
200 |
Min=200, Max=1000 |
Yes |
No |
Maximum number of inbox messages allowed to sync to device. This is the absolute maximum view filter size, no matter what value the Mobile Client specifies. |
|
|
int |
50 |
Min=50, Max=200 |
Yes |
No |
Maximum message size, in KB, which a user may sync to a device. This is the absolute maximum size, no matter what value the Mobile Client specifies. |
|
|
int |
7 |
Min=7, Max=14 |
Yes |
No |
Maximum number of days past user can fetch messages to sync to their device. This is the absolute maximum days view filter size, no matter what value the Mobile Client specifies. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for PushService:
Table 4-106 PushService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Defines the Apple Push Nofication Service settings. |
||
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
1000 |
Min=100, Max=5000 |
Yes |
No |
Maximum number of concurrent mx-based clients connections per Mobile Push Server instance. |
|
|
int |
3 |
Min=3, Max=10 |
Yes |
No |
Maximum number of invalid command attempts before the server closes the connection. |
|
|
int |
100 |
Min=1, Max=1000 |
Yes |
No |
Maximum number of concurrent HTTP true push-based clients connections per Mobile Push Server instance. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
int |
1 |
Min=1, Max=10 |
Yes |
No |
Timeout for non-authenticated sessions in minutes. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for PushService.APNSSettings:
Table 4-107 PushService.APNSSettings Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
Indicates if APNS is enabled as an outbound channel. |
|
|
String |
gateway.push.apple.com |
All permitted values |
Yes |
No |
Defines the hostname of the APNS gateway. |
|
|
byte[] |
n/a |
All permitted values |
Yes |
No |
Contents of the .p12 file that contains the APNS certificate and private key. |
|
|
int |
2195 |
All permitted values |
Yes |
No |
Defines the port of the APNS gateway. Default value is: 2195 |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables the usage of the web proxy settings for http/https requests. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Defines a hostname to be used as a proxy for all HTTP/HTTPS communication. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Defines a password to be used for the web proxy. |
|
|
int |
8080 |
All permitted values |
Yes |
No |
Defines a port number to be used for all proxied HTTP/HTTPS communication. Default value: 8080 |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Defines a username to be used for the web proxy. |
The following properties are available for RecordsManagementService:
Table 4-108 RecordsManagementService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
n/a |
All permitted values |
Yes |
No |
Records Management Service uses Oracle Universal Records Manager for records management. The URM configuration includes host, port, admin user account details, and agent name of the URM deployment. There can be at most one URM configured in the system. |
The following properties are available for RemoteContentService:
Table 4-109 RemoteContentService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
String |
beehive/rcsspool |
All permitted values |
Yes |
No |
description bundle not set |
|
|
String |
n/a |
All permitted values |
Yes |
No |
description bundle not set |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
description bundle not set |
|
|
String |
n/a |
All permitted values |
Yes |
No |
description bundle not set |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
209715200 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
int |
30000 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
int |
250 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
int |
45 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
int |
15 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
int |
45 |
All permitted values |
Yes |
No |
description bundle not set |
No other properties exist for RemoteSite .
The following properties are available for ResourceAdapter:
Table 4-110 ResourceAdapter Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
No |
Yes |
ResourceAdapterImage associated with the ResourceAdapter |
||
|
Set<ResourceAdapterInstance> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Set of instances of ResourceAdapter |
The following properties are available for ResourceAdapterImage:
The following properties are available for ResourceAdapterInstance:
The following properties are available for ResourceDirectoryService:
Table 4-113 ResourceDirectoryService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
When true, all resources are considered readable by everyone. When false, explcit access control checks are made to determine the access. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
Integer |
20000 |
All permitted values |
Yes |
No |
The maximum number of resource entries to be returned on a list operation. This setting can affect the results of some system administration commands. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for RmServletService:
Table 4-114 RmServletService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for SAMLIdentity:
Table 4-115 SAMLIdentity Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
Specifies the alias for the certificate of the SAML issuer. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Specifies whether the SAML issuer is a trusted service or not. (It is a SAML IdP if it is not a service.) |
The following properties are available for SearchService:
Table 4-116 SearchService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
image/,application/ics |
All permitted values |
Yes |
No |
This parameter specifies a comma-separated list of attachment mime-types to be discarded from indexing. When processing attachments, for example email attachments, if the mime-type of the attachment starts with one of the specified mime-types, it will be discarded and, as such, its content will not be indexed. |
|
|
String |
true |
All permitted values |
Yes |
No |
Start or stop the change capture for the search service |
|
|
String |
All permitted values |
Yes |
No |
List of Collab Ids of users or groups for which change capture is allowed. The entries in the list can be seprated by whitespaces (space or tab), comma or a new line. Empty list signifies no restriction. |
||
|
Integer |
120 |
This property has a customized constraint. |
Yes |
No |
The maximal nap time for crawl job. This is the same as long nap time, and short nap time is 50% of the maximal nap time. |
|
|
Integer |
5000 |
This property has a customized constraint. |
Yes |
No |
The threshold of crawl job processing amount. If current run processed more than threshold amount of feeds, crawl job will not nap. If less than threshold, crawl job will take a short nap. If no feeds, crawl job will take a long nap. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Integer |
10 |
This property has a customized constraint. |
Yes |
No |
The index fragmentation threshold. If current fragmentation level is lower than the threshold, index optimization will not happen. Default to 10. |
|
|
Integer |
120 |
This property has a customized constraint. |
Yes |
No |
The maximal nap time for index job. This is the same as long nap time, and short nap time is 50% of the maximal nap time. |
|
|
Integer |
5000 |
This property has a customized constraint. |
Yes |
No |
The threshold of index job processing amount. If current run processed more than threshold amount of feeds, index job will not nap. If less than threshold, index job will take a short nap. If no feeds, index job will take a long nap. |
|
|
Integer |
0 |
This property has a customized constraint. |
Yes |
No |
The interval in days between index optimizations with FULL mode. 0 means disabled. |
|
|
Integer |
480 |
This property has a customized constraint. |
Yes |
No |
The maximal time in minutes that can be spent on each index optimization with FULL mode. Default to 480 minutes. |
|
|
String |
2010-08-01,00:00:00 |
This property has a customized constraint. |
Yes |
No |
Start date of index optimization in DB time, format is 'YYYY-MM-DD,HH24:MI:SS'. Default to next Sunday 00:00:00. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Integer |
1000 |
This property has a customized constraint. |
Yes |
No |
Maximum number of search results returned by the search service |
|
|
Integer |
4096 |
This property has a customized constraint. |
Yes |
No |
The maximum entity size for snippet computation. Value is specified in Bytes. The range is between 0 and 32767Bytes. 0 indicates no snippet computation. Any nonzero value will compute snippets for entities whose size is upto the value specified in the property.Default is 4096 |
|
|
Integer |
0 |
This property has a customized constraint. |
Yes |
No |
The interval in days between mdata optimizations. 0 means disabled. |
|
|
Integer |
0 |
Min=0, Max=15 |
Yes |
No |
This parameter is used for improving multi-workspace query performance. It determines how many threads a search query can use per database RAC node dedicated for search (as configured in the search Data-Source). Parallel query is NOT used if one of the following conditions is true: (1) the QueryWithSearchDataSource property is set to false, (2) this parameter is set to 0 (default), or (3) the query is in a single workspace or a set of workspaces in the same partition. When the value of this parameter is 1 and the workspaces correspond to partitions on different RAC nodes, search service spawns one thread per RAC node, each of which executes the query for the set of partitions that is affinitized to the given RAC node, and the results are combined in mid-tier. Currently 0 and 1 are the only supported values. In future release we may allow a value N that is greater than one, when search service can use up to N threads for each RAC node, if the workspaces to query in a RAC node fall in multiple partitions. |
|
|
Integer |
100 |
This property has a customized constraint. |
Yes |
No |
This parameter determines the size of the thread-pool from which all parallel search queries will be spawned. This sets the maximum total number of concurrently running threads for search queries. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
Map<String,String> |
n/a |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.SearchBundle, key SEARCH_DISCLAIMER_LONG_DESC |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
String |
* |
All permitted values |
Yes |
No |
Specify the wildcard character for search (Default is *) |
The following properties are available for Server:
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Collection<String> |
n/a |
All permitted values |
Yes |
No |
A list of alternate host names for the Server. A Server may have multiple host names, for example if there are multiple network interface cards installed. |
|
|
Set<BeehiveInstance> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of BeehiveInstances associated with the Server. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The primary host name of this Server. |
|
|
String |
127.0.0.1 |
IP Address |
Yes |
No |
The IP address of the Sip listener. Required for Sip integration |
The following properties are available for Service:
Table 4-118 Service Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for SesEndptService:
Table 4-119 SesEndptService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
String |
changethis |
All permitted values |
Yes |
No |
The host portion of the url to access the SES endpoint web service. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
5 |
All permitted values |
Yes |
No |
When SES users do advanced search with Contains operator for creator name, modifier name, participants, the SES Endpoint searches in the directory for usernames containing the user given string. This parameter restricts the number of such matches. |
|
|
int |
0 |
All permitted values |
Yes |
No |
The port portion of the url to access the SES endpoint web service. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables the SES endpoint service. |
|
|
Map<String,SecureString> |
n/a |
All permitted values |
Yes |
No |
The trusted entity name and password of the SES brokers are stored in this map.The BEECTL command add_trusted_identity is used to add trusted entity credentials which are stored in this map. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for SipContainer:
Table 4-120 SipContainer Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Oc4j associated with the SipContainer |
||
|
boolean |
true |
All permitted values |
Yes |
No |
long description key not set |
|
|
int |
5080 |
Network Port, Min=1, Max=65536 |
Yes |
No |
Maximum permitted value for SIP protocol port |
|
|
int |
5060 |
Network Port, Min=1, Max=65536 |
Yes |
No |
Minimum permitted value for SIP protocol port |
The following properties are available for SipGateway:
Table 4-121 SipGateway Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
IP Address |
Yes |
No |
IP address of the SIP Gateway |
|
|
int |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
Port used to establish outbound connections from site to SIP Gateway |
|
|
n/a |
All permitted values |
No |
No |
SipGatewayCluster associated with the SipGateway |
The following properties are available for SipGatewayCluster:
The following properties are available for Site:
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String[] |
[oracle.beehive., oracle.csi.] |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.SystemModelBundle, key SITE_BEEHIVE_ROOT_LOGGER_LONG_DESC |
|
|
n/a |
All permitted values |
Yes |
No |
The global Bti configuration |
||
|
n/a |
All permitted values |
Yes |
No |
A database where business data is stored. An Enterprise may be configured with its own business database. If an Enterprise does not have its own database configured, then the business data for that Enterprise gets stored in the Site level BusinessDatabase |
||
|
SecureString |
n/a |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
If application clustering is enabled for the site |
|
|
n/a |
All permitted values |
Yes |
No |
The database where system configuration is stored |
||
|
n/a |
All permitted values |
Yes |
Yes |
This database holds the configuration data and holds business data for any Enterprise that does not have its own dedicated storage. |
||
|
List<Integer> |
[1000, 5000, 9000] |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
n/a |
All permitted values |
Yes |
No |
The Diagnosability settings |
||
|
n/a |
All permitted values |
Yes |
No |
The database where diagnostic data is stored |
||
|
int |
54321 |
All permitted values |
Yes |
Yes |
The enterprise id |
|
|
Set<Enterprise> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of Enterprise associated with the Site. |
|
|
n/a |
All permitted values |
Yes |
No |
The database where Event Listener data is stored |
||
|
n/a |
All permitted values |
Yes |
Yes |
The HttpServerCluster associated with this Site. |
||
|
byte[] |
n/a |
All permitted values |
Yes |
No |
The Beehive language pack |
|
|
n/a |
All permitted values |
Yes |
No |
An external LDAP server which can be a source of information that gets synchronized into Beehive and can be used by the Authentication Service to authenticate users. |
||
|
n/a |
All permitted values |
Yes |
Yes |
The ManagedOc4jCluster associated with this Site. |
||
|
String |
n/a |
All permitted values |
Yes |
No |
the name of the system object. |
|
|
n/a |
All permitted values |
Yes |
Yes |
The OpmnCluster associated with the Site. |
||
|
n/a |
All permitted values |
Yes |
No |
A database where read-only business data is stored. An Enterprise may be configured standby database read-only database access. If an Enterprise does not have read-only database configured, then the read-only data for that Enterprise accesses using BusinessDatabase |
||
|
Set<RemoteSite> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of RemotesSite associated with the Site. |
|
|
Set<ResourceAdapter> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of ResourceAdapters associated with the Site. |
|
|
n/a |
All permitted values |
Yes |
No |
The database where Search data is stored |
||
|
Set<Server> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of Servers associated with the Site. |
|
|
Set<Service> (Structural property) |
n/a |
This property has a customized constraint. |
Yes |
No |
The set of Services associated with the Site. |
|
|
n/a |
All permitted values |
Yes |
Yes |
The SipGatewayCluster associated with this Site. |
||
|
int |
54321 |
All permitted values |
Yes |
Yes |
The site id. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
description bundle not set |
|
|
Set<UnmanagedOc4j> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of UnmanagedOc4js associated with the Site. |
|
|
n/a |
All permitted values |
Yes |
No |
The VirtualServer associated with the Site. |
||
|
n/a |
All permitted values |
Yes |
Yes |
The cluster of virus scan engines associated with this Site. All engines in the cluster are of the same type, i.e. provided by the same vendor. |
No other properties exist for Site.DiagnosabilityProperties .
The following properties are available for SmppDeliveryService:
Table 4-124 SmppDeliveryService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.SmppDeliveryServiceBundle, key SMPP_ENABLE_MO_LONG_DESCRIPTION |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
int |
-1 |
Min=-1, Max=255 |
Yes |
No |
Defines the Numbering Plan Indicator used by the shortcode for the outbound SMS deliveries. |
|
|
int |
1 |
All permitted values |
Yes |
No |
The maximum number of active SMPP connections. This may be more or less than the number of SMPP Delivery Service instances. |
|
|
int |
45 |
Min=1, Max=59 |
Yes |
No |
The interval in seconds between sending Enquire Link Protocol Data Units to Short Message Service Center. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
The SMPP system password assigned by the Short Message Service Center. |
|
|
int |
25 |
All permitted values |
Yes |
No |
Controls the number of threads allocated for background processing of incoming SMS delivery requests. |
|
|
String |
All permitted values |
Yes |
No |
Defines a hostname/port URL for the SMPP server. Format: host:port Example: smpp.somehost.com:2775 Default port: 2775 (smpp), 3550 (ssmpp) |
||
|
String |
All permitted values |
Yes |
No |
The SMPP system ID assigned by the Short Message Service Center. |
||
|
String |
All permitted values |
Yes |
No |
The SMPP system sype assigned by the Short Message Service Center. |
||
|
int |
15 |
Min=1, Max=59 |
Yes |
No |
The time in seconds the SMPP client will wait for a response from the Short Message Service Center before closing the connection. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables TLS support for SMPP connections. Enable if required by the Short Message Service Center. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables the use of QUERY_SM PDU for delivery status reporting. |
|
|
SmppDeliveryService.VersionNumber (Legal values: VERSION_33, VERSION_34, VERSION_5) |
VERSION_5 |
All permitted values |
Yes |
No |
Defines which SMPP protocol version will be advertised in the BIND requests. Some providers will reject the BIND request if the protocol version is not one of their supported versions.. |
No other properties exist for SoftwareImage .
No other properties exist for StateManageable .
No other properties exist for StatusManageable .
The following properties are available for SubscriptionActionService:
Table 4-125 SubscriptionActionService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for SubscriptionService:
Table 4-126 SubscriptionService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
30 |
Min=1, Max=30 |
Yes |
No |
Maximum allowed anchor age in days when querying "getElementModifications". AnchorToooldException will be thrown if the anchor passed in getElementModifications is older than the maximum allowed anchor age (in days) in configuration. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for SyndicationService:
Table 4-127 SyndicationService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for SyndicationServletService:
Table 4-128 SyndicationServletService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
BASIC |
This property has a customized constraint. |
Yes |
No |
Default authentication scheme for Syndication Servlet. Accepted values are: BASIC, DIGEST, SSO |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
No other properties exist for SystemObject .
No other properties exist for SystemObjectWithHelper .
No other properties exist for SystemObjectWithStats .
The following properties are available for TCPCommBasedScanEngine:
Table 4-129 TCPCommBasedScanEngine Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Integer |
1344 |
Network Port, Min=1, Max=65536 |
Yes |
No |
Communication port used by Beehive for sending client requests to the third-party scan engine. |
|
|
String |
localhost |
All permitted values |
Yes |
No |
Hostname of the server where the third-party scan engine is installed. |
|
|
n/a |
All permitted values |
No |
No |
A VirusScanEngineCluster is made up of scan engines of the same type, i.e by the same provider, configured for the Site or Enterprise. This property shows the VirusScanEngineCluster that this engine belongs to. |
The following properties are available for TCPCommBasedScanEngineCluster:
Table 4-130 TCPCommBasedScanEngineCluster Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Long |
600000 |
This property has a customized constraint. |
Yes |
No |
The interval at which Beehive VirusScanner process refreshes its in-memory cache with data from the virus defnitions storage. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Indicator to determine if detailed stats related to virusscanner needs to be captured. These stats include method stats. |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Indicates if Beehive should over-ride certain return scan statuses. This will allow Beehive to treat what the scan engine considers as INFECTED as CLEAN. |
|
|
VirusScanEngineCluster.ScanEngineCommProtocol (Legal values: ICAP, CUSTOM) |
ICAP |
All permitted values |
Yes |
Yes |
The protocol used by Beehive to communicate with the third-party scan service engine. |
|
|
String |
1.0 |
All permitted values |
Yes |
Yes |
The version of the protocol used to communicate with the third-party scan service. |
|
|
Set<VirusScanEngine> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of virus scan engines, of the same type, that are part of this cluster. |
|
|
VirusScanEngineCluster.ScanServiceProvider (Legal values: Symantec, TrendMicro, McAfee) |
Symantec |
All permitted values |
Yes |
Yes |
Engines in a cluster are of the same type and are supplied by this third-party virus scan service provider. |
|
|
VirusScanConfigurable.VirusScanPolicy (Legal values: NO_SCAN_OR_REPAIR, SCAN_ONLY, SCAN_AND_REPAIR) |
NO_SCAN_OR_REPAIR |
All permitted values |
Yes |
No |
Scan policy configured for Beehive. If the policy is set to SCAN_ONLY is set and a request to scan and repair is received, caller will receive an exception. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
List of viruses that Beehive can choose to ignore and treat as un-infected. This list will only be evaluated if the the OverrideEngineResultEnabled is also set to true. |
The following properties are available for TeamCollaborationApisService:
Table 4-131 TeamCollaborationApisService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for TeamCollaborationService:
Table 4-132 TeamCollaborationService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
10 |
This property has a customized constraint. |
Yes |
No |
The number of threads in the thread pool, used while updating non time-critical data such as page view count and discussions forum change status. Deployments that typically find that the page view count and discussions change status take too long to be updated may improve this behavior by increasing this number above the default. On the other hand, those deployments that anticipate very low concurrent access to the application may benefit by decreasing this value below the default. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
This parameter determines whether the server checks if the CSRF token supplied in the request by the client is valid. If true, it compares the server-side token with the client's; if false, just bypass the validation. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
int |
50 |
Min=1, Max=1023 |
Yes |
No |
The number of threads in the thread pool for ExecutorService, used for parallel loading of contents in pages such as home, overview, and profile. Those pages contain mixed contents and typically require multiple CSI/database calls to generate the response. Thus they are designed to spawn several threads in the ExecutorService thread pool to load the contents concurrently. |
|
|
String |
http://www.oracle.com/technology/products/beehive/beehive_users/2_0/teamcollab.htm |
All permitted values |
Yes |
No |
A configurable link to help text for Beehive clients. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
1024 |
This property has a customized constraint. |
Yes |
No |
Specifies the maximum logo size in KB for workspaces. This value is used when uploading new logos. Only logo images of size smaller than this value is allowed. |
|
|
int |
100 |
This property has a customized constraint. |
Yes |
No |
This number applies to table listings such as recent activity or tagged entities, which includes many types in one table. Default value is set as 100, but is recommended to be increased (always in multiples of 25) on deployments where the primary usage comes from workspaces client. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Specifies whether or not Rich Text descriptions will be filtered by AntiSamy prior to display in the Team Collaboration Client to remove potentially malicious xhtml and javascript. Valid values: true, false |
|
|
String |
oracle/ocs/amshare/util/antisamy-strict.xml |
All permitted values |
Yes |
No |
Path to the AntiSamy policy xml file, used to configure the AntiSamy XHTML filtering of Rich Text descriptions. The path may be absolute or relative to the Beehive home directory. |
|
|
int |
10 |
This property has a customized constraint. |
Yes |
No |
This number is similar to MultiTypeListingBatchSize but only applies to search results. Default value is set as 10, and the value should always be in multiples of 10. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
This parameter determines whether the tacit related UI modules are displayed. By default, it is true. If set to false, all the tacit related UI modules like Connection Requests, Search Interests and Expertise, Interests and Expertise modules are hidden. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for TimeManagementService:
Table 4-133 TimeManagementService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
true |
All permitted values |
Yes |
No |
Enables or disables Time Management consistency background tasks. When enabled, the system will automatically perform various verifications and adjustments to ensure consistency. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Enables or disables some Oracle Beehive housekeeping cleanup processes. These cleanup tasks include the physical removal of purged resources, meetings and tasks, and typically occur about one month after the system purges such entities. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the dynamic aspect of composite participants, such as groups and team workspaces. When enabled, future instances of meetings and tasks that include groups or team workspaces as participants will be adjusted automatically to reflect any membership changes. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the delivery of notifications to external participants. When enabled, external participants of meetings and tasks will receive e-mail notifications to inform them of new or updated invitations and assignments. Notification e-mails can include iCalendar attachments. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Send external mail notifications for meetings that are formatted with iMIP information so that the external recipients can easily import them into their own calendar when using a client that is iMIP capable. This option offers better interoperability with MS Outlook and Google Calendar but the default option (false) is more widely supported. |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Enables or disables the generic Time Management business event integration. Does not apply to business events prefixed by TM_, which are raised independently of this property's setting. Enabling generic business events has performance implications. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Enables or disables presence integration. When enabled, the system will automatically set users' presence settings to "In a meeting" during the periods they are scheduled to attend meetings created in Oracle Beehive. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
75 |
All permitted values |
Yes |
No |
Maximum number of occurrences allowed for recurring meetings where the number of occurrences is unspecified. When a recurrence rule is defined during the creation of a new meeting, if the rule does not explicitly specify an end date or a number of occurrences, the number of occurrences created is limited to no more than this value. It is not recommended to increase it to a value above 100 as many Calendar interfaces will create recurring meetings without explicitly specifying a limit and this value will be used. This could cause scalability issues in some calendaring flows. Users that need recurring meetings with more occurrences can explicitly request up to MaxOccurrencesPerSeries occurrences. The recommended value is 75. |
|
|
Integer |
150 |
All permitted values |
Yes |
No |
Maximum number of occurrences allowed for any recurring meeting. This value must be greater or equal to MaxOccurrencesForUnboundedRecurrence. Increasing this value can cause scalability issues in some server flows or client flows. It is not recommended to increase this value above 250 as loading such large meetings will cause side effects or delays in some calendar interfaces. The recommended value is 150. |
|
|
int |
500 |
All permitted values |
Yes |
No |
No subscription business events are raised for any TM operation that tries to raise more than this limit. This is to reduce the potential load caused by having to raise too many business events for large operations. It is currently only supported for operations relating to meetings and calendars. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
n/a |
All permitted values |
Yes |
No |
Defines time periods during which certain non-essential background tasks should not be run. You can define periods for each day, set an entire day to busy, and use the property 'CanRunDuringSystemBusyPeriod' to allow certain tasks to be run during defined busy periods. |
||
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
No other properties exist for TimeManagementService.AccessControlComputationTaskProperties .
The following properties are available for TimeManagementService.ChangeLogsCleanupTaskProperties:
Table 4-134 TimeManagementService.ChangeLogsCleanupTaskProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
Enables or disbales running the task during the configured system busy period (see property SystemBusyPeriod). When disabled (false), the task will not be allowed to run during the defined SystemBusyPeriod; it will only be run outside that period. |
No other properties exist for TimeManagementService.ContainerSyncTaskProperties .
The following properties are available for TimeManagementService.MethodMonitoringCleanupTaskProperties:
Table 4-135 TimeManagementService.MethodMonitoringCleanupTaskProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
Enables or disbales running the task during the configured system busy period (see property SystemBusyPeriod). When disabled (false), the task will not be allowed to run during the defined SystemBusyPeriod; it will only be run outside that period. |
The following properties are available for TimeManagementService.PurgedItemsCleanupProperties:
Table 4-136 TimeManagementService.PurgedItemsCleanupProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
Enables or disbales running the task during the configured system busy period (see property SystemBusyPeriod). When disabled (false), the task will not be allowed to run during the defined SystemBusyPeriod; it will only be run outside that period. |
The following properties are available for TimeManagementService.ResourceCleanupProperties:
Table 4-137 TimeManagementService.ResourceCleanupProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
Enables or disbales running the task during the configured system busy period (see property SystemBusyPeriod). When disabled (false), the task will not be allowed to run during the defined SystemBusyPeriod; it will only be run outside that period. |
The following properties are available for TimeManagementService.ResourceConsistencyProperties:
Table 4-138 TimeManagementService.ResourceConsistencyProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
Enables or disbales running the task during the configured system busy period (see property SystemBusyPeriod). When disabled (false), the task will not be allowed to run during the defined SystemBusyPeriod; it will only be run outside that period. |
The following properties are available for TimeManagementService.StandardContextCleanupProperties:
Table 4-139 TimeManagementService.StandardContextCleanupProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
Enables or disbales running the task during the configured system busy period (see property SystemBusyPeriod). When disabled (false), the task will not be allowed to run during the defined SystemBusyPeriod; it will only be run outside that period. |
The following properties are available for TimeManagementService.SystemBusyPeriod:
Table 4-140 TimeManagementService.SystemBusyPeriod Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
7:00-24:00 |
This property has a customized constraint. |
Yes |
No |
Defines, for this day, the period(s) during which certain non-essential background tasks should not be run. You can set 'XX:XX-YY:YY' to represent a 24h time range, 'BusyAllDay' to block the whole day, or 'NotBusy' to make the whole day available for such tasks. |
|
|
String |
7:00-24:00 |
This property has a customized constraint. |
Yes |
No |
Defines, for this day, the period(s) during which certain non-essential background tasks should not be run. You can set 'XX:XX-YY:YY' to represent a 24h time range, 'BusyAllDay' to block the whole day, or 'NotBusy' to make the whole day available for such tasks. |
|
|
String |
NotBusy |
This property has a customized constraint. |
Yes |
No |
Defines, for this day, the period(s) during which certain non-essential background tasks should not be run. You can set 'XX:XX-YY:YY' to represent a 24h time range, 'BusyAllDay' to block the whole day, or 'NotBusy' to make the whole day available for such tasks. |
|
|
String |
NotBusy |
This property has a customized constraint. |
Yes |
No |
Defines, for this day, the period(s) during which certain non-essential background tasks should not be run. You can set 'XX:XX-YY:YY' to represent a 24h time range, 'BusyAllDay' to block the whole day, or 'NotBusy' to make the whole day available for such tasks. |
|
|
String |
7:00-24:00 |
This property has a customized constraint. |
Yes |
No |
Defines, for this day, the period(s) during which certain non-essential background tasks should not be run. You can set 'XX:XX-YY:YY' to represent a 24h time range, 'BusyAllDay' to block the whole day, or 'NotBusy' to make the whole day available for such tasks. |
|
|
String |
7:00-24:00 |
This property has a customized constraint. |
Yes |
No |
Defines, for this day, the period(s) during which certain non-essential background tasks should not be run. You can set 'XX:XX-YY:YY' to represent a 24h time range, 'BusyAllDay' to block the whole day, or 'NotBusy' to make the whole day available for such tasks. |
|
|
String |
7:00-24:00 |
This property has a customized constraint. |
Yes |
No |
Defines, for this day, the period(s) during which certain non-essential background tasks should not be run. You can set 'XX:XX-YY:YY' to represent a 24h time range, 'BusyAllDay' to block the whole day, or 'NotBusy' to make the whole day available for such tasks. |
The following properties are available for TimeZoneService:
Table 4-141 TimeZoneService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
No other properties exist for TimeZoneService.DatabaseConfiguration .
The following properties are available for TranscodingService:
Table 4-142 TranscodingService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
/INBOX |
All permitted values |
Yes |
No |
description bundle not set |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for UdsCache:
The following properties are available for UdsCacheService:
Table 4-144 UdsCacheService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
5 |
All permitted values |
Yes |
No |
description bundle not set |
|
|
int |
1000 |
Min=100, Max=10000 |
Yes |
No |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
description bundle not set |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
50 |
Min=10, Max=100 |
Yes |
No |
description bundle not set |
|
|
int |
10000 |
Min=100, Max=2147483647 |
Yes |
No |
description bundle not set |
|
|
int |
3600 |
Min=60, Max=2147483647 |
Yes |
No |
description bundle not set |
|
|
int |
100 |
Min=1, Max=9999 |
Yes |
No |
description bundle not set |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
int |
60 |
Min=5, Max=1003600 |
Yes |
No |
description bundle not set |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for UnmanagedBeehiveInstance:
Table 4-145 UnmanagedBeehiveInstance Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
1 |
This property has a customized constraint. |
Yes |
No |
The number of processors committed for the current Oracle Beehive instance. This figure is used by the sizing algorithm to calculate the number of server and client Beehive Transport Infrastructure (BTI) workers, as well as the Oracle Containers for Java (OC4J) instances, required to support the current Oracle Beehive instance. |
|
|
Integer |
n/a |
This property has a customized constraint. |
Yes |
No |
The amount of physical memory in megabytes (MBs) committed for the current Oracle Beehive instance. This figure is used by the sizing algorithm to calculate the number of Oracle Containers for Java (OC4J) instances required for the current Oracle Beehive instance. |
|
|
String |
n/a |
All permitted values |
Yes |
Yes |
The name of the current Oracle Beehive instance. |
|
|
n/a |
All permitted values |
Yes |
No |
The Oracle Beehive Transport Infrastructure (BTI) associated with the current Oracle Beehive instance. |
||
|
n/a |
All permitted values |
Yes |
No |
A reference to a SystemObject that holds the properties used to configure diagnosability functionality. You do not directly modify the value of this property. You modify the properties of the referenced DiagnosabilitySettings object. |
||
|
n/a |
All permitted values |
Yes |
No |
A reference to the HttpServer SystemObject for the current Oracle Beehive instance. You do not directly modify the value of this property. You configure the HTTP Server by modifying the properties of the referenced HttpServer object. |
||
|
File |
n/a |
All permitted values |
Yes |
No |
Path of the keystore file associated with the current Oracle Beehive instance. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
Password for the keystore file associated with the current Oracle Beehive Instance. |
|
|
File |
beehive/logs |
All permitted values |
Yes |
No |
The base directory where Oracle Beehive will store its log files. |
|
|
Set<ManagedOc4j> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of references to the SystemObjects that configure the OC4J instances deployed in the current Oracle Beehive instance. The system automatically manages the value of this property. You must never directly modify the value. |
|
|
n/a |
All permitted values |
No |
No |
This is a reference to the SystemObject that configures OPMN for the current Oracle Beehive instance. The system automatically manages the value of this property. You must never directly modify the value. |
||
|
String |
n/a |
All permitted values |
No |
Yes |
The Oracle home for the current Oracle Beehive instance. |
|
|
n/a |
All permitted values |
No |
No |
This is a reference to the SystemObject that represents the Server associated with the current Oracle Beehive instance. The system automatically manages the value of this property. |
||
|
String |
n/a |
All permitted values |
Yes |
No |
Directory path of the Oracle Wallet associated with the current Oracle Beehive instance. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
The password for the Oracle Wallet associated with the current Oracle Beehive instance. |
The following properties are available for UnmanagedOc4j:
Table 4-146 UnmanagedOc4j Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
the password of the oc4j admin user |
|
|
String |
oc4jadmin |
All permitted values |
Yes |
No |
the name of the oc4j admin user |
|
|
Set<BeehiveJ2eeApplication> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of BeehiveJ2eeApplications associated with the Oc4j instance. |
|
|
n/a |
All permitted values |
Yes |
No |
This database holds the configuration data and holds business data for any Enterprise that does not have its own dedicated storage. |
||
|
String |
n/a |
All permitted values |
No |
No |
The host name of the server the UnmanagedOc4j belongs to. |
|
|
String |
n/a |
All permitted values |
No |
No |
the name of the oc4j |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The opmn request port used to contact the UnmanagedOc4j. If null, the RMI port must be set. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
A Boolean flag that is used to enable/disable the pseudo-translation in Beehive Resource Bundle. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The class name of pseudo translation algorithm that will be used for translation process by Beehive Resource Bundle. |
|
|
Set<ResourceAdapterInstance> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The list of ResourceAdapterInstances associated with the Oc4j instance. |
|
|
int |
1200 |
Min=1, Max=2147483647 |
Yes |
No |
RMI client timeout value (in seconds) for this Oc4j. |
|
|
int |
5000 |
Min=1, Max=10000 |
Yes |
No |
RMI lookup timeout value (in milliseconds) for this Oc4j. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The RMI port used to contact the UnmanagedOc4j |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The wallet directory of this UnmanagedOc4j. |
|
|
SecureString |
n/a |
All permitted values |
Yes |
No |
The wallet password of this UnmanagedOc4j. |
No other properties exist for UnsupportedSystemObject .
The following properties are available for Urm:
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
BeeAdapter |
All permitted values |
No |
Yes |
Records Management Service registers itself as an external agent with URM. This property represents the external agent name that is used by RM Service during registration with URM. |
|
|
long |
1 |
Min=1, Max=10000 |
Yes |
No |
Records Management Service Agent periodically loads disposition instructions from URM. This number specifies in hours the time interval between two successive loads of disposition instructions from URM. Default is one hour. |
|
|
long |
1 |
Min=1, Max=10000 |
Yes |
No |
Records Management Service Agent periodically processes disposition instructions from URM in batches. This indicates the time interval in hours between two successive runs to process and acknowledge the dispositions received from URM. Default is one hour. |
|
|
SecureString |
n/a |
All permitted values |
No |
Yes |
The password of the Records Management Administrator in URM. This is used by Records Management Adapter to connect and file records in the URM Deployment. |
|
|
String |
rmadmin |
All permitted values |
No |
Yes |
The user name of the Records Management Administrator in URM. The Records Management Adapter connects to URM as this user to file records in the URM deployment. |
|
|
String |
n/a |
All permitted values |
No |
Yes |
The Beehive user account used to store outgoing emails to be filed as records. |
|
|
String |
n/a |
All permitted values |
No |
Yes |
Records Management Service interacts with URM through Web Services. This URL indicates the service end point URL of the URM deployment for accessing URM Web Services. Typically, the URL is of the form http://host:port/{yoursitename}/{yoursitename}plg. |
The following properties are available for UserDirectoryService:
Table 4-148 UserDirectoryService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Configuration parameter for UDS service. |
||
|
List<CustomAttribute> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Framework to register the custom properties with UDS service. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
List<DirectoryProfile> (Structural property) |
n/a |
All permitted values |
Yes |
No |
User Directory Service can have many directory profiles. Each of them will point to an external directory server |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for UserDirectoryService.AttributeMap:
The following properties are available for UserDirectoryService.ConfigurationParameters:
Table 4-150 UserDirectoryService.ConfigurationParameters Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
int |
6 |
All permitted values |
Yes |
No |
Database retry count. |
|
|
int |
30000 |
All permitted values |
Yes |
No |
Database retry in milli seconds. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Whether global address list entries are access checked when loading the global address list. It may be useful to set this to false if the global address list is fully public. |
|
|
int |
3 |
All permitted values |
Yes |
No |
Count should not exceed super max count. |
|
|
int |
5 |
All permitted values |
No |
No |
Super max count is the upper limit. And this is applicable to contacts only |
No other properties exist for UserDirectoryService.ConfigurationParameters.Attribute .
The following properties are available for UserDirectoryService.CustomAttribute:
Table 4-151 UserDirectoryService.CustomAttribute Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
Text describing the property. This is an optional field |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Custom property name being registered. |
|
|
UserDirectoryService.CustomAttribute.CustomPropertyType (Legal values: STRING, BOOLEAN, DOUBLE, DATETIME, COLLABID) |
STRING |
All permitted values |
Yes |
No |
Property types supported are STRING, BOOLEAN, DOUBLE, DATETIME and IDENTIFIER. |
The following properties are available for UserDirectoryService.DirectoryAttributeMap:
Table 4-152 UserDirectoryService.DirectoryAttributeMap Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Map<String,UserDirectoryService.AttributeMap> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Each object type can have its own Attribute mapping. Allowed object types are ENTERPRISE_USER, EXTENDED_ENTERPRISE_USER, EXTERNAL_PERSON and STATIC_GROUP |
The following properties are available for UserDirectoryService.DirectoryCache:
Table 4-153 UserDirectoryService.DirectoryCache Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
false |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.UserDirectoryServiceResourceBundle, key UDS_DIR_CACHE_ENABLED_LONG_DESC |
|
|
int |
0 |
All permitted values |
Yes |
No |
Maximum number of cached entites; a value of zero will disable snapshot caching. This parameter influences the variable size of the cache. |
|
|
int |
0 |
All permitted values |
Yes |
No |
description not found Can't find resource for bundle oracle.ocs.management.model.UserDirectoryServiceResourceBundle, key UDS_DIR_CACHE_RIM_PROJ_LONG_DESC |
The following properties are available for UserDirectoryService.DirectoryProfile:
Table 4-154 UserDirectoryService.DirectoryProfile Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
UserDirectoryService.DirectoryProfile.ProfileType (Legal values: DEFAULT, NON_DEFAULT) |
n/a |
All permitted values |
Yes |
No |
Profiles can have flags like DEFAULT or NON_DEFAULT. If a profile is set as default, then the ldap server object is set on the Site. If it is NON_DEFAULT then, the ldapserver is available with the directory profile |
|
|
n/a |
All permitted values |
Yes |
No |
Attribute map of a directory profile will map source attributes to that of target. A profile can contain mappings for different types of objects like ENTERPRISE_USER, EXTENDED_ENTERPRISE_USER, EXTERNAL_PERSON and STATIC_GROUP |
||
|
List<GroupTypeMapEntry> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Group type map of a directory profile will help in synchronizing a group from external directory to target directory. The mapping could be based on the attribute or a DN of the group |
|
|
UserDirectoryService.DirectoryProfile.ProfileState (Legal values: ENABLE, DISABLE) |
DISABLE |
All permitted values |
Yes |
No |
Profiles can have state like ENABLE or DISABLE. If the profile is in enabled state, then synchronization will happen from external directory. If it is in disabled state, then synchronization will be turned off. By default the directory profile is disabled |
|
|
List<ScopeMapEntry> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Scope type map of a directory profile will help in synchronizing a user or group from external directory to target directory. The mapping could be based on the attribute or a DN of the user or group |
|
|
List<UserTypeMapEntry> (Structural property) |
n/a |
All permitted values |
Yes |
No |
User type map of a directory profile will help in synchronizing a user from external directory to target directory. The mapping could be based on the attribute or a DN of the user |
The following properties are available for UserDirectoryService.FieldMap:
Table 4-155 UserDirectoryService.FieldMap Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
Field name can be mapped to an ATTRIBUTE or an ADDRESS or a PROPERTY. Givenname and familyname are some of the examples |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Field sub type is mapped to the address schemes. MAILTO and TEL are some of the examples |
|
|
UserDirectoryService.FieldMap.BeehiveFieldType (Legal values: ATTRIBUTE, PROPERTY, ADDRESS, PRINCIPAL) |
n/a |
All permitted values |
Yes |
No |
Target directory fields can be of type ATTRIBUTE or an ADDRESS or a PROPERTY. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Source attribute will have the name of the attribute, which will be mapped to the target attribute. Givenname and sn are some of the examples of the source attribute |
|
|
UserDirectoryService.FieldMap.SourceSpecialHandlingType (Legal values: PROXY) |
n/a |
All permitted values |
Yes |
No |
Source special handling is relevant to Activate Directory. Valid value is PROXY |
|
|
List<SourceTargetValueMapping> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Contains the value mapping between source and target.Used mainly for external inbox feature |
The following properties are available for UserDirectoryService.FieldMap.SourceTargetValueMapping:
Table 4-156 UserDirectoryService.FieldMap.SourceTargetValueMapping Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
Attribute value at the external directory. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Attribute value in the target directory. |
The following properties are available for UserDirectoryService.GroupTypeMapEntry:
Table 4-157 UserDirectoryService.GroupTypeMapEntry Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
UserDirectoryService.DirectoryProfile.GroupType (Legal values: STATIC_GROUP) |
n/a |
All permitted values |
Yes |
No |
Allowed value is STATIC_GROUP. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Name of the external directory attribute. Givenname and sn are some of the examples |
|
|
UserDirectoryService.DirectoryProfile.FieldType (Legal values: DN, ATTRIBUTE) |
n/a |
All permitted values |
Yes |
No |
Source field type can be an ATTRIBUTE or a DN. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Value associated with external directory attribute. |
The following properties are available for UserDirectoryService.LdapDirectoryProfile:
Table 4-158 UserDirectoryService.LdapDirectoryProfile Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
UserDirectoryService.DirectoryProfile.ProfileType (Legal values: DEFAULT, NON_DEFAULT) |
n/a |
All permitted values |
Yes |
No |
Profiles can have flags like DEFAULT or NON_DEFAULT. If a profile is set as default, then the ldap server object is set on the Site. If it is NON_DEFAULT then, the ldapserver is available with the directory profile |
|
|
n/a |
All permitted values |
Yes |
No |
Attribute map of a directory profile will map source attributes to that of target. A profile can contain mappings for different types of objects like ENTERPRISE_USER, EXTENDED_ENTERPRISE_USER, EXTERNAL_PERSON and STATIC_GROUP |
||
|
List<GroupTypeMapEntry> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Group type map of a directory profile will help in synchronizing a group from external directory to target directory. The mapping could be based on the attribute or a DN of the group |
|
|
n/a |
All permitted values |
Yes |
No |
Ldap server has the details of the external directory, using which the User Directory Service would connect and get the user and group data. |
||
|
int |
30 |
This property has a customized constraint. |
Yes |
No |
Time interval at which the external directory will be polled by the synchronization engine. The poll interval is in seconds |
|
|
UserDirectoryService.DirectoryProfile.ProfileState (Legal values: ENABLE, DISABLE) |
DISABLE |
All permitted values |
Yes |
No |
Profiles can have state like ENABLE or DISABLE. If the profile is in enabled state, then synchronization will happen from external directory. If it is in disabled state, then synchronization will be turned off. By default the directory profile is disabled |
|
|
List<ScopeMapEntry> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Scope type map of a directory profile will help in synchronizing a user or group from external directory to target directory. The mapping could be based on the attribute or a DN of the user or group |
|
|
List<UserTypeMapEntry> (Structural property) |
n/a |
All permitted values |
Yes |
No |
User type map of a directory profile will help in synchronizing a user from external directory to target directory. The mapping could be based on the attribute or a DN of the user |
The following properties are available for UserDirectoryService.MembershipMapEntry:
Table 4-159 UserDirectoryService.MembershipMapEntry Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
CollabId |
n/a |
All permitted values |
Yes |
No |
Identifier of the organization into which the users or groups will be synchronized. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Organization name can be specified and this field is optional. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Name of the external directory attribute. Givenname and sn are some of the examples |
|
|
UserDirectoryService.DirectoryProfile.FieldType (Legal values: DN, ATTRIBUTE) |
n/a |
All permitted values |
Yes |
No |
Source field type can be an ATTRIBUTE or a DN. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Value associated with external directory attribute. |
The following properties are available for UserDirectoryService.ScopeMapEntry:
Table 4-160 UserDirectoryService.ScopeMapEntry Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
List<MembershipMapEntry> (Structural property) |
n/a |
All permitted values |
Yes |
No |
Member type map of a directory profile will help in synchronizing a user or group from external directory to target directory. The mapping could be based on the attribute or a DN of the user or group |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Enterprise or organization name can be specified and this field is optional. |
|
|
CollabId |
n/a |
All permitted values |
Yes |
No |
Enterprise or organization identifier should be specified. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Name of the external directory attribute. Givenname and sn are some of the examples |
|
|
UserDirectoryService.DirectoryProfile.FieldType (Legal values: DN, ATTRIBUTE) |
n/a |
All permitted values |
Yes |
No |
Source field type can be an ATTRIBUTE or a DN. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Value associated with external directory attribute. |
The following properties are available for UserDirectoryService.UserTypeMapEntry:
Table 4-161 UserDirectoryService.UserTypeMapEntry Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
Name of the external directory attribute. Givenname and sn are some of the examples |
|
|
UserDirectoryService.DirectoryProfile.FieldType (Legal values: DN, ATTRIBUTE) |
n/a |
All permitted values |
Yes |
No |
Source field type can be an ATTRIBUTE or a DN. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
Value associated with external directory attribute. |
|
|
UserDirectoryService.DirectoryProfile.UserType (Legal values: ENTERPRISE_USER, EXTENDED_ENTERPRISE_USER, EXTERNAL_PERSON) |
n/a |
All permitted values |
Yes |
No |
Can have 3 different types of users. They are ENTERPRISE_USER, EXTENDED_ENTERPRISE_USER and EXTERNAL_PERSON |
The following properties are available for VirtualServer:
Table 4-162 VirtualServer Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The virtual port for MX client |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The secure virtual port for MX client |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The FTP virtual port. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The Http virtual Port. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
If Http SSL is enabled for this VirtualServer. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The secure Http virtual Port. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The VirtualServer Ip Address. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The IMAP virtual port. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If IMAP SSL is enabled. |
|
|
Integer |
993 |
Network Port, Min=1, Max=65536 |
Yes |
No |
The secure IMAP port. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The ServerName of the VirtualServer. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The secure Http virtual Port. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The ServerName of the VirtualServer. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If SMTP authentication is required. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The SMTP virtual port. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
If SMTP SSL is enabled. |
|
|
Integer |
465 |
Network Port, Min=1, Max=65536 |
Yes |
No |
The secure SMTP virtual port. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The XMPP virtual port. |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
If XMPP SSL is enabled. |
|
|
Integer |
n/a |
Network Port, Min=1, Max=65536 |
Yes |
No |
The secure XMPP port. |
The following properties are available for VirusScanConfigurable:
Table 4-163 VirusScanConfigurable Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Boolean |
false |
All permitted values |
Yes |
No |
Indicates if Beehive should over-ride certain return scan statuses. This will allow Beehive to treat what the scan engine considers as INFECTED as CLEAN. |
|
|
VirusScanConfigurable.VirusScanPolicy (Legal values: NO_SCAN_OR_REPAIR, SCAN_ONLY, SCAN_AND_REPAIR) |
NO_SCAN_OR_REPAIR |
All permitted values |
Yes |
No |
Scan policy configured for Beehive. If the policy is set to SCAN_ONLY is set and a request to scan and repair is received, caller will receive an exception. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
List of viruses that Beehive can choose to ignore and treat as un-infected. This list will only be evaluated if the the OverrideEngineResultEnabled is also set to true. |
The following properties are available for VirusScanEngine:
Table 4-164 VirusScanEngine Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
No |
No |
A VirusScanEngineCluster is made up of scan engines of the same type, i.e by the same provider, configured for the Site or Enterprise. This property shows the VirusScanEngineCluster that this engine belongs to. |
The following properties are available for VirusScanEngineCluster:
Table 4-165 VirusScanEngineCluster Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
Long |
600000 |
This property has a customized constraint. |
Yes |
No |
The interval at which Beehive VirusScanner process refreshes its in-memory cache with data from the virus defnitions storage. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Indicator to determine if detailed stats related to virusscanner needs to be captured. These stats include method stats. |
|
|
Boolean |
false |
All permitted values |
Yes |
No |
Indicates if Beehive should over-ride certain return scan statuses. This will allow Beehive to treat what the scan engine considers as INFECTED as CLEAN. |
|
|
VirusScanEngineCluster.ScanEngineCommProtocol (Legal values: ICAP, CUSTOM) |
ICAP |
All permitted values |
Yes |
Yes |
The protocol used by Beehive to communicate with the third-party scan service engine. |
|
|
String |
1.0 |
All permitted values |
Yes |
Yes |
The version of the protocol used to communicate with the third-party scan service. |
|
|
Set<VirusScanEngine> (Structural property) |
n/a |
All permitted values |
Yes |
No |
The set of virus scan engines, of the same type, that are part of this cluster. |
|
|
VirusScanEngineCluster.ScanServiceProvider (Legal values: Symantec, TrendMicro, McAfee) |
Symantec |
All permitted values |
Yes |
Yes |
Engines in a cluster are of the same type and are supplied by this third-party virus scan service provider. |
|
|
VirusScanConfigurable.VirusScanPolicy (Legal values: NO_SCAN_OR_REPAIR, SCAN_ONLY, SCAN_AND_REPAIR) |
NO_SCAN_OR_REPAIR |
All permitted values |
Yes |
No |
Scan policy configured for Beehive. If the policy is set to SCAN_ONLY is set and a request to scan and repair is received, caller will receive an exception. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
List of viruses that Beehive can choose to ignore and treat as un-infected. This list will only be evaluated if the the OverrideEngineResultEnabled is also set to true. |
The following properties are available for VoiceMessageService:
Table 4-166 VoiceMessageService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Integer |
0 |
All permitted values |
Yes |
No |
long description key not set |
|
|
boolean |
true |
All permitted values |
Yes |
No |
long description key not set |
|
|
n/a |
All permitted values |
Yes |
No |
long description key not set |
||
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
String |
n/a |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for VoiceMessageService.EnterpriseProperties:
Table 4-167 VoiceMessageService.EnterpriseProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
n/a |
All permitted values |
Yes |
No |
long description key not set |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
URI to where exclusive (application specific) audio content can be found by a VoiceXML router. This is optional. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The name of the Enterprise. For example, "Oracle" or "General Motors". |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The URI where audio, spoken by a caller, is received by the server and stored in the database. This is optional. Reasons for setting it is if an environment is configured with a load balancer or different security settings. For example, the server may always require SSL, but streaming by not. By default the value is http://[host]:[port]/voice-servlet/vmail/crs. However, if the server is behind a load balancer with multiple midtiers, then the URI of the load balancer should be specified: http://beehive.example.com/voice-servlet/vmail/crs. NOTE: The scheme (http/https), host and port are the only things that are configurable. The remaining parts of the path are note. If NOT set at the Facility level, then the Enterprise value is used. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The URI where audio, spoken by a caller, is received by the server and stored in the database. This is optional. Reasons for setting it is if an environment is configured with a load balancer or different security settings. For example, the server may always require SSL, but streaming by not. By default the value is http://[host]:[port]/voice-servlet/vmail/crs. However, if the server is behind a load balancer with multiple midtiers, then the URI of the load balancer should be specified: http://beehive.example.com/voice-servlet/vmail/crs. NOTE: The scheme (http/https), host and port are the only things that are configurable. The remaining parts of the path are note. If NOT set at the Facility level, then the Enterprise value is used. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
Shared audio refers to audio that is generic across all voice services: integers, digits, phone numbers, dates, times, etc. Setting this is optional. Reasons for setting it is if an environment is configured such that these audio resources are on a separate server from the one currently deployed. By default the value will be relative to the application: ../shared-audio. If NOT set at the Facility level, then the Enterprise value is used. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
The email address that appears in the 'from' field of an email when a voice mail is received from an unknown caller. This email address must exist in Beehive. When the sender is known, then his or her email address is used. But, this email address is only when the caller is unknown and is required to exist, but not monitored to receive email responses. |
The following properties are available for VoiceMessageService.FacilityProperties:
Table 4-168 VoiceMessageService.FacilityProperties Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
URI to where exclusive (application specific) audio content can be found by a VoiceXML router. This is optional. |
|
|
String |
n/a |
All permitted values |
Yes |
No |
long description key not set |
|
|
String |
n/a |
All permitted values |
Yes |
No |
"Facility" is a well-defined technical notion for voice mail. It referes to a group of people and associated telephone equipment and other information, such as the local number to dial in to hear voice messages. Historically, Facilities have been identified with geographical locations, such as corporate headquarters, or the Chicago field office, but this is not strictly necessary. Example of Facility names are "Headquarters" and "Chicago Sears Tower Office". |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The URI where audio, spoken by a caller, is received by the server and stored in the database. This is optional. Reasons for setting it is if an environment is configured with a load balancer or different security settings. For example, the server may always require SSL, but streaming by not. By default the value is http://[host]:[port]/voice-servlet/vmail/crs. However, if the server is behind a load balancer with multiple midtiers, then the URI of the load balancer should be specified: http://beehive.example.com/voice-servlet/vmail/crs. NOTE: The scheme (http/https), host and port are the only things that are configurable. The remaining parts of the path are note. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
The URI where audio, spoken by a caller, is received by the server and stored in the database. This is optional. Reasons for setting it is if an environment is configured with a load balancer or different security settings. For example, the server may always require SSL, but streaming by not. By default the value is http://[host]:[port]/voice-servlet/vmail/crs. However, if the server is behind a load balancer with multiple midtiers, then the URI of the load balancer should be specified: http://beehive.example.com/voice-servlet/vmail/crs. NOTE: The scheme (http/https), host and port are the only things that are configurable. The remaining parts of the path are note. |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
Shared audio refers to audio that is generic across all voice services: integers, digits, phone numbers, dates, times, etc. Setting this is optional. Reasons for setting it is if an environment is configured such that these audio resources are on a separate server from the one currently deployed. By default the value will be relative to the application: ../shared-audio |
The following properties are available for VoiceServletService:
Table 4-169 VoiceServletService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for WebdavService:
Table 4-170 WebdavService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
String |
BASIC |
This property has a customized constraint. |
Yes |
No |
Default authentication scheme for WebDAV server. Accepted values are: BASIC, DIGEST, DIGEST-BASIC. |
|
|
int |
30 |
This property has a customized constraint. |
Yes |
No |
Length of idle time (in minutes) after which browser session will expire. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables collection of Dynamic Monotoring System statistics. |
|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
int |
960 |
This property has a customized constraint. |
Yes |
No |
Idle time (in minutes) until the Pure WebDAV client session is timed out. |
|
|
String[] |
[index.html, index.htm] |
All permitted values |
Yes |
No |
The array (comma-delimited list) of welcome document names that are served up if a GET is done on a collection containing one of these documents. |
|
|
int |
3 |
Min=1, Max=6 |
Yes |
No |
The depth limit to be used for PROPFIND when depth of infinity is specified by the WebDAV client. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables display of the last-modified user in generated HTML index pages. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables display of the last-modified time (date and time) in generated HTML index pages. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables display of locked status in generated HTML index pages. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Enables or disables display of versioning information in generated HTML index pages. |
|
|
int |
261888 |
Min=16384, Max=1048576 |
Yes |
No |
The buffer size, in bytes, used while downloading stream data. Deployments that typically stream small files, as well as those with limited midtier memory, may improve performance by setting this value below the default. Deployments with a large amount of midtier memory may likewise improve performance by setting this value above the default. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
4 |
This property has a customized constraint. |
Yes |
No |
The minimum timeout value (in minutes) that a client can request while acquiring a lock. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
int |
260096 |
Min=16384, Max=1048576 |
Yes |
No |
The buffer size, in bytes, used while uploading stream data. Deployments that typically stream small files, as well as those with limited midtier memory, may improve performance by setting this value below the default. Deployments with a large amount of midtier memory may likewise improve performance by setting this value above the default. |
|
|
int |
180 |
This property has a customized constraint. |
Yes |
No |
Length of time (in minutes) before user preferences are refreshed. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables the WebDAV server. When set to false, the WebDAV server will return an exception. |
The following properties are available for WikiService:
Table 4-171 WikiService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Specifies whether or not Rich Text descriptions will be filtered by AntiSamy prior to display in the Team Collaboration Client to remove potentially malicious xhtml and javascript. Valid values: true, false |
|
|
String |
oracle/ocs/amshare/util/antisamy-strict.xml |
All permitted values |
Yes |
No |
Path to the AntiSamy policy xml file, used to configure the AntiSamy XHTML filtering of Rich Text descriptions. The path may be absolute or relative to the Beehive home directory. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
Specifies whether or not users can insert raw html into wiki pages using the html plugin. Valid values: true, false |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
List<String> |
n/a |
All permitted values |
Yes |
No |
This service property allows administrators to specify a list of regular expressions that will be applied to rendered WikiPages for display purposes. The regular expressions should follow the standard Perl regular expression syntax, for example: s/match/replace/g. Please see Perl documentation for more information on regular expressions. The regular expressions are applied to each text node in the HTML after all XHTML related escaping is done so it is the responsibility of the administrator to write regular expressions that are safe for insert directly into HTML pages. This also means that when attempting to match characters <, >, &, ", ', the administrator should use <, >, &,", ' instead, respectively. The regular expressions will be applied to the WikiPage text nodes in the order that they are provided in beectl. Please note that the administrator must re-specify all regular expressions if they want to add another one. Similarly, if the administrator wants to remove one, then all of the existing regular expressions need to be specified except for the one to be removed. For these reasons, administrators are strongly encouraged to keep a file containing the last command that was used to modify this property. If a user enters a set of regular expressions, and observes that the intended text is not being replaced in the wiki pages, the user can set the log level of BEECLIENT to INFO and search for MalformedPerl5PatternException to determine what the syntax error(s) may be in the regular expressions. To remove all regular expressions, please run modify_property with the --revert_to_default flag. |
The following properties are available for WorkspacesService:
Table 4-172 WorkspacesService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
boolean |
true |
All permitted values |
Yes |
No |
Allows or disallows uploads of HTML files with client-side scripting. This is enabled by default, but administrators may wish to disable this in order to prevent malicious JavaScript code from executing on the server. |
|
|
String |
This property has a customized constraint. |
Yes |
No |
Specifies a comma-separated list of file extensions that are disallowed from being uploaded to the Beehive server, without the periods and with no spaces after the commas. This is intended to be used so administrators can block potential security vulnerabilities from entering the system. For example, a list might look like: xls,doc,swf |
||
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
int |
261888 |
Min=16384, Max=1048576 |
Yes |
No |
The buffer size, in bytes, used while downloading stream data from the database layer. Deployments that typically stream small files, as well as those with limited memory, may improve performance by setting this value below the default. Deployments with larger memory may likewise improve performance by setting this value above the default. |
|
|
int |
260096 |
Min=16384, Max=1048576 |
Yes |
No |
The buffer size, in bytes, used while uploading stream data to the database layer. Deployments that typically stream small files, as well as those with limited memory, may improve performance by setting this value below the default. Deployments with a larger memory may likewise improve performance by setting this value above the default. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
int |
5000 |
This property has a customized constraint. |
Yes |
No |
The group-max property specifies the maximum number of entries to retain for each group (defined by RecentActivityPurgeType property) during a scheduled-purge of the recent activities table. The scheduled-purge keeps, for each group (defined by RecentActivityPurgeType property), at most N entries, if the number of entries specified in this property equals N. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables e-mail notification to a user when joining or leaving a workspace. |
|
|
int |
5 |
This property has a customized constraint. |
Yes |
No |
The group-min property specifies the minimum number of entries to retain for each group (defined by RecentActivityPurgeType property) during a scheduled-purge of the recent activities table. The scheduled-purge ensures that the most recent activities of each group are kept for up to the number of entries specified in this property, preventing them from being purged even if they are older than RecentActivityDaysToLive. |
|
|
boolean |
true |
All permitted values |
Yes |
No |
Enables or disables e-mail notification to workspace coordinators when workspace quota is reached. |
|
|
int |
5 |
This property has a customized constraint. |
Yes |
No |
Percentage of quota, expressed as an integer, that may be exceeded the first time prior to automatic rejection of further data additions to a workspace. For example, if 1 GB of quota is allocated to the workspace, and the quota overflow percentage is 5, and hard quota has not been reached, then data additions will succeed if workspace size will be below 1.05 GB after this. Once hard quota is reached, data addition will be rejected even if workspace size is below 1.05 GB. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
int |
90 |
This property has a customized constraint. |
Yes |
No |
The Days-To-Live property specifies the maximum days a recent activity entry will be kept during a scheduled purge of the recent activities table. The recent activities table is expected to be huge, and therefore a scheduled job is used regularly to automatically clean up old entries that are deemed less relevant. The purge ensures that each group (indicated by RecentActivityPurgeType property) will have a minimum number of rows (see MinRecentActivitiesPerGroup property), and then keep only recent activities within Days-To-Live days as long as the total number of rows per group does not exceed the maximum (see MaxRecentActivitiesPerGroup property). |
|
|
boolean |
false |
All permitted values |
Yes |
No |
When this property is set to true, recent activities in personal workspaces are tracked. Out of box, the value is false |
|
|
int |
1 |
Min=0, Max=2147483647 |
Yes |
No |
The purge-type property specifies how the scheduled-purge for recent activities table is performed. Currently it can be set to 0 (no purging), 1 (purge-by-workspace) or 2 (purge-by-user). Purge-by-workspace indicates the ranking of recent activity is done per workspace, which means it will keep at least MinRecentActivitiesPerGroup (and at most MaxRecentActivitiesPerGroup) the most recent entries captured in each workspace. Purge-by-user indicates the ranking of recent activity is done per user. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for XmppService:
Table 4-173 XmppService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
List<String> |
[example.com] |
This property has a customized constraint. |
Yes |
No |
All domains for which xmpp allows login. For example oracle.com, sales.idc.com, org.company.com |
|
|
String |
en |
This property has a customized constraint. |
Yes |
No |
Language used by server. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
List<String> |
[] |
This property has a customized constraint. |
Yes |
No |
purpose of this property is to send relevant messages to users when they perform operation which are either not allowed of carried out with wrong inputs. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
List<SearchField> |
[first, last, email] |
All permitted values |
Yes |
No |
Fields on which a user can search User Directory. |
|
|
List<AgentType> |
[uds] |
All permitted values |
Yes |
No |
List of all agents supported by xmpp server |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
|
List<String> |
[] |
This property has a customized constraint. |
Yes |
No |
specify the rules for different xmpp messenger clients, sending message to user and whether disconnect the user or let him/her continue on using a particular client |
|
|
int |
5222 |
Network Port, Min=1, Max=65536 |
Yes |
No |
Xmpp Server accepts connection on this port |
|
|
int |
5223 |
Network Port, Min=1, Max=65536 |
Yes |
No |
Port for SSL communication |
|
|
int |
5 |
Min=0, Max=10 |
Yes |
No |
keep-alive time, in minutes, used for detecting the stale connections. Negative or zero value disables the stale connection detection timer |
The following properties are available for ZimbraConnectorService:
Table 4-174 ZimbraConnectorService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
The following properties are available for ZimbraUIService:
Table 4-175 ZimbraUIService Properties
| Name | Data Type | Default Values | Accepted Values | Mutable | Read Only | Description |
|---|---|---|---|---|---|---|
|
n/a |
All permitted values |
Yes |
No |
Service specific database storage information. |
||
|
List<Integer> |
n/a |
This property has a customized constraint. |
Yes |
No |
The database retry interval list is a list of non-negative integer values used to configure the desired retry behavior when database operations fail. Beehive components that interact with the database will retry failed operations as many times as the number of values in the list. The values of the integers in the list configure the length of the interval guaranteed to elapse before each successive retry is attempted. The units are in milliseconds. If the list is empty, failed operations will not be retried. There is no limit on the number of values in the list, so there is no limit on how many retry attempts may be configured. A value of 0 causes immediate retry. |
|
|
Level (Legal values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) |
OFF |
All permitted values |
Yes |
No |
The standard logging level that can be used to control logging output. The levels are ordered. Enabling logging at a given level also enables logging at all higher levels. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). In addition there is a level OFF that can be used to turn off logging, and a level ALL that can be used to enable logging of all messages. |
|
|
Boolean |
true |
All permitted values |
Yes |
No |
Priority for enabling read-only access for the serice. |
|
|
boolean |
false |
All permitted values |
Yes |
No |
long description key not set |
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|