—

VSM KM Synch to Cell with TSIM

or BPPM via Direct Publishing

(PPOSTER) v2.0

Karlis Peterson WW Architect Team

May 6, 2015

… with Simple Service Modeling support and more

Bring IT to Life.

This presentation covers how to synch discovered CIs and Relationships from VSM KM to the TSIM or BPPM

Service Cell using Direct Publishing.

*This is for BPPM/TSIM Sybase DB only Deployments

The Goal of this Integration

Quickly build

Application Models

Downstream Correlation Use Cases

Data Flow

Enrich meta data

Housekeeping – force lowecase, REGEX FQDN

Virtual Resources

Host (ESXi) vCluster VM Relationships

MACAddress (*for EdgeSwitch connectivity)

Different Icons for Host and VMs

ETL cab be Scheduled and/or Event Driven

Simple Service Model support

Edge Switch Connectivity (Entuity)

Accelerate Value Realization

Step 1 – Enable Direct Publish Publishing

Step 2 – Create Publishing Environment on BPPM Server penv open -e VSM -p “OriginId=DirectPublish” -p “HomeCell= cellName”

Step 3 – Extract and Configure Pentaho CE for ETL automation

Step 4 – Run ETL

Step 5 – *Optional – Simple Service Models

Step 6 – *Optional – Edge Switch Connectivity (Entuity)

Step 1 By default, Direct Publish publishing is enabled. Direct Publish is controlled in the pserver.conf file, located ininstallationDirectory/pw/server/etc, by the parameter DirectPublishOrigin = T. (Default = T) For Direct Publish environments, the Publishing Server looks up the cell information from a cell directory file. You can set this file in pserver.conf with the parameter IMFileDirectoryName. It defaults to mcell.dir, so cells and BMC ProactiveNet Publishing Server share the file.

Step 1 - Continued

Step 2 Make sure that publishing is running. If not, run the following command: pserver –b ps_pncell_<hostname> When all the BMC ProactiveNet data for the environment goes to one single cell, you can define the cell with the parameter HomeCell. Create a Direct Publish environment and define HomeCell by running the following command: penv open -e EnvId -p “OriginId=DirectPublish” –p “HomeCell=cellName” where EnvId represents the name of the environment you are creating. CellName represents the name of the cell to which you are sending objects.

Step 2 - Continued Example: penv open -e VSM -p "OriginId=DirectPublish" –p "HomeCell=pncell_mgmt"

Validation of env: penv -e VSM info

Step 3 - Choose a server to run ETL (BPPM server or any remote server)

- Ensure a JRE is installed locally on that server (no specific version)

- Download latest version of Pentaho Communities Edition from SourceForge and extract:

http://sourceforge.net/projects/pentaho/files/Data%20Integration/

- Extract VSM integration archive or ZIP

- Configure Steps (minimal configuration)

- Save Transformations/Job

- Change icons by copying and replacing the component_icon.properties file from integration to pw\pronto\conf\ and pw\pronto\data\Image\Icon\ directories.

Step 4

Step 4

Step 5 *Optional – Simple Service Model (XLSX)

Step 6 *Optional - Reasoning Entuity Topology

Step 6 *Optional - Reasoning Entuity Topology

FAQs 1. What is the ETL engine? Do I need to purchase any additional software? Pentaho Data Integration Communities Edition is free of charge and is used as the ETL engine to extract, transform and load data. Download PDI from Sourceforge: http://sourceforge.net/projects/pentaho/files/Data%20Integration/

2. How does the ETL connect to BPPM? The input step for Inventory and Relationships will connect to the BPPM/TSIM database tables using JDBC. You will need to use a user such as dba (or a user with rights to read tables) for the ETL to connect. See the Appendix for details.

3. How does the ETL handle changes (deltas)? The Relationships transformation will delete all the existing VSM relationships in BPPM and then rebuild every run. The ETL is very fast so there is no issue with rebuilding relationships every time the ETL is run (scheduled on a daily basis).

4. How do I delete a device with Direct Publishing? Since the ETL does not remove devices, you just need the mc_udid of the device and create a baroc file. See Appendix on details. More info on pposter from BMC Docs: https://docs.bmc.com/docs/display/public/proactivenet96/pposter

