Siebel Server Sync Guide > Customizing Siebel Server Sync > Process of Customizing SSSE >

Example of Changing Integration Objects (New Field)

This topic gives one example of changing integration objects as part of customizing SSSE. You may use this feature differently, depending on your business requirements.

In this example, you want to add the new Siebel field ManagerLogin to the Employee domain, so SSSE can synchronize it. To accomplish this, you must change both the Siebel Integration Object and the Intermediate Integration Object for the Employee domain. For more information about Integration Objects, see About SSSE Integration Objects.

NOTE:  This example assumes that the new ManagerLogin field already exists in the appropriate Siebel Business Component, but it does not yet exist in the Siebel Integration Object or the Intermediate Integration Object, and it has not yet been synchronized.

To change Siebel and Intermediate Integration Objects for a new field

1. Log in to Siebel Tools.
2. In the Object Explorer pane, select Integration Object, and complete the following substeps:
   1. In the Integration Objects list editor, select PIMSI Employee.
   2. In the Object Explorer pane, select Integration Component.
   3. In the Integration Component list editor, select Employee.
   4. Scroll to the right until the Inactive field is visible, and clear the Inactive check box.
3. In the Object Explorer pane, select Integration Object, and complete the following substeps:
   1. In the Integration Object list editor, select PIMSI Intermediate Employee.
   2. In the Object Explorer pane, select Integration Component.
   3. In the Integration Component list editor, select Employee.
   4. In the Object Explorer pane, select Integration Component Field.
   5. In the Integration Component Field list, right-click any record, and choose Copy Record.
   6. In the Siebel Tools menus, select View Windows > Properties Window.
   7. In Properties pane, modify property values for the copied record as shown in the following table.

      Field Property	Field Property Value	Comment
      Name	ManagerLogin	Internal name of the field. The Name value must differ from the Parent Name value, or data will not synchronize properly.
      External Name	ManagerLogin	For a Siebel Integration Objects, External Name must match the name of the field as it is specified in the Siebel Business Component. For an Intermediate Integration Object, you can choose any value for External Name.
      XML Tag	ManagerLogin	Enter a value that does not contain any spaces. This value is included in the XML output that SSSE produces.
      XML Sequence	18	Specifies the order in which the field will appear in the Output XML message. Enter a value that is not already present in the field list, such as the number that follows the value used for the last existing field in the sequence. It is recommended that you use the same value for XML Sequence and External Sequence.
      External Sequence	18	Specifies the order in which the field will appear, when Data Mapper is used to map the fields. Enter a value that is not already present in the field list, such as the number that follows the value used for the last existing field in the sequence. It is recommended that you use the same value for XML Sequence and External Sequence.
      Parent Name	Employee	The Integration component that is the parent of the Integration Object that is being modified.

      CAUTION:  For Siebel Integration Objects (but not Intermediate Integration Objects), if an MVG field is not a user key, be sure to set the XML Sequence property value and the External Sequence property value to be greater than the value of a user key MVG field. If you do not specify a greater value, synchronization may not work properly for information that travels from Exchange to the Siebel application.

      A user key MVG field is a field that is specified in the Integration Component User Key object as a user key. For example, for the Integration Object called PIMSI Employee and the Integration Component called Employee_Position, the user key field is Position. If any new MVG field is added to the Employee_Position component, then the XML Sequence and External Sequence property value for the new field should be greater than that of the Position field.

4. Save the record.
5. Recompile the SRF for the project.

   Use the recompiled SRF when you make corresponding changes to Data Maps.