Enterprise Management System Andreas Dieckow Principal Product Manager Symposium 2011

Preview:

Citation preview

Enterprise Management SystemAndreas Dieckow Principal Product Manager

Symposium 2011

Challenges

• Today every Instance is configured individual• No structural view• Certain changes require re-starts• User Management is Instance specific

– Unless 3rd party components are used• No history of configuration changes• The Enterprise Management System is designed to

solve these challenges

Agenda

• Introduction• Detailed look at functional components• Demo• Q&A

The Enterprise

Development

QD

UAT

Production

The Enterprise

Development

QD

UAT

Production

Development

QD

UAT

Production

Development

QD

UAT

Production

Introduction• The Enterprise Management System (EMS) is a standalone

application• Designed to manage all registered Instances of Caché and

Ensemble• Provides centralized form to change configurations, and

security settings, and to perform user management• Configuration security • Build-in version control, with diff and compare capabilities

Standalone Application

• Client connectivity components starting with 2011.1• Enterprise Management System

– Standalone installation• Locked down• Pre-configured

– Build-in SMP functionality designed for EMS needs– Allows to act as a License Server

Managing the Enterprise

• Instances register with the EMS– Instances are grouped – Assigning an Instance to a Group completes the

registration process– EMS managed components are not accessible on the

Instance– Instances always see resolved Configuration changes– Instances may disconnect from the EMS

EMS - Groups

• Controls the managed components– Configuration– Security

• Changes to the configuration are performed using a special version of the SMP

• Editing and Activation are distinct operations• Configuration Security

– Edit Users, Activate Users– Access control on the Group level

EMS Groups

• Groups can be initialized by– The configuration of an Instance– Coping from a different from Group

• Instances can be moved between Groups• All Instances in a Group have the same configuration

– Unless the values are Instance specific• Pathnames• Port numbers• ….

Edit and Activate

• Configuration changes are pending until activated• All changes are versioned on activation• Previous versions can be compared to examine differences

– Can also be compared to the current pending changes• Previous versions can be activated• Editing and Activation configurations are audited

Synchronized Activation

• Some changes require synchronized activation– E.g. Namespace mapping– SSL configurations between Instances– Mirroring

• Multi-step process– Preparation– Activation

• After some steps synchronization with the EMS• Very short system freeze across Instances for Activation

Group and Instance Attributes

• Provides current state– On Group level– On Instance level

Group Attributes

Instance Attributes

Tags

• System Tags– Derived from the Instance

• Product Type, Version, OS– Derived from specific product usage

• E.g. Mirroring

• User Tags• Tags can have multiple values

– E.g. City Tag could be defined to include• Boston, Orlando, Dallas, Sydney, Tokyo, Frankfurt

Tags

• Tag view• Tags can be selected for a hierarchy level to provide a

structured view• Groups are at the bottom of the view, and can be selected

for details or modificationsBoston

Windows Unix VMS

Caché

Security Configurations

• User Management• Security settings

– Resources, Roles, System settings, ….• Changes are activated immediately • Users are known with all Roles throughout the Enterprise• Roles contents is specific to the Instances within a Group

Technology

• Browser based application• Web Services communications• WS-Policy

– Various levels of securing communications– Certificate based

• Mirrored configuration• On the horizon for 2012.1:

– PKI with certificate generation and distribution

Demo

• User Interface• Registration• Tags• Configuration Changes

– Compare– Auditing

• Users with Edit and Activate capabilities

Call for action

• Field Test for EMS in progress• Contact: andreas.dieckow@intersystems.com or your

Account Management team

Questions?

Andreas Dieckow
Please change the title of this slides to: Securing Data Elements using Credit Card information as an example.
Andreas Dieckow
Please remove the VISA logo from all the slides. We are not advertising for one Credit Card provider. From this and all following slides.

Join the Global Summit Community

We’ve established an online community where you can:

• talk about the Global Summit• get helpful product information• share your thoughts about sessions• ask questions of presenters• assemble a group to meet for dinner or social events,

etc.

community.intersystems.com

Recommended