A specialized Java Library Service Engine is easier to build, but it could be not relevant.Needs for the Specialized Library Service Engine:

• JBI Specific Library Wrapper Service Engine to glue the Java Library.• WSDL that describe the Library interface.• The Java Library calls are hard coded in the Library Wrapper Service Engine.

2.1.2. Generic JBI Service Engine

A Generic Java Library Service Engine is more complex to build, but it allows at design time touse a Java library by using a WSDL that describe this Java Library.

Needs for the Generic Library Wrapper Service Engine:

• JBI Generic Library Wrapper Service Engine.• WSDL that describe the Library interface.• Wrapper component to glue the Generic Service Engine to the Java Library• Dynamic loading of the Java Library Wrapper from the Generic Service Engine.

2.2. Use case: How to build a Library Wrapper Service Engine ?

For this use case, the Generic approach has been chosen.

The use case will demonstrate how to build a Generic Library Wrapper Service Enginethat uses a Java JNI wrapper Library.

2.2.1. Architecture of the Library Wrapper Service Engine

The Architecture of the Library Wrapper Service Engine is divided into four parts:

- callLib(params): provides the:DOM Node that content datas extracted from the NMR message.messageInput name from the NMR message.

- JNIMapper: to glue the Generic Service Engine with the specific Java JNIWrapper (JNIMapper.jar).JNIMapper extends Mapper for the specific JNIWrapper library.Components of the Generic Library Wrapper Service Engine: LibWrapperServiceEngine