5. How do I remove all CIs and Relationships from the integrations? If you want to reset or remove all CIs from then run munpublish from the BPPM server: munpublish -n <cell> "DirectPublish.VSM"

Appendix – ETL Job

Minimal Configuration – just put in Parameter information at Job Level.

Appendix – *Optional – Edge Switch to Host

Pre-Req: For customers who have Entuity, first you must configure the Entuity Device Synchronization found here https://communities.bmc.com/docs/DOC-35933

Appendix – *Optional – vSwitch to Virtual Machine

By default only Edge Switch to Hypervisor relationships are created. If you would like vSwitch (e.g. nexus100v) to Virtual Guests, then configure the following: 1. Edit step 3 on the Job (“VSM_Entuity_MAC_to_EdgeSwitch_Relationships.kjb”

2. Remove AND Item: equals Server from the script.

Appendix – Schedule ETL

Here is a sample Windows batch script that can be scheduled through Windows Scheduler. If you run on Linux, then create a similar script and leverage CRON or other.

@ECHO OFF C:\<pentaho_dir>\data-integration\kitchen.bat /file:C:\<location_of_ETL>\VSM_Device_Synch_with_TrueSight.kjb exit

@ECHO OFF C:\<pentaho_dir>\data-integration\kitchen.bat /file:C:\<location_of_ETL>\ VSM_Entuity_MAC_to_EdgeSwitch_Relationships.kjb exit

For the Optional ETL for linking Edge Switch to Host:

Appendix – BAROC Sample Output

BMC_ComputerSystem;mc_udid='tsom.deaee417-ec36-11e4-8589-5362aeaada3c';HostName='as';Domain='localdomain';Category='Hardware';Type='Processing unit';Item='Virtual Server';PrimaryCapability='Not Dedicated';ShortDescription='as';Name='as';Description='as.localdomain - Red Hat Enterprise Linux 5 (64-bit) ';InstanceId='1360';ComponentAliases=[BMC_ComputerSystem:VI-UUID:42006f3f-1dd2-aa5c-1087-1fdd3347251d];END BMC_ComputerSystem;mc_udid='tsom.deabfdbd-ec36-11e4-8589-5362aeaada3c';HostName='clm-esx2';Domain=' ';Category='Hardware';Type='Processing unit';Item='Virtual Server';PrimaryCapability='Not Dedicated';ShortDescription='clm-esx2';Name='clm-esx2';Description='clm-esx2 - Other Linux (64-bit) 5.0.0';InstanceId='13';ComponentAliases=[BMC_ComputerSystem:VI-UUID:564df3f9-ed1e-32d2-361b-5d26e13de990,BMC_ComputerSystem:clm-esx2:,BMC_ComputerSystem:clm-esx2:bmc.local,BMC_ComputerSystem:clm-esxi2:,BMC_ComputerSystem:clm-esxi2:bmc.local];END

…

Sample BAROC format:

Appendix – Reset the Direct Publishing

munpublish -n <cell> "DirectPublish.VSM"

To delete all CIs in the Direct Publishing environment

Appendix – Deleting specific CIs

mquery -n <cell> -d -a BMC_ComputerSystem -w "publish_env_id: equals DirectPublish.VSM" -s “Hostname,mc_udid,InstanceID" -q -f BAROC > c:\Data\ddelete.baroc

To delete a specific CI, you will need the mc_udid in the following format (baroc). First mquery the cell for BMC_ComputerSystems from Direct Publishing:

Find the instances that you want to delete, and create a baroc format file such as this one named ddelete.baroc: ddelete BMC_ComputerSystem; mc_udid='pentaho.072eb8e1-009f-11e4-96d1-09a1c04cb6e4'; END ddelete BMC_ComputerSystem; mc_udid='pentaho.072f0702-009f-11e4-96d1-09a1c04cb6e4'; END

Then run the following: pposter -v -e VSM c:\Data\ddelete.baroc

© copyright 2014 BMC Software, Inc.

—

Bring IT to Life.™

Thank You