Layer7 API Management

  • 1.  Error passing Request  Source in the HTTP (S) Routing Properties

    Posted May 27, 2015 12:52 PM

    I'm having problems sending the parameters of the request to my web services routing in the HTTP (S) Routing Properties I define the variable type userRequest Message.

    request1.png

    In the http method I select the Automatic option, also tried with post method and the Headers tab SoapAction habiliete the option.

    routing.png

     

    Returning error if failed (status 500) and log file can web service I can see the following error

     

    error 2.png

     

    error log file server Web service application

     

    may 27, 2015 09:51:58 AM org.apache.axis.transport.http.AxisServlet getSoapAction

    GRAVE: Generating fault class

    AxisFault

    faultCode: {http://xml.apache.org/axis/}Client.NoSOAPAction

    faultSubcode:

    faultString: no SOAPAction header!

    faultActor:

    faultNode:

    faultDetail:

    {http://xml.apache.org/axis/}stackTrace:no SOAPAction header!

           at org.apache.axis.transport.http.AxisServlet.getSoapAction(AxisServlet.java:1013)

           at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)

           at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)

           at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)



    Can someone help me out.

     

    greetings,

    Enrique Mestas



  • 2.  Re: Error passing Request  Source in the HTTP (S) Routing Properties

    Posted May 27, 2015 01:01 PM

    i may be mistaken, but since you created a new 'message' variable 'userRequest', I'm not sure you can specify 'original_value' as no value has existed yet for the header SOAPAction for that specific message context. You'll need to populate this with something manually.

     

    I'll test and confirm shortly.



  • 3.  Re: Error passing Request  Source in the HTTP (S) Routing Properties

    Posted May 27, 2015 01:11 PM

    Confirmed.

     

    What the backend sees:

     

    (using 'original_value' populating the headers of a newly created 'message')

    all headers: connection:Keep-Alive,

                 content-length:4,

                 content-type:text/xml; charset=utf-8,

                 host:127.0.0.1:8080,

                 user-agent:Layer7-SecureSpan-Gateway/v8.2.00-b4710

                

    (injecting a header value)            

    all headers: connection:Keep-Alive,

                 content-length:4,

                 content-type:text/xml; charset=utf-8,

                 host:127.0.0.1:8080,

                 soapaction:boom,

                 user-agent:Layer7-SecureSpan-Gateway/v8.2.00-b4710



  • 4.  Re: Error passing Request  Source in the HTTP (S) Routing Properties

    Posted May 27, 2015 03:30 PM

    Hi Doyle

     

    Thanks for the answer, add the value in headers "orginal_value" and runs the answer.

     

    Saludos,

    Enrique Mestas



  • 5.  Re: Error passing Request  Source in the HTTP (S) Routing Properties

    Broadcom Employee
    Posted May 27, 2015 01:02 PM

    Enrique,

     

    From the error and the screen captures you need to enter a value for the SOAPAction header in the HTTP routing as there will not be an original value assigned to the userRequest context variable.

     

     

    Sincerely,

     

    Stephen Hughes

    CA Technologies
    Director, CA Suppor

     



  • 6.  Re: Error passing Request  Source in the HTTP (S) Routing Properties

    Posted May 27, 2015 03:33 PM

    Hi Stephen,

     

    Yes, that was the problem exactly "original_value" the header.

     

    Thanks for you help .

     

    greetings,

    Enrique Mestas