Configuration Best Practices

The following are the best practices that we recommend when you are configuring 
CA Live API Creator
.
lac52
We recommend the following best practices when you are configuring 
CA Live API Creator
:
2
Cluster Configuration
  • Consider configuring 
    CA Live API Creator
     to run as a cluster of nodes:
    • To provide high availability of services.
    • To support failover if there are hardware failures.
    • If you expect 
      CA Live API Creator
       to handle large numbers of incoming requests.
    For more information about how to configure 
    CA Live API Creator
     to run as a cluster, see Configure to Run as a Cluster.
  • When configuring Hazelcast for cluster synchronization strategy, if reliability is more important than performance or if you are configuring 
    CA Live API Creator
     to run in an unstable cluster or in a cluster that changes in size frequently, add the 
    LAC_CLUSTER_SYNC_STRATEGY
     option when you start API Server with the 
    in_memory_with_locking
     property value.
    For more information about this option, see Configure to Run as a Cluster.
Memory & Heap Size Configuration
Repository & Backup Configurations
If your server is for development, disable backups in runtime mode where you have APIs deployed to these environments as part of your CI/CD process. Disable backups by adding the 
LAC_REPOSITORY_BACKUP
 option when you start API Server and set the value to 
false
.
For more information about this option, see API Server Startup Options.
Logging Configurations
  • Persist your 
    CA Live API Creator
     log messages by creating a logger for externalizing your API logs, listener logs, and timer logs.
    For more information about how to configure external logging, see External Logging.
  • Set up log levels that are appropriate for your environments.
    For more information about how to configure logging levels, see View Logging Information.
  • If you have configured 
    CA Live API Creator
     to collect and send telemetry data, or usage data, configure the 
    lactelemetrylogger
     logger to capture the activities for sending usage data.
    For more information about how to configure this logger, see External Logging.
  • In production environments, minimize in-memory usage and optimize your server performance by completing the following:
    1. Turn off in-memory logging at the API Server level by adding the 
      LAC_USE_IN_MEMORY_LOGGING
       option when you start API Server and setting it to 
      false
      . By default, 
      CA Live API Creator
       determines whether to display the in-memory logs based on the API level setting for displaying in-memory logs (the 
      Enable In-Memory Logs
       checkbox on the Settings tab) (the value for this option is 
      true
      ).
      For more information about this option, see API Server Startup Options.
    2. Configure external logging.
Configuration Considerations
Determine whether you require a database for persisting your authentication tokens.
For a list of all best practices, see Best Practices.