apama, terracotta, webmethods upgrade: avoiding common pitfalls

14
APAMA, TERRACOTTA, WEBMETHODS UPGRADE AVOIDING COMMON PITFALLS Marianne Fuller Architect, R&D Solutions PM for SAG Installer and webMethods Installation/Upgrade/Database © 2015 Software AG. All rights reserved.

Upload: software-ag

Post on 13-Apr-2017

1.750 views

Category:

Software


0 download

TRANSCRIPT

Page 1: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

APAMA, TERRACOTTA, WEBMETHODS UPGRADE AVOIDING COMMON PITFALLS

Marianne Fuller

Architect, R&D Solutions

PM for SAG Installer and webMethods

Installation/Upgrade/Database

© 2015 Software AG. All rights reserved.

Page 2: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

2 |

PITFALLS AROUND THE UPGRADE PROCEDURE (UPGRADE GUIDE)

Identified through support calls and feedback from GCS and customers

© 2015 Software AG. All rights reserved.

WHERE are all sources of upgrade

info? Where is deprecation

and change info?

WHAT are supported

upgrade paths?

WHEN install fixes?

WHAT to do with my database

(clone)? What do db

migration scripts do?

WHERE find workarounds for

issues that arise?

!

Page 3: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

3 |

UPGRADE SEQUENCE (SIDE-BY-SIDE UPGRADE)

© 2015 Software AG. All rights reserved.

Gather doc needed to perform upgrade (release notes, readmes, guides)

Install new products in new directory or on new machine using SAG Installer or Command Central

Prepare old environment for upgrade (e.g., install fixes, stop document activity in IS)

Shut down old products

Migrate database components (will no longer be able to use them with old products)

If installing on a new machine, create zip files of old installations to use as source

Complete the upgrade for each product, usually by running a migration utility that migrates

configurations, assets, and data from old installation to new

Update SAG Infrastructure (for all products)

Configure new products (see product doc)

If installed on new machine, update host names in product configs and db tables

Adjust products and assets based on product change info in readmes

1

2

3

4

5

6

7

8

9

10

11

Page 4: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

4 |

MANY SOURCES OF UPGRADE INFORMATION

© 2015 Software AG. All rights reserved.

UPGRADE INFORMATION

System requirements (OS, RDBMS, etc.)

Release notes for new product features

Supported upgrade paths matrix

(details to follow)

Product and fix readmes

(details to follow) Upgrade guide

Using SAG Installer (how to use the

installer, not product specific)

Installing SAG Products guide (how to install products)

Using SAG Update Manager guide (how

to install fixes)

Page 5: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

5 |

SUPPORTED UPGRADE PATHS

© 2015 Software AG. All rights reserved.

Page 6: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

6 |

PRODUCT READMES CONTAIN CRUCIAL INFORMATION

© 2015 Software AG. All rights reserved.

PRODUCT READMES EXPLAIN:

• Deprecation of, changes to, or removal of

services, parms, props, APIs, other items,

and replacements, if any

• Changes to product behavior

• New services, parms, props, APIs,

other

• Critical info, known and resolved issues

USABILITY IMPROVEMENTS TO READMES:

• Deprecation policy at top

• Now cumulative

(e.g., 9.9 release readmes contain

information for 9.5 through 9.9)

• Many are now combined logically

(e.g., Rules Dev, Rules Engine, Rules

Console readmes now single Business

Rules readme)

• Read product readmes before upgrading, to help with planning

• Always read the readme for Software AG Infrastructure

• Use readme after upgrade to modify product files and assets

Page 7: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

7 |

UPGRADE GUIDE – CRITICAL REQUIREMENTS

© 2015 Software AG. All rights reserved.

NEW CHAPTER STARTING IN 9.8

RECOMMENDATIONS

upgrade in a controlled

test environment

CRITICAL

REQUIREMENTS

read readmes, do

steps in exact order,

don’t start products

prematurely

TESTED SCENARIOS

SAG tests migration

across machines that

have same hardware

and OS

REQUIREMENTS FOR

SPECIFIC PRODUCTS

e.g., how to update IS or

MWS cluster

NEW SECTION

REQUIREMENTS AND RECOMMENDATIONS FOR DATABASES

use clone, archive/purge

!

Page 8: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

8 |

INSTALL FIXES, AND READ FIX READMES FOR CHANGES

© 2015 Software AG. All rights reserved.

TYPES OF FIXES

• Install latest product fixes on new products

• Install latest product migration-utility fixes

(usually these are combined with product fixes

and are not separate)

• Install latest migration framework fix

(framework underlies all product migration

utilities – fix for this is very rare)

• *exception is SAG Infrastructure – that fix is

installed after running the SAG Infrastructure

migration utility

After installing new products,

install latest fixes

Always read fix readmes closely - fixes

can include changes to products

Since upgrade might take days or weeks

to complete, continue to check for and

install latest fixes throughout upgrade

Install latest product fixes on specified

old products

Page 9: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

9 |

PREPARE DATABASES

© 2015 Software AG. All rights reserved.

OLD AND NEW GUIDELINES

• Upgrade RDBMS to version supported by

new products (see System Requirements)

• Reduce time to migrate by archiving and

purging first (IS, Optimize, PE, and TN dbs)

• When backing up DBs, must back up MwS

installation directory at same time – if

problems, will need both, in sync

• Use cloned DBs when testing your upgrade

• Recommendation now stated in upgrade guide

• Follow instructions on grants and privileges

Page 10: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

10 |

MIGRATE DATABASE COMPONENTS

© 2015 Software AG. All rights reserved.

DB migration

scripts

update existing

DB schemas so

they are

compatible with

new product

release

New product

release might

require changes to

DB components,

such as new

tables, columns,

keys, or indexes –

details can be

seen by opening

the DB migration

scripts in a text

editor

Scripts might

modify

existing DB

components, or

might create

parallel DB

components with

the new structure

and then insert,

select, rename,

and drop the

tables, columns,

keys, and indexes

Scripts might

increase DB

size – will vary

each release –

upgrade partner

will have best

practices that will

help with

estimating this

Install the latest

fix on the DB

migration scripts

Page 11: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

11 |

FINAL UPGRADE TASKS

© 2015 Software AG. All rights reserved.

• Configure your new products (see product doc) 1 • If old and new products are on different machines, update host names:

• In new product UIs, and config files (see product doc)

• In connections between products

• In database tables (greatly reduced for BPM in 9.9) 2

• Read the readmes and modify product files and assets to accommodate:

• Deprecations, changes, or removals of services, parms, props, APIs, other

• Changes to product behavior 3

Page 12: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

12 |

COMBINED WEB HELP OF ALL INSTALL AND UPGRADE DOC

• Release notes for all supported paths

• Readmes for all supported paths

• System requirements

• Supported upgrade paths matrix

• Using SAG Installer

• Installing SAG Products

• Using SAG Update Manager

• Upgrading SAG Products

© 2015 Software AG. All rights reserved.

Page 13: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

13 |

DEVELOPING UPGRADE AREA ON TECHCOMMUNITIES

© 2015 Software AG. All rights reserved.

Wiki

Feedback on

upgrade and

upgrade

documents?

Pages that list

common issues

and

workarounds?

OPINIONS?

Page 14: Apama, Terracotta, webMethods Upgrade: Avoiding Common Pitfalls

14 | © 2015 Software AG. All rights reserved.