Multiple Production Environments for separate applications


Good Day!!

We have the requirement to have two applications to be deployed to two different production servers in the same environment.

For example : Application 1 code has to be deployed to Production 1 server. Application 2 code to Production 2 server. Development and Quality servers will have code of both applications.

Please help me with the below.

How can we manage deploying Application 1 code from Quality to Production 1. Is there any affect on database entities in such server setup? 

Is it possible/recommended to have the above set up?

What are the risks/challenges of having the above server set up.




CMIIW, if you using lifetime, you cannot bypass what already specified by lifetime environment.

But, you can create solution on dev from service center, then deploy that solution on the production 2.

Hi sai charan,

Let me just start by clarifying some OutSystems terms, so we can all be on the same page:

When you talk about Development, Quality and Production, you are talking about OutSystems environments. An environment can have multiple servers, all using the same environment database: different environments = different databases

An OutSystems infrastructure is a set of environments under the same licensing contract (the number of environments possible, and the characteristics of each is part of the licensing deal).

LifeTime manages the entire infrastructure, allowing you to deploy your applications between any two environments. It is most useful when your environments form a pipeline (for instance Development->Quality->Production).

Now, do you want your two applications to be installed (a) on two different servers of the same environment?, or (b) two different environments in the same infrastructure?

For (a) you can look into Selective Deployment using Deployment Zones, both your applications will be using the same database and tables (they will be able to share data) but please not it is not available for Cloud environments managed by OutSystems.

For (b), provided your license allows it, you can add a Production 2 environment to your infrastructure and set it up after your original Production 1environment in LifeTime (something like Development->Quality->Production 1->Production 2). This allows you to deploy from Quality to either (although LifeTime will always default to deploying to Production 1). If each of your applications is deployed to a different Production environment, they will be using distinct databases.

Hope this helps