Resources

The projects, folders, and files that exist in the workbench are called resources. They are collectively referred to as the workspace. and they are stored in your local file system.

By default, resources are stored (with their metadata) in the workspace directory. The workspace directory is created the first time that you start the workbench.

where user_ID is the user name with which you are logged on.

You can create projects in other directories in addition to the workspace directory. You can maintain multiple workspaces by specifying a new location at the prompt when you start your workbench session.

Typically, you edit and view workbench resources in the Broker Development view in the Broker Application Development perspective. The exception is a broker domain resource (also referred to as a domain object) which you view and edit in the Broker Administration Navigator view in the Broker Administration perspective.

The following figure shows a server project, a message flow project, and a message set project in the Broker Development view of the Broker Application Development perspective.

A screen capture of the Broker Development view in the Broker Application Development perspective

Resource editors do not automatically reflect the changes that you make in one window in additional windows that you have opened to view the same resource. Close and reopen additional windows each time that you update a resource in an editor session.

Types of resource

You can create and work with three basic types of resource:
Files
Workspace files are comparable to files in a file system. Different types of resource are maintained in different file types, for example, message flow files, message set definition files, ESQL files, mapping files, XML Schema files and broker archive files. File types are listed in Resource types in the workbench.
Folders
Workspace folders are comparable to directories in a file system. Folders are contained within projects or other folders. Folders can contain files and other folders.

When you create resources, they are grouped together by file type in logical categories within the hierarchy, and placed in virtual folders.

Within a Message Flow project, a number of virtual folders contain groups of resources:
Flows
This virtual folder is always shown after project creation, and contains .msgflow files, which are grouped by namespaces.
Maps
This virtual folder is shown only when it contains .msgmap files, which are grouped by namespaces.
ESQLs
This virtual folder is shown only when it contains .esql files, which are grouped by namespaces.
Database Connections
This virtual folder is shown only when it contains database related files, for example, .conxmi, .dbxmi, and .schxmi. These database files are grouped by namespaces.
Enqueues
This virtual folder is shown only when it contains .enqueue files, which are grouped by namespaces.
Flow Tests
This virtual folder is shown only when it contains .mbtest files, which are grouped by namespaces.
Within a Message Set project, a message set folder contains a message set file (.messageSet.mset) and potentially two virtual folders that contain groups of resources:
Message Definitions
This virtual folder is always shown after project creation, and contains .mxsd files, which are grouped by namespaces.
Message Categories
This virtual folder is shown only when it contains .category files, grouped by namespaces.

If you select Hide Categories, these folders do not appear.

Projects
Projects contain folders and files. Projects are used for building, version control, sharing, and resource organization. Like folders, projects map to directories in a file system. When you create a project, you specify a location for it in the file system. By default, projects are created in the workspace directory.

A project is either open or closed. You can view and modify an open project in the workbench. You cannot view or modify the contents of a closed project. The files and folders of a closed project are not displayed in the workbench, but they still reside on the local file system.

You can filter closed projects so that they do not appear in the workbench, by selecting Filters from the view menu (shown by a down arrow) in the Broker Development view, and then clicking Closed Projects from the displayed list of resource filters.

A closed project requires less memory than an open project.

You can:
  • Add a project to the workbench.
  • Save a new version of a project in an external repository.
  • Copy a project from another user's workbench.

Project types are listed in Resource types in the workbench.

Working sets

A working set is a logical collection of application projects, that you can use to limit the number of resources that are displayed in the Broker Development view. By creating and using a working set, you can reduce the visual complexity of what is displayed in the Broker Development view, making it easier to manage and work with your application projects.

The active working set is the current working set of application projects that you choose to display. Only the application projects contained in the active working set are displayed in the Broker Development view. If you do not create any working sets, the default active working set contains <all resources> and displays all of your application projects.

You can create a new working set in the Broker Development view in either of the following two ways:
  • You can create a new working set and add existing application projects to it.
  • When you use a Quick Start wizard to set up the basic resources that are required to develop an message flow application, you are given the option of creating a new working set for the resources.

When you use the Broker Application Development perspective to create a new file or new project, the new file or project is automatically added to the current active working set. If you have not identified an active working set, the new file or project is displayed under all resources in the Broker Development view, but is not added to a working set.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:19:47

ab00230_