Each installation binds on a separate IP address and listens on the Standard Application
Server port(8080) with the option to listen on the Standard HTTP port (80).

Using any combination of the deployment methods listed above, you are able to
. Specify a default Application Server
. Specify a default JDK Version
. Specify a default Application
. Specify a default MailSession
. Specify a default JDBC Realm for authentication
. Specify a default DataSource
. Dynamically create the Database and connection value for each JVM's Datasource
e.g. for JVM 1: jdbc/mydata may look like:
username="saasuser_1" password="tiger" url="jdbc:mysql://localhost:3306/saasuser_1
while JVM 2: jdbc/mydata may look like:
username="saasuser_2" password="tiger2" url="jdbc:mysql://localhost:3306/saasuser_2
. Dynamically assign a specific IP address from an IP Pool to a JVM
. Deploy a specific JVM
. Undeploy a specific JVM

How does this Framework help in the real world?
Suppose you have an application, and you would like to sell it using the SaaS model,
The following are the scenarios to automate and lower your deployment costs:
1)Customer purchases the SaaS service online.
2)The payment script hooks into the NGASI Open API and is able to deploy and start
the customer's service, all with little or no human intervention.
The JAVA SaaS Hosting solution enables the application service to function as a separate system from the end customer's web site. For example the application could be a ticketing solution linked from the end user's web site. Or it may be for a company's internal use, such as an accounting application. Although all of the functions can be performed from the web control, the comprehensive set of APIs and scripts were developed to automate a full scale SaaS service.
User Guide