Package Manager

Last updated
Save as PDF

Overview

You can install (=import) or update packages with the package manager. The status of a package indicates, whether a reinstallation or an update is possible. If your current Data World is active, you can open the package manager only for the view. Reinstallation or updates are only possible with a disabled data world.

After opening the package manager, the waveware Service Center is opened. Registration with your user data, which you received after registration, is required.

In the waveware server settings, in the 'Service Center' area, you can specify which data is used for logging in by default:

The default is "https://portal.waveware.de" in the 'Url' field. After successful registration, you can add your email address and password in the 'Login' field so that you can access the Service Center without having to re-enter your password.

In addition, as of waveware 11.190.3625, settings for the proxy server including user name and password can be stored in this area. This may be necessary because the package download takes place in the background and not in the browser window that the repository displays in the package manager. The specified proxy server data is then used for these downloads.
Since access can be different for each PC in the network, these settings are not stored centrally, but only within the DataManagement Client. If you start the DataManagement on another PC, you have to store the proxy server data there again.

Then select the menu item 'Packages" under 'Technical Support' on the left to display a list of available packages.

In the standard system, all packages are listed sorted by package ID that have the status "released" and are licensed for your version. In the upper area of the window you can search the package list for specific keywords and thus display the appropriate packages. In addition, three filters are offered:

Status
You can filter which packages should be shown according to the development status. The development status is as follows:
- All
  Regardless of the level of development, all packages are offered. The filter is deactivated.
- Released
  The package has been tested, released and can be used (default).
- Untested
  The package development is completed. The package is located in the Quality Control. Unchecked packages can generate side effects, which were not considered in the development. Installation or update entails a distinct risk.
- Beta
  Package is located in the advanced development stage. Installation or update entails a distinct risk.
- Alpha
  Package is located at the beginning of the development. Such package is not recommended for the installation or update!
Licensed
Another filter allows you to restrict only licensed packages (default). 'All' deactivates the filter and lists all packages regardless of the licensing status.
Update Status
This filter only shows packages that require an update. 'All' (default) deactivates the filter and shows all available packages.

Create a backup before you install or update packages. When problems occur, you are indicated, that you should reset your system to the original state.

Install Packages

Choose the package, which are to be installed. To do this, click on the plus symbol in front of the line of a desired package or select all corresponding packages by clicking on the 'All LICENSED' button to mark all licensed or 'All UPDATES' to mark all packages to be updated. A segment then appears in the upper area, in which the selected packages are displayed.

To install all selected packages, click the button with the blue triangle. You can remove individual packages from this selection by clicking on the cross behind the entry. With the 'NONE' button in the header of the window you can reset the selection completely.

Alternatively, packages can also be installed directly with one click. There is a triangle button in every line of an uninstalled package.

There is also the option of selecting a specific version of a package for installation or installing it directly. The column 'Versions' is available in the rear area of a package line. This can be expanded with one click and releases all available versions of the current package. With the familiar buttons (plus or triangle symbol) the version can now be selected for the installation of several packages or installed directly.

After installing the packages, you will receive an HTML file named 'wavewarePackageManager%date&time%.html', which is located in your temp directory, in the 'LoyHutz' folder. It is automatically opened immediately after the process is completed and contains all errors, warnings and notes that have occurred (more under 'Messages').

Package Dependencies

If you want to install a package that has dependencies on other packages that have not been installed, a message appears before the installation that breaks down these dependencies:

In this example the 'REG-IS Interface' package is installed (shown under 'Selected packages'). Which packages really need to be installed to maintain the dependencies is shown under 'Packages that will be installed'. The previously selected package itself is also listed here for a complete list.

When installing, all packages are updated first and then new packages are imported.

Install Packages Offline

If waveware cannot access the waveware Service Center directly, for example, ifthere is no Internet connection, you can use the 'Local Package Manager' button in the DataManagement ribbon to install packages from a local directory. You can obtain the package files from another device and transfer them to the local directory created.

