Configure BeyondInsight for Unix & Linux

  1. You can customize the console using the pbsmc.toml.default file located in:
    • Linux: /etc/pbsmc
    • Windows: %ProgramFiles%\PBSMC
  1. Create a copy of the file using the name pbsmc.toml. You can include only the settings that you want to customize.
  1. Be sure to include the section title in pbsmc.toml. For example, if you want to change the default port number, the text will look similar to the following:
[server]
port="4443"

Apply proper security settings on the .toml file. The file owner requires Read and Write privileges.

  1. You can configure the following settings:
    • SSL: By default, the console supports encrypted HTTPS connections using automatically generated, self-signed certificates. The console serves only HTTPS traffic on the configured port, unless explicitly configured to fall back to insecure HTTPS in the pbsmc.html configuration file. A custom certificate pair may also be provided and placed in the configuration file.
    • Port: By default, the console runs on port 4443. Before changing this value, stop the service.
    • Database: By default, the console creates a SQLite database in /atc/pbsmc/pbsmc.sqlite or in %ProgramFiles%\pbsmc on Windows. This can be changed to another location.
    • Pool: Console tasks are run in a concurrent pool of processes. The default number of processes running at a time is 20. You can increase the pool size to allow jobs to complete faster. However, the server performance might lag, and decreasing the pool size will have the opposite affect.
    • keys: Encryption keys for BIUL use base64 encoded AES 256 encryption. The key secures sensitive data stored in the database. More than one key can be used at a time. The Active key in the pbsmc.toml file is the key currently in use. If you start BeyondInsight for Unix & Linux without an encryption key, one is generated for you. You can review the comments in the pbsmc.toml.default file.

You must restart the service to apply changes.