Thursday 3 December 2015

Message Broker(IIB) How to configure MQ for remote connection of QM for RFH

Steps to need to do on server assuming operating systme is Linux:

1. Connect to the server by using putty
2. First we need to check whether MQ is installed or not.
3. We need to exeucte following command.
    rpm -qa | grep MQSeries .
4. Switch to the mqm user by using following command
    su - mqm
5. Execute following command to ensure that the path is correct set for MQ
    dspmq command
6. If we get Command not found it means installation path is not set.
7. For setting the instllation path we need to go to the instllation path i.e. typicall /opt/mqm or on Aix /usr/mqm.
     cd /opt/mqm/bin
8. After switching the directory then we will set instllation path by using following command.
     ./setmqinst -i -p /opt/mqm
9. If installation path is already set then ignore above steps.
10. We  need to create user id which is intending to connect to the Remote Qmanager by using RFHUTIL.
11. Considing the user name is 'sreedhar', we exeucte following command, which is to be executed from root. This command will add the user to the group mentioned.
   useradd -g mqm sreedhar
12. After creating user, we  need to give access of the MQ objects  to this user (i .e sreedhar)  by using below command. Note that below command will provide a FULL ACCESS to the QM KCB_DEV_QM
    setmqaut -m KCB_DEV_QM -t qmgr -p sreedhar+all
13. Now we need to disable the channel authorites so that remote clients can connect.

14. We need to enter into the QM and execute the command shown below
      runmqsc KCB_DEV_QM            ---- Enter into QM
      alter qmgr chlauth(disabled)    ---- Disabling Channel Auth
           
15. If MQ installed version is 8 then we have to set the  CONNAUTH to authenticate connections to a queue manager.If MQ version is 7.5 then no need to execute following commands one after the other.

    runmqsc  KCB_DEV_QM
    ALTER QMGR CONNAUTH(USE.PW)
    DEFINE AUTHINFO (USER.PW)  AUTHTYPE(IDPWOS)  FAILDAY (10) CHCKLOCL (OPTIONAL)  CHCKCLNT (OPTIONAL)
    REFRESH SECURITY TYPE (CONNAUTH)
   
16. Now try to connect from RFHUTIL. If we still face problem then check the Qmanger logs once.]


RFH Remote Utils Screenshot



   
   
   
   

    

Message Broker(IIB) SOAP over JMS: WSDL File 4/4

<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="SOAPJMS" targetNamespace="http://www.example.org/SOAPJMS/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.example.org/SOAPJMS/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <wsdl:documentation>
    <wsdl:appinfo source="WMQI_APPINFO">
      <MRWSDLAppInfo imported="true">
        <generatedXSD location="SOAPJMS_InlineSchema1.xsd"/>
        <binding hasEncoding="false" imported="true" name="SOAPJMSSOAPJMS" originalBindingStyle="document"/>
      </MRWSDLAppInfo>
    </wsdl:appinfo>
  </wsdl:documentation>
  <wsdl:types>
   
          <xsd:schema targetNamespace="http://www.example.org/SOAPJMS/" xmlns:ibmSchExtn="http://www.ibm.com/schema/extensions">
<xsd:include schemaLocation="SOAPJMS_InlineSchema1.xsd"/>
    </xsd:schema>
    </wsdl:types>
  <wsdl:message name="SOAPJMSAdditionRequest">
    <wsdl:part element="tns:SOAPJMSAddition" name="parameters"/>
  </wsdl:message>
  <wsdl:message name="SOAPJMSAdditionResponse">
    <wsdl:part element="tns:SOAPJMSAdditionResponse" name="parameters"/>
  </wsdl:message>
  <wsdl:portType name="SOAPJMS">
    <wsdl:operation name="SOAPJMSAddition">
      <wsdl:input message="tns:SOAPJMSAdditionRequest"/>
      <wsdl:output message="tns:SOAPJMSAdditionResponse"/>
    </wsdl:operation>
  </wsdl:portType>
  <wsdl:binding name="SOAPJMSSOAPJMS" type="tns:SOAPJMS">
    <soap:binding style="document" transport="http://www.w3.org/2010/soapjms/"/>
    <wsdl:operation name="SOAPJMSAddition">
      <soap:operation soapAction="http://www.example.org/SOAPJMS/SOAPJMSAddition"/>
      <wsdl:input>
        <soap:body use="literal"/>
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:service name="SOAPJMS">
    <wsdl:port binding="tns:SOAPJMSSOAPJMS" name="SOAPJMSSOAPJMS">
      <soap:address location="jms:jndi:JMSREQUESTQ?jndiConnectionFactoryName=JMSQCF&amp;jndiInitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&amp;jndiURL=file%3A%2FC%3A%2FSOAPJNDIBindings&amp;replyToName=JMSREPLYQ&amp;targetService=SOAPNodesSample_JMS_Service/"/>
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>

Message Broker(IIB) SOAP over JMS: Application Creation 3/4





















Message Broker(IIB) SOAP over JMS: JMS Configuration on MQ 2/4





















Message Broker(IIB) SOAP over JMS: Creation of WSDL 1/4