This function is available as of waveware 11.190.3625. In earlier versions, the offline package installation is only possible via Microsoft PowerShell.

Log into your account at the waveware Service Center from any other device.
Navigate to the point 'Technical Support' / 'Packages' in the Service Center.
Now look for the package that you want to install; e.g. Equipment Management (112).
Click the 'Download' button.

Packages that the downloaded package depends on will be downloaded automatically.

You will receive a 'package.zip' file.
Create a directory on the waveware server into which you extract the content of the 'package.zip' file. The directory should then contain subdirectories with package numbers.
Open the dialog 'Local Package Manager' via the menu ribbon in DataManagement.
In the 'Local package directory' field, enter the path to the directory you just created with the downloaded packages.
Finally, under 'Packages to be installed', enter the numbers of the packages that you want to install. If you want to specify several package numbers, separate them with a comma.
You can use the optional installation of the demo data of these packages via 'Import demo data with'.
Carry out the installation by clicking on the 'Import packages' button.

Offline Installation with PowerShell

If you want to use Microsoft PowerShell for offline package installation, transfer the downloaded packages to a directory on the waveware server and carry out the following steps.

Log into your account of the waveware Service Center from any other device and download the packages to be installed as described under 'Install Packages Offline' (steps 1.-5.).
Create a directory on the waveware server into which you unzip the content of the downloaded file 'package.zip'. The directory should then contain subdirectories with package numbers.
Open the DataManagement, deactivate the data world in which you want to install and then click in the 'Tools' menu on 'DataManagement Powershell'.
Then enter the following lines to register variables for login. Replace %PASSWORD% with the password of the DataManagement administrator:

$user="Administrator"
$password=ConvertTo-SecureString -String "%PASSWORT%" -AsPlainText -Force
$credential=New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $user,$password

With the help of the previous commands '$credential' was created as a secure object that contains the login data and can be used for login. Now create variables for the data world ($installid) to be installed, for the package ($package) to be installed and for the local directory ($repopath) in which the previously downloaded package is located Files are located. Replace the information in the following example:

$installid="waveware"
$package="112"
$repopath="C:\OfflinePakete"

5. Then use the following command to run the package installation:

Import-WavePackage -InstallId $installid -Server localhost -DatamanagementCredential $credential -PackagesToInstall $package -Address $repopath -ForceLogin

Extend the last command with "-verbose" and repeat it in order to receive detailed information in the event of an error.

Messages

Below, the systematic messages and recommendations, which occur are listed.

Critical Error Messages

These errors stop the whole process.

Message	Recommendations
There is no package folder in the selected directory.	Switch the path to the package repository in the server settings and select a directory where a package exists.
The tables cannot be correctly assigned to the new DefDb.	The tables for the new DEF files cannot be adopted in the database. At this point, your database is unchanged.
When copying the DefDb an error has occurred.	Copying can be failed based on various grounds, for example if the directory is blocked. At this point, the database was already changed! Please restore a backup and try to remove the cause of the error message.
When updating the delta files an error has occurred.	See „When copying the DefDb an error has occurred“.
The creation of the folder and files in the package folder has failed.	Copying can be failed based on various grounds, for example if the directory is blocked. At this point, the database was already changed! Please restore a backup and try to remove the cause of the error message.
The creation of the sub-folder and its files in the package folder has failed.	See „The creation of the folder and files in the package folder has failed“.
The package could not be copied in the data directory.	See „The creation of the folder and files in the package folder has failed“.

Error Messages

These errors abort only the the import/update of the single package.

