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

Update of PLANTA project

General Information

Information

  • This topic is a parent center for all further descriptions concerning the installation of PLANTA project. Links to the respective topics can be found in the "Overview of topics relevant for update" section.
  • Since from version 39.5.0, individual PLANTA software components (client, server, and database (customizing)) can be updated independent of one another, there is an individual description for the update of each component. There may be dependencies between individual versions of different components. In such a case, all components concerned must be updated.
  • For database update, PLANTA generally recommends to update the server as well since there are more dependencies between server and database than between, e.g., between database and client. Since it is also relevant from which version you want to update, there are several update combinations which are handled differently or which come with respective peculiarities. For a list of such combinations with links to the topics to be taken into account for the respective combinations, please refer to the "Overview Update Variants" section. The table only lists updates for server or server + database combinations. The client can always be updated independent of server and database. For more information, please refer to the Client Update topic.
  • All files required for the software update are available for download on the PLANTA Transfer Server.

Attention

  • PLANTA expressly recommends that software updates be carried out by experienced administrators. Please read the system requirements before you begin to update PLANTA project.
  • In the case of a database update, PLANTA recommends that you do this in a test system first, before updating the productive system.
  • If you have any questions regarding the basic conditions of the update procedure, please contact your PLANTA consultant.

Overview Update Procedure

Notes on numbering and names of PLANTA versions:

  • Release Earth: All three components (client, server, and database) stem from the version range of 39.4.0.0 - 39.4.4.0.
  • Release Venus: All three components (client, server, and database) stem from the version range of 39.5.0 - 39.5.x.
  • Release Venus on Earth: The database is of version 39.4.4.0 (Earth), server and client, however, are of version 39.5.x (Venus)

Version of your system You want to update to How?
Earth
(DB 39.4.4.0 and Server 39.4.4.0)
Venus on Earth
(only Server to 39.5.x)
The update is carried out via PLANTA Installer and for this purpose the following options must be selected
  • server.install = "yes" (GUI: select server installation)
  • db.install = "yes" (GUI: select database installation)
    • Please note that despite this setting no proper DB-update will be carried out. This setting is required in order to enable the execution of particular customizing-specific migration packets during server update.
  • planta.update_type = "r94" (GUI: update type: Update from Release 39.4.4.0 to Release 39.5.x (with DB 39.4))

Depending on the selected option, further parameters must be edited in the PLANTA Installer. Update via installer is only one step out of several within the server update process. For a description of the entire process, please click here.

  Venus
(Server and DB to 39.5.x )
In this constellation, a simultaneous update of both components via PLANTA Installer is not possible. The update must be carried out in two steps here.
  • Step 1: Server update to 39.5.x, as set out in the description above.
  • Step 2: For a database update to 39.5.x, the following options must be selected
    • server.install = "no" (GUI: server installation remains unselected)
    • db.install = "yes" (GUI: select database installation)
    • planta.update_type = "voeToVenus" (GUI: update type = Migrate from DB 39.4 to DB 39.5 with Release 39.5.x).

Depending on the selected option, further parameters must be edited in the PLANTA Installer. Update via installer is only one out of several steps within the DB-update process. For a description of the entire process, please click here.

Venus on Earth
(DB 39.4.4.0 and Server 39.5.x)
Venus on Earth
(only Server to a higher 39.5.x)
The update is carried out via PLANTA Installer and for this purpose the following options must be selected
  • server.install = "yes" (GUI: select server installation)
  • db.install = "no" (GUI: leave database installation unselected)
  • planta.update_type = "r95" (GUI: update type = Update from Release 39.5.x (with DB 39.4)).

The update with installer is only one out of several steps within the server-update process. For a description of the entire process, please click here.

  Venus (Server and DB to 39.5.x ) The update is carried out by PLANTA Installer and for this purpose, the following options must be selected
  • server.install = "yes" (GUI: select server installation)
  • db.install = "yes" (GUI: select database installation)
  • planta.update_type = "voeToVenus" (GUI: update type = Migrate from DB 39.4 to DB 39.5 with Release 39.5.x).

Depending on the selected option, further parameters must be edited in the PLANTA Installer. Update via installer is only one out of several steps within the server-update process. For a description of the entire server-update process, please click here. For the DB-update process, please click here.

Venus
(DB 39.5.x and Server 39.5.x)
Venus
(only Server to a higher 39.5.x)
The update is carried out via PLANTA Installer and for this purpose the following options must be selected
  • server.install = "yes" (GUI: select server installation)
  • db.install = "no" (GUI: leave database installation unselected)
  • planta.update_type = "venus" (GUI: Update type = Update from Release 39.5.x (with DB 39.5)).

