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 » Message Broker File Extender Best Practices

Post new topic  Reply to topic
 Message Broker File Extender Best Practices « View previous topic :: View next topic » 
Author Message
Ching
PostPosted: Thu Oct 06, 2005 10:31 am    Post subject: Message Broker File Extender Best Practices Reply with quote

Apprentice

Joined: 08 Nov 2004
Posts: 25
Location: Portland, OR

Hey Everyone,

Can everyone who has used the MB File Extender please respond with any tips/tricks or best practices that you have learned.

I've gotten the provided f2f, m2f, and f2m working. Now I'm developing my own.

Here are some questions that I have:

Where can I find more documentation on the file extender? The information I'm looking for is not in the provided C3466660.pdf .

Are you using it in production? What has it been like to support the applications? How easy has it been to recover error files for processing? Any file size issues? CPU/Memory usage considerations?

1. What's best practice for using file input node catch and failure terminnals? How should they be used?

2. How can you tell why a message is "poisoned"? What does it mean if the RestartableStatus is BLOCKED? I can't find why it is blocked from logs

*********************************
SessionId: -1023261223
Broker: FADWBID1
Execution Group: Ching2
Flow: mbfesf2m
NodeTrnsactionOwnerName: FADWBID1.Ching2.mbfesf2m.FileInputNode
LastHandledRecord: 0
RetryCount: 3
RestartableStatus: BLOCKED
NotRestartableReason: POISON_FILE
NotRestartableInfo: null
WorkStatus: status: 'WORKING' - progress: ''.
*********************************
INPUT FILE
1)
FileName: mbfesf2m.Input.Celsius
Directory: null
FileId: 10r1g4h2g
NodeOwnerName: FADWBID1.Ching2.mbfesf2m.FileInputNode
MBFEQueueName: FADWBID1.Ching2.mbfesf2m.FileInputNode-.var.IBM.MBFE.filedata.inbox.mbfesf2m.Input.Celsius$
FirstReadDate: null
LastReadDate: null
OUTPUT FILES
No output file related to this transaction.

4. What are the files in the repository used for? On AIX it's in /var/IBM/MBFE/repository

5. What is best practice for using trace in a production environment? Should it be turned on or off?


I appreciate your help!!!
Ching
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Broker File Extender Best Practices
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.