COMP-10: OpenEdge ® Management & Replication – Divide et impera! Cyril Gleiman & Libor Laubacher Principal Technical Support Engineers

COMP-10: OpenEdge® Management & Replication – Divide et impera!

Cyril Gleiman & Libor LaubacherPrincipal Technical Support Engineers

© 2007 Progress Software Corporation2 COMP-10: OpenEdge Management & Replication – Divide et impera!

Agenda

What’s new in OpenEdge Management 3.1B What’s new in OpenEdge Replication 10.1B Getting OpenEdge Replication status via

OpenEdge Management Transition and Failback (+ demo) How to monitor SonicMQ® & Sonic ESB® from

OpenEdge Management

OpenEdge Management & Replication – Divide et impera!


Remote monitoring infrastructure upgraded to SonicMQ 6.1

New log file rules and search criteria for OpenEdge Replication

DataCompaction job improvements SNMP trap enhancements TrendDB SQL92 memory leak fixed

What’s new in OpenEdge Management 3.1B

Main new features


Support for IE 7 dbagent support for 64-bit databases Alerts can now set an email priority TrendDB enhancements to support 64-bit

VST’s Extra alerts can be thrown if a resource is

consistently failing


Main new features (cont.)


Scalability• Unlimited number of remote containers

• Only restricted by your system resources

Stability• No cache corruption for remote containers

• Status of resources remains stable

• OEMA remains online and reconnects when OEM machine restarts




Remote monitoring matrix



Remote monitoring

9.1E04TF10.0B05TF10.1A02TF10.1B01

OpenEdge 10.1B01OE Management 3.1B01

SonicMQ 6.1

OEMA = OpenEdge Management Agent (s)


D I S C L A I M E R

OE Management 3.1B: Under Development

This talk includes information about potential future products and/or product enhancements.

What I am going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here.

D I S C L A I M E R


Log file viewer and monitor for remote databases• Coming soon!!

Work in progress• Lays foundation for replication rules to be

used across all remotes– remote managed, scripted databases

• Targeted for 3.1B02


Remote database log file monitoring


Demo: Remote log file viewer + monitor


Agenda


OpenEdge Management Transition and Failback (+ demo) How to monitor SonicMQ & Sonic ESB from

OpenEdge Management

OE Management & Replication – Divide et impera!


What’s new in OpenEdge Replication 10.1B

Main new features – Semper paratus

Failback Online enabling of Source database New transition/recovery options Enhanced automated processing Audit replication events WGP DB support RDBMS IPC queue (-pica) current usage info

in PROMON -pica increased to 8192k in 10.1B01


Queue used by any RDBMS process which needs to send a message to another one

Specifies the amount of storage (in Kb) allocated for the queue

For Replication it contains notifications that RDBMS has just written an AI block

Important to set the size of –pica properly• Queue being full = database is stalled• Good to have a monitoring of –pica in place

What’s new in OpenEdge Replication 10.1B

-pica explained


Agenda




OpenEdge Management


Getting OE Replication status via OE Mgmt

Log file rules for OE Replication databases

One set of rules for source and target Need to hook “DB_OE_Replication” rule sets

to a database with Log File Monitor and Default Schedule Plan• When a rule gets broken, an alert will fire

• Can add customized and edit shipped rules

Database log file must be located on the file system known to OEM AdminServer


RDBMS IPC queue (-pica) usage monitoring• Need to call “promon db” under the covers

Status information monitoring• Need to call “dsrutil db –C status” under the

covers

OE Management custom job needed• Job calls “dsrutil” or “promon”, processes the

output and fires an alert if necessary

Getting OE Replication status via OE Mgmt


Demo: -pica usage and Replication status info


Agenda




OpenEdge Management


Primary – Original production machine Secondary – Original recovery machine Source – Production database Target – Recovery database Failover – Transitioning from Primary to

Secondary Failback – Transitioning from Secondary to

Primary

Transition and Failback

Replication terminology



Primary and secondary replication schema

Primary Machine Secondary Machine

Repl Agent

Database Brk/ServerProcesses

TargetDatabase

R/OClients

R/WriteClients

AI Extents

Repl Queue

Repl Server

AI ExtentsSource

Database

Database Brk/Server Processes



Secondary Machine

Repl Agent


TargetDatabase

R/OClients

R/WriteClients

AI Extents

Repl Queue

Repl Server

AI ExtentsSource

Database


Biff!

Kablam

!eeekk!

Primary Machine Loss of Database Comm. or Server Failure



Secondary Machine

Repl Agent


TargetDatabase

R/OClients

After timeout:• In pre-transition mode• Manual Transition• Automatic Transition



After timeout:• In pre-transition mode• Manual Transition• Automatic Transition• AI extents…• Target, now “Normal”

• Allows updates

Secondary Machine


NormalDatabase

R/WriteClients

AI Extents



After timeout:• In pre-transition mode• Manual Transition• Automatic Transition• AI extents…• Target transitions to Source

• Auto DB Restart option• Allows updates• Polls for repl agent

Secondary Machine


SourceDatabase

R/WriteClients

AI Extents

Repl Queue

Repl Server



• Shutdown Secondary Source Database

• Perform backup• Restore to Primary• Transition Primary to

Source• Transition Secondary to

Target

Secondary Machine


SourceDatabase

R/WriteClients

AI Extents

Repl Queue

Repl Server



Primary Machine Secondary Machine

Repl Agent


TargetDatabase

R/OClients

R/WriteClients

AI Extents

Repl Queue

Repl Server

AI ExtentsSource

Database


Back in business


Demo: Transition and Failback in OEM


Agenda



OpenEdge Management Transition and Failback (demo) How to monitor SonicMQ & Sonic ESB from

OpenEdge Management


TCP Monitor available OOTB• Set up new TCP resource with MQ and ESB

ports

OEM can call Sonic API to get more info• All pure java

• Need to use OEM Jobs and LFM capabilities

• Requires a bit of scripting and java coding

SonicMQ & ESB monitoring via OE Mgmt


Demo: SonicMQ & ESB monitoring


In Summary

OE Management and Replication They put chocolate in my peanut

butter. Two great tastes meant for each other.

Together they provide highest availability for your OpenEdge based systems.

Divide et impera!

© 2007 Progress Software Corporation31 Session ID: Session Title

For More Information, go to…

PSDN• www.psdn.com/library/kbcategory.jspa?categoryID=21• www.psdn.com/library/kbcategory.jspa?categoryID=334

Knowledge Centrum (esupport.progres.com)• 3.1B01/10.1B01 upgrade: P122926, P123418, P123420,

P123424, P123426, P123427, P123676• sizing –pica: P121969

Documentation• OE Replication 10.1B docs (www.psdn.com)• OE Management 3.1B docs (www.psdn.com)


Relevant Exchange Sessions

DB-2: OpenEdge Replication: How to get Home in Time …

COMP-13: The “Weakest Link” in your HA system

COMP-15: Disaster Recovery Planning – Be Scared, Be Very Scared


Questions?


Thank you foryour time


Documents

COMP-10: OpenEdge ® Management & Replication – Divide et impera! Cyril Gleiman & Libor Laubacher Principal Technical Support Engineers