Auto-configuration

This section walks you through integrating Atoti Limits with an Atoti Server via auto-configuration. This feature was introduced in V1.1.0.

Auto-configuration

As per the Manual Configuration, the following properties are required to enable Atoti Limits to connect to an already running Atoti Server:

• limits.connected-server.url.map
• limits.connected-server.as-of-date.map
• limits.connected-server.auth.map
• limits.rest-url
• limits.auth
• content.server.url
• content.server.auth

Some of these properties can be auto-configured at runtime by the Atoti Server. Here’s how to do this:

1. Import ‘LimitsAutoConfig’ into the Atoti Server

Maven dependency:

  <dependency>
    <groupId>com.activeviam.limits</groupId>
    <artifactId>limits-auto-config-{AP VERSION}</artifactId>
    <version>{LIMIT MODULE VERSION}</version>
  </dependency>

Currently, auto-configuration is available for the following Atoti Server versions:

Java import:

import org.springframework.context.annotation.Import;
import com.activeviam.limits.autoconfig.impl.LimitsAutoConfig;

@Import( LimitsAutoConfig.class )
public class ActivePivotApplication {
	// Spring App
}

2. Start the Limits server

Start the Limits server using the installation instructions. Limits will wait for a connection from the Atoti Server.

3. Start the Atoti Server with the following properties

One of each of the following two sets of properties are required (i.e. either 1a or 1b and either 2a or 2b) . The first takes precedence over the second (a takes precedence over b). Note that a org.springframework.security.core.userdetails.UserDetailsService must be defined for the username options to work.

The following properties can be provided but are optional:

You are connected!

Your Atoti Server should now resolve and register the correct LookUpPostProcessor (depending on the Atoti Server version being used), auto-configure the properties required by Atoti Limits, send these properties to the Limits server at limits.rest-url and the module will connect to your Atoti Server.

Startup sequence does not matter

The auto-configuration does not care if your Atoti Server or your Limits server is up first. As long as limits.connection.attempts has not been reached, your Atoti Server will continuously try to send information to the module.

Auto-configuration properties

The following optional properties can be used to start the Atoti Server in the event that the server cannot auto-configure the properties.

Note that the auto-configuration can be disabled by setting the following property to false.