Shared Objects

Shared objects include:

  • Resource templates and resource instances based on those templates. There are several types of such shared resource. Commonly-used ones include:
    • JDBC resource instances for connection to an external database.
    • HTTP clients to provide connection to a web service.
    • SMTP resources to provide connection to an SMTP mail server.
    • JMS resource instances enable applications to access objects maintained in JMS servers.
    • LDAP connections define the connection details of the LDAP directory you intend to use.
    • Keystore providers. These provide a reference to a keystore that contains the keypair required to invoke a secured web service.
    • Identity providers. These provide a reference to a specific keypair required to invoke a secured web service.
      Note: Resource templates are defined with a scope, which can be at enterprise level, environment level, or application level. TIBCO ActiveMatrix BPM resources are scoped at application level, thus allowing different TIBCO ActiveMatrix BPM systems to use their own set of shared resources.
  • Substitution variables can be used to map a shared resource value in a business process - the fields that appear on the Shared Resource section of the Properties view for a Business Studio object within a business process— to a resource available at runtime on the node where the BPM application is deployed. See the use of the substitution variable AddressService_Consumer1 in the How to Call an External Web Service From a Process tutorial for an example of how substitution variables work.
  • Logging appenders define the output targets to which log statements are output. They can be:
    • File  Appends events to a log file.
      • Clear Text  The log file is stored in clear text format.
    • JMS  Appends events to a log service instance, which in turn stores the events to a database.

      See "Appenders" in TIBCO ActiveMatrix BPM - BPM Administration for more information on logging appenders.