Update the crash database connection information

Top  Previous  Next

Clients that have purchased a configuration will need to update the connections to point to their internal collision database. In general Pd' Programming creates configurations based on a sample copy of the clients collision database. Configurations sent to users therefore contain database connection information for sample database at Pd' Programming, and must be changed. Each configuration can contain one or more connections to the collision database. The information required by these connections should be provided by the database administrator of the collision data. Here is how to locate the connections:

 

1.Log into the Crash Magic web site as the Group Admin using the default user login.
2.In the admin tree on the left, click on the plus sign (+) next to the .shared user under the user group that your are currently logged into .
3.Under the .shared user, click the plus sign (+) next to the connection name in the admin tree.

 

AdminMultipleDBConnections

In this example two connections are available for the CO@PdProgramming user group. A DataEntry and Default connections are shown in this example.

 

Here is how to change a connection string:

1.Select a connection to update by clicking on it in the admin tree(For the next examples we will select the Default connection).
2.Click on the green settings tab.
3.Change the Data Source of the connection string to the data source for the collision data(For MS SQL this will be the name of your database server. For Oracle this will be the name of the database service specified in the tnsnames file. With DB2 this is name used by the client for the database).
4.If your connection string includes a catalog change the catalog name to the name of the database(This is generally only for MS SQL).

 

Once the connection string is changed the login and password information will need to be updated. There are two options for Crash Magic logins. Standard Crash Magic logins or DBVerify.

 

The standard option allows a single database login to be specified. This will cause Crash Magic to use this login to query the collision database. In this case user logins and passwords must be managed in Crash Magic. In this case you will enter a valid login and password into the Login and Password fields of the connection string. Default analysis connections require only select access to the collision tables. If you are setting a connection for Data Entry then a login and password that has select, insert, update and delete privileges must be used.

 

DBVerify allows Crash Magic to pass the login name(User id on the login page) and password on to the database for verification. This allows for user logins and passwords to be managed with the database. Click the Set for DBVerify login link to set the login and password fields to use DBVerify.

 

Some database use roles to manage permissions on the database. A default empty role is included in the configuration. Roles defined under the .shared user will be displayed in the Role drop down list. If your logins require roles on the database you may need to add or change the roles provided. See the Roles section of the manual.

 

The connection to the database can be checked using the the Test button. Clients using DBVerify can test their connection string by entering a Login name and password, but the connection must be set back to DBVerify when complete. A successful test will display "Test connection succeeded." along with information on the database driver in use.

 

With the installation and setup of Crash Magic complete users can now be added to Crash Magic.