1 Logi Ad Hoc Reporting Configuration for Load Balancing (Sticky Sessions) Version 10 Last Updated: December 2010
2 Page 2 Table of Contents About This Paper... 3 What Are Sticky Sessions?... 3 Configuration... 4 Contact Us... 7
3 Page 3 About This Paper This paper outlines most of the Ad Hoc configuration considerations for load balancing in sticky session and non-sticky session configurations. The paper does not cover other aspects of load balancing configuration or Ad Hoc configuration. What Are Sticky Sessions? In a load balanced environment, there are essentially two configuration models regarding the processing of requests; sticky sessions (also referred to a session affinity ) and non-sticky sessions. In the sticky session configuration, the session is established and a server is assigned to process all of the requests for the life of the session. From Microsoft: The request forwarder filter is an ISAPI filter that monitors incoming requests and decides whether to allow requests to pass through and be executed locally or forward the request to another server, and if it must forward the request, it does the necessary preparatory work. It also gives out and interprets routing cookies, which allow for session coherency (sticky sessions) where a client is attached (stuck) to a single server for the lifetime of its browser session. In the non-sticky configuration, each request is independent of previous requests and may be routed to any of the servers in the server pool for processing. From an Ad Hoc configuration point of view, little has to be done to accommodate the sticky session. Each session behaves much like a standalone web application. For the non-sticky environment, the primary considerations are the management of session state and centralizing the location of the data cache repository.
4 Page 4 Configuration Background and Definitions An ASP.NET session is defined as the period of time a unique user interacts with a particular web application. HTTP is a stateless protocol, in the sense that a Web server is concerned only with the current HTTP request for any given Web page. The server retains no knowledge of previous requests. The stateless nature of HTTP requests presents unique challenges when writing Web applications. ASP.NET applications that require session state to be maintained use session management techniques. ASP.NET offers three options for the management of session state: Session state is stored locally on the web server and is managed in InProc the same worker process as the ASP.NET application. Session state is managed by ASP.NET state service, which runs outside of the ASP.NET worker process. The service can run local to StateServer the web server to support web gardens or on a different server to support web farms. Session state is managed outside of the ASP.NET worker process SQLServer and is stored in a SQL Server database. Like the StateServer option, this method can support web gardens and web farms. Note: There may be other configuration considerations other than load balancing affecting the session state management decision. Management of Session State for Sticky/Non-Sticky Configurations Typically, by default, the web server is configured to manage session information as InProc. In both standalone and load balanced, sticky environments this setting allows a single server to manage the session information for the life of the session. For non-sticky, load balanced configurations the session state needs to be centrally managed. Since requests can be processed by any of the servers in the pool, the servers need to access the state information for the session from a common location. Either the StateServer or SQLServer session state management options may be configured to meet the goal of centralizing the session state information management.
5 Page 5 Configuration of the session state options is found under the ASP.NET configuration dialog in IIS management. The details of configuring the session state options are outside the scope of this paper. Centralizing Data Cache for Non-Sticky Configurations The data cache repository is, by default, the rddatacache folder in the Ad Hoc instance. In a standalone or sticky environment where all the requests are processed by the same server, the default cache configuration is sufficient. In a non-sticky environment, centralizing the data cache repository is required. In the _Definitions/_Settings.lgx file of each instance, there is a <General> element with a DataCacheLocation attribute. By default this is set to which identifies the path to the cache folder. Replace this attribute value with the path to a central data cache location in each _Settings.lgx file on each instance serving the Ad Hoc application. The _Settings.lgx file is an XML file that may be edited with any plain-text editor, such as Notepad. If you also have Logi Info Studio product, you can use the Studio to open your Logi Ad Hoc application and edit the settings file. General Load Balancing Configuration Ad Hoc Instances the Ad Hoc instances must be structurally replicated across all servers in the server pool. This includes any custom files, stylesheets, themes, etc. Metadata Database in a load balanced environment, all instances must be directed to a single metadata database. Using the Management Console, for each Ad Hoc instance click on the Instance Configuration / Metadata Connection to set and test the connection string to the metadata database. Report Repository a central repository for the report definition files is necessary in a load balanced environment. To set the report repository for each Ad Hoc instance, use the Management Console and click on Instance Configuration / Application Settings / Reporting Options. Dashboard Preferences centralizing the repository for the dashboard preference files is necessary in a load balanced environment. To set the dashboard preferences repository for each Ad Hoc instance, use the Management Console and click on Instance Configuration / Application Settings / Reporting Options.
6 Scheduling the Logi Ad Hoc Scheduler service must be used in a load balanced environment. Using the Management Console, for each Ad Hoc instance click on Instance Configuration / Scheduling and select the Logi Scheduling Service. Provide the Server, Password, and Port Number to the same scheduler service. Page 6 Archiving a centralized location for archived reports is necessary in a load balanced environment. Using the Management Console, for each Ad Hoc instance click on Instance Configuration / Archiving and set the archive folder and URL for the archive repository. Note: Consult the Management Console Usage Guide for additional information regarding the above configuration options. Licensing an appropriate license file (number of cpu s) must be placed in the root folder of each active server in the load balanced environment. SecureKey Security If the SecureKey authentication method is used, the requests are managed in Application scope and the "SecureKey Shared Folder" option must be configured in a load balanced environment. In the _Settings.lgx file is a <Security> element. If the AuthenticationSource attribute is set to SecureKey, add the SecureKeySharedFolder attribute and set the value to a network path (e.g. //mysharedserver/securekeyfolder ) This must be added to the _Settings.lgx file for all Ad Hoc instances. From our documentation: Used only when AuthenticationSource="SecureKey", SecureKeySharedFolder allows SecureKey to work in clustered configuration with web farms and web gardens. In a single-server configuration, SecureKey keeps SecureKey requests in Application state. With multiple servers, this information must be stored in files in this folder that is shared among the web servers. The account used by (or impersonated by) the web application must have network access rights to read, write and delete files from this folder. Old files in the SecureKeyFolder are automatically deleted over time, so do not use this folder to store other files.
7 Page 7 Contact Us For more information about other Logi Analytics products or assistance beyond this user manual, please contact Logi Analytics in the following ways: Corporate Headquarters Phone: (703) Fax: (703) Address: Web Site: 7900 Westpark Drive, Suite A200 McLean, VA Sales Department Phone: (703) Customer Support Phone: (703) Link:
Logi Ad Hoc Reporting Troubleshooting Scheduling Failure Version 10 Last Updated: April 2011 General Configuration Overview The execution and delivery of scheduled reports is one of the more complicated
NEFSIS TRAINING SERIES Nefsis Dedicated Server version 5.2.0.XXX (DRAFT Document) Requirements and Implementation Guide (Rev5-113009) REQUIREMENTS AND INSTALLATION OF THE NEFSIS DEDICATED SERVER Nefsis
SilkCentral Administration Module 2010 Help Borland Software Corporation 4 Hutton Centre Dr., Suite 900 Santa Ana, CA 92707 Copyright 2009-2010 Micro Focus (IP) Limited. All Rights Reserved. SilkCentral
SAS 9.4 Intelligence Platform Middle-Tier Administration Guide Third Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS 9.4 Intelligence
Software used by portions of this application require the following license statement: [The BSD License] Copyright (c) 2004-2011 Jaroslaw Kowalski email@example.com All rights reserved. Redistribution
SilkCentral Administration Module 2009 SP1 Help Borland Software Corporation 4 Hutton Centre Dr., Suite 900 Santa Ana, CA 92707 Copyright 2009 Micro Focus (IP) Limited. All Rights Reserved. SilkCentral
FileMaker Server 12 FileMaker Server Help 2010-2012 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc.
FileMaker Server 13 FileMaker Server Help 2010-2013 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker,
Ipswitch WhatsUp Professional and Premium Edition 2006 User s Guide Software Version 2 Ipswitch, Inc Ipswitch Inc. Web: HTTP://www.ipswitch.com 10 Maguire Rd, Suite 220 Phone: 781.676.5700 Lexington, MA
E-mail Filter SurfControl E-mail Filter 5.0 for SMTP Getting Started Guide www.surfcontrol.com The World s #1 Web & E-mail Filtering Company CONTENTS CONTENTS INTRODUCTION About This Document...2 Product
Evaluation Guide Powerful & Immediate Business Web Security via the Cloud Contents 1 Introduction & Product highlights 2 Set up & Configuration 3 Managing your WebTitan Cloud Service 4 Reporting 5 Support
GFI Product Guide Administrator Guide The information and content in this document is provided for informational purposes only and is provided "as is" with no warranty of any kind, either express or implied,
ISA Server Plugins Setup Guide Secure Web (Webwasher) Version 1.3 Copyright 2008 Secure Computing Corporation. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed,
Cloud Services for Backup Exec Planning and Deployment Guide Chapter 1 Introducing Cloud Services for Backup Exec This chapter includes the following topics: About Cloud Services for Backup Exec Security
COMvantage Solutions Presents: Version 3.x Cloud based Document Management Guide to Setting up Docs2Manage using Cloud Services Docs2Manage Support: Email: firstname.lastname@example.org Phone: +1.847.690.9900
Administration GUIDE Exchange Database idataagent Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 233 User Guide - Exchange Database idataagent Table of Contents Overview Introduction Key Features
Configuration Guide BES12 Version 12.1 Published: 2015-04-22 SWD-20150422113638568 Contents Introduction... 7 About this guide...7 What is BES12?...7 Key features of BES12... 8 Product documentation...
Richmond SupportDesk Web Reports Module For Richmond SupportDesk v6.72 User Guide Contents 1 Introduction... 4 2 Requirements... 5 3 Important Note for Customers Upgrading... 5 4 Installing the Web Reports
Web Application Hosting Cloud Architecture Executive Overview This paper describes vendor neutral best practices for hosting web applications using cloud computing. The architectural elements described
Journyx Technical Document System Administration and Disaster Recovery Guide For Journyx Timesheet version 8.7m5 Document Version: 3.0.9 (January 2012) for version 8.7m5 For product versions prior to 8.7m5
SAS 9.3 Intelligence Platform Application Server Administration Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2011. SAS SAS 9.3 Intelligence
Sugar Community Edition User Guide Version 5.2 Copyright Information Version 5.2, 2008 Copyright 2004-2008 SugarCRM Inc. www.sugarcrm.com This document is subject to change without notice 1. License This