Working with Preference File (JSON) for Post-migration

When you want to update the schema and use the feature of preferences, then a migrateSchema.json file would need to be created in the root folder of TIBCO ActiveMatrix BusinessWorks™ 6.x project.

A template of the preference file would be installed in the tools folder of the plug-in in the following location:

$TIBCO_HOME/bw/palettes/tux/version/tools/migrateSchema.json_template

A Preference file (JSON format) can be used in the following manner:
  • To override configuration defined in the ActiveMatrix® Adapter for Tuxedo project created on ActiveMatrix BusinessWorks 5.x and the adapter services carried over to the plug-in.
  • To provide the configuration available in the plug-in but not available in ActiveMatrix BusinessWorks 5.x project.
Note:
  • The JSON preference file template should be used for reference only and should not be modified or used as it is. The preference file should be edited with the necessary properties and their corresponding values.
  • The file created under the root folder of the ActiveMatrix® Adapter for Tuxedo project created on ActiveMatrix BusinessWorks 6.x do not just contain Tuxedo but also other plug-ins that supports adapter migration.

The migrateSchema.json configuration has TUXSCHEMA key which has 3 tuples separated by :. The first tuple indicates the TIBCO ActiveMatrix BusinessWorks™ 5.x adapter field name, second tuple indicates schema reference of migrated TIBCO ActiveMatrix BusinessWorks™ 6.x project and third tuple indicates the replaced value inside schema reference. For example: 

"TUXSCHEMA":
	{
		"EMPID__33554532":"Output/EmployeeDetailsOutput:EMPID",
		"RequestResponseServiceReply":"Output/EmployeeDetailsOutput:RfcResponse_EmployeeDetailsOutput"
	}

EMPID__33554532 is replaced by EMPID inside the Output/EmployeeDetailsOutput schema reference, if it is available.

The RequestResponseServiceReply schema reference is replaced by RfcResponse_EmployeeDetailsOutput inside Output/EmployeeDetailsOutput.