Migrating Custom Mediation Tasks

If you created and deployed custom mediation tasks in earlier versions of TIBCO ActiveMatrix, and you want to use them with this version, you must migrate them to TIBCO ActiveMatrix 3.x.

Procedure

  1. Import your TIBCO ActiveMatrix 2.x model and UI plug-ins into your workspace.
  2. The Model plug-in uses import packages. Replace all Required-Bundles with:
    com.tibco.amsb.core.mediation.model.report.impl
    com.tibco.amsb.core.componentType
    com.tibco.amsb.core.mediationbpel.custom.task.persistence
    com.tibco.amsb.core.mediationextmodel
    com.tibco.amsb.core.mediationextmodel.impl
    com.tibco.amsb.core.mediation.model.ext.internal
    com.tibco.amsb.core.querymodel
    com.tibco.amsb.core.task.model.ext
    com.tibco.amsb.core.task.model.report
    com.tibco.amsb.core.taskdescriptormodel
    com.tibco.amsb.task.common.validation
    com.tibco.amsb.core.task.validation.constraints
    org.eclipse.core.runtime
    org.eclipse.bpel.model
    org.eclipse.emf.common
    org.eclipse.emf.ecore
    org.eclipse.emf.ecore.xmi
    org.eclipse.emf.ecore.impl
    org.eclipse.emf.validation
    org.eclipse.emf.common.util
    org.eclipse.emf.ecore.plugin
    org.eclipse.emf.common.notify
    org.eclipse.emf.common.notify.impl
    org.eclipse.emf.ecore.xmi.impl
    org.eclipse.wst.wsdl org.eclipse.xsd
  3. Delete the methods getStaticInputTypeSchemaStream() and getStaticOutputTypeSchemaStream() methods from class <TaskName>MediationTaskReport.java.
  4. Delete the class <TaskName>MediationTaskValidator.java after plugging out the validation code as the 3.x validation is based on EMF model constraints. The CMT developer must migrate the existing validation to EMF model constraints.
    Remove its extension entry in plugin.xml by deleting com.tibco.amsb.core.mediation.model.ext.MediationTaskValidationExtension entry.
  5. Update the the UI plug-ins.
    1. Update the following dependencies from:
      com.tibco.amsb.core.mediation.model
      com.tibco.amsb.core.mediation.model.report
      com.tibco.amsb.core.mediation.model.ext

      to

      com.tibco.amsb.core.mediation.model.eclipse
      com.tibco.amsb.core.mediation.model.report.eclipse
      com.tibco.amsb.core.mediation.model.ext.eclipse
    2. Add the dependency: com.tibco.xml.mapper.schema.emfapi.
  6. Re-compile the plug-ins by doing a clean build.
  7. Re-create your runtime plug-in, and port your custom code using the Mediation API.
  8. Re-create the DAA in the SOA project that is created. See Deploying Custom Mediation Tasks.
  9. Install the custom mediation task. See Writing Custom Mediation Code.