Upgrading tips when going from 5.x to current version

	Product(s):	APM Implementation and Performance Management
	Version(s):	All
	Environment:	N\A
	Area:	N/A
	Subarea:	N\A

Various upgrade tips sent to client doing their own upgrade from 5.x to 7.x

Things to note

UOM conversion from DTAs to database will need to be executed when going from 5.3.2 to 6.2.4. You would only require a temporary R6 license if you have too many custom UOMs to recreate manually. Look for instructions in the upgrade guide. If you need to do the automated conversion for custom uoms, contact Support for a legacy license key.

to tell which ones are custom - do a compare of the custom DTA with a base DTA to identify the newly added ones.

The odbc logon needs DBA rights for doing the upgrade. You can temporary assign DBA privileges to the Ivara user for the upgrade or you can use a dba credential for doing the upgrade.

For the upgrade, a upgrade of instance includes some extra steps in upgrading your existing APM server instance, but since you don’t have one in release 5, you should just go with upgrade database.

The thick client and server options since R6 is for the change in software architecture. Since release 6 APM is using 3 tier architecture.

A server is an instance that runs as a windows service and has odbc connection to the APM database. It resides on the application server and handles all the business logic processing. When APM server is setup, a thin client is packaged and deployed on end users machine and the thin client connects to the server instance.

A thick client is a self contained client, used in most cases by administrators. It has a direct connection to the APM database and does not require connection to a server instance.

Name is the APM thick client or server instance name, it uses this to find the database connection to run the upgrade wizard on.

Upgrading tips when going from 5.x to current version

Things to note

See Also