How are hooks used in OneData?

webMethods, OneData, and Terracotta 10.2 | Managing Master Data with webMethods OneData | Developing for webMethods OneData | OneData Hooks | How are hooks used in OneData?

Hook Invocation Modes and Triggering Events

Hook Types

You can extend OneData’s functionality using commands called Hooks. Hooks invoke external procedures. You can use the Hook interface to provide parameters that are required to execute stored procedures at a specific data manipulation event such as:

Inserting a new record in an object.

Updating a column or an attribute in an object.

Deleting (logically) a record in an object.

Restoring a logically deleted record.

Purging (physically deleting from database) a logically deleted record.

You can use hooks in to perform an action based on a trigger, for example:

Automatically insert a record in a mapping table whenever you create a new code.

Map or auto-create a customer when a matching customer record is imported from the source systems.

Determine whether a customer created in their system is a unique global customer or is a duplicate of an existing global customer.

Parse a product record from the source system and decompose it into different tables.

OneData provides interactive hook support for objects in order to enable interactive user feedback from Data Manager screens. The following table lists the hook functionality that is supported for objects in Nova mode.

	Processing Action		Hook Trigger
Hook Type	Pre-Hook Processing?	Post-Hook Processing?	Standard Command Hook?	UI Interactive Command Hook?
Java Hook	Yes	Yes	Yes	Yes
Java RMI	Yes	Yes	Yes	Yes
Stored Procedure	Yes (Oracle Repository Only)	Yes (Oracle Repository Only)	Yes (Oracle Repository Only)	Yes (Oracle Repository Only)
Integration Server Hook	Yes	Yes	Yes	Yes
Process Flow Hook	No	No	No	Yes