Perform Actions on Derived Objects

After you register file objects (containing non-relational data) and create derived objects (tables) out of the registered file objects, you can perform the following actions on the derived objects:
tdm49
After you create derived objects (tables) out of the registered file objects, you can perform the following actions on the derived objects:
2
2
Import Data into Derived Objects
Import the sample data into derived objects (tables) that you have created in the relational database. Use an appropriate file to import the sample data into derived objects. You can then add more data into these derived objects by using data generation rules. The import data options that are displayed in the
Import
dialog change based on the object type.
  1. Select an appropriate project and its corresponding version from the
    Project
    drop-down list in the top blue bar.
    This selection sets the required project and version context for all the related operations that you perform in the Portal.
  2. Click
    Modeling
    in the left pane.
    The
    Modeling
    option expands and displays two options:
    Objects
    and
    Variables
    .
  3. Click
    Objects
    .
    The
    Objects
    page opens.
  4. Click the file object that you want to use for the data import operation.
    You cannot import the data into inherited file objects.
    The
    <Object_Name>
    page opens. This page includes the list of derived objects.
  5. Click the
    Import Data
    icon (up arrow).
    This icon becomes visible only when you create and register derived objects (tables).
    The
    Import Data
    dialog opens.
  6. Complete the following fields:
    • Document Group ID
      ID to assign to the data you import into derived objects. This value can be a string (excluding hyphens) or integer.
      You can use this ID to filter data in derived objects, during the Export process.
    • Advanced Settings
      • Connection Profile
        Specifies the default Connection Profile that you used at the time of creating derived objects, from a drop-down list of available Connection Profiles.
        Only select a Connection Profile different to the one you chose at Step 2, if you are sure that this Connection Profile also contains the tables you want to import, and that you have access to this Connection Profile.
      • Schema Name
        Specifies the schema name that you want to use. This drop-down list is populated based on the Connection Profile that you select.
      • Data Encoding
        Specifies the encoding format of the XML (for XSD, XML, WSDL, RR Pair) or JSON file that you want to use for importing the sample data.
        Default:
        UTF-8
        TDM Portal supports all encoding formats that Java supports. However, only these encoding formats are tested and certified:
        For XML:
        US-ASCII, ISO-8859-1, UTF-8, UTF-16BE, UTF-16LE, UTF-16.
        For JSON:
        UTF-8, UTF-32BE, UTF-16BE, UTF-32LE, UTF-16LE.
    • Import to Generator
      Lets you import the sample data into the data generator. Select the required data generator from the
      Data Generator Connection
      drop-down list. This drop-down list is populated with all the data generator connections available to the selected Project, Project version, and Connection Profile.
      If you import the sample data into the data generator, you can use the
      Registered Tables
      (
      Generators, Data Generators, <Generator_Name>, Select Tables
      ) dialog to verify whether required tables include the imported data.
    • (XSD, XML, or JSON only) 
      File(s) to Upload
      Specifies the location of the file that contains the sample data that you want to import into the derived objects. You can drag and drop the file or browse to the file location.
    • (WSDL or RR Pair only)
      R/R Pair Link ID
      Specifies an alphanumeric request-response link ID that identifies the associated request-response pair. For import, the value can be an integer or string (without hyphens). For example,
      100
      or
      RD
      .
      You can filter data by
      R/R Pair Link ID
      when you export derived objects.
    • (WSDL or RR Pair only)
      Request-File to Upload
      Specifies the location of the request data .xml (applicable for WSDL and RR Pair), .json (applicable for RR Pair), or .txt (applicable for RR Pair) file. You use this file to populate the relational database with the sample request data included in the specified file. You can drag and drop the file or browse to the file location.
      Ensure that the request and response pair files are of the same type. In the case of WSDL files, both XML files must be of the same version of SOAP (1.1 or 1.2).
    • (WSDL or RR Pair only)
      Response-File to Upload
      Specifies the location of the response data .xml (applicable for WSDL and RR Pair), .json (applicable for RR Pair), or .txt (applicable for RR Pair) file. You use this file to populate the relational database with the sample request data included in the specified file. You can drag and drop the file or browse to the file location.
      RR pair files using .txt extension contain information in the form of HTTP headers and body, thereby providing support for REST format. For more information about the structure of .txt RR files, see the REST RR Pair Format section.
  7. Click the
    Import
    button.
    The CA TDM Portal creates a job for the import operation and adds it to the jobs queue.
