Kick Off

September 26, 2016

Agenda

2

OBR Content Development Workshop

Overview

Community Content

Operations Bridge on ITOM Insiders

Technical Presentation & Demo

Q&A

hpe.com/software/obr

Workshop Overview

3

Free Community Workshop: Content Development for OBR

4

Get the skills, resources, and support

Explore and build OBR Content Packs

Access to R&D experts in webinars and forum

Submit content to the community

Get highlighted in the OpsBridge Blog

Earn points on „ITOM Insiders“ along the way

For HPE and HPE Channel Partner Internal Use

DevelopLearn Submit

The Process

5For HPE and HPE Channel Partner Internal Use

Registration

• Submit form• Receive details• Setup OBR

Live Kickoff Webinar

• Intro & Overview• Presentation:

Content Designer Overview

Live Webinar II

• Presentation:CDE Advanced &Report Customizations

• Q&A / Validate your approach

Live Webinar III

• Progress• Wrap Up• Takeaways• Q&A

Coding OBR & Learning Week Support from the Experts (Forum)Required for participation

Earn points by completing related challenges on the ITOM Insiders platform

Submit your OBR Content

• Submit your content to the HPE Live Network

Community Content on the HPE Live Network

6For HPE and HPE Channel Partner Internal Use

login to HPE Live Network

select your product (OBR)

creating community

content is an easy task

involving few clicks only

any HP Passport will work

Useful Resources for OBR/OpsBridge on the HPE Live Network

7For HPE and HPE Channel Partner Internal Use

Offers exclusive benefits and networking opportunities for customersand partners using HPE IT Operations Management products

How it works

– You choose which activities to participate in Social media, attend webinars, volunteer to be a reference, test drive our products and more

– Earn points for completing activities, pick up badges, and move up in user status as you progress

– Points can be redeemed for items that will benefit you and your organization

We have special challenges for this workshop: Earn points for registration, webinar attendance and content submission.

Not a member yet? Send us an e-mail to receive your invitation.

HPE ITOM Insiders

Help & Resources

9For HPE and HPE Channel Partner Internal Use

R&D Experts will answer your questions Operations Bridge Reporter Practitioners Forum

Meet the experts in another live session on Thursday See your welcome e-mail for the invitation links

Find more content and free resources Operations Bridge Reporter @ HPE Live Network Operations Bridge @ HPE Live Network

General questions about the workshop? Send an e-mail to obr.community.workshop@hpe.com

Watch out for more information via e-mail.

HPE Operations Bridge ReporterContent Designer 10.01 – Webinar #1

September 2016

Agenda

– Content Development Overview

– Flavors of Content Development tools

– Content Designer Overview

– OA as source Content Development – Walkthrough

– Content Designer : Pros and Cons

– Q&A

11

Pre-requisites

– Basic Data warehouse concepts

– Basic Understanding of CDE and Content Packs

– OBR 10.01 setup pre-installed with sample sources

12

OBR Content Designer

13

Generic Collectors (DB, CSV…)

Agent Collector

SiSCollector

Staging area

Business View

Aggregated/transformed data

Raw data

DWH – Vertica

Platform Services

Admin and Monitoring UI

Reporting & Analytics Business Objects

CONTENT

CoreContent Pack

PLATFORM

NNMi/NPS Collector

Collectors

3rd Party ETL (Load / Align)

Met

adat

aD

eplo

y M

gr

MyBSM

OM Collector

BSM / OMiCollector

RtSM Collector

Application CP (Reports)

Domain CP (Schema /

Rollup)

ETL (Load / Align)

Audit / Control Streams

Con

tent

Dev

Env

ironm

ent

OBR Platform Architecture

OBR Content Architecture

Data Warehouse(DWH) MetadataLogical model (Business View)

Physical model (Relations)

Aggregation rules

(Generated) Data Load rules

DW

H

Aud

it &

Con

trol S

tream

sDomain Model Content Pack

Reports, Dashboard, Analytics,…

Extended Universes

Core Universe

Application Content Pack

Data Acquisition & Alignment Metadata

Reconciliation Rules

Mapping Rules

Collection Policies

ETL Content Pack

ETL

Aud

it &

Con

trol S

tream

s

Stage Rules

Logical view/relational model

