skip to main content
Corticon Server: Integration & Deployment Guide : Implementing EDC : Working with EDC in Corticon Studio : Connecting a Vocabulary to a database : Creating a database access properties file
 

Try Corticon Now
Creating a database access properties file
Even though no tables have been defined for the database and nothing read or written, it is a good practice to export the successfully tested database access properties file. In the Vocabulary editor, select Vocabulary > Database Access > Export Database Access Properties, as shown:
You can specify a preferred name and location for the file, although colocating it within its related project folder is a good idea. The generated properties file looks like this:
com.corticon.database.id=com.corticon.database.id.MsSql2014
com.corticon.database.readonly.supported=true
hibernate.c3p0.max_size=100
hibernate.c3p0.max_statements=50
hibernate.c3p0.min_size=1
hibernate.c3p0.timeout=1800
hibernate.connection.driver_class=com.prgs.jdbc.sqlserver.SQLServerDriver
hibernate.connection.password=030046016058035029061039110
hibernate.connection.url=jdbc:progress:sqlserver://myDBhost:333;databaseName=Cargo
hibernate.connection.username=061046
hibernate.dialect=com.corticon.eclipse.studio.drivers.core.DDSQLServer2008Dialect
hibernate.temp.use_jdbc_metadata_defaults=false
Notice that the username and password values are very different from the credentials that were entered. These values were encrypted when the database access file was created, and will be decrypted when they are implemented in a decision service.
You shouldn't have to edit this file but if the Server is not colocated with the Studio, you see why it was a good idea to use the explicit host identifier rather than localhost.