FMS3 Process Scope

Question

I have a suite of FMS apps that I want to deploy across
different VHosts on ws2003. The principal app is deployed in packs
of 15 instances, although there are about 5 smaller 'helper' apps
which are mainly singletons. Each pack is a running unit - so from
a process isolation point of view, setting process scope to "app"
seems fine. But this raises the following questions:
1) What are the performance implications of each scope - my
guess is that 'inst' scope is expensive. But are there scalability
or resource implications for each scope? I'd be interested to know
if scope can play an active part in tuning my apps.
2) If scope is set at the application level, and I set it to
'inst', and I do this for each application, does this mean that if
I have 10 apps with 10 instances each, that I create 100
FMSCore.exe processes? And does it mean that if I set 'numproc' to
3 for each of them that I'd create 30 processes?

Answer 1

Hi,
I tried without using any valuechange listener and its absolutely working fine.
No need of putting any values in processScope and blah blah!!
I am passing values in backing bean for the ExecuteWithParams this way:
BindingContainer bindings = getBindings();
OperationBinding operationBinding =
bindings.getOperationBinding("ProcurementLOVParams");
Map map = operationBinding.getParamsMap();
map.put("ContractTypeBind", conTypeChoice.getValue().toString());
map.put("ContractPseBind", pseNumber.getValue().toString());
Object result = operationBinding.execute();
And this is working fine..
Thanks,
Sanjaykar