Configuring the server settings

The file attachment, file storage configuration, and logging configuration settings affect the entire FootPrints system.

To configure the server settings

  1. Select the Administration tab.
  2. In the System Management section, select System Settings > Server Configuration.
  3. In the Server Configuration page, in the File Attachments section perform the following steps:
    1. Enter the Maximum size of each attachment.
      The system does not allow users to attach files in the interface or via email that are larger than the specified size across all containers for all types of records. The Maximum Size of Attachment Directory is currently a deprecated setting.
    2. In the Excluded attachment file names and extensions (1 per line) field, enter the file extensions or file names.
      • If you are installing FootPrints for the first time, this field includes a list of default file extensions. You can add or remove file extensions or file names from the existing list.
        For example, if you add image.png file name in the excluded list, users cannot add files with names simage.png, image.png.jpg, and so on. 

         Click here to see the default list of excluded file extensions
        .cla   .fxp.its.maq.mde.mshxml.plg.reg.vbp
      • If you upgrade to the current version of FootPrints, enter the file extensions or file names that you want to restrict users from attaching to the records. 
    3. (For FootPrints and LDAP authentication only) In the Base URL field, enter the URL that will be used for external communications that provide links back to the system.
      This setting includes links to Ticket details in emails, links to survey emails, and links to auto run reports.
      For example, http://<domain>:8080/footprints/servicedesk.
    4. (For Web server authentication only) In the Web Server Authentication Base URL field, enter the URL of the preconfigured web server.
      The default value of this field is the same as base URL.
  4. In the File Storage Configuration section, in the Path to the Repository field, type the location of the repository.
    This location is where record attachments are stored. For more information, see Changing the location of the file attachments directory.
  5. (Optional) In the Logging Configuration section, perform the following steps:
    1. To change the level of logging, select Enable Custom Logging Configuration.
      Additional fields appear.
    2. To send the client-side errors to the server, select Send browser errors to the server log.
      These errors get logged in the footprints.log application log file.


      Send browser errors to the server log is a global setting. This setting affects all the application clients.

      BMC recommends that you use this option with caution, such as only for troubleshooting, because it leads to additional network traffic.

    3. In the Logging Level field, select the level of events that you want tracked in the log.
      The default setting is Warnings, which is the lowest level. Selecting either Debug or Trace (the two highest levels) can significantly impact system performance because of the amount of data that is recorded.
    4. In the Package Filter field, enter the name of the FootPrints package that will be tracked.
      The package must be located under the "com.numarasoftware.footprints" base package.
  6. Click Save.

To retrieve application logs

  1. Select the Administration tab.
  2. In the System Management section, select System Settings > Server Configuration.
  3. Perform one of the following actions: 
    • To download the application log, click Download application log.
    • To download all logs, click Download all logs.


The downloaded logs are saved in the default Downloads folder. 

Related topics


Browsing audit trail logs

Was this page helpful? Yes No Submitting... Thank you