Creating, Editing, or Deleting an Event Channel

In this section:

How to:

Reference:

The following topics describe how to create, edit, or delete a channel for your iWay Event. All defined event ports must be associated with a channel.


Top of page

x
Creating a Channel

The following procedure describes how to create a channel using iWay Explorer.



x
Procedure: How to Create a Channel

To create a channel:

  1. Click the iWay Events tab.

    The adapters that appear in the left pane support events.

  2. In the left pane, expand the RDBMS node.

    The ports and channels nodes appear in the left pane.

  3. Click the channels node.
  4. In the right pane, move the pointer over Operations and select Add a new channel.

    The Add a new RDBMS channel pane opens on the right as shown in the following image.

    1. In the Channel Name field, type a name, for example, NewChannel.
    2. In the Description field, type a brief description.
    3. From the Channel Type drop-down list, select a channel type.
  5. Click Next.

    The Edit channels pane opens on the right with six tabs; five representing listener parameters. The following image shows four of the tabs.

    1. Select either an Oracle, SQL Server, DB2, EDA Server, or JDBC-ODBC Bridge Listener by clicking the appropriate tab.

      Note: If you are configuring listening capabilities for a non-relational database, select the EDA Server Listener.

      For information on common listener parameters see Common Listener Parameters.

      For information on listener parameters for JDBC-ODBC Bridge, see JDBC-ODBC Bridge Listener Parameters.

      For information on listener parameters for Oracle, see Oracle Listener Parameters.

      For information on listener parameters for SQL Server, see SQL Server Listener Parameters.

      For information on listener parameters for DB2, see DB2 Listener Parameters.

      For information on listener parameters for EDA Server, see EDA Server Listener Parameters.

      For information on listener parameters for JDBC, see JDBC Listener Parameters.

      From the Advanced tab, you can access the Synctype drop-down list which defaults to REQUEST.

    2. Type the system information that is specific to the database on which you are listening based on the descriptions in the previously referenced topics.
  6. Click Next.

    The Select Ports pane opens on the right with buttons to enable you to move ports from one area to the other as shown in the following image.

    1. Select an event port from the list of available ports. To select more than one, hold down the Ctrl key and click the ports.
    2. Click the single right arrow button to transfer the selected port(s) to the list of current ports. To transfer all event ports, click the double right arrow button.
  7. Click Finish.

    Summary information appears as shown in the following image and includes the channel description, channel status, and current ports. All the information is associated with the channel you created in the right pane.

    The channel appears under the channels node in the left pane with an X over the icon indicating that the channel is currently disconnected as shown in the following image.

    You must start the channel to activate your event configuration.


Top of page

x
Reference: Common Listener Parameters

The following table lists and describes the parameters common to all listeners. For parameters specific to your listener, see the reference topics in this section.

Parameter

Description

Polling Interval

Interval, in milliseconds, at which to check for new input.

SQL Query

SQL SELECT statement that the listener issues to poll the table.

If the SQL statement includes a date column or long text column, you must provide a value for the SQL Post-query parameter. The value you provide must not contain a date column or a long text column. This applies whether you provide an SQL statement here or rely upon the default.

For example, the following SELECT statement retrieves all unprocessed records from the DISCRETE_JOBS table:

SELECT * FROM WIP_DISCRETE_JOBS D
WHERE DJ.WIP_ENTITY_ID >
(SELECT WIP_ENTITY_ID
FROM WIP.TEMP_NEW_WORK_ORDER_ENTITY_ID)

Important: When a SQL Query joins two or more tables, a SQL Post Query must be used. Also, do not use a semicolon at the end of a SQL statement for a SQL Query or a SQL Post Query.

Post Query

A SQL statement that is executed after each new record is read from the table. Case sensitive: the case used to specify the column names must match the case used in the SELECT statement that polled the table. If the SQL Query property was omitted so that a default SELECT statement polled the table, the case used to specify the column names must match the case used to define the columns in the DBMS native schema.

If you do not specify a value for SQL Post-query, each record read from the table is deleted after it is read. How this happens depends on whether you specify the Delete Keys property. If you:

Specify the Delete Keys property, by default the adapter issues a DELETE statement with a WHERE clause containing every key column specified for the Delete Keys property.

At run time this is faster than if you had not specified the Delete Keys property if there is an index on the key or if there are fewer key columns than there are columns in the SELECT statement that polled the table.

Do not specify the Delete Keys property, by default the adapter issues a DELETE statement with a WHERE clause that specifies every column from the SELECT statement that polled the table.

You can choose to retain the table data after it is read by specifying a value for this parameter, as shown in the examples that follow.

Note: The SQL Post-query and Delete Keys parameters are mutually exclusive, because Delete Keys applies to the default DELETE statement, and SQL Post-query overrides the default DELETE statement. You can provide a value for one or the other, but not for both.

There are two field operators, ? and ^, that you can use in a post-query SQL statement. For more information, see The Post-query Parameter Operators.

