What are the steps to prepare a Database adapter that publishes events?
Before a Database adapter can publish events, some stored procedures need to be generated in iStudio. See Also: “Design Time Questions” iStudio will create two SQL scripts for a publish message; one with stored procedures and one with types. The types script name will end with TYPES.sql. Using any username, load the types scripts and the stored procedure script into the database. When an event occurs, there are several PL/SQL methods that must be called to publish the event message. All of the methods reside in the
Before a Database adapter can publish events, some stored procedures need to be generated in iStudio. iStudio will create two SQL scripts for a publish message; one with stored procedures and one with types. The types script name will end with TYPES.sql. Using any user name, load the types scripts and the stored procedure script into the database. When an event occurs, there are several PL/SQL methods that must be called to publish the event message. All of the methods reside in the event business object package which is created in the stored procedure SQL script. The first procedure that must be called is crMsg_event name_event owner_event version. It has two out arguments which are both of type number: the message id and the root data type id. Next, populate the message with the correct data. For each non-primitive attribute that the message contains, there is a function called cr_data type name_attribute name. This function has one argument for each primitive attribute it contains a
