An Arquillian container adapter (DeployableContainer implementation) that can connect and run against a remote (different JVM, different machine) WebSphere Liberty Profile V8.5.5 and run tests on it over a remote protocol (effectively in a different JVM).
Container Injection Support Matrix
|@EJB||@EJB (no-interface)||@Inject (CDI)||@Inject (MC)||@PersistenceContext @PersistenceUnit|
This DeployableContainer has been tested with WebSphere Application Server Liberty Profile V18.104.22.168. You can find the download on the WASdev Liberty Profile download site.
Prerequisite WLP Configuration
In the server.xml of the WLP server at least enable the following features:
enable security, one example would be:
You need to have those keys trusted by your client as well, otherwise you'll see SSL certificate trust errors, and you need to give permission for the container adapter to write to the dropins directory:
If you need a sample server.xml, please refer to the one in our source repository.
Default Protocol: Servlet 3.0
Container Configuration Options
|serverName||String||defaultServer||Name of the liberty server instance to connect to.|
|hostName||String||None||Hostname for the target machine where the WebSphere Liberty Profile server is running.|
|username||String||None||The username to use to connect to the target.|
|password||String||None||The password to use to connect to the target.|
|httpPort||Integer||9080||HTTP Port of the server.|
|httpsPort||Integer||9443||HTTPS Port of the server.|
|serverStartTimeout||Integer||30||Time in seconds to wait for the application server to start|
|appDeployTimeout||Integer||20||Time in seconds to wait for the application deployment to complete and the application to start|
|appUndeployTimeout||Integer||2||Time in seconds to wait for the application undeployment to complete|
|outputToConsole||Boolean||true||When enabled output from the application server process will be emitted to stdout|
Example of Container Configuration (arquillian.xml)
Example of Maven profile setup