Bookshelf Home | Contents | Index | PDF     

Using Siebel Tools > Managing Repositories > Managing Modifications That Developers Make to Repositories >

Using Object Tags to Manage Modifications That Multiple Developers Make

This topic describes how to use object tags to manage the modifications that multiple developers make. It includes the following information:

Administering Object Tags

This topic describes how to administer object tags.

To administer object tags

  1. Consult with your team members to identify the tags that your deployment requires.

    For example, ABC team - developer 1, ABC team - developer 2, and so forth.

  2. Log in to the Siebel client with administrator privileges.
  3. Enable object tagging by completing the following steps:
    1. Navigate to the Administration - Application screen, and then the System Preferences view.
    2. Query the Name field for Enable Object Tagging.
    3. Set the value in the System Preference Value field to TRUE.
  4. Create the tags by completing the following steps:
    1. Navigate to the Administration - Tag screen.

      The Tags list displays all the tags that the repository contains.

    2. Create a record for one of the tags that you identified in Step 1:
    3. Add information in the Name and Description field that describes that tag.
    4. Navigate to the Users view, and add developers to the tag.
    5. Repeat Step b for each tag that your deployment requires.
  5. Administer an existing tag by completing the following steps:
    1. Choose the tag that you want to administer in the Tags list.
    2. Navigate to the All Objects view to identify the objects that are associated with a tag.

      The All Objects list displays information about all the objects that developers have created, modified, or deleted. For example, if you choose the Siebel Sales tag in the Tags list, then it displays objects only for developers who use the Siebel Sales tag when they log in to Siebel Tools. For a description of the format that this list uses in the Object Path field, see Example of an Object List File.

    3. Navigate to the Conflicts Only view to review conflicts.

      The Conflicts Only list displays all the objects that are in conflict and details for each of these objects. The grandchild list displays the details of other tags that are associated with the conflict.

Enabling Object Tagging in Siebel Tools

This topic describes how to enable object tagging.

To enable object tagging in Siebel Tools

  1. Make sure you use a version of Siebel Tools that supports object tagging.
  2. Set up the shortcut that you use to start Siebel Tools to start in iPack mode:
    1. Right-click the shortcut that you use to open Siebel Tools, and then click Properties.
    2. In the Properties dialog box, click the Shortcut tab.
    3. In the Target field, add the iPackMode switch.

      For example:

    C:\Siebel\8.1\Tools_2\BIN\siebdev.exe /c "C:\Siebel\8.1\Tools_2\bin\enu\tools.cfg" /u SADMIN /p SADMIN /d Sample /iPackMode

    Bold font indicates the switch that you add.

  3. Log in to Siebel Tools.
  4. Click the Screens menu, System Administration, and then click System Preferences.
  5. In the System Preferences list, create a new record using the values from the following table.
    Property
    Value

    System Preference Name

    Enable Object Tagging

    System Preference Value

    TRUE

    To disable object tagging, you can set the System Preference Value to FALSE.

  6. Log out of Siebel Tools.

Tagging Objects

This topic describes how to tag objects.

To tag objects

  1. Make sure you enable and administer object tagging.

    If you enable object tagging, then you must choose a tag when you log in to Siebel Tools or when you use the command-line interface. For more information, see Administering Object Tags and Enabling Object Tagging in Siebel Tools.

  2. Log in to Siebel Tools.

    If you associate:

    • More than one tag with a developer, then Siebel Tools displays the Select a Development Tag Name dialog box during the login, and allows you to pick a tag.
    • Only one tag with a developer, then Siebel Tools automatically chooses this tag during the login.

      You associate developers to tags in Step b.

      After you finish the login, Siebel Tools automatically tags objects if you do any of the following work:

    • Create or modify an object
    • Import an SIF file
    • Check in or check out
    • Do a manual update

      To use a different tag after you log in, you must log out of Siebel Tools and then choose another tag when you log back in to Siebel Tools.

      To identify the tag that you are currently using, do one of the following:

    • View the tag name in the Title bar.
    • Click the View menu, click Options, click the General tag, and then view the value in the Development Tag Name window.

Tagging Objects That You Do Not Modify

Touch is a feature in Siebel Tools that allows you to tag an object that Siebel Tools has not tagged as a result of you importing an SIF file, checking in or checking out an object without changing it, or doing a manual update. It uses this tag information to identify the objects that it extracts from an SDF file during a repository merge. If you touch an object, then you cannot remove the tag that Touch adds.

Siebel Tools automatically tags the objects that it imports or checks in. If Siebel Tools requires an object during an SDF export, and if this object is not tagged, then you can touch the object to make it available to the export. For information about how to export the objects that a developer tags, see Exporting Only Modified Objects to an Archive. For more information about SDF files, see How Siebel Tools Minimizes Processed Data During Exports and Imports.

