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 IndexGeneral IBM MQ SupportWhat is the use of POSTCARD in MQ, Where we use

Post new topicReply to topic
What is the use of POSTCARD in MQ, Where we use View previous topic :: View next topic
Author Message
Android 23
PostPosted: Wed Jun 07, 2017 9:26 pm Post subject: What is the use of POSTCARD in MQ, Where we use Reply with quote

Apprentice

Joined: 27 Mar 2017
Posts: 37

From past few days, i'm not able to understand where do we use postcard.

I figured out that we can use it within the queue manager.
Can use it in Publish/Subscribe or in Clustering ?

So could help me guys to understand it in depth
Any materials,URL,stuff is accepted.
Thanks in Advance.

Regards,
Android23
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu Jun 08, 2017 3:54 am Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17448

Postcard is a sample application. It's extremely unlikely you would need to use it for anything other than learning.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
zpat
PostPosted: Thu Jun 08, 2017 5:16 am Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5578
Location: UK

Sadly I have seen this jar file copied or referenced in all sorts of places.

Developers seem to think it's needed to use MQ with java/JMS.

At this point can I repeat some sensible advice on this subject:


Quote:
Installing and upgrading the WebSphere MQ classes for JMS JAR files

The only supported way to get the IBM WebSphere MQ classes for JMS JAR files onto a system, is to install either the IBM WebSphere MQ product, or the WebSphere MQ V7.5 Clients SupportPac- MQC75, or by using a software management tool such as Apache Maven, for more information see IBM WebSphere MQ classes for JMS and software management tools.
Do not move, or copy, the IBM WebSphere MQ classes for JMS JAR files or native libraries, to other machines, or to a different location on a machine where the IBM WebSphere MQ classes for JMS have been installed, unless you are using a software management tool.
Fix packs cannot be applied to an "installation" where JAR files have been copied from another machine, because this makes it much more difficult to ensure that all the JAR files are kept in step with each other, and are at compatible levels.
Copying the IBM WebSphere MQ classes for JMS JAR files between machines can also result in multiple copies of the files residing on the same machine, which can cause problems servicing the code, and debugging problems.
The dspmqver command, used to display version information from a IBM WebSphere MQ installation, only displays version information for the IBM WebSphere MQ classes for JMS installed into the \java\lib directory.
If multiple copies of the files reside on the same machine, running dspmqver might not give accurate information about the version of the IBM WebSphere MQ classes for JMS being used by an application.
Do not include the IBM WebSphere MQ classes for JMS JAR files within application archives (such as enterprise application archives, or EAR files).
Updates to the IBM WebSphere MQ classes for JMS cannot be applied using a IBM WebSphere MQ Fix Pack.
It will not be possible for IBM Support to easily determine the version of the IBM WebSphere MQ classes for JMS that are being used by the application.
Problems can arise if multiple applications running inside the same Java Runtime Environment include different versions of the IBM WebSphere MQ classes for JMS, as multiple versions of the IBM WebSphere MQ classes for JMS are loaded into the Java Runtime Environment at the same time.
Examples of these problems include the following exceptions:
java.lang.ClassCastException :
com.ibm.mq.jmqi.system.JmqiSystemEnvironment incompatible with
com.ibm.mq.jmqi.system.JmqiSystemEnvironment

java.lang.ClassCastException :
com.ibm.mq.jms.MQQueue incompatible with com.ibm.mq.jms.MQQueue
If an application uses the BINDINGS transport to connect to a queue manager, any major upgrades to the queue manager also require the application to be updated to include the corresponding level of the IBM WebSphere MQ classes for JMS.
For example, if a queue manager is upgraded to the IBM WebSphere MQ Version 7.5 level, any applications that connect to the queue manager using the BINDINGS transport also need to be updated to include the IBM WebSphere MQ Version 7.5 classes for JMS.


_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportWhat is the use of POSTCARD in MQ, Where we use
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.