BPC RiskManager Frequently Asked Questions: Difference between revisions

From RiskWiki
m 1 revision imported
No edit summary
Tag: Manual revert
 
(9 intermediate revisions by the same user not shown)
Line 58: Line 58:


<noinclude>
<noinclude>
[[Category:RiskManager FAQ]]
[[Category:Risk Management]]
[[Category:Risk Management]]
[[Category:Risk Management - Software]]
[[Category:Risk Management - Software]]

Latest revision as of 13:58, 16 April 2026

  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

There is a very detailed installation process on RM625ENT Installation Instructions


However, this assumes an essentially manual installation process, essentially starting from a raw iron server, and includes installation of the OS components required. If you use the automatic installer (recommended) the process is much simpler. Production, generally differs from Test or Dev environments, however as the components maybe more widely distributed and you are generally starting with an at least partially configured server (unless you are dedicating a production application server instance to RiskManager).


Different sites do differing things for production, some reinstall completely others duplicate test into production, some do everything manually for production, while using the automated system for Dev, etc.


We recommend a reinstallation - partly because it is the least error prone, and possibly faster.


If You Have An Existing BPC RiskManager Production Installation

If you have an existing RM installation in production, you can actually just copy the changed files onto the server (replacing the existing files of the same name) and start the RiskManagerData server once, then close it down, and you are done, so the auto-installer is not actually necessary in this case. Alternativley, you can run the uninstaller in production to remove the previous installation, and then use the new installer to reinstall. You will NOT loose any of your configuration settings - so it is completely safe to do this. That will essentially make you existing system a raw machine EXCEPT that the connection settings will be in place already.


If this is your situation, the steps below are still correct BUT you should NOT let the installer create the database(s) for you - as you already have the connections present. Just say no to this question when it comes up during installation.


Performing the Migration To Production

Read the preceding section if your production server has a pre-existing RiskManager V6 installation. If you are migrating from BPC RiskManager Express or RiskMan, you DO NOT NEED TO UNINSTALL, BPC RiskManager V6.x will ignore the Express settings and installation.


Assuming we are starting with a W2003+ server that does not have a pre-existing RM installation, and that your SQL Server is on a separate computer:


MAKE DECISIONS BEFORE INSTALLING:

  1. If using BPC support during installation email us to arrange a time for our call to assist you install.
  2. Decide whether you are going to enable SurveyManager as part of the installation, or later. (Ask the business)
  3. Decide how many databases will be set up in production (Can be increased later if desired, but easiest if known prior to installation as the installer does all the work for you).
  4. If you want to make an existing database available in production that has been set up in dev/test and you will NOT be using the same ..→Read More..



BackLinks