IBM WebSphere MQ bridge for HTTP on Tomcat 9.0.2

Requirements:

    1. IBM MQ server 

    2. WMQHTTP.war, location MQ_HOME\java\lib\http\

    3. IBM MQ client libraries 

    4. tomcat 

IBM WAS 8.0.0.9 post upgrade issue with MQ connections: disableSSLv3 is set to true

After upgrade to 8.0.0.9 you can get below exceptions if you are using SSL.
You need to change cipher type to TLS in channel configuration and in WAS datasource  in order to resolve it.

Caused by: java.lang.IllegalArgumentException: Only SSLv3 was enabled while com.ibm.jsse2.disableSSLv3 is set to true
        at com.ibm.jsse2.ad.a(ad.java:142)
        at com.ibm.jsse2.ad.<init>(ad.java:65)
        at com.ibm.jsse2.SSLSocketImpl.setEnabledProtocols(SSLSocketImpl.java:714)
        at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.makeSocketSecure(RemoteTCPConnection.java:1886)
        at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.connnectUsingLocalAddress(RemoteTCPConnection.java:711)
        ... 90 more

IBM WebSphere Application Server on z/os, how to increase number of servants regions

To increase number of servants you need:

1. Open dmgr console
2. Servers > app. servers > ${YOUR APP SERVER NAME} > server infrastructure > Java and Process Management > Server Instance
3. Enable Multiple Instances Enabled
4. Set min and max according to requirements.
5. save changes

WDMyCloud problem with mounting(WD didn't accept login and password) network drives on Windows 7

Recently found that my NAS storage doesn't want to accept my credentials.
I checked my NAS dashboard and it's working. I can log in and use it through WD application .

IBM WebSphere MQ v 6.0 corrupted queues

On one qmgr I found 10 corrupted queues/

I don't know why but standard way of deleting and recreating object didn't helped.

Unfortunately that's was not the only problem. 

I decided to create dump of qmgr objects using saveqmgr utility but I got this error since my SYSTEM.DEFAULT.MODEL.QUEUE were in the list of corrupted objects :

SAVEQMGR V6.1.4.0

(mqutils.c) MQOPEN failed for SYSTEM.DEFAULT.MODEL.QUEUE, CC=2 RC=2101 

To identify which queues are corrupted you need simply to use:

echo "dis q(*)" | runmqsc QMGRNAME

At the end what I done:

1. crtmqm test

2. cp /var/mqm/qmgrs/test/queues/YOUDAMAGED QUEUES /var/mqm/qmgrs/YOURQMGR/queues/

3. strmqm -c QMGRNAME with correpted queues

4. you will see that all corrupted objects were successfully recreated .

IBM announce new version of WebSphere MQ v 8.0

Official url:
http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS214-177/index.html&lang=en&request_locale=en

Here are enhancements list:

• Verification of user ID and password, making use of either operating system definitions or a Lightweight Directory Access Protocol (LDAP) repository
• Use of Domain Name System (DNS) host names in Channel Authentication Records (CHLAUTH)
• Channel-level certificates, allowing multiple certificates to be used in a queue manager
• Routed publish-subscribe in clusters
• Enhanced status reporting for publish-subscribe
• Performance enhancements including queue manager scaling and multiplexed client performance
• Support for updated standards
• Support on all platforms for 64-bit queue managers
• Support for multiple transmission queues defined for use in a clustered queue manager on all platforms
• Availability on all platforms of both Advanced Message Security and Managed File Transfer

IBM WebSphere Application Server ND installation using Installation Manager

Download IIM(IBM installation manager):
command line:

./installc -c

GUI problem when you can't add second and third disk:
Check you repository.config file and add there 2 extra line with disk 2 and 3:

cat ~/Desktop/was/repository.config
LayoutPolicy=Composite
LayoutPolicyVersion=0.0.0.1

repository.url.disk1=./disk1
repository.url.disk2=./disk2
repository.url.disk3=./disk3