MEGA Advisor Administration MEGA 2009 SP5 EN

Size: px

Start display at page:

Download "MEGA Advisor Administration MEGA 2009 SP5 EN"

Dylan Barber
5 years ago
Views:

1 MEGA Advisor Administration MEGA 2009 SP5 EN Revised: April 5, 2012 Created: May 2, 2011 SME: Sylvie CHABE / Olivier SCHARFF Author: Herveline GLEVER

2 CONTENTS Introduction... 3 Audience... 3 How this document is organized... 3 Improving MEGA Advisor first connection response time... 4 Timeout configuration... 4 Configuring IIS Application Pool timeout... 4 Configuring Advisor ASP.NET Session State timeout... 5 Configuring Advisor session timeout... 6 Preload profiles configuration... 7 Configuring the KeepAlive value... 7 Configuring the Preload profiles... 7 Administration page... 8 Preload planning... 9 Managing MEGA Advisor Administration Console Opening the MEGA Advisor Administration Console MEGA Environments Web Users Connected Active Profiles Active Profiles Statistics MEGA Process Information Links to Check MEGA Statistics link MEGA System Information link Client-Side Diagnosis link Requesting the log file MEGA Advisor Administration MEGA 2009 SP5 EN page 2/15

3 INTRODUCTION Audience This document is intended for the MEGA administrator or the physical server administrator. How this document is organized This document details the following information: MEGA Advisor first connection response time improvement, which details actions to be performed before using Advisor application. When performed these actions enable to have an optimized connection time to the Advisor application. MEGA Advisor administration console, which enables Administrators to perform basic administration tasks. These tasks include web user connection management and cache management. MEGA Advisor Administration MEGA 2009 SP5 EN page 3/15

4 IMPROVING MEGA ADVISOR FIRST CONNECTION RESPONSE TIME At the first Advisor connection, four processes are launched. By default, these processes are stopped, without requests, after 20 minutes of idle time. The time spent to launch these processes slow down the connection to Advisor. To optimize the first connection time to the application you can configure IIS and the application to preload required processes and prevent them to stop. To start with MEGA Advisor in optimized conditions, you must: Configure IIS and application timeout, the time with no activity before stopping mgwmwas. Configure Advisor to preload the Mega Sub Process needed for each mega profiles. Plan the preload using Windows Scheduler. Timeout configuration The default timeout configuration is 20 minutes. To prevent the mgwmwas process to shut down during a day, modify the default timeout to 12 or 24 hours. Configuring IIS Application Pool timeout From IIS: 1. In the left pane, from the tree view select Application Pools. 2. In the right pane, right-click ADVISOR application and select Advanced Settings. 3. From the Advanced Settings window, in the Process Model part, modify the Idle Time-out (minutes) value. MEGA Advisor Administration MEGA 2009 SP5 EN page 4/15

Configuring Advisor ASP.NET Session State timeout From IIS: 1. From the left pane, expend the Sites tree view and select the Advisor Application. 2. In the right pane, open the ASP.

5 Configuring Advisor ASP.NET Session State timeout From IIS: 1. From the left pane, expend the Sites tree view and select the Advisor Application. 2. In the right pane, open the ASP.NET Session State feature. 3. Modify the Time-out (in minutes) value. 4. In the Actions pane, click Apply to validate your modifications MEGA Advisor Administration MEGA 2009 SP5 EN page 5/15

6 Configuring Advisor session timeout From the root folder of the Advisor deployment path: In the Web.Config file, update the OpenSessionTimeout value. This value is given in milliseconds. <add key="opensessiontimeout" value=" "/>  MEGA Advisor Administration MEGA 2009 SP5 EN page 6/15

