On this page:

Target audience:

CAST Administrators

Summary: this section describes how to manage the analysis of your Siebel applications in the CAST Management Studio, following delivery of the source code.

The analysis process for your Siebel applications is designed to work with the two analysis services that were created earlier (see Siebel 5.0 - Installation):

Please note that the following document refers to SQL scripts delivered in text files with the extension. These files are located here and are delivered for both Oracle and CAST Storage Service implementations:

ExtensionLocation
Archive (5.0.1)
  • ToBeUsedForConfigurationInCMS/CSS
  • ToBeUsedForConfigurationInCMS/Oracle
Nuget (5.0.1 - 5.0.3)
  • %PROGRAMDATA%\CAST\CAST\Extensions\com.castsoftware.siebel.<version>\CSS
  • %PROGRAMDATA%\CAST\CAST\Extensions\com.castsoftware.siebel.<version>\Oracle
Nuget (5.0.4)
  • %PROGRAMDATA%\CAST\CAST\Extensions\com.castsoftware.siebel.<version>\InstallScripts\CastStorageService\DIAG\CMS
  • %PROGRAMDATA%\CAST\CAST\Extensions\com.castsoftware.siebel.<version>\InstallScripts\Oracle\DIAG\CMS

Analysis setup for Project

Configure CAST Management Studio preferences

Once the CAST Management Studio has launched, open Windows/Preferences and define the Cast General settings:

Import the Assessment Model

Analysis setup for Vanilla

Manage and run the analysis for Vanilla

Accept delivery and use it as current version

Select the Version and then click the Manage the delivery… option to open the CAST DMT. Check the packaging is correct:

Note that this procedure can take a long time as it deploys the source code. If you want to increase the speed, you should deactivate any real-time anti-virus scanning that may be configured on the Deployment folder.

Configure the Content Enrichment

In the Application editor, click the Content Enrichment tab.

Siebel Content Enrichment

Siebel Application Content

Run analysis

Post analysis checks

Manage and run the analysis for Project

Accept delivery and use it as current version

Select the Version and then click the Manage the delivery… option to open the CAST DMT. Check the packaging is correct

Note that this procedure can take a long time as it deploys the source code. If you want to increase the speed, you should deactivate any real-time anti-virus scanning that may be configured on the Deployment folder.

Configure the Assessment Model

Note that the Search may not function correctly - if this is the case, please quit the CAST Management Studio and then re-run it (ensuring that you connect to SIEBEL5_MNGT (i.e. the Project)


Multiple values, char: as they are related to naming convention, they must be adapted to the project

MetricID
(external ID)

Rule name

Parameter name

Default value

Project value

1520380

Siebel: Applet's name should contain the type

Siebel: Suffix Applet - Association List

Assoc Applet

 

 

 

Siebel: Suffix Applet – Detail

Detail Applet or Popup Applet

 

 

 

Siebel: Suffix Applet – MVG

Mvg Applet

MVG Applet

 

 

Siebel: Suffix Applet - Pick List

PickList Applet

Pick Applet

 

 

Siebel: Suffix Applet - Playbar

Playbar Applet

 

 

 

Siebel: Suffix Applet - Standard

Standard Applet

 

 

 

Siebel: Suffix Applet - Task

Task Applet

Form Applet

1521700

Siebel: Table's name should have a designated prefix like XX_LABEL

Siebel: Prefix Table

CX_

 

1521702

Siebel: Business Component's name should begin with Company prefix

Siebel: Prefix Business Component

AM_

ACME_

1521704

Siebel: Applet's name should begin with Company prefix

Siebel: Prefix Applet

AM_

ACME_

1521706

Siebel: View's name should begin with Company prefix

Siebel: Prefix View

AM_

ACME_

1521708

Siebel: Screen's name should begin with Company prefix

Siebel: Prefix Screen

AM_

ACME_

1521710

Siebel: Business Object's name should begin with Company prefix

Siebel: Prefix Business Object

AM_

ACME_

1521712

Siebel: Business Service's name should begin with Company prefix

Siebel: Prefix Business Service

AM_

ACME_


Single value, numerical: As a first approach, you can stick to the default values

MetricID
(external ID)

Rule name

Parameter name

Default value

Project Value

1520180

Siebel eScript: Avoid Functions with High Cyclomatic Complexity

Siebel: Max CC

15

 

1520442

Siebel eScript: Avoid Functions with a low comment/code ratio

Siebel: Min comment ratio

5

 

1520494

Siebel eScript: Avoid complex PreGetFieldValue Functions

Siebel: Max LoC for PreGetFieldValue

50

 

1520540

Siebel: Avoid too many MVG on list applet

Siebel: Max MVG Applet

5

 

1520726

Siebel eScript: Avoid putting all code in the Applet_PreInvokeMethod event

Siebel: Max LoC for Service_PreInvokeMethod

20

 

1520728

Siebel eScript: Avoid putting all code in the Service_PreInvokeMethod event

Siebel: Max LoC for Service_PreInvokeMethod

20

 

1520730

Siebel eScript: Prefer SWITCH over nested IF-THEN-ELSE in Functions

Siebel: Max Nested IF

5

 

1520734

Siebel eScript: Avoid using multiple conditions in IF constructions in Functions

Siebel: Max Condition in IF

5

 

1520860

Siebel: Avoid Business Objects referencing too many Business Components

Siebel: Max Buscomp

50

 

1520862

Siebel: Avoid Business Components referencing more than X tables

Siebel: Max Table

40

 

1520864

SiebelReview: Too Many Applets on a View

Siebel: Max Applet

10

 

1520866

SiebelReview: Excessive Number of List Columns in a List Applet

Siebel: Max number of columns

50

 

1520868

Siebel eScript: Avoid Functions with more than X variables

Siebel: Max Variables

15

 

1520880

Siebel eScript: Avoid Functions with more than X Lines of Code

Siebel: Max LoC

30

 

Configure the Content Enrichment

In the Application editor, click the Content Enrichment tab.

Siebel Content Enrichment

Siebel Vanilla Import

Siebel Discrimination with Vanilla

If VANILLA_SCHEMA (in our example, SIEBEL5_V_LOCAL) has been reinstalled in server manager ( to update Siebel extension or to manage any other extension ...) just before this step, be aware that all custom tables are recreated, all data will be overwritten and lost. So you have to rerun the SQL Tool after analysis (Content Enrichment) on  VANILLA_SCHEMA. It will populate again the custom tables used for the discrimination step on PROJECT_SCHEMA

 

Siebel Application Content

Modules

Generate a snapshot

Post snapshot checks