The analysis process for your Siebel applications is designed to work with the two analysis service schemas that were created earlier (see Siebel 5.2 - Installation) - note that the names of the schemas are just examples and they can be called anything:

• SIEBEL5_LOCAL: Analysis Service that will store the analysis results for the Project repository
• SIEBEL5_V_LOCAL: Analysis Service that will store the analysis results for the Vanilla repository

Vanilla: Analysis setup and configuration

CAST Management Studio connection

Run the CAST Management Studio and then validate and choose the connection profile for the SIEBEL5_V_MNGT Management Service schema (i.e. for the Vanilla repository). Click Next to start the setup wizard

Enter the CAST License Key and click Next:

Configure the folders (note that the required folders have changed in CAST AIP ≥ 8.3.x):

Click Finish to launch the CAST Management Studio.

Configure CAST Management Studio preferences

Once the CAST Management Studio has launched, open Windows/Preferences:

Import the Assessment Model - required when using CAST AIP 8.2.x ONLY

Open the Dashboard Service editor for the Dashboard Service (SIEBEL5_V_CENTRAL) that is associated to the Management Service you are currently connected to. Click the Import Assessment Model option - the Assessment Model will then be displayed in the CAST Management Studio in the Assessment Models view.

Configure the Assessment Model

Open the Assessment Model and check that the parameter settings for the Siebel rules are adapted to your project. To do so, go to the Contextual Parameters tab and search for names that start with "Siebel:"

Click to enlarge

To check or modify a parameter, edit the parameter - this will open the parameter in an editor window. For example, for the naming conventions, edit the parameters "Siebel: Prefix XXX":

Click to enlarge

Check the following tables and modify each parameter to the value defined in the Project value column.

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

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

Manage the Application, accept the delivery and set as current version

In the CAST Management Studio, Application view, click Manage an Application registered in AIC Portal…. The wizard displays all available applications. Select the "Vanilla" application:

Assuming the packages have already been delivered as explained in Siebel 5.2 - Application onboarding, the Application editor will show the delivered Version in the Delivery tab:

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

• The Content state of the package should be showing Packaging successful
• In the Package content tab, you should see one project named Vanilla for the Siebel Extractor Project type:

Quit the CAST Delivery Manager Tool. Back in the CAST Management Studio, select the Version and click Accept delivery and use it as current version. You should use the default values in the wizard that is displayed.

Configure Modules

In the Application editor, click the Modules tab. Ensure the option to generate a Full Content module is ticked (this should be the case already):

You are now ready to generate a snapshot, see below.

Vanilla: Generate a snapshot and check results

Generate a snapshot

Generate a snapshot for the Vanilla Application - ensure this includes an analysis:

Post snapshot checks

Check log files

You should ensure that no error nor warning messages are reported and that any unusual message recorded in the log file should be reported to CAST Support. When using the GUI, navigate to each analysis execution item and then click the log link: 

Analysis warning messages: end of comment '*/' not found

During the analysis, you may see warnings in the analysis log referencing certain scripts when the script is not syntactically valid. Typically, this has been seen in scripts related to the Vanilla standard object "CSSSWEFrameWebCallScriptPlayer". The impact on results is very low since the analyzer will just ignore the content of these invalid scripts. Potential warning messages:

• end of comment '*/' not found

Check the results in the CAST dashboards

Benchmarking feature

In particular, you should use the Benchmarking feature in the legacy CAST Engineering Dashboard - CED to help perform an inventory check. Expand the table at the bottom, below the bar chart, and look at the main Siebel object types: we expect 100's or 1000's of added and modified Applets, Business Components, Business Services etc.