7 Preload profiles configuration Configuring the KeepAlive value By default a Mega Profile remains connected, and its associate Mega Sub Process alive, even when the last user using the profile has gone. The configuration parameter that controls this behavior is located in the Web.Config file. Make sure you have the following line in your Web.Config file: <add key="keepalive" value="1"/>  Configuring the Preload profiles Configuring the preload profiles consists of code instructions to open session for a user for each profile to preload and instructions to discard each preloaded environments. 1. From the App_Code folder, open the preload.cs file. 2. Modify the Preload method according to the following model: <environment Path> must be replaced by the environment path with duplicate backslash. static public bool PreLoad(MEGAWebAccessLib.MegaWebAccessServerClass pmwa, settings psettings, int nlevel, bool bdiscarding) { bool bpreloading = true; if (bdiscarding && (nlevel == 1)) { pmwa.discard(1, "<environment_1 path>"); pmwa.discard(1, "<environment_n path>"); } string[] sdiagramarray = new string[<nd - number of diagram type to preload>]; ---- sdiagramarray[0] = "<hexaidabs of a diagram for the first diagram type>"; sdiagramarray[<nd-1>] = "<hexaidabs of a diagram for the last diagram type>"; switch (nlevel) MEGA Advisor Administration MEGA 2009 SP5 EN page 7/15

8 { } case 1: PreLoadProfil(pMWA, psettings, psettings.settings_language_<language Name>, "<mapped user>", "<password>", "<environment path>", "<base name>", sdiagramarray); break; case <n>: PreLoadProfil(pMWA, psettings, psettings.settings_language_<language Name>, "<mapped user>", "<password>", "<environment path>", "<base name>", sdiagramarray); break; default: bpreloading = false; break; } return bpreloading; Administration page The administration page in the admin folder calls the Preload method when resetting cache with false for bdiscarding. Then only the selected environment will be discarded. Otherwise to start the preload call the administration page with preload parameter set to 1 (see Preload planning). MEGA Advisor Administration MEGA 2009 SP5 EN page 8/15

9 Preload planning You can plan the preload to have profiles loaded before the first user connection. From the Windows Scheduler: 1. Create a new task. 2. Configure the trigger. Ex.: everyday at 6 AM. 3. Configure the action: a. Select Start a program. b. In the Parameters pane, Browse the mwsr.exe program (located in the Utilities\MEGA ldap folder). c. In the argument field set URL of the administration page with preload parameter set to 1, for instance : " The preload start discarding environment which reset cache. MEGA Advisor Administration MEGA 2009 SP5 EN page 9/15

MANAGING MEGA ADVISOR ADMINISTRATION CONSOLE The administration console of MEGA Advisor has been provided to enable Administrators to perform basic administration tasks.

10 MANAGING MEGA ADVISOR ADMINISTRATION CONSOLE The administration console of MEGA Advisor has been provided to enable Administrators to perform basic administration tasks. These tasks include web user connection management and cache management. The MEGA Advisor Administration console enables to: manage web user connections manage caches check the application performances on the client s end Opening the MEGA Advisor Administration Console To access the MEGA Advisor Administration console: Type /admin/ after the server address. Example: The Administration Console appears. The Administration Console includes the following tables: MEGA Environments: lists the environments accessible from MEGA Advisor Web Users Connected: relates to the web users logged in to MEGA Advisor Active Profiles: displays information regarding the MEGA profile used to log in to MEGA Advisor Active Profiles Statistics: displays statistical information regarding the MEGA profiles used to log in to MEGA Advisor MEGA Process Information: relates to the processes involved in the connection Links to Check: relates to the generation of reports which displays information regarding the operating system and its response times. MEGA Environments The MEGA Environments table details for each environment that can be accessed from MEGA Advisor, its access path. MEGA Advisor Administration MEGA 2009 SP5 EN page 10/15

MEGA Advisor operates with a cache system to avoid regenerating Web pages with unchanged content. To delete this cache, click Reset Cache. The cache is deleted only if the repository has been updated.

11 MEGA Advisor operates with a cache system to avoid regenerating Web pages with unchanged content. To delete this cache, click Reset Cache. The cache is deleted only if the repository has been updated. When you click Reset cache, read-only sessions that are open in MEGA Advisor are closed momentarily. They are then reopened to take into account the dispatches of other users. It is recommended that you warn users that are still connected (see Web Users Connected) that there will be inopportune disconnections. Web Users Connected Web users are required to log in to MEGA Advisor: These Web users are mapped to MEGA users. Several Web users can be mapped to a single MEGA user. Upon login, a session is opened in MEGA Web Access. This session is assigned an ID by MEGA Web Access. Each Web user has his own session identifier even if he shares his MEGA user with other Web users. The Web Users Connected table displays for each Web user logged in to MEGA Advisor: the Web user Session Id. This ID number enables to identify the Web user activity via the MEGA Web Access log. the TimeOut Status of the Web user session, which can take the following values: o TimeOutISPending: indicates that user activity has ceased and that the session will soon expire. You can disconnect the session if you so desire. o OK: indicates that the Web user session is being used. o TimeOut: indicates that the session has expired. the MEGA User (profile) used to log in to MEGA Advisor. This profile can be configured from the mapping tool and is used to define a particular view of the repository. The Language in which MEGA Advisor is displayed. The Environment and repository (Database) on which the Web user works. The ID (Run Id) of the MEGA process used for the current Web user. Click the corresponding button to perform the following actions: Disconnect: enables to delete the session of the selected Web users, logging them out of MEGA Advisor. This option should be used when problems occur, when requested by a technical support engineer, or when you delete the cache. MEGA Advisor Administration MEGA 2009 SP5 EN page 11/15

