...
One of the overarching ideas in JBI is that every integration scenario should not require custom code to be created. Instead, the most common components should be provided by vendors that use the JBI APIs. This will make the integration developers' job a bit easier because they are most concerned with simply providing a configuration for these existing components. In JBI parlance, binding components (BCs) and service engines (SEs) are defined by the JBI spec and are key building blocks for working with JBI containers. However, the JBI APIs are meant to be used for container development and not for application development. The difference here is subtlesubtile, but important. To better understand the difference, let's examine the differences between these two roles.
...
- A developer needs to support the SNMP protocol - Because a JBI binding component does not yet exist for the SNMP protocol, this developer would need to create a new JBI binding component that speaks the SNMP application layer protocol to integrate SNMP messages into the JBI normalized message router (NMR).
...