Stage table

OBR Content Development Environment

– In short CDE !

– Utility/Tool used to develop content packs.

– With minimal input from the content developer creates ETL, Domain and Application content pack.

16

CDE

ETL

DOMAIN

REPORTS

Flavors of CDE

Content Designer

CDE Simplified

CDE Advanced

17

The Content Development Environment (CDE)consists of a set of tools that you use during theprocess of content development.

These tools use XML files authored by the contentpack developer to generate the installable contentpack component packages.

A simplified method of creating a content pack can beused in the following cases:

• When a fact table is associated with one ormore dimensions (star schema) and thedimensions are not further normalized(dimensions without a parent table).

• When facts are to be reconciled against host(when HP Operations agent is the datasource).

• When the generated reports do not require anyroll up or drill down of data.

Identify your reporting use case with details

Study the domain of interest

Understand sources of data

Choose suitable flavor of CDE and proceed towards OBR content building

Pre-requisites for Any Content Creation

18

Content Designer OverviewA simplified way to create content

19

Content Designer – An Introduction

• Interactive User Interface

• Content Development is Simpler

• Create End to End Content pack (ETL ,Domain, Application)

• Simplified Platform for Simple Use Cases

• .csv files, Databases and Operations Agent as data source types for content creation

20

Content Designer – Points to note before you get started

– The Content Designer tool enables you to build a full –fledged OBR content pack– The ETL, Domain and Application content pack

components are built during content build.– The designer does NOT currently support creation of a

content extension/silo’ed component as yet (eg. only ETL extension for existing domain content)

– Supports Star Schema based model creation

– Suited for ‘simple’ schema use cases wherein source schema is similar to the reporting schema in OBR (e.gno pivot transformations/extensive source join queries/merge across sources etc.)

21

.csv files– Expected name Format of

.csv file to align with that supported via OBR Collectors *<Category>_0_<Type>_0_*.csv : “RetailPos_0_Sales_0_123.csv”

