content

---

Kick Off

September 26, 2016

Agenda OBR Content Development Workshop

 Overview  Community Content  Operations Bridge on ITOM Insiders  Technical Presentation & Demo  Q&A

hpe.com/software/obr 2

Workshop Overview

3

Free Community Workshop: Content Development for OBR  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

Learn

Develop

Submit

For HPE and HPE Channel Partner Internal Use

4

The Process

Live Kickoff Webinar

Registration • Submit form • Receive details • Setup OBR

• Intro & Overview • Presentation: Content Designer Overview

Required for participation

Live Webinar II • Presentation: CDE Advanced & Report Customizations • Q&A / Validate your approach

Live Webinar III • • • •

Progress Wrap Up Takeaways Q&A

Submit your OBR Content • Submit your content to the HPE Live Network

Coding OBR & Learning Week  Support from the Experts (Forum)

Earn points by completing related challenges on the ITOM Insiders platform

For HPE and HPE Channel Partner Internal Use

5

Community Content on the HPE Live Network

 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 For HPE and HPE Channel Partner Internal Use

6

Useful Resources for OBR/OpsBridge on the HPE Live Network

For HPE and HPE Channel Partner Internal Use

7

HPE ITOM Insiders Offers exclusive benefits and networking opportunities for customers and 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.

Help & Resources 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 [email protected]

Watch out for more information via e-mail. For HPE and HPE Channel Partner Internal Use

9

HPE Operations Bridge Reporter Content 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

OBR Platform Architecture

Metadata

PLATFORM

Deploy Mgr

Content Dev Environment

MyBSM

DWH – Vertica

Reporting & Analytics Business Objects

CONTENT

Business View Audit / Control Streams Aggregated/transformed data Application CP (Reports)

Admin and Monitoring UI

Raw data

Platform Services

Staging area

Core Content Domain CP Pack (Schema / Rollup)

Collectors OM Collector BSM / OMi Collector

Agent Collector

SiS Collector

RtSM Collector

NNMi/NPS Collector

3rd Party Generic Collectors (DB, CSV…)

ETL (Load / Align) ETL (Load / Align)

OBR Content Architecture Logical view/ relation al model

Application Content Pack Reports, Dashboard, Analytics,… Extended Universes Core Universe

DWH

Audit & Control Streams

ETL

Audit & Control Streams

Domain Model Content Pack Data Warehouse(DWH) Metadata Logical model (Business View) Physical model (Relations) Aggregation rules (Generated) Data Load rules

ETL Content Pack

Stage table

Data Acquisition & Alignment Metadata Stage Rules Reconciliation Rules Mapping Rules Collection Policies

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.

ETL

CDE

DOMAI N

REPORT S

16

Flavors of CDE Content Designer

The Content Development Environment (CDE) consists of a set of tools that you use during the process of content development. These tools use XML files authored by the content pack developer to generate the installable content pack component packages.

CDE Simplified

CDE Advanced

A simplified method of creating a content pack can be used in the following cases: • When a fact table is associated with one or more dimensions (star schema) and the dimensions are not further normalized (dimensions without a parent table). • When facts are to be reconciled against host (when HP Operations agent is the data source). • When the generated reports do not require any roll up or drill down of data.

17

Pre-requisites for Any Content Creation

Understand sources of data

Identify your reporting use case with details

Study the domain of interest

Choose suitable flavor of CDE and proceed towards OBR content building

18

Content Designer Overview A 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.g no pivot transformations/extensive source join queries/merge across sources etc.)

21

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

.csv files – Expected name Format of .csv file to align with that supported via OBR Collectors *_0__0 _*.csv : “RetailPos_0_Sales_0_12 3.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.)

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_System dimension of OOTB CoreSystemPerformanc e OBR Content pack .

22

Download, Install, Deploy …

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/

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

Open command prompt & go to /cdeConsole and execute the following commands: deploy.bat start.bat Log on to Content Designer via any supported browser: http://:3000

23

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

24

Content Designer : Settings Page

25

Content Designer– Enabling content build Step 1 : Select the data source type against which you want to develop reporting content

26

Content Designer : Provide inputs to ‘auto-discover’ content elements 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

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

