3.3.2. Deploying the fragment
Prev | 3.3. Remote control extension | Next

### 3.3.2. Deploying the fragment

Once you have written your fragment, you still need to make all components aware of its presence. This is done by exporting the fragment and deploying it into the remote control.

| The AUT remote control status (succuessfully loaded or warnings occurred) of a deployed fragment is echoed to the console of the ITE as well as the testexec when the connection to the AUT gets established.

There are different ways for installing your fragment into the remote control, depending on the AUT Agent used and the specific AUT. You are free to use either the embedded AUT Agent or the standalone AUT Agent. Also your AUT can be based upon the OSGi framework or not. The following table shows an overview, where to deploy your fragment:

| without OSGi (Swing, SWT, JavaFX) | with OSGi (RCP, GEF)
embedded AUT Agent | ITE | AUT
standalone AUT agent | standalone AUT agent

It shows, in which case you usually deploy your fragment into

- the ITE with a feature including your fragment,

- the standalone AUT Agent by adding your fragment to its configuration, or

- the AUT with a feature including your fragment.

The configuration of the standalone AUT Agent can be done by modifying the file server/configuration/config.ini. There you have to append ,fragment_id at the end of the line starting with osgi.bundles=. Make sure that the bundles are comma-separated. It is also necessary to add the argument -clean in the file server/autagent.ini, when deploying a new version with the same fragment ID. Apart from the deploying methods mentioned, it is also possible to install your fragment using a p2 repository or the OSGi console.

If you have deployed fragments for the JavaFX RC bundle, you have to keep in mind that if you are executing the ITE with Java 7 the RC bundle is not active and therefore the wiring for the fragments has not been done by the OSGI framework. The current workaround in Jubula is that all the fragments for the JavaFX RC bundle are added, without taking any version ranges from the fragments into account.

You should be able to test your new component once you have installed the toolkit feature into the ITE and the fragment as described before.