Understanding Implementing Handlers Using the Bulk Load Handler

You can bulk load large amounts of data (large messages) into a local table using the bulk load handler.

Note:

Bulk load handlers are allowed only on asynchronous service operations and only one bulk load handler is allowed per service operation.

When you implement a handler using a data mover script use the OnNotify event. When the OnNotify event is fired, the message data is inserted into the tables. Bulk load handlers do not perform any data validation.

Bulk Load Handler Message Types

You can use bulk load handlers for service operations that contain the following types of asynchronous messages:

• Rowset-based messages.

  For service operations that contain rowset-based messages, the message structure determines processing.

• Nonrowset-based messages.

  For service operations that contain nonrowset-based messages, you define the structure for processing by mapping data to PeopleSoft records and providing attribute names and values.

• Container messages that contain rowset-based messages parts.

  For service operations with container messages that contain rowset-based message parts, the bulk load handler uses the message structure of the message parts to determine processing.

Transactional Rollback

Bulk load handler processing is destructive load processing, meaning that the handler deletes existing data from the table and then bulk inserts the new data.

PeopleSoft Integration Broker provides an optional transaction rollback feature that enables you to rollback the database to the pre-bulk insert state if needed.

Transactional rollback is dependent on the bulk size of the data to be updated. Therefore, when you select the rollback option, a Rollback Size field appears where you specify a rollback value. The default value is 32 kilobytes.

Table Truncation

By default, the bulk load handler truncates table data before performing any processing.

PeopleSoft Integration Broker enables you to disable table truncation.

Nonrowset-Based Messages and the Bulk Load Handler

If a service operation contains a nonrowset-based message, you must add a data structure to define the message content, thereby allowing non-PeopleSoft data to map to the records and fields in the database.

In addition, you can provide an XML attribute name/value pair to distinguish record and field nodes on incoming XML content.

Process Overview for Implementing Handlers Using Bulk Load Handlers

The process for implementing a bulk load handler is:

1. Add a bulk load handler to the service operation on the target system.

   This procedure is discussed elsewhere in this topic.

   See Adding a Handler to a Service Operation.

2. Specify general handler details.

   This procedure is discussed elsewhere in this topic.

   See Specifying General Handler Details.

3. (Optional.) Enable transactional rollback and the rollback size.

   This procedure is discussed in this section.

4. (Optional.) Specify XML record attributes.

   This procedure is discussed in this section.

5. Add the data structure for the message contained in the service operation.

   The step is required only when a nonrowset-based message is contained in the service operation.

   This procedure is discussed in this section.