H-Sphere Merchant Gateway SDK comes with following directories and files:
gateway/build/ | directory for the class files generated by compilation of your java files |
docs/ | documentation for Merchant Gateway SDK |
gateway/etc/ | directory which contains the test-data.in file |
sdk-lib/ | includes MerchGatewaySDK.jar along with supporting jar files |
gateway/lang-files/ | directory for the language files |
gateway/lib/ | directory to place all extra jar files required by your Merchant Gateway |
gateway/src/ | directory to place all java files you will develop for your new merchant gateway |
| build.xml | the default Ant's build.xml file; in most cases, it will not require any changes |
| gateway/main.xml | deployment descriptor for the merchant gateway. It has to be altered as described in the Deployment Descriptor manual |
| gateway/log4j.properties | Log4j property file to control the level of logging |
| build.number | Tracks build number |
| hs-lib/ | This symbolic link can be set up manually to point to the H-Sphere's
java_rt directory with H-Sphere jar files if they are needed. To create the link, execute ln -s /path/to/java_rt hs-lib |
| hs-classes/ | This symbolic link can be set up manually to point to the directory with H-Sphere classes if they are needed. To create the link, execute ln -s /path/to/h-sphere/classes hs-classes |
Additionally to generation of the H-Sphere package, the package_name/ directory will be created (containing all package files required for the package), as well as the package_name-version-build.hsp file. That distributable H-Sphere package can be installed as an add-on to any H-Sphere 2.4+ installation. For the more info on defining package name, version and build number, see Deployment Descriptor.