Spring components integrate Spring Beans into the TIBCO ActiveMatrix platform.
A Spring component is very similar to Java component, but its implementation can consist of more than one Java class. The classes are specified in a Spring Bean configuration file. Each Spring Bean corresponds to a Java class. In Spring components, each service, reference, and property is associated with a Bean (as opposed to all being associated with the same Java class in the case of Java components).
TIBCO ActiveMatrix Service Bus Concepts 56 | Service Component Architecture
Glossary
abstract component
A component whose implementation type is unspecified but whose interfaces and connections to services, other components, and references are defined. Abstract components can be used by system architects to specify the relationship of a component to other composite elements while deferring the choice of implementation type.
application
An instance of an application template.
application fragment
A component or binding running on a node.
application template
A root composite and a set of related configuration files including nested composites, WSDL files, substitution variable files, and resource templates.
binding
A transport configuration that specifies how messages are transported from service consumers to providers.
A service can have multiple bindings. A reference can have one binding.
bundle
An OSGi mechanism for grouping Java classes into a modular, sharable unit. In TIBCO Business Studio, a plug-in implements a bundle.
component
A configured implementation that provides a business function as a service and consumes other services.
composite
An assembly of components, services, references, and properties and the wires that encapsulate the connections between these elements.
distributed application archive (DAA)
A package for applications, libraries, and adapter archives. A DAA contains zero or more application templates, custom features, and an optional distribution.
distribution
Specifies a mapping of one or more application fragments to one or more logical nodes.
endpoint
A runtime object that manages each direction of the messages associated with the operation supported by a binding.
enterprise archive (EAR)
A TIBCO ActiveMatrix Adapters deployment package. An EAR file is created in TIBCO Designer and is assembled from one or more adapter archives. The EAR file is uploaded to Administrator when creating an application. During uploading and parsing an EAR file adapter configurations are identified, global variables are collected and an application template containing a TIBCO ActiveMatrix Implementation Type for TIBCO Adapters component is created.
environment
A logical grouping of applications and nodes.
feature
A software package that specifies the plug-ins (bundles) it includes and the features on which it depends.
There are two types of features:
• System, which are defined by the TIBCO ActiveMatrix product.
• Shared library, which contain component implementations and libraries.
governed object
An element at which TIBCO ActiveMatrix can enforce policies. The following elements can be governed objects:
• Composite
• Component
• Component service or reference
• Promoted service or reference
• Binding host
Runtime entity that manages nodes and installed TIBCO ActiveMatrix software.
identity provider
A resource that encapsulates a user identity. The identity may be implemented using usernames and passwords or other credentials.
intent
Describes abstract constraints on the behavior of a component, or on interactions between components. Intents let application designers specify requirements in a high-level, abstract form, independent of the configuration details of the runtime and bindings. Intents guide administrators as they configure bindings, policies, and runtime details.
interface
Defines the contract for services and references.
keystore
A database of keys and certificates. Keystores contain keystore entries, which serve as identities for participants in SSL sessions.
keystore provider
A resource that encapsulates a keystore credential.
log appender
An output destination for a logger.
logging configuration
An object that identifies the level of events to be logged and whether to pass messages to a parent logger.
logical node
A heterogeneous group of application fragments that must be deployed to the same physical node. You cannot distribute fragments to different nodes if they are contained in the same logical node.
message
The basic unit of communication between a requester and a service. An abstract, typed definition of the data required by an operation.
message exchange pattern (MEP)
The sequence of messages in an operation. This sequence includes the order, direction, and cardinality of the normal and fault messages.
node
The runtime environment for application fragments.
operation
The set of messages required to perform a single abstract action. An operation has zero or one request (input) message and zero or one response (output) message, and zero or more fault messages.
policy
A configuration that specifies the precise details that TIBCO ActiveMatrix needs to enforce a constraint declared in an intent. A policy can also be specified without an intent.
policy set
Contains one or more policies. Adding a policy set to a governed object applies its policies at the object. When you add a policy set, you are explicitly requesting that TIBCO ActiveMatrix enforce all its policies for the governed object.
promotion
The process whereby services and references defined by an object are made visible at the level of its container object. The service and references of a component can be promoted to its containing composite and the services and references of an application can be promoted to its containing environment.
property
Data that influences the behavior of an application fragment. Property values can be configured when the fragment is deployed.
reference
Identifies the service consumed by a component or composite.
resource instance
An instance of a resource template.
resource template
TIBCO ActiveMatrix Service Bus Concepts 58 | Glossary
A configuration of the properties required by a resource.
service
A set of operations and the messages required by the operations.
service-oriented architecture (SOA)
A software architecture in which applications are decomposed into discrete, operationally independent services, which can be executed in a highly distributed manner. SOA is based on three principles:
• Modularity - Breaking tasks and services into smaller tasks or services.
• Encapsulation - Clearly defined interfaces that insulate a service's internal workings from outside contact.
• Reuse - Re-assembling services into composite applications that support new business processes.
SOA inherently encompasses a heterogeneous collection of platforms and sources. Enterprise applications may be hosted on Java and .NET platforms, as well as third-party packaged systems and legacy applications.
SOA infrastructure spans these varied application architectures and provides mediation between them.
Service Component Architecture (SCA)
A set of specifications that describe a model for constructing composite applications that conform to a service-oriented architecture.
service virtualization
The messaging configuration specified in an environment that enables message transport between the environment's wired service providers and consumers in the absence of associated bindings.
software repository
A set of folders on the file system that act as a source of software features. The file system folders must be accessible from an Administrator server. The software repository holds metadata about products and product features. Administrator uses the following software repositories:
• Product - A read-only software repository containing the TIBCO products installed by TIBCO installers.
• Administrator - Read-write software repository containing features uploaded into Administrator.
substitution variable
A variable that you can reuse in resource and application configurations. Substitution variables enable late binding of property values to values available in Administrator at deployment time. At design time, instead of explicitly setting property values, they are bound to a substitution variable. Administrators set the substitution variables values to values supported by the resources available on the node on which the resources are installed and applications are deployed.
trust provider
A resource that encapsulates access to a trust store.
trust store
A keystore containing trusted certificates.
wire
A connection between a service and a reference.
Glossary | 59