Page tree
Skip to end of metadata
Go to start of metadata

On this page:

This section explains how to package one or multiple live target database/schemas for subsequent analysis in the CAST Management Studio. The technologies that fall into this category are as follows:

  • Oracle PL/SQL
  • Microsoft T-SQL
  • Sybase T-SQL


Because of the way in which the CAST analyzers are built, the packaging mechanism (i.e. what actually gets packaged and delivered by the CAST Delivery Manager Tool) differs as explained below:

Packaging Oracle PL/SQL, Microsoft T-SQL and Sybase T-SQL databases/schemas

When packaging schemas/databases hosted on any of the above RDBMS, the CAST Delivery Manager Tool will do as follows:

  • extract the required schema(s) to file from a live target database
  • the extracted files are then packaged and delivered
  • these files are then analyzed in the CAST Management Studio, therefore the live database does not need to be available during the analysis.

Packaging IBM DB2 UDB

When packaging schemas hosted on an IBM DB2 UDB server, instead of extracting the target schemas to file, the CAST Delivery Manager Tool will only package:

  • The connection parameters for your target DB2 UDB server
  • A list of schemas you need to analyze defined manually or via connection to the database.

No physical files are packaged and delivered. The CAST Delivery Manager Tool therefore requires network access to the target server to perform the packaging action from the CAST Delivery Manager Tool. You do NOT need to install a compatible client connection layer (for the target server) on the machine on which you are running the CAST Delivery Manager Tool. Instead, the CAST Delivery Manager Tool will use a JDBC connection to access the live target server so that you can select the schemas for analysis.

A note about what happens when the package is deployed in the CAST Management Studio

When the DB2 UDB package is deployed in the CAST Management Studio, the following is created:

  • An Analysis Unit for each schema you selected for analysis in the CAST Delivery Manager Tool
  • A JDBC connection profile to the target server on which the selected schemas are stored - using the connection parameters you packaged in the CAST Delivery Manager Tool

When you run the analysis in the CAST Management Studio, network access to the live database to be analyzed is required, therefore the database must be available and online during the analysis process. The CAST Management Studio will no longer use the JDBC connection profile to access the target server, instead the analyzer will look for a 32bit ODBC User DSN entry referencing an alias containing the "host name" of the target server that was defined in the JDBC connection profile (configured in the CAST Delivery Manager Tool and then transferred to the CAST Management Studio). This ODBC entry needs to be created on the machine running the CAST Management Studio before the analysis is run or the snapshot is generated and will require the installation of a compatible 32bit DB2 UDB client connection layer on the same machine - this is explained in Validate and configure RDBMS connection for DB2 UDB Analysis Units.

Create and configure the package

As an example we are going to package an Oracle schema that forms the "server side" part of our Application "MEUDON", but the process is identical for all of the technologies mentioned above:

  • In the CAST Delivery Manager Tool, in the Version page, click the  button as shown below:

  • The Add Package wizard will then be displayed:

  • As explained earlier, in this example we are going to package the source code from an Oracle schema. The first screen in the wizard will ask you where your source code is located - in this example we have selected Oracle as shown above.
  • Click Next to continue.

  • In this screen we are presented with various options - we will choose the first option (CAST extractor for Oracle) since we want to package a schema located on an Oracle 11g database.
  • Click Finish to complete the wizard.
  • The Package Configuration tab will then be displayed, enabling you to configure how the CAST Delivery Manager Tool will access your target live database server and which databases/schemas need to be packaged:

  • Start by giving the source code package a name:

  • Next fill in the connection details for your Oracle database:

  • For example:
Field name
Host name

Enter the internet host name (or machine name) of the machine on which the database is installed so that the CAST Delivery Manager Tool can access via a JDBC connection.

Note that when packaging DB2 UDB schemas, the contents of this field must match the name of the alias (the value "DBALIAS") defined in your ODBC connection entry on the machine where you will run the analysis from (i.e. the machine on which the CAST Management Studio is installed). For more information, please see Validate and configure RDBMS connection for DB2 UDB Analysis Units.

Enter the port number on which your database runs. The default values are set as follows:

  • Oracle = 1521
  • Microsoft = 1433
  • Sybase ASE = 12500
  • DB2 UDB = 50000
DatabaseEnter the name of the database on which your required schemas are stored.
CredentialsPlease refer to Required RDBMS rights for packaging a database for more information about the user name and password you should use. You can find out more information about the Remember password option in the CAST Delivery Manager Tool help.
  • Finally, choose the schema(s) you want to include in the package. There are two methods of doing this:
    • Either browse the Oracle database and choose those you require (we will do this as it also means you can check that the connection details you entered are correct)
    • Or enter the schema name(s) manually

  • The chosen schema (CASTPUBS in this example) will now be listed in the table:

Note that if you intend to extract and analyze multiple schemas and you expect to be able to view inter schema links after the analysis, please ensure that all schema/databases from the same instance are included in the same CAST Delivery Manager package.


  • No labels