SBM Integration with Remedy

SBM Integration with Remedy

Hi All,

We are trying to build an integration with Remedy using web services.

We have got it working for the most part.

The calls are tested and working from SoapUI.

We have an issue when trying to call from SBM. Our original issue was due to the WSDL. The Remedy web service requires header information (username/password token via WS-Security) which is required by the web service, but is not defined within the WSDL. We have now customised the WSDL to contain these fields and the WSDL imports correctly into SBM to allow us to map these fields.

When calling the web service, Remedy rejects this due to the format of the XML payload. SBM is adding additional elements (the name of the orchestration), which wraps the header components. A sample of the XML below. How do we remove these additional SBM elements/tags that are added to the XML being sent? They cannot be deleted within the Composer. The tags are highlighted below "RemedyTestService_executeProcess_Envelope".

Normal 0 false false false EN-ZA X-NONE X-NONE MicrosoftInternetExplorer4

<env:Envelope xmlns:env='' xmlns:xsd=''><env:Header><RemedyTestService_executeProcess_Envelope xmlns='' xmlns:bpws='' xmlns:defaultNS='' xmlns:defaultNS1='' xmlns:ns8=''>

              <ns9:Security xmlns:defaultNS='' xmlns:defaultNS1='' xmlns:ns9=''>

                <ns9:UsernameToken xmlns:defaultNS='' xmlns:defaultNS1=''>

                  <ns9:Username xmlns:defaultNS='' xmlns:defaultNS1=''>SBM</ns9:Username>

                  <ns9:Password xmlns:defaultNS='' xmlns:defaultNS1=''>sbmtoremedy</ns9:Password>



            </RemedyTestService_executeProcess_Envelope></env:Header><env:Body><defaultNS1:executeProcess xmlns:bpws='' xmlns:defaultNS='' xmlns:defaultNS1='' xmlns:ns10=''><ns10:gridName>GRID1</ns10:gridName><ns10:processName>:SBSA-OA-SBM_Integration:Submit</ns10:processName><ns10:parameters><ns10:Input><ns10:Parameter><ns10:Name>INP_EmployeeNumber</ns10:Name><ns10:Value ns10:type='Text'><ns10:Text>A186617</ns10:Text></ns10:Value></ns10:Parameter><ns10:Parameter><ns10:Name>INP_RequestDetail</ns10:Name><ns10:Value ns10:type='Text'><ns10:Text>Testing</ns10:Text></ns10:Value></ns10:Parameter><ns10:Parameter><ns10:Name>INP_ExternalReference</ns10:Name><ns10:Value ns10:type='Text'><ns10:Text>9389280</ns10:Text></ns10:Value></ns10:Parameter></ns10:Input></ns10:parameters></defaultNS1:executeProcess></env:Body></env:Envelope>HTTP/1.1 500 Internal Server Error


Labels (1)


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Grant, you might want to post this in the Forums, where you are more likely to get users to see this question and hopefully respond.
Now that you have a clear idea of what your theme is, you can flesh out the beginning and the end. Try to stay away from cutesy or clever opening lines and instead, try to answer
Top Contributors
Version history
Revision #:
2 of 2
Last update:
‎2020-01-30 18:18
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.