Difference between revisions of "SQL Server - OpenKM 6.2"
From OpenKM Documentation
| Line 58: | Line 58: | ||
</security:authentication-manager> | </security:authentication-manager> | ||
</source> | </source> | ||
| + | |||
== Troubleshooting, error you can not connect to MS SQL Server == | == Troubleshooting, error you can not connect to MS SQL Server == | ||
Revision as of 10:16, 6 September 2013
Download SQL Server JDBC driver from Miscrosof SQL Server Driver Page and move it to $TOMCAT_HOME/lib
 |
Other JDBC driver for MS SQLServer we've tested is jdts. |
|
OpenKM 6.2 has been verified to run with SQL Server 2005 using the JDBC driver sqljdbc4.jar under tomcat-7.0.27 |
In this OpenKM release you can create the databases automatically configuring the hibernate.dialect and hibernate.hbm2ddl properties in OpenKM.cfg.
hibernate.dialect=org.hibernate.dialect.SQLServerDialect
hibernate.hbm2ddl=create
More info about this at:
Database creation
Starting with OpenKM 6.0, only one databases is needed:
okm_repo
Start SQL Server Management Studio Express and create the database.
Select your appropiate database collate.
Tomcat datasources
Edit file $TOMCAT_HOME/conf/server.xml
<Resource name="jdbc/OpenKMDS" auth="Container" type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000" validationQuery="select 1"
username="sa" password="***" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:sqlserver://localhost:1433;databaseName=okm_repo"/>
Login configuration
Edit file $TOMCAT_HOME/OpenKM.xml
<security:authentication-manager alias="authenticationManager">
<security:authentication-provider>
<security:password-encoder hash="md5"/>
<security:jdbc-user-service
data-source-ref="dataSource"
users-by-username-query="select usr_id, usr_password, 1 from OKM_USER where usr_id=? and usr_active='T'"
authorities-by-username-query="select ur_user, ur_role from OKM_USER_ROLE where ur_user=?"/>
</security:authentication-provider>
</security:authentication-manager>
Troubleshooting, error you can not connect to MS SQL Server
Ensure you've got tcp protocol enabled ( by default is disabled )
