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.
The following procedure describes how to create a channel using iWay Explorer.
To create a channel:
The adapters that appear in the left pane support events.
The ports and channels nodes appear in the left pane.
The Add a new RDBMS channel pane opens on the right as shown in the following image.
The Edit channels pane opens on the right with six tabs; five representing listener parameters. The following image shows four of the tabs.
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.
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.
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.
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. |
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. |
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. |
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. |
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:
|
User |
The user ID used to access the database. |
Password |
The password associated with the user ID given. |
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. |
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. |
To start or stop a channel:
The X over the icon disappears as shown in the following image, and the channel starts.
The following procedures describe how to edit or delete a channel.
To edit a channel:
The Edit channels dialog box opens.
To delete a channel:
A confirmation dialog box opens.
The channel disappears from the list in the left pane.
iWay Software |