Using a database transport
This section describes the steps to define a trigger, transport and transport map that demonstrates the inserting of data into a database table.
Assumptions
Before you begin, make sure the following has occurred:
- You installed the Enterprise Gateway software on a computer. For more information, see Installing product software.
- You installed the Workbench on a computer that has TCP connectivity to the node. For more information, see Installing the Workbench software.
- You have access to an external database server with the access authority to create a simple example table.
About the example trigger
The example trigger you will define will be a schedule event type trigger. When started, the trigger will execute every 5 seconds. It will use a database Transaction action to insert data into a database table.
The example trigger is made up of these
components:
The components are named as follows:
- MyDatabaseTransport — This is the transport that you will define. This transport represents the connection to a database server. The transport is created before any of the other components. You must have a database product installed and your database administrator must have created the database tables, provided you with the IP address of the database server, and a user ID and password.
- MyFirstTransportMap — This is the transport map that you will define. The transport map identifies the database operation, an insert for this example, and the mapping of data from a trigger into the format that the enterprise system is expecting (in this case, columns in a database table). All transport maps require a transport. This transport map will use the MyDatabaseTransport transport.
- MyFirstTrigger — This is the trigger that you will define. This trigger will be a schedule event type trigger defined to execute every 5 seconds. When the trigger executes, it will use a Transaction action to reference the MyFirstTransportMap transport map to insert data into a database table.