• If one of the counts is 0, then it is a failure. The issue is most likely located in the discrimination, the Siebel Vanilla Import task, or the extraction itself, as such check the processing of these tasks.
• If both counts are equal, then it is a failure. The issue is most likely located in definition of modules, as such check the explicit lists code.
• If Added is 100% of the Project AU content (i.e. 18,000 Applets etc.) and Modified is empty, then the issue is most likely located in the discrimination, the Siebel Vanilla Import task, or the extraction itself. Therefore, check the processing of these tasks. Check content of table siebel_objects_v (in the Project's analysis schema).

Measure based rules

Using the Investigation View in the legacy CAST Engineering Dashboard - CED, look for invasive and extension customization ratio. Expected range of values for the 7 invasive measure-based rules, and 7 extensive measure-based rules is 0.1% to 25% or more. For now, this inspection is manual. Take this opportunity to fill the Excel report provided in the reporting kit, it will allow the consumers to have access to the measure in one single instant.

An abnormally high invasive customization ratio is usually a sign that the Vanilla and the Project are not in sync (the difference is due to a Siebel version difference or one of more patches) as opposed to actual customization made by the development team. The development team will team you what value is expected and what value is unexpected.

Quality Rules check

All Siebel applications will have critical and non-critical violations. This is inherent to this development environment. So even with low customization ratios, the number of critical and non-critical violations will be 100s or 1000s.

Project: Analysis setup and configuration

CAST Management Studio connection

Run the CAST Management Studio and then validate and choose the connection profile for the SIEBEL5_MNGT Management Service schema (i.e. for the Project repository). Click Next to start the setup wizard

Enter the CAST License Key and click Next:

Configure the folders (note that the required folders have changed in CAST AIP ≥ 8.3.x). You should use the SAME FOLDERS as defined when you setup the analysis for Vanilla:

Configure CAST Management Studio preferences

Once the CAST Management Studio has launched, open Windows/Preferences:

Import the Assessment Model - required when using CAST AIP 8.2.x ONLY

Open the Dashboard Service editor for the Dashboard Service (SIEBEL5_CENTRAL) that is associated to the Management Service you are currently connected to. Click the Import Assessment Model option - the Assessment Model will then be displayed in the CAST Management Studio in the Assessment Models view.

Configure the Assessment Model

Open the Assessment Model and check that the parameter settings for the Siebel rules are adapted to your project. To do so, go to the Contextual Parameters tab and search for names that start with "Siebel:"

Click to enlarge

To check or modify a parameter, edit the parameter - this will open the parameter in an editor window. For example, for the naming conventions, edit the parameters "Siebel: Prefix XXX":

Click to enlarge

Check the following tables and modify each parameter to the value defined in the Project value column.

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

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

Manage the Application, accept the delivery and set as current version

In the CAST Management Studio, Application view, click Manage an Application registered in AIC Portal…. The wizard displays all available applications. Select the "Project" application:

Assuming the packages have already been delivered as explained in Siebel 5.2 - Application onboarding, the Application editor will show the delivered Version in the Delivery tab:

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

• The Content state of the package should be showing Packaging successful
• In the Package content tab, you should see one project named Vanilla for the Siebel Extractor Project type:

Quit the CAST Delivery Manager Tool. Back in the CAST Management Studio, select the Version and click Accept delivery and use it as current version. You should use the default values in the wizard that is displayed.

Configure Modules

Define Module Strategy

In the Application editor, click the Modules tab. Untick all options under Generate one module per:

Create empty User Defined Modules

Create the following empty User Defined Modules:

The configuration described above will give you something similar to the list of User Defined Modules shown below:

Edit the modules

For EACH of the empty User Defined Modules you have just created, you must open and edit each one as follows:

Delete the default Object Filter (called My Object Filter) from the Filters tab:

Activate the option Build module content using an explicit list of objects in the Explicit content tab - this will populate the SQL Query section with a default query template:

Delete the default SQL query template in the Explicit content tab:

Copy in the appropriate SQL query provided in the template TXT file for EACH empty User Defined Module. Template text files can be found in:

%PROGRAMDATA%\CAST\CAST\Extensions\com.castsoftware.siebel.<version>\CMS_ConfigScripts\CastStorageService

Project_Module_REPOSITORY_ADDED.txt
Project_Module_REPOSITORY_MODIFIED.txt
Project_Module_SiebelApp_ADDED.txt
Project_Module_SiebelApp_MODIFIED.txt

for example:

Use the following templates:

select * from §SIEBEL_MODULE_ADDED('$(ModuleName)','Siebel Power Communication')
/

Configure a platform variable

You now need to configure a new platform variable that defines the name of the CAST Analysis Service schema installed for the Vanilla. In our example this is "SIEBEL5_V_LOCAL":

In the Technologies view, double click the Common entry to open the Common editor. In the Platform tab, add a new variable called SIEBEL_VANILLA_SCHEMA with a value equal to the name of the CAST Analysis Service schema installed for the Vanilla:

Click to enlarge

Project: Generate a snapshot and check results

Generate a snapshot

Generate a snapshot for the Project Application - ensure this includes an analysis:

Post snapshot checks

Check log files

You should ensure that no error nor warning messages are reported and that any unusual message recorded in the log file should be reported to CAST Support. When using the GUI, navigate to each analysis execution item and then click the log link: 

Check the results in the CAST dashboards

Benchmarking feature

In particular, you should use the Benchmarking feature in the legacy CAST Engineering Dashboard - CED to help perform an inventory check. Expand the table at the bottom, below the bar chart, and look at the main Siebel object types: we expect 100's or 1000's of added and modified Applets, Business Components, Business Services etc.

• If one of the counts is 0, then it is a failure. The issue is most likely located in the discrimination, the Siebel Vanilla Import task, or the extraction itself, as such check the processing of these tasks.
• If both counts are equal, then it is a failure. The issue is most likely located in definition of modules, as such check the explicit lists code.
• If Added is 100% of the Project AU content (i.e. 18,000 Applets etc.) and Modified is empty, then the issue is most likely located in the discrimination, the Siebel Vanilla Import task, or the extraction itself. Therefore, check the processing of these tasks. Check content of table siebel_objects_v (in the Project's analysis schema).

Measure based rules

Using the Investigation View in the legacy CAST Engineering Dashboard - CED, look for invasive and extension customization ratio. Expected range of values for the 7 invasive measure-based rules, and 7 extensive measure-based rules is 0.1% to 25% or more. For now, this inspection is manual. Take this opportunity to fill the Excel report provided in the reporting kit, it will allow the consumers to have access to the measure in one single instant.

An abnormally high invasive customization ratio is usually a sign that the Vanilla and the Project are not in sync (the difference is due to a Siebel version difference or one of more patches) as opposed to actual customization made by the development team. The development team will team you what value is expected and what value is unexpected.

Quality Rules check

All Siebel applications will have critical and non-critical violations. This is inherent to this development environment. So even with low customization ratios, the number of critical and non-critical violations will be 100s or 1000s.