Two methods can be employed for deploying a service:
HTTP Post method sending a DAR file as a parameter.
Decompress a DAR file directly in the Serventdeploy directory.
A DAR file is, in fact, a ZIP file which contains libraries and information (something similar to the usual JAR, WAR or EAR file).
The information inside the DAR file must be organized in a specific way to be understood by the Servent at deployment time. The only mandatory file inside the DAR file is the deployment.props file which specify the Adapter (DBEService) to be used.
/-- deployment.props |- service-impl/ | |- classes/ | \- lib/ |- META-INF/ | \- ServiceManifest \- service-chain/
deployment.props: | This is the properties file where there is the information about the service and the deployment issues |
classes: | In this directory usually there are, extended, the classes that are part of the DBEService (the service itself) |
lib: | This directory contains any extra or third party libraries needed by the DBEService |
ServiceManifest: | Is a document containing the BML definition + SDL definition + specific data (about the company, I guess). The ServiceManifest is also known as SM |
service-chain : | This directory will be used, in short, to store .BPR files needed by composed services |