12 Dump Cache: by default, MEGA WEB Access stores all data generated from MEGA in a cache. Dump Cache enables to write the content of the cache to the disk, in the folder where the cache is stored. It should only be used when requested by a technical support engineer. Disconnect Timeout Sessions: enables to delete all Web user sessions that are identified as expired (timed out). Refresh Mapping: if the mapping tool used to map Web users to MEGA profiles (MEGA Users) has been updated, Refresh Mapping enables to ensure that future connections take the update into account. Active Profiles Active Profiles table displays information about the MEGA profiles that are used and shared between the Web users. The sharing or mapping is managed in the Web Users Mapping tool. A profile corresponds to a connection to the MEGA repository. It represents: the combination of the MEGA user used to log in to MEGA, the selected language of the user, and the environment and repository to which the user is connected. Each profile offers a particular view of the repository. Several Web users share the same profile for connecting to the repository. Profile use makes it easier to manage MEGA user configurations (options, permissions, license). The Active Profiles table displays the following information for each active profile: Run Id: the MEGA process ID used for the current Web user. MEGA User: the MEGA user used to log in to MEGA. Language: the language selected by the user. Environment: the environment in which the user works Database: the repository to which the user is logged and in which his work is stored. File Tag: the ID attached to the MEGA user work file. Cache Path: the cache storage location for the given profile. MEGA Advisor Administration MEGA 2009 SP5 EN page 12/15

13 Active Profiles Statistics The Active Profiles Statistics table summarizes information about the pages requested by each active profile, and the pages generated: Number of Pages Queried: indicates the MEGA Web Access number of pages requested. Queried Pages time: indicates the time spent requesting MEGA Web Access pages. Number of Pages Generated: the number of pages requested and generated for a given profile, as they were not present in the cache. Generated Pages Time (ms): the time in which the requested pages, which are not in the cache, are generated. Collisions: the number of pages requested simultaneously by different users. This can be a report element in the event of a generation error. Concurrent: the maximum number of pages generated simultaneously per profile. This indicates if a particular profile is often requested. With the generated page number and the generated page time you can find out the average time for generating a response. MEGA Process Information Each time a new session is opened in MEGA a new MEGA process is launched. There are as many processes as there are active profiles. A process ID is associated to each active profile. This ID is used to identify the process on which there is an impact in the Windows Task Manager. The process ID is 5b8 (hexadecimal), which corresponds to the mgwspro 1464 process. The MEGA Process Information table displays the following information: Run ID / Process ID: indicates the MEGA process IDs for the current user and active profile Computer Name / IP: indicates the machine on which the process is launched MEGA Version: the version of MEGA that is launched MEGA Advisor Administration MEGA 2009 SP5 EN page 13/15

14 MEGA Paths: indicates the installation path of the MEGA version being used and the error file location. Access to the error file is dependent on the types of Web servers used. A MEGA Technical Support engineer may request this file if problems arise. Links to Check The Links to check table includes links that generate reports relating to the installation used and the profiles connected to MEGA Advisor. MEGA Statistics link The MEGA Statistics link generates an XML report that contains technical statistic data regarding MEGA Advisor requests. MEGA System Information link The MEGA System Information link generates an HTML report that contains technical information regarding the installation that can render error diagnostics easier. The generated report can help you find the reasons for delays in response time from the application. Use the MEGA System Information link: to check the application performances on the client s end when browsing on MEGA Advisor is slow, and send the page information to the Technical Support. for information on product licenses available for the active profiles, and user activity when the report is requested by a technical support engineer Client-Side Diagnosis link The Client-Side Diagnosis generates a report that facilitates making diagnostics on the Web client. MEGA Advisor Administration MEGA 2009 SP5 EN page 14/15

15 Requesting the log file If you want to create a log file of all the page requests made by the active profiles, click Log Requests. Do not perform this action unless extremely necessary as this file is only for debugging purposes. The log file is stored in the website directory on the server used. MEGA Advisor Administration MEGA 2009 SP5 EN page 15/15

User Manual. Admin Report Kit for IIS 7 (ARKIIS)

User Manual. Admin Report Kit for IIS 7 (ARKIIS) User Manual Admin Report Kit for IIS 7 (ARKIIS) Table of Contents 1 Admin Report Kit for IIS 7... 1 1.1 About ARKIIS... 1 1.2 Who can Use ARKIIS?... 1 1.3 System requirements... 2 1.4 Technical Support...