Creating a broker schema

If you want to organize your message flow project resources, and to define the scope of resource names to ensure uniqueness, you can create broker schemas. A default schema is created when you create the message flow project, but you can create additional schemas if you choose.

Before you start:

To create a broker schema:

  1. Switch to the Broker Application Development perspective.
  2. Click File > New > BrokerSchema or right-click any resource in the Navigator view and click New > BrokerSchema.

    You can also press Ctrl+N. This displays a dialog that allows you to select the wizard to create a new object. Click Message Brokers in the left view. The right view displays a list of objects that you can create for WebSphere Event Broker. Click Broker Schema in the right view, then click Next. The New Broker Schema wizard displays.

  3. Enter the message flow project in which you want the new schema to be created. If you have a message flow project or one of its resources highlighted when you invoke the wizard, that project name appears in the dialog. If a name does not appear in this field, or if you want to create the schema in another project, click Browse and select the correct project from the displayed list.

    You can type the project name in, but you must enter a valid name. The dialog displays a red cross and the error message The specified project does not exist if your entry is not a valid project.

  4. Enter a name for the schema. Choose a name that reflects the resources that it contains. For example, if you want to use this schema for message flows for retail applications, you might give it the name Retail.

    A broker schema name must be a character string that starts with a Unicode character followed by zero or more Unicode characters or digits, and the underscore. You can use the period to provide a structure to the name, for example Stock.Common.

  5. Click Finish to complete the task.
The schema directory is created in the project directory. If the schema is structured using periods, further subdirectories are defined. For example, the broker schema Stock.Common results in a directory Common within a directory Stock within the message flow project directory.
Related concepts
Broker schemas
Project references
Development repository
Message flows overview
Related tasks
Creating a message flow project
Deleting a message flow project
Creating a message flow
Related reference
Broker Application Development perspective
Rules for naming workspace objects