Download and Installation Guide
Before you start, it's important to to check about the dependencies.
- Resoa is developed and tested with Java 1.6, please check the version of your your local Java installation and ensure the correct setting of the JAVA_HOME system variable.
- Resoa maintains the dependencies to other open source projects within an ARTIFACT folder structure, which is included in the distribution packages. You must define a system environment variable so called RESOA_ARTIFACT, pointing to your local ARTIFACT folder. If you work with Eclipse, define RESOA_ARTIFACT variable there as well.
What is inside Artifact?
The java folder:
- java/common: Here you find all jar’s of external projects, Resoa depends on.
- java/resoa: The Ant based build system optionally copies the generated JAR’s to Artifact as well. If you re-build a project, ensure that the newly generated JAR is copied to this folder, otherwise you will not see the changes in your runtime environment.
- java/resoa/service: If you develop a new business domain, place the JAR with all service stuff inside this folder, so it will be automatically available on Java classpath during runtime.
- java/resoa/test: This folder is used for testing stuff.
The script folder contains the start scripts for Resoa nodes. The ResoaInfoBuilder will copy these scripts into the grid topology configuration folders.
The xsd folder should be the home of your business service model XSD files. The resoa subfolder contains the XSD's, Resoa uses internally.
How to prepare the Business Service deployment
You should declare a system variable called RESOA_PROJECTS pointing to the root directory of your Business Service projects.
Beside your personal projects you maintain the grid topology configuration here. Create a folder named topology, it is the root folder for your grid configuration used by the deployer tool ResoaInfoBuilder.
Every grid is represented by a subfolder there, these grid folder again need the following folder structure:
- controller: The topology is maintained by controllers (a specialized node). Create a folder for every controller host.
- node: Do the same for every business service container node here.
- rest: Again, create a folder for every REST server within the grid.
- client: Define other Resoa client hosts here (like console testers, etc.)
Read more about within the Grid configuration abstract, it shows how the ResoaInfoBuilder deployment tool will generate a "ready to run" environment.