BPC RiskManager Frequently Asked Questions: Difference between revisions

From RiskWiki
← Older edit
Bishopj (talk | contribs)
Bureaucrats, Interface administrators, Administrators
183 edits
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...

What will need to be arranged prior to the installing BPC RiskManager?

Things we will need you to have arranged prior to the install:

  1. Fully patched Windows 2000, 2003 or 2008 server with IIS 6+ for the application server hosting (or if undertaking a desktop install - Windows 2000, Windows XP, Windows Vista SP2, Windows 7 PC).
  2. If using SSL/HTTPS as the communication protocol, an SSL Certificate for the Windows IIS 6/7 server for the domain you will be using for the RiskManager application server. We do not perform certificate validation – so an internal certificate should be fine but note that we use real Certificates issued by Verisign and Thawte on our sites so we have only tested under an environment where the certificates are “real”. I can not think of any reason why an internal certificate should be a problem however. Certificates are ONLY required for HTTPS, not for HTTP or Raw TCP/IP communications protocols (which is the normal way the application is used).
  3. Fully patched SQL Server 2000, 2005 or 2008 database engine (installed in MIXED MODE – not just Windows Authentication Mode) with Enterprise Manager (SQL 2000) or Database Studio (2005/2008) available (unless you want to fluff around in SQL command line calls).
  4. Administration access to the Windows servers and the SQL Server (you need to be able to create and restore a database and create an SQL user account and assign roles to that account), or if installing a destop version, you will need administration access to the desktop PC.
  5. A test client computer with admin rights to that computer – preferable Win XP (latest patches – of course) that has network connectivity to the Windows application server.
  6. Simple TCP/IP network connectivity between all these components – lets get it working in the simple scenario before we complicate it all with proxy servers. If you plan on using the HTTP or HTTPS communication protocols between the client and the application server, the windows IIS server rights settings are a little fiddly and the error messages are less than helpful when they are wrongly set so it would be better to know we have these right before we in introduce another layer network communications problems like proxy servers.

Read More..



BackLinks

Retrieved from "https://www.bishopphillips.com/riskwiki/index.php?title=BPC_RiskManager_Frequently_Asked_Questions&oldid=1220"