Important: When a SQL Query joins two or more tables, a SQL Post Query must be used. Also, do not use a semicolon at the end of a SQL statement for a SQL Query or a SQL Post Query.

Delete Keys

Comma-separated list of key columns to be used in the default DELETE statement. DELETE operates on keys, so specify the table key columns.

This is case sensitive: the case used to specify the column names must match the case used in the SELECT statement that polled the table. If the SQL Query property was omitted so that a default SELECT statement polled the table, the case used to specify the column names must match the case used to define the columns in the DBMS native schema.

Note: The Delete Keys and SQL Post Query parameters are mutually exclusive, because Delete Keys applies to the default DELETE statement, and SQL Post Query overrides the default DELETE statement. You can provide a value for one or the other, but not for both. For more information, see the description of the SQL Post-query parameter in this table.



x
Reference: JDBC-ODBC Bridge Listener Parameters

The following table lists and describes the parameters for the JDBC-ODBC Bridge listener.

Note: Common listener properties are defined in Common Listener Parameters.

Parameter

Description

Datasource

Name of the data source configured under the ODBC Driver Manager. For more information, see your ODBC Driver Manager documentation.

User

Database user ID to access the table.

Password

Database password associated with the user ID.



x
Reference: Oracle Listener Parameters

The following table lists and describes the parameters for the Oracle listener.

Note: Common listener properties are defined in Common Listener Parameters.

Parameter

Description

Host

Name or URL of the machine where the database is installed.

Port

Port on which the Host database is listening. The default is 1521.

SID

A unique name for the database service, chosen by the database administrator or the person who installed Oracle E-Business Suite.

User

Database user ID to access the table.

Password

Database password associated with the user ID.



x
Reference: SQL Server Listener Parameters

The following table lists and describes the parameters for the SQL Server listener.

Note: Common listener properties are defined in Common Listener Parameters.

Parameter

Description

Host

Name or URL of the machine where the database is installed.

Port

Port on which the Host database is listening. The default port is 1433

Database Name

Database name of the database where the table specified in the SQL statement is located.

User

Database user ID to access the table.

Password

Database password associated with the user ID.



x
Reference: DB2 Listener Parameters

The following table lists and describes the parameters for the DB2 listener.

Note: Common listener properties are defined in Common Listener Parameters.

Parameter

Description

Host

Name or URL of the machine where the database is installed.

Port

Port on which the Host database is listening.

Database Name

The name of the database.

DB2 Driver Type

Select from the following:

  • app driver(type2)
  • net driver(type3)
  • jcc driver(type4)

User

The user ID used to access the database.

Password

The password associated with the user ID given.



x
Reference: EDA Server Listener Parameters

The following table lists and describes the parameters for the EDA Server listener.

Note: Common listener properties are defined in Common Listener Parameters.

Parameter

Description

Host

Name or URL of the machine where the database is installed.

Port

Port on which the Host database is listening.

Database Name

Database name of the database where the table specified in the SQL statement is located.

Note: When you access a non-relational database, and the server component is an SSCTL server component, the database name must be the service name, and you must specify it. If the server component is installed on USS, you can leave the database field blank. For more information about the server component, see Introducing the iWay Technology Adapter for RDBMS.

User

Database user ID to access the table.

Password

Database password associated with the user ID.



x
Reference: JDBC Listener Parameters

The following table lists and describes the parameters for the JDBC listener.

Note: Common listener properties are defined in Common Listener Parameters.

Parameter

Description

Driver Class

Driver class for the JDBC listener.

Driver URL

Valid location of the JDBC driver.

User

Database user ID to access the table.

Password

Database password associated with the user ID.



x
Procedure: How to Start or Stop a Channel

To start or stop a channel:

  1. Expand the iWay Events node.
  2. Expand the RDBMS node.
  3. Select the channel you want to start or stop.
  4. To start the channel, move the pointer over Operations and select Start the channel.

    The X over the icon disappears as shown in the following image, and the channel starts.

  5. To stop the channel, move the pointer over Operations and select Stop the channel.

Top of page

x
Editing or Deleting a Channel

The following procedures describe how to edit or delete a channel.



x
Procedure: How to Edit a Channel

To edit a channel:

  1. Expand the iWay Events node.
  2. Expand the RDBMS node.
  3. In the left pane, select the channel you want to edit.
  4. In the right pane, move the pointer over Operations and select Edit.

    The Edit channels dialog box opens.

  5. Make the required changes to the channel configuration and click Finish.


x
Procedure: How to Delete a Channel

To delete a channel:

  1. Expand the iWay Events node.
  2. Expand the RDBMS node.
  3. In the left pane, select the channel you want to delete.
  4. In the right pane, move the pointer over Operations and select Delete.

    A confirmation dialog box opens.

  5. To delete the channel you selected, click OK.

    The channel disappears from the list in the left pane.


iWay Software