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.
To create a broker schema:
- Switch to the Broker Application Development
perspective.
- Click or right-click any resource
in the Navigator view and click .
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 Message Broker.
Click Broker Schema in the right view, then click Next.
The New Broker Schema wizard displays.
- 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. You must specify a
message flow project; if you select a message set project, the Finish button
remains disabled.
- 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.
- 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.