Forum Discussion

BA_Service_Haus's avatar
BA_Service_Haus
Regular Contributor
14 years ago

[Resolved] Deploying Mocks on WLS

Hi,

in the past we often had trouble to deploy soapUI mocks on a WebLogicServer.
So I hope you can help us to find the reason.

To make all steps reproducible I will use the soapUI example Service (delivered with every soapUI installation package).

The first thing I want to know is, which settings to choose when using the "deploy as war" feature.

I usually choose "Script Library" as groovy is used within the mocks, and "WebUI" (see attached screenshot)

Is this correct. Or do I have to choose more or less options to run the soapUI example Service-Mock on an WLS?

Best regards
Nico

12 Replies

Show More
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hi Nico,

    ufortunately these all look like they are related to the class-loading problem we tried to target with the configuration changes; the mock is not getting the correct classes when trying to execute its code which results in internal errors which in turn results in these responses. You would have to dig further into that issue first...

    regards,

    /Ole
    SmartBear Software
  • BA_Service_Haus's avatar
    BA_Service_Haus
    Regular Contributor
    13 years ago
    Hi Ole,

    this issue is some months ago, but finaly I solved it today.
    At the end you were right: it was a classloading problem.

    I used the cat-tool of the WLS (http://wls-host:port/wls-cat) and it suggested how to fill the <prefer-application-packages> part of the weblogic-application.xml.
    So I just had to insert the suggested XML into a weblogic-application.xml and build an ear-archive out of this file and the soapUI-Mock (war-file).

    That's it.

    Now all dispatching-methods are running problem-free. And also FAULTs are returned. And last but not least the XmlHolder can be used again (I had to switch to XmlSlurper in the past).

    Best regards