OpenL Tablets Deployment

Jar Files

To deploy OpenL Tablets in runtime environment one needs to place the following .jar files into application classpath (replace 4.1.1 with more recent version where applicable):

${plugins}/org.openl.commons_4.1.1.jar ${plugins}/org.openl.core_4.1.1.jar ${plugins}/org.openl.j_4.1.1.jar ${plugins}/org.openl.rules_4.1.1.jar ${plugins}/org.openl.rules.helpers_4.1.1.jar ${plugins}/org.openl.lib.apache.poi.modified_4.1.1.jar ${plugins}/org.openl.lib.apache.commons_4.1.1/commons-lang-1.0.1/commons-lang-1.0.1.jar ${plugins}/org.openl.lib.apache.commons_4.1.1/commons-logging-1.0.3/commons-logging-api.jar ${plugins}/org.openl.lib.apache.commons_4.1.1/commons-logging-1.0.3/commons-logging.jar

Excel Files

Excel files need to be present in deployment as well. OpenL Tablets may retrieve Excel files in runtime either from the file system or from classpath. If Excel files are to be retrieved from file system, the location where they would be retrieved from is called user home. If user home coincides with Java VM current directory, no further action is required. If user home is different from Java VM current directory, you need to set user home in Java Wrapper file before creating Java Wrapper instances.

For example: 


MyProjectJavaWrapper.__userHome = "webapps/myapp/rules";

MyProjectJavaWrapper wrapper = new MyProjectJavaWrapper();

Included Excel Files

OpenL Tablets Excel document may contain include instructions to include other documents in case of a large project. OpenL uses C-language convention for handling include files. If the name is double quoted, the path is relative to the main file's location. If the name is in angle brackets, the path is relative to includepath. By default includepath is /include. Deployed include files must comply with these rules.

Project Classes

All project classes including dependencies and a (generated) Java Wrapper should be deployed according to common Java deployment practices for the particular deployment target.

Deploying Standalone Webstudio with a single Demo project

Note: This procedure requires that your eclipse plugins and workspace folders were located in the same parent eclipse folder. Otherwise required plugins can not be properly copied into the new location with preserving relative paths

In project org.openl.rules.webstudio locate launch file Make Standalone Webstudio.launch and run it using right-click menu Run As. This will copy webstudio and required plugins into location defined by variable targetDir in file build/make.standalone.webstudio.build.xml. This procedure will also generate file workspace/StartWebstudio.bat that can be used to start the Web Studio

To deploy the demo project with all the necessary dependencies copy file org.openl.rules.webstudio/Deploy ${some.project} To Standalone Webstudio.launch into demo project folder. Replace ${some.project} with the name of the project in file's name and all the occurrences inside the file using text editor. The run the file using right-click menu.

To run Web Studio switch to ${targetDir}/workspace and run StartWebstudio.bat. Also you can zip targetDir and deploy it on any other computer as a stand-alone application