...
| Info |
|---|
Summary: this page explains how to onboard a new PeopleSoft application with AIP CAST Console and work the process of analyzing the source code and generating a snapshot. Note that AIP CAST Console automates a large part of the configuration process for analyzing PeopleSoft technologies, as such, if you have previously been using the legacy CAST Management Studio to run your analyses, you will find that some of the steps required for CAST Management Studio are not mentioned in the instructions below. This is not an omission, it is simply because these steps are now automated and do not require manual intervention. |
Prerequisites
| AIP Core | ≥ 8.3.39 | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AIP CAST Console | ≥ 1.27.0-funcrel | ||||||||||||||||||||
| Extension | ≥ 5.2.0 2 (this will be installed automatically by AIP CAST Console).
| ||||||||||||||||||||
| Application creation | Two applications should be created in AIP CAST Console, for the Vanilla and Project repositories. See See Application onboarding without Fast Scan - Add a new Application for for more information about this. These applications should be named as follows:
Here are some indicative schema sizes for a large PeopleSoft analysis (3.4 GB of source code):
| ||||||||||||||||||||
| Repository Vanilla and Project repository extraction | AIP CAST Console only accepts .castextraction files generated by the CAST Database Extractor, in other words, the Vanilla and Project repository extraction must be actioned outside of AIP CAST Console (see below for more information). Note that for the Project repository extraction, this .castextraction file must be named with the exact same prefix as used for the .project file, for example if you name the file PeopleSoftExtract_Project.castextraction, the .project file must be named PeopleSoftExtract_Project.projectPeoplesoftProject. | ||||||||||||||||||||
| .project PeoplesoftProject file for Project repository | A .projectPeoplesoftProject text file must be configured and delivered with the .castextraction file for the Project repository. This file configures rule parameters and other data ((see below for more information). Note that this file must be named with the exact same prefix as used for the Project repository .castextraction file, for example if you name the file PeopleSoftExtract_Project.projectPeoplesoftProject, the .castextraction file must be named PeopleSoftExtract_Project.castextraction. |
...
These files need to be delivered to AIP CAST Console - see below.
Batch file logging
...
| Validation error #-1: Schema EFORCE_G5R3R is not a PeopleSoft repository: table PSRECDEFN is missing | If errors similar to "Validation error #-1: Schema EFORCE_G5R3R is not a PeopleSoft repository: table PSRECDEFN is missing" are reported in extactorextractor's log, it means either the schema has no PSRECDEFN table, or USER rights are insufficient (SELECT has not been granted on this table). |
|---|---|
| Resolution error type in / Invalid identification group value | The extraction log may contain the following messages:
These messages have a limited impact if the ratio of "Number of information messages" / "Number of rows extracted" is kept low (i.e. less the 1 or 2%). Some Quality Rule rule violations may be missed if these messages appear, however, the overall impact is low. |
Step 2 - .
...
PeoplesoftProject file configuration
| Info |
|---|
Note that this file must be named with the exact same prefix as used for the Project repository .castextraction file, for example if you name the file PeopleSoftExtract_Project.projectPeoplesoftProject, the .castextraction file must be named PeopleSoftExtract_Project.castextraction. |
The Project repository requires a .projectPeoplesoftProject configuration file that defines specific information required during the analysis:
- The name of the Vanilla application or Analysis schemaAnalysis schema (highly recommended) or the Vanilla Application name as defined in CAST Console
- Definition of PeopleSoft Definition of PeopleSoft specific rule contextual parameters
Below is a template .project PeoplesoftProject file - items in square brackets need to be manually defined:
| Code Block |
|---|
<PeoplesoftProjectConfig vanillaApplication="[application_name_or_<!-- The opening <PeoplesoftProjectConfig> element can define the [analysis_schema_name]"> <PeopleSoftApplication name="[peoplesoft_app_name_in_console] (recommended) or the [application_name_in_console]. Whichever you choose, ensure that you use the correct attribute as shown below: --> <PeoplesoftProjectConfig vanillaName="[analysis_schema_name_in_console]"> ... </PeoplesoftProjectConfig> or <PeoplesoftProjectConfig vanillaApplication="[application_name_in_console]"> ... </PeoplesoftProjectConfig> <!-- In between the opening <PeoplesoftProjectConfig> element you should define the following: --> <PeoplesoftProjectConfig ... > <PeopleSoftApplication name="[peoplesoft_app_name]" vanillaName="[app_name_in_vanilla]"/> <QualityRule id="[rule_id]"> <Parameter name="[parameter_name]" value="[parameter_value]"/> </QualityRule> <QualityRuleGroup name="companyPrefix" active="[true_or_false]"> <QualityRule id="[rule_id]" active="[true_or_false]"> <Parameter name="[parameter_name]" value="[parameter_value]"/> </QualityRule> </QualityRuleGroup> </PeoplesoftProjectConfig> |
...
This opening tag is required and defines the name of the Vanilla application defined in AIP Console. You can define either as created in CAST Console. CAST highly recommends that you input the Analysis schema name where possible as this ensures that Peoplesoft extension does not need to perform a lookup based on the Application name, or the corresponding Analysis schema namebut you can use the Application name instead if necessary. Both are highlighted in the screenshot below and can be found in the AIP CAST Console Admin Center (see Administration Center - Applications - Application Details):.
In the above example, this would give the following when using the Application Name:
Using the highlighted items shown in the example screenshot above, you can define either of the following:
| Code Block |
|---|
<PeoplesoftProjectConfig vanillaName="peoplesoft_project_local">
...
</PeoplesoftProjectConfig>
or
|
| Code Block |
<PeoplesoftProjectConfig vanillaApplication="PeoplesoftPeopleSoft_Project"> ... </PeoplesoftProjectConfig> |
...
| Code Block |
|---|
<QualityRule id="1600184"> <Parameter name="PeopleSoft: Max CC in Event" values=" -999"/> </QualityRule> <QualityRule id="1600384"> <Parameter name="Suffix PeopleSoft Language Record Table " value="Joe, William, Jack, Averell"/> </QualityRule> |
...
You now need to configure the source code to deliver in AIP CAST Console. There are two ways to deliver the source code, either in a ZIP file, or via a Source Folder Location:
| Vanilla repository | Place the PeopleSoftExtract_Vanilla.castextraction file (resulting from the extraction process in Step 1) in a folder called Vanilla. If you want to:
|
|---|---|
| Project repository | Place the following files in a folder called Project - note that the prefix of each file must be identical the other:
If you want to:
|
...
For each Application (Vanilla and Project) that you have created in AIP CAST Console, you need to now deliver the source code configured in Step 3 and run the analysis/snapshot. In AIP CAST Console, the process can be done in small steps, or in one go, and each is explained in more detail in:
...
in Workflow - Application onboarding without Fast Scan.
It is very important that you run the analysis and snapshot for the Vanilla application BEFORE you run the analysis and snapshot for the Project application.
...
When the snapshot has been completed for both repositories, CAST highly recommends that you check the results. This process is explained in more detail in Application onboarding without Fast Scan - Standard onboarding - check results. For the analysis step, the following is an example of the messages that you could expect (errors are shown in red):
...