Computer Associates SQLSTQ99000600 Diagnostics Guide - Page 34

Apply the Cure and Document the Solution, Unicenter IT Resource Management Diagnostics Guide - jobs

Get Computer Associates SQLSTQ99000600 - Unicenter SQL-Station 6.0.0 PDF manuals and user guides
UPC - 757943257441
View all Computer Associates SQLSTQ99000600 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 34 highlights

Apply the Cure and Document the Solution „ Each agent can only connect to and be managed by one Domain Managertherefore, it is critical that each agent, which is being migrated from two or more legacy products\managers, end up in the same UDSM r11 domain. Use integration between USD-UAM query groups or dynamic groups to automate migration scope group population. „ Migration tasks rely on HostUUID for lookups of already migrated agents in the MDB. If, in previous releases, you had multiple agents sharing the same HostUUID, the information for multiple legacy agents could end up being merged into a single r11 agent record. Steps for identifying agents with duplicate UUIDs can be found in the Implementation Guide. „ Data migration for managers is performed through a new migration engine task - one job per product and per pre-r11 manager that you want to migrate from. There are several considerations that are specific to each component. For example, when migrating Software Delivery you need to be aware that: „ on Windows, the migration job relies on the USD r.0 API - if the UDSM manager and USD 4.0 managers are co-hosted, the migration job will reuse the installed USD API. If not, you will need to install the legacy USD 4.0 API manually. „ on Linux - the USD 4.0 API is installed as part of the UDSM manager - no additional steps required „ MSI support has changed. Carefully review the Implementation Guide for details and information on specific considerations and migration tools before any migration of legacy local servers is performed. For Asset Management, you need to be aware that: „ only software inventory based on filescan in UAM 4.0 is migrated. Software inventory based on heuristic scanning is not. „ only application definitions found on one or more computers are migrated. To migrate an application definition which is not currently found on any computer, create a category in UAM 4.0 called "migration" and link those definitions to it. „ software definitions are migrated - configuration and collected metering data is not - nor is auditing. Metering must be reconfigured and rerun to collect new data „ in order to migrate UAM query jobs successfully, you must run the migration job at least twice because of two-way dependencies „ the "execute job after logoff" scheduling feature is not supported for r11. If you migrate a job that uses this feature that job will be migrated without this setting. „ if you are migrating from multiple UAM 4.0 sources to one UDSM r11 database, ensure that template definitions have unique file names before rescheduling them 5-4 Unicenter IT Resource Management Diagnostics Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
Apply the Cure and Document the Solution
Each agent can only connect to and be managed by one Domain Manager-
therefore, it is critical that each agent, which is being migrated from two
or more legacy products\managers, end up in the same UDSM r11 domain.
Use integration between USD-UAM query groups or dynamic groups to
automate migration scope group population.
Migration tasks rely on HostUUID for lookups of already migrated agents in
the MDB.
If, in previous releases, you had multiple agents sharing the
same HostUUID, the information for multiple legacy agents could end up
being merged into a single r11 agent record.
Steps for identifying agents
with duplicate UUIDs can be found in the Implementation Guide.
Data migration for managers is performed through a new migration engine
task - one job per product and per pre-r11 manager that you want to
migrate from.
There are several considerations that are specific to each component.
For
example, when migrating Software Delivery you need to be aware that:
on Windows, the migration job relies on the USD r.0 API - if the UDSM
manager and USD 4.0 managers are co-hosted, the migration job will
reuse the installed USD API.
If not, you will need to install the legacy USD
4.0 API manually.
on Linux - the USD 4.0 API is installed as part of the UDSM manager - no
additional steps required
MSI support has changed.
Carefully review the Implementation Guide for
details and information on specific considerations and migration tools
before any migration of legacy local servers is performed.
For Asset Management, you need to be aware that:
only software inventory based on filescan in UAM 4.0 is migrated.
Software inventory based on heuristic scanning is not.
only application definitions found on one or more computers are migrated.
To migrate an application definition which is not currently found on any
computer, create a category in UAM 4.0 called "migration" and link those
definitions to it.
software definitions are migrated - configuration and collected metering
data is not - nor is auditing. Metering must be reconfigured and rerun to
collect new data
in order to migrate UAM query jobs successfully, you must run the
migration job at least twice because of two-way dependencies
the "execute job after logoff" scheduling feature is not supported for r11.
If you migrate a job that uses this feature that job will be migrated
without this setting.
if you are migrating from multiple UAM 4.0 sources to one UDSM r11
database, ensure that template definitions have unique file names before
rescheduling them
5–4
Unicenter IT Resource Management Diagnostics Guide