1. Automation Tools For Testing

Number of employees5,036 (2005)WebsiteSiebel CRM Systems, Inc. Was a company principally engaged in the design, development, marketing, and support of (CRM) applications. The company was founded by and in 1993. At first known mainly for its products, the company expanded into the broader CRM market. By the late 1990s, Siebel Systems was the dominant CRM vendor, peaking at 45% market share in 2002.On September 12, 2005, announced it had agreed to buy Siebel Systems for $5.8 billion.

Siebel is now a brand name owned by Oracle Corporation.The CRM software development environment is known as Siebel Tools and those skilled in such are known as Siebel Consultants. Contents.History Siebel Systems, Inc. Began in sales force automation software, then expanded into and customer service applications, including CRM.

From the time it was founded in 1993, the company grew quickly. Benefiting from the explosive growth of the CRM market in the late 1990s, Siebel Systems was named the fastest growing company in the United States in 1999 by Fortune magazine.Key dates.

1993: Siebel Systems, Inc.

Bookshelf v8.1/8.2: Configuring Third-Party Code Control Configuring Third-Party Code ControlYou can integrate the check in feature in Siebel Tools with a code control system from a third party. You can use any third-party control system that Siebel CRM can start and control from a batch file. Some example third-party control systems include Borland Star Team, ClearCase, CVS Open Source, Microsoft Visual SourceSafe, Serena, and PVCS.If you use third-party code control, then Siebel Tools creates an archive each time you check a project into the server repository. It also checks the project into the code control system. The archive includes all the objects in the project. The code control system can include successive versions of this project. You can use third-party code control only to check in items.

You cannot use it to check out items. For more information, seeTo configure third-party code control. In Siebel Tools, choose the View menu, and then click Options. In the Development Tools Options dialog box, click the Check In/Out tab.

Set the options in the Source Control Integration section.For more information, see. Click OK. Modify the batch file.For more information, see.

Automation Tools For Testing

Using Check In with Third-Party Code ControlAfter you configure Siebel Tools to use third-party code control, you can use Siebel Tools to check in projects just like you typically do. In this example, assume that Project A and Project B are currently checked out. You must check in these projects to the server repository and the code control system. Version 5 is the latest version of the ProjectA.sif file in the code control system. Version 6 is the latest version of the ProjectB.sif file.To use check in with third-party code control. In Siebel Tools, choose the Tools Menu, and then click Check In.Siebel Tools does the following:. Checks Project A and Project B into the server repository.

Starts the srcctrl.bat file from the following directory:SIEBELTOOLSROOT BINThis batch file does the following:. Checks out ProjectA.sif and ProjectB.sif.

DescriptionPATHIdentifies the directory where you install the code control software. You must modify this parameter so that it identifies this directory.SOFTWAREName of the command-line utility that the code control system uses. Running Simultaneous Siebel Tools Sessions After You Modify the ODBC Data SourceIf you exit Siebel Tools after you modify the ODBC data source, then Siebel Tools writes these modifications to Siebel Preference Files (SPF) in the following directory:SIEBELTOOLSROOT BINIt caches these preferences. The next time you Log in to Siebel Tools, it does not read the ODBC settings in the tools.cfg file, and you cannot use a single user Id to run simultaneous Siebel Tools sessions.

You can open only one local data source at a time. For more information, see and.Using Siebel ToolsCopyright © 2013, Oracle and/or its affiliates. All rights reserved.