Skip to content

Post Installation Follow-up

After deployment of IFS Cloud database objects, the output log files should be analyzed. The most important ones are listed below. Which of the log files that are written in a deployment is depending on the content of the installation, i.e. not all of the logs are generated in every deployment.

The logs from database deployment are gathered in a subfolder called database suffixed with a timestamp, e.g. database_20200907_010059 in the logFileLocation. If logFileLocation not defined in the customer yaml file, nor sent as --set parameter to the installer, the default location for the logs are in the OS temp folder, e.g. windows %TEMP%/ifsinstaller_<namespace>.

File Comment
_deploy.log All output from the main thread
_ERROR_*.log List all deployment errors. Code might need to be corrected and re-deployed
_biservices.log Overview deployment information of BI services installation files
_convert_lob.log List all converted LOB columns into secure files
_enable_rowkey.log List of all entities where rowkeys are enabled
_grant_*.log Grants to a specific role or system
_triggers.log During deployment, all triggers are temporary disabled and at the end enabled again
_installtem.log Main actions from deployment of the install.tem file
_LicenseImpact.log Presentation objects modified in the delivery that are included in LTU license permission sets. Additional grants to database methods or database views can be done without requiring a new license
_PostData.log Overview deployment information of Post Data installation files
_PostObject.log Overview deployment information of Post Object installation files
_pres_object_changes.log New and modified presentation objects in the delivery. The security grants must be updated accordingly
<component>*.log E.g. Fndbas.log, Accrul_biservices.log. Detailed information about one component.

Interrupted Database Deployment

During the database deployment, background jobs are turned off and triggers are disabled. If the deployment is interrupted by any reason, the installer will revert these settings the next time a database deployment is executed.

However, if you want to reset these settings directly and not wait for the next deployment you can do this by running this piece of code logged on to the database as application owner: