TIBCO BusinessWorks shared modules are designed to promote reusability and modularity. They export specific components for use in application modules or other shared modules. Public processes are explicitly designated for external invocation, allowing other modules to reuse common business logic. Shared resources, such as JDBC or JMS connections, are also exported. This allows multiple applications to use a single, centrally managed resource configuration, ensuring consistency and simplifying maintenance. These two functionalities form the core of what a shared module exposes for reuse.

A. reference bindings: Reference bindings are configured at the application level to link a component reference to a concrete service, not exported by the shared module itself.

B. private processes: By definition, private processes are encapsulated within the shared module for internal logic and are not visible or accessible to other modules.

D. service bindings: Service bindings, which expose a service via a specific transport (like HTTP), are configured in the application, not exported from the shared module.

1. TIBCO BusinessWorks™ Concepts Guide (Version 6.8, Page 53, "Shared Modules"): "A shared module can contain processes, schemas, and resources. Processes in a shared module can be either public or private... Shared resources in a shared module can be used by application modules that have a dependency on the shared module." This directly supports that public processes and shared resources are the exported functionalities.

2. TIBCO BusinessWorks™ Application Development Guide (Version 6.8, Page 101, "Process Visibility"): "Processes in shared modules can be either public or private. Public processes can be called from other modules. Private processes can only be called by other processes in the same shared module." This confirms the role of public processes as an exported asset.

3. TIBCO BusinessWorks™ Application Development Guide (Version 6.8, Page 103, "Shared Resources in a Shared Module"): "You can add shared resources to a shared module. The shared resources can be used by the application module that has a dependency on the shared module." This verifies that shared resources are a key exportable functionality.