Using WebSphere MQ on z/OS for messaging and the WebSphere MQ resource adapter within JBoss EAP 6, I want to set the Application Name that appears when viewing the active handles on a queue.
The default is WebSphere MQ Client for Java and I have not managed to change it. I have no administrative access to the queue / queue manager, I am just the sender posting messages to it.
My configuration for the queues / queue manager are located in the JBoss EAP config file at the resource adapter configurations. I have tried - without success - setting the application name using a config-property inside the connection definition, for example:
<config-property name="PutApplName">
my application name
</config-property>
I have also tried names like applicationName, applName, appName, application or JMS_IBM_MQMD_PutApplName. The latter and the name from the example I have taken from here and here.
How can I change the displayed application name?
Is this even possible without using the specific WebSphere MQ classes inside the java application?
http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/index.jsp?topic=%2Fcom.ibm.mq.dev.doc%2Fq030790_.htm
Somewhere buried in there, it says its not supported for z/OS.
Note: Queue managers running on z/OS® platforms do not support setting
application names.
Related
I have JNDI context in MQ queue manager, my standalone java client is able to do lookup, with initial context class, com.ibm.mq.jms.context.WMQInitialContextFactory, it is working with MQ client jars for versions before MQ 8. It also has the mqcontext.jar in my classpath.
With MQ 8 and 9, I am trying to use the relocatable jars com.ibm.mq.allclient.jar and com.ibm.mq.traceControl.jar in my classpath and the JNDI lookup is failing. If I add the old mqcontext.jar to classpath, I get below error.
javax.naming.NamingException: Caught an MQ Exception: com.ibm.msg.client.jms.DetailedMessageFormatException: JMSCC0053: An exception occurred deserializing a message, exception: 'java.io.InvalidClassException: com.ibm.msg.client.wmq.common.WMQConnectionName; local class incompatible: stream classdesc serialVersionUID = 3226780381239434112, local class serialVersionUID = -2174857328193645055'.
For IBM MQ Classes for JMS you can find the list of files required on the Knowledge Center page "What is installed for IBM MQ classes for JMS":
Relocatable JAR files
Within an enterprise, the following files can be moved to systems that need to run IBM MQ classes for JMS:
com.ibm.mq.allclient.jar
com.ibm.mq.traceControl.jar
jms.jar
fscontext.jar
providerutil.jar
com.ibm.mq.jms.context.WMQInitialContextFactory
I would strongly recommend you not use the MQ queue manager as the resource holder for MQ JNDI. You should either use file based MQ JNDI or LDAP based MQ JNDI.
The last time I checked, using WMQInitialContextFactory would not allow the use of either MQ client-side security exit and/or TLS/SSL. Hence, you have to connect to the queue manager without any security. Bad, bad idea.
With hacks taking place everyday and private/confidential information getting dumped to the web and/or dark web, EVERY queue manager should be locked down tight.
How can one modify the max-beans-in-free-pool property for a given MDB via the Weblogic 10.3.1.0 Console ? I know this can be added in weblogic-ejb-jar.xml configuration file, but want to do this via Weblogic Console.
It doesn't have that feature Admin Console in 10.3.1, not sure for later versions of WLS.
According to WebLogic documentation, it defines a free pool size for EJBs and it's also a property which you could configure your MDB but only using the ejb-jar.xml file and there's no way to do this in the console because it's something that belongs to the application.
Here there is a set of possibles attributes to configure the MDB with annotations or only in the ejb-jar file for Weblogic
Thanks to Maarten I was able to get basic ActiveMQ JMS topics and connection factories working in WAS. He has a nice write up in his reply to this topic: ActiveMQ 5.11 with WebSphere Application Server 8.5
But I cannot find a way to define any ActiveMQ JMS Activation Specs in the WAS admin console. And of course I need those in order to trigger my MDBs. ActiveMQ simply doesn't show up as a JMS provider when creating a new AS.
How do I configure Activation Specs in WAS using ActiveMQ as the provider? Am I missing a jar file?
activemq-client-5.11.0.jar
hawtbuf-1.11.jar
slf4j-api-1.7.10.jar
If you want to use Activation specification, you need to install ActiveMQ as JCA 1.5 compliant resource adapter. As far as I know, ActiveMQ provides resource adapter as separate install.
See also:
Deploying the ActiveMQ Resource Adapter into IBM WebSphere
Managing messaging with a third-party JCA 1.5 or 1.6-compliant messaging provider
ActiveMQ resource adapter
Listener ports are stabilized, and should only be used if provider doesn't support JCA.
Really straight forward once you understand (of course).
From the IBM Redbook mentioned above, sg247770.pdf, we need to configure ActiveMQ as a Generic JMS provider in WAS. And since we want to use Activation Specs, again from the Redbook, we need to use the ActiveMQ Resource Adapter, or rar file. There is a link on the ActiveMQ page to the latest rar, I don't need to provide it here. Once the rar is installed, using the WAS Console/Resources/Resource Adapters menu, you can configure J2C CFs, ASs, and administered objects including Queues and Topics from the rar configuration page. These will all have custom properties where you will enter your destinations, etc.
I'm novice guy in JCA and JMS parts of Java EE stack, and now I'm struggling with JMS bridge configuration between two JMS providers (ActiveMQ 5.9.1 -> Weblogic 11g 10.3.5), and I need some help to understand all the moving parts and required configuration elements.
What I've done already:
JMS server configured on Weblogic 11g node
Configured Foreign Server - AMQ connection factory, and source queue objects bound to the local JNDI (OK: conn. factory and queue objects visible in server jndi tree)
Create JMS Bridge with default props (OK - I think)
Created the Bridge Destination for target destination (Weblogic) with default configuration - where possible (OK: Resource Adapter deployed)
Created the Bridge Destination for source destination (AMQ) - JNDI properties, default props where possible (FAIL - Cannot connect to the source destination)
And there is the question:
By default there are two resource adapters (XA, non-XA), do I need install the AMQ specific resource adapter?
I've assumed that yes, so I've downloaded rar file on Weblogic machine, then tried to install with Weblogic Console (Deployment -> Install), but.. another trouble - no way to achive Running state in Deployments view. I've read that all jars from rar need to be placed in Weblogic CLASSPATH, so I've copied them to Weblogic lib directory. But, with no success so far.
So, what I did wrong, where is the gap or an error in this configuration?
I have studied the Oracle documentation, but I feel still didn't get the complete understanding of the bridge config :((
Any explanatory replies very appreciated!!!
Ok, problem solved. I've used wrong JNDI names of connection factory and queue - local names defined in Foreign Server configuration instead of names on remove JMS server.
Actually, no additional configuration like Foreign Server, or Resource Adapter is needed here.
I'm currently switching from Glassfish to WildFly-8.0.0.Final application server, and my MQ / JMS browser does not support the built-in HornetQ (2.4.0.Final) implementation.
After changing to JMSBrowser 2.6 (which should support HornetQ), I was unable to connect to my running WildFly instance. I presume, I need a little more configuration within the application server to make it work
Can someone supply a working wildfly standalone.xml or standalone-full.xml configuration, that has an enabled remote jmx which can be accessed by QBrowsers?