penv
Use the penv
command to create and manage publishing environments when the source of the service model data is either the BMC Atrium CMDB (Atrium Publish) or the CLI pposter
(Direct Publish). For more information about publish environments, see Understanding publishing environments and Publishing from a Direct Publish source.
You can secure publish environments by applying a password. See Securing publishing environments.
penv syntax
penv (close | init | open | set) <common options> [-f] [-e <EnvID>] [-s <description>]
penv action commands: open, init, close, set, info
penv
provides additional functionality with these action commands: close
, info
, init
, open
, and set
. Some action commands work differently or have different requirements, depending on the type of environment, Atrium Publish or Direct Publish, as described in the following table.
Actions commands
Action command | General description | Specific to BMC Atrium CMDB environments | Specific to direct publish environments |
---|---|---|---|
| Removes data related to the specified environment. Note: BMC recommends you to backup or get information of all the custom publication filters before running this command. Running this command deletes all the user-created custom publication filters and published data from the environment and all the cells are re-initialized. After restarting pserver, the custom filters need to be recreated from the information stored previously and the published data can be retrieved by running the publish command. For more information, see publish. See example. | If | |
| Displays information relevant to environments
| All parameters are valid except Cell Aliases. | Relevant parameters are |
| Resets the notification error (NOE) subscriptions. | Not applicable | |
| Creates the asset of the specified environment and stores environment settings in the cell. | Also stores the settings for the environment in the BMC Atrium CMDB | Data is stored only in the cell (and the source file); there is no secondary data store. |
| Sets or resets the parameters of the publish environment | You can reset only the | You can reset only the |
penv command options
The following table lists the options for penv
.
penv options
Option | Description |
---|---|
| |
| The pair of opening and closing brackets are allowed but not mandatory.
|
| Sets a unique identifier for the environment |
| Forces the command execution without prompting the user to confirm the initialization action. |
| Describe request |
Atrium Publish environments-valid parameters for each action command
The following table provides a brief description of the parameters in the pclient.conf configuration file for an Atrium Publish environment and specifies the parameters that are valid for each penv
action command: close
, info
, init
, open
, and set
.
For a complete list of parameters in the pclient.conf file and additional parameter information, see pclient.conf file and parameters.
Valid parameters for a BMC Atrium CMDB publish environment
Parameter name | Description | close | info | init | open | set |
---|---|---|---|---|---|---|
AssetDataSetId | Defines the asset dataset ID; default is BMC.ASSET.EnvId | yes | ||||
AssetDataSetType | Defines the asset dataset type as Regular or Overlay; default is Overlay | yes | ||||
AssetUnderlyingDataSetId | Defines the underlying dataset for an overlay asset dataset; default is BMC.ASSET | yes | ||||
AutomatedPublish | Enables (T) or disables (F) automated publication for the publish environment; default is T, except for overlay publish environments | yes | ||||
CellAliases | Defines cellalias-to-cellname pairs that are unique to a given environment | yes | yes | |||
CloseAliases | Enables (T) or disables (F) the removal of aliases of an environment; this releases the cells for use in another environment | yes | ||||
CloseAsset | Enables (T) or disables (F) the removal of the asset dataset along with all objects in the dataset | yes | ||||
CloseCells | Enables (T) or disables (F) the removal of all data instances (including management data) of the service model from the cells | yes | ||||
EnvDesc | Describes the environment | yes | ||||
EnvName | Specifies the name of the environment | yes | ||||
HomeCell | Specifies to which cell to publish. If | yes | yes | |||
Format | Defines the information displayed with info | yes | ||||
InitMgmtData | Specifies whether management data is initialized, T (true) or F (false) | yes | ||||
InitServiceModel | Specifies whether the service model is initialized, T (true) or F (false) | yes | ||||
Level | Determines the amount of information displayed by the info action command | yes | ||||
NewPassword1 | Specifies a new password | yes | yes | |||
NewPassword2 | Confirms a new password | yes | yes | |||
OriginId | Defines the source of the service model data | yes | yes | yes | ||
Password | Specifies a password for authentication | yes | yes | yes | yes | |
PublishModeMgmtData | Defines whether management data must be approached as overlay or as regular dataset | yes | ||||
PublishModeServiceModel | Defines whether components and impact relationships must be approached as overlay or as regular dataset | yes | ||||
SourceBarocMgmtData | Causes the import of initial management data from instances in the .baroc files pointed to in the .load file | yes | ||||
SourceBarocServiceModel | Causes the import of initial service model data from instances in the .baroc files pointed to in the .load file | yes | ||||
SourceEnvMgmtData | Causes initial management data to be imported from instances of the source environment EnvId | yes | ||||
SourceEnvServiceModel | Causes initial service model data to be imported from instances in the asset dataset in the source environment EnvId. Data is created in the asset dataset of the environment. | yes |
Direct Publish environments-valid parameters for each action command
The following table provides a brief description of the valid parameters in the pclient.conf configuration file for a Direct Publish environment and specifies the parameters that are valid for each penv
action command: close
, info
, init
, open
, and set
.
For a complete list of parameters in the pclient.conf file and additional parameter information, see pclient.conf file and parameters.
Valid parameters for a Direct Publish environment
Parameter name | Description | close | info | init | open | set |
---|---|---|---|---|---|---|
CellAliases | Defines cell alias and cell name pairs that are unique in an given environment | yes | yes | |||
Cells | Defines cell names when cell aliases are not used | yes | ||||
Format | Defines the information displayed with info | yes | ||||
HomeCell | Specifies to which cell to publish. If HomeCell is set, the whole service model is published to the specified cell. In this case, cell aliases are not used. | yes | yes | |||
Level | Determines the amount of information displayed by the info action command | yes | ||||
NewPassword1 | Specifies a new password | yes | yes | |||
NewPassword2 | Confirms a new password | yes | yes | |||
OriginId | Defines the source of the service model data | yes | yes | yes | ||
Password | Specifies a password for authentication | yes | yes | yes | yes | |
SIM | Enables (T) or disables (F) the classes that can be published for the Direct Publish environments only | yes |
penv examples
This section contains examples of penv info
. Some examples of penv
are as follows:
Example 1-includes cell names and cell aliases, but no column headings
In example 1, Atrium Publish environments are displayed and cell names and cell aliases are displayed because the -p "Level=1"
option is used, but column headings are missing because the -v
option is not used.
Example 2-raw format
Example 2 displays the information in raw format, rather than display format.
Example 3-includes cell aliases and column headings
In Example 3, cell aliases and column
headings are included for an Atrium Publish environment.
Example 4-Direct Publish environment with cell aliases
The following example is for a Direct Publish publish environment. Cell names and cell alias are displayed because of the -p "Level=1"
option, and column headings are displayed because the -v
option is used.
Example 5-Shows the impact of running the penv close
command in the specified environment
penv close -e <Specific environment name>
For instance, if the Specific environment name is specified as PROD, the following output is displayed:
BMC Impact Publishing Server Environment Manager vX.X.XX (Build 241435256 - 29-May-yyyy)
Copyright 2005-yyyy BMC Software, Inc. as an unpublished work. All rights reserved.
Please confirm command (type y (yes) / n (no). Default is n): y
Request received and accepted by the Publishing Server with id Z00000kbj2af4zXpa1ZyjMZgkkt1b
Request successfully applied
Comments
Log in or register to comment.