Chapter 4
[ 55 ]
The figure above shows the file binding component acting as a Provider of messages.
In this scenario, a message has been sent to the JBI container, and picked up by
a protocol-specific binding component (for example, a SOAP message has been
received). A JBI Process then occurs within the JBI container which may include
routing the message between many different binding components and Service
Engines depending upon the process. Finally, after the JBI Process has completed,
the results of the process are sent to File Binding Component which writes out the
result to a file.
The figure above shows the file binding component acting as a Consumer of
messages. In this situation, the File Binding Component is periodically polling the
file system looking for files with a specified filename pattern in a specified directory.
When the binding component finds a file that matches its criteria, it reads in the file
and starts the JBI Process, which may again cause the input message to be routed
between many different binding components and Service Engines. Finally, in this
example, the results of the JBI Process are output via a Binding Component.
Of course, it is possible that a binding component can act as both a provider and
a consumer within the same JBI process.
Pages:
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68