RADE

Principle

The Configuration management enables you to establish and maintain variations and alternative versions of your product structure. Configuration applicability is carried by each item instance within your product structure. Subsequently, when you open a product using a particular configuration filter, the applicability criteria you specified determine whether a given item instance is included in the view. When a product is associated with a specific configuration, it is considered to be under configuration control.

But, according to their applicative products, customers may need new fields to take internal processes into account for example.

In the example below, you are going to customize a Config. This use case shows a customization of the whole modeler, that is to say, all entities will be customized. You have to remember that  it is not mandatory to customize all classes to customize the Config modeler. The following principle graphic explains what to customize relating to what you want to do:

You are going to add an attribute to each customized class:

• a string internal_ref to MyCategory

• a date CustoAttr1 to MyExpressionrule

• a boolean CustoAttr2 to MyInclusionRule

• a boolean CustAttr3 to MySpecification

[Top]

Creating a UML Project

1. From the File menu, select New->Other->UML Project. Click Next>.
2. Enter the name of the UML project. Click Next> and Finish.
3. In the Navigator view, right-click your project and select Open as a DMC Project.
4. In the Open a DMC Project window, select the tool level and click Next>.
5. Click Close in the Initializing tools window.
6. Click Add and select your prerequisite frameworks. Click Finish.
7. Click Close in the Installing Prereqs window.

[Top]

Creating a Config Customization

1. From the File menu, select New->Other->DMC Elements->New LCA Customization. Click Next>.

2. Enter the name of the application, MyConfig in this example.
3. Click ... in the Customize LCA application field. The Select a framework dialog box opens.
4. Select Config and click OK.
5. Click Finish. The wizard creates a new workspace.

[Top]

Creating a Modeler Object

1. In the Navigator view, expand the MyConfig node and double-click the .emx file.

2. From the File menu, select Other->DMC elements->New Modeler Object. Click Next>. The New Modeler Object window opens.
3. Enter the class name in the Class name field, MyCategory in this example.
4. Select CATEGORY in the list. Click Next>.
5. Click Insert to add an attribute to your MyCategory. In this case, add a string called "Internal_ref".
6. Click Finish when done.
7. Repeat the above steps for the other 3 customized classes.

   INCLUSIONSPEC	EXPRESSIONSPEC
   CATEGORYSPEC	SPECIFICATION

[Top]

Generating the Dictionary File

1. Select DMC Project->Generate VPM Dictionary file.

The wizard creates MyConfig.metadata under the directory MyConfig/CNext/code/dictionary.

[Top]

Publishing Enovia Data

1. Select DMC Project->Publish VPM Dictionary file in Database.

[Top]

Check if the settings are correctly valuated and click OK to start the Publish command to finish the scenario.

Testing in ENOVIA

Now it is time to test your customization. To use this customization, launch ENOVIA with the environment of the customization. To do so, indicate the location where your customization is built on the server, as follows:

On UNIX:

$ENOVIA_INSTALLATION_PATH$/$OS$/code/command/enoviastart -direnv $EnvDir$ -env $EnvName$

where:

• ENOVIA_INSTALLATION_PATH is the location where you installed the ENOVIA CD.
• OS is the operating system tag (eg. solaris_a, aix_a, hpux_b).
• EnvDir is the environment folder containing the EnvName.txt file.
• EnvName is the name of the ENOVIA environment (Default name is ENOVIA_LCA.V5R17.B17).

On Windows:

$ENOVIA_INSTALL_PATH$/$OS$/code/bin/CATSTART -run "ENOVIA.exe" -direnv $EnvDir$ -env $EnvName$ -object "-senv $sEnvName$ -sdirenv $sEnvDir$"

where:

• ENOVIA_INSTALLATION_PATH is the location where you installed the ENOVIA CD.
• OS is the operating system tag (eg. intel_a).
• EnvDir is the environment folder containing the EnvName.txt file.
• EnvName is the name of the ENOVIA environment ( Default is : ENOVIA_LCA.V5R17.B17).
• sEnvName is the name of server environment contained in your new customization workspace (The default name is WorkspaceEnv)
• sEnvDir is the server environment folder containing the sEnvName.txt file.

Now, the new MyInclusionRule has a new field available: CustoAttr2.

And a search can be performed to find this object in the database.

Here is a sample of a customized category with a customized specification:

[Top]

History

Copyright © 2006, Dassault Systèmes. All rights reserved.