ObjectServer properties and command-line options

ActingPrimary is set to TRUE in the backup ObjectServer for the period during which the backup ObjectServer acts as the primary server. Otherwise, this property is set to FALSE in the backup ObjectServer.

ActingPrimary is always set to TRUE in the primary ObjectServer,

• A member of the Normal group can modify a row that is assigned to themselves or the nobody user.
• A member of the Administrator group can modify a row that is assigned to themselves, the nobody user, or a member of the Normal group.

If the AlertSecurityModel property is enabled (1), only users in the group that owns the row can modify the row. In this case, a member of the Normal or Administrator group can modify a row that is assigned to a group of which they are a member.

A member of the System group can always modify any row.

If TRUE, this can be enabled for each user using Netcool/OMNIbus Administrator.

If TRUE, this can be enabled for each user using Netcool/OMNIbus Administrator.

If FALSE, the timed refresh check box is grayed out in the Refresh tab of the Event List Preferences window and timed refresh is disabled.

Statistics are gathered unless the -autoenabled command-line option is set to FALSE, which disables all automations.

The default FALSE setting enables heartbeating, and prevents invalid and unnecessary client timeouts. If the ObjectServer is active but busy, this setting causes the ObjectServer to send a pop-up message to a connected client, with details of the type of processing in progress.

The value that you specify must be identical to that used when you ran nco_aes_crypt with the -c setting, to encrypt the string values.

Use this property in conjunction with the ConfigKeyFile property.

Specifies the path and name of the key file that contains the key used to decrypt encrypted string values (including passwords) in the properties file.

The key is used at run time to decrypt string values that were encrypted with the nco_aes_crypt utility. The key file that you specify must be identical to the file used to encrypt the string values when you ran nco_aes_crypt with the -k setting.

Use this property in conjunction with the ConfigCryptoAlg property.

The maximum value is 1024. The default value is 256. Up to two connections can be used by the system. If the ObjectServer reaches the specified value, no further connections are possible until some of the previously made connections are dropped.

By default, deletes are logged to the file $NCHOME/omnibus/log/servername_deletes_file.logn.

• <0: No logging
• 0: Client type (application ID; for example, ctisql for nco_sql) and SQL run. This is the default log level.
• 1: Time, user ID, client type, and SQL run.

The output from a single delete command is never split between log files. Therefore, log files can be larger than the specified size.

The default log file size is 1024 KB.

If the Profile property is set to TRUE, at the end of each granularity period, the ObjectServer writes a summary to the profiling log of the time spent for each client connection.

0: When set to this value (the default):

• If the client is not a gateway, the number in the Tally field is incremented.
• The LastOccurrence, Summary, and AlertKey fields are updated with the new values and the StateChange and InternalLast fields are updated with the current time.
• If the new Severity is greater than 0 (clear) and the old Severity was 0, the alert is also updated with the new Severity value.

1: If the client is a gateway, the new event replaces old event.

2: If the client is a gateway, the new event is ignored.

3: When set to this value:

• For all clients, the number in the Tally field is incremented.
• The LastOccurrence, Summary, and AlertKey fields are updated with the new values, and the StateChange and InternalLast fields are updated with the current time.
• If the new Severity is greater than 0 (clear) and the old Severity was 0, the alert is also updated with the new Severity value.

For example, a computer named sfo might actually be identified on the network as sfo.bigcorp.org. To allow clients to connect to the ObjectServer on sfo, set this property to sfo.bigcorp.org.

The default is the name of the local computer, as reported by the hostname command.

You can also specify the port in the /etc/services file on the host machine.

If this time is exceeded, or if the ObjectServer is down, a communication error occurs and the alert is instead sent to the cache file.

The default is 60 seconds.

The default is 10.

If set to TRUE, the logging system opens the number of files specified for the pool at startup, and keeps them open for the duration of its run. (You define the number of files in the pool using the LogFilePoolSize property.) When a file in the pool reaches its maximum size (as specified by the MaxLogFileSize property), the logging system writes to the next file. When all the files in the pool are at maximum size, the logging system truncates the first file in the pool and starts writing to it again. Files in the pool are named using the format servername.log_ID, where ID is a two-digit number starting from 01, to the maximum number specified for the LogFilePoolSize property. When the logging system starts to use a file pool, the system writes to the lowest-available file number, regardless of which file it was writing to when it last ran.

The default is FALSE. When set to FALSE, the default servername.log file is renamed servername.log_OLD and a new log file is started when the maximum size is reached. If the file cannot be renamed, for example, because of a read lock on the _OLD file, and the LogFileUseStdErr property is set toFALSE , the logging system automatically starts using a pool of log files.

The default is TRUE. If this setting is TRUE and the ObjectServer is run from the command line, messages are logged to the console if the ObjectServer cannot write to the default log file. If this setting is TRUE and the ObjectServer is running as a Windows service, messages are written to a file named %NCHOME%\omnibus\log\nco_objserv*.err if the ObjectServer cannot write to the default log file.

If set to FALSE and the ObjectServer cannot write to the default log file, messages are written to a pool of log files, as set by the LogFileUsePool property.

