| Does OpenLexicon Support SQLServer |
|
|
|
|
One thing you can do is define operational data in SQLServer through JDBC support. The metadata might remain in MySQL or in a cache file. Regarding SQL server: first of all, I should say that OpenLexicon Wizard and metadata support isn't provided for SQL Server at this time. That shouldn't be a major issue in and of itself, as you're free to develop business objects and business rules in one database and execute them against a different database. As far as runtime compatibility with SQL Server goes, it really depends on what you are doing. If you are looking for basic query capacity (i.e. SELECT statements), I think that has a decent chance of working natively with OpenLexicon, subject to testing. On the other hand, due to the different implementations of the SQL standard by the various database vendors, stored procedure support can only be provided by writing code targeting each specific database. This would require adding some code to the com.hotapp.lexicon.JDBCModule.java code module, and was necessary to provide both Oracle and MySQL support. Here's what I might try to see if basic query support will work under SQL Server: 1. Develop a single validation and a single transformation rule to query a database table 2. Setup a Torque database connection in your Torque.properties file for your SQL Server database - the Torque website will be helpful to find the proper URL format and that sort of thing. You'll of course need a SQL Server driver JAR file to be added to your dev environment. 3. Test the SQL Server connection using the RulesEngineTest class. 4. Once you can get a db connection in step 3, test the individual rules using the appropriate methods from the RulesEngineTest class. This will require minor coding on your part, as the RulesEngineTest class was designed to be as simple as possible. You will need to initialize the cache using one database name, and execute the rules engine using a different database name (so that the metadata comes from your MySQL instance and the rules are executed against your SQL Server instance). Probably the easiest way to do this is to get two separate db connections, then invoke the desired method from LexiconValidationService or lexiconTransformationService. This bit of test code might do the following: * Get a database connection to your metadata instance * Initialize the cache * Get a database connection to your SQL Server instance * Call one of the following methods in com.hotapp.LexiconTransformationService or com.hotapp.LexiconValidationService, sending the SQL Server connection for the transformConn or valConn parameter. |
OpenLexicon.org | Home
FAQ Does OpenLexicon Support SQLServer