BPC RiskManager Quick Help With Common Tasks

From RiskWiki

Jump to: navigation, search

Contents

Introduction

This page includes a list of links to pages grouped by common tasks for rapid access.


Adding an Extra Database or Moving A Database From a Different Location

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:

Create a new database in your database server:


You will probably 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:



Restoring or Replacing a RiskManager Database

In this scenario we assume that you are restoring an existing 'in use' database from a backup, or from an upgraded database returned after conversion or upgrade by Bishop Phillips Consulting. The key issue here is that the connection from the risk manager data server already exists, so you do not need to create a new one.


The first step is to restore the database from the backup:


In moving the database from one server to another the login id held in database that the riskmanager dataserver uses will probably become 'disconnnected' from the SQL Server instance, so we need to re-link the login id to the restored database.


If the database is otherwise the same as the original database you are replacing (ie. you are restoring from a backup), then you are finished.


Assuming that the database being restored is a replacement database, not originally sourced from the destination database server, we will need to perform another couple of configuration steps:


Changing the security model

BPC RiskManager supports musltiple access security modes. These can be changed at any time and are interchangeable, but only one access mode can exist on a specific application server (although multiple application servers connecting to one database could each use a different acccess model if one desired).


The modes currently supported are:

  • Fixed (where everyone accesses with a single default role)
  • Managed in RiskManager (where the Risk Manager manages roles, passwords and all the access rights itself)
  • LDAP (where users are authenticated by an LDAP server and roles are managed in the application)
  • AD (where users are authenticated by an MS Active Diretory server and roles are managed in the application)
  • NT Groups (where users and roles are defined in NT Groups)


For Locally managed modes the logins may be trusted or untrusted. Trusted means that the system assumes the login id presented by the client is legitimate and authorised (and so does not check the password), while untrusted means that risk manager requires a password and authenticates that with the user id.


In addition user ids can be include or exclude the network domain portion. Generally we recommend excluding the network domain. If you include the network domain, then the same user logging in from different domains is treated as two seperate users - one of whon may have access, the other may not.


To change the access security mode to "locally managed" or any of the other modes go to:



How to move RiskManager into production after dev/test has been approved

We have prepared a comprehensive guide to rolling BPC RiskManager into production (or adding an extra application server in production).



What to do after adding a new application server or moving to test/dev into production

Enterprise sites normally have multiple installations - possibly multiple application servers or (more commonly) seperate dev/test and production systems. In these sites the database to which the new application server is connecting may have already been configured and installed and you just want to connect to it from a new application server. The best way to do this is simply run the installer on the new application server. After you do, however the client may seem to not be able to connect. This is because the installer has set you up as if you were a new installation, rather than an existing one.


This page tells you how to switch the application server into the correct security model for your site.



Also, it might help to check out the guide on setting up production. In particular the section about "after installation"



Managing Resources & Access


Updating your user preferences in BPC RiskManager

Various user details can also be set or updated on a per user basis by the individual user. These include your password, spell checker, screen colour coding, screen resoultion handling, etc.


Recycle IIS WorkerProcess for the HTTPSrvr.dll

In the unlikely event that users report that they can not log on using the HTTP or HTTPS connection mode, and that they get an error message that either questions whether the socket server is running on the server, or states "could not convert variant of type(Dispatch) into type (Integer)", it is likely that your HTTPSrver.dll worker process on the server has locked up:


Image:HttpSrvr Client LoginErrorMsg1.png


You can either wait 20-30 minutes for the process to naturally recycle, or do the following:



Configure IE for the BPC RiskManager Plugin

The BPC RiskManager is shipped with multiple client versions, one of which is a browser plugin for IE and compatible browsers. The browser plugin is Versign signed ActiveX, similar to other plugins supplied with IE such as Flash and Adobe, etc. To allow your browser to be able to download, install and run the plugin you may need to make some browser configuration changes as detailed on this page:


BackLinks



CopyRight Bishop Phillips Consulting Pty Ltd 1997-2012 ( BPC RiskManager Quick Help With Common Tasks )
Personal tools