Give it a name and copy out the Client Key.Ĭopy this as you will need it later. Login and click on Security and then Edit REST API client settings.Ī window will pop up and you will need to click on the green plus to create a new one. To get this client ID Launch the Cherwell Administrator console. The Client ID is basically a generated string called the client key used for connecting to Cherwell’s API. Note that you do not want to copy the entire URL. You will want to copy this to use in the OMS ITSM connector setup. Launch Cherwell.īefore you login you can edit the connection to see the URL as shown in the screenshot. If you don’t know your Cherwell URL you can get this from the Cherwell client console. So you will need a username and password of an account that has access to Cherwell, the Cherwell URL, and a Cherwell Client ID. Needed settings from Cherwell:īefore you set the connection in OMS go and get the information you will need. The documentation is good however after setting this up I did find that there could be a few more steps spelled out as well as screenshots with the Cherwell piece. There is official documentation for the integrations. I wanted to give this a test run with a test Cherwell instance that I have. Hopefully in the future OMS could be used to populate a CMDB and even create application maps from OMS’s Service Map. This new ITSM connector is bi-directional meaning work items can flow from the ITSM solution into OMS and OMS can create work items in the ITSM solution such as incidents, alerts, and events. The ITSM solutions it can connect to are: This new ITSM connector can connect to many ITSM solutions out there. Microsoft has built an ITSM connector in OMS. Microsoft recently released public preview of OMS and ITSM integration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |