Forum Discussion

Ilario72's avatar
Ilario72
Occasional Contributor
4 years ago

unable to send message to weblogic JMS

Hello, I'm unable to send message to weblogic JMS server using ReadyAPI 3.10.0 following the instruction reported in https://support.smartbear.com/readyapi/docs/testing/environments/jms.html and ...
  • Ilario72's avatar
    4 years ago

    I finally solved it following this procedure that I want share to you:

    - insert in <readyapi>/bin/ext/ directory the jar files: weblogic.jar and wlthint3client.jar (get them from from your weblogic machine)
    - Start ReadyAPI
    - create new project, then new test suite and test case
    - add a new JMS Server with:
          - Initial Context Class: weblogic.jndi.WLInitialContextFactory
          - Provider URL: (insert your t3 address, e.g.: t3://twls01:7020 )
          - Connection Factory JMDI Name: insert the JNDI name of your connection factory (see your weblogic configuration)
          - User and Password of weblogic
          - additional JNDI: add java.naming.security.principal (with weblogic user value)
          - additional JNDI: add java.naming.security.credential (with weblogic password value)
    - once created press "test" button to check connection
    - import a new API definition using a wsdl (e.g.: http://www.dneonline.com/calculator.asmx?wsdl )
    - in the test case add new step: JMS Request
    - in the JMS Request popup select interface: SOAP
    - in the JMS Request popup select a operation interface (e.g.: CalculatorSoap->Add)
    - leave empty the options for the new request
    - in the question: Start Hermes for creating JMS objects? press NO
    - in the manual tab insert:
          - JMS Server (select the JMS created)
          - Send JNDI Destination: insert the JNDI name of the queue/topic (see your weblogic configuration)
    - in the step JMS Request insert your xml message and assertion: JMS Status


    As conclusion I believe that in this new version there are too many references to HermesJMS even if it is no longer used, this creates confusion to the user
    and in addition the online documentation is not exhaustive