BPC RiskManager Frequently Asked Questions

How do I get a copy of BPC RiskManager V6.2.5? Would it be possible to get a copy of the BPC RiskManager V6 installation guide? 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. 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? Can you please provide information on the cost of licensing and the type of licensing for BPC RiskManager V6.x ? Does your license include the cost of MS SQL Server ? I just purchased BPC RiskManager. Will you be sending the install disks, and when? What will need to be arranged prior to the installing BPC RiskManager? Does the RiskManager client application work with FireFox browsers? In what programming language is BPC RiskManager written? Does the RiskManager plug-in itself have a certificate like a java applet does? For support, what type of support is available (i.e.: email, phone, onsite, etc...)? What is the best way to get support? How do I arrange installation support and what is the timeline? What support packages are available and at what cost? 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? Is there a User Group Forum? What type of documentation, technical and user is available for BPC RiskManager? How does one decide the optimum BPC RiskManager configuration? Is BPC RiskManager a Client-Server application? What is the difference between the browser plugin and the windows executable RiskManager client? Database stability: Is the RiskManager essentially a SQL Server application ported to Oracle? Database support: Which database choice will give us the best level of support? Security: What is the most secure architecture for BPC RiskManager? What is the best client version - the browser or non browser Risk Manager client? What admin account rights are required to setup a browser plug-in? How do I configure IE for the RiskManager browser plugin? We just ported our enterprise system to a new server and I can't login. What do I do now? How do I port BPC RiskManager from test (or dev) to production? How do I install BPC RiskManager onto a computer running a 64bit Windows OS?

A Frequently asked Question is... Security: What is the most secure architecture for BPC RiskManager? Access Rights With respect to access security we support trusted login, AD, LDAP, NT Groups, and internally managed methods for user access rights at the application server layer. Database Acess Only the application server accesses the database. There is no direct user to database connection ever established (even in report generation), consequently only one access login account is required between the database layer and the application server and there is no need to establish (or desirability in establishing) access rights for a user at the database level. Browser Plugin & Network Communictions RiskManager Browser and Non-Browser Clients The browser based and non browser versions of the Risk Manager client face the same issues and use the same models for network communications. The browser merely hosts a plug-in component (think flash player, or adobe pdf reader) and is essentially used for distribution of that component. Once the plug-in starts it establishes a direct connection to the application server on a different port than that used for normal web communications (which may or may not also be a web server – i.e.. The web server that delivers the base page can use any security model you prefer – and the application server(s) can be on any physical server you desire – not necessarily the same machine as the web server). The data stream is not a linear ascii data stream like a web page system but a stream of binary delta (change) packets which are essentially unusable out of the context of their stream and the non-delta (change) packets that are not re-transmitted in any case. On a private network this would generally be sufficient, in all but the most extreme scenarios. The stream itself can also be separately encrypted, our preferred model where additional security is required is that the entire channel is encrypted through a Vitrual Proviate Network (VPN) tunnel (which can be defined to operate on a single port if desired) because these are generally more secure and faster than data-level encryption as they can be imposed at the hardware level. The RiskManager access model is STATEFULL so security models that allow for preservation of state across access are appropriate (hence VPN tunnels are a really good idea). With respect to VPN solutions, either a fully fledged VPN (ideally hardware implemented for speed) should be used an the entire traffic between client and server tunnelled there-through, or HTTPS (SSL) can be used directly from the client to a dedicated (supplied) listener on the server, however in this latter case you will have to install an SSL certificate on the IIS server running in the application server and use the HTTPSrvr dll instead of (or in addition to) the SocketServer. Built in to the RiskManager client / application server architecture are three models for communications: Proprietary port using raw TCP/IP (This is the default method) HTTP HTTPS (SSL) ==SurveyManager ..→Read More..