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

• PSOFT5_V_LOCAL: Analysis Service that will store the analysis results for the Vanilla repository
• PSOFT5_LOCAL: Analysis Service that will store the analysis results for the Project repository

Analysis setup for Project

• Run the CAST Management Studio
• Validate and choose the connection profile for PSOFT5_MNGT (i.e. the Project)
  
• Click Next to start the setup wizard

• Enter the CAST License Key:

• Configure the two folders for the delivery and the deployment of the source code. The "Source Delivery" folder must be the exact same folder as the folder configured during the setup of the CAST AIC Portal:

• Click Finish to launch the CAST Management Studio.

Configure CAST Management Studio preferences

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

• Log Root Directory: you should select a dedicated folder for the current PSOFT5_MNGT Management Service
• Large intermediate storage area: you should select a dedicated folder for the current PSOFT5_MNGT Management Service
• Large temporary storage area: you should select a dedicated folder for the current PSOFT5_MNGT Management Service
• Audience: select Advanced

Import the Assessment Model

• Open the Dashboard Service editor for the Dashboard Service (PSOFT5_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.

Re-attach the Complexity - Functional Evolvabilty Technical Criterion

The Technical Criterion "Complexity - Functional Evolvabilty" is delivered out of the box as "detached" (which will mean that the criterion and any child Quality Rules will be ignored), however, the PeopleSoft analysis requires this Technical Criterion and its child Quality Rules, therefore you must ensure that you re-attach it as follows:

• In the CAST Management Studio, move to the Assessment Models view and double click the imported Assessment Model. It will open in an editor.
• Click the Technical Criteria tab as shown below:

• Scroll down until you locate the "Complexity - Functional Evolvabilty" Technical Criterion - you can see that there is a tick in the "Detached" column:

• Double click the Technical Criterion to open it in its own editor, then tick the Attach option as shown below:

Analysis setup for Vanilla

• If the CAST Management Studio is already running and you are connected to PSOFT5_MNGT (i.e. the Project), quit the CAST Management Studio.
• Run the CAST Management Studio
• Validate and choose the connection profile for PSOFT5_V_MNGT (i.e. the Vanilla)
• Repeat the entire section (including all sub-sections) entitled "Analysis setup for Project" as described above. Ensure that you work with the CAST schemas that have been defined for the Vanilla: PSOFT5_V_CENTRAL and PSOFT5_V_LOCAL

Manage and run the analysis for Vanilla

• While still connected to PSOFT5_V_MNGT (i.e. the Vanilla) in the CAST Management Studio, in the 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 PeopleSoft 5.0 - Application onboarding, the Application editor will show the delivered Version in the Delivery tab:

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:

• 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 PeopleSoft 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 the Content Enrichment

In the Application editor, click the Content Enrichment tab.

PeopleSoft UA objects

• Create a SQL tool under Tools after analysis to update some metrics.
• In the Parameters tab:
  • copy the following statement into the SQL section:

Insert into §objpro (idobj,idpro,prop)
Select distinct t1.idkey,t3.idpro,0
From §keys t1
Join §keypar t2 on (t2.idkey = t1.idkey)
Join §objpro t3 on (t3.idobj = t2.idparent)
join §keys t4 on (t4.idkey = t3.idpro)
Where t1.objtyp in (1600673, 1600999)
and t4.objtyp=1600003
and t4.keynam not like '%PeopleSoft' -- not in the UA subset
And not exists (select 1
From §objpro op
Where op.idobj = t1.idkey
And op.idpro = t4.idkey)

• • There are no variables to define.

PeopleSoft Metrics Update

• Create a SQL Tool under Tools after analysis to update some metrics.
• In the Parameters tab:
  • copy and paste into the SQL section, the SQL from the file "Vanilla_ContentEnrichment_1_SQL_PeopleSoft Metrics Update.txt" provided in the extension as explained at the top of this page (use the text file that corresponds to your chosen CAST AIP environment - i.e. CSS).
  • There is no variable to define.

PeopleSoft Content Enrichment

• Create a Universal Importer tool under Tools after analysis to create additional links.
• In the Parameters tab:
  • copy and paste into the SQL section, the SQL from the file "Vanilla_ContentEnrichment_2_UI_PeopleSoft Content Enrichment.txt"provided in the extension as explained at the top of this page (use the text file that corresponds to your chosen CAST AIP environment - i.e. CSS).
  • set the Group Name to "PSOFT_TECHNICAL".
  • There is no variable to define.
• Activate the Drop data after import option.

Run analysis

• Check that the services are correctly defined and then run an analysis of the Application using the Run Analysis Only option:

Post analysis checks

• Check the log files - please see the documentation here for more information about this.

Manage and run the analysis for Project

• If the CAST Management Studio is already running and you are connected to PSOFT5_MNGT (i.e. the Project), quit the CAST Management Studio.
• Run the CAST Management Studio
• Choose the connection profile for PSOFT5_MNGT (i.e. the Project)
  
• In the 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 PeopleSoft 5.0 - Application onboarding, the Application editor will show the delivered Version in the Delivery tab:

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

• The Content state of the package should be showing Packaging successful
• In the Package content tab, you should see one project named Project for the PeopleSoft 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 the Assessment Model

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

• 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 "PeopleSoft: Prefix XXX".

• 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

Configure the Content Enrichment

In the Application editor, click the Content Enrichment tab.

PeopleSoft UA objects

This configuration is only required for CAST AIP 7.3.x

• Create a SQL tool under Tools after analysis to update some metrics.
• In the Parameters tab:
• copy the following statement into the SQL section:

Insert into §objpro (idobj,idpro,prop)
Select distinct t1.idkey,t3.idpro,0
From §keys t1
Join §keypar t2 on (t2.idkey = t1.idkey)
Join §objpro t3 on (t3.idobj = t2.idparent)
join §keys t4 on (t4.idkey = t3.idpro)
Where t1.objtyp in (1600673, 1600999)
and t4.objtyp=1600003
and t4.keynam not like '%PeopleSoft' -- not in the UA subset
And not exists (select 1
From §objpro op
Where op.idobj = t1.idkey
And op.idpro = t4.idkey) 

• There is no variable to define.

PeopleSoft Metrics Update

• Create a SQL tool under Tools after analysis to update some metrics.
• In the Parameters tab:
  • copy and paste into the SQL section, the SQL from the file "Project_ContentEnrichment_1_SQL_PeopleSoft Metrics Update.txt" provided in the extension as explained at the top of this page (use the text file that corresponds to your chosen CAST AIP environment - i.e. CSS).
  • There is no variable to define.

PeopleSoft Content Enrichment

• Create a Universal Importer tool under Tools after analysis to create additional links.
• In the Parameters tab:
  • copy and paste into the SQL section, the SQL from the file "Project_ContentEnrichment_2_UI_PeopleSoft Content Enrichment.txt" provided in the extension as explained at the top of this page (use the text file that corresponds to your chosen CAST AIP environment - i.e. CSS).
  • set the Group Name to "PSOFT_TECHNICAL".
  • There is no variable to define.
• Activate the Drop data after import option.

PeopleSoft Vanilla Import

• Create an SQL Tool under Tools after analysis to import data from the Vanilla's analysis service.
• Use the template provided in the file "Project_ContentEnrichment_3_SQL_PeopleSoft Vanilla Import.txt" provided in the extension as explained at the top of this page (use the text file that corresponds to your chosen CAST AIP environment - i.e. CSS) and paste the SQL into the SQL section in the Parameters tab:

• Now move to the Variables tab and add a variable:
  • Name = VANILLA_SCHEMA
  • Value = the name of the analysis service (in our example, PSOFT5_V_LOCAL)

PeopleSoft Discrimination with Vanilla

• Create an SQL Tool under Tools after analysis to compute the discrimination between the Vanilla and the Project.
• Use the template provided in the file "Project_ContentEnrichment_4_SQL_PeopleSoft Discrimination with Vanilla.txt" provided in the extension as explained at the top of this page (use the text file that corresponds to your chosen CAST AIP environment - i.e. CSS) and paste the SQL into the SQL section in the Parameters tab:

Modules

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

• Now create User Defined Modules as follows (the text files are provided in the extension as explained at the top of this page - use the text file that corresponds to your chosen CAST AIP environment - i.e. CSS).
  
  • Two modules for the entire PeopleSoft repository: this allows specific quality rules (like deadcode) to be executed and to check the quality rules on all objects
    • REPOSITORY_ADDED: use the template "Project_Module_REPOSITORY_ADDED.txt"
    • REPOSITORY_MODIFIED : use the template "Project_Module_REPOSITORY_MODIFIED.txt"

• For all these modules, remove the default Object Filter from the Filters tab and activate the option Build module content using an explicit list of objects in the Explicit content tab:
• Enter the appropriate query provided in the template txt file for EACH Module:

Generate a snapshot

• Check that the services are correctly defined and take a snapshot of the application.

Post snapshot checks

• Check the log files.
• Check the results in the CAST dashboards.