Configuring the DSM Legacy Integration

before you can install the software through a service request or incident in , you must synchronize the software between desktop and server management (dsm) and (see synchronizing software packages and sets docid 5xpr0a1 znljnd8rchvt ) the software must also be activated on (see activating software packages and os sets docid\ lcrmqk1abl2vg 3rko5fp ) s periodically synchronize software packages to keep the list up to date after manually activating packages, sets, and operating systems, s can install or provision a software package on a managed computer establishing the dsm legacy environment step # step description reference 1 specify the dsm server url and restart the dsm messenger service see configuring the new dsm integration docid\ x0r5tiz6qouj7r9ii2xys 2 ping the dsm server from to verify connectivity 3 synchronize software so that software packages and sets on the dsm application are accessible through see synchronizing software packages and sets docid 5xpr0a1 znljnd8rchvt 4 activate the software to make it available for installation or provisioning through during activation you can update software parameters, specify whether approval is required, and publish the software by making it available in the self service portal activating software packages and os sets docid\ lcrmqk1abl2vg 3rko5fp and specifying approval for software packages docid 5xpr0a1 znljnd8rchvt 5 update the default software package parameters viewing and editing default installation parameters docid 5xpr0a1 znljnd8rchvt 6 link the software packages to software records to enable dsm managed software to appear in the software list linking software packages to software records docid 0keewn lklkkhasijbno1 7 create the hardware and software profiles for provisioning defining hardware and software profiles docid 7xzv1c2mxhgbpwq33yc 8 map the configuration items to dsm managed computers mapping configuration items to dsm managed computers docid\ aur6yozs4pcqfvqalj20r configuring the software you must apply the following changes in dsm update to dsm release 7 0 2 or a newer version open the dsm console specify the url for the dsm integration service dsm console log into the configuration database see the configuration database guide for for more information about using the configuration database open the tenants workspace and then open the tenant copy the value in the client authentication key field into the dsm console field in the dsm console set the integration with field to cloud platform (this was formerly called itsm saas ) save the changes that you made in the dsm console stop and restart the dsm messenger service ping the dsm server from to verify connectivity, as described in pinging the dsm server docid\ fpvwdx gpmvci9kneqmc4 pinging the dsm server ping the dsm server to check the connection between and dsm log into the console open the dsm on demand sync request legacy workspace click new dsm sync request from the sync request type menu, choose ping dsm service click save click refresh if the ping is successful, the status changes to completed if the ping fails, the status changes to failed dsm ping server if the ping fails, do the following check the connectivity between the dsm messenger service and the dsm integration web services check the connectivity between the dsm server and the dsm integration web services check the workflow instantiation record upon creating the ping request viewing configuration items in the dsm managed software legacy workspace s can open the dsm managed software legacy workspace to view (but not change) managed software, its status, and other information log in to open the dsm managed software legacy workspace to view software synchronization and activation status software parameters whether a package is uninstallable whether an approval is required for a package whether a package or set is published to the portal