This procedure shows you how to adapt a default mask definition to define a new mask. As an example, the PLMProductDS.metadata file derives from PLMCORE metadata, and you want to adapt the DEFAULT mask definition of the PLMProductDS modeler for designers to create a Designer mask.
If you create a custom metadata file, use the VPLMPosMaskGenerator tool to generate the corresponding mask file. For more information, see VPLMPosMaskGenerator.
-
Modify the mask file.
- Copy PLMProductDS.mask file from:
<ENOVIAPlatformServer_WEB-INF>/classes/vplm/mask/DEFAULT
to : <MyCustomization_root>/vplm/mask/Designer directory
If <MyCustomization_root> is not <ENOVIAPlatformServer_WEB-INF>/classes, this directory must be specified to the mask compiler using the -addpath
option.
- Edit the PLMProductDS.mask file to meet your requirements:
- Modify accesses
- Replace MASK DEFAULT by MASK Designer
-
Compile the mask file:
PLMPosMaskCompiler -m Designer -d /tmp/masks -html /tmp/masks/html -addpath <MyCustomization_root>
- The Designer.SecurityMask file is generated in directory /tmp/masks, as well as the result.log file.
- Html files are generated in /tmp/masks/html.
The modelers index file is_index.html and lists all processed modelers and the number of errors.
- Deploy the mask file.
With write access on the server runtime view, copy the Designer.SecurityMask file from /tmp/masks
to:
Tomcat: <apache_root>/webapps/ematrix/WEB-INF/classes/vplm/mask