Computer Associates SQLSTQ99000600 Diagnostics Guide - Page 45

Agent Registration, Infrastructure Deployment, Troubleshooting Installation and Migration

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 45 highlights

Infrastructure Deployment Important note (1): When the infrastructure deployment wizard is completed, a deployment job is created which manages the progress of the deployment to all the selected end systems. The status of this job can be viewed through the Unicenter DSM Explorer, but please note that the job is NOT persistent. It is maintained in the memory space of the DMDeploy manager process. If the DMDeploy manager exits for any reason (crashes, is restarted, machine rebooted) the job information is lost, as are any unprocessed status messages from end system installations, though these installations will continue if already started. Important note (2): All operating systems are not created equal. The deployment manager has different capabilities on different platforms. Two major restrictions on the Linux manager 1) it cannot push out a primer to Windows shares since it cannot run the installation command 2) it cannot enumerate Windows domains. You will get an error if you try to do the latter. The Windows manager, however, is fully capable of SSH & telnet/FTP deployment to UNIX variant targets. Important note (3): Deployment using FTP can seem back to front until you think about it. This method of deployment works as follows: „ DMDeploy Manager connects to target using telnet „ DMDeploy Manager issues ftp commands over telnet on the target, pulling the primer installation image from manager to target, i.e. initiating the FTP "get" request on the target. This is different from deployment via shares and ssh, which are pushes from the manager to target. This method only requires that a single FTP server be set up on the Manager, rather than requiring one on each target. Agent Registration When a Unicenter DSM agent is installed on an end system the first thing it does is attempt to register its existence with its Domain Manager via its Scalability Server. This registration process is common across all products and includes a limited amount of inventory information (known as "Basic Inventory" or sometimes "Basic Hardware Inventory"). Note that agents register on a regular basis but basic inventory information is delta'd after the first registration. Chapter 5: Troubleshooting Installation and Migration 5-15

  • 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
Infrastructure Deployment
Important note (1):
When the infrastructure deployment wizard is
completed, a deployment job is created which manages the progress of the
deployment to all the selected end systems. The status of this job can be
viewed through the Unicenter DSM Explorer, but please note that the job is
NOT persistent. It is maintained in the memory space of the DMDeploy
manager process. If the DMDeploy manager exits for any reason (crashes, is
restarted, machine rebooted) the job information is lost, as are any
unprocessed status messages from end system installations, though these
installations will continue if already started.
Important note (2):
All operating systems are not created equal. The
deployment manager has different capabilities on different platforms. Two
major restrictions on the Linux manager 1) it cannot push out a primer to
Windows shares since it cannot run the installation command 2) it cannot
enumerate Windows domains.
You will get an error if you try to do the latter.
The Windows manager, however, is fully capable of SSH & telnet/FTP
deployment to UNIX variant targets.
Important note (3):
Deployment using FTP can seem back to front until you
think about it. This method of deployment works as follows:
DMDeploy Manager connects to target using telnet
DMDeploy Manager issues ftp commands over telnet on the target, pulling
the primer installation image from manager to target, i.e. initiating the FTP
“get” request on the target.
This is different from deployment via shares and ssh, which are pushes from
the manager to target. This method only requires that a single FTP server be
set up on the Manager, rather than requiring one on each target.
Agent Registration
When a Unicenter DSM agent is installed on an end system the first thing it
does is attempt to register its existence with its Domain Manager via its
Scalability Server.
This registration process is common across all products and
includes a limited amount of inventory information (known as “Basic
Inventory” or sometimes “Basic Hardware Inventory”). Note that agents
register on a regular basis but basic inventory information is delta’d after the
first registration.
Chapter 5: Troubleshooting Installation and Migration
5–15