pserver.conf file and parameters
This section contains the information that you need to configure the Publishing Server. For changes to this file to take effect, you must restart the Publishing Server service or process.
The following table describes the default pserver.conf file and all its parameters. You can also view the pserver.conf file for a detailed explanation of the parameters and arguments.
pserver.conf file
Filename | pserver.conf | ||
File path | installationDirectory/pw/server/etc/ps_ hostname or if that file does not exist installationDirectory/pw/server/etc | ||
Description | Contains the configuration settings that control the behavior of the Publishing Server | ||
Parameter name | Description | Default value | |
---|---|---|---|
SystemLogDirName | Specifies the name of the log directory for the publishing server On UNIX platforms, you must specify an NFS path. Specifying a UNC path is not supported. | Log | |
AtriumCMDBPublishOrigin | Enables (T) or disables (F) publishing from publishing server to a cell | T (true) | |
AtriumCMDBHeartbeatInterval | Sets the length of time that the publishing server waits for a heartbeat, a cancel, or a commit from a client during publish preview When no heartbeat is received after this interval, the publish is canceled. | 180 (seconds) | |
AtriumCMDBDefaultEnvId | Identifies the default environment for the BMC Atrium CMDB publication. If the environment does not already exist, it will be created when pserver starts. | PROD | |
AtriumCMDBDefaultAssetDatasetId | Identifies the default asset dataset for the default publish environment of BMC Atrium CMDB. The default environment is created when pserver uses this asset dataset. | BMC.ASSET | |
AtriumCMDBDefaultFilterIds | Lists the default filters. When pserver creates the default environment, it registers the default filters for this environment. | PublishProvidersToSIM,ServiceModelSet,HomeCell,ExtAuth | |
ARSNotifyMode | Specifies the mode in which pserver will receive notifications for certain events in CMDB as per the configuration of ARSNotifyEvents. Valid values are: Pull, Push, None When ARSNotifyMode is set to Pull, pserver will poll regularly via AR API to find the notification events cached by the SIM notify server (ARDBC plugin). When ARSNotifyMode is set to Push, pserver will open a tcp/ip connection with the SIM Notify server (ARDBC plugin) to get the notification events in real-time (i.e. as soon as they occur). When set to None, pserver doesn't take any action to get the notification events. | Pull | |
ARSNotifyPushHeartbeatInterval | Specifies the hearbeating interval in seconds. When you set ARSNotifyMode to Push mode, the heartbeating is enabled between pserver and the ARS Notify plugin. When you set ARSNotifyPushHeartbeatInterval to 0 or to a negative value, the heartbeating is disabled. Heartbeating is disabled by default. | -1 | |
ARSNotifyPullInterval | If ARSNotifyMode is set to Pull, the pserver retrieves (via AR API) the new (newly created since previous retrieval) notification events from SIM Notify server (ARDBC plugin) at the time interval specified by ARSNotifyPullInterval. ARSNotifyPullInterval is the maximum time period for a notification to reach the pserver. | 60 (seconds) | |
ARSNotifyPushHeartbeatTimeout | Specifies the time out period for the AR Notify plugin to acknowledge to a heartbeat received from the pserver. | 5 (seconds) | |
PreviewTimeout | Sets the length of time that publishing server waits for an answer to cancel or commit the publish after publish preview When no answer is received after this interval, the publish is cancelled. | 180 (seconds) | |
CellPublishOrigin | Enables (T) or disables (F) publishing from staging cells | T (true) | |
CellPublishIms | Lists all the staging cells, that is, all the cells that define CellPublish publishing environments. If you want to use the publish -e OVO command, then you have to add the adapter cell to this parameter. If empty, then the command will fail with the message No publish environment OVO found and you must use the following command: "publish -e OVO -p "OriginId=CellPublish" -p "Cell=ovo_java"" | ||
CellPublishGateway | Enables (T) or disables (F) listening by the Publishing Server for incoming IPS_CP_TRIGGER events propagated by a staging cell that will trigger a publication for a CellPublish environment of the cell | T (true) | |
CellPublishGatewayName | Defines the name of gateway that listens for incoming IPS_CP_TRIGGER events to trigger a CellPublish publication This name is looked up in the directory set in IMFileDirectoryName. | Not defined, set by install | |
CellPublishGatewayIms | Lists the cells from which the Publishing Server accepts incoming events If no cell is listed, then all incoming events are accepted. | Not defined | |
CellPublish2CmdbContinueOn Warning | Enables (T) or disables (F) continuation when instances that cannot be imported must skipped The list of skipped instances and the reason they were skipped is sent to the request log. | F (false) | |
CellPublish2CmdbReconJobTimeOut | Defines the length of time, in seconds, that CellPublish2Cmdb checks for the termination of the reconciliation job run. If the interval expires before the reconciliation job run completes, then the request log does not indicate the result. Even though no result is indicated, the reconciliation job might complete successfully after the timeout. | 120 (seconds) | |
CellPublishCommitRetryTime Out | Defines the length of time, in seconds, that CellPublish2Cmdb retries in total to commit the data in the import dataset When a commit fails, a new commit is retried without the offending data. By retrying the commit without the offending date, CellPublish2Cmdb can find all offending data in one run. | 900 (seconds) | |
Cells | Gives the cells for which pserver creates the cell information in BMC Atrium CMDB | ||
ClassInfoValidation | If enabled, the class information of BMC Atrium CMDB and of the cell is validated when publishing. If disabled, then the class information is not validated when being published. Disabling the validation results in slightly better performance when being published. This might be important when increments are really small (a single modification). When disabled, publication might fail when a CI is published with an attribute that does not exist in cell. | T (enabled) | |
CMDBMaxQueryListConditionSize | The number of expressions in a list of a query condition that is limited by the RDBMS. | 500 | |
CMDBNOEQRDTimeOut | The BMC Atrium CMDB Notification Engine supports the Publishing Server to calculate the delta of the resultset of a query. In Atrium CMDB versions earlier to 7.6.04 SP1, the Notification Engine would timeout after a maximum time of 5 minutes because the Filter API RPC Timeoutparameter of BMC Remedy AR Server had a maximum value of 600 seconds. In BMC Atrium CMDB versions 7.6.04 SP1 and later, the Notification Engine supports large queries (queries that take more than 5 minutes to return). The CMDBNOEQRDTimeOut parameter gives the timeout value, in seconds, for the Notification Engine to timeout on a query. | 900 | |
DefaultCell | Sets the CellName for the default HomeCellAlias. This is used by the PROD publish environment of CentralPublish and for the default BMC Atrium CMDB publish environment. | <DefaultCell> | |
DefaultEnvCells | Gives the cells for which pserver creates CellAliases <CellName> -> <CellName> for the default environment | ||
DirectPublishOrigin | Enables (T) or disables (F) direct publishing feed | F (false) | |
DropDuplicateComponentAlias | If enabled, the offending duplicate alias is dropped from the CI that reports the collision. | T (enabled) | |
DropConsumerRelation | If enabled, the CI model will be converted from a circular model to a linear model. In this case, the model appears different than in CMDB or BMC Discovery. | F (false) | |
DropDuplicateRelation | If enabled (T), ignores the duplicate relationship between the same set of provider and consumer CIs and publishes the service model. If disabled (F), publishing fails. For more information about duplicate service models, see Publishing duplicate relationships. | T (enabled) | |
Enterprise | Enables (T) or disables (F) the enterprise mode of operation | F (false) | |
EnterpriseNodes | Limits the enterprise nodes (does not include all Publishing Servers that use the same Atrium CMDB) that are used. An empty value means that all the Publishing Servers that use Atrium CMDB are included. EnterpriseNodes=<pserverName>{,<pserverName>} where <pserverName> is the Publishing Server that you want to include. | ||
EnterpriseCIsSelection | Enterprise CIs are the provider CIs of cross cell impact relationships. If a CI is a provider of 2 CIs selected by the PublishWithProviders filter of 2 different Publishing Servers, then when this CI has the default settings of HomeCellAlias (default), it (and its providers) is sent to the two cells. | PublishWithProvidersCIs | |
JNPServers | Defines the host and port of JNP Servers. When the Portal is set up in cluster mode, this value must match the same value in the pclient.conf file. | Localhost:1100 | |
JMSCommWarnReconnectCount | The number of times to retry to establish JMS communication If the trial fails, then an IPS_ERROR event with the message "Unable to establish JMS communications" of severity WARNING is generated. If JMSCommWarnReconnectCount is -1, then retries continue indefinitely. | 30 (reconnect attempts) | |
JMSCommWarnReconnectInterval | The interval (in seconds) between two reconnection attempts | 10 (seconds) | |
JMSCommMajorReconnectCount | The number of times to retry to establish JMS communication. If the trial fails, then an IPS_ERROR event with the message "Unable to establish JMS communications" of severity MAJOR is generated. If JMSCommMajorReconnectCount is -1, then retries continue indefinitely. | -1 (connection attempts) | |
JMSCommMajorReconnect Interval | The interval (in seconds) between two reconnection attempts | 300 (seconds) | |
CMDBServer | Specifies the name of the computer on which BMC Atrium CMDB resides. This is the same name as the one specified in the ar.conf file. | Not defined, set by install | |
CMDBPort | Defines the port number for connecting to the BMC Atrium CMDB This is the same as the port number specified in the ar.conf file. | Not defined, set by install use 0 for dynamic port detection | |
CMDBUser | Defines the user ID that grants access to the BMC Atrium CMDB | Not defined, set by install | |
CMDBPassword | A valid BMC Atrium CMDB user password appears in plain text when entered; encrypted at first launch | Not defined, set by install | |
ARSGroupMembers | Lists the host and TCP/IP port of every AR Server Group member If an AR Server Group is deployed then you must set this parameter, regardless of whether you use a load balancer. Use 0 for dynamic port detection. | Not defined | |
RequestHistorySize | Sets the maximum number of request log files that are retained by the publishing server | -1 | |
CellConnectionTimeout | Sets the length of time the publishing server maintains a connection to a cell when there is no activity from the cell | 60 (seconds) | |
IMMessageBufferSize | Sets the size of the message buffer for communication with the cell | 2000 | |
IMMessageBufferKeepSent | Sets the time to keep messages buffered while waiting for an answer | 300 (seconds) | |
IMFileDirectoryName | Defines the name of the Impact Manager directory for direct publications; it is looked up in the directory installationDirectory/pw/server/etc/ PSName, or if that file does not exist, in the directory installationDirectory/pw/server/etc This directory file is also used to locate the cell for publishing server event generation. | mcell.dir | |
PasswordLogging | Enables (T) or disables (F) the display of passwords in generated request logs and IPS_REQUEST events | F (false) | |
SMMMessageBufferSize | Sets the size of the message buffer for communication with Service Model Manager | 500 | |
SMMMessageBufferKeepSent | Sets the time to keep messages buffered while waiting for an answer | 300 (seconds) | |
SMMMessageBufferKeepSent Estimate | Enables (T) or disables (F) the use of the estimate when the length of time exceeds the value that is calculated for the upload time of the service model | T (true) | |
ARSNormalTimeOut | Sets the time to stop waiting on a BMC Remedy AR System operation that occurs quickly | 300 (seconds) | |
ARSLongTimeOut | Sets the time to stop waiting on a BMC Remedy AR System operation that occurs slowly | 600 (seconds) | |
ARSXLongTimeOut | Sets the time to stop waiting on a BMC Remedy AR System operation that occurs slowly | 1800 | |
ARSXLongTimeOutEstimate | Enables (T) or disables (F) the use of the estimate when the length of time exceeds the value that is calculated for committing bulk entry transactions | T (true) | |
AutomatedCancelAckTimeout | When automated publishing is stopped, an ongoing publish is canceled, if possible. This parameter sets the length of time for an ack reply of the publishing request, which returns the requestID. If the requestID is unknown, then the publish request is not canceled. | 5 (seconds) | |
AutomatedCancelScsFlrTimeout | When automated publishing is stopped, an ongoing publish is canceled, if possible. This parameter sets the length of time for the final reply of the publish request, which returns a message indicating whether the publish request was canceled or not. If the publish is canceled or if the final reply is unknown, then the publish is retriggered when automated publish is restarted. | 900 (seconds) | |
AutomatedHeartbeatInterval | Sets the length of time between the publishing server and the AR Notify plug-in for heartbeat. 0 or a negative value disables heartbeat. | 60 (seconds) | |
AutomatedHeartbeatTimeout | Sets the length of time that the publishing server waits for an answer to a heartbeat from the AR Notify plugin. | 5 (seconds) | |
AutomatedPublishRetryCount | The maximum number of times automated publishing is retried after failures. n represents the number of repeated publication attempts:
Publications that are skipped are not counted as retry attempts, so AutomatedPublishRetryCount is the effective maximum number of retries. | 12 | |
AutomatedPublishRetryPeriod | Sets the length of time between two consecutive publish requests when publish fails If a previous publish request is not terminated when the interval times out, the next trial is skipped. | 300 seconds | |
AutomatedStartMode | The publishing mode when the publishing server starts or restarts When the publishing server is running, you can change the publishing mode by using requests (by using the CLI command pscontrol ). By default, the publishing server starts in automated mode. | Automated | |
IPSEventsIM | Defines the cell to which publishing server events are sent | Not defined, set by install to Product Short cell | |
IPSEventClasses | Defines the event classes for which publishing server events are created | All subclassess of IPS_EVENT | |
MultiTenancyMode | Set one of the following modes to retrieve the tenants:
| CLM | |
Haenable | Enables high availability configuration on the active and standby nodes. | This parameter should be set to true in pserver.conf if TrueSight Infrastructure Management is running in HA mode for both active and standby nodes. | |
NumberOfNotes | The Publishing server restricts the number of notes being added to 10 by default. You can increase or decrease it. Ensure that the value of the NumberOfNotes parameter multiplied by the value of the NotesLength parameter does not exceed 10000 characters. If this value exceeds 10000, the number of notes reverts back to the default value 10. Restart the Publishing server for this parameter to take effect. | 10 | |
NotesLength | The Publishing server restricts the length of the notes to 1000 characters. You can increase or decrease it. Ensure that the value of the NumberOfNotes parameter multiplied by the value of the NotesLength parameter does not exceed 10000 characters. If this value exceeds 10000, the length of the notes reverts back to the default value 1000. Restart the Publishing server for this parameter to take effect. | 1000 |