Planning user-defined extensions

Before you start to create your user-defined extension, be clear about what you want it for. Most tasks can be performed using the functions already provided with WebSphere Message Broker, so it might not be necessary to create a user-defined extension for your particular task.

To write user-defined extensions you need to be a skilled programmer, with some knowledge of WebSphere Message Broker and its architecture, so make sure you have the skills and knowledge required. You also need the time to test and debug your user-defined node or parser, and a safe environment in which to do this.

Also bear in mind that the maintenance and servicing of your own user-defined extensions is your responsibility. You should ensure that there will be someone available who can perform future updates or fixes.

A user-defined extension might be appropriate in the following situations:

There are a number of general design and development considerations that you should consider and understand when you are planning or writing a user-defined node or parser, and considerations that are specific to the type of user-defined extension you want to create. You should be familiar with the concepts covered in the topics below before designing a user-defined extension.

Related concepts
User-defined extensions
User-defined parsers
Designing user-defined extensions
Related tasks
Developing user-defined extensions
Related reference
User-defined extensions
cpiWriteBuffer