To tag objects that you do not modify

  1. Make sure you enable object tagging.

    For more information, see Enabling Object Tagging in Siebel Tools.

  2. In the Object List Editor, locate the object that you want to tag.
  3. Check out the object.

    For more information, see Checking Out Objects from the Server Repository.

  4. Right-click the object that you located in Step 2, and then click Touch Object.
  5. Check in the object.

    For more information, see Checking In Projects or Objects to the Server Repository.

    If the object is not already tagged, Siebel Tools adds an entry in the TagObject table. If the object is already tagged, Siebel Tools updates the Last Updated date in the TagObject table.

    Siebel Tools displays the following message:

    The Object is Touched.

Using a Batch Operation to Tag Objects That You Do Not Modify

This topic describes how to tag objects that you do not modify in batch.

To use a batch operation to tag objects that you do not modify

  1. Create an object list file.

    For more information, Example of an Object List File.

  2. Open a command-line interface in the following folder:

    SIEBEL_TOOLS_ROOT\bin

  3. Enter the following command:

    siebdev /c tools.cfg /l language_code /u user /p password /d database /iPackMode /t "tag_name" /BatchTouchObj object_list_file_name log_file_name

    where:

    • language_code identifies the language code (for example, enu).
    • user identifies the Siebel Tools user.
    • password identifies the password that you use to log in to Siebel Tools.
    • database identifies the database where the object resides.
    • tag_name identifies the name of the tag. This is the same name that you typically click in the Tag Name field in the log-in dialog box that you use to open Siebel Tools.
    • object_list_file_name identifies the full path to and the name of a text file that includes a list of the objects that Siebel Tools must tag. For more information, Example of an Object List File.
    • log_file_name identifies the file that Siebel Tools uses to store the log entries that it creates during the batch operation.

      For example:

    siebdev.exe /c tools.cfg /d ServerDataSrc /u sadmin /p sadmin /iPackMode /t "Siebel Mobile" /BatchTouchObj C:\Touch\TouchObjList.txt C:\Touch\touchobj.log

Example of an Object List File

The Object List file is a text file that includes a list of the objects that Siebel Tools must tag. You can use any file name that meets Windows file name requirements. You can locate this file anywhere on the computer where Siebel Tools resides. The Object List file uses the following format:

object hierarchy,object type
.
.
.

object hierarchy,object type

where:

  • object hierarchy identifies the full object hierarchy of the object that Siebel Tools must tag.
  • object type identifies the type of object that Siebel Tools must tag.
  • , (a comma) separates the object hierarchy from the object type. You must not include a space before or after the comma.

The file must not include any empty lines.

For example, you use the following format to tag the control user property of a control in an applet:

applet_name||control_name||control_user_property_name,Control User Prop

where:

  • Two vertical bars (||) separate two different levels in the object hierarchy.

For example, the following code specifies the control user property named Url of the CancelQuery control in the ABO Bulk Request Component Product Pick Applet:

ABO Bulk Request Component Product Pick Applet||CancelQuery||Url,Control User Prop

If you specify an object in the TouchObjList.txt file, and if this object does not exist in the SRF, then Siebel Tools creates an error message in the log file.

Examples of Specifying Objects That Do Not Include the Name Property

You use the Name property to specify most objects. If an object does not include a Name property, then you can use the next significant property. For example, you use the following Field property for a pick map:

business_component_name||field_name||pick_map_field_property,Pick Map

The following code specifies the Account Status pick map of the Account Status field in the Account business component:

Account||Account Status||Account Status,Pick Map

For another example, you use the following Table property for a join:

business_component_name||table,Join

The following code specifies the S_CONTACT table of a join in the Account business component:

Account||S_CONTACT,Join

Tagging Objects When Using Siebel Remote

This topic describes how to configure your environment so that you can use object tagging with Siebel Remote. Siebel Tools does not synchronize any modifications that you make when you use Siebel Remote. It communicates only with the repository on the Siebel Server through project Check Out, project Check In, or a Get. You do not use Siebel Tools to synchronize the modifications that you make through object tagging in a Siebel Remote client. Instead, you must use the synchronization features that Siebel Remote provides. For more information, see Checking Out and Checking In Projects and Objects and Siebel Remote and Replication Manager Administration Guide.

To tag objects when using Siebel Remote

  1. Make sure every developer who uses the Siebel Remote client uses the MOBILE CLIENT - STANDARD routing model to synchronize client changes with the server database.

    Developers must not use the MOBILE CLIENT - EXTRACT ONLY routing model because it only extracts the local database. It does not synchronize the local database. For more information about how to use these routing models and Siebel Remote, Siebel Remote and Replication Manager Administration Guide.

  2. Make sure the tools.cfg configuration file and the Local ODBC data source that the Siebel Web Client uses each reference the same database file, such as sse_data.dbf. For more information about configuring this file and data source, see Specifying the Data Source That Siebel Tools Uses.
  3. Make sure each developer synchronizes any modifications that the developer makes through object tagging with the Siebel Server, and that each developer periodically synchronizes their local database with the Siebel Server so that their client includes the object tagging modifications that other developers make.
      
Using Siebel Tools Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.