2.6 Summary of Interoperability Capabilities
The following table summarizes the interoperability capabilities for an Oracle Tuxedo/ WebLogic Server deployment.
| This component . . . | Can call a . . . | Through . . . |
|---|---|---|
| Tuxedo ATMI client * | WebLogic Server EJB object | WSH ** → TDomain → WTC |
| Tuxedo Jolt client *** | WebLogic Server EJB object | JSH → TDomain → WTC |
| Tuxedo CORBA C++ client * | WebLogic Server EJB object | ISH → TDomain → WTC or
RMI-over-IIOP client direct connectivity to an EJB |
| Tuxedo ATMI server | WebLogic Server EJB object | TDomain → WTC |
| Tuxedo CORBA C++ server | WebLogic Server EJB object | TDomain → WTC or RMI-over-IIOP client direct connectivity to an EJB |
| WebLogic Server EJB, JSP, or servlet | Tuxedo ATMI service | WTC → TDomain or Jolt for WebLogic Server → JSH |
| WebLogic Server EJB, JSP, or servlet | Tuxedo CORBA C++ object | WTC → TDomain |
| * A native Tuxedo ATMI or CORBA C++ client does not use Tuxedo handler gateway processes (WSH, ISH).
** WSH stands for Workstation Handler. *** The Tuxedo Jolt client connection to a WebLogic Server EJB object has not been tested. |
||
Parent topic: Interoperability with Oracle WebLogic Server