You can view the jobs queue in the Requests table by clicking the job ID in the message. The requests table displays all the job requests with their status, date, name, and other relevant information. You can also click rows in the Requests table, to view additional information about that job in the
Additional Information
dialog.
Create Data Generation Rules
After you import the sample data into derived tables, create data generation rules. These rules help you generate synthetic data that you can publish into the derived tables.
Note:
For more information about how to create data generation rules, see the Create Data Generation Rules section.
Publish Data into and Export Data from Derived Objects
You can publish the data into the appropriate target schema based on the defined data generation rules and then export the same data into required formats.
  1. Select an appropriate project and its corresponding version from the
    Project
    drop-down list in the top blue bar.
    This selection sets the required project and version context for all the related operations that you perform in the Portal.
  2. Click
    Modeling
    in the left pane.
    The
    Modeling
    option expands and displays two options:
    Objects
    and
    Variables
    .
  3. Click
    Objects
    .
    The
    Objects
    page opens.
  4. Click the file object that you want to use for the data publish and export operations.
    You cannot export data from inherited file objects.
    The
    <Object_Name>
    page opens. This page includes the list of derived objects.
  5. Click the Export Data icon (down arrow).
    This icon becomes visible only when you create and register derived objects (tables).
    The
    Export Data
    dialog opens.
  6. Complete the following fields:
    • Connection Profile
      Specifies the connection profile that you want to use for the publish or export process.
      Users can access only those connection profiles that they have created. They cannot access connection profiles created by other users.
    • Schema Name
      Specifies the schema name that you want to use for the publish or export operation. This drop-down list is populated based on the connection profile that you select.
    • Document Group ID
    1. ID to assign to the data you import into derived objects. This value can be a string (excluding hyphens) or integer.
      You can use this ID to filter data in derived objects, during the Export process.
      You can specify this value in the following ways:
      • Single document group ID. For example:
        101
      • Comma-separated list of document group IDs. Examples:
        101,102,103
        or
        ID1,ID2,ID3
      • Range of document group IDs. For example,
        101-109
        . You can use the range method only if your document group IDs are integers.
    • Publish Files
      Lets you generate and add more data to the derived tables in the database based on the defined data generation rules. When you select
      Publish Files
      , the following options appear:
      • Data Generator Connection
        Lets you select the appropriate data generator connection from the drop-down list. This list is populated with all the data generator connections based on the selected project, project version, and connection profile.
      • No of Files to Publish
        Lets you specify the number of rows that you want to add to the derived tables in the database.
    • (WSDL or RR Pair only)
      R/R Pair Link ID
      Specifies an alphanumeric request-response link ID that identifies the associated request-response pair. For import, the value can be an integer or string (without hyphens). For example,
      100
      or
      RD
      .
      You can filter data by
      R/R Pair Link ID
      when you export derived objects.
    • (WSDL or RR Pair only)
      Update Virtual Service
      Specifies whether you want to update a virtual service in a CA Service Virtualization 9.1 environment with sample RR pair data. The integration with CA Service Virtualization helps you take advantage of the large volume of test data in the form of sample RR pairs that the CA TDM Portal generates. You can deploy your virtualized services with that test data and cover a wide range of testing scenarios. Using this integration, you can manage the following use cases:
      • Virtual service on demand
      • Increase test coverage
      • Data synchronized across inter-dependent systems and services
      • Up-to-date virtual services
      When you select the
      Update Virtual Service
      option, the following fields are displayed:
      • Virtual Service Environment
        Specifies the name of the virtual service environment (VSE) to which you want to connect to add the sample RR pair data to a virtual service. This list is populated based on the virtual service configuration that you perform in Configure CA Service Virtualization Details.
      • Virtual Service
        Specifies the name of the virtual service that you want to update with the sample RR pair data. This list is populated based on the virtual service configuration that you perform in Configure CA Service Virtualization Details.
    • Advanced Settings
      • Data Encoding
        Specifies the encoding format of the XML (for XSD, XML, WSDL, RR Pair) or JSON file that you want to use for importing the sample data.
        Default:
        UTF-8
        TDM Portal supports all encoding formats that Java supports. However, only these encoding formats are tested and certified:
        For XML:
        US-ASCII, ISO-8859-1, UTF-8, UTF-16BE, UTF-16LE, UTF-16.
        For JSON:
        UTF-8, UTF-32BE, UTF-16BE, UTF-32LE, UTF-16LE.
      • Base File Name
        Specifies the value to prefix to the exported XML file name.
        Default:
        CATDMShredder
      • (XML or XSD only)
        Export Into
        Specifies whether to export the data into a single XML file or multiple XML files. Supported options are Single File or Multiple Files.
        You can only export XSD or XML data to XML files.
        Default:
        Multiple Files
      • (XML or XSD only)
        Require Data Indentation
        Specifies whether to indent the XML data while exporting.
        Default:
        Yes
      • (XML or XSD only)
        Include XML Processing Instruction
        Specifies whether to include the XML declaration in the exported XML file.
        Default:
        Yes
      • (XML or XSD only)
        Include Standalone Attribute
        Specifies whether to include the generated standalone attribute value in the exported XML file.
        Default:
        No
      • (XML or XSD only)
        Honor Unqualified forms
        Specifies the flag to honor the unqualified form for elements. If 'elementFormDefault' is 'undefined' for a schema (or an element has form=undefined), its XML instance files can have elements without namespace prefixes.
        Default:
        Yes
      • (JSON only)
        Export Into
        Specifies whether to export the data into a single file or multiple files. Supported options are Single File or Multiple Files.
        Default:
        Multiple Files
      • (JSON only)
        Escape Non-ASCII
        Specifies whether to escape non-ASCII characters at the time of exporting the data into a JSON file. If enabled, this property exports all characters outside the 7-bit ASCII range using the backslash character as an escape character.
        Default:
        No
      • (JSON only)
        Quote Field Names
        Specifies whether you want to export JSON object field names using double quotes.
        Default:
        Yes
      • (JSON only)
        Quote Non Numeric Numbers
        Specifies whether you want to export float values or double values as strings using double quotes.
        Default:
        Yes
      • (JSON only)
        Write Numbers As Strings
        Specifies whether you want to export all numbers as JSON strings.
        Default:
        No
      • (JSON only)
        Pretty Print JSON
        Specifies whether you want to format/indent the JSON data while exporting.
        Default:
        Yes
  7. Click the
    Publish & Export
    button.
    The CA TDM Portal creates a group job for the publish and export operation and adds it to the jobs queue. The group job includes two jobs—publish job and export job.
