BPC RiskManager Frequently Asked Questions: Difference between revisions

From RiskWiki
m 1 revision imported
m 1 revision imported
(No difference)

Revision as of 11:30, 29 October 2018

  1. How do I get a copy of BPC RiskManager V6.2.5?
  2. Would it be possible to get a copy of the BPC RiskManager V6 installation guide?
  3. Is there a feature listing for the BPC RiskManager windows client and the browser client? We are looking at the possibility of using a mixed client environment based on user specific needs and where they are.
  4. When are multiple BPC RIskManager server licenses required? We are looking to have RM implemented across a group of companies. They will all be using the same instance with same fields and definitions as the subject matter is the same. Can we use a single server license or will we require multiple server licenses?
  5. Can you please provide information on the cost of licensing and the type of licensing for BPC RiskManager V6.x ?
  6. Does your license include the cost of MS SQL Server ?
  7. I just purchased BPC RiskManager. Will you be sending the install disks, and when?
  8. What will need to be arranged prior to the installing BPC RiskManager?
  9. Does the RiskManager client application work with FireFox browsers?
  10. In what programming language is BPC RiskManager written?
  11. Does the RiskManager plug-in itself have a certificate like a java applet does?
  12. For support, what type of support is available (i.e.: email, phone, onsite, etc...)?
  13. What is the best way to get support?
  14. How do I arrange installation support and what is the timeline?
  15. What support packages are available and at what cost?
  16. Is there a cost associated with telephone support (i.e.: cost per call or issue)?
  17. How do I get custom features added, or request new features for BPC RiskManager?
  18. Is there a User Group Forum?
  19. What type of documentation, technical and user is available for BPC RiskManager?
  20. How does one decide the optimum BPC RiskManager configuration?
  21. Is BPC RiskManager a Client-Server application?
  22. What is the difference between the browser plugin and the windows executable RiskManager client?
  23. Database stability: Is the RiskManager essentially a SQL Server application ported to Oracle?
  24. Database support: Which database choice will give us the best level of support?
  25. Security: What is the most secure architecture for BPC RiskManager?
  26. What is the best client version - the browser or non browser Risk Manager client?
  27. What admin account rights are required to setup a browser plug-in?
  28. How do I configure IE for the RiskManager browser plugin?
  29. We just ported our enterprise system to a new server and I can't login. What do I do now?
  30. How do I port BPC RiskManager from test (or dev) to production?
  31. How do I install BPC RiskManager onto a computer running a 64bit Windows OS?
A Frequently asked Question is...

Introduction

BPC RiskManager is a 32 bit application, but it will work just fine on 64 bit Windows. In most scenarios (particularly W2008 and above and Windows 7), the supplied BPC Riskamanger auto installer will correctly install the RiskManager system on a 64bit computer with no manual intervention. The optional SurveyManager library will require some manual steps in IIS and you should consider the notes lower down this page concerning that. If you are installing the W2003 64bit you may have to do some manual steps.


If you wish to pursue this solution on Windows 2003 for 64 bit or Windows 2008 for 64 bit you will need to do the following things:


  • Install on the application server machine the 32bit ADO drivers for the target database (eg the MDAC 2.8 driver set. The RiskManager Installer will automatically cheeck for these and install them for you, so you can just run the installer for this step if you wish. For standard MS databases these should already be present, but you may need to download the appropriate 32 bit MDAC driver set from Microsoft. (A 64bit DB server will still require a 32bit driver for BPC RM to connect to it, but these should already be present.).
  • Install BPC RiskManager as you would on a 32 bit operating system accepting the defaults. The installer will automatically put the 32but components in the x86 directory as required.
  • Run the 32bit SocketServer, BPC RiskManager, BPC RiskManager DataServer and BPC RiskMailManager in 32 bit compatible mode i.e. using WOW (Windows-32 bit on Windows-64 bit) on your server. The auto installer will automatically do this for you, so you should not need to do anything unless you are doing a manual install (ie. copying and pasting the components).
  • Move the 32 bit Midas.dll into the 32 bit system directory and register it manually. Again the installer will do this automatically and you should not have to do anything unless you are doing a manual install.
  • Enable IIS to run 32 bit ISAPI dll's (if using the web components like surveymanager). This, you will have to do even if using the installer.
  • Move the 32 bit ISAPI libraries into the 32 bit ISAPI directory. This you may have to do even if using the installer.


If you are installing on Windows 2008 or above, Windows 7 or above the 32 bit and 64 bit MDAC drivers should already be present, or if you are using the installer they should be installed automatically by the installer.


So, the simple solution to setting up RiskManager on 64Bit windows? - Just run the RiskManager Installer and let it do all the work.


Setting Up the Database drivers on WOW64

If you are using the insatller to install Riskanager, the installer will check for the MDAC (ADO) drivers and install the correct ones if missing.


There are multiple scenarios that you could be facing - all have essentially the same solution:

  1. . Locally installed 64 bit database server : You will need the appropriate 32 bit drivers. These have probably been installed ..→Read More..



BackLinks