Share rule documents across projects

There are three ways to share Oracle Policy Modeling documents across projects:

Multiple projects in folder structure

It is possible for more than one Oracle Policy Modeling project (and corresponding .xprj file) to co-exist in one location. Each project keeps track of which documents are to be included when compiling the application. Both .xprj files should sit side-by-side in the Development folder (which, in turn, contains the folders Rules, Test Cases, etc.).

With this set-up, only the project file is duplicated, and so any change to any rules or xsrc files will take effect in any project that incorporates them. Individual rules or xsrc files can be removed from the project. Alternatively, files can remain in the project but be excluded from the build.

To be in the compile set, a file must be in the project, and to be in the project, a file must be in the folder structure. Source control operates as usual for a single application.

 

 

This method of sharing files between projects is particularly suitable where two versions of an application are required (ie a complete version and a "Lite" version). In these situations, the rules and xsrc files are organized into the same structure. The projects differ only by the inclusion or exclusion of the various source files they comprise.

Share files in source control

Another method of applying the rules and/or xsrc files in a Oracle Policy Modeling project is to duplicate the files in the file system but synchronize them in source control.

 

 

This method of sharing files between projects is suitable where selected rules and/or xsrc files in one main application can be isolated into particular file/s and introduced into another application which shares some of the same subject matter. It is possible for files to become out-of-sync on individual computers under this method, if the source control procedure is not strictly adhered to.

Duplicate files in source control

Finally, the entire project can be duplicated and maintained separately in both the file system and in source control.

 

 

This method does not so much share files between applications, but rather involves a "branch" in the evolution of the project, and is suitable where the source files in one project are useful merely as a starting-point for the other project, for example, where the projects are (at least partly) based on the same source material, but require different analyses for their own purposes. All maintenance and source control occurs separately, since these projects are effectively separate applications once the branching has occurred.

 

See also