When serving both APSV and WEB/REST/SOAP clients from a single PASOE instance, that APSV requires the use of sticky sessions, which is why it is recommended to have one webapp to handle APSV traffic only and another for the other clients.
Having one ABL application on an instance, means there will be one set of agents/sessions and two webapps: one for ASPV only and the other for the WEB/REST/SOAP transports.
Since webapps provide part of the URL, a load balancer can be configured to route traffic differently for each webapp (and so client sessions).
- When sticky sessions are not used when using a load balancer, anything that binds the server to the client (eg running persistent procedures) are likely to break. This is because the client makes a couple/three requests when running things persistently and these requests all need to go to the same sessions.
- If stateful clients are emulated by setting the SESSIONSERVER-CONNECTION-BOUND-REQUEST attribute all requests (by definition) also need to go to the same ABL sessions.
