1 reply Latest Post - ‏2013-01-02T22:13:17Z by swlinn
6772 Posts

Pinned topic DP objects understanding that how its behaving...

‏2012-12-21T14:35:21Z |
I want to understand, how DP objects are behaving? like i am creating one reusable processing rule, and i am calling that object from other processing rules at run-time like based on some conditions, and most of time same processing rule will be using by all other processing rules.
Created request/response reusable processing rule, everything is working fine, no issue fount yet. But need to understand the inner processing. As i know, it should not be create any issue as it will create new object for each request.
If anyone has some other view please share with me, so i can finalize the design.

Another query, i need to implement the processing rule at operation level, but need to support the http/https port as same time, if i am adding MPGW in front of WSproxy, it will take extra hop in production. Not want to use any extra object.
If i am adding, another FSH, it will create new port/operation for that FSH, which means i need to implement same on it, I know MPGW is the best solution of it as it will support multiple FSH at same time.
Need your input.
How much time will be taken by MPGW in front of WSproxy? For me it will take 10ms max.
Updated on 2013-01-02T22:13:17Z at 2013-01-02T22:13:17Z by swlinn
  • swlinn
    1344 Posts

    Re: DP objects understanding that how its behaving...

    ‏2013-01-02T22:13:17Z  in response to SystemAdmin
    For question 1, you can call a common rule from different service's processing policy. Each instance will be passed data (a context) from the main rule and it's OUTPUT context will go to the call action's output context. There is no interaction between different invocations of each rule.

    For question 2, you can have a WSP with a http and https FSH for the same wsdl endpoint. Just click on the + to create the FSH and then click on the Add button to add that to your endpoint processing. Your processing rules are part of your policy specification, so regardless of if the request came in on either protocol, your operation based processing rule will process the request.