Building and Packaging
Once everything is ready, we need to build, package and deploy the application. The following jar files need to be in your classpath, they all reside in the <GigaSpaces Root\lib directory or its subfolders:
In order to deploy the application, we need to deploy each of the three processing units separately. To do this, every processing unit must be placed in the <GigaSpaces Root>\deploy directory. Every processing unit is actually a folder (whose name is the name of the processing unit later used for deployment) with several subfolders. Here's a typical processing unit directory as it resides under the <GigaSpaces Root>\deploy directory: As the image shows, under the deploy folder of the product, we've put the oms-feeder folder which is in fact our feeder PU of the application. The folder name states the name of the processing unit. Under META-INF\spring is our pu.xml file, relevant for the feeder processing unit. Also, directly under the deploy folder is our compiled code, with its appropriate package structure (that's the org folder seen in the image). Finally, the shared-lib includes all those libraries that are used globally by that processing unit and potentially other processing units. In this case, shared-lib includes a jar file that includes our domain model (account and order) objects as well as the DAO. The same jar is put under the shared-lib folder of each of the processing units in our application. To summarize the building and packaging process:
|
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |