CA Service Management

Expand all | Collapse all

Error with a Web Service - Service Catalog

  • 1.  Error with a Web Service - Service Catalog

    Posted 10-31-2016 10:41 AM

    Hi Team, 


    Our customer has Service Desk, Service Catalog and PAM (Version 12.9), actually the end user create the request from Service Catalog and they can attach document without any problem, then there is a two Process on  PAM, the first process create the request on Service Desk, and the second process create a link of the attachment. 


    The problem is with the second process called "add_Attachment", in this process I execute a Web Service called "addAttachmentToRequestItemWithPath" whit the next structure: 



    <soapenv:Envelope xmlns:xsi=''
    xmlns:xsd='' xmlns:soapenv='' xmlns:ser=''>
    <soapenv:Header/> <soapenv:Body>
    <ser:addAttachmentToRequestItemWithPath soapenv:encodingStyle=''>
    <sessionID xsi:type='soapenc:string' xmlns:soapenc=''></sessionID>
    <requestID xsi:type='xsd:int'>86324</requestID>
    <subscriptionDetailID xsi:type='xsd:int'>257568</subscriptionDetailID>
    <attachmentName xsi:type='soapenc:string' xmlns:soapenc=''>ixutil.txt</attachmentName>
    <attachmentDescription xsi:type='soapenc:string' xmlns:soapenc=''></attachmentDescription>
    <attachmentPath xsi:type='soapenc:string' xmlns:soapenc=''>C:\Program Files\CA\Service Catalog\scripts\ixutil.txt</attachmentPath>
    </ser:addAttachmentToRequestItemWithPath> </soapenv:Body></soapenv:Envelope>


    If i execute this structure on Soap UI (SoapUI | Functional Testing for SOAP and REST APIs ) it finished Ok. But when i used the web service since PAM (whit operator Invoke SOAP Method) the result is "soapenv:Server.generalExceptionException occurred in"


    I don´t Understand which is the error, any idea? 



  • 2.  Re: Error with a Web Service - Service Catalog

    Posted 10-31-2016 11:11 AM

    Hello Wicner.
    On a local server, I managed to execute the SOAPUI wsdl method properly too.
    <soapenv:Envelope xmlns:xsi="" xmlns:xsd="" xmlns:soapenv="" xmlns:ser="">
          <ser:addAttachmentToRequestItemWithPath soapenv:encodingStyle="">
             <sessionID xsi:type="xsd:string">1b20dc14-d4a6-403f-95b1-4dfd2eb7e6f9</sessionID>
             <requestID xsi:type="xsd:int">10131</requestID>
             <subscriptionDetailID xsi:type="xsd:int">10656</subscriptionDetailID>
             <attachmentName xsi:type="xsd:string">stderr.txt</attachmentName>
             <attachmentDescription xsi:type="xsd:string">Test Attachment in SOAP</attachmentDescription>
             <attachmentPath xsi:type="xsd:string">C:\Program Files\CA\Service Catalog\stderr.txt</attachmentPath>
    Unfortuntalely, I do not have a PAM process to check this in PAM, so I can not test this in there.
    The following information I found:
    The Request web service includes the method addAttachmentToRequestItemWithPath which adds an attachment to a service option.
    The attachment is uploaded to the following folder: USM_HOME\filestore\documents\requests\request_id
    USM_HOME is the documentation convention that specifies the local CA Service Catalog installation directory.
    The default path name is C:\Program Files\CA\Service Catalog. And request_id specifies the ID of the catalog request.
    The above made me thinking on this:
    1. Since the folder-name as used in the SOAPUI, holds a space, could this cause the PAM process to fail?
    2. Can the PAM process 'access/reach/write into' the named USM_HOME\... folder for the request_id?
    Please check on the above and let me know your findings.
    Thanks and kind regards, Louis van Amelsfort.

  • 3.  Re: Error with a Web Service - Service Catalog

    Posted 10-31-2016 11:47 AM

    If you are just trying to sync attachments from Catalog to SDM there are OOTB event/rule/actions and PAM processes that accomplish this:


    Synchronize Notes and Attachments