– Data in CSV : Expected to be in form of Header/Value (1 row of well-qualified values should suffice – the tool attempts to interpret as much info from type of data samples represented in the .csv (eg. data types like DATETIME et al.)

22

Databases• Currently supports

Oracle, Sybase, PostgreSQL etc. database types

• Congenial for use cases wherein source schema reflects reporting schema being developed in OBR

Operations Agent based sources

• Supported ONLY in integration with an RtSM (OMi or BSM)

• All fact data (metric data sets) would be reconciled against Node CI types• Every fact table created

using OpsAgent as source would have foreign key reference to K_CI_Systemdimension of OOTB CoreSystemPerformance OBR Content pack .

Content Designer – More Facts you need to be aware of …Supported data source types

Download, Install, Deploy …

Install the .msi/.rpm files on Windows/RHEL systems as per instructions detailed in OBR Content Designer Help.

Open command prompt & go to <CDE Extracted folder>/cdeConsole and execute the following commands:deploy.batstart.batLog on to Content Designer via any supported browser:http://<hostname>:3000

23

Download CDE 10.01.000 from https://hpln.hpe.com/contentoffering/hpe-obr-content-development-environment

For the workshop, it is also available @ ftp://ftp.ext.hpe.com/HPE-OBR-CDE/

Content Designer Deep-diveStep by Step process for creating content for Operations Agent based data sources

24

Content Designer : Settings Page

25

Content Designer– Enabling content build

26

Step 1 : Select the data source type against which you want to develop reporting content

Content Designer : Provide inputs to ‘auto-discover’ content elements

27

Step 2: Provide an instance of an agent based data source and an RtSM node (OMi/BSM) as input

Content Designer : Define/qualify content elements

28

Step 2 Details:Content pack name represents any logical well-qualified name representing the model you are trying to build

Content Designer : Define/qualify content elementsSelect Agent Datasource and Class

• Both Dimension and Fact should be selected for each unique Datasource/Class combination

• Upon deploying the generated content in OBR, Dimension & Fact tables would be created for each such combination

29

Step 2 Details:Picking dimension and fact entities from source

Content Designer : Define/qualify content elements Logical view of dimensions

Essentially, this step enables creation of dimension tables and fact tables in OBR schema based on these selections/mappings

30

Step 2 Details:A re-cap of the prior selection …

Content Designer : Define/qualify content elements Define Dimensions

• Select the business key column – these are column(s) that uniquely identify a row/instance of the dimension against which facts(metrics) are logged.

• Dimensions represent relatively static entities –therefore, select such properties (predominantly string data types) as dimension columns; AVOID selecting time-variant metrics (eg. uptime, utilization etc.) when you map dimension columns 31

Step 2 Details:Getting to know the dimension definition …

Content Designer : Define/qualify content elements Define Dimensions [Contd.]

32

Step 2 Details:Another example …

Content Designer : Define/qualify content elements Logical View of CDE-generated Dimension table

33

This is an example of how the “generated” OBR schema would translate to – based on sample inputs that had been selected…

Step 2 Details:Logical view of CDE generated dimensions…

Content Designer : Define/qualify content elements Define Facts

• Facts represent time-variant entities(collection of measures/metrics)

• Do not select non numeric columns as part of fact attributes except perhaps the business key column.

• Do not re-select AgentTimeStamp column as part of fact selection.

• Select the respective dimension class (ONLY !) as associated dimension.

34

Step 2 Details:Defining facts …

Content Designer : Define/qualify content elements Define Facts [Contd.]

• Choose required functions for aggregation (default.: min/max/avg)

• Ensure that you do not select Business key columns while selecting metrics for aggregation

• Do not change the default mapping of Business key column which appears in UI.

35

Step 2 Details:Defining facts – do’s and don’ts

Content Designer : Define/qualify content elements Logical view of Facts

36

Step 2 Details:Logical view of the example facts used …

Content Designer : Define/qualify content elements Fact to dimension association

37

Step 2 Details:Logical view of the sample schema generated

Content Designer : Define/qualify content elements Fact to dimension association

38

Step 2 Details:Another example …

Content Designer : Define/qualify content elements Select custom RtSM view and CI types

• Dimension collection will happen from the selected view(s) for the selected CI Type(s)

• Ensure you select nt/unixCI types from RTSM view which would drive collection of node data

• The nodes synch’d as part of nt/unix instances will be loaded to K_CI_Systemtable in System Performance content pack

39

Step 2 Details:Relevance and significance of choice of RtSM views and CI types …

Content Designer : Define/qualify content elements Select custom RtSM view and CI types – an illustration

40

Step 2 Details:Relevance and significance of choice of RtSM views and CI types …an illustration…

Content Designer : Define/qualify content elements Mapping Global dimension

• Map a Datasource/Class which had been selected for Agents Fact collection to the CI type.

• This Dimension table created for this Datasource/Class would be treated as global dimension table

41

Content Designer : Define/qualify content elements About the Fact-global dimension association

42

Content Designer : Define/qualify content elements Multiple associated dimensions …

43

Content Designer : Define/qualify content elements Fact to multiple dimensions (global + local)

44

Content Designer : Review your selections

45

Step 3: Review your choices before proceeding towards content build …

Content Designer : Review your selections

• Choose the option of where to create .unx

- on local System - or Publish directly in Bobj

repository

46

Step 3: Review your choices before proceeding towards content build …

Content Designer : Build status

• Step by Step CDE would execute and create ETL, Domain and Application content pack components

• Content Developer has to view logs for any error or build is successful

• On successful build, content packs would be available under CDE workspace

47

Generated Artifacts

– The folders for the content pack components(Domain, ETL, and Report) are created in theCDE workspace.

– The newly-created directory structure containsall the required source artifacts that have beengenerated by the tool.

– Model Mapper CSV file is generated andavailable in the output location. A ModelMapper CSV file is an intermediate documentbefore generating the end-to-end content packfor Domain and ETL containing the metadatainformation user have selected in the CDE UI.

– Name of the file will be <CSV policy's nameattribute>_MappingFile_<timestamp>.CSV.The content developer has the option to editthe required column names in the CSV file ifneed be and re-run the CDE build viacommand line.

48

Generated Artifacts(cont.)

49

– UNX files that can be opened from BObjClient tooI (Information Design Tool).[Note that client tools like IDT have to beinstalled separately on a Windows systemas detailed in the product manuals.]

– Option to either export generated universedirectly to repository OR to local folder(incase universe edits are further planned)

– In the case of latter, create sample projectin IDT and perform the steps detailedfurther …

Generated Artifacts(cont.): Information Design Tool

50

– Project Name :- The name which youwant to give typically the CP Name.

– Project Location :- Browse to Universe connection folder in the content pack.

– e.g.: {CDE_HOME}\RetailPOS\RetailPOS.ap\UnxFolder\UnxLayers

Generated Artifacts(cont.): Information Design Tool

51

– After selecting the folder, we can see the contents of thefolder listed under the project name that we gave in theprevious slide.

– Double click on ApplicationRetailPOS.cnx so that it willopen on the right side panel,

– Verify the database connection details and click on Edit,click on Next, change Array Fetch Size to 5 instead of 10and finish.

– Do test connection and save

– Right click on ApplicationRetailPOS.cnx and publish theconnection to repository “Common Connections” folderand click Finish, this step asks for shortcut of connectionto project. Click on Yes.

– Now we will observe one more connection calledOBR_CONNECTION.cns

– Delete the connection ApplicationRetailPOS.cnx andopen ApplicationRetailPOS.dfx. And change theconnection to OBR_CONNECTION

– Right click on ApplicationRetailPOS.blx and publish torepository.

Create Report on BI Launch Pad

52

– Open Bi Launchpad http://<servername>:8080/BOE/BI

– Select the generated universe and create a sample report.

Deploy content Verify content Reports: Build & package

•Navigate to CDE workspace•Copy the generated content packages to {PMDB_HOME}/packages•Install Domain and ETL content pack to start with, using Deployment Manager UI in OBR Admin console

•Configure required data sources in OBR Admin console•Verify the data flow

NOTE: Edits on content can be done using CDE Advanced/artifacts in workspace.

•Login into BI Launch Pad and start creating Reports as per use cases

•It is recommended that you as well package the reports within the Application content pack, steps for which are detailed in the product manuals.

HPE Template How-To-Guide 53

Content Dev : Next Steps …

In Summary…Content Development Steps using CDE UI

Select Data Source

Define inputs and mappings

Review the selection

Content Pack components

generated

54

Logging & Troubleshooting

– To view Help Files, go to CDE.zip extracted folder. Go to cdeConsole\public\help and double click onDefault.htm.

– Content Pack Creation logs can be located at {CDE_HOME}\log\cde.log

– As CDE UI is a web based GUI Tool, it is using NodeJS as the backend server. For NodeJS Server related logs,please refer to {CDE_HOME}\cdeConsole\logs\server.log & {CDE_HOME}\cdeConsole\logs\server_err.log

– If in case, you want to update the generated content pack, you need to do this explicitly and run ant commandseparately for each artifact. For this you need to add BO_HOME in environment variables, with value inquotes(“”).

– The creation of the Application Content Pack might fail with an exception “Tables not found in database”, torectify this exception, ensure that before the creation of Application Content Pack, the Domain Content Pack isinstalled. Business Objects requires that tables referenced in the universe are present in the backend database.

55

Content Designer – Known Limitations

– Snowflake Schema cannot be achieved via Content Designer

– Only ETL, Only Domain and Only Application mode of creation not supported.

– Extension of OOTB content via Content Designer OR two layered content pack(Application(with inherent data model)+ETL) creation are not supported

– Only single user support– In Linux Environments, while generating/updating

universe there is a necessity to have Windows Server separately to install BObj client tools.

56

Are there any means to get past some of these limitations? Universes/Reports ?

57

Are there any means to get past some of these limitations? Universes/Reports ?

Stay tuned for Webinar #2 this Thursday on

CDE Advanced !!!

58

Before we start with Q & A...

59

Complete a challenge!

60

You have registered for this workshop,but you have not earned the points?

Complete the challenge on ITOM Insidersto get your points:

https://itominsiders.influitive.com/?&id=1670

Not a member yet?Send us an e-mail to receive your invitation.

...or two?

61

You have attended this session?

Now get another 100 points on ITOM Insiders:

https://itominsiders.influitive.com/challenges/1692

Not a member yet?Send us an e-mail to receive your invitation.

Questions?

62

Thank youhttps://hpln.hpe.com/product/operations-bridge-reporter

63