Examples of advanced environments


The penv command allows for staging scenarios mentioned in the following examples:

Example 1–Creating two service models for two departments

This approach is best suited for testing large service models where the effort to automate the tasks by script is acceptable in terms of the volume of data being tested.

At the beginning of a BSM project, you want to test two separate service models for two different departments.

  1. You can define two environments for the two different departments, by running the following command:

    Information
    Example

    >penv open -e dept1 >penv open -e dept2

  2. The components and impact relationships for each department are loaded from BAROC files, in the respective asset datasets BMC.ASSET.dept1 and BMC.ASSET.dept2.
     After an initial publication, modifications are published incrementally. When you are satisfied with the results, the staging asset datasets can be reconciled with the production dataset.
  3. Reconcile with the staging asset datasets into the production dataset.

Example 2–Publishing a single service model to multiple environments

Additionally, it is possible to publish a single service model (the data in an asset dataset) to multiple BMC ProactiveNet environments. For example, you can send the service model to production cells (for real-life monitoring and impact analysis) and send the same service model data to a test cell to experiment with the impact of component failure.

For the simulation publishing environment, the HomeCell parameter of the publishing environment is defined.

Both the production publishing environment and the simulation publishing environment use the production asset dataset BMC.ASSET. The last successful publication of the simulation publishing environment SIMULATION is saved in the PN:PublishedData form. A reconciliation merge to the BMC.ASSET dataset triggers an automated publish on both environments.

Alternatively, if you want to perform simulations on a service model that is derived from the production service model, then your simulation publishing environment would use an overlay asset dataset BMC.ASSET.SIMULATION with underlying dataset BMC.ASSET. Reconciliation merges with the BMC.ASSET dataset will trigger an automated publish (if enabled) on the simulation publishing environment.

To create a simulation publishing environment that uses the production asset dataset, run a command similar to the following command:

Information
Example
penv -e SIMULATION -p "AssetDataSetId=BMC.ASSET" -p "HomeCell=simulation"

This command creates only the simulation publishing environment, not the production publishing environment, which must already exist because it is created by default. 

To create a simulation publishing environment with an overlay asset dataset:

Information
Example
penv -e SIMULATION -p "AssetDataSetType=Overlay" -p "HomeCell=simulation" -p "AutomatedPublish=T"

 

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

BMC ProactiveNet 9.6