Clarity

Expand all | Collapse all

BPM-0704:Failed to send a SOAP message generated to

  • 1.  BPM-0704:Failed to send a SOAP message generated to

    Posted Aug 28, 2013 09:58 PM
    Hi,

    I am calling an external web service (Sharepoint) to create a new Sharepoint site. Please see my script and the error message I get. I have tried a few things checking related posts, but nothing seems to work. Just wanted to check if my script is ok? (the error message is given after the gel script)

    ------------------------------------------SCRIPT

    <gel:script xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:core="jelly:core"
    xmlns:file="jelly:com.niku.union.gel.FileTagLibrary"
    xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary"
    xmlns:soap="jelly:com.niku.union.gel.SOAPTagLibrary"
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:sql="jelly:sql" xmlns:xog="http://www.niku.com/xog"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

    <gel:log category="INFO" level="INFO">Start</gel:log>

    <soap:invoke endpoint="http://centre.ourspace/it/is/ispteam/solutiondelivery/agile/_vti_bin/Meetings.asmx" var="auth" soapAction="http://schemas.microsoft.com/sharepoint/soap/meetings/CreateWorkspace">
    <soap:message>
    <soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope">
    <soapenv:Header/>

    <soapenv:Body>
    <CreateWorkspace xmlns="http://schemas.microsoft.com/sharepoint/soap/meetings/">







    <title>ABC0001</title>







    <templateName>sample.stp</templateName>







    <lcid>1033</lcid>







    <timeZoneInformation></timeZoneInformation>







    <recurrenceId>0</recurrenceId >







    <uid></uid>







    <sequence>0</sequence >







    <utcDateStamp></utcDateStamp>







    <cancelMeeting>true</cancelMeeting>







    <searchtext></searchtext>







    <maxResults>10</maxResults>







    <principalType>User</principalType>





    </CreateWorkspace>
    </soapenv:Body>
    </soapenv:Envelope>
    </soap:message>
    </soap:invoke>
    <gel:log category="INFO" level="INFO">End</gel:log>
    </gel:script>

    --------------
    Error Message
    BPM-0704: An error occurred while executing custom script: org.apache.commons.jelly.JellyTagException: null:12:202: <soap:invoke> Failed to send a SOAP message generated to 'http://centre.ourspace/it/is/ispteam/solutiondelivery/agile/_vti_bin/Meetings.asmx'.centre.ourspace at com.niku.union.gel.tags.soap.InvokeTag.doTag(InvokeTag.java:64) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) at com.niku.union.gel.tags.ScriptTag.doTag(ScriptTag.java:20) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at


  • 2.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Aug 29, 2013 01:40 AM
    To add to this, the URL that I am trying to hit in this SOAP call is NOT accessible from Clarity server, is that why I'm getting this error?


  • 3.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Aug 29, 2013 03:45 AM

    pankaj_navlekar wrote:

    To add to this, the URL that I am trying to hit in this SOAP call is NOT accessible from Clarity server, is that why I'm getting this error?
    Yes ; that would be one reason why a script would generate that sort of error.

    The GEL script runs "on" the server where the process-engine is running (usually your BG server). It runs "as" the user that is running the Clarity BG service. So if you logon interactively to that server as that user and can not connect to that URL, then the SOAP call in your GEL script will not be able to connect either.


  • 4.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Aug 30, 2013 12:08 AM
    Thanks Dave, I will try to get the access and re-try my code.


  • 5.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 01, 2013 10:42 PM
    So I have given another try this time ensuring that even the "server" can access the URL. It wasn't an issue with the access as such, I had to append a specific string to the URL, to make it work. This is the changed URL. Note the difference. This can be accessed from the server too
    http://centre.ourspace.int.corp.sun/it/is/ispteam/solutiondelivery/agile/_vti_bin/Meetings.asmx

    Now, to the "user id" part of it (who is accessing). I noticed that the user id that has access to the server is, let's call it "xyz" but I am accessing Clarity using a different one. So what I have done now is manually create a "User" on the Clarity admin side with id = "xyz" and running the process logged in as "xyz" so to be sure that the "running at" and "running as" issues are sorted (hopefully so).

    Now, I get this error

    org.apache.commons.jelly.JellyTagException: null:13:206: <soap:invoke> Failed to send a SOAP message generated to 'http://centre.ourspace.int.corp.sun/it/is/ispteam/solutiondelivery/agile/Lists/Assets/'.HTTP Error: Status-Code: 401: Access denied


  • 6.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 02, 2013 04:33 AM

    pankaj_navlekar wrote:

    Now, to the "user id" part of it (who is accessing). I noticed that the user id that has access to the server is, let's call it "xyz" but I am accessing Clarity using a different one. So what I have done now is manually create a "User" on the Clarity admin side with id = "xyz" and running the process logged in as "xyz" so to be sure that the "running at" and "running as" issues are sorted (hopefully so).
    OK I think this might be a problem for you. :unsure:

    The Clarity process is not running "as" a Clarity user (irrespective of what you do in the Clarity application). The process will be running "as" the operating system user who is running the BG process (I'm not even sure that this is your "xyz" user??) - and it will be running "as" that O/S user for all/any Clarity users that you may initiate that process as. Therefore if your "called web-service" has some element of authorisation based upon "who" is calling the web-service ; you will never be able to make that call "user-specific" (unless of course you can pass the "Clarity-user" to the web-service somehow).


  • 7.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 02, 2013 12:07 PM
    My guess is that SharePoint is configure to require authentication based on the HTTP Error: Status-Code: 401: Access denied.

    You are going to need to determine the authentication method that your SharePoint site is using.

    If it is set to basic authentication, you should be able to send the username and password in the soap header. If memory serves me right, think it looks something like this:
    <soap:Header xmlns:share="http://schemas.microsoft.com/sharepoint/soap/">
    < share:AUTHHEADER>
      < share:USERNAME>Administrator</ share:USERNAME>
      < share:PASSWORD>Password</ share:PASSWORD>
    </ share:AUTHHEADER>
    </soap:Header>
    If it is set to forms mode authentication you are going to need to use the Login method in the Authentication.asmx web service to get your ASPXAUTH cookie.

    This will be a challenge as you will need to include this cookie value in the request to the SOAP request header for the CreateMeeting method in the Meeting.asmx.

    It doesn't appear that "com.niku.union.gel.SOAPTagLibrary” supports setting cookies.

    You might want to try commons-jelly-tags-soap v1.0 which has a soap:invokeRaw method and might let you set the HTTP request headers to include the ASPXAUTH cookie.

    V,r,
    Gene


  • 8.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 03, 2013 02:15 AM
    this is my new script. error that I now get is org.apache.commons.jelly.JellyTagException: null:14:215: <soap:invoke> Failed to send a SOAP message generated to 'http://centre.ourspace.int.corp.sun/it/is/ispteam/solutiondelivery/agile/_vti_bin/Meetings.asmx'.HTTP Error: Status-Code: 500: Internal Server Error
    --------------
    <gel:script xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:core="jelly:core"
    xmlns:file="jelly:com.niku.union.gel.FileTagLibrary"
    xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary"
    xmlns:soap="jelly:com.niku.union.gel.SOAPTagLibrary"
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:sql="jelly:sql" xmlns:xog="http://www.niku.com/xog"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <gel:log category="INFO" level="INFO">Start</gel:log>
    <core:catch var="soaperr">
    <soap:invoke endpoint="http://centre.ourspace.int.corp.sun/it/is/ispteam/solutiondelivery/agile/_vti_bin/Meetings.asmx" var="auth" soapAction="http://schemas.microsoft.com/sharepoint/soap/meetings/CreateWorkspace">
    <soap:message>
    <soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope">
    <soapenv:Header>




    <soapenv:AUTHHEADER>




    <soapenv:USERNAME>my_user_id</soapenv:USERNAME>




    <soapenv:PASSWORD>my_password</soapenv:PASSWORD>




    </soapenv:AUTHHEADER>




    </soapenv:Header>





    <soapenv:Body>
    <CreateWorkspace xmlns="http://schemas.microsoft.com/sharepoint/soap/meetings">







    <title>PR1111023</title>







    <templateName>BTProjects.stp</templateName>







    <lcid>1033</lcid>







    <timeZoneInformation></timeZoneInformation>







    </CreateWorkspace>
    </soapenv:Body>
    </soapenv:Envelope>
    </soap:message>
    </soap:invoke>

    </core:catch>
    <gel:log category="INFO" level="INFO">soaperr ${soaperr}</gel:log>
    </gel:script>
    ---------------------


  • 9.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 03, 2013 06:04 AM
    Hi Pankaj,

    I have encountered this 500 Internal error earlier.
    We assumed that WCF services might not be accessible from gel scripts. I suspect it is happening in your case.

    To confirm, please access any other external web service which is not WCF and let us know.

    Regards,
    Ritesh


  • 10.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 03, 2013 07:41 PM

    riteshkumar wrote:


    We assumed that WCF services might not be accessible from gel scripts. I suspect it is happening in your case.
    Thanks Ritesh, were you able to find any solution to this? Or was it unresolved


  • 11.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 03, 2013 08:28 PM
      |   view attached
    If you use SOAPUI and enter your meeting.asmx, you should see that it support SOAP 1.1.


  • 12.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 03, 2013 12:05 PM
    Not sure but you might need the namespace for the AUTHEADER.
    <gel:script
    
    xmlns:core="jelly:core"
    
    xmlns:file="jelly:com.niku.union.gel.FileTagLibrary"
    
    xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary"
    
    xmlns:soap="jelly:com.niku.union.gel.SOAPTagLibrary"
    
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    
    xmlns:sql="jelly:sql" xmlns:xog="http://www.niku.com/xog"
    
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    
    
    <gel:log category="INFO" level="INFO">Start</gel:log>
    
    
    <core:catch var="soaperr">
    
    
    <soap:invoke endpoint="http://centre.ourspace.int.corp.sun/it/is/ispteam/solutiondelivery/agile/_vti_bin/Meetings.asmx" var="auth" soapAction="http://schemas.microsoft.com/sharepoint/soap/meetings/CreateWorkspace">
    
    
    
    <soap:message>
    
    
    
    
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:meet="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:auth="http://schemas.microsoft.com/sharepoint/soap/">
    
    
    
    
    
    <soapenv:Header>
    
    
    
    
    
    
    <auth:AUTHHEADER>
    
    
    
    
    
    
    
    <auth:USERNAME>my_user_id</auth:USERNAME>
    
    
    
    
    
    
    
    <auth:PASSWORD>my_password</auth:PASSWORD>
    
    
    
    
    
    
    </auth:AUTHHEADER>
    
    
    
    
    
    </soapenv:Header>
    
    
    
    
    
    <soapenv:Body>
    
    
    
    
    
    
    <meet:CreateWorkspace>
    
    
    
    
    
    
    
    <meet:title>PR1111023</meet:title>
    
    
    
    
    
    
    
    <meet:templateName>BTProjects.stp</meet:templateName>
    
    
    
    
    
    
    
    <meet:lcid>1033</meet:lcid>
    
    
    
    
    
    
    
    <meet:timeZoneInformation></meet:timeZoneInformation>
    
    
    
    
    
    
    </meet:CreateWorkspace>
    
    
    
    
    
    </soapenv:Body>
    
    
    
    
    </soapenv:Envelope>
    
    
    
    </soap:message>
    
    
    </soap:invoke>
    
    </core:catch>
    
    
    <gel:log category="INFO" level="INFO">soaperr ${soaperr}</gel:log>
    </gel:script>


  • 13.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 03, 2013 08:19 PM
    Thanks Gene, appreciate your continued assistance. Now I get this :-(

    org.apache.commons.jelly.JellyTagException: null:14:215: <soap:invoke> Failed to send a SOAP message generated to 'http://centre.ourspace.int.corp.sun/it/is/ispteam/solutiondelivery/agile/_vti_bin/Meetings.asmx'.HTTP Error: Status-Code: 401: Unauthorized


  • 14.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 03, 2013 09:26 PM
    Does you Sharepoint require domain user logins?

    If so, try adding the domain to your username.
    <auth:USERNAME>my_user_id</auth:USERNAME>
    to
    <auth:USERNAME>my_domain\my_user_id</auth:USERNAME>


  • 15.  RE: BPM-0704:Failed to send a SOAP message generated to

    Posted Sep 10, 2013 08:29 PM
    Thanks all for your help, just fyi, we're working through the issues, I'm sure it's to do with some SP issues at our end too.

    I'll surely post the final solution once we are through with this.