Hello Websphere forum users, I would be much appreciated, If I could have your advise on the following issue: - Preface about cust. infrastructure: One of the major local bank accounts (Alpha Bank) has deployed a J2EE FileNet Workflow application (cardloans) on top of Websphere platform. The architecture actually relies on High Availability (failover) at three layers : Network Dispatchers, Web Servers, WAS servers. Actually the two Network dispatchers (Edge/LBs) -primary & backup- are using as back end servers the two HTTP Servers (Active/Active failover) for load balancing and each Web server routes and distributes load (session trafic) among the two WAS cluster nodes via plugins. There are also another two Wintel servers in FileNet production architecture : One Server that "hosts" the Card Loan application source code , written in Power Builder (programming tool with GUI for RDBMS which builds queries, buttons, etc) and uses COM+ for communication. A second Server that acts as Process Distributor (ODISY) in order to route web user requests and exploits native web services for communication. Meaning that web services are being used when application users hit a URL for accessing the application. The application programming tool used in this case was Delphi. ODISY manages the COM+ API calls from clients, and it has registered the IP address of the server where the COM+ API resides (WAS cluster node 1) along with the "method" name that will be called. The COM+ APIs are based on Microsoft.NET Framework SDK 1.1. Customization has been performed on the COMM/MSDTC part of WAS cluster node1 where the COM+ components are installed. Accoridng to cust. feedback the no of COM+ API calls per day is about 400 with increasing trend. - Scope of Cust. request : 1) Is it possible for Edge Load Balancer/Network Dispatcher to handle COM+ API calls (based on desciption provided)? As far as I know, LB/ND is capable of distributing session load based on TCP forwarding methods (MAC, NAT, CBR). 2) If LB/ND is not capable of handling COM+ API calls, is there an alternative mechanism? How we should configure LB/ND, considering that additional load on WAS cluster node1 caused by direct COM+ API calls? How about weight values? 3) Is it possible for routing COM+ API calls, directly to WAS cluster node1 where COM+ components are installed? If yes > How? P.S. Considering that we are in the middle of a major project in terms of services and revenue, any advise will be much appreciated. Nick Dakoronias (IBM ITS/ Greece)