Server User Guide

9.2.5
- 9.2.4.6

Back Next

Packaging the Custom Invoke Handler as an EJB

If your custom invoke handler is an EJB, you must package the EJB and other files into an EAR archive.

Packaging includes the following:

JAR files for the custom invoke handler

Deployment descriptors

Service Implementation Bean class and their dependent classes. These files are

ae_wsio.jar

ae_awfwsio.jar

, and

qname.jar

Sample EAR package

META-INF
      Manifest.mf
          jboss-app.xml
          application.xml
          name.jar
          customInvokeSample.jar
          ae_awfwsio.jar

The following table describes the contents of the sample EAR file.

Web Application File	Description
META-INF Manifest.mf	Contains meta-information about the EAR file and can also contain information about the other files that are packaged in the archive. This file name and pathname are required for an EAR file.
jboss-app.xml	A representative configuration file from a J2EE server, in this case JBoss
application.xml	Descriptor required for the EAR file
customInvokeSample.jar	Custom Invoke handler referencing the IAeInvokeHandler implementation
ae_wsio.jar	Contains the core interfaces used to send messages to the engine. The file is located in the Process Server EAR file.
ae_awfwsio.jar	Contains the required interfaces for interacting with the Process Server EJB. The file is located in the Process Server EAR file.
qname.jar	Required for handling WSDL. The file is located in the Process Server EAR file.

Rename Saved Search

Table of Contents

Server User Guide

Server User Guide

Packaging the Custom Invoke Handler as an EJB

Packaging the Custom Invoke Handler as an EJB