Depending on the selected option, further parameters must be edited in the PLANTA Installer. Update via installer is only one out of several steps within the server-update process. For a description of the entire process, please click here.

  Venus
(Server and DB each to a higher 39.5.x )
The update is carried out by PLANTA Installer and for this purpose, you have to select
  • the database installation options
  • =server.install= = "yes" (GUI: select server installation)
  • and db.install = "yes" (GUI: select database installation)
  • planta.update_type = "venus" (GUI: update type = Update from release 39.5.x (with DB 39.5)).

Depending on the selected option, further parameters must be edited in the PLANTA Installer. Update via installer is only one out of several steps within the server-update process. For a description of the entire server-update process, please click here. For the DB-update process, please click here.

Overview of Topics Relevant for Update

From DB 39.5.7

Group Topic Content
Before installation/update SystemRequirements Soft and hardware requirements for PLANTA project
  UpdateSafetyOfIndividualCU Information on how to operate update-safe customizing and what must be considered otherwise
Update    
  InstallationByAutomaticInstaller Procedure for client, server, and database update to 39.5 with PLANTA Installer. A complete update of all components with automatic installer is possible from DB 39.5.7.
  ClientUpdate Procedure for updating the clients
  UpdateServer394To395 Procedure for updating the server from 39.4.4.0 to 39.5.x
  UpdateServer395 Procedure for updating the server from 39.5.x to 39.5.y
  DatabaseUpdate NEW Procedure for updating the database from DB 39.4.4.0 to DB 39.5.x and from DB 39.5.x to DB 39.5.y
  MigrationProcess The new hotfix procedure via with the help of which changes are made to the database
  DatabaseImportExportFromS39512 Description of the procedure for importing and exporting the database
After update InCaseOfUpdate Specific corrections which may be necessary after an update

From S 39.5.12

Group Topic Content
Before installation/update SystemRequirements Soft and hardware requirements for PLANTA project
  UpdateSafetyOfIndividualCU Information on how to operate update-safe customizing and what must be considered otherwise
Installation/Update InstallationPLANTAProject395  
  InstallationByAutomaticInstaller Procedure for the client and server update to 39.5 with the automatic installer. A complete reinstallation with the automatic installer is possible from DB 39.5.7.
  ClientUpdate Procedure for updating the clients
  UpdateServer394To395 Procedure for updating the server from 39.4.4.0 to 39.5.x
  UpdateServer395 Procedure for updating the server from 39.5.x to 39.5.y
  CustomizingDeployment NEW Exchange of the customizing (e.g. from the test system to the productive system) (new procedure from S 39.5.12)
  MigrationProcess Overview of the migration process introduced with 39.5 (changes to the database)
  DatabaseImportExportFromS39512 NEW Description of the procedure for importing and exporting the database
After installation/update InCaseOfUpdate Concrete corrections that may be necessary after an update
  PostInstallationSteps Post Installation Steps

Up to S 39.5.12

ClientUpdate Procedure for updating the client
CuExchange Exchange of the customizing (e.g. from the test system to the productive system) (old procedure up to S 39.5.12)
DatabaseImportExportUpToS39512 Instruction for import/export of entire database schemas to/from Oracle
InCaseOfUpdate Specific corrections that may be necessary after an update
PostInstallationSteps Post Installation Steps
InstallationByAutomaticInstallerS3958UpToS39526 Procedure for updating client and server to 39.5 using the automatic installer. It is currently not possible to carry out the entire reinstallation with the automatic installer (as long as database 39.5 is not available).
MigrationProcess Overview of the migration process introduced with 39.5 (changes to the database)
UpdateServer394To395 Procedure for updating the server from 39.4.4.0 to 39.5.0 or 39.5.1
UpdateServer395 Procedure for updating the server from 39.5.0 to 39.5.1
SystemRequirements Software and hardware requirements for PLANTA project
UpdateSafetyOfIndividualCU Information on how to operate update-safe customizing and what must be considered otherwise

Note

  • The description in this topic (as well as those of all linked topics) refers to updates in which customer systems are updated with the new/elaborated PLANTA Standard. If the customer uses multiple PLANTA systems, e.g. a test system, a development system, etc., in which the customizing status of one system is to be transmitted to the other one, we speak of a customer customizing deployment.

         PLANTA project









 
  • Suche in Topic-Namen

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