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

Customer Customizing Deployment From S 39.5.12

Description dor versions < S 39.5.12


Information

  • The customizing delivery procedure serves to roll out the customizing, e.g. from a development system at the customer's facility to his/her productive system. As a result, the customizing in the target system is completely replaced by an export from the source system using the Database Import/Export function.

Requirements

  • Source and target system must be congruent, i.e.
    • the program status of both systems must be identical and all migration packets must have the same status
    • the database schema of the target system must have the same status as the source system

A customizing deployment generally consists of the following elements:

  • Python directory of the server (example: py.zip)
  • Customizing deployment files (example: cu_deployment_2015_02_04.zip)
  • SQL files (example: sql_planta_1_1.sql)

Export Procedure

From S 39.5.18

The export step is necessary if you carry out the deployment internally yourself. If you have any questions, please get in contact with your PLANTA consultant.

Information

  • NEW For the export, there are two versions of a parameter file which provides all necessary files.
    • These two files are located in the server installation directory under config/export/customizing_deployment_*.par.
    • The config/export/customizing_deployment_venus.par file is used for systems with DB 39.5.x.
    • The config/export/customizing_deployment_voe.par file is used for systems with DB 39.4.4.0.
Export example 
./planta_export.sh --output-file /tmp/cu_deployment_2015_02_04  @config/export/customizing_deployment_venus.par

Up to S 39.5.18

The export step is necessary if you carry out the deployment internally yourself. If you have any questions, please get in contact with your PLANTA consultant.

Information

  • For the export, there is exactly one parameter file that provides all necessary files.
    • The file is located in the server installation directory under config/export/customizing_deployment.par.
Export example 
./planta_export.sh --output-file /tmp/cu_deployment_2015_02_04  @config/export/customizing_deployment.par

Import Procedure

Information
  • The import procedure requires several steps.
  • The associated parameter files are located in the config/import/customizing_deployment subdirectory.

From S 39.5.18

File Description Note
01_replace_q1b_q2b.par Involves the complete replacement of the Q1B and Q2B schema (except for DT345) Mandatory part
02a_replace_module_variants.par Completely replaces the module variants. As a result, tables 500-503 are overwritten. optional
02b_add_module_variant_itexts.par Additionally provides the I-texts of the Q3B schema incrementally, i.e. not destructively  
03_replace_interfaces_voe.par NEW Completely replaces the interface tables (for DB 39.4.4.0) optional
03_replace_interfaces_venus.par NEW Completely replaces the interface tables (for DB 39.5.x) optional
04_replace_process_models.par Replaces the process models optional

Up to S 39.5.18

FileSorted descending Description Note
04_replace_process_models.par Replaces the process models optional
03_replace_interfaces.par Completely replaces the interface tables optional
02a_replace_module_variants.par Completely replaces the module variants. As a result, tables 500-503 are overwritten. optional
02b_add_module_variant_itexts.par Additionally provides the I-texts of the Q3B schema incrementally, i.e. not destructively  
01_replace_q1b_q2b.par Involves the complete replacement of the Q1B and Q2B schema (except for DT345) Mandatory part

Step 1: Steps to be taken before deployment

  • Stop the PLANTA service.
  • Save the database and the Python directory of the server (e.g. rename "py" to "py_alt")

From S 39.5.18

Step 2: Import new files to the Python directory of the server
  • Unzip the zip-archive which contains the Python directory.
  • All subdirectories of the new "py" directory are to be copied to the "py" directory of the server.
    • The directory structure has changed with server 39.5.18 and the files of a former release cannot simply be copied. Instead they must be allocated to the correct directories. See also: DirectoryStructure

Up to S 39.5.18

Step 2: Loading new PLANTA application server files
  • Unzip PLANTA application server files (example: Applikationsserver.zip).
  • The directories delivered by PLANTA are to be replaced:
    • Example: New binary files (dlls)
      • All files of the delivered "dlls" directory are to be copied to the "dlls" directory of the application server.
    • Example: New Python files ("py")
      • All subdirectories of the delivered "py" directory are to be copied to the "py" directory of the application server.

Step 3: Importing delivered customizing deployment files

  • PLANTA delivers a zip archive including the customizing deployment files (example: cu_deployment_2015_02_04.zip).
    • This zip archive does not need to be unpacked. The archive is automatically unpacked during the import procedure.
  • Store the zip archive at an arbitrary position on the application server (example: /tmp/)
  • Switch to the PLANTA application server directory (example: /planta/app/Lief).
  • Carry out the following import commands in this exact order:

From S 39.5.18

Example: 
./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/01_replace_q1b_q2b.par

./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/02a_replace_module_variants.par

./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/02b_add_module_variant_itexts.par

# Only use the file corresponding to the database.
./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/03_replace_interfaces_venus.par
./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/03_replace_interfaces_voe.par

./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/04_replace_process_models.par

Up to S 39.5.18

Example 
./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/01_replace_q1b_q2b.par

./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/02a_replace_module_variants.par

./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/02b_add_module_variant_itexts.par

./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/03_replace_interfaces.par

./planta_import.sh --input-file /tmp/cu_deployment_2015_02_04.zip @config/import/customizing_deployment/04_replace_process_models.par

Step 4: Executing the SQL files

  • Launch SQL Plus and connect it to the database user of the PLANTA application 
    sqlplus DB user/password@DB-SID
  • Execute the delivered SQL file(s) 
     @ sql_planta_1_1

From S 39.5.20

Step 5: Steps to be taken after deployment
  • Delete the target server directory.
  • Start the PLANTA service.
    • The target directory will be regenerated with current POJO classes.

Up to S 39.5.20

Step 5: Steps to be taken after delivery
  • Start the PLANTA service

Notes

  • If the contents of the data table that possess an automatic number are transferred but their counter values are not, the counter values must be adjusted manually afterwards.
  • If history data tables (HIS) are copied during import, the HIBERNATE_SEQUENCE must be set to the highest level of the data available in the history tables.
  • If interface data is exchanged, the archived interface configurations will be lost.
    • This includes all logging files, parameters, as well as all pool records!
  • If import errors occur due to data corruption, the Check Database Consistency module can be used to check or correct the data.

         PLANTA project







 
  • Suche in Topic-Namen

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