Hi Salvatore.
In response to this 'https://cawiki.ca.com/display/CASupport/SDM-Catalog+Integration" page I referred to
and with my apology (since this is an internal CA Support Page), I add the below information, taken from that page:
Catalog-SDM integration using Self Service integration option:
- Report an Issue offering in 14.1.
- It uses native integration between Catalog – SDM.
- No PAM is needed here.
Here’s what we know about this over couple of cases that we ran into:
1) Any request in Catalog (against this offering) would create a ticket in SDM automatically, through Events/Rules/Actions in CA Service Catalog(SC).
a. SC/Catalog/Offerings/IT Support Services/Service Management > 'Report an Issue' service invokes 'Java actions' to create the SDM ticket.
b. SC/Administration > Events-Rules-Actions > Request/Subscription Item Change > When Category is Service Management Content and Status is Pending Fulfillment > Create Incident
c. This is based on the service option category (i.e. Catalog > Service Offerings > Option Groups > Report an Issue > Definition > <Edit> > Category) set to 'Service Management Content'.
2) Associated SDM’s ticket contains a reference to Catalog request via: external_system_ticket attribute in SDM. It’s of the format: casc-<catalog_item_id>-<catalog_request_id>
3) From now one, SDM’s Catalog Sync Daemon (see further below on this page) is supposed to keep:
a. activity log updates synced to Catalog (SDM has new options for CA SC, see further below on this page).
b. attachments in SDM should sync to Catalog as a link.
c. status of SDM tickets should be synced to Catalog too. (one of them is – if SDM ticket is closed, then Catalog request should be set to Fulfilled).
Note: In SDM: itsm_msg_queue trigger on alg object does this magic apart from catalog_sync_daemon’s java code.
To debug the messages being sent from SDM To Catalog, with in SDM check Debugging section below:
4) SDM’s catalog sync daemon uses some internal messages of the format “123456@@@@@"Comments from SDM"@@@@@CASMAdmin” (Catalog request#, followed by comment in SDM, followed by userid separator is @@@@@)
5) This message is inserted into itsm_msg_queue table and then the message is processed by SDM’s Catalog sync daemon.
a. If it is successful, the record is deleted from the table.
b. If not, we keep retrying until retry count/interval is reached
If the message format was changed for some reason the integration will stop functioning.
In a similar way, if the user, updating the SDM request, doesn’t have the appropriate privileges on a Catalog Request, the sync won’t happen.
Thanks and kind regards, Louis.