A DeployableContainer implementation that connects to a remote WebLogic Server 12c (12.1) instance and deploys the test archive using the weblogic.Deployer command. Details of the deployment are later obtained using JMX, by connecting to the WebLogic Domain Runtime MBean service.
Container Injection Support Matrix
|@EJB||@EJB (no-interface)||@Inject (CDI)||@Inject (MC)||@PersistenceContext||@PersistenceUnit|
Default Protocol: Servlet 3.0
Container Configuration Options
|adminUrl||String|| The listen address, port and protocol of the WebLogic domain's Administration Server.
For example, t3://localhost:7001 is a valid adminUrl, if the Administration Server is bound to localhost on port 7001, and supports the t3 protocol for the Admin channel. Valid protocols include t3, http, iiop, t3s, https and iiops. Note that, it would be necessary to enable HTTP tunneling to support the http and https protocols. Refer to the WebLogic Server documentation, on how to set up WebLogic Server for HTTP Tunneling, from the Administration Console.
Also, note that weblogic.Deployer can support only https and t3s to connect to a SSL-secured port, and not iiops. Therefore, the use of iiops is not encouraged.
|adminProtocol||String||The protocol used to connect to the Administration Server when running the weblogic.Deployer command. This is optional, for this is deduced from the adminUrl property|
|adminListenAddress||String||The listen address of the Administration Server; weblogic.Deployer will connect to the Administration Server bound to this address. This is optional, for this is deduced from the adminUrl property.|
|adminListenPort||int||The port on which the Administration Server listens for admin traffic. weblogic.Deployer will connect to the Administration Server at this port. This is optional, for this is deduced from the adminUrl property.|
|adminUserName||String||The name of the WebLogic Server user to use for authentication. Any user specified here, should belong to the Deployers group.|
|adminPassword||String||The password of the WebLogic Server user, to use for authentication.|
|wlHome||String|| The location of the WebLogic Server installation. This property value should be the same as the base directory housing the WebLogic Server installation (a directory containing "wlserver" or similar). This is the same as the WL_HOME environment property set by the commEnv or setDomainEnv scripts.
Assuming a BEA/Oracle home directory of C:\Oracle\Middleware, the wlHome property would typically be C:\Oracle\Middleware\wlserver_12.1.
Arquillian requires the presence of a local WebLogic Server installation since the Arquillian WebLogic Server adapter uses weblogic.Deployer to deploy applications and a WebLogic JMX client to retrieve the deployment information. Both of these operations require certain files in the WebLogic Server installation.
|wlsHome (Deprecated)||String|| Same as the wlHome configuration option.
|target||String|| The target for the deployment. This is either an individual Server or a cluster within the WebLogic domain. If the target is a cluster, Arquillian will perform the deployment on all the running cluster members, but will execute the test only against one member
For an individual server, it's equivalent to the name of the folder inside the "servers" directory where the domains are stored.
|weblogicJarPath||String||The location of the weblogic.jar file within the WebLogic Server installation. The location is typically inferred from the wlHome property, but this can be specified explicitly. Due care must be taken to ensure that all dependent libraries of weblogic.jar are available in the desired locations.|
|jmxProtocol||String||The protocol to use, to connect to the WebLogic Domain Runtime MBean Server. If the value is not specified, it will be derived from the adminUrl property.|
|jmxHost||String||The hostname or IP address to connect to, when creating a connection to the WebLogic Domain Runtime MBean Server. If the value is not specified, it will be derived from the adminUrl property.|
|jmxPort||int||The port on the jmxHost to connect to, when creating a connection to the WebLogic Domain Runtime MBean Server. If the value is not specified, it will be derived from the adminUrl property.|
|useDemoTrust||Boolean||Specifies whether the weblogic.Deployer command and the JMX client should use the WebLogic Demonstration Trust Store when connecting to the Domain Administration Server on a SSL port. The demonstration Trust Store (DemoTrust.jks) should be present in the WebLogic Server installation in the wlHome/server/lib directory. This is meant to be enabled when the Administration Server is configured to use the Demonstration Trust Store as the Trust Store.|
|useJavaStandardTrust||Boolean||Specifies whether the weblogic.Deployer command and the JMX client should use the Trust Store of the JRE when connecting to the Domain Administration Server on a SSL port. This is meant to be enabled when the Administration Server is configured to use the Java Standard Trust Store as the Trust Store.|
|useCustomTrust||Boolean||Specifies whether the weblogic.Deployer command and the JMX client should use a Custom Trust Store when connecting to the Domain Administration Server on a SSL port. The location of the trust store is specified by the trustStoreLocation property. This is meant to be enabled when the Administration Server is configured to use a Custom Trust Store as the Trust Store.|
|trustStoreLocation||String||The location of the truststore to use when connecting to an Administration Server on a SSL channel. This value is ignored when one uses the Demo Trust or the Java Standard Trust Store, and is therefore considered only when you use a Custom Trust Store.|
|trustStorePassword||String||The password used to protect the truststore. Usually, one need not specify a password, as the trust store entries (in a JKS file) can be read without a password.|
|hostnameVerifierClass||String||The fully qualified class name of the hostname verifier class.|
|classPath||String||The classpath entries that will be added to the classpath used by weblogic.Deployer. The location of the hostname verifier class can be provided via this property.|