MAPS 2.5 Recommended and Supported Configuration (226337)

SUMMARY

This article provides recommendations on how to achieve optimal performance in a data center with MCIS Administration and Provisioning Service (MAPS) 2.5.

The following recommendations represent best results obtained from performance testing and are the supported methods:

• TranDB must be on a separate SQL Server than the Membership database SQL Server. TranDB can be local with the MAPS server for an additional performance gain.
• Have TranDB reside on Microsoft SQL Server 7.0. Even though SQL Server 6.5 will work with MAPS 2.5, our testing to achieve 45 sign-ups per minute was performed with SQL Server 7.0.
• If you implement personal web pages (PWP) and generate heavy PWP traffic, create virtual directories on the MAPS server pointing to the PWP filestores. In the MAPS configuration for PWP, the top text box (Web Server) should point to the MAPS server and the second box (Virtual Server) should point to the virtual server instance on the MAPS server. This will allow MAPS to read vdir information from the MAPS server instead of a busy PWP server. In the MAPS PWP configuration, the third (Web Server DNS Name) and 4th (FTP Server DNS Name) entries should still point to the real PWP server. This optimizes MAPS looking up the virtual directories during user creation. During load on PWP system, this will help speed up MAPS.
• There is a stored procedure called purgetrans. This should be run on a scheduled basis in SQL Server to clean up TranDB. If the Transaction Database becomes too large, MAPS performance will suffer and possibly fail in extreme situations. When following these recommendations, MAPS has been tested to complete 45 sign-ups per minute.