Design

The procedure implementation class uses the HCL® Marketing Operations API to read and update Marketing Operations components, start services, and so on. Other Java™ packages can be used to do other tasks.

In your design, focus on producing a single unit of work that operates atomically. Ideally, a procedure performs some series of tasks that can be scheduled asynchronously to run at some later time. This "fire and forget" integration model results in the least load on both systems.

Note: Only the documented classes and methods will be supported in future releases of Marketing Operations. Consider all other classes and methods in Marketing Operations to be off-limits.

After you code and compile the procedure implementation classes, you make them available to Marketing Operations. The build scripts that are supplied with the Marketing Operations Integration Services place the compiled procedures in the default location. The final development step is to update the custom procedure plug-in definition file that is used by Marketing Operations to discover the custom procedures.

The procedure must implement the com.unica.publicapi.plan.plugin.procedure.IProcedure interface and have a parameter-less constructor (usual JavaBeans model). Coding and compilation of each procedure is done in a Java IDE of the customer's choice, such as Eclipse, Borland JBuilder, or Idea. Sample code is provided with HCL Marketing Operations as developer toolkits, in the following location:

<MarketingOperations_Home>/devkits/integration/examples/src/procedure