RADE

JAVA Interactive Dashboard

Workbench Commands Mapping

Correspondence between Workbench commands and RADE Dashboard or IRAD menus
Quick Reference

Abstract

This article has been written for those getting skills using Workbench commands [1], with Windows or Unix platforms. They will find here what are the menus corresponding to these commands and how command options have been mapped to graphic items such as check or combo boxes. This article can also be read if you want to work on Unix platforms where only shell commands are available. It is a way for them to find the commands hidden behind IBM Rational Software Development Platform (IRAD).

Some conventions are used in this article:

  1. Labels of buttons or menus which are extracted from IRAD are written using this format.
  2. Except for the commands written below in the summary, when command names appear as hypertext links, they refer to the corresponding command reference pages.

This article is divided into the following sections:

Setting up the Working Environment

In a DOS/shell Window From Interactive Dashboard

With Windows platform:

Execute the following commands to access mkmk:

  • tck_init.bat
  • tck_profile CXR17

With Unix platform:

Execute the following commands to access mkmk:

  • . tck_init.bat
  • tck_profile CXR17
  1. In the Navigator view, right-click a project and select Open CAAV5 Workspace.

[Top]

mkmk Commands

Setting Workspace Prerequisites

In a DOS/shell Window From Interactive Dashboard
There are two ways to set prerequisites: you can copy them into your workspace with mkCopyPreq or register the workspace containing them:
  1. mkCopyPreq: static access
  2. mkGetPreq: dynamic access

In the window displayed in the right side, the Copy prereq ... radio button corresponds to the mkCopyPreq command and the Use Prereq ... radio button corresponds to the mkGetPreq command. In this example, the corresponding command is:

mkGetPreq -p
  H:\BSF;E:\Program Files\Dassault Systemes\B17D04
  • From the CAA Project menu, select Get Prerequisites....

Note that the first directory you set in the list will be the first browsed when searching for prerequisites. You can change directories order by selecting a directory in the list and clicking the arrow Up and Down buttons.

You can specify additional options by clicking the Specify other options button, which is especially useful for the mkCopyFw command.

  • Access prerequisites from their orgin location: Gives you dynamic access (mkGetPreq).
  • Copy prerequisites from origin location to current workspace: Gives you static (mkCopyPreq) access.
  • Copy prerequisites from origin location to a local directory and acc: Combines both modes by copying your prerequisites in a directory different from your own (mkCopyPreq to an other directory, followed by mkGetPreq referencing this directory).

[Top]

Copying a Framework

In a DOS/shell Window From Interactive Dashboard
The command used to copy framework(s) from a workspace to another is mkCopyFw. Our sample dialog box corresponds to this command: 
mkCopyFw -update VisualStudio -d

Using the dialog box, you enter the path of the origin workspace(s) in the top list, then type the name of the framework(s) you want to copy (use <space> between two framework names), you can filter the modules to copy by clicking on the Add... button associated with the middle list (at least one framework name must have been typed in before).
  • From the CAA Project menu, select Copy Framework....

The check boxes in the Copy Options area correspond, from top to bottom, to the following options: -nm, -no, -d, -f, -update and -remove.

[Top]

Running mkmk

In a DOS/shell Window From Interactive Dashboard
Run mkmk with appropriate options regarding the current directory and what you wand to compile. For instance:
$ mkmk -ug EnoviaDMC
$ cd VisualStudio
$ mkmk -ug CATVBTDevBase.m

Advanced users can take benefit from the mkGMake tool to compile just one file or to link a library. This is faster than running mkmk. This feature is available in IRAD through the usual keyboard shortcuts which have been changed to run the CAAV5 builders: Ctrl-F7 and F7.

  • Ctrl-F7 starts the compilation of all source files in the current active project.
  • F7 starts the link of the project (module) corresponding to the source file currently active.
  • From the CAA Project menu, select mkmk
  • select mkmk options, select the various modules, frameworks or whole workspace that you wish to compile and type additional options if any.

[Top]

Create the Runtime View

In a DOS/shell Window From Interactive Dashboard
The command to build a Runtime View from a workspace is mkrtv

The items of the dialog boxes correspond respectively to -c, -d, and -k options of the command.
  • From the CAA Project menu, select Create/Update Runtime View....

[Top]

Replay test objects

In a DOS/shell Window From Interactive Dashboard
Test objects that are delivered in a test framework of CAAV5 workspace can be run using mkodt command.

The test objects selected in the right side of the dialog box are specified using -s option on the command line.
  • From the CAA Project menu, select Replay test-cases....

The following window appears displaying the test objects found in test frameworks of your workspace. Select which ones you want to run and click OK.

You can also define additional variables, to take them into account only during the replay.

[Top]

Accessing Commands without Associated Menu Item

Once a workspace has been opened (for mkmk and/or for Workspace Manager usage), any command launched from IRAD inherits environment variables and paths and thus can access mkmk or Workspace Manager commands. One command that can be run is the DOS interpreter. To do so, from the Window menu, select Open command window. In this window, you are able to access Workspace Manager or mkmk commands and therefore any command for which no interface is provided in IRAD.

[Top]

References

[1] Summary of Commands around mkmk
[2] Customizing >IBM Rational Software Development Platform
[4] Working with the RADE Dashboard
[Top]

History

Version: 1 [Jan 2000] Document created
Version: 2 [May 2003] Document updated
Version: 3 [June 2005] Document updated
[Top]

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