BPC RiskManager Frequently Asked Questions

From RiskWiki

Jump to: navigation, search
  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...

What is the difference between the browser plugin and the windows executable RiskManager client?


In a nutshell, very little.

Bishop Phillips Consulting supplies a browser based and non-browser based client for BPC RiskManager. Both solutions are application server solutions (also called 3-tier application server) – not client-server.

There is no difference in functionality between the browser and non-browser version. The solutions differ in how the client component is served to the client computer desktop.

The browser based client is delivered as an IE 5/6/7/8 browser plug-in (like adobe reader or flash player) while the windows (non-browser) client resides on the user’s desktop (like word or excel). The main argument for using one over the other is that the browser based client is distributed simply by publishing it to a web server web page, while the windows client is distributed by copying it to the client computer. The interface is otherwise the same in both solutions. While the browser client is slightly simpler to distribute and update (just point your browser at the web site versus copy a single executable application to your computer.), it disconnects from the server when you close the web page on which it is hosted (just like adobe pdf reader), while the non-browser solution stays connected until you close it yourself (or the server side socket server times out the associated com object through inactivity).

The user interface is identical across both the browser and non-browser versions. We generally release updates to the non-browser client first and in the coming releases the non-browser client will probably behave more like outlook (existing as an icon in the system tray) when not actively in use. We tend to use the non-browser version oiurselves as opposed to the browser version, but that really doesn't prove anything either way.Read More..


CopyRight Bishop Phillips Consulting Pty Ltd 1997-2012 ( BPC RiskManager Frequently Asked Questions )
Personal tools