The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.

Anonymized Scheduling Data Export MOD009CL8

From DB 39.5.7

Attention
  • For the installation and in order to be able to use the export file, you need access to the server. If you do not have access, please consult your administrator

Up to DB 39.5.7

Attention
  • For the installation and in order to be able to use the export file, you need access to the server. If you do not have access, please consult your administrator

Access path

  • PM Administration Special Functions Anonymized scheduling data ecport
    • From version DB 39.5.7, the module is contained by default under the specified path. If this module does not exist under this path in your PLANTA version, you can optionally install it manually (for this purpose, see Module Installation Procedure).

Information

  • With this module, data and parameters relevant for scheduling can be exported anonymized.
  • This data can be made available to PLANTA for integration into the local test infrastructure for maintenance and further development of the scheduling.
  • The experience gained from analysis and evaluation help PLANTA to improve the functionality and performance of the scheduling.

Details

  • There are two parameters that can be edited in the module (the export can easily be carried out with the presets as well):
    • Export path
      • Directory in which the exported data is stored (the server work directory is preset here)
      • The length of this field is restricted to 40 characters.
        • If you enter more than 40 characters and then try to export, the Directory not available message is displayed.
      • The path
        • must lie on the server (not local)
        • must already exist
        • can be specified relatively or absolutely
    • Export mode
      • is used for naming the export file and has no functional influence
        • test: Input data from running operation (please use this setting if you want to provide us with your project structure)
        • expected: Result data by reference scheduling

Export

  • If you do not want to export to the server directory, adjust the Export path parameter.
  • Click on the Start export button
  • Confirm the Transfer all records for this mode? query.
  • After successful export, a dialog message is displayed that contains the path to the exported file (<test/expected>_data_lic<license number>_cs<changeset number>_<date>.zip).
    • This file in turn contains several .csv files (<test/expected>_data_<tables ID>.csv), which contain the data relevant for scheduling apportioned on data tables.
    • You may gladly check the content of the files before transferring them.
  • For transferring the file to PLANTA, please use the PLANTA Transfer Server.

From DB 39.5.7

Procedure for the module installation
  • The module is not contained in PLANTA project by default but can be integrated by carrying out the following steps:
    • Unpack the files from the attached 39.5.zip .zip archive in the server directory. As a result, the required files are copied to the migration, py, and sql directories.
    • Log on to PLANTA project and import migration packets from the file system to the Cross Release Packets module (via the button of the same name).
    • After restarting the server, the new module can be found under Access path as described.

From S 39.5.11

Procedure for the module installation
  • The module is not contained in PLANTA project by default but can be integrated by carrying out the following steps:
    • Unpack the files from the attached 39.5.zip .zip archive in the server directory. As a result, the required files are copied to the migration, py, and sql directories.
    • Log-on to PLANTA project Read migration packets.
    • Run the PortExportSchedulingDataCustomizing migration packet in the NEW Optional Packets module.
    • Run the CreateFolderPacket in the Help Packets or NEW Special Functions module.
    • After restarting the server, the new module can be found under Access path as described.

From S 39.5.0/DB 39.5.0

Procedure for the module installation
  • The module is not contained in PLANTA project by default but can be integrated by carrying out the following steps:
    • Unpack the files from the attached 39.5.zip .zip archive in the server directory. As a result, the required files are copied to the migration, py, and sql directories.
    • Log-on to PLANTA project and read the migration packets.
    • Run the PortExportSchedulingDataCustomizing migration packet in the NEW Migration Packets module.
    • Run the CreateFolderPacket migration packet (described here) in the NEW Migration Packets module.
    • After restarting the server, the new module can be found under Access path as described.

From S 39.5.0 to DB 39.5.0

Procedure for the module installation
  • The module is not contained in PLANTA project by default but can be integrated by carrying out the following steps:

From S/C/DB 39.4.4.0

Procedure for the module installation
  • The module is not contained in PLANTA project by default but can be integrated by carrying out the following steps:
    • Unpack the files from the attached 39.4.4.0.zip .zip archive to the server directory. As a result, the required files are copied to the py and sql directories.
    • Log-on to your database management system and run the respective files from the sql directory in your SQL dialect (from the oracle or ms.sql directories).
      • If you use SQLPlus, you have to run the SET SQLBLANKLINES ON command before running the sql files.
    • After restarting the server, the new module can be found under Access path as described.
Topic attachments
I Attachment History Size Date Comment
Zipzip 39.4.4.0.zip r7 r6 r5 r4 r3 14.5 K 2015-10-19 - 20:41  
Zipzip 39.5.zip r6 r5 r4 r3 r2 15.1 K 2015-10-19 - 20:41  

         PLANTA project









 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl