MettleCI Compliance Rules are delivered as a zip file containing a ready-to-use Local Git repository. This means you can install and run Compliance Rules simply by unzipping the file to your DataStage Engine’s file system, without necessarily requiring a Git server to host a Remote repository.
Creating you Local Repository
You can configure your local repository like this:
$> # Start in your MettleCI home directory (default: /opt/dm/mci/) $> pwd /opt/dm/mci $> # SCP/FTP the compliance zip file from your download media to this directory $> ls -l dm-compliance-rules-59.zip -rw-r--r-- 1 root root 38578 Jan 13 11:41 dm-compliance-rules-59.zip $> # Unzip it. This will create a subdirectory /opt/dm/mci/compliance. $> unzip dm-compliance-rules-59.zip Archive: dm-compliance-rules-59.zip creating: compliance/ inflating: compliance/One Dataflow.sjb.grm inflating: compliance/rules.cfg inflating: compliance/Link Sort.pjb.grm inflating: compliance/Range Lookup.pjb.grm creating: compliance/.git/ # etc. $> ls -l compliance/ total 128 -rw-rw-r-- 1 ec2-user dstage 1478 Jan 8 15:59 Adjacent Transformers.pjb.grm -rw-rw-r-- 1 ec2-user dstage 3246 Jan 8 15:59 CCMigrateTool Stages.pjb.grm -rw-rw-r-- 1 ec2-user dstage 2227 Jan 8 15:59 CCMigrateTool Stages.sjb.grm # etc. $> # The compliance directory is a local Git repository of default Compliance Rules $> cd compliance $> git status # On branch master # # Initial commit # # Untracked files: # (use "git add <file>..." to include in what will be committed) # # Adjacent Transformers.pjb.grm # CCMigrateTool Stages.pjb.grm # CCMigrateTool Stages.sjb.grm # etc. $> # You're ready to go! Now ensure that your Workbench uses a 'file:'-prefixed reference to refer to this Local repository
Using a Local Repository
To set MettleCI to use a local Compliance repository for your DataStage project you just need to point Workbench to the appropriate repository directory. Under your user icon (top right) in Workbench select Manage Projects , edit the settings of the relevant project and for Compliance Repository set the URL field to an appropriate value following the examples below:
file://C:\MettleCI\compliance\.git
WINDOWS
file:///opt/dm/mci/compliance/.git
UNIX
In all cases leave the Branch field as master
and the Path field empty.
Note that if you use this technique to point to a Local Git repository you’ll be running Compliance against the version of your Compliance rules stored locally on your DataStage Engine tier. This approach does not easily support the collaborative development or maintenance of Compliance rules. For that, it is recommended to use a Remote Git repository served by a Git server.
See also
To migrate your Local Git repository to a shared Remote Git repository see these instructions.