Installation Guides › Implementation Guide › Capacity Planning › Capacity Planning Introduced

Capacity Planning Introduced

Planning a SOA Security Manager deployment with performance in mind is the first step to maintaining high enterprise availability and performance standards. A good approach is to estimate the number of expected requests SOA Security Manager must handle per web service. The following are the most significant factors that influence SOA Security Manager performance:

• Sustained request rates. The rate at which web service clients send requests to protected web service resources fluctuates throughout your business day. Some periods can generate relatively few requests, and therefore require relatively few authentications and authorizations, while others generate more. The sustained request rates represent a sustained period during which SOA Security Manager must service an average number of authentication and authorization requests.

  Note: Each web service request triggers one authentication and one authorization event.

• Peak request rates. During sustained periods of activity, web service client activity may spike. The peak request rates represent a period during which SOA Security Manager must service the highest number of authentication and authorization requests.

The following graphic illustrates how request rates fluctuate throughout the day, are sustained for a specific period, and peak within that period:

Note: Authenticating and authorizing requests results in a number of reads from a user store. Determining sustained and peak rates helps you determine the load under which your user stores must operate to service Policy Server requests.

More information:

Performance Tuning Introduced