Create a development environment
on Linux on x86 or Windows to develop your message
flows.
Before you start:
On Windows, you can
use the Launchpad to install both these components. For details, see Installing by using the Windows Launchpad.
If you are new to WebSphere Message
Broker, and have not created a default
configuration, you might want to use that option to set up your first
configuration. You can use the default environment to run some of
the supplied sample programs, and explore the features that are supported
by WebSphere Message
Broker. Follow the instructions
in Creating a default configuration.
To create your own development environment
on a computer that is running Linux on x86 or Windows, complete the following
steps:
- Start the WebSphere Message Broker Toolkit in
one of the following ways:
From the main menu:- On Red Hat, click .
- On SUSE Linux,
click .
Click , or double-click
the shortcut on your desktop.
- Use the following commands in a command prompt from their location
in the root directory for the package group:
A new session of the WebSphere Message Broker Toolkit opens, and prompts you for the
name of a workspace in which to store the resources that you create
in this session. You can accept the default value, workspace,
type your preferred name into the text field, or click Browse to select
the location of your choice. Select Use this as the default
and do not ask again to inhibit the display of the workspace
dialog next time you start the WebSphere Message Broker Toolkit.
- Click OK to confirm the location
of your workspace. Your WebSphere Message Broker Toolkit session
opens, and displays the Welcome page. You can tailor various
settings in the WebSphere Message Broker Toolkit to suit
your requirements and your working environment; for example, the colors
and fonts. These options are described in Configuring the Toolkit.
- Close the Welcome page. You can return to the
Welcome page later by clicking . If more than one option
is listed, select WebSphere Message
Broker.
- In the Broker Application
Development perspective, select
the Brokers view. Alternatively,
click to show the Brokers view.
- Right-click WebSphere
Message Brokers, and click to create a broker,
and complete the wizard for this task.
If you want
more detailed instructions, see Creating a broker for a development environment.
Your
configuration might be affected by the operation mode of your broker.
The default operation mode is advanced mode, in which your broker runs with
no restrictions. Check with your broker administrator which operation
mode applies to your organization; you might have to change the mode
of your broker after you have created it. For more information about
operation modes, see Operation modes.
- You must create at least one execution group on your broker. To add additional execution groups to your broker, right-click
the broker, and click . Enter a name for your execution group,
and click OK.
The execution group is the
runtime environment in which your message flows run. You can create
many execution groups on a single broker, and you can deploy your
message flows to one or more execution groups on one or more brokers.
For
more detailed instructions about this task, see Creating an execution group using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer.
Your configuration is now ready to use.
Next: You can start to develop
resources to deploy to your broker. You can create your own message
flows, or you can use the patterns and samples that are provided to
get you started. For details of these options, see
Developing message flows.
This task has covered the minimum set of
steps that you must complete to create a broker and configure your
development environment. Typically, as an application developer, you
are working in a single platform environment to create, deploy, and
test your message flows before they are ready for use in a test of
production environment.
More options are available for enhanced
configurations, including configurable services. When the requirements
of your message flows extend beyond this basic configuration,
and you need additional configuration to support those requirements,
you can find details of these more advanced options in Configuring brokers for test and production environments.