Summary of CLI commands for   BMC Impact Publishing Server

The following table lists all of the available BMC Impact Publishing Server CLI commands and provides a brief description of the purpose for each command.

You can invoke BMC Impact Publishing Server CLI commands from a command prompt on Windows, from a UNIX operating system prompt, or from a script, either locally on the BMC ProactiveNet Server computer or remotely on another computer.

To use the BMC Impact Publishing Server CLI commands remotely, you must copy the CLI installation to the remote host and configure the CLI for remote access. For more information, see Configuring-Publishing-Server-CLI-commands.

BMC ProactiveNet Publishing Server CLI command descriptions

Command

Description

Page

pclassinfo

Compares the service model class definitions on a cell or cells with the class definitions in the BMC Atrium CMDB and lists the differences
You can also use this command to export service model class definitions from the BMC Atrium CMDB.

penv

Enables you to set up advanced environments and staging scenarios

pinit

Initializes or reinitializes cells with service model impact data

plog

Obtains the XML log for a specific service model publishing request and routes it to standard output
Use this command with the plogdisplay command.

plogdisplay

Displays the XML log for a specific service model publishing in text format to standard output

pposter

Sends SIM elements, such as component instances, relationships, and management data to cells by using the BMC Impact Publishing Server

pscontrol

Sends a specific command (automated, manual, stop) to the BMC Impact Publishing Server

pserver

Starts the BMC Impact Publishing Server service or daemon

The major differences between pserver and the other BMC Impact Publishing Server CLI commands are as follows:

  • The exit codes are different.
  • pserver is the BMC Impact Publishing Server itself, while the others are CLI commands that communicate with the server.
  • The configuration files and tracing files are different.
  • Although possible, the process for copying pserver to another computer is different, and performance considerations must be taken into account.
pshowlog

Obtains the XML log for a specific service model publishing request plus the prior publishing request and routes it in readable format to standard output

psstat

Returns the status (starting, started, or stopping) and mode (automated or manual) of the BMC Impact Publishing Server

publish

Publishes service model or displays (-w) the service model objects to be published

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*