Bind listeners for message-driven beans settings

Use this page to specify bindings for message-driven beans in your application or module.

To view this administrative console page, click Applications > Application Types > WebSphere enterprise applications > application_name > Message Driven Bean listener bindings. This page is the same as the Bind listeners for message-driven beans page on the application installation and update wizards.

Each message-driven bean must be bound to a listener port name or to an activation specification Java™ Naming and Directory Interface (JNDI) name.

Provide a listener port name if your application uses either of the following Java Message Service (JMS) providers:

Provide an activation specification JNDI name if your application's resources are configured using the default messaging provider or any generic J2C resource adapter that supports inbound messaging.

Not providing valid listener port names or activation specification JNDI names results in the following errors:

To apply binding changes to multiple mappings:

  1. In the list of mappings, select the Select check box for each EJB module that you want mapped to a particular binding.
  2. Expand Apply Multiple Mappings.
  3. Complete one of the following steps:
    • Specify a listener port name.
    • Select a target resource JNDI name for an activation specification. Optionally specify the following parameters:
      Destination JNDI name
      For resource adapters that support JMS, specify javax.jms.Destinations so the resource adapter can service messages from the JMS destination. A Destination JNDI name set as part of application deployment take precedence over properties set on an activation specification administrative object. Note that the Destination JNDI name is also referred to as Destination lookup.
      ActivationSpec authentication alias
      Specify an authentication alias that is used to access the user name and password that are set on the configured J2C activation specification. Authentication alias properties set as part of application deployment take precedence over properties set on an activation specification administrative object.
  4. Click Apply.
  5. Click OK or Next.

Module

Specifies the name of the module that contains the enterprise bean.

Bean

Specifies name of an enterprise bean in the application.

URI

Specifies the location of the module relative to the root of the application EAR file.

Messaging Type

Specifies the type of message-driven bean.

Listener Bindings

Specifies a listener port name or an activation specification JNDI name for the message-driven bean. When a message-driven enterprise bean is bound to an activation specification JNDI name you can also specify the destination JNDI name and the authentication alias.

Bindings specify JNDI names for the referenceable and referenced artifacts in an application. An example JNDI name for a listener port to be used by a Store application might be StoreMdbListener. The binding definition is stored in IBM® bindings files such as ibm-ejb-jar-bnd.xmi.
支援的配置 支援的配置: 對於 IBM 延伸和連結檔而言,.xmi 或 .xml 副檔名取決於您是使用 Java EE 5 之前的應用程式或模組,或 Java EE 5 或更新版本的應用程式或模組。 IBM 延伸或連結檔稱為 ibm-*-ext.xmi 或 ibm-*-bnd.xmi,其中 * 是延伸或連結檔的類型,例如:app、application、ejb-jar 或 web。 適用的條件如下:
  • 如果應用程式或模組使用第 5 版之前的 Java EE,副檔名必須是 .xmi。
  • 如果應用程式或模組使用 Java EE 5 或更新的版本,副檔名必須是 .xml。 如果 .xmi 檔是隨附在應用程式或模組,則本產品會忽略 .xmi 檔。

不過,即使應用程式含有 Java EE 5 之前的檔案,且所用的副檔名是 .xmi,其中也可以有 Java EE 5 或更新版本的模組。

ibm-webservices-ext.xmiibm-webservices-bnd.xmiibm-webservicesclient-bnd.xmiibm-webservicesclient-ext.xmiibm-portlet-ext.xmi 檔會繼續使用 .xmi 副檔名。

sptcfg

指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 11:20
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=urun_rapp_bindmdb
檔名:urun_rapp_bindmdb.html