Can anyone provide the business and/or technical reasons for why Crystal provides for support of multiple APS's, or why a site would want to maintain multiple APS's ?
I'm sure that the high availability paper mentioned above has good info in it, but for those not inclined to search it out, the two main reasons we run two APS machines (as a cluster) is:
1. Redundancy. If we lose a server to a hardware failure, our environment is still running.
2. Capacity. User sessions are split between the two APS machines allowing for more simultaneous users before seeing a slowdown. This is especially true if you are using custom CSP or SDK calls that do a lot of queries against the APS database (InfoStor) to get report IDs, names, Admin info, etc.
TimAetna, you write about APS clustering, which I assume is sharing one APS between multiple servers, which I assume is transparent to the user. My question has to do with 2 seperate APS's, not one clustered APS. What is the reason for support of multiple (not clustered) APS's.
Am I misunderstanding the ability to maintain two seperate APS's as opposed to clustering one APS ? When I logon to CE, I am asked to choose an APS.
We run two APS's.... one is a production server and one a development server.
Report Designers use the development server and we, the admin use it for testing changes to the application and the software environment (ie patches, DLL's, CSP, images, js etc).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.