Apama 10.15.0 | Developing Apama Applications | Developing EPL Plug-ins | Writing EPL Plug-ins in Java | Creating an EPL plug-in using Java
 
Creating an EPL plug-in using Java
 
Permitted signatures for methods
*To create a Java class to use as an EPL plug-in
1. In the Java class used as a plug-in, you need to have one or more public static methods that match the permitted signatures, which are described in Permitted signatures for methods.
All calls from an Apama application are made to these static methods from all contexts.
As the plug-in author you are responsible for any concurrency concerns.
2. You need to create a deployment descriptor file in the plug-in's META-INF/jmon-jar.xml file. For the plug-in, you need to add a <plugin> element to the <application-classes> element. For more information, see Creating deployment descriptor files for EPL plug-ins written in Java.
Instead of writing a deployment descriptor file manually, if you are using Software AG Designer to create the plug-in, you can annotate the plug-in class and have Software AG Designer automatically generate the descriptor file. For more information, see Inserting annotations for deployment descriptor files.
3. Create a JAR file for deploying the plug-in and add the Java class file and the deployment descriptor file META-INF/jmon-jar.xml to it. In Software AG Designer when you create an EPL plug-in written in Java, this is done automatically.