| Author | Message | 
  		
		  |  Topic: Sap Adapter : Retry option | 
  		
		  | tatyeong 
 Replies: 10
 Views: 8537
 
 |  Forum: WebSphere Message Broker (ACE) Support   Posted: Thu Mar 03, 2011 6:10 pm   Subject: Sap Adapter : Retry option | 
  		
		  | Hi Jhosie, 
 I am aware of the fix and already applied that in my environment.
 
 Where I am coming from is more of when SAP is actually down when the SAPRequest node tries to send the message, does  ...
 | 
  		
		  |  Topic: Rollback to Input Queue from SAPRequest Node | 
  		
		  | tatyeong 
 Replies: 1
 Views: 1507
 
 |  Forum: WebSphere Message Broker (ACE) Support   Posted: Thu Mar 03, 2011 6:48 am   Subject: Rollback to Input Queue from SAPRequest Node | 
  		
		  | Hi, 
 I have message a flow that looks like this
 
 
 MQInput --> Compute --> SAPRequest
 |
 V
 Catch flow
 
 My catch flow handles all the exceptions that are generated beyond it.
 
 I want to ...
 | 
  		
		  |  Topic: Sap Adapter : Retry option | 
  		
		  | tatyeong 
 Replies: 10
 Views: 8537
 
 |  Forum: WebSphere Message Broker (ACE) Support   Posted: Thu Mar 03, 2011 6:21 am   Subject: Sap Adapter : Retry option | 
  		
		  | Hi, 
 Did anyone manage to find out if there is a retry count property which can be set on the SAPRequest node, to handle scenario such as temporary drop in network connectivity so that the message d ...
 | 
  		
		  |  Topic: A Message Set can not contain two global type definitions | 
  		
		  | tatyeong 
 Replies: 4
 Views: 3151
 
 |  Forum: WebSphere Message Broker (ACE) Support   Posted: Thu Sep 16, 2010 4:59 am   Subject: A Message Set can not contain two global type definitions | 
  		
		  | I guess there is no shortcut. I did get the Idoc header from the ABAP developer. 
 Anyway, I regenerate the BO and all is fine.
 
 Thanks
 | 
  		
		  |  Topic: A Message Set can not contain two global type definitions | 
  		
		  | tatyeong 
 Replies: 4
 Views: 3151
 
 |  Forum: WebSphere Message Broker (ACE) Support   Posted: Wed Sep 15, 2010 6:51 am   Subject: A Message Set can not contain two global type definitions | 
  		
		  | Hi, 
 I have a message flow that uses an SAP inbound adapter and convert the idoc into XML before putting in a MQ queue.
 
 Recently there is an additional field added to the IDOC structure. Instead  ...
 | 
  		
		  |  Topic: The object name is not set on the business object | 
  		
		  | tatyeong 
 Replies: 4
 Views: 6629
 
 |  Forum: WebSphere Message Broker (ACE) Support   Posted: Fri Aug 27, 2010 12:49 am   Subject: The object name is not set on the business object | 
  		
		  | Thanks. 
 It works now when I use the SAP adapter wizard to re-create the message set
 | 
  		
		  |  Topic: The object name is not set on the business object | 
  		
		  | tatyeong 
 Replies: 4
 Views: 6629
 
 |  Forum: WebSphere Message Broker (ACE) Support   Posted: Thu Aug 26, 2010 5:25 pm   Subject: The object name is not set on the business object | 
  		
		  | Thanks Gaya, 
 But if that's case, why doesn't it gives any error when I build the message set and message flow?
 | 
  		
		  |  Topic: The object name is not set on the business object | 
  		
		  | tatyeong 
 Replies: 4
 Views: 6629
 
 |  Forum: WebSphere Message Broker (ACE) Support   Posted: Wed Aug 25, 2010 11:23 pm   Subject: The object name is not set on the business object | 
  		
		  | Does any one knows what this error means? I tried to do a search on google but couldn't find anything on this. 
 BIP3450-throw a RecordNotFoundException--com.ibm.j2ca.extension.metadata.exceptions.In ...
 | 
  		
		  |  Topic: wait option in fteCreateTransfer | 
  		
		  | tatyeong 
 Replies: 6
 Views: 9549
 
 |  Forum: IBM MQ File Transfer Edition   Posted: Thu Jul 15, 2010 2:39 am   Subject: wait option in fteCreateTransfer | 
  		
		  | Hi 
 My MQ version is as follow:
 WebSphere MQ for CQM - 7.0.1
 WebSphere MQ for agent QM and command QM - 6.0.2.5
 
 According to IBM, the issue is fixed in APAR IC66063
 | 
  		
		  |  Topic: wait option in fteCreateTransfer | 
  		
		  | tatyeong 
 Replies: 6
 Views: 9549
 
 |  Forum: IBM MQ File Transfer Edition   Posted: Wed Jul 14, 2010 6:18 pm   Subject: wait option in fteCreateTransfer | 
  		
		  | I'm using agent version 7.0.1 on AIX 5.3 
 Here's the FFDC log
 
 
 com.ibm.wmqfte.wmqiface.WMQApiFailureException: cc=2 rc=2195 op=_get - MQGET
 com.ibm.wmqfte.wmqiface.WMQApiFailureException: cc=2  ...
 | 
  		
		  |  Topic: temp output file | 
  		
		  | tatyeong 
 Replies: 3
 Views: 6199
 
 |  Forum: IBM MQ File Transfer Edition   Posted: Wed Jul 14, 2010 6:43 am   Subject: temp output file | 
  		
		  | Thanks, I figured that out too. 
 Anyway, relating to this question is that I was testing a scenario where the source FTE agent went down suddenly during a file transfer. After restarting the FTE age ...
 | 
  		
		  |  Topic: wait option in fteCreateTransfer | 
  		
		  | tatyeong 
 Replies: 6
 Views: 9549
 
 |  Forum: IBM MQ File Transfer Edition   Posted: Wed Jul 14, 2010 6:39 am   Subject: wait option in fteCreateTransfer | 
  		
		  | I want the wait forever behavior, but it timeout after 5 mins during the transfer. 
 Anyway, IBM support mentioned that this 'bug' has been fixed in 7.0.2.1
 I am waiting for my sys admin to upgrade  ...
 | 
  		
		  |  Topic: temp output file | 
  		
		  | tatyeong 
 Replies: 3
 Views: 6199
 
 |  Forum: IBM MQ File Transfer Edition   Posted: Tue Jul 13, 2010 4:12 am   Subject: temp output file | 
  		
		  | Hi, 
 I have set the doNotUseTempOutputFile to true in agent.properties. However when I transfer a file (~500Mb), e.g. text.txt. I see that text.txt being created in destination while the transfer is ...
 | 
  		
		  |  Topic: Message from MQ to JMS | 
  		
		  | tatyeong 
 Replies: 6
 Views: 4991
 
 |  Forum: IBM MQ Java / JMS   Posted: Thu Jul 08, 2010 8:06 pm   Subject: Message from MQ to JMS | 
  		
		  | Thanks all for the suggestions and pointers | 
  		
		  |  Topic: Message from MQ to JMS | 
  		
		  | tatyeong 
 Replies: 6
 Views: 4991
 
 |  Forum: IBM MQ Java / JMS   Posted: Thu Jul 08, 2010 7:57 pm   Subject: Message from MQ to JMS | 
  		
		  | Apparently the XML message contains some fields with URL, and the MDB did not handle it properly when parsing the message |