We use cookies and other technologies on our website. They help us to improve our documentation and your experience. You can find more information about the use of your data in our privacy policy. There is no obligation to consent to the processing of your data in order to use our documentation. View our Privacy Policy
Log files and others can take a considerable amount of disk space. As of Bridge 7.6.0, the Bridge supports you by automatically deleting log and service backup files that are older than a threshold (see Node Instance Preferences). Some files, however, still need to be deleted manually.
List of Files You Can Safely Delete
System Files of Old Installations In your Bridge program folder, you may find folders containing old installations of
xUML Runtime, e.g. bridgeserver-2019.1
Apache, e.g. apache-2.2.29
Tomcat, e.g. tomcat-9.0.12
Node.js, e.g. nodejs-8.9.1
Java, e.g. j2re-1.8.152
These folders can safely be deleted, if you do not have any services up and running that use them.
You can see the versions of the installed software on the Runtime tab of your Bridge. See Managing the xUML Runtime of the Node Instance for more information on this. Alternatively, you can look into <your Bridge program folder>/console.properties, where you can find entries for all used software versions.
File Clean-up on Bridges Before Version 7.6.0
From time to time, you should clean-up the Bridge files and delete old files you do not need anymore.
Before 7.6.0
List of Files You Can Safely Delete
Bridge Log Files
Bridge log files can be deleted at any time. Current log files may be locked by services. If you delete a log file of the current day, the Bridge will create a new one and continue logging to the new file.
The following log files can be deleted without effecting the system:
all xUML service and Node.js service logs from <your bridge data directory>/<service directory>/logs
all Bridge access and error logs from <your bridge data directory>/servlets/logs/admin
all proxy logs from <your bridge data directory>/proxies/logs
Service Backup Files On every service deployment, the Bridge creates a service export of the old service as a backup to folder <your Bridge data directory>/backup.
System Files of Old Installations In your Bridge program folder, you may find folders containing old installations of
xUML Runtime, e.g. bridgeserver-2019.1
Apache, e.g. apache-2.2.29
Tomcat, e.g. tomcat-9.0.12
Node.js, e.g. nodejs-8.9.1
Java, e.g. j2re-1.8.152
These folders can safely be deleted, if you do not have any services up and running that use them.
You can see the versions of the installed software on the Runtime tab of your Bridge. See Managing the xUML Runtime of the Node Instance for more information on this. Alternatively, you can look into <your Bridge program folder>/console.properties, where you can find entries for all used software versions.
Purge Files on Linux
To clean-up Bridge log files and service backup files on Linux, you can use shell script purge.sh. The script resides in <your Bridge program directory>/bin/.
Usage:
BASH
[DAYS=<a number of days>] <your bridge program directory>/bin/purge.sh [remove|dryrun]
Parameters:
Parameter
Description
Output
remove
Remove log files from disk that are older than a given period of time. Default is 7 days.
Removed the following log files because they were older than 7 days:
/opt/e2e_bridge_data/bridge_SAP_PurchaseOrder/logs/transaction_2019-03-22.log
dryrun
Show which files are older than the given period of time and can be deleted. Default is 7 days.
List of log files that would be removed because they are older than 7 days: /opt/e2e_bridge_data/bridge_SAP_PurchaseOrder/logs/transaction_2019-03-22.log
By setting the environment variable DAYS, you can define the period of time to be considered.