Resolution:
Description:
================

Prior to BusinessConnect (BC) 5.3, the external DMZ component was a standalone BC engine that passed inbound internet traffic to the BC Interior server.  BC 5.3 introduced a version of the DMZ that can run as a servlet in popular J2EE webservers such as JBOSS, WebLogic, and WebSphere.  What are the advantages or disadvantages of deploying DMZ as a servlet as compared to DMZ export deployment?

Environment:
===============
BusinessConnect 5.3 and above

Resolution:
===============
The DMZ servlet is a small application that replicates the DMZ functionality inside a non-TIBCO J2EE Web Application Server, such as JBoss, Oracle/BEA's WebLogic server, or IBM's WebSphere server. The functionality is identical between the DMZ servlet running on a WebAppServer and the DMZ that runs on the TRA.  

You only need to use the DMZ servlet if you want to use one of these Web Application Servers as a gateway for external partners to access BusinessConnect in addition to other, non-TIBCO based applications.  If there is no other need for partners to access other applications, the standard BC DMZ server, either belonging to a TIBCO Application domain or standalone via export, is all that is needed.

With regard to monitoring, if you use the DMZ Servlet with an external application server, you will have to use that application server's monitoring tools to monitor the DMZ's operation.  If you use the DMZ export on the TRA environment, you can use TIBCO Hawk to monitor the DMZ.

Keywords/Tags:
= = = = = = = = =