Support different KRAD/KNS database platform #32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…de Rice application than the standalone server
ewestfal
changed the title
ewestfal
changed the title
jwbennet
approved these changes
Dec 8, 2017
|
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.platformandkrad.datasource.ojb.platformconfig properties. The first of these should be the fully qualified classname of theorg.kuali.rice.core.framework.persistence.platform.DatabasePlatformimplementation 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.