Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • normal:  The normal launch tool, most programs use this one.
  • agent: Use this when launching an agent. 
  • runall: Use this when creating a launch tool that runs the checked launch tools (see Launching Multiple Programs at Once).
  • first_wait: Use this when launching with a runall type to delay time before the next checked program launches.  This is useful for programs such as the UT Server that takes time to start up.  Multiple first_wait programs can be used with each subsequent program launching after the time specified.
  • wait:  Use this when launching with a runall type, it wait however many seconds that you specify after launching this program.
  • logger = This is a special logging tool that is started automatically when the tool is launched.
  • wait_component = This makes the component wait on the specified component (whose value (elvin-name) is specified in the Wait Component).   It's also possible to specify the time in 'seconds after the wait component is launched'. 

...

  • "Edit <tool name>": Opens the Editing dialogue for the launch tool.
  • "Clone <tool name>":   Opens the Creating dialogue, but the new tool will be pre-populated with the data from this launch tool.
  • "Switch to Build Mode": Makes this launch tool use the 'build' version of its program.
  • "Switch to SVN Mode": Makes this launch tool use the 'svn' version of its program.
  • "Set as not Launched": Sets this launch tool as not being launched..

Launching a program locally

Assuming that To launch a specific program locally, find the program uses the correct VHMsg messages, it will highlight green while it is running. The on the Launcher and click on its pull-down list after "Machine:" argument is the computer that the program will be launched on and should be either to choose either "localhost" or the name of your computer or 'localhost'. Click the local computer.  Click the "Launch" button to launch a program and the or "Kill" button to close it. Make sure that if you have a VHMSG_SERVER environment variable then, it is set to localhost or the name if your machine.either launch or close the program locally.  If the program conforms to VHMsg messaging, its row on the Launcher will highlight in green when it is running. Note: If there is a VHMSG_SERVER environment variable, it must be set to "localhost" or the name of the local computer. 

Launching a program remotely

This is done just like the same as launching a program locally, except that you should select the name of the remote computer in from the "Machine-Name" argument. The :" pull-down list.  The remote computer must be running the RemoteApplicationLauncher on the same VHMSG_SERVER and VHMSG_SCOPE as the Launcher. See   See the readme file for the RemoteApplicationLauncher for more details. Make   Make sure that the machine which runs the remote launcher has the environment variable VHMSG_SERVER, which should be set to the machine which is running the Launcher.  If not using remote launchers, you do this variable does not need to be set this variable.

Launching and quitting multiple

...

programs

To launch multiple programs, check the boxes next to the programs to be launched and click the top "Run Checked" green "launch" button.

To quit multiple programs, check the boxes next to the programs to be quit and click the top "Run Checked" red "quit" button.

To quit all running programs, click the top "Run Checked" red "quit all" button.  Note: This will quit all running programs whether or not their box is checked.

In addition, a Master Profile can be created to run other launch tools.  This will launch any program with a checked check-box.  If this is a first_wait type of program, it will honor the delay (see above about Creating/Editing Launch Tools).  Additionally, it will launch the programs on the machine that is selected in the machine argument of each launch tool.

Launching programs that do not conform to VHMSG messaging

If the program you are launching a launched/running program does not support VHMSG VHMsg messages, it its row will not highlight green on the launcher while it is running (it will be orange instead). It highlight in orange not green.  It will not respond to the "Kill" button so you will have to close it yourself quit" or "quit all" buttons.  This program needs to be closed manually instead of from the launcher. If   If the program is an exe (or possibly other types) you can use the ElvinAppWrapper program. ElvinAppWrapper lets you "wrap" a program that does , use the ElvinAppWrapper program which enable programs that do not support elvin messages to respond to the messages required by the launcher. You can find more info in Launcher.  For more details, go to the ElvinAppWrapper readme file.

Using

...

VHMsg messages to work with the Launcher

It should The application needs to have an "elvin-name" (now called the "vhmsg-name") that it will use for all messages. On start up it should say .  Note: the application's "elvin-name" needs to match the Master Profile's "elvin-name".  On startup, the application should say, "vrComponent <vhmsg-name>". When ; when it receives a "vrAllCall" message it should say "vrComponent <vhmsg-name>". When ; when it receives a "vrKillComponent <vhmsg-name>" message it should say "vrProcEnd <vhmsg-name>" and then exit. If it   If the application is an agent, then it should listen for "vrKillAgent <vhmsg-name>" instead of "vrKillComponent <vhmsg-name>". If a program only does some of the above, then it   An application will only partially work with the Java Launcher, if it only does some of the aforementioned.

Things to know

  • If a launch tool is the normal gray color of the Launcher window, it is not running. 
  • If a launch tool is green, then it is running and sending the appropriate VHMSG messages. 
  • If a launch tool is orange, then it is running but there is possibly a problem. Either the program is not responding (i.e. it crashed) or it does not respond correctly to the vrAllCall message. The launcher can sometimes show a component as unresponsive in error, so it is advisable to check the status of the component manually if problems persist. 
  • You can Click on a group name to expand/collapse a group by clicking on its name. You can it.
  • To send a VHMSG message by typing it , type the message into the text box at the bottom of the window and clicking click the "Send" button. It   It has been tested with launching .bat files, .jar files, and .class files, and any .  Any properly formatted VHMSG should work.

...