| Author |
Message
|
| kishoreMuthyala |
 Posted: Thu Mar 25, 2004 1:02 am Post subject: HELP |
 |
|
Apprentice
Joined: 24 Mar 2004
Posts: 35
Location: singapore
|
Hi ,
Softwares versions
Websphere MQ 5.3 with CSD 05
DB2 ver 8.1 with Fix Pack 3
Websphere Adapter 5.5.
Websphere Business Integration Message Broker ver 5.0 with CSD 02.
I am trying to retrieve the data from SAP BAPI module into the message broker using the SAP Adapter.
From WebSphere Business Integration Adapters->tools
Configured the SAP Adapter and Developed Business Objects using SAPODA and saved them in System Manager by creating the project
The SAP Adapter has been configured and it is polling.
From system manager I have deployed the project to Message Broker in this process i have given the message set name which was
imported into the Message Broker.
In the message broker, I have created a message flow project and developed a message flow with MQ input node
and compute node and MQ output node and deployed both the message set and the message flow successfully
to the broker.
In the Websphere MQ, I have created an input queue in which I want to put the message. When I am putting xml data
into the queue, it is giving errors.
ERROR
______
( wmbroker.default ) Message Format 'CwXML' does not match a Wire
Format Identifier or a Format Name.
The Message Format is used to identify a Physical Format layer in the
message set (via the Wire Format Identifier of the layer).
Message Set I18HGHC002001 did not contain any Physical Format layer
with a Wire Format Identifier of 'CwXML'.
The Message Format can also identify a bitstream worker by its name,
but 'CwXML' is not a valid name for a bitstream worker.
'xml','cwf','tds' and 'pdf' are valid names, and others may be available on your
system.
If the Message Format was intended to identify a Physical Format layer,
check that the Message Format has been specified correctly, and check
that the message set has been deployed successfully.
If the Message Format was intended to refer to a bitstream worker,
check that the appropriate bitstream worker file (dll or shared object)
exists in the correct directory.
E.g. On NT if we send an XML message to the broker we should have the
file bipxmlworker.wrk in the <MQSI dir>/bin directory. Other platforms
should have the .wrk files in the <MQSI dir>/lib directory.
Ensure that all the required workers are available and have loaded
without error. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Mar 25, 2004 5:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What are the properties on your MQInput node?
What are the names of the physical wire formats of your message set?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kishoreMuthyala |
| Posted: Tue Mar 30, 2004 11:38 pm Post subject: Help |
|
|
Apprentice
Joined: 24 Mar 2004
Posts: 35
Location: singapore
|
Hi ,
my in my Input node properties
iam giving the input Queue name xxx and iam putting a sample xml data <test>001</test>
Physical wire format of my message set is CwXML
regards & thanks
Kishore Muthyala |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 31, 2004 12:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What are the rest of the properties of your input node?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kishoreMuthyala |
| Posted: Wed Mar 31, 2004 12:47 am Post subject: hello |
|
|
Apprentice
Joined: 24 Mar 2004
Posts: 35
Location: singapore
|
Hi,
i have given my input Q and Message Doamin as XML
thats it in I/P node properties
regards
Kishore Muthyala |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 31, 2004 3:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So, you are trying to take a piece of XML data coming in, without using a message set, and then turn it into a piece of data that matches a message set?
What your error message is telling you then is that you are not fully populating all of the necessary fields to output the data using the message set model.
You will need to use ESQL to also set the MessageType, MessageSet and one or two more members of OutputRoot.Properties that I don't recall the names of right now.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kishoreMuthyala |
| Posted: Fri Apr 02, 2004 12:19 pm Post subject: Help |
|
|
Apprentice
Joined: 24 Mar 2004
Posts: 35
Location: singapore
|
hi everyone,
Thanks for the help and support given to me.The problem is finally resolved.
regards
Kishore Muthyala |
|
| Back to top |
|
|
|
|
