-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Makefile.config to configure SQL/SQL++/ODM and SPARK ; Reorg for …
…Makefiles ; Remove all jars from repository (now all pulled through ant scripts) ; Refresh README
- Loading branch information
Jerome Simeon
committed
Sep 3, 2017
1 parent
7ce11d9
commit dd491f5
Showing
28 changed files
with
517 additions
and
266 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,15 @@ | ||
*~ | ||
.#* | ||
*.vo | ||
*.v.d | ||
*.glob | ||
*.aux | ||
Makefile.coq | ||
Makefile.config | ||
bin/qdata | ||
bin/qcert | ||
bin/qcertJS.js | ||
bin/*.jar | ||
bin/services/*.jar | ||
/.project | ||
.DS_Store | ||
*~ | ||
.#* | ||
*.vo | ||
*.v.d | ||
*.glob | ||
*.aux | ||
.DS_Store |
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
### Uncomment to support a given source or target language | ||
|
||
### Source languages configuration | ||
|
||
## SQL and SQL++ support requires Java and Ant | ||
SQL=yes | ||
SQLPP=yes | ||
|
||
## ODM rules support requires Java and Ant, plus a copy of the jrules-engine.jar (See README.md) | ||
#JRULES=yes | ||
|
||
### Target languages configuration | ||
|
||
## Java support requires Java and Ant | ||
JAVA=yes | ||
|
||
## Spark support requires Scala, SBT (Scala Built Tool), and Ant | ||
#SPARK=yes | ||
|
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
### Obtaining the ODM Rules dependencies | ||
|
||
The ODM rules support requires that you obtain a legal copy of the ODM | ||
Designer component that comes with various versions of ODM. | ||
|
||
ODM comes in (at least) two configurations called "ODM Rules" and "ODM | ||
Insights". Each comes with its own Designer, which in turn supports a | ||
characteristic set of languages. There are (at least) two license | ||
arrangements: "ODM Classic" has only the Rules configuration and "ODM | ||
Advanced" comes with both Rules and Insights. There is also ODM in | ||
the cloud, based on the Rules configuration. We hope that our support | ||
will work with either the Insights Designer or the Rules Designer but | ||
we have only tested it with the Rules Designer and it only covers the | ||
languages that are provided by that Designer. | ||
|
||
There is no free version of ODM, but some 30 day free trial programs | ||
will allow you to try out certain versions. In order to use our | ||
"technical" rule support, you need a binary jar available only with an | ||
ODM Designer. To use the "designer" rule support, you need to fully | ||
install and utilize an ODM Designer. | ||
|
||
One possible route is to sign up for the 30 day free trial of ODM in | ||
the Cloud (https://www.bpm.ibmcloud.com/odm/index.html). Once you are | ||
authorized for the trial, you can log in to the cloud service and | ||
obtain a copy of the ODM Rules Designer (downloaded and installed on | ||
your own machine). | ||
|
||
Once you have a Designer component installed on your machine, the next | ||
step is to find the library called **jrules-engine.jar** and copy it | ||
to a directory in the qcert working tree. Start by making the | ||
directory | ||
|
||
``` | ||
jrules2CAMP/lib | ||
``` | ||
|
||
if it does not already exist. | ||
|
||
If you installed the Designer using ODM in the cloud, there is a copy | ||
of `jrules-engine.jar` in the `studio/lib` directory of the directory | ||
where the Designer is installed. Simply copy that file into the | ||
`jrules2CAMP/lib` directory. If you have some other version of ODM | ||
Rule Designer or Insights Designer, find the location where the ODM | ||
plugins are located and look for a plugin jar whose name starts with | ||
"com.ibm.rules.engine...". Inside this jar you may find a copy of | ||
jrules-engine.jar. Unzipping the outer jar into the `jrules2CAMP` | ||
directory should put a copy of jrules-engine.jar in the `lib` | ||
subdirectory. Beyond those suggestions, you are on your own. | ||
|
||
|
Oops, something went wrong.
dd491f5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This closes issue #63.