1. Development Workbench - Bulk Generation
  2. Generate Bulk Files

2 Generate Bulk Files

This topic provides systematic instructions to generate both front-end and back-end units in bulk.

On the Development Workbench Login page, specify the User ID and Password, and login to the Development Workbench Landing Page.
  1. On Expand Menu, click Bulk Generation node.
    The Bulk Generation screen displays.

    Figure 2-1 Bulk Generation


    Description of Figure 2-1 follows
    Description of "Figure 2-1 Bulk Generation"

    Oracle FLEXCUBE Universal Banking Development Workbench provides bulk generation (all files at one time) of both front-end and back-end units for both Extensible and Non-Extensible RADXMLs.

    Note:

    For Non-Extensible function IDs (RADXMLs), the bulk generation of only front-end files is supported.
  2. On the Bulk Generation screen, specify the fields.

    Table 2-1 Bulk Generation - Field Description

    Field Description
    Source File List

    The user must create a text file containing the absolute path of the RADXML for which bulk generation has to be done. Prepare a text file with an absolute path. If all the files are placed in one folder, dos commands (as shown below) can be used to generate the text file.

    Z:\FLEXCUBE_Kernel\FCUBS_11.4.0\MAIN>Dir /b /s *_RAD.xml > D:\BulkGeneration\Console.txt

    If the user is generating function IDs which has call forms attached to them, then the call form list should be included as a part of the source file list. If the call form is not included, then the generation fails.

    If units for call form files are not required to be generated, then call form paths can be prefixed with a Double Hyphen (--). All lines starting with a double hyphen will not be taken up for the bulk generation.

    As it is difficult to search and put each call form for individual screens, prepare a call form list upfront and add the files to be generated at the end of the call form list. Even if any of the call forms is repeated in the generation list it won’t affect the generation of that file.

    For example, Including call form to the source list, --Z:\FLEXCUBE_Kernel\FCUBS_11.4.0\MAIN\AM\RADXML\AMCPRPCL_RAD.xml

    If the user is generating a complete RADXML from the baseline area, a call form list is not required.
    Destination Path Enter the path where files will be generated. The Destination Path must be in the Client Machine if the Save Mode is Client, and it must refer to a path in Server if the Save Mode is Server.

    Note:

    The Zip mode is not supported for the Bulk generation activity.
    Sources Files Select the sources files from the drop-down list:
    • Extensible - On the selection of this option, only extensible files will be considered for a generation.
    • Non-Extensible - On the selection of this option, only non-extensible files will be considered for a generation.
    • Both - Both extensible and non-extensible files get generated.
    The Data XML Path field is defunct.

    The user has to select the required files to be generated for all RADXML’s.
    Workbench will generate the required files into respective folders.

    Figure 2-2 Source File list sample


    Description of Figure 2-2 follows
    Description of "Figure 2-2 Source File list sample"

    Figure 2-3 Including call forms in source file list


    Description of Figure 2-3 follows
    Description of "Figure 2-3 Including call forms in source file list"

    The workbench generates the required files into respective folders.

    Figure 2-4 Bulk Generation- After Selection of Required Fields


    Description of Figure 2-4 follows
    Description of "Figure 2-4 Bulk Generation- After Selection of Required Fields"

  3. On the Bulk Generation screen, click Generate.
    The Information window displays the generation status.

    Figure 2-5 Information


    Description of Figure 2-5 follows
    Description of "Figure 2-5 Information"

    On the successful generation of files, the file status displays as generated, and on failure, the file status displays as failed.

    Note:

    No front-end units will be generated for the notification and purge-entity RADXMLs.

    Figure 2-6 Bulk Generation- Generation Message


    Description of Figure 2-6 follows
    Description of "Figure 2-6 Bulk Generation- Generation Message"

    The time taken for bulk generation of units depends on the number of files, the number of units to be generated for each file, the client, and server machine configuration, etc.
  4. To view the generated file status, navigate to the bulk generation console path.
    Development Workbench generates a file status log in the Destination Path.

    Figure 2-7 User log files


    Description of Figure 2-7 follows
    Description of "Figure 2-7 User log files"

    It gives the details of all the files processed and their status as shown in the Status Log File figure.

    Figure 2-8 Status Log File


    Description of Figure 2-8 follows
    Description of "Figure 2-8 Status Log File"

    Missing label information will also be generated for each function ID for the generated units.

    Figure 2-9 Missing labels file


    Description of Figure 2-9 follows
    Description of "Figure 2-9 Missing labels file"