Viewing and Resolving Conflicts after Siebel Archive File Imports in Web Tools
After the completion of RepositoryUpgrade or you have imported a Siebel Archive File (SIF) through the command line Interface (only siebdevcli command is supported), you can view the imported objects and their properties. To do this you use the SIF Attribute Differences report in Web Tools.
Using the SIF Attribute Differences Report
Here's how you can view attribute differences and resolve conflicts:
-
Open the editable Developer Workspace into which you imported the attribute differences.
Note: If you have run RepositoryUpgrade, locate the parent Integration Workspace you used to run the RepositoryUpgrade utility. Under that integration workspace will be an Integration Workspace created by the RepositoryUpgrade utility named int_siebel_updateN (where N is a sequential number). Underneath int_siebel_updateN is the Developer Workspace to open. -
Go to Application Menu > Archive > SIF Attribute Differences (Keep the developer workspace open).
-
When the report opens you will see a tree structure listing the changed object types such as Applet, Business Component, Workflow Process and so on.
-
Expand each object type to find the objects that have changed. Each object type can have multiple changed objects.
-
When you select a particular object, the Account Business Component for example, if any of the attributes at the top-level object have changed, you will see a list in the Attribute Differences Applet on the right.
-
For each attribute that has changed you will see the following:
-
Attribute Name: Name of the attribute that has been changed such as Post Default Value for a Business Component Field.
-
Pre-existing Value: Value that was in your Repository before you imported the SIF file or ran RepositoryUpgrade.
-
Import Value: Value that has been imported from RepositoryUpgrade or a SIF import.
-
Keep Pre-existing Value checkbox: Select this to keep the value that was in your Repository before the import. Leave it unchecked to allow the imported value to overwrite the existing value.
-
-
Expand each object type and its child object types and resolve each changed attribute by either selecting the check box to keep the Pre-existing Value or leaving it unchecked to allow the imported value to overwrite the existing value.
-
Your changes are automatically saved when you navigate to a different row, or you can manually save each record that you change.
-
If you need to resolve these conflicts in multiple sessions, you can return to this report later.
-
Once you have made all the changes for each attribute, click Apply Changes to save all your decisions in the current Developer Workspace.
-
Once you click Apply Changes the report closes, and you are returned to the View you were on in Web Tools.
Note: You can still go back in and make multiple changes to the report. Nothing is final until you version the Developer Workspace. Once you have done that, all decisions in that Workspace are final. -
Apply all the decisions that you have made to the Workspace using the Apply Changes button, you are ready to deliver the Workspace.
-
Deliver the Workspace to its parent
int_siebel_updateN
Workspace. -
You are now ready to deliver
int_siebel_updateN
to its parent workspace.