Packaging and deploying a Java MDA component

 

Packaging a Java MDA component

Before a Java MDA component can be deployed, it must first be packaged. This operation allows to compress the Java MDA component, with its resources, in a file.

 

Java MDA components can be packaged by clicking on the  icon, defined in the “MDA” tab, from the Java MDA component.

 

Steps:

1.      In the explorer, click on the Java MDA component you wish to package.

2.      Click on the  icon. The “Java MDA component packaging” window then appears.

3.      Enter the version information.

4.      Enter an archive name and click on “Package” to confirm.

 

Figure 184. Packaging a Java MDA component

 

Default values are proposed so that the packaging can be run simply by pressing the "Package" button. These default values are as follows:

·         The default version number used for packaging is the version number that has been defined in the “Create an MDA component” dialog box.  Please note that this dialog box is also used to “edit” the MDA component (activation by double-clicking on the MDA component) and that the version number can be set to the proper value in this box. If you modify the version number in the packaging dialog box, the modified version will become the version number of the  MDA component in the project.

·         The default path and name for the packaged MDAC are defined as follows:

o        the value used the last time the MDAC was packaged

o        for the first packaging operation:  $WORKSPACE/$NAME_$VERSION.jmdac, where $WORKSPACE is the workspace dir of the MDA component, $NAME its name and $VERSION its version number.

 

MDA Modeler will check that the packaging name follows the rule that the version number appears just before the .jmdac extension. If this is not the case, a warning dialog is displayed, and you can confirm that you really want to violate the rule or else abort the packaging operation, in order to modify the chosen name of the archive. We highly recommend that you follow the proposed rule.

 

 

Deploying a Java MDA component in UML Modeler

When a Java MDA component is packaged, it contains all the information necessary to its deployment in UML Modeler, by guaranteeing that the versions of the different components will be compatible.

 

If the Java MDA component uses templates or patterns, the MDARuntime MDAC must also be selected in UML Modeler. This Java MDA component contains the template driver execution library, as well as the commands necessary to the application of patterns.

 

To deploy a Java MDA component, the “Deploy an MDAC” command is used (see “Working with MDACs”).