10 Deployment Architecture and Options

There are no physical location constraints on where bdi-<app> applications can be deployed as long as they are visible from the same network. But the decision on where to physically and logically locate your bdi-<app> applications has a huge impact on the high availability, performance and maintainability of your integration solution, so this decision must be given careful consideration.

Recommended Deployment Options

The BDI applications can be deployed in a variety of physical and logical configurations depending on the retailer's needs. Oracle Retail has the two recommended configuration alternatives.

Distributed

In this deployment, each of the BDI application (bdi-<app>.war) is deployed in a different WebLogic Application Server than the integrating application (<app>.ear) but it is physically close to the integrating application. This is the recommended configuration for production environment.

Figure 10-1 Distributed Configuration

Centralized

In this deployment, all bdi applications (bdi-<app>.ear) are deployed in a single WebLogic Application Server (not managed server instance) independent of where the Oracle Retails apps (<app>.ear) WebLogic Application Server is. This is an alternative configuration for non-production environments such as Dev.

Figure 10-2 Centralized Configuration

In all cases, the BDI application (bdi-<app>.war) should be deployed in its own managed server instance. It is not recommended to deploy multiple BDI applications into the same WLS managed server instance, or to have the BDI application (bdi-<app>.war) deployed into the same WLS managed server instance as the integrating application (<app>.ear). The configuration of deploying multiple bdi-<app>s in one managed server instance is not recommended or supported by WLS.