OpenL Web Studio consists of the following main components:
OpenL Web Studio components |
|
---|---|
Component |
Description |
Rule editor |
Graphic user interface running in a web browser allowing users to browse rule modules, modify table data, and run tests. Rule editor is the default user interface displayed when user opens OpenL Web Studio. Rule editor does not display all rule module files but provides a logical view of rules stored in a module. This view is convenient for users who modify business rules. Rule editor displays only modules available in projects stored in user's workspace. To retrieve a project to user's workspace, the project must be opened or checked out. For information on opening and checking out projects, see Working with Projects in OpenL Web Studio. For detailed information on using rule editor, see Chapter 3: Using Rule Editor. |
Repository editor |
Graphic user interface running in a web browser allowing users to browse and manage projects in design time repository. Unlike rule editor, repository editor displays physical contents of rule projects. Users can easily switch between rule editor and repository editor in user interface. Repository editor provides the following main functions:
For detailed information on using rule editor, see Chapter 4: Using Repository Editor. |
Design time repository |
Centralized storage of rule projects accessible by all OpenL Web Studio users.Projects uploaded to design time repository are visible to other users. Design time repository creates a separate project version each time a project is checked in. A project can be restored to any of its previous versions if it is checked in with incorrect data. |
Production time repository |
Centralized storage of final rule projects delivered to the production environment where solution applications use them. Projects can be deployed to production time repository from design time repository using deployment projects. A deployment project is a specific OpenL Web Studio project type. It stipulates which rule projects and project versions must be deployed to production time repository. Deployment projects are saved and versioned so that developers can identify which specific rule project versions are deployed. In the context of Exigen Process Backbone, the Exigen Studio run-time repository is used as production time repository. |
User workspace |
Project storage on the server containing projects checked out by users. Each user has a personal workspace not accessible by others. |