When it reaches the size specified, the servername.log file is renamed servername.log_OLD and a new log file is started. When the new file reaches the maximum size, it is renamed and the process starts again.

On Windows, if the system cannot write to the specified log file (for example, as the result of a fatal error) it writes the error to a file named %NCHOME%\omnibus\log\nco_objserv*.err.

The default is NCOMS.

The default is $OMNIHOME/log/NCOMS_http_access.log.

The default is omnibus.

The default is ''.

The default is $OMNIHOME/etc/restos/docroot.

The default is FALSE.

The default is FALSE.

The default is 15.

The default is localhost.

The default is 0.

The default is 5.

The default is FALSE.

The default is 0.

The default is ''.

The default is FALSE, which means that the interfaces are disabled.

The default is $OMNIHOME/etc/restos/resourcecfg.json.

Specifies the timestamp format to use in the log file.

Set the value to TRUE to display the timestamp format that is used in Tivoli Netcool/OMNIbus V7.2.1, or earlier. For example: dd/MM/YYYY hh:mm:ss AM or dd/MM/YYYY hh:mm:ss PM when the locale is set to en_GB on a Solaris 9 computer.

Set the value to FALSE to display the ISO 8601 format in the log file. For example: YYYY-MM-DDThh:mm:ss, where T separates the date and time, and hh is in 24-hour clock. The default is FALSE.

On Windows, specify the user name of a valid local account, domain account, or UPN account.

On UNIX, any user who requires access to the process control system must be a member of a UNIX user group (default ncoadmin) that you identify as an administrative group for this purpose. Note that if using Pluggable Authentication Modules (PAM) for authentication, users do not have to be a member of a UNIX user group such as ncoadmin, to gain access to the process control system.

• DES: Data Encryption Standard encryption. Only the first eight characters of a DES-encrypted password are read. Additional characters are ignored.
• AES: Advanced Encryption Standard (AES128) encryption. Only the first 16 characters of an AES128-encrypted password are read. Additional characters are ignored. In FIPS 140–2 mode, the AES option is mandated by the system.

Specify the value of the this property as a colon-separated set of integer values. Each value defines a password requirement. The format is:min_len:alpha_num:digit_num:punct_numtwhere:

• min_len is the password length.
• alpha_num is the minimum number of alphabetic characters.
• digit_num is the minimum number of numeric characters.
• punct_num is the minimum number of punctuation characters.

The default value of 8:1:1:0 indicates that a password must be at least 8 characters long, and contain at least 1 alphabetic character and at least one numeric character. The password need not contain any punctuation characters.

For example, if the property is set to 8:1:1:0 and a user specifies the password abcdefgh590675, the password is rejected because the first 8 characters contains no numeric characters.

After this property is set, the ObjectServer validates all new or changed passwords against this requirement and passwords that do not meet the requirement are rejected. Existing passwords are not validated.

The profile statistics are also logged to the file $NCHOME/omnibus/log/servername_profiler_report.logn every profile statistics interval.

The default value of NETCOOL is useful for single-byte character processing and is provides optimal system performance.

To enable the use of the extended regular expression syntax on single-byte and multi-byte character languages, set the value to TRE. This setting results in decreased system performance.

When TRUE, the format specified by the PasswordFormat property is enforced.

The default is FALSE.

If FALSE, connections from a proxy server can run any ObjectServer SQL commands.

The debug and info levels generate messages for authentication successes and failures, while warn and error levels generate messages for authentication failures only.

• none: Use this value to perform user authentication against the user names and passwords that are stored in the ObjectServer. This setting disables external authentication.
• LDAP: Use this value to externally authenticate users whose credentials are stored in a Lightweight Directory Access Protocol (LDAP) repository.
• PAM: Use this value to authenticate users by using the supplied Tivoli Netcool/OMNIbus PAM, or to externally authenticate users by using a third-party PAM configuration (such as the operating system, or a PAM configuration that is set up to use LDAP credentials).

On UNIX and Linux, the default is PAM. On Windows, the default is none.

The default is FALSE, which disables localized sorting in favor of standard C library (libc) string comparisons. For example, Å will be treated as a variant of A and the two characters will sort near each other. Use this default setting for optimal system performance.

Set the value to TRUE to enable localized sorting. For example, in a Danish locale, Å will be treated as a separate letter that sorts just after Z. Note that specifying this setting results in decreased system performance.

The values are:

• OFF: Sorting is case-insensitive, and uppercase and lowercase letters are ordered in accordance with their tertiary sort weights.
• UPPERFIRST: Uppercase characters are sorted before lowercase characters. For example, Account is sorted before account.
• LOWERFIRST: Lowercase characters are sorted before uppercase characters. For example, account is sorted before Account.

The default is OFF.

If TRUE, the log file is uniquely named by appending the process ID of the ObjectServer to the default log file name. For example, if the NCOMS ObjectServer is running as process 1234, the log file is named NCHOME/omnibus/log/ NCOMS.1234.log. The default is FALSE.

If the MessageLog property is set to stderr or stdout, the UniqueLog property is ignored.

Controls the encoding of data that is passed into, or generated by, this application on Windows.

Set the value of -utf8enabled to TRUE to run the application in the UTF-8 encoding. The default is FALSE, which causes the default system code page to be used.