To Change the application log directory
Environment: Windows
Notes:
- This kb is not recommended.
- The support file (Community -> Troubleshoot -> Support File) will be generated with log files which are generated using the bat files. The new logs, generated in changed log directory won't be listed here.
- In View logs (Community -> Troubleshoot -> View Logs) the new logs won't be listed, the logs which are generated using the bat files only listed. The new logs, generated in changed log directory won't be listed here.
- Example restore logs, backup logs which is generated by executing the restoreData.bat file and backUpData.bat file respectively.
- The following bat and jar file is not SPD Version specific. Hence it can be run in any builds.
- The LogDirectoryChanger.bat file need to be executed after every successful SDP Upgrade.
- However we will take one copy of logging.properties named logging_old.properties before modifying the original file. But the logging.properties file which is in application_installed_directory\conf\ can be copied (not moved) to some other disk in order to ensure the original file is there for recovery process.
- Some of the log file directory could not be changed. Example restore logs, backup logs which is generated by executing the backUpData.bat file.
Steps:
Step 1: Extract the following zip file.
Step 2: Shutdown the application
Step 3: Navigate to the application_installed_directory\lib\ and place the LogDirectoryChanger.jar file
Step 4: Navigate to the application_installed_directory\bin\ and place the LogDirectoryChanger.bat file, open command prompt and execute the LogDirectoryChanger.bat file
Step 5: Enter the full path of the log directory where the logs need to be logged.
Step 6: After the successful execution of bat file, kindly start the server once and ensure, the new log files are generated in configured directory.
New to ADSelfService Plus?
Related Articles
How to change the database from MySQL/PostgreSQL to MSSQL
The steps mentioned below are applicable only if you migrate the DB from PgSQL to MSSQL. This means that the application server is going to remain the same. The data alone is going to be transferred to MSSQL DB from the existing PgSQL DB. For ...How to assign CAB members to a change request automatically.
Note: Attached script will not work beyond 11138 SDP Version. This is a sample script to add CAB Members to a Change Request through Change Custom Triggers.The CAB Members can only be added manually to the Change Request ,under the Approval Tab, ...How to automatically assign users to different roles in a change request.
This script is applicable only for builds prior to 11138. This is a sample python script to read the value in the Change Owner field, when a Change Request is created and set him/her as the Change Implementer automatically, using Change Custom ...Close change requests using custom schedules.
This post describes the use of a python script to close change that are in a specific stage using Custom Schedules. Use Case: There may be a scenario where number of old Change Requests that have gotten lost in the shuffle over the years. Most of ...AppManager Integration - Create downtime schedule in AppManager from a change request in ServiceDesk Plus.
This script will invoke the AppManger api to set downtime of monitor and monitor groups using the schedule time and an additional field value chosen in a change request in ServiceDesk Plus. Execution steps: 1. Download and copy the script and xml ...