Skip to content

Support different KRAD/KNS database platform#32

Open
ewestfal wants to merge 3 commits intomasterfrom
support-differnt-kns-database-platform
Open

Support different KRAD/KNS database platform#32
ewestfal wants to merge 3 commits intomasterfrom
support-differnt-kns-database-platform

Conversation

@ewestfal
Copy link
Copy Markdown
Collaborator

@ewestfal ewestfal commented Dec 8, 2017

This pull request makes it possible to configure a database "platform" for a KRAD/KNS client application which differs from the standalone Rice server it's integrated with.

In otherwords, a Rice client application could be using MySQL while the standalone server remains on Oracle. This is a specific requirement at Indiana University where we plan to migrate our KFS to MySQL but remain on Oracle for Kuali Rice (until we retire it).

In order to take advantage of this, one simply needs to configure the krad.datasource.platform and krad.datasource.ojb.platform config properties. The first of these should be the fully qualified classname of the org.kuali.rice.core.framework.persistence.platform.DatabasePlatform implementation to use. The second of these will be the OJB platform name, one of 'MySQL', 'Oracle', or 'Oracle9i'

This enhancement should be fully backward compatible, not requiring any configuration changes for existing applications when this new version is pulled in.

@ewestfal ewestfal changed the title Support differnt kns database platform Support differnt KRAD/KNS database platform Dec 8, 2017
@ewestfal ewestfal changed the title Support differnt KRAD/KNS database platform Support different KRAD/KNS database platform Dec 8, 2017
@ewestfal
Copy link
Copy Markdown
Collaborator Author

One additional thing that I should note. I didn't have a way to really test a client application and rice server on two different platforms. The best way to test this is probably going to be to try and use these changes on the setup here at IU if possible. I did some manual testing in Rice itself to ensure that at least the various configuration properties were doing what they should be doing, but this is a bit of a "blind" change ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants