ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Unsing Convert Encoding and CCSID on Input Node

Post new topic  Reply to topic
 Unsing Convert Encoding and CCSID on Input Node « View previous topic :: View next topic » 
Author Message
schroederms
PostPosted: Fri Jun 03, 2005 10:58 am    Post subject: Unsing Convert Encoding and CCSID on Input Node Reply with quote

Disciple

Joined: 21 Jul 2003
Posts: 169
Location: IA

I'm testing out some data and created a flow where the input node has the Convert property checked and Encoding and CCSID is also be populated. However, the messages are not coming off the queue. I have the failure node wired as will, thinking that might be where they would go, but still no luck.

Thanks,
Mike
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Jun 03, 2005 11:20 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Wire the catch terminal, not the failure terminal.

Add a throw node to the end of the catch terminal.

Try again.

Check your system log for errors indicating the cause of the failure.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
EddieA
PostPosted: Fri Jun 03, 2005 12:47 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Quote:
the input node has the Convert property checked and Encoding and CCSID is also be populated

Why do you need to do this. This will only work if the message is MQSTR, unless you have your own conversion exit. In most, if not all, cases it's easier to leave this out, and let WMQI convert within the flow.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
schroederms
PostPosted: Mon Jun 06, 2005 4:56 am    Post subject: Reply with quote

Disciple

Joined: 21 Jul 2003
Posts: 169
Location: IA

EddieA,

I'm trying to figure out where we are loosing some European characters from SAP. We use WBI as our EAI backbone to allow front end applications to call services and services to call other services as well. Except for SAP services that we use iWAY nodes within WBI, most of our services are JAVA, which the format is MQSTR on all the messages that pass thru the EAI pipe.

The problem that has been brought to my attention is a JAVA web application that is asking for some data from SAP. Here is a standard XML request to SAP below. Where the <R3> tag begins is the application data the JAVA front end is populating for getting info back from SAP. Notice the tag named <I_NAME_2> you will see the European special character.

Now when this message gets to the flow that goes after the SAP data, that tag value looks like this 'Rottmüller'. We do NOT use convert at all in any of our flows todate. I was trying to see if by using it I could see the correct data in another flow.

The lifecycle of our messages is this:
1). JAVA application puts a message on EAI.REQUEST.
2). EAI.REQUEST is input into a flow that looks up in a database to determine the service queue. In this case the message is put onto SAP.Z_RFC_FARMER_SEARCH queue.

3).SAP.Z_RFC_FARMER_SEARCH queue is input into anther flow where the message is parsed out to only the data within the <R3></R3> tags and this is sent to R3.

I think the character is messed up already on #1 or #2.


Any ideas or suggestions would be greatly appreciated.

Thanks,
Mike




<?xml version="1.0" encoding="UTF-8"?>
<REQUEST>
<CONTROL>
<ORIGINATOR>O2O</ORIGINATOR>
<ORIGIN_DATETIME>Fri Jun 03 07:52:28 CDT 2005</ORIGIN_DATETIME>
<SERVICE>R3</SERVICE>
<FUNCTION>Z_RFC_FARMER_SEARCH</FUNCTION>
<DESTINATION>
<INSTANCE>PR2</INSTANCE>
<CLIENT>150</CLIENT>
</DESTINATION>
<VERSION>1.1</VERSION>
<PERSISTENCE>N</PERSISTENCE>
<REALTIME>Y</REALTIME>
<AUDIT_LOG>Y</AUDIT_LOG>
</CONTROL>
<APP>
<R3>
<I_ADDRESS_1>Haager Str. 10</I_ADDRESS_1>
<I_ADDRESS_2/>
<I_ADDRESS_3/>
<I_CITY/>
<I_EMAIL/>
<I_FARMER/>
<I_VKORG>1900</I_VKORG>
<I_ZIP_CODE/>
<I_FAX/>
<I_NAME_1/>
<I_NAME_2>Rottmüller</I_NAME_2>
<I_NAME_3/>
<I_PBC_ID/>
<I_SOLDTO>1010174153</I_SOLDTO>
<I_SPART>10</I_SPART>
<I_SUB_CITY/>
<I_TELE_1/>
<I_TELE_2/>
<I_VIRTUAL_FARMER1/>
<I_VIRTUAL_FARMER2/>
<T_VTWEG>
<VTWEG>40</VTWEG>
</T_VTWEG>
</R3>
</APP>
</REQUEST>
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Unsing Convert Encoding and CCSID on Input Node
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.