Install RiskManager From CD or Downloaded Installer

From RiskWiki
Jump to: navigation, search

Introduction

The installation of Risk Manager Enterprise registers certain program components and sets up a programme menu on the machine on which it is run, but it is simple to perform the few key steps manually, and the folder structure is not critical to the installation and, finally, most components are self registering so you can install Risk Manager directly onto your application network server or install it to a local PC and then progressively move program components during the installation.


We recommend, however (to make your life easier) that you install BPC RiskManager on the target application server (or if you are using multiple application servers, the machine you will be notionally treating as the primary “home” of the application server).


In earlier versions of BPC RiskManager the Enterprise installer did less work than this release. With the advent of Vista it became necessary that the installer application performs most of the administration level tasks so in this release we have assumed the most common scenario.


To install in all versions of windows, simply run the “Setup.exe”. It will create a BishopPhillips menu in the Programs list that appears when you select the start button and a group of files in the “Program Files” directory that are the application files.


If you are installing under Vista or Windows 7, a number of the subsequent steps may require you to run an application “as administrator”. If the program in the instruction fails to run, right click on the icon in the folder and choose the “run as administrator” option on the relevant program. This only applies to setup and OS components. During normal usage the RiskManager client will always executed under normal user rights. The application server in configuration mode should normally be run "as administrator" from the start menu or desktop icon, by using the right mouse button-context menu and selecting "run as administrator" to start it rather than the normal single or double left mouse click.


The installer run in full/complete mode will leave you with a functioning BPC RiskManager installation and open the client to verify. In a single user environment this will generally be the end of the installation, but in an networked, enterprise or advanced single user configuration there are many more capabilities to be enabled after the installer completes. These are covered in other sections.


Installers

There are essentially 3 installers:

  1. Single user/desktop installer  : Install / upgrade the entire system on a single computer.
  2. Enterprise installer : Install / upgrade entire system on an a single application server or different components on separate machines.
  3. Client installer(s) : Contained within the Enteprise Installation is a separate installer deleivered as both an single exe and a MSI file that allows installation of the just the desktop client application for distribution of the installable client desktop component. All versions also include the ActiveX client component for opional browser based client component distribution and installation.


The Single User Installer

Run this in Full/Complete or repair mode.


Enterprise Installer

There are multiple modes available after starting the installer. Normally you will run this in Full/Complete.

  1. Full/Complete: This mode will install all components on to the application server, set up local or remote databases and local services, optionally upgrade existing databases, optionally import backup databases, install web components on the local IIS server and test the installation.
  2. Databases: This mode just installs the database components. Use only on a database server, and only if Full/Complete not used.
  3. Minimum: Just copies the components onto the server in the programme files directory and registers the libraries. Allows a full manual installation as documented in this wiki. Only advised in advanced scenarios. Full/Complete mode also copies all the components used in Minimum and completes the install. It does not exclude a manual install as well.
  4. Client: Just installs the client components on a target computer. It is probably easier to use one of the supplied client installers copied to your server during Full/Complete and Minimum install modes. These versions will only present the client install option.


BackLinks