Configuring the DSM
This section contains an overview of HEAT–DSM integration concepts.
The HEAT–DSM integration makes DSM software lifecycle management tools available in the HEAT application.
You configure the HEAT and DSM servers as separate entities. The DSM server is configured by default. However you must configure the DSM integration within HEAT, as described in Configuring the DSM Environment in HEAT to create an integrated HEAT–DSM environment.
Software Synchronization and Activation
Before you can install software through a service request or incident in HEAT, the software must be synchronized between the DSM system and HEAT. (See Synchronizing Software Packages and Sets.) The software must also be activated on HEAT. (See Activate Software Packages, Software Sets, and Operating System Sets.)
Service Desk Analysts periodically synchronize software packages to keep the list up to date. After manually activating packages, sets, and operating systems, Service Desk Analysts can install or provision a software package on a managed computer.
DSM Workflows
The HEAT–DSM integration uses the following workflows:
FRS_data_dsm_sync_request business object:
DSM Sync
Incident business object:
Approval Incident Detail Workflow
SoftwareInstallation and Computer Provisioning completion
ScheduleEntry business object:
DSM Computer Sync
DSM Software Sync
Task.ComputerProvisioning business object:
Software Provisioning
Task.SoftwareInstallation business object:
Activate Task
Software Installation Request