Sun Microsystems Portal Server 6 - Manual (Page 72)

SRA Sizing
72 Portal Server 6 2005Q1 • Deployment Planning Guide
❍
Maintenance demands
Considering these factors enables you to develop a sizing figure that is flexible and
enables you to avoid risk when your assumptions regarding your portal change
following deployment.
The resulting figure ensures that your portal site has the following:
• Scalability high availability, reliability and high performance
• Room for whatever you want to provide
• Flexibility for adjusting to changes
Validate Your Final Figures
Use a trial deployment to verify that the portal deployment satisfies your business
and technical requirements.
SRA Sizing
Use this section only if your organization is implementing a secure portal by
installing SRA. As you did for portal, for SRA, you must first establish your
Gateway instances baseline sizing estimate (A single machine can have one
Gateway installation but multiple instances. SRA enables you to install multiple
Gateways, each running multiple instances.) Your design decisions help you make
accurate estimates regarding SRA user sessions and concurrency.
You must first establish your Gateway instances baseline sizing estimate. This
baseline figure represents what you must have to satisfy your Gateway user
sessions and concurrency needs.
Establishing an appropriate sizing estimate for your SRA deployment is an
iterative process. You might wish to change the inputs to generate a range of sizing
results. Test these results against your original requirements. You can avoid most
performance problems by formulating your requirements correctly and setting
realistic expectations of SRA performance.
This section explains the following types of performance factors that the Gateway
instances baseline sizing process involves:
• Identifying Gateway Key Performance Requirements
• Advanced Gateway Settings