Topic
  • 4 replies
  • Latest Post - ‏2012-11-15T17:10:42Z by nukite8d
nukite8d
nukite8d
8 Posts

Pinned topic E2E Shadow-Resource?

‏2012-11-14T14:59:40Z |
Hi,
for an content based routing we have three domains:
CBR, WSO1, WSO2
and lets look only on one resource res.

The resource CBR-res gets requests and depending the content, it forwards the request to either WSO1 or WSO2.

With this in mind we got a relationship between all resources:
CBR-res must be online, as long one of the WSO-res is online.

In TSAMP I would create an shadow-resource (equivalency) checking, whether one WSO*-res is still online.

But how do I implement this in an E2E context?

Any hint would be helpful ^^

Cheers,
Manfred
Updated on 2012-11-15T17:10:42Z at 2012-11-15T17:10:42Z by nukite8d
  • SystemAdmin
    SystemAdmin
    46 Posts

    Re: E2E Shadow-Resource?

    ‏2012-11-14T16:00:56Z  
    Hi Mani,

    I don't know - maybe I have not quite understand your problem, but why dont you just create an E2E policy with two startAfter Relationships?

    WSO1 -- startAfter --> CBR
    WSO2 -- startAfter --> CBR

    GROUP_X
    member: WSO1
    member: WSO2
    member: CBR

    I mean - why do you need something link "start CBR when observed online WSO1 or WSO2" when you can say it the other way round?

    Cheers,

    Josi.
  • nukite8d
    nukite8d
    8 Posts

    Re: E2E Shadow-Resource?

    ‏2012-11-14T16:22:23Z  
    Hi Mani,

    I don't know - maybe I have not quite understand your problem, but why dont you just create an E2E policy with two startAfter Relationships?

    WSO1 -- startAfter --> CBR
    WSO2 -- startAfter --> CBR

    GROUP_X
    member: WSO1
    member: WSO2
    member: CBR

    I mean - why do you need something link "start CBR when observed online WSO1 or WSO2" when you can say it the other way round?

    Cheers,

    Josi.
    Hi Josi,

    CBR may not start before any WSO. Because CBR would try to forward requests to not running WSOs. (If one WSO is offline, the other works as backup.)

    With your suggestion, CBR would start after both WSO.

    If everything is offline.
    One WSO must start first, before CBR may start.
    CBR --> startAfter --> (WSO1 or WSO2)

    If both WSO are offline, CBR must be stopped.
    CBR --> forceDownBy --> (WSO1 and WSO2)
    or
    CBR --> forceDownBy --> GROUP_WSO
    Cheers,
    Mani
  • SystemAdmin
    SystemAdmin
    46 Posts

    Re: E2E Shadow-Resource?

    ‏2012-11-15T08:23:29Z  
    • nukite8d
    • ‏2012-11-14T16:22:23Z
    Hi Josi,

    CBR may not start before any WSO. Because CBR would try to forward requests to not running WSOs. (If one WSO is offline, the other works as backup.)

    With your suggestion, CBR would start after both WSO.

    If everything is offline.
    One WSO must start first, before CBR may start.
    CBR --> startAfter --> (WSO1 or WSO2)

    If both WSO are offline, CBR must be stopped.
    CBR --> forceDownBy --> (WSO1 and WSO2)
    or
    CBR --> forceDownBy --> GROUP_WSO
    Cheers,
    Mani
    Hi Mani,

    this sounds like another scenario requiring something like the serverGroup as known from SA zOS, right?

    I discussed a similar scenario before: https://www.ibm.com/developerworks/forums/thread.jspa?threadID=412496&tstart=15

    Maybe the trigger resources explained here do help, as long we dont have a servergroup?

    Cheers,

    Josi.
  • nukite8d
    nukite8d
    8 Posts

    Re: E2E Shadow-Resource?

    ‏2012-11-15T17:10:42Z  
    Hi josi,
    this looks promising, indeed :)

    I couldn't create an test-envirmont today, but will try to do it the next days.

    Thanks so far,
    Mani