Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • BW6.X - BWCE - How to access HTTP headers while exposing or invoking WEB Services in BusinessWorks 6.X and BusinessWorks Container Edition


    While exposing or invoking WEB Services it is in some cases needed to access standard or custom HTTP headers. In BusinessWorks 5.X there was no other solution than developing an HTTP Proxy but this is no longer the case in BusinessWorks 6.X and BusinessWorks Container Edition.

    To get or set HTTP headers while exposing or calling WEB Services you have to do the following:

    Create an XML schema to manage your context

    Using the tool of your choice create an XML schema containing the elements you want to use to set or get HTTP header values.

    1*5hRrJndaBGimtmr0iBgLbg.jpeg

    Define the context in the BusinessWorks process exposing or invoking the WEB Service

    Depending on what you want to do select the Component or the Reference that needs HTTP headers to be accessed.

    Open the Context tab and set the Input Context or Output Context or both as needed.

    1*SZnWpiQOAoub9VHBzVSszQ.jpeg

    Note : it is possible to use the same context for all operations or a specific context for each operation (click on the yellow pencil icon for this).

    Set or Get the context in the BusinessWorks process

    Add a Set Context or Get Context activity, or both, in the process and map inputs has needed.

    1*TVNLxV6CHBD6zToT-a0FUg.jpeg

    Map the header fields in the SOAP Service Bindings

    Then select the Component corresponding to the target process Component or Reference and open the ‘Bindings’ tab and map the Headers using the Request Context or map the Response Context using the Headers or both as needed.

    1*Q0Ln75l5_0_tnxCKVQ8XgQ.jpeg

    Note that it is possible to access standard HTTP Headers and also custom HTTP Headers as shown in the example above.


    User Feedback

    Recommended Comments

    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...