The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>InstallationAndUpdate>UpdatePLANTAProject>DatabaseImportExportFromS39512>CustomizingUpdate

Customizing Update

Objective

The customizing update serves to deliver the current PLANTA standard customizing and its integration in a development system. A.o., the customizing in the target system is replaced by a selective export of the source system using the DatabaseImportExportFromS39512 here. The owner license of the records is the basis for decision making for the retained respective range.

This procedure replaces the use of Pentaho in customizing exchange.

Requirements

Delivery and customer system must be congruent, i.e.
  • the program status of both systems must be identical.
  • migration packets must have run in the customer system.
  • the database schema of the customer system must be on the level of the delivery.
Generally, the same semantic requirements for the customizing exchange apply here as well — only the procedure for transport of database content is replaced.

Application

From S 39.5.18

There is a parameter file for the export which makes all required data available; it is located in the server installation directory under config/export/customizing_update_*.par. Here, all licenses to be exported must be entered under --include-licenses or all licenses to be retained must be entered under --exclude-licenses.

The counterpart for import can be found under config/import/customizing_update_*.par and must be adjusted to the respective target system. Here, all customer licenses that are not affected by the update must be entered under --exclude-licenses.

  • NEW The file exists in two versions::
    • config/import/customizing_update_venus.par for systems with a Venus database
    • config/import/customizing_update_voe.par for systems with an Earth database

Application example: 

# Export in the source system:
./planta_export.sh --output-file /tmp/cu_update @config/export/customizing_update_venus.par

# Import in the target system:
./planta_import.sh --input-file /tmp/cu_update @config/import/customizing_update_venus.par

Up to S 39.5.18

There is a parameter file for the export which makes all required data available; it is located in the server installation directory under config/export/customizing_update.par. Here, all licenses to be exported must be entered under --include-licenses or all licenses to be retained must be entered under --exclude-licenses.

The counterpart for import can be found under config/import/customizing_update.par and must be adjusted to the respective target system. Here, all customer licenses that are not affected by the update must be entered under --exclude-licenses.

Application example: 

# Export in the source system:
./planta_export.sh --output-file /tmp/cu_update @config/export/customizing_update.par

# Import in the target system:
./planta_import.sh --input-file /tmp/cu_update @config/import/customizing_update.par

         PLANTA project







 
  • Suche in Topic-Namen

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