Cognos Release Management Strategies using MotioCI

Presented by Mary Bolen

April 24, 2014

Agenda

I. Past State of Release Management Strategies at Hillsborough County Public Schools (HCPS)

I. Release Management

II. Version Control

II. How MotioCI Resolved Release Management Issues

I. Explanation

II. Demo

III. How MotioCI Resolved Version Control Issues

I. Explanation

II. Demo

IV. Q&A

Release Management

Moving reports between environments was time consuming and difficult

Past Release Management Process Export had to be created in

Development Environment Reports were selected

individually and added to the export

Reports were imported into QA environment

Process was repeated for move from QA to Production

Past Release Management Process - Export

Past Release Management Process – Import

Past Release Management Process

After the import is complete, the reports would be tested and the process would be repeated from QA to Production

The reports would then be manually copied from a QA Staging folder in Development into their corresponding Production folders

At that time the developers could begin working on the reports again as needed

Release Management

Difficulties with Approach

Required manual syncing of folders in Development environment

Separate version of report needed in order to continue development

Difficult to test drill through reports

Version Control

Difficulties without Versioning

Could not revert to a previous version if a mistake was made

Could not track when a report was being developed Report changes could be overwritten by another developer

Multiple versions of the reports existed

No version control existed

Solutions with MotioCI

MotioCI OverviewVe

rsio

n Co

ntro

l • Version all Cognos Object Types, Anywhere in the Content Store

• Version Framework Manager Models, Transformer Models, etc.

• Integration with Defect Tracking Systems

• Studio Integration & Exclusive Locking

• Recover Deleted Content• Version All Properties

Rele

ase

Man

agem

ent • Deploy Versioned Content

• Full Featured Content Labeling

• Scheduled Deployments• Promotion to Multiple

Cognos Environments• Impact Analysis of Staged

Content Deployments• Automated Promotion

Upon Validation• "Undo" Promotion Button

Auto

mat

ed T

estin

g*

• Regression Testing for Executable Content (reports, active reports, queries, etc.)

• Regression Testing for Non-executable Cognos Content (folders, dispatchers, data sources)

• Unlimited Regression Test Scenarios

• Regression Testing for all Output Formats (HTML, SQL, Excel, etc.)

• Stress Testing for Cognos• Continuous Verification of

Cognos Content

Release Management Solution

Label creation Administrators and Developers

Easy and Quick Report Promotion

Login Screen

Administration Console

Release Management Solution

Version Control Solution

Check Reports In and Out Lock Reports Note Major Revisions

Track Changes

Report Versioning Can revert back to previous version of report

Cognos Connection – Revision History

Report Studio Motio Integration

Report Studio Motio Integration

Report Studio Motio Integration

Report Studio Motio Integration

Version Control Solution

Things to Consider

Need to Determine: Who can create labels Who has authority to promote

Release Manager Who can revert reports back to previous versions How should projects be implemented?

*These are all customizable! Motio can adapt the configuration and security to match to your business!

Conclusion

MotioCI has empowered HCPS Cognos Administrators and Developers to work more efficiently and effectively

Q&A

Thank you!