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 -e
EnvId
-p "OriginId=DirectPublish" open -p "HomeCell=*
cellName
"
For more information about creating environments and the penv
command, see penv.
pposter <common options> -e EnvId sourceFile {sourceFile}
The following table lists the options for pposter
.
You must specify a environment ID and a source file for pposter
.
pposter options
Option | Description |
---|---|
<common option> -c -h -? -i -q -l -p -r -s -t -u -v -z | |
-e EnvId | Sets the environment identifier to EnvID to specify a service model |
SIM=T/F | If |
Init=T/F | If |
sourceFile | File that contains the data to send |
pposter
uses the following parameter in the installationDirectory /pw/server/etc/pclient.conf file:
ContinueOnFailure=T/F
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.
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.
Command | Definition |
---|---|
| Create a new data instance; if this instance exists, update it. |
| Create a new data instance. |
| Change the existing data instance. |
| Delete the existing data instance. |
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.
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
.
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:
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:
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.
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:
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:
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:
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:
cell alias | cell name |
---|---|
c_alias_1 | cell_1 |
c_alias_2 | cell_2 |
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:
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:
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:
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
Return Code | Description |
---|---|
| All data commands in the source files are successfully applied to all cells of the environment. |
| Publish has successfully completed, but some errors were detected. |
| BMC Impact Publishing Server refused to initiate the publish process. The actual cause of the error (for example, another publish is in progress) is displayed on the standard error device. |
| An error is returned by BMC Impact Publishing Server when data is being sent to it. |
| An error is returned by BMC Impact Publishing Server when data is effectively applied to the cells. |
| The source file contains a syntax or invalid BAROC object. |
| An I/O error is occurred with a source file. For example, no source file or the source file cannot be opened. |
3 Comments
Hutson Meeks
The example penv command on this page (also shown below) fails. Please provide a working example.
penv -e
EnvId
-p "OriginId=DirectPublish" open -p "HomeCell=*
cellName
"
Sithesh V.V
Sithesh V.V