1.1.5 Deployment Patterns for Application Integration
This topic describes the deployment patterns for application integration.
Table 1-1 Deployment Patterns
| Business Integration Needs | Nature of Integration | Oracle Banking Treasury Management Deployment Pattern | Remarks | 
|---|---|---|---|
| Inbound Transactions into Oracle Banking Treasury Management | Synchronous | OBTR EJB | Recommended | 
| 
                                  OBTR HTTP Servlet  | 
                              This can be used if the external system cannot communicate to Oracle Banking Treasury Management using EJB. | ||
| 
                                  OBTR Web Services  | 
                              This can be used if the external system chooses to communicate only through Web Services. | ||
| Asynchronous | 
                                  OBTR MDB  | 
                              This can be used if the external system chooses to communicate only through JMS queues | |
| 
                                  Inbound Queries into Oracle Banking Treasury Management  | 
                              Synchronous | OBTR EJB | Recommended | 
| 
                                  OBTR In Servlet  | 
                              This can be used if the external system cannot communicate to Oracle Banking Treasury Management using EJB. | ||
| 
                                  OBTR Web Services  | 
                              This can be used if the external system chooses to communicate only through Web Services. | ||
| Asynchronous | 
                                  OBTR MDB  | 
                              This can be used if the external system chooses to communicate only through JMS queues | |
| 
                                  Handoffs from Oracle Banking Treasury Management  | 
                              Asynchronous | 
                                  OBTR Notify  | 
                              Recommended | 
Parent topic: Gateway Functions - An Overview