You can view the jobs queue in the requests table by clicking the job ID in the message. The requests table displays all the job requests with their status, date, name, and other relevant information. When the status of your job is shown as
Completed
, the CA TDM Portal completes the following tasks in sequence:
  • Publish the data into the derived tables in the database.
  • Export the published data from the derived tables into the specified file format.
You can use these exported files to test applications that rely on non-relational data sources.
Delete Data from Derived Objects
You can delete data from derived tables. Only the data is cleared from derived tables, the derived tables are not deleted from the database.
  1. Select an appropriate project and its corresponding version from the
    Project
    drop-down list in the top blue bar.
    This selection sets the required project and version context for all the related operations that you perform in the Portal.
  2. Click
    Modeling
    in the left pane.
    The
    Modeling
    option expands and displays two options:
    Objects
    and
    Variables
    .
  3. Click
    Objects
    .
    The
    Objects
    page opens.
  4. Click the file object for which you want to delete data from derived objects.
    Note:
    You cannot perform this operation if the file objects are inherited.
    The
    <Object_Name>
    page opens. This page includes the list of derived objects.
  5. Click the Delete Data icon.
    Note:
    This icon becomes visible only when you create and register derived objects (tables).
  6. Click
    Delete
    on the confirmation dialog.
    The CA TDM Portal creates a job for the delete data operation and adds it to the jobs queue. You can view the jobs queue in the requests table by clicking the job ID in the message. The requests table displays all the job requests with their status, date, name, and other relevant information. When the status of the job is shown as Completed, the CA TDM Portal completes the task of deleting the data from derived tables. You can also click the required row in the requests table to view the additional information about the job, if necessary. The additional information is displayed in the
    Additional Information
    dialog.
Drop Derived Objects
You can drop derived tables from the database if you do not require them. When you drop derived tables, the tables are unregistered from the repository and then they are deleted from the database.
Note:
You cannot drop a single derived table.
  1. Select an appropriate project and its corresponding version from the
    Project
    drop-down list in the top blue bar.
    This selection sets the required project and version context for all the related operations that you perform in the Portal.
  2. Click
    Modeling
    in the left pane.
    The
    Modeling
    option expands and displays two options:
    Objects
    and
    Variables
    .
  3. Click
    Objects
    .
    The
    Objects
    page opens.
  4. Click the file object for which you want to delete derived objects.
    Note:
    You cannot perform this operation if the file objects are inherited.
    The
    <Object_Name>
    page opens. This page includes the list of derived objects.
  5. Click the Drop Derived Objects icon.
    Note:
    This icon becomes visible only when you create and register derived objects (tables).
  6. Click
    Delete
    on the confirmation dialog.
    The CA TDM Portal creates a job for the drop derived objects operation and adds it to the jobs queue. The selected objects are removed from the
    Objects
    page only when the corresponding delete job is completed. They remain visible on the page till the job is in progress.
    You can view the jobs queue in the requests table by clicking the job ID in the message. The requests table displays all the job requests with their status, date, name, and other relevant information. When the status of the job is shown as Completed, the CA TDM Portal completes the task of removing all derived tables from the database. You can also click the required row in the requests table to view the additional information about the job, if necessary. The additional information is displayed in the
    Additional Information
    dialog.