BPC RiskManager Frequently Asked Questions: Difference between revisions

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

Revision as of 11:39, 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...

In What Language Is BPC RiskManager Programmed

BPC RiskManager consists of more than 100,000 lines of code written in Delphi 7 (Object Pascal) from CodeGear (formerly Borland, now Embarcadero) compiled into W32 binary executables and TSQL/SQLPlus. Some smaller components are written or supported by libraries in JavaScript, PaxScript, and ReportBuilder script.


The Delphi environment was originally developed by Borland, starting with Turbo Pascal in the 1980's. It has been one of the leading development environments and languages for almost 20 years and has one of the largest and most skilled development communities in the world. Delphi 7 was released in 2001 and has proven to be perhaps the most resilient, and bullet proof development environment of the last decade.


Why Object Pascal?

From our perspective the most apparent reason is that by default Pascal imposes rigid data typing, and size checking. In Pascal you have to turn these off if you want to misbehave, while in C the reverse is the case. Buffer overflow errors such as those that have plagued Microsoft operating systems (written in C and Basic) and been the cause of many security holes are not possible in Pascal - because while it still operates at the hardware level of the computer it dynamically checks pointer references and array boundaries (raising exceptions when indexes flow past them) and maintains reference counts of objects allocated so that they can be released when no other objects point at them.


This safety net means that it is slightly slower in array and memory release operations than C, but identical in procedure calls, pointer, floating point and stack operation speeds. So it delivers a higher level of reliability than C, while compromising only slightly on speed but remains much faster than .Net languages or Java - which are "interpreted" (although both claim to be compiled - the reality is that they are compiled as a set of runtime library calls) and operate inside a virtual machine that provides a managed pseudo machine in which the applications work.


A further advantage is that, because no run time engine is needed, any Pascal library will work on all the target machines, with any other machine library regardless of the compiler version. You do not have to worry about framework or psuedo machine engine versions - the idea is simply irrelevant.


Does It Matter?

Not really.

You won't notice the language in which we develop, any more than it is apparent what language Microsoft Word is written in. Think of RiskManager as just another MS Office application and you will be about right - it looks, feels and behaves the same way.


I am used to applications in the .Net and Java Languages. How is this different?

Its an awful lot simpler. No run time environment, no library version problems, no interactions with other applications sharing the run time environment. Just take our application out of the box and put it on your ..→Read More..



BackLinks