A DeployableContainer implementation that can connect and run against a remote (different JVM, different machine) running a WebSphere Application Server V7.0 profile. This implementation has no lifecycle support, so it can not be started or stopped.
|This container implementation has been deprecated as the WebSphere Application Server version has reached its end of service.|
|This container implementation is currently not available in public maven repositories. If you want to use it, please follow our build instructions.|
Container Injection Support Matrix
|@EJB||@EJB (no-interface)||@Inject (CDI)||@Inject (MC)||@PersistenceContext @PersistenceUnit|
This DeployableContainer requires WebSphere Application Server fix pack V18.104.22.168 or higher.
Default Protocol: Servlet 2.5
Container Configuration Options
|remoteServerAddress||String||localhost||Hostname for the target machine where the WAS profile is running.|
|remoteServerSoapPort||Integer||8880||SOAP port of the target WAS profile.|
|securityEnabled||Boolean||false|| Defines whether security is enabled.
Note: When security is enabled you have to use an IBM SDK, otherwise the SSL connection will fail.
|username||String||admin||The username to use to connect to the target. - This is required even when security is disabled.|
|password||String||admin||The password to use to connect to the target.|
|sslTrustStore||String||""||The location of the SSL Trust store to use. - This is required when security is enabled.|
|sslTrustStorePassword||String||WebAS||The password for the SSL Trust store. - This is required when security is enabled.|
|sslKeyStore||String||""||The location of the SSL Key store to use.|
|sslKeyStorePassword||String||WebAS||The password for the SSL Key store.|
Example of Container Configuration (arquillian.xml)
Example of Maven profile setup