RM625ENT Installation Instructions

From RiskWiki
Jump to: navigation, search


BPC Risk Manager (TM) is a governance productivity tool used to help organisations capture and organise risks, compliance obligations, incidents, hazards, insurance, process workflow, corporate objectives and monitor actions, controls and performance for risk management across an enterprise. Now in Version 6 (Enrima), BPC RiskManager has been the flagship product of Bishop Phillips Consulting Pty Ltd, since 1996 and is sold and supported world-wide by Bishop Phillips Consulting through our world-wide offices.

BPC Risk Manager Enterprise is a multi user intranet/internet product. It requires a database server and can optionally use a web server for some component delivery. It may be installed in both a single-user configuration on (with all components on the onel PC or Laptop) or in an enterprise/multi-user configuration on a corporate or Government network. It will easilly support an organisation with 70,000+ employees, or an organisation with 2 employees.

This document is a very detailed guide to installing Risk Manager Enterprise – Enrima ADO Edition. Please read accompanying document [RiskManagerEnterprise_ SystemsRequirements] to ensure your environment satisfies the minimum requirements for this product. Please contact Bishop Phillips before proceeding if these requirements are not met.

IN THESE INSTRUCTIONS…“[RMInstallDir]” refers to the directory in which the BPC RiskManager system was installed. This will generally be something like:

“c:\program files\BishopPhillips\BPCRiskManager0625\”

Beginning with version 6.2.5 there is a new fully automated installer which looks after practically everything for you. You will need to install the Windows operating system with IE 6/7/8 (which is most likely already installed), IIS 5/6/7 as appropriate if using any of the IIS dependent parts (eg. ActiveX plugin, BPC HTTPSrvr or BPC SurveyManager), the database engine SQL 2000 / SQL 2005 / SQL 2008 / SQL 2005 Express / SQL 2008 Express, and MS Office (2000/XP/2003/2007) if you intend to use office integration support. The instructions in this wiki will tell you how to do all this (except for installing Windows itself). The automated installer will do everything else for you:

  • Install the application server
  • Install the client
  • Create 1 or more databases
  • Upgrade databases from earlier versions
  • Enable importation of any supplied preconfigured databases
  • Register all components
  • Build any web sites requested
  • Launch the client and start the rapid configuration wizard

If you are using the enterprise version (as opposed to the single user version), the installer has multiple modes to support installation of different parts on different computers. For those that really want to do everything manually, these instructions supply a very detailed step by step guide to all of the installation tasks.


In these instructions we will assume the following terminology:

  • DataBase Server Computer– this is the computer on which the database server software is installed. It may or may not be the same computer as the Application Server Computer.
  • Application Server Computer – this is the computer on which you will be installing and running BPC RiskManager DataServer (i.e. the BPC RiskManager Application Server – known as the RM DataServer). It may or may not be the same as the Database Server Computer.
  • Web Server Computer – this is the computer on which you will be running the web server components (i.e. MS IIS). Except in rare scenarios it will be the same as the Application Server computer.
  • Client computer – these are the computers on which you will be running the BPC RiskManager client software (i.e. this is what most people would understand to be BPC RiskManager – but of course, it is only the front end of it.)

BPC RiskManager Installation Guide

Before You Install - Deciding the configuration

Order of Installation

  1. Install your MS Database Server (MSDE 2000, SQL Server 2000, SQL Express 2005 or SQL Server 2005) on the Database Server Computer.
  2. Backup all Risk databases (if performing an upgrade)
  3. Uninstall prior version of Risk Manager Enterprise (if performing an upgrade)
  4. (OPTIONAL) Install MS IIS 5 (IIS 6+ is preferred) on the Web Server Computer
  5. (OPTIONAL) Install MS SMTP Services or other SMTP services software on the EMail Server Computer or get the SMTP server connection details for later use.
  6. (OPTIONAL) Configure the SMTP services software on the EMail Server Computer.
  7. Install Risk Manager from CD or Downloaded install set, on the Application Server Computer.
  8. (OPTIONAL) Install Database Connectivity Tools on the Application Server Computer
  9. Install or Upgrade the Risk Database (on the Database Server Computer)
  10. Install Socket Server as a Service And HTTPSrvr as an ISAPI library
  11. Configure the BPC RiskManager & BPC SurveyManager Application Server

Adding an Extra Database or Restoring A Database

BPC RiskManager can access as many databases as you like. Essentially, adding a database is largely a matter of attaching a database or restoring a database backup. The only real issue to which you should pay attention is the access / login id used by the application server or BPC SurveyManager library to access the database.

You can find instructions for setting up a new database here:

You will probabluy also need to establish the local configuration options for the risk manager application server and survey manager library to be able to access the database and connect the database to your network environment (such as mail servers, web sites, etc). You can find instructions for these aspects here:

Migrating RiskManager from Test or Dev to Production

We were recently requested to supply a short form guide to the process of migrating a test site installation into production. This is that guide:


BPC RiskManager Software Suite