Page Comparison

...

Default Process

Make sure ole-build.properties and impex-build.properties, have been deleted from ${user.home}

Checkout the project

No Format
svn checkout https://svn.kuali.org/repos/ole/branches/dev/50-upgrade-test-1

Full build - run this from the root folder of the checkout
No Format
mvn clean install -DskipTests=true
Change into the directory for ole-fs the OLE FS application
No Format
cd ole-app/ole-fs
Generate the local configuration file configured with default values
Create the database for OLE FS - More detailed database info is available here
No Format
mvn generate-resourcesinitialize -Plocal
1. The above command generates the file
  No Format
  ~/.kuali/ole/ole-fs.properties
2. By default, the database vendor is MySQL with the root password set to NONE.
3. You will need to update this file with the password for the MySQL root user on your system
Reset an OLE FS database

Property Loading

Info

title	Property Loading Order

Order of property loading
1. the properties generated by the ant script (the old way and its still gets run as part of the ant script) - again not to be touched.
2. olefs-default.properties - Within the codebase and should not be touched as it is checked into SVN.
3. configuration.properties (~/.kuali/ole/fs/configuration.properties) - present on the local machine and generated during the generate-resources phase when the local profile is active. Can be modified.
4. If an external configuration file is present. - local to the developer and doesn't get checked in to SVN. So can point to anywhere in the local system where you hava a valid configuration.properties file.

Runtime property resolution is now possible for OLE FS!
This means the exact same war file can be used for development as well as deployment without altering the binary
Automatically loaded external configuration files are used to reconfigure the binary with machine specific configuration
The default external directory used by OLE FS is now based on the system property user.home
To change this you only have to override one property - ole.fs.home
1. Properties pointing to other directories needed by OLE FS are expanded into their absolute path at runtime
2. This way only a single property needs to be overridden (instead of all of them)
The following external property locations are automatically checked and loaded, in this order, if they exist
1. No Format
  ~/.kuali/ole/fs/configuration.properties
2. If the system property olefs.configuration is set, the properties file it points to is automatically loaded
If the property ole.fs.runtime.property.expansion=true the following actions are also taken
1. After loading classpath:configuration.properties load classpath:olefs-default.properties
2. Expand any properties containing placeholders into their fully resolved equivalents

Logging

A default logging configuration is now bundled into OLE FS
This means logging will work out of the box without requiring you to point OLE FS at an external log4j.properties file
You can still override the default log4j configuration if desired
1. set the property
  No Format
  ole.fs.log4j.override=true
  1. This can be set as a system property
  2. Or as a property in one of the configuration files that gets automatically loaded
2. create a log4j.properties containing your custom settings at
  No Format
  ~/.kuali/ole/fs/log4j.properties
3. OLE FS will use settings from the custom log4j.properties
4. The custom properties file is also monitored by a background thread and reloaded if changes are made
Going forward, any new logging statements added to OLE FS should use the SLF4J logging api
If existing code is modified, log4j logging calls should be replaced by SLF4J logging calls

Properties

...

System properties are set by specifying the -D parameter in the VM arguments.

...

Pdb
Point your IDE's Tomcat integration to the location on the file system containing the unpacked war
No Format
ole-app/ole-fs/target/ole-fs-webapp
Use your IDE's Tomcat integration to start Tomcat
Open a browser to the default OLE FS url
No Format
http://localhost:8080/olefs

Optional Customization

These steps are only necessary if you do not have a default MySQL install running locally
Change into the directory for ole-fs
No Format
cd ole-app/ole-fs
Generate the local configuration file configured with default values
No Format
mvn generate-resources -Plocal
1. The above command generates the file
  No Format
  ~/.kuali/ole/ole-fs

...

1. .properties

...

Property

...

Default Value

...

Description

...

olefs.configuration

...

None

...

If this system property is set, properties are loaded from the location it points to. Properties supplied here, override internal properties

...

ole.fs.runtime.property.expansion=true/false

...

false

...

If true, property expansion is performed at runtime instead of at build time. The resource classpath:olefs-default.properties is loaded if this property is set to true

...

ole.fs.log4j.override=true/false

...