Welcome
Troubleshooting and support
Learn how to troubleshoot some common issues with HCL Launch.
Logging
The server maintains logs for auditing and troubleshooting.
Creating a rotating audit log file
You can create rotating audit log file at a regular interval, such as every day.

Welcome
Welcome to the HCL Launch 7.2.0 documentation, where you can find information about how to install, maintain, and use HCL Launch.
Release information
Overview
This section provides overview and getting started information.
Learning
Tutorials and instructions for all experience levels.
Installing
An HCL Launch installation consists of the HCL Launch server, a database, and at least one agent.
Upgrading and migrating
Learn how to upgrade HCL Launch elements, including the server, agents, and how to migrate data.
Uninstalling
Learn how to uninstall an HCL Launch server, or agent.
Integrating
HCL Launch supports integrations with other IBM® products, products from others, and certain cloud systems.
Administering
Learn how to administer settings in HCL Launch elements and communication between the elements.
Managing security
HCL Launch uses a flexible team-based and role-based security model that maps to your organizational structure.
Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Deploying
Learn how to deploy applications in HCL Launch.
Reporting
provides several different deployment and security reports.
Extending product function
Learn how to extend the function of HCL Launch.
Troubleshooting and support
Learn how to troubleshoot some common issues with HCL Launch.
- Troubleshooting process overview
  Troubleshooting is the process of finding and eliminating the cause of a problem. When you have a problem with HCL Launch, the troubleshooting process begins as soon as you ask yourself what happened.
- Logging
  The server maintains logs for auditing and troubleshooting.
  - Viewing logs
    You can view logs from the Settings > System page.
  - Changing the server output log contents
    The server stores its log by using Apache Log4j version 1.2.16. You can edit the Log4j settings to change the format of the log and the information that is added to the log.
  - Creating a rotating audit log file
    You can create rotating audit log file at a regular interval, such as every day.
  - Increasing the size of the log file
    Log data contains information that is written by components within the product. The log provides a snapshot of the flow and transfer of information between components. The log data includes the time frames for when problem occurred on the server, client, and agent. Because the log file holds a limited amount of data, data related to a problem can be overwritten.
  - Determining the Java heap memory size
    The Java heap is memory that contains objects used by Java programs. It contains objects that are currently in use, objects that are no longer needed, and free memory. Objects that are no longer needed are freed by the garbage collection process. The JVM heap size determines how often to run garbage collection and how long the garbage collection runs.
- Troubleshooting the HCL Launch server and agents
  Troubleshooting information that is specific to the server and agents is provided here.

Creating a rotating audit log file

You can create rotating audit log file at a regular interval, such as every day.

About this task

You can create a rotating audit log file by adding the audit-log-to-file appenders to the log4j.properties. Starting with 7.0.1.1, you can find the appenders in the log4j.properties file. Go to Settings > Logging, and uncomment the respective appenders.

The following code fragment shows the audit-log-to-file appenders to be used to create a rotating audit log file:

log4j.appender.audit-log-to-file=org.apache.log4j.DailyRollingFileAppender
log4j.appender.audit-log-to-file.File=../var/log/audit.log
log4j.appender.audit-log-to-file.MaxFileSize=100MB
log4j.appender.audit-log-to-file.DatePattern='.'yyyy-MM-dd
log4j.appender.audit-log-to-file.layout=org.apache.log4j.PatternLayout
log4j.appender.audit-log-to-file.layout.ConversionPattern=%m%n
log4j.logger.AuditLog=DEBUG, audit-log-to-file
log4j.additivity.AuditLog=false

Procedure

Edit the log4j.properties file.
Use a text editor to edit the file. You can also access the file by clicking Settings > Logging.
Modify the appenders.
Restart the server.
Verify the logs generating in the /var/log/audit.log file.

What to do next

This feature works especially well with audit log cleanup enabled. Go to Settings > System > Audit Log > Audit Log settings > Enable Audit Log Cleanup to enable audit log cleanup. Additionally, configure your audit log settings from the Server settings as required.