You can use Sybase WorkSpace to model and test custom wire format messages. In a Message Designer project, each custom wire format is modeled as a message definition (for example, PurchaseOrder). A message definition defines each data element in the message as a tree of containers (for example, BillToAddress) and fields (for example, PostalCode). Each container and field has properties you must configure to specify the nature and characteristics of each data element. Select any combination of containers and fields necessary to model the data elements in your message.
When creating message definitions, they can reside in a Message Designer Project folder or in a regular Sybase Project folder that has been updated with Message Designer resources (automatic upon creation).
When finished, a message definition is used to generate a set of objects that can be packaged, including an XSD, parser, and serializer. These objects can be used by other components, such as a Transformation service to parse and serialize custom wire format messages as part of a business process.
The following workflow guides you through the process of creating and testing a message definition project. You can also view these steps in a cheat sheet.
Set up Message Defaults preferences to select default settings for all future message definitions and any containers and fields that you add to it (optional).
In the Message Designer project, create a new message definition using the New Message Definition wizard.
Edit the message definition by modeling the custom wire format as a tree of containers and fields representing a sequence of data elements.
Add one or more containers to the message definition or to other containers.
Add one or more fields to the message or to a container.
Generate the message definition objects, which are required to test or deploy the message definition:
Parser
Serializer
XSD
Enter test data directly or load a text file containing test data.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com