LibraryLink ToToggle FramesPrintFeedback

A Service Assembly Project

FUSE ESB requires that all service units be bundled into a service assembly before they can be deployed into a container. The FUSE ESB Maven plug-in will collect all of the service units to be bundled and the metadata needed for packaging. It will then build a service assembly containing the service units.

FUSE ESB provides a Maven artifact for seeding a service assembly project. You can seed a project with the smx-arch command. As shown in Example C.8, the smx-arch command takes two arguments. The groupId value and the artifactId values correspond to the project's group ID and artifact ID.


The double quotes(") are required when using the -DgroupId argument and the -DartifactId argument.

A service assembly project typically only contains the POM file used by Maven.

You configure the Maven plug-in to package the results of the project build as a service assembly by changing the value of the project's packaging element to jbi-service-assembly as shown in Example C.9.

The Maven plug-in needs to be told what service units are being bundled into the service assembly. you do this by specifying the service units as a dependencies using the standard Maven dependencies element. You add dependency child element for each service unit. Example C.10 shows configuration for a service assembly that bundles two service units.

Example C.11 shows the POM file for a project building a service assembly.

Example C.11. POM for a Service Assembly Project

<project xmlns=""


    <parent> 1

  <name>CXF WSDL Fisrt Demo ::  Service Assemby</name>
  <packaging>jbi-service-assembly</packaging> 2

  <dependencies> 3

      <plugin> 4

The POM in Example C.11 does the following:


Specifies that it is a part of the top-level project described in Example C.2.


Specifies that this project builds a service assembly.


Specifies the service units the service assembly bundles.


Specifies that the FUSE ESB Maven plug-in is to be used.