Splitting the SOAP into different POA

Splitting the SOAP into different POA

Creating a separate POA for SOAP only

Splitting the SOAP into different POA will not work for applications where POA needs to notify or SLAP the SOAP Applications about changes in the user database. These notifications are important because they let the SOAP Application know that there is a change in the user database and application needs to come to the POA and get the change. Without these notifications, changes in the user database will not be notified to the SOAP Application immediately and will cause delay of messages/appointments etc to reach the SOAP Application. Most of the SOAP Applications have a time interval after which it will automatically connect to the POA looking for changes. Eventually the message/appointments will reach the SOAP Application after a period of time as the SOAP Applications connects to the POA looking for changes.  These applications include GroupWise Mobile Server, Blackberry Enterprise Server, Mobility etc.

 

There are other applications like Archiving applications that may not require any notification from POA as these applications scan the POA during a certain period of time to Archive the messages.

 

Splitting the POA is good for such applications that do not require notifications from the POA. Notification list is stored in the memory of the POA and if the POA has been split, one POA cannot access the other POA's memory to check the notification list.