Configuring a messaging engine data store to use a data source

After configuring a JDBC data source, you can configure a messaging engine data store to use the data source.

Before you begin

To complete this task, you must have chosen or created a bus and a messaging engine, and the messaging engine must specify data store as its message store type.

You must also have configured a data source, as described in Creating the database, schema and user ID for a messaging engine.

About this task

A messaging engine uses an instance of a JDBC data source to interact with the database that contains the data store for that messaging engine.

Use the WebSphere® Application Server administrative console to set the data store configuration parameters.

Procedure

  1. In the navigation pane, click 服務整合 -> 匯流排 -> bus_name -> [拓蹼] 傳訊引擎 -> engine_name.
  2. Check that the Message store type is Data store.
  3. Click [Additional Properties] Message store. The data store configuration detail panel is displayed.
  4. Specify the following data store configuration details:
    Data source JNDI name
    Type the JNDI name of the data source that provides access to database that holds the data store.
    Schema name
    Type the name of the database schema that contains the tables used by the data store.
    General tip: The schema name is usually the same as the user ID that is declared in the authentication alias. With some databases, for example DB2®, you can provide an alternative schema name. For more information about the relationship between users and schema, refer to the documentation for your chosen RDBMS.
    Informix tip: When you configure your messaging engine to use an Informix® database, you must specify the schema name in lowercase letters.

    When it is starting, a messaging engine that uses a data store checks to see if its data store exists. If the Create tables option is selected for the configuration, the messaging engine creates the tables in its chosen schema.

    The Schema name field is optional. If you require a schema name, consider the following:
    • The default schema name is IBMWSSIB.
    • If you delete the text so that field is blank, the messaging engine takes the user id defined in the authentication alias to be the schema name.
    • If you define a schema name explicitly, that schema name is used by the messaging engine.
    • If there are multiple messaging engines, you must configure each messaging engine to use a unique schema, otherwise FFDC error messages stating that Connection cannot be provided as Datasource has been disabled! might appear. This applies to DB2 in particular.
    Authentication alias
    Select the authentication alias that enables access to the data source.
    [AIX Solaris HP-UX Linux Windows][IBM i]Apache Derby Tip: [IBM i][AIX Solaris HP-UX Linux Windows]當您建立新的 Network Attached Apache Derby 資料儲存庫時,依預設,您會取得空白的鑑別別名。 [IBM i][AIX Solaris HP-UX Linux Windows]如果您在「網路連接」模式中,搭配 DB2 Universal JDBC 驅動程式來使用 Apache Derby(也就是說,您用到「使用 (DB2) Universal JDBC 驅動程式之 Derby Network Server 的 JDBC 提供者」),您必須指定一個鑑別別名。Apache Derby 所需的資料來源設定下限 中有這項需求的說明文件。 [IBM i][AIX Solaris HP-UX Linux Windows]另請參閱下列疑難排解要訣:當連接到 Network Attached Apache Derby 10.3 版資料庫時,發生不支援使用者 ID 的異常狀況
    Create tables
    Select the check box if you want WebSphere Application Server to create the database tables automatically.
    Note: The user ID that the messaging engine uses to connect to the data source must have sufficient authority to create the database tables and indexes.
    DB2 for z/OS restriction: Do not select Create tables if you are using DB2 for z/OS, otherwise an exception will be thrown when WebSphere Application Server attempts to create the tables.
    Restrict long running locks

    This parameter specifies whether the active messaging engine must retain long running locks on the SIBOWNER table in the database.

    Select the check box to restrict the active messaging engine from retaining long running locks on the SIBOWNER table in the database. When this option is selected, the messaging engine establishes a lock over the database only for short durations. In the event of the active messaging engine not responding to the database, the standby messaging engine will be able to take ownership of the database because the active messaging engine holds only short duration locks. This option also ensures that only one active messaging engine can access the database at a given time.

    Note: When the check box is selected and if the active messaging engine fails to communicate with the database or respond to the database, all the current transactions from the applications are ended and no new connections from the applications are allowed to the messaging engine.
    Number of tables for permanent objects
    Permanent tables contain persistent objects for the data store.
    Note: You can only increase the number of permanent tables, not decrease them.
    Number of tables for temporary objects
    Temporary tables contain nonpersistent objects that have been saved to the data store to reduce the messaging engine memory requirement.
    Note: You can only increase the number of temporary tables, not decrease them.

指出主題類型的圖示 作業主題



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