|
A Processing Unit should follow a certain directory structure in order so it can be deployed with Processing Unit containers. Here is an example of a Processing Unit (loosely based on the data example): -data-processor |----META-INF |--------spring |------------pu.xml |----org |--------openspaces |------------example |----------------data |--------------------processor |------------------------DataProcessor.class |----lib |--------commons-math.jar |----shared-lib |--------data-common.jar The above example shows a Processing Unit directory composed of several sections. The first is the META-INF section which includes the Spring context XML configuration called pu.xml (this is the default location of the Spring configuration used by all containers). The second section is the Processing Unit application class files, which exists directly under the Processing Unit root directory. The third section includes third party jar files that are used only by the Processing Unit. The example shows commons math which might be used for different mathematical computations. The fourth section includes jar files that are shared between the Processing Unit and other Processing Units or spaces. In the above example, the data-common.jar includes the domain model written to the space and a shared interface (when using OpenSpaces remoting) between the processor PU and the feeder PU. The standalone container and Service Grid container supports the above structure. The integrated container has a sensible default only for the pu.xml location (which can be overridden) which follows the above structure, the rest is assumed to be configured externally. |
Previous release
Add GigaSpaces wiki search to your browser search engines! (works on Firefox 2 and Internet Explorer 7)
