Arquillian deploy to remote domain EAP 6.1 fails - How to specify server?

[nswartz99]

I have some integration tests that build a test.ear and deploy to an EAP 6.1 running on a remote server. I have it working when the remote server is standalone.

I created a domain managed server and am trying to use it, but it is failing. I suspect that I need to specify the server or server group somewhere in arquillian.xml,

but I don't understand the structure of this file and cannot find examples.

I have a description from running arquillian test on domain remote but it is not good enough to write the arquillian.xml.

Here is what I am using now:

    <defaultProtocol type="Servlet 3.0" />

    <engine>

        <property name="deploymentExportPath">target</property>

    </engine>

    <container qualifier="jbossas" default="true">

        <configuration>

            <property name="managementAddress">remote_server</property>

            <property name="managementPort">9999</property>

            <property name="username">deploy</property>

            <property name="password">password</property>

        </configuration>

        <protocol type="Servlet 3.0">

            <property name="host">remote_server</property>

            <property name="port">8080</property>

        </protocol>

    </container>

This fails with

Caused by: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "JBAS014807: Management resource '[(\"deployment\" => \"test.ear\")]' not found"

        at org.jboss.as.arquillian.container.ManagementClient.checkSuccessful(ManagementClient.java:339)

I have several server groups and several servers, but only 1 is runnning.

I do not want to add anything to my test code and I think I should be able to specify the server in the arquillian.xml

[nswartz99]

OK, I got through it. Here is what is needed:

1. You must use jboss-as-arquillian-container-domain-remote instead of jboss-as-arquillian-container-remote. Best way to do this is to have two profiles: 1 for standalone and one for domain deployment

2. You need to add @TargetsContainer("your-server-group") after each @Deployment in your tests. The "your-server-group" name must match the server groups in your domain. If not, you can add a name map in the arquillian.xml -- I did not try this, but should be simple. That will avoid having to hardcode the server group names

3. You need to use two different arquillian.xml for standalone and domain. For standalone use "<container qualifier="your-server-group" default="true"/> You can also include port and IP information and protocol/servlet info there if needed. For domain use "<group qualifer="jbossas" default="true"><container qualifier="DomainController" /></group> - You should include configuration and protocol/servlet information if needed.

4. The namemap can go in as a property in the domain controller container.Namemap is a comma delimited string or name=value pairs. Not sure which is the name and which is the value.

5. References running arquillian test on domain remote and arquillian configuration with domain mode test?

[kpiwko]

Hi Neil,

thanks for figuring that out yourself! There is one thing that might help you, you can have single arquillian.xml file with 2 <group>s and in your profiles simply set arquillian.launch property. Otherwise you hit the nail. Example is here:

Maven selection:

https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-browsers-scenario/pom.xml#L421

Arquillian.launch file:

https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-browsers-scenario/src/test/resources/arquillian.launch

Arquillian.xml file:

https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-browsers-scenario/src/test/resources/arquillian.xml#L52

Karel

[nswartz99]

Some more observations:

The property is "'containerNameMap" and the name is the name of the server group in the domain and the value is the string in the TargetsContainer() annotation in the code.

You cannot have a server group with the name matching the targetsContainer in the domain. If you do, it will be used instead of the mapped name.

Maybe we could consider this a bug. If I use a mapping, I want to to be used, not ignored. There is a reason why I wanted to deploy to a different servergroup.