28

Content Designer : Define/qualify content elements Select Agent Datasource and Class Step 2 Details: Picking dimension and fact entities from source

• 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

Content Designer : Define/qualify content elements Logical view of dimensions Step 2 Details: A re-cap of the prior selection …

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

30

Content Designer : Define/qualify content elements Define Dimensions Step 2 Details: Getting to know the dimension definition … • 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 timevariant metrics (eg. uptime, utilization etc.) when you map dimension columns 31

Content Designer : Define/qualify content elements Define Dimensions [Contd.] Step 2 Details: Another example …

32

Content Designer : Define/qualify content elements Logical View of CDE-generated Dimension table Step 2 Details: Logical view of CDE generated dimensions…

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

33

Content Designer : Define/qualify content elements Define Facts Step 2 Details: Defining 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

Content Designer : Define/qualify content elements Define Facts [Contd.] Step 2 Details: Defining facts – do’s and don’ts • 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

Content Designer : Define/qualify content elements Logical view of Facts Step 2 Details: Logical view of the example facts used …

36

Content Designer : Define/qualify content elements Fact to dimension association Step 2 Details: Logical view of the sample schema generated

37

Content Designer : Define/qualify content elements Fact to dimension association Step 2 Details: Another example …

38

Content Designer : Define/qualify content elements Select custom RtSM view and CI types Step 2 Details: Relevance and significance of choice of RtSM views and CI types … • Dimension collection will happen from the selected view(s) for the selected CI Type(s) • Ensure you select nt/unix CI 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_System table in System Performance content pack 39

Content Designer : Define/qualify content elements Select custom RtSM view and CI types – an illustration Step 2 Details: Relevance and significance of choice of RtSM views and CI types …an illustration…

40

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 Step 3: Review your choices before proceeding towards content build …

45

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

• Choose the option of where to create .unx - on local System - or Publish directly in Bobj repository

46

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 the CDE workspace. – The newly-created directory structure contains all the required source artifacts that have been generated by the tool. – Model Mapper CSV file is generated and available in the output location. A Model Mapper CSV file is an intermediate document before generating the end-to-end content pack for Domain and ETL containing the metadata information user have selected in the CDE UI. – Name of the file will be _MappingFile_.CSV. The content developer has the option to edit the required column names in the CSV file if need be and re-run the CDE build via command line.

48

Generated Artifacts(cont.)

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

– Option to either export generated universe directly to repository OR to local folder(in case universe edits are further planned)

– In the case of latter, create sample project in IDT and perform the steps detailed further …

49

Generated Artifacts(cont.): Information Design Tool

– Project Name :- The name which you want 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

50

Generated Artifacts(cont.): Information Design Tool – After selecting the folder, we can see the contents of the folder listed under the project name that we gave in the previous slide. – Double click on ApplicationRetailPOS.cnx so that it will open 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 10 and finish.

– Do test connection and save – Right click on ApplicationRetailPOS.cnx and publish the connection to repository “Common Connections” folder and click Finish, this step asks for shortcut of connection to project. Click on Yes. – Now we will observe one more connection called OBR_CONNECTION.cns – Delete the connection ApplicationRetailPOS.cnx and open ApplicationRetailPOS.dfx. And change the connection to OBR_CONNECTION – Right click on ApplicationRetailPOS.blx and publish to repository. 51

Create Report on BI Launch Pad

– Open Bi Launchpad http://:8080/BOE/BI

– Select the generated universe and create a sample report.

52

Content Dev : Next Steps …

Deploy content

Verify content

•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.

Reports: Build & package •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

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 on Default.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 command separately for each artifact. For this you need to add BO_HOME in environment variables, with value in quotes(“”). – The creation of the Application Content Pack might fail with an exception “Tables not found in database”, to rectify this exception, ensure that before the creation of Application Content Pack, the Domain Content Pack is installed. 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!

You have registered for this workshop, but you have not earned the points? Complete the challenge on ITOM Insiders to get your points:  https://itominsiders.influitive.com/?&id=1670 Not a member yet? Send us an e-mail to receive your invitation.

60

...or two?

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.

61

Questions?

62

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

63