Each module in MIP is a part of a package. Packages provide a way to “group” related modules and make a prioritization scheme for each “group”. To learn how to create a package please read the how to make a package tutorial.

Cluster names are used to make relationships and bindings in MIP. This information is used by MIP Integrator and the MIP Producer's. (Note: Clusters are actually related to Packages, but each module is a part of a package, so naturally modules are associated with Clusters) For a more in depth explanation of the Cluster name abstraction and their use please review the how to make a package tutorial.

Additionally MIP uses the following variables to reference locations: (these variables are located in the $configdir/source.pl file)

We will start with “Name”. Assume the Name of the Computing Element is the same as the Unique ID of the Computing Element. Remember from above: The Parents Unique ID is the second command-line argument passed to the module. So the start of the script will look like this:

Lastly we will get the GateKeeperPort. Let us say the port number is in the package's configuration file, which is also written in perl. Assume the example configuration file is named “example-conf.pl” and is located in the $configdir. It contains the following information: