Skip to Main Content U.S. Department of Energy

MIF Deployment Instructions


Deploying your application to a MIF Server Instance

Unless specified otherwise, these instructions assume that the commands are executed from $MIF_HOME

Linux Instructions

Add your jars to the MIF Server instance

  • Package your applications into a jar file.
    • Do not include any MIF dependencies (ie, libraries needed by MIF) in the jar. The MIF dependencies are already include in the MIF installation.
    • Do not include any of your application's dependencies in the jar. These should be added as separate jars to the MIF installation
  • Place your application's jar in $MIF_HOME/app
  • Place your application's dependency jars in $MIF_HOME/app
NOTE: The MIF start scripts specify $MIF_HOME/app/* as the classpath, so all jars in that directory will be automatically included in the MIF classpath

Start MIF in Server mode

To start MIF in server mode, you use the “ start” command and provide the name of your main class with the ”-c” option. For example:

bin/ start -c fully.qualified.main.ClassName

For example, to start the HelloWorld pipeline, we specify the main class like this:

bin/ start -c gov.pnnl.mif.samples.hello.stdio.HelloStdioDriver

After running this command, you should see output like the following:

Starting MIF...
MIF was started, logging to: /home/d3p299/local/mif/mif-3.1.1/log

To monitor the log file:

> tail -f log/mif.log 

This should produce output ending with:

2012-03-28 08:27:00,376 INFO  [gov.pnnl.mif.internal.MifManagerImpl] storing PID: /tmp/
2012-03-28 08:27:00,380 INFO  [gov.pnnl.mif.internal.MifManagerImpl]  -- MIF has started --

Then to stop the MIF server:

> bin/  stop
Trying to kill MIF process
MIF was stopped

To check on the status of MIF:

> bin/  status
MIF is not running

Windows Instructions

Please contact if you need these instructions

mif_deployment_instructions.txt · Last modified: 2012/03/28 08:31 by adamw