TYPICAL DEPLOYMENT SCENARIOS

By only keeping to one deployment scenario during development is not practical as differing deployments may and will bring their own problems. By having the answers to the problems prior to providing client installations will allow for a smoother implementation, a tested choice of deployment options that are flexible to the client’s requirement and scale as the client grows.

a. Low-end (or the cheep client)

• The low-end deployment will provide the client with options that require no additional outlay over and above the cost of the application. This would be deployed on freely available open source software, that would conform to all the industry requirements.

> Top <

b. High-end (or we like this client)

• The high end deployment would be looked at as a 24/7 installation, the application is mission critical and is required to be available at all times.#

> Top <

c. Linking to existing database

• There will exist clients that would like to see direct connections onto their existing UniVerse database. This deployment situation will add a new level of complexity into the equation that will be satisfied through the use of RedBack. Connecting to a UniVerse database from an external application through a RedBack gateway provides the same flexibility in scalability that is give to other database products like DB2, allowing for pooling of connections and other performance enhancements reducing the overhead on user licenses and removing the connect disconnect lag from the application.

> Top <

d. 2-tier deployment

• There will probably exist the requirement for a 2-tier deployment, this will be taken care of in the following manner.

• By examining the proposed deployment scenarios the majority of configurations that would be required can be configured from tried and tested solutions. Giving this flexibility to clients allows for them to modify the deployment scenario over time and as their requirements change.
• Providing a multiple tier design 2-tier, 3-tier and n-tier allows the client to scale the application over time with essentially no change to the software that they would be running. 

> Top <