Izenda reports may be deployed by integrating it directly into your application or on a separate standalone servers.  While the majority of integrations are directly embedded, it is is important to consider the standalone option for rapid deployments or situations where each tenant has an independent server or web site.

Embedded Integration

Methodology

• Copy Starter Kit Into “Reporting” folder of application
• Use PostLogin() method to map user security

Advantages

• A single, seamless deployment process for all application functionality
• Better load balancing and performance across your entire infrastructure
• Redundancy from being on multiple servers
• Deep integration with multi-tenant, multi-role multi-user security models
• Simple XCOPY deployment
• Becomes a part of standard source control
• Easy coordination between developers
• Leverage existing security and compliance controls
• Seamless user experience when navigating between application pages and reports
• Supports easy publishing from dev, test or staging to production envionrments.
• High performance transitions between reporting and application content

Disadvantages

• Must me coordinated with the release cycle of other code
• May require recompiling or republishing web application

Stand-Alone Integration

Methodology

• Install starter kit on independent server
• Send secure user identifier on query string for single sign on or setup secondary login page
• Look up user information from database inside PostLogin() method based on secure user identifer

Advantages

• Can be deployed independent of a release cycle
• Does not require recompiling or republishing base application

Disadvantages

• Requires more code to integrate user security
• May feel like a separate application to the user
• Requires independent load balancing and redundancy
• An additional web site and server to maintain
• Additional windows licensing and hardware costs

{ 0 comments }