Submit and vote on feature ideas.

Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

Different Protocol's in the same TestSuite

Options
daruna1
daruna1 Posts: 8

Hello All

Tried, Http Protocol & WebSphere MQ(Posting a messaging to a Queue), in the same TestSuite and it does not work.

Comments

  • jakubiak
    jakubiak Posts: 804 admin
    Options

    That is a core feature of SOAtest and we have many nightly tests running internally that verifies that it works. I would suspect that there is some kind of misconfiguration.

  • benken_parasoft
    benken_parasoft Posts: 1,243 ✭✭✭
    Options

    it does not work

    If you are getting a particular error or test failure message that you do not understand, please post it here so someone can help you interpret it.

  • Rajasekar_Subburaj
    Options

    I am also not able to use both the https and MQ in same test suite.. I added one test with https and one with MQ along with the respective certificates. I opened the SOATest after adding the IBM JDK in the target path and added the shortcut.
    After opening the Keystore in that test suite. I am getting Invalid Key store format for https protocol test case. Could you please provide the solution for this one .

  • Ireneusz Szmigiel
    Ireneusz Szmigiel Posts: 228 ✭✭✭
    Options

    Hi Rajasekar_Subburaj,

    the error which you see is related to format of key/certificate used in your communication protocol/transport.
    As you maybe are aware, Oracle Java and IBM Java are using a "little bit" different implementation ( in other words, there are small differences to which you may need to pay attention).
    One of them might be format or types of supported encryption algorithms.
    There is nothing wrong with SOAtest, but you have to ask or check what algorithms are used in your keystore/certificate.
    Or check if certificate has been created using different JDK/SDK.
    To summarize here, there are few reasons of such message and I'm mentioning only related to your error, I think:

    • The source keystore was created using an IBM SDK, and the import is attempting to use OpenJDK/Oracle JDK which results in the 'Invalid keystore format' error.
    • The cacerts file is using the wrong format or is corrupted.

    You might need to contact person who is responsible for endpoints in your test to verify such case.

    Ireneusz Szmigiel
    http://www.catb.org/esr/faqs/smart-questions.html

  • jakubiak
    jakubiak Posts: 804 admin
    Options

    In some cases an IBM JRE might need to be used - not sure if that is the case here or not though.

  • daruna1
    daruna1 Posts: 8
    Options

    Is there any URL encoding or anything expected while post MQ Messaging. The Body of the Message does not get decoded

    PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nd2luZG93cy0xMjUyJz8+DQo8bnMwOkNDUF9UcmlnZ2VyIHhtbG5zOm5zMD0iaHR0cDovL3NjaGVtYXMubWwuY29tL0NDUC9TdGFuZGFyZHMvQ29tbW9uL01lc3NhZ2luZy9DQ1BfVHJpZ2dlcl92MV8wLyI