BPC RiskManager Frequently Asked Questions: Difference between revisions

From RiskWiki
No edit summary
No edit summary
Tag: Reverted
Line 18: Line 18:
# [[Is there a cost associated with telephone support (i.e.: cost per call or issue)?]]
# [[Is there a cost associated with telephone support (i.e.: cost per call or issue)?]]
# [[How do I get custom features added, or request new features for BPC RiskManager?]]
# [[How do I get custom features added, or request new features for BPC RiskManager?]]
# [[Is there a User Group Forum?]]
<!-- # [[Is there a User Group Forum?]] -->
# [[What type of documentation, technical and user is available for BPC RiskManager?]]
# [[What type of documentation, technical and user is available for BPC RiskManager?]]
# [[How does one decide the optimum BPC RiskManager configuration?]]
# [[How does one decide the optimum BPC RiskManager configuration?]]

Revision as of 02:35, 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. What type of documentation, technical and user is available for BPC RiskManager?
  19. How does one decide the optimum BPC RiskManager configuration?
  20. Is BPC RiskManager a Client-Server application?
  21. What is the difference between the browser plugin and the windows executable RiskManager client?
  22. Database stability: Is the RiskManager essentially a SQL Server application ported to Oracle?
  23. Database support: Which database choice will give us the best level of support?
  24. Security: What is the most secure architecture for BPC RiskManager?
  25. What is the best client version - the browser or non browser Risk Manager client?
  26. What admin account rights are required to setup a browser plug-in?
  27. How do I configure IE for the RiskManager browser plugin?
  28. We just ported our enterprise system to a new server and I can't login. What do I do now?
  29. How do I port BPC RiskManager from test (or dev) to production?
  30. How do I install BPC RiskManager onto a computer running a 64bit Windows OS?
A Frequently asked Question is...

Answer

This is a tricky issue. Generally we would recommend the windows non-browser version, unless you have a large number of users and want to be able to distribute the client component in an ‘on-demand’ manner.


Why? - Simply because there is one less 'moving part' and resizing of the application can be applied to the base (main) window, but an alternate argument is that where there are multiple databases, the browser client offers an advantage because you can easilly list the various connections on the hosting web page, and specifically secure access to the web page as part of your access model. Further the web page offers a simple "single point of publication" distribution system which instantly delivers the latest version to all users.


Like we said - there are really good arguments for both versions. Most larger lients use both versions, with the majority of users using the web browser version. Smaller clients tand to use the windows version.


On the face of it, the browser plug-in would be best in the situation involving a large, diverse oir geographiucally spread user base, as it will look after distribution, and updating itself on client computers. Note, however, the comment following:


The plug-in component is a self registering verisign signed ActiveX which does not write back to the web page hosting it, nor does it respond to scripted instructions sent externally to the plug-in (i.e.. it is a self contained blackbox). The default version contains a separate MIDAS library which it installs and writes to the client computer as part of the registration process, but we can replace this with an internal version of the library if needed. The non-browser version uses an internal version of the library, and is therefore installed merely by copying it to any place on the client computer to which a user has write access. Both the browser and non-browser clients write user preference information to the registry and work under Vista with UAC enabled. Some lockdown configurations of client computers can (obviously) prevent the plug-in from registering, and in those cases the non-browser client is the better choice as it does not need to register itself.


ActiveX plug-ins are not supported in the latest release of FireFox (although earlier releases are fine). Clients using the latest release of FireFox are advised to use the non-browser client.


In version RiskManager 2.5 and above, both the browser and non-browser clients use an internal com wrapper for IE (any version 5+ available on the client computer) to allow embedded document, procedure manuals and other links such as team web sites to be displayed integrated with the risk information on certain tabs. The capability is not critical to the operation of the application, but significant for some forms of user experience. In the event that IE has been stripped from the client computer, this capability will not work. If this proves to be a critical issue, we ..→Read More..



BackLinks