Message	Recommendations
No package can be updated.	You have either selected no package or only the packages, which cannot be updated. Please, check the further error messages in the HTML file.
No DefDb file was found with the table number (0) or they were not Licensed through the license file (OPP). The process is canceled.	This package expects a particular table and wants to extend it for example through a new field. Check with the Designer, whether the table overall exists. If you do not need this package, it brings along this table or you have deleted the table. If the table is shown canceled, it must be licensed through the license file or in the case of the transactions or catalogs, it must be inserted at the designated place. The package cannot be installed or updated without this table.
There is already a DefDb file with the number (0). The process is canceled.	This package brings along a table, which is already available in the system. It is not permissible, as a table must always belong maximum to one package. As a package is not installable for several times, there is a problem. Please, contact the support.
No DefDb file was found with the table number (0) or they were not Licensed through the license file (OPP). The process is canceled.	See message: "No DefDb file was found with the table number (0) or they were not Licensed through the license file (OPP). The process is canceled."
The DefDb file (0) was ignored, as it cannot be deserialized.	The package brings along a corrupt DefDb file. Please, contact the support.
The DEF View file (0) was ignored, as it cannot be deserialized.	The package brings along a corrupt DEF View file. Please, contact the support.
There is already a DEF View file with the number (0). The process is canceled.	This package brings along a table, which is already available in the system. It is not permissible as a table must always belong maximum to one package. As a package is not installable for several times, there is a problem. Please, contact the support.
A field already exists, to which the hierarchy (0) is assigned. Two fields with identically assigned hierarchy cannot be in one table. Fid (1), Field type (2) (Table (3) – (4)).	This package brings along a hierarchical field for a particular table. Either a table was changed in the delivery or you have personally changed the hierarchical field. If you have changed the hierarchical field personally, you cannot import or update the package. Instead, you have an option to remove the hierarchy with the Designer and then import/update the package.
An attempt was made to import a field, which already exists with another field definition. FId: (0), field type (1) – new field type (2) (Table: (3) – (4)). The previous field definition is retained. The problem can be removed, if you delete the field or change the type of the field. Otherwise, you will lose your data!	A field of a particular type cannot be overwritten with another field definition, as it is probably used in rules. The package cannot be installed. You can adjust the field type with the Designer. Please, consider that when changing the field type the data is lost. If you change merely the Fid of the field, the data survive and can be imported in the new field after a successful installation per Multi (perhaps with adjustments). If you are not sure, contact the support.
An attempt was made to import a field, which already exists with another field definition. The field is however assigned to another catalog. FId: (0), catalog (1) – new catalog (2) (Table: (3) – (4)). The previous field definition is retained. The problem can be removed, if you delete the field or change the type of the field. Otherwise, you will lose your data!	A field to which a particular catalog is assigned, another catalog can be also assigned. It is the same procedure as in the previous message.
When merging the Delta DefDbs , an error has occurred. The process cannot be continued.	Delta files extend the DefDb files, they are integrated into the available file. During this process, an error has occurred. As nothing is processed in the data directory at this time, no changes were adopted.
A package cannot bring along a new DEF file and at the same time a Delta DEF file, which changes this DEF file.	The package is defected or was manually edited. Please, contact the support.
The package update cannot be implemented, as the following catalog is not Licensed: (0).	To be able to update this package. you must unlock the catalog or if it is visible in the Designer assign a field as a catalog. Unused catalogs behave as if they were not Licensed, because they do not exist only at a file level, but are available in waveware.
The package cannot be imported, as the following catalog is not Licensed: (0).	See „The package update cannot be implemented, as the following catalog is not Licensed: (0)“.
The package update cannot be implemented, as the catalog (0) does not contain the field (1) (2).	This package requires a particular field for the catalog. This is available in the delivery or relative packages and was perhaps removed by you. You can refrain from update or add the field with the Designer.
The package cannot be imported, as the catalog (0) does not contain the field (1) (2).	See „The package update cannot be implemented, as the catalog (0) does not contain the field (1) (2)“.
The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1).	Your Opp must be adjusted so that you can update this package. Please, contact your account manager or the support.
The package cannot be imported, as the transaction (0) is not Licensed for the catalog (1).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package update cannot be implemented, as the transaction (0) does not contain the field (1) (2).	See „The package update cannot be implemented, as the catalog (0) does not contain the field (1) (2)“.
The package cannot be imported, as the transaction (0) does not contain the field (1) (2).	See „The package update cannot be implemented, as the catalog (0) does not contain the field (1) (2)“.
The package update cannot be implemented, as the sub-transaction (0) is not Licensed for the transaction (1).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package cannot be imported, as the sub-transaction (0) is not Licensed for the transaction (1).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package update cannot be implemented, as the sub-transaction (0) does not contain the field (1) (2).	See „The package update cannot be implemented, as the catalog (0) does not contain the field (1) (2)“.
The package cannot be imported, as the sub-transaction (0) does not contain the field (1) (2).	See „The package update cannot be implemented, as the catalog (0) does not contain the field (1) (2)“.
The package update cannot be implemented, as the following object is not Licensed: (0).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package cannot be imported, as the following catalog is not Licensed: (0).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package update cannot be implemented, as the object (0) does not contain the field (1) (2).	See „The package update cannot be implemented, as the catalog (0) does not contain the field (1) (2)“.
The package cannot be imported, as the object (0) does not contain the field (1) (2).	See „The package update cannot be implemented, as the catalog (0) does not contain the field (1) (2)“.
The package update cannot be implemented, as the transaction (0) is not Licensed for the object (1).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package cannot be imported, as the transaction (0) is not Licensed for the object (1).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package update cannot be implemented, as the following transaction is not Licensed (0).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package cannot be imported, as the following transaction is not Licensed (0).	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package update cannot be implemented, as the sub-transaction (0) is not Licensed.	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The package cannot be imported, as the sub-transaction (0) is not Licensed.	See „The package update cannot be implemented, as the transaction (0) is not Licensed for the catalog (1)“.
The comparison of the DEF files could not be executed, as errors have occurred (0). The tables could not be correctly created for the new DefDbs.	The tables for the new DEF files could not adopted in the in the database. At this point, your database is unchenged. Please, check the error message and ask the support.
When merging the Delta DEF views, an error has occurred. The process cannot be continued.	Delta files extend DEF view files. They are integrated in the available file. An error has occurred during this process. As nothing is processed in the data directory at this point, the changes were not adopted.
The package could not be imported as the Import of the following related package has failed.	This package requires another package, which was not imported erroneously. Remove the error of the related package and then try the import of this package again.
The package was not Licensed through the Opp.	Packages can be installed only if you have them in your license file. Contact the support to prolong your license.
The version of the updateable package is higher or the same as the version of update. The update is not implemented.	You can always implement an update only to a newer version.
The package (0) cannot be updated, as the following necessary packages are not installed: (1).	A package, that requires other packages, which are neither available nor in the installation list, cannot be installed. Please, at first install the listed packages.
The package (0) cannot be imported, as the following necessary packages are not installed: (1).	See „The package (0) cannot be updated, as the following necessary packages are not installed: (1).“.
A folder with the package ID (0) already exists.	In your version, the folder is already available for the package, however the package was not normally installed. This version should not be used anymore. Please, contact the support.
You cannot update a package, which does not exist in your system.	A package should be updated. As it does not exist in your system, you can merely install a new one. This error message should not appear as long as you do not make manual changes in the data directory.
The package does not contain any valid configuration file.	The package that is to be imported or updated is defected. Please, contact the support.
The package has no valid waveware server version saved in the configuration file. Without a proper testing of the version, the package cannot be imported.	See „The package does not contain any valid configuration file“.
The system would be crested with this package, if it has a higher update status than your system. Package version (0), version of the system (1).	A package with a higher version number than your system, can perhaps include functionalities, which your system cannot process. Please, update at first your waveware system, then install the package again.
The package cannot be imported as the following package is excluded (0).	Some packages can run errorless, only if other packages are not available. For example, a cleaning package 1 and a cleaning package 2 bring along alike functionalities. The new package cannot be installed.
The package is excluded from the following package (0).	See „The package cannot be imported as the following package is excluded (0).“.
The configuration file of the package could not be fully loaded.	See „The package does not contain any valid configuration file“.
The DefDb file {0} could not be deserialized.	The package brings along a corrupt DefDb file. Please, contact the support.
The Delta DefDb file {0} could not be deserialized.	The package brings along a corrupt DefDb file. Please, contact the support.
No 500`s tables can be included in the packages. Please, contact the creator of the package or the support.	The tables in the area from 500 to 599 are created for the demo and test purposes. You cannot normally reach a package. Please, contact the creator of the package or in the case of the Loy & Hutz package contact the support.

Warning

Message	Recommendations
When updating the import components, errors have occurred.	This package brings along import components, which should be taken to your database. During this process, errors have occurred, as a result records are missing which are necessary for the Import. The package was yet installed. Please, contact the support.
When importing the import components, errors have occurred.	See „When updating the import components, errors have occurred“.
When importing selections, errors have occurred.	This package brings along selections, which should be taken to your database. During this process, errors have occurred, as a result records are missing which are necessary for the selection. The package was yet installed. Please, contact the support.
When importing selections, errors have occurred.	See „When importing selections, errors have occurred“.
When importing dashboards, errors have not occurred.	This package brings along dashboards, which should be taken to your database. During this process, errors have occurred, as a result records are missing which are necessary for the dashboards. The package was yet installed. Please, contact the support.
When updating the dashboards, errors have occurred.	See „When importing dashboards, errors have not occurred“.
Data for the table (0) could not be imported, as it is not Licensed.	See „Data for the table (0) could not be imported, as this table does not exist in the DB“.
The Dump file (0) is not correct.	The file that brings along data, is defected! Please, contact the support.
The data could not be correctly imported.	This package brings along data which could not be taken to your database.
Error has occurred, when copying images for objects/catalogs and transactions.	This package brings along images which should be displayed in the ribbon of waveware. For that, these images are specially copied into the system image directory. If errors occur when copying, you can even copy the images from the package in the system rule editor, in the system package.
The category for this package could not be found. Please, ensure that the name of the category does not have additional character (dots are not allowed as well).	The package brings along a path, in which a package should reside in the package tree of the system rule editor. For example, „Module.FM“. path of this package was buggy, so the package was inserted under system. You can move it really easily.
Package structure could not be saved.	The package structure is responsible for the display of the package in the system rule editors. If it could not be saved, that is your new package is not included in this structure. You can yet add it. For that, please open the system rule editors, select a yellow category folder, and choose „Add new package“ in the context menu, and press the Ctrl button meanwhile. A small dialog should appear, where you can enter the number of the package. Then, the package should come up in the package tree and it can be normally used.
Following lines of the table {1} could not be imported: {0}.	This line is erroneous in the Dump file and could not be imported. This message refers only to this message, and each further available line is tried to be imported.

Hints

Message	Recommendations
Following card areas are added as invisible card areas through the update for the table (0): (1).	There are new card areas for this table through the update, that are not available in your system. They are visible only with the Designer now, but you can make the areas visible through a property in the card.
Following areas for CustomPages are added through the update for the table (0): (1).	There are new CustomPage areas for this tables through the update, which are not available in your system. They were added.
Following CAD ranges are added for the table (0) through the update.	There are new CAD areas for this tables through the update, which are not available in your system. They were added. Now you can use the new CAD ranges.
The following record should be updated, but it is not possible, as it is already altered.	When first installing a package, data were transferred to your database for the particular tables. You have adjusted these records, so it is not possible to transfer updated values.
The image (0) already exists and is not overwritten.	The package brings along an image, that already exists in your system. Available files are not overwritten. It is merely a hint.
When executing the update for new packages, errors have occurred.	When executing the update for new packages, errors have occurred.
The ribbon file from the package (0) could not be read. All the changes can be also added manually with the Designer.	If a package brings along new tables, the ribbon can also be adjusted. This file is defective. You can adjust the ribbon with the Designer and acquire new tables.
The rule (0) was changed in the system version, but you still work with your own file. (Your changes are not overwritten through the update).	A system rule was changed in the package version. This rule was overwritten. Your own changes really survive in the user rule. If you want to compare the rules, you can rename the user rule, then the system rule appears. After the comparison, you should change the name of the user rule to its original name, and then the system rule appears again.
The image (0) was changed in the delivery. As you have changed the image, you still work with your own image.	In the package version, an available image was replaced. As you have adjusted it on your own, your changes are not overwritten.
The web file (0) was changed in the delivery. As this file was changed by you, you still work with your own file (Your changes were not overwritten).	See „The image (0) was changed in the delivery. As you have changed the image, you still work with your own image.“
The resource (0) was changed in the delivery. As you have changed this file, you still work with your own file (your changes are not overwritten through the update).	See „The image (0) was changed in the delivery. As you have changed the image, you still work with your own image.“
Data for the table (0) could not be imported as this table does not exist in the DB.	This package brings along data for a table, which does not exist in your system. This is, for example the case when a catalog is almost available but is not used. As long as the table is created or is licensed through the Opp, the data are automatically installed later.

Update Packages

You can find whether updates are available for a package in the package manager in the column 'Install state'. Here "Update available" is shown with the previous version:

Note that a particular waveware server version is required for the particular update. No package update can be implemented, when your installed waveware version is lower than the one specified here.

Activate the button with the plus symbol in front of the package line to update a specific package. With the 'ALL UPDATES' button you automatically mark all packages for which there is an update. Then click the button with the triangle symbol to start the process, see 'Install Packages'.

During a package update, an old package is completely deleted. Only user rules and resources are kept. The package with the higher version number is completely installed again.

As only user rules survive, the rules which were created or changed with the license right 'Package Developer' (Systemscripter), are backuped or converted into user rules, in the case they are to survive.

Install Packages

After installation of the package you get an HTML file with the name 'wavewarePackageManager%Date&Time%.html', which is located in your temp directory in the folder 'LoyHutz'. It is directly opened after completing the process and contains all the occurred errors, warnings and notes.

The button 'Save the last log file' allows to export all generated log files of the package manager of the current session. Select a directory, where the log files are to be saved.

Uninstall Packages

Once installed, you can also remove packages again using the package manager.

To do this you need access to the waveware Service Center, otherwise uninstall via the local package manager.

In the listing, click the white cross on blue button for the package you want to remove.

If other installed packages depend on the package you want to uninstall, you will receive an error message later. Therefore, first remove the packages that work with the package to be deleted and only then continue at this point.

Note, that the data, which were saved in the delivered tables, are also removed. Create preferably a full backup before you continue.

Confirm the following security message with 'Yes'.

At the end, another message asks, whether delivered data should be removed. This can be selections for the Data Selection, Import, and Export components or catalog or Demo data. If you are sure, that you do not want to use these data anymore, click 'Remove data'. 'Retain data' leaves these components in the system.

During the uninstalling process, only the package folder with all assigned functionalities (rules, resources and if selected, the components brought along) is removed. Changes on the data structure, which are executed during package installation, cannot be undone anymore. Tables, which the package has once brought along, survive and must be removed manually with the help of the Designer. The fields of a package, which remain in the database, behave as if they are manually inserted. However, they are not exported with another package.

The end of the uninstalling is subsequently acknowledged with a message.

Uninstall Packages Offline

If there is no access to the waveware Service Center, e.g. because there is no internet connection, you can also uninstall packages locally from waveware 11.200.4928.

Open the 'Local Package Manager' dialog via the ribbon in DataManagement.
From the list of installed packages, select the packages you want to remove; e.g. 111 (medical equipment) and 112 (Equipment management). If necessary, enable filters in the table header to make entries easier to find.
Click 'Remove Selected Packages' to delete the selected packages.

Package Manager

5 Changes

32 Views