Tight Integration with WebLogic Server Interoperability With Other Messaging Services

Introduction and Roadmap 1-7 ■ Multicasting of messages for simultaneous delivery to many clients using IP multicast, as described in Using Multicasting with WebLogic JMS in Programming JMS for Oracle WebLogic Server.

1.5.4 Tight Integration with WebLogic Server

WebLogic JMS includes the following features to enable tight integration with WebLogic Server: ■ JMS can be accessed locally by server-side applications without a network call because the destinations can exist on the same server as the application. ■ Uses same ports, protocols, and user identities as WebLogic Server T3, IIOP, and HTTP tunnelling protocols, optionally with SSL. ■ Web Services, Enterprise Java Beans including MDBs, and servlets supplied by WebLogic Server can work in close concert with JMS. ■ Can be configured and monitored by using the same Administration Console, or by using the JMS API. ■ Supports the WebLogic Scripting Tool WLST to initiate, manage, and persist configuration changes interactively or by using an executable script. See Chapter 6, Using WLST to Manage JMS Servers and JMS System Module Resources. ■ Complete JMX administrative and monitoring APIs, as described in Developing Custom Management Utilities With JMX for Oracle WebLogic Server. ■ Fully-integrated Transaction Manager, as described in Introducing Transactions in Programming JTA for Oracle WebLogic Server. ■ Leverages sophisticated security model built into WebLogic Server policy engine, as described in Understanding WebLogic Security and Resource Types You Can Secure with Policies in Securing Resources Using Roles and Policies for Oracle WebLogic Server.

1.5.5 Interoperability With Other Messaging Services

WebLogic JMS includes the following features for interoperability with other messaging services: ■ Fully supports direct interoperability with prior WebLogic Server releases as described in WebLogic Server Compatibility in Information Roadmap for Oracle WebLogic Server . ■ Messages forwarded transactionally by the WebLogic Messaging Bridge to other JMS providers — as well as to other instances and versions of WebLogic JMS, as described in Configuring and Managing the Messaging Bridge for Oracle WebLogic Server. ■ Supports mapping of other JMS providers so their objects appear in the WebLogic JNDI tree as local JMS objects. Also references remote instances of WebLogic Server in another cluster or domain in the local JNDI tree. See Section 3.11, Foreign Server Configuration. ■ Uses MDBs to transactionally receive messages from multiple JMS providers. See Programming and Configuring MDBs: Details in Programming Message-Driven Beans for Oracle WebLogic Server. 1-8 Configuring and Managing JMS for Oracle WebLogic Server ■ Reliable Web Services integration with JMS as a transport, as described in Using Web Services Reliable Messaging in Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server. ■ Automatic transaction enlistment of non-WebLogic JMS client resources in server-side applications via JMS resource-reference pooling. See Enhanced Java EE Support for Using WebLogic JMS With EJBs and Servlets in Programming JMS for Oracle WebLogic Server. ■ Integration with Oracle Tuxedo messaging provided by WebLogic Tuxedo Connector. See How to Configure the Oracle Tuxedo Queuing Bridge in the WebLogic Tuxedo Connector Administration Guide for Oracle WebLogic Server. ■ The WebLogic JMS C API enables programs written in C to participate in JMS applications. This implementation of the JMS C API uses JNI in order to access a Java Virtual Machine JVM. See WebLogic JMS C API in Programming JMS for Oracle WebLogic Server. ■ Oracle Streams Advanced Queuing AQ provides database-integrated message queuing functionality that leverages the functions of the Oracle database to manage messages. WebLogic Server interoperates with Oracle AQ using a Foreign JMS and JDBC data source configuration in a WebLogic Server domain. Both local and remote JMS clients can use Oracle AQ destinations from WebLogic JNDI. See Chapter 7, Interoperating with Oracle AQ JMS.

1.6 New and Changed JMS Features