IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
  • 1.  CAF Error.

    Posted 02/22/16 02:15 AM

    Hi,

    I’m new in the webMethods CAF development and i went through one of the CAF tutorial videos from SAG.

    In that there was a simple example where we just drag the WSDL of our service from the IS package tab to the view and the system automatically generates the UI with Input, output parameters and refresh button to get the output.

    I’m getting the below error when i click refresh after providing the input parameters. Anybody knows how to get this working ?

    Error:

    POST /asa/default.view

    body:
    jsf:disjointForm = osS01LCiqit4h1vvV3HufbX/QL4nv4hc73kPrN7d2RU=
    jsf:disjointForm:htmlInputText = com.webMethods.caf.wsclient.ikea.xmltest_wsd.IKEAXmltest_WSDStub$Xmltest@f1a42d2
    javax.faces.ViewState = …
    __forms = jsf:disjointForm
    __fc = jsf:disjointForm:button
    __vf = jsf:disjointForm
    hiddenRequest = true
    shell = shell.blank
    replaceForNextUrl = hiddenRequest=&shell=&layout=&portlet=

    403 Forbidden

    403 !role

    !role (403)

    The requested URL /asa/default.view resulted in an error.

    ==================================================================

    br,
    Kiran


    #MWS-CAF-Task-Engine
    #webMethods-BPMS
    #webMethods


  • 2.  RE: CAF Error.

    Posted 02/22/16 06:17 AM

    Hi Kiran,

    please provide your MWS version.

    One place to check:

    MWS SysAdmin portal:
    Under Folders → System → Portlets → check the Tools Menu for Permissions.

    Please add “View Only” to the User/Group/Role your are running the Portlet with.

    Reagrds,
    Holger


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 3.  RE: CAF Error.

    Posted 02/22/16 06:53 AM

    Hi Holger,

    Thanks for your quick reply.
    I should have mentioned this in the beginning itself. Im using Wm9.5 version.

    Im building a web application it is not a portlet, so i’m not getting this option in the MWS console.

    Now i tried to build a portlet application and made the changes you suggested and got he below error !

    Error: com/webMethods/portal/webservices/wss/WSStackClientInitializer

    br,
    Kiran


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 4.  RE: CAF Error.

    Posted 02/22/16 04:12 PM

    The 403 error means that the current user isn’t a member of the role that the in the web.xml has defined as required for access to that page.


    #webMethods-BPMS
    #MWS-CAF-Task-Engine
    #webMethods


  • 5.  RE: CAF Error.

    Posted 02/23/16 03:31 AM

    Hi Eric,

    I was trying to create a web service connector from my the IS service in a web application project. In this case i get the 403 error.
    In the web.xml the role node is *. should i be creating a role and update here ? im using the Administrator user.

    But the same if i try to create a portlet project and then create a portlet it seems to work without any issues.

    Not sure why it doesnt work in web application.

    br,
    Kiran


    #webMethods-BPMS
    #MWS-CAF-Task-Engine
    #webMethods


  • 6.  RE: CAF Error.

    Posted 02/23/16 12:29 PM

    I don’t recall off the top of my head what the exact behavior was in 9.5

    But for standard container managed security, * in auth-contraint in web.xml files does not mean any role, it actually means any role that is declared in the web.xml file with a myrole element. This is the correct behavior as specified by the servlet specification.

    Unfortunately, earlier versions of CAF have incorrectly used the * auth constraint to indicate any user that has been authenticated (i.e. not anonymous). I believe this was corrected in MWS/CAF 9.8.

    You could try changing * to Everyone or some other existing role name in your MWS instance to see if that works better for you.


    #webMethods-BPMS
    #webMethods
    #MWS-CAF-Task-Engine