Register your PeopleSoft applications in the CAST AIC Portal

In the CAST AIC Portal, register two new Applications as follows:

• One for the Vanilla: the PeopleSoft Repository without any custom code
• One for the Project: the PeopleSoft Repository that contains the custom code for one or multiple PeopleSoft applications

Deliver the source code for Vanilla

To deliver the source code for the Vanilla, you must download and install the CAST Delivery Manager Tool (DMT) on a machine that has access to the database that hosts the PeopleSoft repository (see the Operating System section in Supported Platforms for more information). CAST recommends installing the DMT on the same machine as the database is installed on, to take advantage of faster direct disk to disk performance for the code extraction. The DMT establishes a JDBC connection to the database and executes a set of queries. If the DMT is installed on another machine, the network will negatively impact the time required to extract the source code.

Once the DMT has been downloaded and installed, you'll have access to the interface:

First create a version:

The version editor is then displayed:

Create a package. In the wizard, select "PeopleSoft" under "Select a vendor specific repository":

In the wizard, select the extractor corresponding to the database that contains the PeopleSoft repository:

 In the package editor, provide a package name and enter the relevant values in "Where is your source code?":

• The user name in the credentials is used for the connection
• For the Vanilla, select "Vanilla" in the field "Repository type"
• Provide the schema that contains the PeopleSoft tables (PSRECDEFN, …)

To extract the source code, click on "Package…".

When the extraction has completed, the content state for the Package should display "Packaging successful" and the action required is "Package ready to be delivered". You can then deliver the source code. To do so, click "Deliver…". In the wizard, answer "Yes" when prompted whether the delivery is complete:

When the delivery has completed, the content state for the Package should display "Packaging successful" and the action required is empty (i.e. nothing further to do).

Deliver the source code for Project

To deliver the source code for the Project, you must download and install the CAST Delivery Manager Tool (DMT) on a machine that has access to the database hosting the PeopleSoft repository. Then follow the same process as for the Vanilla. 

1- Create a package for "PeopleSoft" extraction 

• In the wizard, select "PeopleSoft" under "Select a vendor specific repository":
• In the package editor, enter the relevant values in "Where is your source code?":
  • The host name and service ID/name hosting schema with PeopleSoft tables 
  • The user name in the credentials is used for the connection
  • Select "Project" in the field "Repository type"
  • Provide the schema that contains the PeopleSoft tables (PSRECDEFN, …)

2- Create a second package to deliver the database extraction (i.e. the ddl) in order to compute the embedded SQL.

• In the wizard, select "Oracle" or "DB2 zOS" or "DB2 UDB" under "Select a database". 
• In the package editor, enter the relevant values in "Where is your source code?":
  • • The host name and service ID/name hosting schema with PeopleSoft tables 
    • The user name in the credentials is used for the connection
    • Provide the schema that contains the PeopleSoft tables ( same schema referenced in first package for "PeopleSoft" extraction)

Post extraction check

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 extactor'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:

• Resolution error type in
• Invalid identification group value

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 violations may be missed if these messages appear, however, the overall impact is low.