||Detailed installation log|
||Delta Control log|
||A log file will be created for each process instance or task executed
||Tomcat application log file, redirected console output|
||Appserver application log file|
Package not being picked up by installer
The installation scripts contain a set of known packages to install, e.g. core Platform packages.
If you have created a custom package, configure your
install.config file to tell the installer how to handle your package.
See Package List Options for more details.
Failed to install package
The install configuration profile of each package can define a list of packages which the package depends on to function. This installation script will check that these packages are installed. If this check fails the install script will exit with a failure.
grep DEP install_config/profiles/DeltaStream.install.config DEP|DeltaControl
Above we see that to install the DeltaStream package, the DeltaControl package is required.
If the configuration profile does not contain the correct dependencies, the installer will try to install the packages. It is possible to have a failure during the import of the packages to Control.
auto import failed to start see DeltaControl.log for more info
This will happen if there are entities that depend on other entities which are not available yet. To solve this issue:
DEPto install config profile to catch possible issues earlier in the installation process.
- If you are using Package List Options ensure the package order is correct.
Port changing during installation
The installation script has in-built logic to prevent an installation trying to use a port which is already in use on the server. Due to this, it is possible that the install script will not use the port specified during the installation or in the
install.config file, but the next available free port.
[TOMCAT_PORT] Port  in use Using port 
If this is not the expected behavior, you should ensure there is nothing running on port
8080 before performing the installation.