Installing the OneStop Reporting Modules on Terminal Server

Transcription

1 Installing the OneStop Reporting Modules on Terminal Server Table of Contents 1 Introduction 2 Planning 3 Installation 4 Example 2010 OneStop Reporting support@onestopreporting.com Version 2.1 1

2 1. Introduction This document describes at a fairly high level what you should plan for ahead of an OneStop Reporting (OSR) installation on Terminal Server. It also describes the most important steps in the installation process. For more details about the installation we ask you to read the complete installation documentation Installing OneStop Reporting Products. It can be downloaded here: Reporting%20Products.pdf 2. Planning 2.1 Roles It is important to identify the different roles in the installation process. An organization that uses Terminal Server(s) as a platform for its ERP systems often has people with the following roles: - Customer/Users: Owns and uses the ERP system. We will refer to this group as Customer in the rest of this document. - ASP Provider/System & Network Administrator: This is typically an external partner of the customer or an internal resource at the customer that manages the servers and the network (IT systems). It is often the same resource that administers users and access rights for the organization. In the rest of this document, this role will be referred to as System Administrator. - ISV Partner/Reseller: The external partner that delivers installs and implements one or more dedicated ERP systems that they resell and that they deliver consulting services and support for. In the rest of this document, this role will be referred to as Reseller. There can be variations of the roles mentioned above and in some organizations, it could be the same person wearing many hats and managing both the IT systems and the ERP systems. 2.2 OneStop Reporting Modules The OneStop Reporting (OSR) modules offers different types of functionality and different users will often have different configurations and combinations of the OSR modules. It is therefore important that you decide the users configurations in advance so that all roles described above know which configuration is expected for each user. It is the customer (user) that that should be the source for this information, and the reseller should in advance provide the customer the information about the functionality of the different OSR modules so that the right product can be installed for the different end users. The following is a short description of the different OSR modules: - OneStop Report Composer: A Windows application with a connection to the OSR Repository and the ERP database. Start it from a shortcut in the Windows Start menu 2

3 - OneStop Report Player: An Excel COM add-in with a connection to the OSR Repository and the ERP database. Start indirectly (from OSR sidebar menu) in Excel when an OSR report (Excel file) is opened. So, there is NO shortcut in the Excel Start menu for this OSR module. - OneStop Report Designer: An Excel COM add-in with a connection to the OSR repository and the ERP database. Start from within Excel through its own Excel Ribbon menu. So, there is NO shortcut in the Excel Start menu for this OSR module Note: Normally, a user should never have both the Report Player and the Report Designer add-ins installed in their Excel application. This is important to note because both modules are so-called Excel COM add-ins and both will be installed as active COM add-ins in the Registry for all users with Excel when both products are installed on Terminal Server. OneStop Reporting Module Overview Microsoft Excel Microsoft Excel Report Designer Excel COM AddIn OSR Reports Excel file Report Player Excel COM AddIn OSR Report Composer Windows Application ERP Business System OSR Repository Microsoft SQL Server 2.3 Questions that should be answered prior to the installation 1. Who are doing the installation of the OSR modules? 2. Will the person that installs the OSR modules have administrator access to Terminal Server? 3. How is Terminal Server used in the organization? Is a logon script or other type of application in use that controls access rights to applications for the different user profiles? 4. In that case, who is the administrator for access rights to the applications? 5. Has the customer provided an overview of which end-users should have the different OSR modules, and has this been communicated to the person that will publish the profile information for this? 3

4 3. Installation The following bullet point lists the steps in the installation in the required order and it suggests the person/role to do this according to the descriptions in Chapter Download the installation package from Click on the link Complete installation package for Terminal Server deployment. Unzip the files and install the pre-requisites according to Chapter 5.1 in the installation guide. 2. Terminal Server must be configured to allow installation of MSI packages. See Chapter in the installation guide. 3. After getting administrator access to Terminal Server, install OneStop R Composer first if it is part of the modules to be installed. If not, then start with the OSR Designer. Note: Normally you should install For all users by putting the server in installation mode. This should not be done by using the earlier Windows 2000 Server method Change User, but rather through Add/Remove Programs (Windows 2003 Server) or Install Program (Windows 2008). Both choices are available through the Windows Control Panel. 4. During the installation you will go through the Repository Setup Wizard to install the OSR Repository and enter license keys (see detailed description in the installation manual). If you don t have a license key on hand, leave the fields empty. They can be entered later. Regardless, you have a trial period of 30 days before the license keys must be entered. 5. Now install the OSR Designer (if not already done in Step 3), and the OSR Player. As mentioned earlier are these modules Excel COM add-ins and will not be visible in the Start menu in Windows as shortcuts. See Chapter and in the installation manual for detailed information about registration keys. 6. The next step is to configure which end-users should have which OSR module. This should be clarified with the customer so that the person/role that administers the logon-script or other publishing tools that can program the right settings for the different end-users. See the installation manual for more detail, but here is a short overview of the keys in registry that are used by the different modules: All OSR modules: HKEY_CURRENT_USER\Software\OneStop Reporting\Settings OSR Composer: Start menu shortcut OSR Designer: HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\OneStop.ReportDesigner OSR Player: HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\OneStop.ReportPlayer.Excel2007 4

5 For Excel 2003 respectively: HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\OneStop.ReportPlayer.Excel2003 For OSR Player and OSR Designer you have the following values to Enable/Disable Excel COM Add-ins: LoadBehavior: 3 = Enabled, 2 = Disabled If you don t run any logon-script or other type of profile publishing, as a default, the users will get access to all programs that have been installed in Installation modus. In this case the user will also get a question about which of these two modules (OSR Designer or OSR Composer) that should be used. This happens with first time usage of Excel after the installation. The answer supplied by the user will then adjust the setting in the Registry for the user. Be aware that a logon scripts can override this setting the next time the user logs on. There is also a tool available that export the Registry settings to a.reg file that can be the basis for editing the logon script, etc. See Chapter in the installation manual. 4. Example Here is an example that shows short-cut and Registry settings for three different end-users with the following OSR modules: - John: OSR Composer & OSR Designer - Sarah: OSR Composer & OSR Player Jane: OSR Player 2007 Short-cut and Registry settings for John: Short-cut to the Composer: Registry settings for OSR Designer: 5

6 HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\OneStop.ReportDesigner: Short-cut and Registry settings for Sarah: Short-cut to Composer: Registry settings for OSR Player: HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\OneStop.Player2007: Short-cut and Registry settings for Jane: Registry settings for the OSR Player: 6

7 HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\OneStop.Player2007: 7