Shared Resources
Shared resources are used to define a resource that contains configuration data that can be referenced from multiple processes.
You can define a shared resource and then reference it from multiple activities in the same or different process. For example, you can define a JDBC Connection resource and then use it in any of the JDBC activities in your process to connect to the database.
Shared resources (such as JDBC Connection, HTTP Connection, JMS Connection) are available at design time. At runtime, the referencing activities and event sources have full access to their instances and configuration. Shared resources can be grouped in packages, similar to the way process packages and Java packages are presented in the file system.
When defined in an application module, shared resources are not visible outside the application module. However, when defined in a shared module, they are visible outside the shared module.
For more information about basic concepts like application module, shared module, and shared resource, see General Concepts in the TIBCO BusinessWorks Container Edition Concepts.
Independent Start of a Component
The Independent start of a component feature allows an application to start even if there is component failure (due to shared resource failure) so that the user can use other working components in the application without any issue. This feature mainly targets areas where shared resource creation fails, that results in component initialization failure, which also results in the application to be in an impaired or startFailed state.
When the bw.independent.component.startup=true
property is enabled, it bypasses the shared resource creation failure error and the component initialization failure and starts the application so that you can use the other working components in the application.