Business entities compatibility with earlier versions

A new function was introduced to enable integration between TADDM and products that read data from TADDM by using DataApi or directly from TADDM database by using SQL. The examples of such products are IBM Tivoli Business Service Manager (TBSM), IBM SmartCloud Control Desk (SCCD), Tivoli Directory Integrator (TDI). The current Business Application data model relies on CustomCollection interface, which has nothing in common with former Application and ITSystem interfaces. The new function enables integration with other products without introducing any modifications to those systems.

In the future versions of TBSM and SCCD, the Business Application model will be introduced with new features. The aim is to generate previous business entities, which are copies of custom collection instances.

The new function, which provides compatibility with earlier versions, consists of the following features.
Additional step while running BizAppsAgent
The additional step generates business entities (services, application, collection) compatible with earlier versions for each custom collection that is generated by the agent.

To activate this step, a new property was added to the collation.properties file, com.ibm.cdb.serviceinfrastructure.earlier.ver.compatibility. The default value of this property is TRUE for the upgrade scenario and FALSE for the fresh installation scenario.

OSLC support
OSLC agent was modified and is able to register either old business entities or new custom collections. When compatibility flag is set to TRUE, old business entities are registered. Otherwise, custom collections are used to produce a content for Jazz for Service Management (JazzSM).

In the future, a full reload of business entities will be required when integrating product starts to load data using new model objects (custom collections and nodes). Old business applications (applications) and new business applications (custom collections) cannot have the same GUID. To avoid duplicates, before loading new custom collections, users will have to remove old business applications.

Creating functional groups

New business applications, unlike old business applications, do not have functional groups. However, a new tiers functionality was introduced to serve similar purposes. For each unique tier, to ensure compatibility with earlier versions, a functional group with a name corresponding to the tier name is created.

For more information, see Business application tiers.