View source for BPC RiskManager - Database Configuration

=Introduction=

The Database Configuration tab is used to configure the database ADO connections used by the application server to connect to the RiskManDB.


Please add one entry per risk database for the application to connect to.  Recommend configuring one connection to be set as the Default connection.  This connection string is used when no connection is selected by the user in the RiskManager client program.  Remember to ‘Save’ each connection after editing any property.


Typical uses of more than one risk database are production, training and user acceptance testing.



=Configuration=


[[Image:RMDS_GP3.png]]

<ol>
<li> Select the “RM Database Configuration” tab
<li> Either select a row in the grid to change a connection’s details or select the “New” button to commence a new connection.
<li> Assuming you are entering a new connection, enter the name of the connection in the “Connection Name” field.  Keep this name short, DO NOT INSERT SPACES ands use ONLY letters and digits and underscore, and make it sensible as this the connection by which users will know the underlying database.  It may have to be typed at some points by users, it may be part of a web URL (hence no spaces) and should make sense so users can remember it if needed.
<li> If this will be the default connection set the “Default Connection” to yes.  While you may have more than one default connection, only the first in the list will be seen by the application when the default connection is requested.
<li> Select the ellipsis button to build a new database connection string that will be stored with this connection.
<li> A connection string build window will open.  Select “Use Connection String” and select the “Build” button.
<br>
<br>
[[Image:RMDS_GP4.png]]
<br>
<br>
<li> In the “Data Link Properties” window select the “Provider” tab and select the “Microsoft OLE DB Proider for SQL Server” OLE DB Provider from the list .
<br>
<br>
[[Image:RMDS_GP5.png]]
<br>
<br>
Notes for building ADO Connection Strings:
* Always use nominated provider below for each database:
** SQL Server: ‘Microsoft OLE DB Provider for SQL Server’
** Oracle: ‘Oracle Provider for OLE DB’.
** Interbase: Select ODBC driver for Interbase (needs to be installed separately).
<br>
<br>
<li> In the “Data Link Properties” window select the “Connection” tab or select “Next”and enter the connection details for the database to which you wish to connect..
<br>
<br>
'''SQL Server 2000 / SQL Server 2005/ MSDE'''
* In the “select or enter server name” field either:
** If the database server is on the same computer as the application server, simply entetr a “.” (full-stop or period).
** If the database is on a different computer, select the machine from the drop down list, or type its name.
<br>
<br>
'''SQL Express 2005'''
* SQL Express 2005 installs, by default into a named instance on your computer.  Therefore the correct entry for server name field must include “\SQLExpress”.
** If the database server is on the same computer as the application server, simply entetr a “.\SQLExpress” (full-stop or period).
** If the database is on a different computer, select the machine from the drop down list, or type its name and add “\SQLExpress” to the end of the server name.
<br>
<br>
[[Image:RMDS_GP6.png]]
<br>
<br>
<li> Select the “Use a specific user name and password” radio button.
<li> Enter “riskmanuser” ( or “sa” or other username as appropriate) in the “User name” field and the appropriate password.  If you are using SQL Server 2000 or MSDE 2000 and are using “sa” with a blank password (not recommended) you should tick the “Blank Password” check box
<li> Tick the “Allow saving password” check box.
<li> Select the “Select the database on server” radio button and choose your databse from the drop down list.  If all the details entered were correct, the database name will appear in the drop list.
<li> Select “Test Connection” to verify that we can connect to the database.
<li> If the connection was successful, a message to that affect will appear, and you should select OK to generate the details as a connection string.
<li> Select OK again to cause the new connection to be written to the database.
<li> A couple of message windows may appear at this point that are reminding you that the survey and incident engine connections have been set to the same database which is the default setting (and the recommended setting in most circumstances).
<li> On the RM Database tab of RiskManager Dataserver, if the “Save” button is active, Select “Save” to ensure the details are saved. 
<br>
<br>
[[Image:RMDS_GP7.png]]
<br>
<br>
</ol>


'''''Notes:'''''
*Do not choose Windows NT Integrated Security.  NT integrated security uses the security credentials of the interactive NT account to connect to the database.  This interactive user is not always the same user as the system administrator performing this configuration.  The application server is launched and run under the context of the ID running the Borland Socket Server (configured in step 9: Install Socket Server as a Service).  The Log On used by the Borland Socket Server (and many other services) is the ‘Local System Account’.  Note: A different account can be configured using Windows Services.  If you use windows authentication you would have to provide either that account or a specially created service account (with similar rights) to have access to the database – which is near administration level.
* Be sure to select to the save the password in the connection string: option ‘Allow saving password’.
* Please test all connections before saving.
* The program ‘RiskMailManager’ re-uses all database configurations made in this form.




=BackLinks=

{{#dpl: linksto={{FULLPAGENAME}} }}