Page History

...

First create the service unit. The service unit is a ZIP file that will contain your application's Java class files and the servicemix.xml configuration file. The service unit can also contain a jbi.xml which provides information about services statically provided and consumed. In ServiceMix it is optional to include this file. In the case of our example, we have not included it.

Wiki Markup

Use a ZIP compression tool, such as Winzip or gzip to create a zip file containing the classes in \[servicemix_dir\]\examples\loan-broker\build\loanbroker\components and the {{servicemix.xml}} file which can be found in {{\[servicemix_dir\]\src\su}}. The zip file name is arbitrary, but it is used in the Service Assembly's {{jbi.xml}} file, so to match the example call it {{loanbroker-su.zip}}.
\\

Wiki Markup

Put the {{loanbroker-su.zip}} file in the {{\[servicemix_dir\]\examples\loan-broker\build}} directory for later use. Note: you may store the zip file anywhere.
\\
\\
The above two steps can be done automatically using the ant script: "ant build-su". If you look in the {{build.xml}} file you will see the {{build-su}} target does exactly what we just did manually.
\\

Create the Service Assembly. A service assembly is a zip file containing one or more service units and a jbi.xml file. The jbi.xml file must be in the META-INF directory. you may also include other files in the META-INF directory. The ZIP file directory structure for our example looks like this:

Code Block
loanbroker-su.zip META-INF\ jbi.xml LICENSE.txt DISCLAIMER.txt

The jbi.xml looks like this:

Code Block

<?xml version="1.0" encoding="UTF-8"?>
<jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0">
     
   <service-assembly>
     <identification>
       <name>loanbroker</name>
       <description>LoanBroker Service Assembly</description>
     </identification>
     <service-unit>
       <identification>
         <name>loanbroker</name>
         <description>LoanBroker Service Unit</description>
       </identification>
       <target>
         <artifacts-zip>loanbroker-su.zip</artifacts-zip>
         <component-name>servicemix-lwcontainer</component-name>
       </target>
     </service-unit>
    </service-assembly>
    
</jbi>

Wiki Markup

\\
\\
The interesting thing to note is that the {{jbi.xml}} file tells the JBI container what service units are in the service assembly and where to deploy them. There is only one service unit in our example, which is "loanbroker" (see the {{artifacts-name}} tag) and the component to which it will be deployed is {{servicemix-lwcontainer}} (see the <component-name> tag). There could be multiple service units in a service assembly and they would each be included in the {{jbi.xml}} file with the same type of information for each. 
\\
Create the service assembly ZIP file and include the {{loanbroker-su.zip}} file and the {{META-INF\jbi.xml}} directory and file in it. To remain consistent with our example, call the zip file {{loanbroker-sa.zip}}.
\\
Put the {{loanbroker-sa.zip}} file in the {{\[servicemix_dir\]\examples\loan-broker\build}} directory for later use. Note: in a real world application you may store the zip file anywhere.
\\

Wiki Markup
The final step is to deploy the service assembly to the JBI container. To do this copy the {{loanbroker-sa.zip}} file to the \[servicemix_dir\]\deploy directory.

Child pages

Versions Compared

Old Version 46

New Version 47

Key

Related Documentation