WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Message Sets: New message definition file wizard: Create a new message definition file from a database definition
You can create a new message definition from a database definition file (.dbm) by using the New Message Definition File wizard in the WebSphere® Message Broker Toolkit.
Create a new message definition file from a database definition
When you create a new message definition file from a database definition, you must set the following fields:
Select a database definition
- Message set
- Use this field to choose the message set project that will contain the message definition file that you create. Message set projects are filtered to only show artifacts in the active working set.
- Message definition file name
- Use this field for the name of the message definition file that you want to create.
- Select file from workspace
- Choose this option if the database definition that you want to add to the message definition file that you are creating is in the current workspace, and select the file from the displayed content of the workspace. Database definitions are filtered to only show artifacts in the active working set.
- Select file from outside workspace
- Choose this option if the database definition that you want to add to the message definition file that you are creating is not in the current workspace, and specify the location of the database definition that you want to add.
- Copy source file into the 'importFiles' directory of the message set project
- Select this check box to copy the source file into the 'importFiles' directory of the message set project.
- Model unknown user-defined database types as XML schema
- If the database definition file does not contain information about user-defined data types that are present in the table that you are importing, you must specify how the data is modeled. Choices are string or HexBinary.
- Select the tables to import
- Select the tables that you want to import. If you select tables from more than one schema, a .mxsd file is created for each schema. Each selected table is created as a global xs:element with a message annotation, so that the table can be used directly in Mapping and other similar nodes.