Developing Apama Applications > Developing Apama Applications in Java > Developing and Deploying Java Applications > Creating deployment descriptor files > Defining monitor classes in deployment descriptor files
Defining monitor classes in deployment descriptor files
The deployment descriptor file must define a monitor element for each monitor class in your Java application’s JAR file. Each monitor element must contain the following two elements:
*monitor-name — The name by which this monitor is to be defined within the correlator. The correlator has a single namespace. Consequently, this name must be unique across all applications. For example, SimpleMon or SimpleApp.SimpleMon. If you specify a package qualified name, it is the qualified name that must be unique.
*monitor-class — The name of the Java class in which this monitor is defined. This must correspond to the fully qualified name of the class, for example, SimpleMon if the monitor class is defined within the default Java package, or com.apama.example.monitors.SimpleMon if the monitor class is defined in the com.apama.example.monitors package. The file, for example, SimpleMon.java, is expected to be located within a folder structure that maps to the packaging, as per standard Java convention.
The monitor element can optionally contain a third element. This is the description element. Specify a description of the monitor. For example:
<monitor>
   <monitor-name>Simple</monitor-name>
   <monitor-class>Simple</monitor-class>
   <description>A simple java monitor, used to show functionality of
      a new installation.</description>
</monitor>
Copyright © 2013 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.