Websphere Application Server (WAS) Siebel JCA
in our implementation of Siebel, Web Services are provided by a middleware infrastruture as follows:
- We generate the java classes for BS and IO's using Siebel Code Generator.
- Our middleware team creates and publishes the WSDL and implements in the WAS (Resource Adaptor for Siebel) using Connection Factory.
In the last two years there was a huge increase in the number of WebServices invoked, actually we have something like 1,5 million per working day.
We observe a strange behaviour, the WAS (high availability, 4 servers), has 80 concurrent connections available for front-ends invocations of Siebel Web Services, and has also 4 instances connecting to the EAI Object Manager (in 2 Servers)