...
...
...
...
...
...
...
...
...
...
...
...
...
...
About Microsoft SQL Server
Microsoft SQL Server (MSSQL) is a commercial database product available from Microsoft
Further technical information on this product may be found here
Warning | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
1. Adopters should enable the ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT options in the portal database. Without these options, MSSQL Server will encounter deadlocks in the portlet preferences subsystem under load. You can read more about these setting here. Perform the following commands to enable these settings:
2. MSSQL Server 2005 or later: uPortal 4 starts up correctly, but the channels contain no content. SQLServer2005Dialect writes 'varchar(MAX)' where it should be 'text'. Changing the column definitions below to be 'text' fixes the problem: UP_PORTLET_PREF(PREF_NAME) UP_PORTLET_PREF_VALUES(PREF_VALUE) UP_RAW_EVENTS(EVENT_DATA) 3. MS SQL Server 2005 or later: disable or delete the single uniqueness index on table UP_DLM_EVALUATOR. This index should ensure that if a fragment name is provided (is not null) then it must be unique. Unfortunately, MS SQL server is unable to provide such indexes since uniqueness check of 'null =? null' returns true when building index keys. This is not the case for other DBMS vendors (i.e. postgres). If you're using MS SQL 2008 or later, you can (and should) create a new filtered index to replace the deleted index in order to maintain data integrity. Here's the required SQL query:
Workaround above was submitted by Arvīds Grabovskis who deployed uPortal 4.0.3 at Riga Technical University, you can read his blog entry on the topic here. |
Step 1
...
: Obtaining
...
the Driver
Note |
---|
If using uPortal 4.0.9+, it is best to use the MS SQL Server and MS JDBC Driver (recommended) (click on link to view the instructions) |
...
The groupId, artifactId and version specified in this command are up to you, but they should match the JAR vendor, name and version to avoid confusion down the road.
Step 2
...
: Add the Dependency
From the uPortal source directory, open the uPortal-4.x.x/pom.xml file, there is a section about 110 lines down that reads:
...
See Issues section about possible issues using this driver.
Step 3
...
: Configure the Database Filter
1. NEW: In the filters folder, locate the default local.properties file under uPortal-4.0x.x/filters/local.properties and configure the Database Connection Settings
Code Block | ||
---|---|---|
| ||
# HSQL Configuration environment.build.hsql.port=8887 # Database Connection Settings (Uncomment the Maven Filters section in rdbm.properties) environment.build.hibernate.connection.driver_class=net.sourceforge.jtds.jdbc.Driver environment.build.hibernate.connection.url=jdbc:jtds:sqlserver://my.school.edu:1433/uPortal3db environment.build.hibernate.connection.username=sa environment.build.hibernate.connection.password= environment.build.hibernate.dialect=org.hibernate.dialect.SQLServerDialect |
Step 4
...
: Test the Configuration
Running the dbtest
ant target will tell you if you have configured the database connection properly.
Code Block |
---|
ant dbtest |
...
Step 5: Build and Deploy
Following a successful test, you can execute
...
Code Block |
---|
ant initportal
|
...
the command below to build the database tables and copy files to your servlet container.
Code Block |
---|
ant initportal |
Step 6: Restart Tomcat
Credits
Much of the information on this page was provided by Unlicensed user on the uportal-user list. Thanks.
...