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 ActiveMatrix® Adapter for the Siebel project created on ActiveMatrix BusinessWorks™ 6. x. A template of the preference file is installed in the tools folder of the plug-in in the following location:

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

A Preference file (JSON format) can be used in the following manner:
  • 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 Siebel project created on ActiveMatrix BusinessWorks 6. x does not just contain Siebel but also other plug-ins that support adapter migration.
  • Key and values are case sensitive in the migrateSchema.json file.

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

"SIEBELSCHEMA": 
{
	"<BW5SchemaElementName>":"/<Relative Path Of Siebel Object Editor>/<BW6 Plugin XSD Name> :<BW6SchemaElementName>",
						 
	"<BW5SchemaElementName>":"/<Relative Path Of Siebel Static Schema>/<BW6 Plugin XSD Name>:<BW6SchemaElementName>"
},

"VARIABLES": 
{
	"<BW5VariableElementName>":"/<Relative Path of Siebel Object Editor>/<BW6 Plugin XSD Name>:<BW6SchemaElementType>"		
}

BW5SchemaElementName is replaced by BW6SchemaElementName inside the BW6 Plugin schema reference if it is available.

Note: Relative Path of Siebel Static Schema is either the path of siebel object editor or the path of static Siebel schemas.
Limitations
  • An XSLT out of Sync error occurs in the migrated ActiveMatrix BusinessWorks™ 6.x project. To resolve this issue, Right-click the input mapping and select Show Check and Repair.
  • Component out of place, error occurs after post migration is performed. To resolve this issue, right-click the input mapping and select Show Check and Repair.
  • When BW5 Adapter has a Siebel service created and its Siebel schema is getting used in any ActiveMatrix BusinessWorks Activity but not in Siebel Activity then the Siebel schema is not migrated until it is used in any Siebel Activity. To solve this issue in ActiveMatrix BusinessWorks 6.x, manually you must create the Siebel schema by fetching the required Siebel Object and its component in the Siebel object editor and mapping it in the migrated Schema.json file. To resolve this issue, right-click the input mapping and select Show Check and Repair.
  • If two different activities are using different Siebel object editors but the schema is the same, in this case as the ActiveMatrix BusinessWorks adapter schema element name is the same for both (the key in JSON file), then all such elements/schemas are replaced.
  • In the BW6 Schema Element Name do not specify the root element like ActivityInput/ActivityOutput. You must specify the ActiveMatrix BusinessWorks 6.x element that has to be replaced in the mappings as there are several different schemas in Siebel.
  • When using the Assign activity with Siebel Schema, after performing post-migration, there will be an error in the .xsd file in the project. Right-click and delete the .xsd file to make the project error-free.
  • Any required new field (which was not present in ActiveMatrix BusinessWorks 5.x and introduced in the ActiveMatrix BusinessWorks 6.x plugin) throws a design-time error after the migration or post-migration process, which you must solve manually.