Installation Best Practices

The following are best practices when you are installing 
Layer7 Live API Creator
.
lac52
We recommend the following best practices when you are installing 
Layer7 Live API Creator
:
  • Installing 
    Layer7 Live API Creator
     involves installing API Server. When installing API Server to run as an on-premise service or as a cloud-based service, we recommend:
    • As many CPUs as required for peak load. API Server takes advantage of all available CPUs.
    • A minimum of 512 MB of heap and a maximum of 4 to 8 GB per Java container. If you have extra RAM, consider using several Java containers.
      For more information about heap size configuration, see Installation Requirements and Supported Platforms.
    • A few GB of available disk space for log files.
  • When installing 
    Layer7 Live API Creator
     to run as an on-premise service, work with your infrastructure teams to secure the application server according to the vendor's best practices, in particular:
    • Reset default passwords.
    • Remove unnecessary example applications.
    • Close unnecessary open ports.
  • When installing 
    Layer7 Live API Creator
     to run as a cloud-based service, minimize the server exposure to any vulnerabilities within the environment by setting up the appropriate security groups. For example, if you are installing 
    Layer7 Live API Creator
     to run as a cloud-based service in an Amazon Web Services (AWS) Elastic Beanstalk environment, follow the best practices that are outlined in the AWS documentation.
  • Minimize the round-trip trip time to your databases by installing 
    Layer7 Live API Creator
     close to the database. Ideally, the ping time between API Server and the database server should be less than one millisecond. You can test the ping time using API Creator.
    For more information about how to test the connection to your database, see Database Connectivity.
  • When running 
    Layer7 Live API Creator
     in a production environment:
    • Consider preventing API Server from writing to disk the changes that you make to the admin repository by adding the 
      LAC_REPOSITORY_DISABLE
       option when you start API Server and setting it to 
      false
      .
      For more information about this option, see API Server Startup Options
    • Minimize in-memory usage and optimize your server performance by completing the following:
      • 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, 
        Layer7 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.
      • Configure external logging. For more information about how to configure external logging, see External Logging.
      • Review the security protocol requirements for the services that you host on 
        Layer7 Live API Creator
        . Minimize your services' exposure to security vulnerabilities.
        For more information about how to minimize exposure to these vulnerabilities, see Restrict the Use of Cryptographic Algorithms and Protocols.
    • Configure monitoring services for 
      Layer7 Live API Creator
       server health using the 
      @heartbeat
       system REST endpoint.
      For more information about this endpoint, see System REST Endpoints.
For a list of all best practices, see Best Practices.