If you need to create a custom mediator that performs some logic on a message, you can either create a new mediator project, or import an existing mediator project using WSO2 ESB EI tooling.
| Tip |
|---|
You need to have WSO2 ESB EI tooling installed to create a new message store or to import an existing message store via ESB EI tooling. For instructions on installing WSO2 ESB EI tooling, see Installing WSO2 EI Tooling. |
Once a mediator project is finalised, you can export it as a deployable artifact by right-clicking on the project and selecting Export Project as Deployable Archive. This creates a JAR file that you can deploy to the ESBEI. Alternatively, you can group the mediator project as a Composite Application Project, create a Composite Application Archive (CAR), and deploy it to the ESBEI.
| Info |
|---|
A URL classloader is used to load classes in the mediator (class mediators are not deployed as OSGi bundles). Therefore, it is only possible to refer to the class mediator from artifacts packed in the same CAR file in which the class mediator is packed. Accessing the class mediator from an artifact packed in another CAR file is not possible. However, it is possible to refer to the class mediator from a sequence packed in the same CAR file and call that sequence from any other artifact packed in other CAR files. |
...
Follow these steps to import an existing mediator project into an ESB EI Config project. Alternatively, you can create a new mediator project.
...