Engineering Method Composer command line options

Engineering Method Composer has a number of command line options that configure how MEC behaves when launched. MEC can also be executed from a batch script, and the command line options can be used to performed repetitive operations, such as publishing. This topic describes each of the command line options, and what it does.

MEC is launched from the command line as follows:

<install directory>eclipse.exe -product com.ibm.rmc.rcp.ui.75.composer parameters

where parameters can be:

-data workspace path

or

-rmclibrary library path

MEC always opens a library when launched. You can either specify a workspace-based library to open, or a standard library.
  • "-data workspace path" is used to open a workspace-based library
  • "-rmclibrary library path is used to open a standard library

If no library is specified, the default library is opened (the MEC Practices library that is installed with MEC).

-nl language

Specify a language to use. Language choices are:

ar - Arabic

zh_CN - Chinese (Simplified)

zh_TW - Chinese ( Traditional)

pt_BR - Brazilian Portuguese

da - Danish

de - German

fr - French

it - Italian

es - Spanish

ja - Japanese

ko - Korean

po - Polish

ru - Russian

Refer to the release notes for the MEC version to identify what languages are supported, what has been translated for each language, and how to install the different languages.

-rmcsilent

Indicates that MEC is to execute in batch mode. It must always be followed by another argument indicating the type of operation. At this time, the only operation we officially support for batch mode is publishing, and the key word for it is "publish":

publish -rmcconfiguration configuration name -rmcoutput output path -rmcsearch [php|php-zend]

MEC will publish the specified configuration to the specified output path location, and then exit.

"rmcsearch" specifes the search option to set for publishing, with choices of "php" and "php-zend". If the "rmcsearch" option is not specified, the search option defaults to "Applet".

In addition to these MEC-specific command line options, there are many command line options inherited from Eclipse. These are documented in the Eclipse online help (topic "Running Eclipse").

The most useful ones are:

-clean

Cleans cached data used by the OSGi framework and Eclipse runtime. Try to run Eclipse once with this option if you observe startup errors after install, update, or using a shared configuration.

-refresh

Option for performing a global refresh of the workspace on startup. This will reconcile any changes that were made in the file system since the platform was last run.

-vm vmpath

The location of Java Runtime Environment (JRE) to use to run the Eclipse platform. If not specified, the launcher will attempt to find a JRE. It will first look for a directory called jre as a sibling of the Eclipse executable, and then look on the operating system path. Relative paths are interpreted relative to the directory that eclipse was started from.

-showlocation

Option for displaying the location of the workspace in the window title bar.

Example:

This is an example for publishing the "all_practices-ibm" configuration in German (-nl de):

"C:\Program Files\IBM\MEC76\eclipse.exe" -product com.ibm.rmc.rcp.ui.75.composer -nl de -rmcsilent publish -rmclibrary "C:\rmclibs\lib.7.5.1.2.prac" -rmcconfiguration all_practices-ibm  -rmcoutput "C:\publishing\de\all_practices" -rmcsearch php

This is the same example, using a batch file and some variables:

set rmc_executable_location="C:\Program Files\IBM\MEC76\eclipse.exe"
set library_location="C:\rmclibs\lib.7.5.1.2.prac"
set lang=de
%rmc_executable_location% -product com.ibm.rmc.rcp.ui.75.composer -nl %lang% -rmcsilent publish -rmclibrary %library_location% -rmcconfiguration "all_practices-ibm" -rmcoutput "C:\publishing\%lang%\all_practices" -rmcsearch php
Feedback