Can you tell me how to identify the version bit of installed IBM WebSphere MQ, 32 or 64? On Windows, Linux and UNIX respectively.
Thanks very much
Use dspmqver -a like so:
bash-3.2$ dspmqver -a
Name: WebSphere MQ
Version: 7.0.1.4
CMVC level: p701-104-110114
BuildType: IKAP - (Production)
Platform: WebSphere MQ for Linux (x86-64 platform)
Mode: 64-bit
O/S: Linux 2.6.18-194.17.4.el5
bash-3.2$
Or on Windows:
C:\>dspmqver
Name: WebSphere MQ
Version: 7.5.0.0
Level: p000-L120604
BuildType: IKAP - (Production)
Platform: WebSphere MQ for Windows
Mode: 32-bit
O/S: Windows 7 Ultimate x64 Edition, Build 7601: SP1
InstName: WMQ75
InstDesc:
InstPath: C:\Program Files (x86)\IBM\WebSphere MQ
DataPath: C:\Program Files (x86)\IBM\WebSphere MQ
Primary: Yes
MaxCmdLevel: 750
C:\>
Here is the dspmqver Infocenter page for V7.1 and V7.5.
dspmqver -f 96
http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/index.jsp?topic=%2Fcom.ibm.mq.doc%2Ffa15760_.htm
Related
I am trying to use ACE Toolkit so that it listens / reads from IBM MQ queue (Docker container, dev version, running locally).
Documentations instructs simply:
"You can use the Security identity property on the MQ node or MQEndpoint policy to pass a user name and password to the queue manager, by specifying a security identity that contains those credentials. The identity is defined using the mqsisetdbparms command."
How do I run "mqsisetdbparms" command, where can I find that command ?
I use Ubuntu Linux (for now).
Alternatively, can I test my ACE Flow so that I run MQ Manager (dev) kind of unsecured way, so that it does not expect user / password ?
Now I am getting error :
2023-01-03 20:57:07.515800: BIP2628W: Exception condition detected on input node 'MQFlow.MQ Input'.
2023-01-03 20:57:07.515866: BIP2678E: Failed to make a server connection to queue manager 'QM1': MQCC=2; MQRC=2058.
.
version: '3.7'
services:
mq-manager:
container_name: mq-manager
build:
context: ./mq
dockerfile: Dockerfile
image: ibm-mq
ports:
- '1414:1414'
- '9443:9443'
environment:
- LICENSE=accept
- MQ_QMGR_NAME=QM1
# - MQ_APP_PASSWORD=passw0rd
.
FROM ibmcom/mq:latest
For local testing, you can configure without usage of mqsisetdbparms like this:
Configure a policy in $YOUR_ACE_WORK_DIR/run/DefaultPolicies/MQ.policyxml:
<policies>
<policy policyType="MQEndpoint" policyName="MQ" policyTemplate="MQEndpoint">
<connection>CLIENT</connection>
<destinationQueueManagerName>QM1</destinationQueueManagerName>
<queueManagerHostname>localhost</queueManagerHostname>
<listenerPortNumber>1414</listenerPortNumber>
<channelName>DEV.ADMIN.SVRCONN</channelName>
<CCDTUrl></CCDTUrl>
<securityIdentity>MqIdentity</securityIdentity>
<useSSL>false</useSSL>
<SSLPeerName></SSLPeerName>
<SSLCipherSpec></SSLCipherSpec>
<SSLCertificateLabel></SSLCertificateLabel>
<MQApplName></MQApplName>
<reconnectOption>default</reconnectOption>
</policy>
</policies>
Configure a remote default queue manager and credentials in $YOUR_ACE_WORK_DIR/overrides/server.conf.yaml:
remoteDefaultQueueManager: '{DefaultPolicies}:MQ'
Credentials:
ServerCredentials:
mq:
MqIdentity:
username: 'admin'
password: 'passw0rd'
Restart your ACE server
We have configured WLP and MQ to use JMS messaging. On a server1 where the Liberty Servers and MQ installed we referred the MQ libraries as below and it's working fine. However, we are not sure from server2 when we make connection to MQ we are using client transport type with port number. How to refer the below MQ libraries on the server2 server.xml? Any help or guidance on this? Thanks
server.xml from server1
server2 JMS connection
<properties.wmqJms
transportType="CLIENT"
hostName="Host1"
port="9001"
channel="SYSTEM.DEF.SVRCONN"
queueManager="QM1"/>
You'll need to copy the file wmq.jmsra.rar to the disk of server2 and then set the path to that file in server.xml using a variable:
<variable name="wmqJmsClient.rar.location" value="/path/to/wmq/rar/wmq.jmsra.rar"/>
See: https://www.ibm.com/docs/en/was-liberty/nd?topic=dmal-deploying-jms-applications-liberty-use-mq-messaging-provider
I am not able to run linux containers in windows server 2016 in AWS cloud.
How to run linux containers in windows server 2016 which requires docker ee version
I'm trying to deploy VMWare vCenter Server Appliance.
Mi virtual datacenter looks like:
1 x host ESXi (10 GB RAM)
Windows Server 2012 Virtual Machine (Primary)
Windows Server 2012 (Secondary)
1 x host ESXi (4 GB RAM)
1 x FreeNAS (Sharing 200 GB HD iSCSI)
I follow this instructions to deploy vCenter Server Appliance:
I've installed a Windows Server VM in mi ESXi host.
I've mounted the iso image of VMWare vCenter Server Appliance.
I've clicked the setup file and started the installation.
I've followed the installation steps for installing vCenter Server Appliance with an Embedded Platform Service Controller.
I've got the followin error during the installation:
Spanish: error de instalación no se pudieron descargar los registros del paquete de soporte de vcenter
English: installation error, vcenter records support package could not be downloaded
Anyone can tell me what is the meaning of this error? How can I fix it? Other way to install VMware vCenter Server Appliance?
#Kroka VMware Prefer the usage of the Appliance btw... And I do it also...
So back to the Problem:
DNS-Lookup is possible for the vcenter appliance? The Gateway is pingable?
Which version of appliance?
Use another Browser
I am trying to monitor a remote IBM WAS with VisualVM but I can't connect.
To enable JMX on the IBM Websphere open the WebSphere administrative console and:
navigate to: Server -> Server Types -> WebSphere application servers ->[SERVER_NAME]
Expand Java and Process Management and click Process definition
Click Java Virtual Machine
In the Generic JVM arguments field append the following properties:
-Djavax.management.builder.initial= -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=1099 -Djava.rmi.server.hostname=XX.228.75.XX
Restart the server
When the server starts, open VisualVM and add a new Remote Connection:
In the connection field, put the server host and the port previously configured, for instance 1099.