Define Components & Component Subsets

CodeMRI® Sys Admin Training Videos:

Define Components & Component Subsets

CodeMRI® has the ability to let the user define groups of files and name them as components, and then generate blueprints based on those components. If we look at this, uh, in order to create a component, you would issue the command system component add,-- and then give your component the name, --expressions, and then provide a relative path to where the file group lives.

Each one of these files will be tagged with the component name that you choose to remove a component. It's a similar command system component remove --name, give it the component name, --expressions and give it the path to where the file group lives. Some usage for this, you could do the system add command, giving it the same component name on different subdirectories, and that would group all the files in these various directories into the same component.

You could also issue. A single command with your component name. And for expressions, you could provide a comma-separated list of the relative directory paths to where these files live. Another usage of the add and remove command is imagine you have a directory of files that you want to classify as a component.

Within that directory, there's a subdirectory of files. Which make up their own component and so you would like those to be named as their own component. You can do system component add, give it a component name, and then give it a relative path to the directory, and then system component. Remove from the same component name, but this time give it the subdirectory that's within the original directory.

That will, in effect, take all the files that are in that subdirectory and remove the tag of the component name. Then you could do system add and give it a new component name, and then give it that same subdirectory. It would then go and re-tag those files with a new name. Along with defining components, you can define relationships between the components.

You do that by entering system component dash relationship add and then -- from, and give it the name of the component where the relationship starts, and then a -- to, and then give it a comma-separated list of component names that will define a relationship between components for a code MRI purposes.

If you want to verify this, you can type in system architecture verify. That will give you a list of. What's been flagged as an error or a warning, or just information about the definitions. To view the components that you've defined, you can type in system component list, and that will give you a list of all the of all the components that have been defined.

If you want to see the relationships that have been defined, you can type in system component -relationship list. Um, if you want to verify that all the files have been tagged, you can rerun job run, produce reports, and that will produce all the reports. And then you can look in the file tab and you will see the component name next to each file that it's been assigned to.