Choosing XML Namespace length

When you deploy your project to a message broker, you have the option of selectinglong or short XMLNameSpace format. The default is short. XMLNameSpaceFormat is a standard configuration connection property for adapters. The choice you make within System Manager overrides whatever might already exist in the adapter's configuration file. If you are deploying to WebSphere Business Integration Message Broker, the Select the parameters window allows you to specify that the project is namespace-aware. If the project is namespace-aware, either short or long formats are allowed. If the project is not namespace-aware, then long must be used. Selecting short with a project that is not namespace-aware will cause deployment to fail.

Note:
IBM recommends that any new projects be set to namespace-aware mode for ongoing compatibility with industry standards. IBM recommends setting XMLNameSpace format to short, if possible, for better performance.
If you are deploying to WebSphere MQ Integrator or WebSphere MQ Integrator Broker, then long or short are allowed. However, if short is selected, then the RFH2messagedomain property of the connector must be set to xml. If RFH2messagedomain is set to mrm, only XML messages in long namespace format can be processed.

Note:
WebSphere MQ Integrator and WebSphere MQ Integrator Broker do not support namespaces. Therefore you cannot specify namespace-aware for projects deployed to these brokers.
Table 1 shows the XMLNameSpace format alternatives available:

Table 1. XMLNameSpace format alternatives
Message Broker Namespace aware?

Yes No
WebSphere Business Integration Message Broker long or short long
WebSphere MQ Integrator or WebSphere MQ Integrator Broker N/A long or short (for short, RFH2messagedomain must be xml)


[ Top of Page | Previous Page | Table of Contents ]

Copyright IBM Corp. 1997, 2003