pposter

Use the pposter command to send service model objects (components, relationships, and service impact management data) to a cell for Direct Publish environments only by using BMC Impact Publishing Server.

The main difference between pposter and mposter is that pposter communicates with BMC Publishing Server and uses an environment identifier (EnvId) to refer to a specific service model and enables the deletion of service model objects. For information about mposter, see mposter-and-msend.

To use the pposter command, you must set the parameter DirectPublishOrigin to T in pserver.conf and create a Direct Publish environment with the penv command. For example, at the command prompt, type:

penv -eEnvId-p "OriginId=DirectPublish" open -p "HomeCell=*cellName"

For more information about creating environments and the penv command, see penv.

pposter syntax

pposter command options

The following table lists the options for pposter.

You must specify a environment ID and a source file for pposter.

pposter options

pposter uses the following parameter in the installationDirectory /pw/server/etc/pclient.conf file:

If ContinueOnFailure is set to F, false (default), pposter stops as soon as invalid data in the source file is encountered and no data is sent to the cell, not even items processed before the incorrect data in the source file.

Source files for pposter

You can create a source file and, using the following commands, define the contents in BAROC format with the appropriate data additions, modifications, or deletions.

For each data instance, provide a value for mc_udid. You can publish new data instances without specifying a value for mc_udid, but the mc_udid attribute is still needed to modify or delete the existing data in the cell, except if all existing data is replaced when publishing.

For environments that do not have a value for the HomeCell slot, you must provide a value for the HomeCell slot for each component, and a value for the provider_home_cell and the consumer_home_cell slots for each relationship. A relationship is sent to the cell of its consumer component.

For relationships in which the consumer and provider components belong to different cells, you must specify a value for the provider_classname slot. See pposter example 2-two cells.

You can also use cell aliases by specifying values for HomeCellAlias for components, and Consumer.HomeCellAlias and Provider.HomeCellAlias for relationships. Because these slots do not exist in the class definition of the cell, BMC Impact Publishing Server uses the alias table of the environment and replaces them with the values in the HomeCell, consumer_home_cell, and provider_home_cell slots. See pposter example 3-using cell aliases.

Data instances, possibly prepended with dnew (+ or -), dmodify, or ddelete commands, must terminate with END, followed by a Return.

pposter example 1

This example shows how to create, modify, and delete a simple service model.

The service model consists of three objects: an application (comp0), a database (comp1) that application depends on, and the relationship between the two. The environment is MY_ENV and the HomeCell is MY_HOMECELL.

Creating a service model

To create this service model, create a source file. For this example, the source file is named as FileDnew.baroc:

To send this new service model to the cell, at the command prompt, type the following command:

Modifying a service model

To modify the service model by adding impact costs, create a source file. For this example, the source file is named as FileDModify.baroc:

To send this modification to the service model to the cell, at the command prompt, type the following command:

Deleting a service model

To delete the service model, create a source file. For this example, the source file is named as FileDdelete.baroc:

To send this deletion of the service model to the cell, at the command prompt, type the following command:

pposter example 2-two cells

This service model consists of three objects: an application (comp0) that belongs in cell_1, a database (comp1) that belongs in cell_2, and the relationship between the two.

Creating a service model for two cells

To create this service model, create a source file. For this example, source file is named as FileDnew.baroc:

To send this new service model to the cells, at the command prompt, type the following command:

Modifying a service model for two cells

To modify the service model by adding impact costs, create a source file. For this example, the source is named as FileDModify.baroc:

To send this modification to the service model to the cells, at the command prompt, type the following command:

Deleting a service model

To delete the service model, create a source file. For this example, the source file is named as FileDdelete.baroc:

To send this deletion of the service model to the cell, at the command prompt, type the following command:

pposter example 3-using cell aliases

This service model consists of three objects: an application (comp0) that belongs in cell_1, a database (comp1) that belongs in cell_2, and the relationship between the two. For this example, cell aliases are as follows:

Creating a service model with cell aliases

To create this service model, create a source file. For this example, the source file is named as FileDnew.baroc:

To send this new service model to the cells, at the command prompt, type the following command:

Modifying a service model with cell aliases

To modify the service model by adding impact costs, create a source file. For this example, the source file is named as FileDModify.baroc:

To send this modification to the service model to the cell, at the command prompt, type the following command:

Deleting a service model with cell aliases

To delete the service model, create a source file. For this example, the source file is named as FileDdelete.baroc:

To send this deletion of the service model to the cell, at the command prompt, type the following command:

Return codes for pposter

The following table describes the return codes specific to the pposter command. For return (or error exit) codes common to all BMC Impact Publishing Server CLI commands, see Return-codes-for-Publishing-Server-CLIs.

pposter return codes