Shared Resources
Shared resources contain connection details for physical resources. Shared resources provide a way to use an identifier to reference the configuration of a resource. Using the identifier, multiple governing objects that require similar resource configuration can refer to an already configured resource without having to configure the resource multiple times.
When using shared resources you do not need to provide connection details in services, component implementations, and references. Instead, specify a property of the type of required physical resource in the service, component, or reference. When you configure the application for deployment, map the property to a resource instance available on the node on which the service, component, or reference is deployed.
With TIBCO ActiveMatrix Policy Director Governance, you can manage the configuration of resources such as LDAP, Keystores, Identity Providers, and HTTP connections separately from your policy configurations and reuse them in different policy configurations. For example, you could use a single Keystore resource in the WSS Provider policy and Credential Mapping policy.
Separating resources from polices offer many benefits. A security architect could define Identity Providers, Trust Providers, and WSS Authentication mechanisms to suit the interaction agreements. This can be done with partners independent of the application topologies and policy administration. The Administrator can manage applications, policies, and monitor systems.