| Author |
Message
|
| WBIBB |
 Posted: Wed Aug 20, 2003 12:07 pm Post subject: Postit error>> Message catalog cannot be opened |
 |
|
Novice
Joined: 24 Jul 2003
Posts: 19
|
Hi,
I have seen couple of postings about the above error but haven't found
any solution.I am getting this error on deploy of message flow.
Broker is on AIX5V1 , CC on WINNT & POSTIT(V2.5) .MQSIV2_postit is installed in wmqi/messages/En_US directory.
"BIP0054E Cannot open message catalog file MQSIV2_postit.
The message catalog file could not be opened.
The text for the message 15 could not be obtained".
Any help would be appreciated and also insights about the performance in RQST> RPLY model .
Thanks in advance |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Wed Aug 20, 2003 1:50 pm Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
| Probably a silly question, but are the permissions on the file correct? |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Aug 20, 2003 2:48 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Looking on my system, the properties files (which contain all the messages) are in the Messages directory.
The only file in Messages\En_US is an html.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| WBIBB |
| Posted: Thu Aug 21, 2003 5:34 am Post subject: |
|
|
Novice
Joined: 24 Jul 2003
Posts: 19
|
Hi Guys,
Thanks for your reply,
vmcgloin:
The permissions for file is read only and I do have some NeonMIF20.cat files.I tried to deploy a messageflow with Neon nodes and went thru successfully.
Eddie:
The installed path of MQSIV2_postit.cat is in /usr/opt/wmqi/messages.I was trying out the sample message flow which is in the document.I found that if I remove the postitApply node then it gets deployed.It seems like it doesnt like the configuration done.I was trying to copy the request input tree and then apply it on output reply message as in the document..
Would appreciate your help.
Regards
Mike |
|
| Back to top |
|
|
| mpuetz |
| Posted: Thu Aug 21, 2003 12:39 pm Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
if you install the message catalog in /usr/opt/mqsi/messages
you still need to make the approriate link in the /usr/lib/nls/msg
directory (this assumes that you are using the default language
locale settings. The link may have to be created in a subdirectory of
/usr/lib/nls/msg depending on your locale settings).
Detailed background information can be found in:
Chapter 6 section "event logging from a plugin-node" in the
programming guide of WMQI 2.1.
For AIX syslog messages with national language, see the information on message facility overview for programming in AIX Version 4.3 General Programming Concepts: Writing and Debugging Programs, SC23-4128.
If this message catalog is properly installed correct messages will be logged into the syslog of the broker machine *only*.
To get the correct messages in your control center you need to
install the *.properties file with the messages for the control center
in the install_dir/messages directory on your local control center
machine.
Anyway, all of this is completely *optional*. If the message catalogues are not found by WMQI (CC or broker) you will get a standard message
like the one you are seeing. The fact that you are getting this std. message does *not* imply that the missing message catalog is the
actual *cause* for the message to appear. The cause in your case
is most likely a consequence of a property of the plugin node being
set to an invalid value, and the code which checks the parameters
for consistency raises a configuration exception. Once the
cause is eliminated your flow should deploy and run without
message catalogs properly installed.
To find out the cause for the deployment error you are seeing
either properly install the links to the message catalog and
install the properties file for the CC
or
simply go into the message catalog source definition files and read
what message number 15 means.
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
| mpuetz |
| Posted: Thu Aug 21, 2003 12:42 pm Post subject: postit-plugin performance in req/reply |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi again,
unless your typical reply times of your backend service
is more than a few seconds and you only have a limited
number of postits floating around in your shared memory
(say < 1000) the performance impact of the postit-plugin
itself is absolutely negligible compared to the overheads
of getting the message off and on a queue and parsing
the request and reply messages.
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
| WBIBB |
| Posted: Thu Aug 28, 2003 11:39 am Post subject: Postit >> Implementation scenarios |
|
|
Novice
Joined: 24 Jul 2003
Posts: 19
|
Hi Mathias,
Thanks for your reply and I guess there was something wrongly set in property.I got it working but have to test the error messages after changes have been made..
I have couple of questions about the scenarios in which postitcreate and positapply work together.
1.I have a message flow1 which has postit create and message flow2 which has postit apply.I would like to test message flow1 with MSG1 and MSG2 and then store the contents of both messages in shared memory under 2 postit tag names.
msgflow2 : Input > postitapply(MSG1) > positapply(MSG2) > output
2.I have 2 positapply nodes in sequence for message flow2 copying data to a common output message.How should I use matchon property in postitapply node and implement it at execution group and broker level
Would appreciate help from anyone who have implemented similiar scenarios ..
Regards
Mike |
|
| Back to top |
|
|
|
|
