Checking that the mqweb server is correctly configured on z/OS

Checking that the mqweb server is correctly configured on z/OS

Steps you need to take to check that the mqweb server is correctly configured on z/OS®, and to fix common configuration problems.

Procedure
Check the mqweb server started task. You should see job log messages similar to the following:
+CWWKE0001I: The server mqweb has been launched.
+CWWKZ0001I: Application com.ibm.mq.rest started in 1.493 seconds.
+CWWKZ0001I: Application com.ibm.mq.console started in 0.885 seconds.
+CWWKF0011I: The server mqweb is ready to run a smarter planet.  
There should be no messages in STDERR
There should be messages in STDOUT similar to the following:
Launching mqweb (WebSphere Application Server 17.0.0.2, WAS FOR Z/OS 17.0.0.2, 
MQM MVS/ESA V9 R0.4/wlp-1.0.17.cl170220170523-1818) on IBM J9 VM, 
version pmz6480sr4fp7-20170627_02 (SR4 FP7) (en_US)
[AUDIT   ] CWWKE0001I: The server mqweb has been launched.                                                                                                [AUDIT   ] CWWKG0028A: Processing included configuration resource: /mqm/V9R0M4/web/mq/etc/mqweb.xml                                             
[AUDIT   ] CWWKG0028A: Processing included configuration resource: 
var/mqm/mqweb904/servers/mqweb/mqwebuser.xml                                          
[AUDIT   ] CWWKT0016I: Web application available (default_host): 
yourhost:yourport/api/docs/                                           
[AUDIT   ] CWWKT0016I: Web application available (default_host): 
yourhost:yourport/api/explorer/                                       
[AUDIT   ] CWWKT0016I: Web application available (default_host): 
yourhost:yourport/ibm/api/                                         
[AUDIT   ] CWWKT0016I: Web application available (default_host): 
yourhost:yourport/ibm/api/explorer/
[AUDIT   ] CWWKT0016I: Web application available (default_host): 
yourhost:yourport/ibm/api/docs/subscription/websocket/
[AUDIT   ] CWWKT0016I: Web application available (default_host): 
yourhost:yourport:9080/ibmmq/rest/v1/
[AUDIT   ] CWWKZ0001I: Application com.ibm.mq.rest started in 1.493 seconds.
[AUDIT   ] CWWKT0016I: Web application available (default_host): 
yourhost:yourport/ibmmq/console/
[AUDIT   ] CWWKT0016I: Web application available (default_host): 
yourhost:yourport/ibmmq/console/internal/
[AUDIT   ] CWWKZ0001I: Application com.ibm.mq.console started in 1.459 seconds.
[AUDIT   ] CWWKF0012I: The server installed the following features: 
[jsp-2.2, servlet-3.1, ssl-1.0, jndi-1.0, basicAuthenticationMQ-1.0, 
apiDiscovery-1.0, localConnector-1.0,  appSecurity-2.0, jaxrs-1.1, 
concurrent-1.0, json-1.0, websocket-1.0, distributedMap-1.0, 
applicationMonitorMQ-1.0].
[AUDIT   ] CWWKF0011I: The server mqweb is ready to run a smarter planet.
[AUDIT   ] MQWB2019I: MQ Console level: 9.0.4 - V904-GA904-L171016
[AUDIT   ] MQWB0023I: MQ REST API level: 9.0.4 - V904-GA904-L171016                                  
Notes:
If the procedure fails to start resolve the problems.
If the messages are similar to:
Web application available (default_host): 
http://localhost:portnumber/ibmmq/console/ 
we have not set the httpHost property to allow remote connections to the mqweb server.
<variable name="httpHost" value="*"/> 
If we have changed the httpHost property you will get a message similar to:
Web application available (default_host): 
yourhost:portnumber/ibmmq/console/
Depending on your TCP/IP configuration you might not be able to use the address displayed as a URL.
Changes to the XML server configuration files are picked up a few seconds later. There is no need to restart the mqweb server
Connect to the IBM MQ Console. You should get a window displayed with a title of IBM MQ Console. Notes:
If you see a window with This site can't be reached or Context Root Not Found, the IBM MQ Console is not active; you should wait.
If we do not get a window displayed with a title of IBM MQ Console, there might be additional diagnostics information in WLP_USER_DIRECTORY/servers/mqweb/logs/messages.log, where WLP_USER_DIRECTORY is the directory you specified, when you ran the crtmqweb.sh script to create the mqweb server definition.
Note that this file is in ASCII, and to view the file, we can use oedit from a USS command line, or use ISPF option 3.17 and use the va (view ASCII) line command.
You might get messages in STDOUT similar to:
[WARNING ] SRVE0190E: File not found: /nls/en_GB/labels.json
[WARNING ] SRVE0190E: File not found: /nls/en_GB/errors.json
[WARNING ] SRVE0190E: File not found: /nls/en_GB/strings.json
[WARNING ] SRVE0190E: File not found: /nls/en_GB/pcf.json                                                         
You can ignore these messages.
If we have queue managers defined on the system where the mqweb server is running, and running at the same level as the mqweb server, these queue managers will be displayed in the Local Queue Managers widget in the MQ Console.
If no queue managers are displayed, we do not have any queue managers at the same level as the mqweb server, that have been started since the last IPL.
If you get a message: Lost communication with the server Could not establish communication with the server.

In the procedure used to start the mqweb server:

Check the STEPLIB libraries are at the correct level, and are APF authorized.
Check the PATH and LIBPATH point to the correct path. The PATH and LIBPATH are defined in your web server started task procedure, that you based on sample CSQ4WEBS.

In USS use the command ls -Eltr PathPrefix/web/bin/dspmq, where PathPrefix is the IBM MQ Unix System Services Components installation path. This should display an output similar to -rwxr-xr-t a-s- ... /mqm/V9R0M4/web/bin/dspmq
Check the t and a flags are set.
Use the command:

chmod +t PathPrefix/web/bin/dspmq to set the sticky bit (t)
extattr +a PathPrefix/web/bin/dspmq to set the APF-authorized attribute (a)
Parent topic: Get started with the administrative REST API