The latest stable patch release of KOLE is 1.5.8 version released on February 5th, 2015. The table below highlights some of the differences in the 1.5.0 and the consecutive patch versions.
Version | SVN Location | Notes |
---|---|---|
1.5.0 | https://svn.kuali.org/repos/ole/tags/ole-1.5.0/ | This was the first 1.5.0 stable tag, but wasn't deemed to be "Go live" version by Chicago/Lehigh |
1.5.1 | https://svn.kuali.org/repos/ole/tags/ole-1.5.1/ | This is a "Go Live" version for Lehigh with solr 3.6 |
1.5.2 | https://svn.kuali.org/repos/ole/tags/ole-1.5.2/ | This is a "Go Live" version for Chicago with Solr 4.9. The major difference was in the performance of solr on a huge data volume. |
1.5.2.1 | https://svn.kuali.org/repos/ole/tags/ole-1.5.2.1/ | This is an intermediate critical-patch fix on 1.5.2 which was critical for Chicago. |
1.5.3 | https://svn.kuali.org/repos/ole/tags/ole-1.5.3/ | This is be the final "GO LIVE" version for Chicago university. |
1.5.3.1 | https://svn.kuali.org/repos/ole/tags/ole-1.5.3.1/ | Intermediate patch release before 1.5.4 to fix some critical performance issues regarding 1. Editing a big with large number of items 2. Generation of overdue notices. |
1.5.4 | https://svn.kuali.org/repos/ole/tags/ole-1.5.4/ | |
1.5.5 | https://svn.kuali.org/repos/ole/tags/ole-1.5.5/ | |
1.5.6 | https://svn.kuali.org/repos/ole/tags/ole-1.5.6/ | |
1.5.6.1 | https://svn.kuali.org/repos/ole/tags/ole-1.5.6.1 | |
1.5.6.2 | https://svn.kuali.org/repos/ole/tags/ole-1.5.6.2/ | Critical patch to provide Indexing by range. This was to avoid doing a full index when only partial records were corrupted. |
1.5.7 | https://svn.kuali.org/repos/ole/tags/ole-1.5.7/ | |
1.5.8 | https://svn.kuali.org/repos/ole/tags/ole-1.5.8/ | Performance fix: Problem with rendering the batch process job details page (OLE-7360) Performance fix: Additional POs or Additional charges to Invoices takes too long (OLE-7328) |
The guide below will describe in as much detail as possible the process of building one of the 1.5 tags and database migration processes for in between versions.
or Oracle 11g
To correctly configure Tomcat and MySQL/Oracle follow the section "Required Software" in the Developer Installation Guide. |
mvn clean install -DskipTests=true |
Script for building the bootstrap sql
#!/bin/bash cd ${OLE_DEVELOPMENT_WORKSPACE_ROOT} mvn clean install -DskipTests=true cd ${OLE_DEVELOPMENT_WORKSPACE_ROOT}/ole-app/ole-db/ole-impex mvn clean install -Psql -Dimpex.scm.phase=none cd ${OLE_DEVELOPMENT_WORKSPACE_ROOT}/ole-app/ole-db/ole-liquibase/ole-liquibase-changeset mvn clean install -Pbootstrap-sql-only,mysql -Dimpex.scm.phase=none |
You can skip to step 5.
cd ${OLE_DEVELOPMENT_WORKSPACE_ROOT}/ole-app/ole-db/ole-liquibase/ole-liquibase-changeset mvn clean install -Psql,mysql -Dimpex.scm.phase=none mvn clean install -Psql,oracle -Dimpex.scm.phase=none |
To load the institution specific data after the above executions, execute the following command:
cd ${OLE_DEVELOPMENT_WORKSPACE_ROOT}/ole-app/olefs [For MySQL] mvn initialize -Pdb -Djdbc.dba.username=root -Djdbc.dba.password=root [For Oracle] mvn initialize -Pdb,oracle -Djdbc.username=OLE -Doracle.dba.url=jdbc:oracle:thin:system/manager@localhost:1521:XE |
Ensure there is a default user in the system. You could create using the sql file in JIRA-7246. Further need to update the web.xml under olefs and replace the defaultUser from ole-quickstart to the newly created user. (If you used ole-quickstart, then there is no need to update the web.xml)
<!-- Copyright 2004-2013 The Kuali Foundation Licensed under the Educational Community License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.opensource.org/licenses/ecl2.php Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <config> <!-- Generic URL's --> <param name="appserver.url">[IP address]</param> <param name="application.url">${appserver.url}</param> <param name="ole.docstore.url.base">[IP]/oledocstore</param> <param name="docSearchURL">${ole.docstore.url.base}</param> <!-- MySQL Database (The default jdbc.username = OLE and jdbc.password = OLE) --> <param name="db.vendor">mysql</param> <param name="jdbc.username">[fill me]</param> <param name="jdbc.password">[fill me]</param> <param name="mysql.dba.url">jdbc:mysql://localhost:3306</param> <param name="mysql.dba.username">[mysql dba username]</param> <param name="mysql.dba.password">[mysql dba password]</param> <!-- Oracle Database --> <!-- <param name="db.vendor">oracle</param> <param name="jdbc.username">[fill me]</param> <param name="jdbc.password">[fill me]</param> <param name="oracle.dba.url">[db url]</param> <param name="oracle.dba.username">[dba username]</param> <param name="oracle.dba.password">[dba password]</param> --> <!-- Email --> <param name="mail.debug">false</param> <param name="mail.smtp.host">[Fill me]</param> <param name="mail.smtp.port">465</param> <param name="mail.smtp.ssl.enable">[true or false, choose one]</param> <param name="mail.smtps.auth">[true or false, choose one]</param> <param name="mail.smtp.username">[Fill me]</param> <param name="mail.smtp.password">[Fill me]</param> </config> |
runonce.properties
under ${user.home}/kuali/main/local/olefs-webappContents of the file are as below:
project.db.reset=TRUE |
What this enables is, during the application startup, a spring component will read the value of the project.db.reset and if its "TRUE" then starts the db initialization process automatically. It will automatically be updated to "COMPLETED" when db reset is done.
You can take the sql and manually apply it on your database.
The sql will have some "DATABASECHANGELOG" statements which you can ignore and execute the rest. |
Apache versions prior to Apache 2.4.4 cannot forward PATCH requests via the AJP protocol, which can interfere with some of OLE's APIs. |
If you are experiencing HTTP 501 ("Method Not Implemented") errors, this may be the cause. Check your Apache version and error logs for messages such as "ajp_marshal_into_msgb - No such method PATCH".
Possible fixes:
1. Use mod_proxy_http instead of mod_proxy_http in your proxy setup.
2. Use at least Apache 2.4.4 with mod_proxy_ajp
3. (Unverified) Use mod_jk instead of mod_proxy_ajp
The Incident Report screen allows an User Input field where system users can add information and submit. This is delivered to a pre-configured email address for further analysis. The following are the parameters that are to be added to make this functional.
The 'From' address on the notification email would be the email address from the contact information of the system user posting the Incident report.
The parameters are added to olefs-config-defaults.xml file.
<param name="mail.transport.protocol" override="false"></param> <!-- The mail protocol, usually smtp --> <param name="ole.fs.mail.server"></param> <!-- The mail server --> <param name="ole.fs.email"></param> <!-- The 'To' address for notifications --> <param name="ole.fs.exception.email"></param> <!-- The 'To' address for exceptions --> <param name="mail.debug">false</param> <param name="mail.smtp.host">${ole.fs.mail.server}</param> <!-- The mail server --> <param name="mail.smtp.port"></param> <param name="mail.smtp.ssl.enable"></param> <param name="mail.smtp.auth"></param> <param name="mail.smtp.username"></param> <param name="mail.smtp.password"></param> <param name="mail.relay.server">${ole.fs.mail.server}</param> <param name="mail.smtp.host">${ole.fs.mail.server}</param> <param name="kcb.smtp.host">${ole.fs.mail.server}</param> <param name="mailing.list.batch">${ole.fs.email}</param> <param name="kr.incident.mailing.list">${ole.fs.exception.email}</param> <param name="nonproduction.notification.mailing.list">${ole.fs.email}</param> <param name="KualiExceptionIncidentServiceImpl.REPORT_MAIL_LIST">${ole.fs.exception.email}</param> |
The Incident Report Email Notification currently works only in Kuali Nervous System (KNS) screens and not in the newer Kuali Rapid Application Development (KRAD) screens. This is probably due to a Rice bug which would likely be fixed in Rice v2.4.