Migration from 4.x to 5.1

Manual Change

When migrating 4.x projects, edit the CDD file and set the cluster level property be.engine.cluster.as.discover.url with a valid value (for example, tibpgm://9995/) preferably inside a property group "tibas".

Automatic Changes

The migration utility automatically does the following:

Migrates core Coherence functions to product neutral ones

 A set of core Coherence functions has been renamed so that these functions can be used with either the Coherence or the TIBCO BusinessEvents DataGrid cache provider. Not all Coherence functions are migrated. See Migrating from Coherence to TIBCO BusinessEvents DataGrid Cache Provider for important information.

Migrates the channel driver type  

Driver type is migrated from the 4.0 format to the current format.

Migrates HTTP channel settings

 HTTP channel tuning settings are now maintained in the channel resource instead of the processing unit (PU) area of the CDD. During the migration process, you specify the CDD and within it the PU whose settings you want to migrate. Settings from the selected PU are applied to all HTTP channels.

Migrates CDD file namespaces

 Namespace is changed to the following: http://tibco.com/businessevents/configuration/5.1.

Migrates entity metadata properties to CDD domain object override settings

 In earlier versions, entity-specific configuration for cache and backing store was done using metadata properties (also known as extended properties). It is now done in the CDD only. The migration utility moves all relevant metadata property settings to the equivalent settings in the CDD Domain Objects Overrides area. An override is added for each entity type. You can later remove unnecessary entries as needed. (There is no change to configuration for metadata properties used by the TIBCO BusinessEvents Data Modeling add-on product.)

Migrates localStorage Property to isSeeder property (partial migration)

  The property  tangosol.coherence.distributed.localstorage is migrated to the cache-provider-neutral property be.engine.cluster.isSeeder. However, a change in design makes this property redundant. Cache storage is now set at the processing unit level, using a checkbox labeled Enable Cache Storage. It is not possible to set this checkbox at migration time. Note that without further action, if the isSeeder property is set higher in the order of precedence than the processing unit, then the isSeeder property is used at runtime. However, if the isSeeder property is set lower in the order of precedence than the processing unit, then the checkbox value is used. To complete migration, remove the isSeeder property and instead use the processing unit setting Enable Cache Storage in the project CDD file. Note that enabling cache storage on non-cache agents is not recommended for production. It can be useful for testing and demonstration purposes.

Site Topology, TIBCO BusinessEvents Version Field

 The value of the TIBCO BusinessEvents Version field in Cluster Settings and in Host Settings is updated to the current version.

Adds CDD properties for TIBCO BusinessEvents Monitoring and Management authentication

, which is a new feature in 5.0. The properties are added in these locations:

• BE_HOME/mm/project/emonitor > MM.cdd > mm-class agent class > properties > mm/auth property group
• ToBeMonitored_Project > project.cdd > Cluster properties > auth property group.

The properties are added to all project CDDs if a project has more than one. The following properties are added, with the default values as shown:

be.mm.auth.type=file
be.mm.auth.file.location=BE_HOME/mm/config/users.pwd
java.security.auth.login.config=BE_HOME/mm/config/jaas-config.config