DX NetOps

  • 1.  Unable to get automatically ticket according to device location

    Posted Feb 13, 2018 01:12 AM

    Hi Team,

     

    I need to configure CA Spectrum and CA Service Desk integration by device Location. Foreg: If i have 1 router in Mumbai location and i have enabled automatic ticket creation, only ticket belongs to that location will automatically get to Mumbai location engineer. I have created the template and policy in CA Service Desk end. However do not know how to define location condition under service-desk-ticket-config.xml

     

    Please help me on the same.

     

     

    Regards,

    PMO DCN



  • 2.  Re: Unable to get automatically ticket according to device location

    Posted Feb 13, 2018 01:25 AM

    Hi

     

    You could try this, assuming you are using the SANM with Service Desk Manager.

     

    Create Global Collection with the Mumbai routers, create a policy in the Service Desk Manager.

     

    For example, you have created a Static Global Collection by the name "server" and would like to associate template "server_pt" for all the alarms which get generated on the Global Collection "server", you would need to perform the below on the OneClick Server:

     

    Step 1:
    ========

    Copy service-desk-ticket-config.xml from %SPECROOT%/tomcat/webapps/spectrum/WEB-INF/svdsk/config/ folder to %SPECROOT%/custom/svdsk/config/ folder

     

    Step 2:
    =========

    Open the file %SPECROOT%/custom/svdsk/config/service-desk-ticket-config.xml with editor like notepad

    Search for the below entries:

    <!--
    <sd-ticket>
    <model-association>
    <relation>0x1003a</relation>
    <left-model-name>(the name of the global collection)</left-model-name>
    </model-association>
    <sd-problem-type></sd-problem-type>
    <sd-userid></sd-userid>
    </sd-ticket>
    -->

     

    Add the below lines:

     

    <sd-ticket>
    <model-association>
    <relation>0x1003b</relation>
    <left-model-name>server</left-model-name>
    </model-association>
    <sd-problem-type>server_pt</sd-problem-type>
    <sd-userid></sd-userid>
    </sd-ticket>


    Our file should now finally look like below:


    <!--
    <sd-ticket>
    <model-association>
    <relation>0x1003a</relation>
    <left-model-name>(the name of the global collection)</left-model-name>
    </model-association>
    <sd-problem-type></sd-problem-type>
    <sd-userid></sd-userid>
    </sd-ticket>
    -->

    <sd-ticket>
    <model-association>
    <relation>0x1003b</relation>
    <left-model-name>server</left-model-name>
    </model-association>
    <sd-problem-type>server_pt</sd-problem-type>
    <sd-userid></sd-userid>
    </sd-ticket>

     

    Step 3:
    =========

    For the changes to take effect, log on to the OneClick Homepage from web-browser (e.g. Internet Explorer)

    Click on Administration Tab
    Click on Service Desk Configuration
    Scroll down -> click on Reload Ticket Rules
    You should see the message "Successfully reloaded the Service Desk ticket rules."
    Scroll down to the last and click on Save
    You should see the message "Successfully saved configuration."

     

    Important Note:
    ================

    NOTE 1:
    ========

    If you have created a Dynamic Collection, replace the code 0x1003b with 0x1003a in the line:

    <relation>0x1003b</relation>

    Therefore, the line should now look:

    <relation>0x1003a</relation>


    Our file should now finally look like below:


    <!--
    <sd-ticket>
    <model-association>
    <relation>0x1003a</relation>
    <left-model-name>(the name of the global collection)</left-model-name>
    </model-association>
    <sd-problem-type></sd-problem-type>
    <sd-userid></sd-userid>
    </sd-ticket>
    -->

    <sd-ticket>
    <model-association>
    <relation>0x1003a</relation>
    <left-model-name>server</left-model-name>
    </model-association>
    <sd-problem-type>server_pt</sd-problem-type>
    <sd-userid></sd-userid>
    </sd-ticket>

     


    NOTE 2:
    ========

     

    To determine if a Global Collection is static or dynamic - check for any search options condition. If there is a Search Criteria, the Global Collection is Dynamic, if there is none, Global Collection is Static



  • 3.  Re: Unable to get automatically ticket according to device location

    Posted Feb 15, 2018 02:02 AM

    Hi Sirha,

    Thanks for your reply.

     

    I have made same rule as you suggested above for static global collection. While reload Ticket rule, I got "error to reload rule". I have also tried with tomcat restart, but not any luck. I am getting the automatically tickets as default template not by created one. Is there anything else i can try?

     

    Regards

    PMO DCN



  • 4.  Re: Unable to get automatically ticket according to device location

    Posted Feb 15, 2018 02:06 AM

    Hi,

     

    I suspect typo errors in the service-desk-ticket-config.xml in the %SPECROOT%/custom/svdsk/config/ folder

     

    Could you please double check or upload it to us via ticket. Provide me the ticket number



  • 5.  Re: Unable to get automatically ticket according to device location

    Posted Feb 15, 2018 02:36 AM

    Hi Sirha,

     

    Uploded file service-desk-ticket-config.xml on ticket no 00956803. Please help me to find the error.

     

     

    Thanks.



  • 6.  Re: Unable to get automatically ticket according to device location

    Posted Feb 21, 2018 01:39 AM

    Hi Sirha,

    Have you seen ticket config xml file attached on case no 00956803. Am i doing something wrong?

    Help me on the same.

     

    Regards,

    PMO DCN