h3. Service Unit Descriptor
The Service Unit descriptor file ( jbi.xml ) looks like this:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:petals="http://petals.objectweb.org/extensions"
xmlns:jbi="http://java.sun.com/xml/ns/jbi" version="1.0">
<jbi:services binding-component="false">
<jbi:consumes interface-name="{http://petals.objectweb.org}HelloworldInterface">
<petals:params>
<petals:param name="address">scn://localhost:26400</petals:param>
<petals:param name="destination-name">queueConsumer</petals:param>
<petals:param
name="initial-context-factory">fr.dyade.aaa.jndi2.client.NamingContextFactory</petals:param>
<petals:param name="connection-factory">qcf</petals:param>
<petals:param name="user">anonymous</petals:param>
<petals:param name="password">anonymous</petals:param>
<petals:param name="transacted">false</petals:param>
<petals:param name="operation">printMessage</petals:param>
</petals:params>
</jbi:consumes>
</jbi:services>
</jbi:jbi>
{code}
JMS communication attributes:
JMS communication attributes:
{center}{*}Service Unit attributes to provide services*{center}
{table-plus:columnAttributes=,,style="text-align:center;",style="text-align:center;",style="text-align:center;"}
|| {color:#333333}Parameter{color} || {color:#333333}Description{color} || {color:#333333}Default{color} || {color:#333333}Required{color} ||
| consumes | Name of the JBI service that will be called into the JBI environment. When a JMS message is received. Only the interface (qname) name can be provided (the container will choose a ServiceEndpoint for this interface), or you can only set service (qname) and endpoint (string) names, without the interface name. | \- | Yes |
| address | Address composed of the URL provider (JNDI access) and the destination name to listen to | \- | Yes |
| destination-name | The JMS destination name where messages will be sent (Queue or Topic JNDI name) | \- | Yes |
| initial-context-factory | The initial-context-factory class name, used to create an InitalContext. | \- | Yes |
| connection-factory | name of the JMS ConnectionFactory registered. | \- | Yes |
| user | User name to access the JMS Destination. | "" | Yes |
| password | Password to access the JMS Destination. | "" | Yes |
| transacted | JMS communication transacted mode. true or false. | "false" | No |
| operation | JMS operation property. | \- | Yes |
{table-plus}
Extra attributes:
{center}{*}Advanced configuration of Service Unit (consumes elements)*{center}
{table-plus:columnAttributes=,,style="text-align:center;",style="text-align:center;",style="text-align:center;"}
|| {color:#333333}Parameter{color} || {color:#333333}Description{color} || {color:#333333}Default{color} || {color:#333333}Required{color} ||
| mep | Message exchange pattern abbreviation. This parameter can be used in conjunction with a method of the Listeners: createMessageExchange(Extensions extensions). This method returns
a MessageExchange corresponding to the type of the specified pattern. \\
Admitted values are: {{InOnly}}, {{RobustInOnly}}, {{InOptionalOut}}, {{InOut}}. | \- | Yes |
| operation | Operation to call on a service. This parameter can be used in conjuntcion
with the sendXXX methods of the Listeners. If no operation is specified in the MessageExchange to send, this parameter will be used. | \- | Yes |
| timeout | Timeout in milliseconds in a synchroneous send. This parameter can be used in conjunction with the *sendSync(MessageExchange exchange)* method of the Listeners. With this, a synchroneous send is done with this timeout value. \\
0 for no timeout. \\
int number >= 0 for a timeout. | \- | No |
| org.objectweb.petals.routing.strategy | This property defines the routing strategy. Two kind of strategies can be defined: highest or random. The others parameters represents respectively the local ponderation, the ponderation of the remote active endpoint and
the ponderation of the remote inactive endpoint. \\
The 'random' strategy chooses an endpoint in function of defined ponderations. The endpoints that have the strongest ponderation can be more easely choose in comparison with the others. \\
The 'highest' strategy chooses the first endpoint in the list that have the
strongest ponderation. | \- | No |
| org.objectweb.petals.transport.compress | The payload of a MessageExchange is an XML file. It can be interesting to compress it before messages are exchanged between two PEtALS nodes. \\
Values are {{true}} or {{false}}. True activates the compression of the message content. | \- | No |
| org.objectweb.petals.messaging.noack | All JBI exchanges end by a message containing a DONE or ERROR status. The consumer must accept those messages, otherwise they are accumulated in the NMR. Moreover, thoses messages cause useless trafic. \\
Values are {{true}} or {{false}}. True make DONE or ERROR messages not sent.
| \- | No |
| org.objectweb.petals.transport.qos | This property sets up the policy of the Quality of Service supported by Petals Transporter. \\
Possible values are: {{reliable}}, {{fast}}. If not specified, the reliable policy is selected by default. | "reliable" | No |
| operation | JMS operation property. | \- | Yes |
{table-plus}
{center}{*}Interceptors configuration in the Service Unit*{center}
{table-plus:columnAttributes=,,style="text-align:center;",style="text-align:center;",style="text-align:center;"}
|| {color:#333333}Parameter{color} || {color:#333333}Description{color} || {color:#333333}Default{color} || {color:#333333}Required{color} ||
| name | Name of the interceptor to use, defined in the component. | \- | Yes |
h3. Service Unit content
The Service Unit has to contain the following elements, packaged in an archive:
* The META-INF/jbi.xml descriptor file, has described above
{code}
service-unit.zip
+ META-INF
- jbi.xml (as defined above)
{code}
h1. Component Configuration
The following attributes can be set during the installation phase to configure the component, using the params element of the jbi-install-component ANT task:
no configuration for this component (JBI).
{center}{*}Configuration of the component (CDK)*{center}
{table-plus:columnAttributes=,,style="text-align:center;",style="text-align:center;",style="text-align:center;"}
|| {color:#333333}Parameter{color} || {color:#333333}Description{color} || {color:#333333}Default{color} || {color:#333333}Required{color} ||
| pool-size | Number of threads listening to messages coming from the JBI container 0
(JBIListeners). \\
Int number >= 1 | 0 | No |
| ignored-status | When the component receives an acknowledgement message exchange, it can skip the processing of these message according to the type of the acknowledgment. If you decide to not ignore some acknowledgement, the component listeners must take care of them. \\
\\
Accepted values : DONE_AND_ERROR_IGNORED, DONE_IGNORED, ERROR_IGNORED or NOTHING_IGNORED | DONE_AND_ERROR_IGNORED | No |
| properties-file | Name of the file containing properties used as reference by other parameters. Parameters reference the property name in the following pattern $\{myPropertyName}. At runtime, the expression is replaced by the value of the property. \\
\\
The value of this parameter is :
* an URL