"Patrick Collins" <patrick...@energex.com.au> wrote in message
news:<3c1a5df1$1...@news.beasys.com>...
> I think the only way you can do this is with Data Dependant Routing,
Darren,
This approach works well if you are using FML or VIEW type
buffers you can use the *ROUTING section of the ubb to get the
desired behaviour.
I use this to ensure a service on a appropriate (i.e. local)
machine is called by default. To do this the client needs to add a
field into the buffer to show which machine it is on. You then set
up the routing information to ensure that the service on the
desired machine is called. Below is an extract from a ubb that we
use to do this type of routing:
##############################################################
*SERVICES
##############################################################
HUBQS ROUTING="HUBQSROUTING"
##############################################################
*ROUTING
##############################################################
HUBQSROUTING FIELD=F_AA_APPCODE BUFTYPE="FML32"
RANGES="'CIS':HUBQGRP_NUMA40,'ICIS':HUBQGRP_NUMA64
The HUBQS service is available on two machines (NUMA40 and NUMA64).
The groups that the service is located in are HUBQGRP_NUMA40 and
HUBQGRP_NUMA64. The F_AA_APPCODE field within the FML buffer
allows us to deterime which machine is involved so the messages
are routed to the correct machine.
Hope this is of some help.
Jackson McCann