Migration Packets MOD009BWQ New from DB 39.5.0 / Up to S 39.5.11
Description for versions < DB 39.5.0 and < S 39.5.11
Description for versions < DB 39.5.0 and > S 39.5.11
Description for versions > DB 39.5.0 and > S 39.5.11
Access path
- Customizer Migration Migration Packets
Information
From S 39.5.2
- In this module migration packets can be managed and run.
- The module is divided into four areas:
- Special functions NEW
- In this area, there are 2 packets that are release-independent and contain comprehensive functionalities.
- the
FillMigrationruleTable migration packet which serves to search individually written packets in the file directory and load them in the module. The very same can be achieved by clicking on the Read packet from file system button.
- NEW
CreateFolderPacket.migration packet. It creates an import wrapper for all Python files and packets in order for them to be available for the PLANTA Server. Further information
- Packets to be run
- All packets that have the Completed checkbox deactivated are listed here. This concerns packets that have not been run yet, (help) packets that were run several times as well as packets that failed.
- Completed packets
- Here, all packets that have the Completed checkbox activated are listed here. This concerns both successfully run packets as well as packets for which the Completed parameter has been activated manually.
- Invalid packets
- Invalid packets are those that were e.g. renamed in or even removed from the directory.
- Depending on the packet type, we distinguish between Mandatory packets, Optional packets and Held packets.
- Mandatory packets must be run. Most of them are run automatically when the migration is started, others must be executed manually.
- Optional packets must be run actively if the features or bugfixes contained in it are required.
- Help packets must also be run actively and serve to point out errors.
- For each type, packets are additionally sorted by version.
Up to S 39.5.2
- In this module migration packets can be managed and run.
- The module is divided into four areas:
- Read packets from the data system
- In this area there is a new migration packet which serves to search individually written packets in the files directory and load them into the module.
- The very same can be achieved by clicking on the Read packet from file system button.
- Packets to be run
- All packets that have the Completed checkbox deactivated are listed here. This concerns packets that have not been run yet, (help) packets that were run several times as well as packets that failed.
- Completed packets
- Here, all packets that have the Completed checkbox activated are listed here. This concerns both successfully run packets as well as packets for which the Completed parameter has been activated manually.
- Invalid packets
- Invalid packets are those that were e.g. renamed in or even removed from the directory.
- Depending on the packet type, we distinguish between Mandatory packets, Optional packets and Held packets.
- Mandatory packets must be run. Most of them are run automatically when the migration is started, others must be executed manually.
- Optional packets must be run actively if the features or bugfixes contained in it are required.
- Help packets must also be run actively and serve to point out errors.
- For each type, packets are additionally sorted by version.
Execute migration packets.
- When starting the migration, all migration packets with Upon system start =
are run automatically.
- For those that are not run automatically, the following options are available:
- By clicking on the Execute incomplete packets, all packets for which the Completed is deactivated, can be run (cross-functionally).
- If only packets of a certain type and version are to be run, click on the Execute subordinate packets button.
- If a single packet is to be run manually (e.g. an optional packet or help packet), click on the Run packet button (green triangle) for the required packet in the Packets to be run area.
- After running the migration packets, their status has to be checked and possibly corrections have to be made. For this, see Details.
Details
- All migration packets are marked with a status icon on the left of the packet name.
-
means that a migration packet was run successfully.
-
signalizes that a migration packet failed. The failure of a migration packet may have several reasons:
- Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
- If this is the case, the packet will not be changed. The packet is considered failed.
- In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
- If the modification was carried out or the modification is not necessary, the packet may be set to completed manually by activating the Completed checkbox.
- By doing this, it is transferred from the Packets to be run area to the Completed Packets area.
- Many help packets check the customizing for problems.
- If they fail, this means that the customizer must become active.
- As a result, the positions listed in the logfile have to be checked and modified.
- If the cause for the failure was fixed, the migration packet may be run again by clicking on the run packet button.
-
signalizes that the migration packet has not been executed yet.
- Via the Show history link on the Packet name field, you can switch to the Overview of all previous runs</em Here, the parameters of the packet and their descriptions can be looked at and the logfiled of all runs may be viewed.
Note
- The sequence of execution of the migration packets is as follows:
- PLANTA component (e.g. Server)
- Component version (e.g. S 39.5.0)
- Packet category (e.g. "Mandatory packet")
- Packet name
Attention
. 
png 
