(ascii)Network=com.ibm.mqe.adapters.MQeWESAuthenticationAdapter
(ascii)Network=com.ibm.mqe.adapters.MQeWESAuthenticationAdapter
(ascii)Network=com.ibm.mqe.adapters.MQeTcpipHttpAdapter
com.ibm.mqe.adapters.MQeWESAuthenticationAdapter. setBasicAuthorization("myUserId@myRealm", "myPassword");Replace the parameters with a valid WES Server user ID and password.
You also need to add code to catch the new MQeException Except_Authenticate after each network operation, in case the supplied credentials were invalid.
System.getProperties( ).put( "http.proxySet", "true" ); System.getProperties( ).put( "http.proxyHost", "wes.hursley.ibm.com" ); System.getProperties( ).put( "http.proxyPort", "8082" );The client queue manager's connection to the target MQe server is similar to a connection that doesn't use the WES proxy.
You need to restart the server and client queue managers for the new settings to take effect. The client should then be able to send messages to the server through the proxy.
If you are using the MQe Example Administration tool, select Connection and then Update to configure this.