Service configuration files

Applies to AnyLogic Cloud 2.8.0. Last modified on May 19, 2026.

These configuration files are located in the controller data directory. By default, their location is as follows:

/home/alcadm/alc/controller/conf

Each of these files can be used by multiple service components.

Starting with version 2.8.0, the service configuration files were converted to YAML format. Each file is prefixed with the name of the configuration, so when fetched by the configuration server, it will be bound to a bean automatically. Previously, prefixing was done by the fetch config from controller mechanism.

The balancer service component uses this file. It holds RabbitMQ queues consisting of model run tasks — these tasks are submitted to the executor service components.

Within the balancer file, you configure the queue rules. In addition, this file defines the number of attempts to assign the task that the balancer component will make before dropping the task.

{
  "minAvailableTasksThreshold": 0, // Not used in Private Cloud.
  "rebalanceDelay": 5000, // The delay for rejected tasks, in milliseconds.
  "maxRejectAttempts": 5000, // The number of attempts to rebalance the task before it is rejected.
  "mostLoadedFirst": true, // The balancing strategy. If true, the balancer component will attempt to execute the model run task on the most loaded node. If false, it will use the least loaded node.
  "executorRequestTimeout": 2000, // The request timeout for communicating with executors, in milliseconds.
  "executorConnectionTimeout": 2000 // The connection timeout for communicating with executors, in milliseconds.
}

balancer:
  minAvailableTasksThreshold: 0 # Not used in Private Cloud.
  rebalanceDelay: 5000 # The delay for rejected tasks, in milliseconds.
  maxRejectAttempts: 5000 # The number of attempts to rebalance the task before it is rejected.
  mostLoadedFirst: true # The balancing strategy. If true, the balancer component will attempt to execute the model run task on the most loaded node. If false, it will use the least loaded node.
  executorRequestTimeout: 2000 # The request timeout for communicating with executors, in milliseconds.
  executorConnectionTimeout: 2000 # The connection timeout for communicating with executors, in milliseconds.

This file contains the configuration of the email server. For Cloud to send email notifications, you need to configure the SMTP relay server there.

Keep in mind the following requirements:

• Cloud supports only the SMTP relay servers that do not require authorization
• Only port 25 is supported for communication with the SMTP server

{
      "smtpServer": "192.168.0.4", // The IP address or FQDN of an SMTP server.
      "supportMailbox": "support@acme.com", // The email address to receive support requests messages.
      "internalNotificationsMailbox": "no-reply@acme.com" // The email address of a server administrator.
    }

email:
  smtpServer: "" # The IP address or FQDN of an SMTP server.
  supportMailbox: "" # The email address to receive support requests messages.
  internalNotificationsMailbox: "" # The email address of a server administrator.

To modify the templates of the emails automatically sent by the Private Cloud instance, go to the email-templates subdirectory of the controller folder and edit them there.

This file contains configuration options for the executor service component that runs the models.

Most of these options should not be changed. In the "userJVMArgs" field, specify the custom Java machine arguments that controller will execute when starting a model run in Private Cloud. If an argument is invalid, an error will occur when the model starts.

{
  "appsRootDir": "/opt/anylogic/", // The directory inside the executor container where the JAR file of the executor component is stored. Should not be edited in any way.
  "s3CacheDir": "/var/cache/executor/", // The directory inside the executor container where executor stores the JAR file of the model and its resources.
  "logsDir": "/var/log/executor/", // The directory inside the executor container where executor stores the model execution logs.
  "sessionsDir": "/var/run/executor/", // The directory inside the executor container where executor creates temporary environments for model execution.
  "sessionTimeout": "300", // The timeout, in seconds, for animation session activity. The executor component will stop animation sessions that are inactive for the specified period.
  "securityManagerEnabled": false, // Allows you to specify whether Private Cloud should use Java Security Manager. If true, models are launched in a sandbox, which may reduce execution speed by 2–3 times.
  "totalOutputFilesSizeLimitMB": 256, // The maximum allowed size, in MB, for files used as model output.
  "gisCacheSizeLimitMB": 256, // The maximum size, in MB, of the GIS cache per model.
  "userJVMArgs": "", // Custom JVM arguments that will be used when launching models.
  "cacheCleanupThresholdGb": 15, // The minimum amount of free disk space, in GB, below which the executor component starts cleaning old cache files.
  "minSpaceToRunExperimentGb": 5 // The minimum amount of free disk space, in GB, required to start a new model run.
}

executor:
  appsRootDir: /opt/anylogic/ # The directory inside the executor container where the JAR file of the executor component is stored. Should not be edited in any way.
  s3CacheDir: /var/cache/executor/ # The directory inside the executor container where executor stores the JAR file of the model and its resources.
  logsDir: /var/log/executor/ # The directory inside the executor container where executor stores the model execution logs.
  sessionsDir: /var/run/executor/ # The directory inside the executor container where executor creates temporary environments for model execution.
  sessionTimeout: "300" # The timeout, in seconds, for animation session activity. The executor component will stop animation sessions that are inactive for the specified period.
  securityManagerEnabled: false # Allows you to specify whether Private Cloud should use Java Security Manager. If true, models are launched in a sandbox, which may reduce execution speed by 2–3 times.
  totalOutputFilesSizeLimitMB: 256 # The maximum allowed size, in MB, for files used as model output.
  gisCacheSizeLimitMB: 256 # The maximum size, in MB, of the GIS cache per model.
  userJVMArgs: "" # Custom JVM arguments that will be used when launching models.
  OSType: busybox # Can be either 'busybox' or 'debian'.
  cacheCleanupThresholdGb: 15 # The minimum amount of free disk space, in GB, below which the executor component starts cleaning old cache files.
  minSpaceToRunExperimentGb: 5 # The minimum amount of free disk space, in GB, required to start a new model run.

This file contains the S3 backend configuration. Private Cloud uses the MinIO server (a file server Docker container) for S3.

{
  "provider": "MINIO",
  "bucket": "anylogic-cloud",
  "root": "",
  "amazonConfiguration": {
    "region": "",
    "accessKey": "<key string>",
    "secretKey": "<key string>"
  }
}

file-storage:
  provider: MINIO
  bucket: anylogic-cloud
  root: ""
  amazonConfiguration:
    region: ""
    accessKey: ${minio_access_key}
    secretKey: ${minio_secret}

This file contains the UUID and optional name for the highlighted user: models that this user uploads to Cloud will appear in the Selected Models section of the title screen of Cloud.

If this user does not have a username on their profile page, their first and last names will be displayed instead.

This file contains the external public address of the Cloud installation. Using this URL, your users will be able to open the Cloud web interface. The same URL is used in AnyLogic desktop installations to export models to Cloud.

A correct Cloud instance URL must start with the explicitly specified protocol — that is, http:// or https://.

You may choose to specify a non-default port: in that case, specify it at the end of the address. If no port is specified, the default port is used — 80 for HTTP, 443 for HTTPS.

{
  "gatewayHost": "http://10.0.0.1:8080"
}

public:
  gatewayHost: http://10.0.0.1:8080

This file contains an option that determines whether the registration via the web interface is available in the Private Cloud instance. Set the option to false to disable the registration form on the login screen and the corresponding API.

If the registration is disabled, the only way to add new users to the Cloud instance is to use the functionality of the corresponding tab in the administrator panel.

The emailVerificationEnabled flag determines whether the instance sends a verification email. If it is set to false, the account activates immediately after the user fills out the signup form. If it is set to true, the instance sends a verification email, and the user must click the confirmation link there.

The enableGuestAccess option determines whether Private Cloud is available to guests. If this option is set to false, the Guest tab on the login screen and guests’ access to public models will be unavailable. To use Cloud, your users will need to sign up first.

The providers object lists the authentication providers supported by the Private Cloud instance. Currently, the following providers are supported:

• anylogic — enables user management functionality of AnyLogic Cloud.
• ldap — enables the authentication via the LDAP server associated with the Private Cloud instance; the server should be specified in the ldap file.
• ad — enables the authentication via the Active Directory server associated with the Private Cloud instance; the server should be specified in the ad file.
• oauth — enables the authentication via the OAuth 2 compliant identity provider. The settings must be specified in the oauth file.

Providers in the enterprise field are listed in order of priority. If anylogic is listed first, Private Cloud will try to identify the authenticating user in its own database first, and then check the ldap database.

The passwordPolicy object specifies the password requirements for users who register through the signup form. Certain restrictions apply:

• Only Latin characters are supported in passwords.
• minLength specifies the total length of the passwords. It should be an integer between 6 and 40.
• For any other field, the value should be a positive integer, while 0 means this option is disabled.
• Each field specifying the number of characters of a particular type is handled separately.
• If the specified number of characters is logically incorrect (say, the number of digits exceeds the maximum length, and another field requires that other type of characters to be present in the password as well), the rest service component will not be able to start up.

{
  "enabled": true, // Specifies whether a user can use the built-in signup form to create a profile in the instance.
  "enableGuestAccess": true, // Specifies whether guests (non-authorized users) have access to the instance.
  "emailVerificationEnabled": true, // Specifies whether the user needs to click the confirmation link in the verification email after registering.
  "providers": {
    "enterprise": "anylogic" // Specifies the list of available providers, a comma-separated string.
    // May include "anylogic" (built-in user management system of Cloud), "ldap" (LDAP integration),
    // "ad" (Active Directory integration), or "oauth" (OAuth 2.0 compliant providers).
  },
  "passwordPolicy": {
    "minLength": 8, // The minimum password length. Must be between 6 and 40.
    "numberOfDigits": 0, // The minimum number of digits required in the password.
    "numberOfUpperCaseCharacters": 0, // The minimum number of uppercase Latin characters required in the password.
    "numberOfLowerCaseCharacters": 0, // The minimum number of lowercase Latin characters required in the password.
    "numberOfSpecialCharacters": 0 // The minimum number of special (non-alphanumeric) characters required in the password.
  }
}

registration:
  enabled: true # Specifies whether a user can use the built-in signup form to create a profile in the instance.
  enableGuestAccess: true # Specifies whether guests (non-authorized users) have access to the instance.
  emailVerificationEnabled: true # Specifies whether the user needs to click the confirmation link in the verification email after registering.
  providers:
    enterprise: anylogic # May include "anylogic" (built-in user management system of Cloud), "ldap" (LDAP integration), "ad" (Active Directory integration), or "oauth" (OAuth 2.0 compliant providers).
  passwordPolicy:
    minLength: 8 # The minimum password length. Must be between 6 and 40.
    numberOfDigits: 0 # The minimum number of digits required in the password.
    numberOfUpperCaseCharacters: 0 # The minimum number of uppercase Latin characters required in the password.
    numberOfLowerCaseCharacters: 0 # The minimum number of lowercase Latin characters required in the password.
    numberOfSpecialCharacters: 0 # The minimum number of special (non-alphanumeric) characters required in the password.

This file specifies the settings of the LDAP server associated with the Private Cloud instance. For more information on LDAP configuration, see Private Cloud: LDAP and AD authentication.

The service account term refers to the user profile whose credentials Private Cloud uses to access the LDAP database.

It is possible to specify that certain fields on the server are binary-encoded. To do that, add b: to the beginning of the string value of the field, for example:

providerSpecificUid: "b:objectGUID"

{
  "serverAddress": "ldap://ldap.example.com:389/dc=company,dc=com", // The URL of the LDAP server.
  "cloudUserDN": "cn=admin,dc=company,dc=com", // The distinguished name (DN) of the service account.
  "cloudUserPassword": "xxx", // The service account password.
  "userSearchBase": "ou=users", // The LDAP organizational unit that Private Cloud processes to identify a user.
  "userSearchFilter": "(mail={0})", // The user identification filter expression. If the user attempts to authenticate, {0} will be replaced with that user's username.
  "groupSearchBase": "ou=groups", // The LDAP organizational unit that Private Cloud processes to identify the groups to which the user belongs.
  "groupSearchFilter": "member={0}", // The group identification filter expression. Upon successful identification of the user, {0} will be replaced with the distinguished name of that user.
  "cloudAdminGroupName": "Cloud Admins", // The common name (CN) of the group whose members should have administrator permissions in the Private Cloud instance.
  "cloudUserGroupName": "Cloud Users", // The common name (CN) of the group whose members should be users of the Private Cloud instance.
  "mapping": { // This object establishes a value mapping between LDAP-specific fields and Private Cloud fields. Upon authentication of the LDAP user, their Cloud profile will be populated according to this mapping. Mapped fields will not be editable via the Cloud web UI.
    "providerSpecificUid": "entryUUID", // The LDAP field whose value Private Cloud should use to uniquely identify the LDAP user.
    "email": "mail", // The LDAP field containing the user's email.
    "firstName": "givenName", // The LDAP field containing the user's first name.
    "lastName": "sn", // The LDAP field containing the user's last name.
    "company": "", // The LDAP field containing the user's company name.
    "personalPage": "", // The LDAP field containing the link to the user's personal page.
    "linkedIn": "", // The LDAP field containing the link to the user's LinkedIn page.
    "description": "" // The LDAP field containing supplementary information about the user.
  }
}

ldap:
  serverAddress: "" # The URL of the LDAP server.
  cloudUserDN: "" # The distinguished name (DN) of the service account.
  cloudUserPassword: "" # The service account password.
  userSearchBase: "" # The LDAP organizational unit that Private Cloud processes to identify a user.
  userSearchFilter: "" # The user identification filter expression. {0} will be replaced with the authenticating username.
  groupSearchBase: "" # The LDAP organizational unit that Private Cloud processes to identify the groups to which the user belongs.
  groupSearchFilter: "" # The group identification filter expression. {0} will be replaced with the distinguished name of the identified user.
  cloudAdminGroupName: "" # The common name (CN) of the group whose members should have administrator permissions in the Private Cloud instance.
  cloudUserGroupName: "" # The common name (CN) of the group whose members should be users of the Private Cloud instance.
  mapping:
    providerSpecificUid: "" # The LDAP field whose value Private Cloud should use to uniquely identify the LDAP user.
    email: "" # The LDAP field containing the user's email.
    firstName: "" # The LDAP field containing the user's first name.
    lastName: "" # The LDAP field containing the user's last name.
    company: "" # The LDAP field containing the user's company name.
    personalPage: "" # The LDAP field containing the link to the user's personal page.
    linkedIn: "" # The LDAP field containing the link to the user's LinkedIn page.
    description: "" # The LDAP field containing supplementary information about the user.

This file specifies the settings of the Active Directory server associated with the Private Cloud instance. For more information about Active Directory configuration, see Private Cloud: LDAP and AD authentication.

It is possible to specify that certain fields on the server are binary-encoded. To do that, add b: to the beginning of the string value of the field, for example:

providerSpecificUid: "b:objectGUID"

{
  "serverAddress": "ldap://ad.example.com", // The URL of the Active Directory server.
  "domain": "domain.example.com", // The Active Directory domain name.
  "rootDn": "dc=example,dc=com", // Optional. Specifies the root distinguished name. Useful in the rare case where the authenticating user's username contains a domain name that differs from the Active Directory server's domain name.
  "cloudAdminGroupName": "Administrators", // The name of the group whose members should have administrator permissions in the Private Cloud instance.
  "cloudUserGroupName": "Cloud Users", // The name of the group whose members should be users of the Private Cloud instance.
  "mapping": { // This object establishes a value mapping between AD-specific fields and Private Cloud fields. Upon authentication of the AD user, their Cloud profile will be populated according to this mapping. Mapped fields will not be editable via the Cloud web UI.
    "providerSpecificUid": "b:objectGUID", // The AD field whose value Private Cloud should use to uniquely identify the LDAP user.
    "email": "userPrincipalName", // The AD field containing the user's email.
    "firstName": "givenName", // The AD field containing the user's first name.
    "lastName": "sn", // The AD field containing the user's last name.
    "company": "", // The AD field containing the user's company name.
    "personalPage": "", // The AD field containing the link to the user's personal page.
    "linkedIn": "", // The AD field containing the link to the user's LinkedIn page.
    "description": "" // The AD field containing supplementary information about the user.
  }
}

ad:
  serverAddress: "" # The URL of the Active Directory server.
  domain: "" # The Active Directory domain name.
  rootDn: "" # Optional. Specifies the root distinguished name.
  cloudAdminGroupName: "" # The name of the group whose members should have administrator permissions in the Private Cloud instance.
  cloudUserGroupName: "" # The name of the group whose members should be users of the Private Cloud instance.
  mapping:
    providerSpecificUid: "" # The AD field whose value Private Cloud should use to uniquely identify the LDAP user.
    email: "" # The AD field containing the user's email.
    firstName: "" # The AD field containing the user's first name.
    lastName: "" # The AD field containing the user's last name.
    company: "" # The AD field containing the user's company name.
    personalPage: "" # The AD field containing the link to the user's personal page.
    linkedIn: "" # The AD field containing the link to the user's LinkedIn page.
    description: "" # The AD field containing supplementary information about the user.

This file specifies the settings of the OAuth 2 compatible identity provider associated with the Private Cloud instance. For more information on OAuth configuration, see OAuth authorization.

The example below shows settings taken from the PingOne identity provider. You must manually adjust them to use another provider. Some of the fields listed there are optional and only need to be specified if your provider requires them. See the example configurations in the corresponding article for reference.

{
  "oauthProviders": [
    {
      "registrationId": "ping", // The registration ID part of the redirect URI you set in the provider console.
      "name": "Ping Cloud",
      "providerConfiguration": { // The identity provider mapping.
        "authorization-uri": "https://auth.pingone.eu/{yourInternalId}/as/authorize",
        "issuer-uri": "https://auth.pingone.eu/{yourInternalId}/as",
        "token-uri": "https://auth.pingone.eu/{yourInternalId}/as/token",
        "user-info-uri": "https://auth.pingone.eu/{yourInternalId}/as/userinfo",
        "jwk-set-uri": "https://auth.pingone.eu/{yourInternalId}/as/jwks"
      },
      "registrationConfiguration": {
        "authorization-grant-type": "authorization_code",
        "client-authentication-method": "client_secret_basic", // The client authentication method. May be omitted if client_secret_basic is used.
        "client-id": "{yourClientId}", // Your identity provider client ID.
        "client-secret": "{yourClientSecret}", // Your identity provider client secret.
        "redirect-uri": "https://<AnyLogic Cloud host name>/api/oauth/ping", // The full redirect URI.
        "scope": [
          "openid", "profile", "email" // The list of scopes depends on the identity provider.
        ]
      }
    }
  ],
  "oauthAttributes": {
    "email": "email",
    "name": "name"
  }
}

oauth:
  oauthProviders:
    - registrationId: ping # The registration ID part of the redirect URI configured in the provider console.
      name: Ping Cloud
      providerConfiguration:
        authorization-uri: https://auth.pingone.eu/{yourInternalId}/as/authorize
        issuer-uri: https://auth.pingone.eu/{yourInternalId}/as
        token-uri: https://auth.pingone.eu/{yourInternalId}/as/token
        user-info-uri: https://auth.pingone.eu/{yourInternalId}/as/userinfo
        jwk-set-uri: https://auth.pingone.eu/{yourInternalId}/as/jwks
      registrationConfiguration:
        authorization-grant-type: authorization_code
        client-authentication-method: client_secret_basic # May be omitted if client_secret_basic is used.
        client-id: "{yourClientId}" # Your identity provider client ID.
        client-secret: "{yourClientSecret}" # Your identity provider client secret.
        redirect-uri: https://<AnyLogic Cloud host name>/api/oauth/ping # The full redirect URI.
        scope:
          - openid
          - profile
          - email
  oauthAttributes:
    email: email
    name: name

This file contains references to the Cloud SQL databases: names and authentication credentials.

Currently, AnyLogic Cloud has a single database, anylogic_cloud, which holds the data for users, models, options, comments, and experiment results.

Previous versions of Private Cloud also had separate databases for experiment results, auth, and node process data, which will be converted and removed during an instance upgrade.

This file contains the configuration of the executor-multi-run service component.

Pre-2.7.0

The size of a batch — a set of model runs (<batch size>) is calculated as <number of iterations> / preferredCount.

The initial number of batches created is equal to the initialCount field, meaning the number of incomplete runs at that point is equal to initialCount * <batch size>. A batch is then created every creationWindowMillis period. The size of this new batch is calculated as follows: min(<batch size> * initialCount - <number of incomplete runs>, <batch size>). The value of the minSize field is ignored in this calculation.

{
  "maxTasks": 1024, // The maximum number of tasks that a single multi-run executor will process simultaneously. Tasks that do not reach this limit will be retried.
  "maxSingleRunsInMultiRun": 65534, // The maximum number of single runs in one multi-run experiment.
  "batches": {
    "minSize": 5, // If the batch size is less than this number, it will be scaled to this number. The last batch can ignore this rule.
    "maxSize": 20, // If the batch size is greater than this number, it will be scaled to this number.
    "initialCount": 8, // The initial number of batches created at the start of the experiment. 
    "preferredCount": 8, // The preferred number of batches.
    "creationWindowMillis": 5000 // The timeout before a new batch is created, in milliseconds. 
  }
}

Post-2.7.0

Contains the setting for duration-based batching, as described in Architecture.

{
  "maxTasks": 1024, // The maximum number of tasks that a single multi-run executor will process simultaneously. Tasks that exceed this limit will be retried.
  "maxSingleRunsInMultiRun": 65534, // The maximum number of single runs in one multi-run experiment.
  "batchingConfiguration": {
    "expectedMaxBatchWorkSeconds": 1800, // The maximum pure execution time of a batch, excluding environment setup and result storage.
    "totalAvailableSlots": 4 // The number of executor slots available. Must match the actual executor count for efficient resource usage.
  }
}

multi-run:
  maxTasks: 1024 # The maximum number of tasks that a single multi-run executor will process simultaneously. Tasks that exceed this limit will be retried.
  maxSingleRunsInMultiRun: 65534 # The maximum number of single runs in one multi-run experiment.
  batchingConfiguration:
    expectedMaxBatchWorkSeconds: 1800 # The maximum pure execution time of a batch, excluding environment setup and result storage.
    totalAvailableSlots: 4 # The number of executor slots available. Must match the actual executor count for efficient resource usage.

Settings in this file determine the availability of certain features of the Private Cloud UI.

It allows to disable the custom UI for Cloud models, and to control the system that tracks unused files.

The file tracking mechanism monitors uploaded model resources and input files, automatically marking those that are no longer referenced anywhere in the system. This feature is enabled by default; disable it if you do not want the Cloud to track such files.

{
  "enableCustomUI": true, // Set to false to disable the custom UI.
  "enableFileTracking": true // Set to false to disable checks for unused files.
}

feature-flags:
  enableCustomUI: true # Set to false to disable the custom UI.
  enableFileTracking: true # Set to false to disable checks for unused files.

This is a service file that stores the credentials that the instance uses to access the animation engines, in case your model uses the non-default animation engine. It should not be modified in any way.

{
  "keystores": [ {
    "filename": "webjar.truststore", // The name of the truststore file.
    "password": "changeme", // The truststore password.
    "aliases": [ "webjarTestKey" ] // The list of public key aliases.
  } ]
}

animations:
  keystores:
    - filename: webjar.truststore # The name of the truststore file.
      password: changeme # The truststore password.
      aliases: # The list of public key aliases.
        - webjarTestKey

This file stores the settings for the cookie consent message, localization packages, and social network sharing buttons.

{
  "cookieConsentMessage": {
    "enable": true, // Set to false to disable the cookie consent message.
    "message": "We and our partners use cookies to give you the best online experience, including to personalize content, advertising, and web analytics.", // The cookie consent message text.
    "privacyPolicyLinkText": "Cookie Policy", // The text of the cookie policy link.
    "privacyPolicyLink": "https://www.anylogic.com/upload/privacy_policy/cookie-policy.pdf", // The cookie policy link.
    "position": "top", // Defines where to display the cookie consent message in the Private Cloud UI. Possible values: "top", "bottom".
    "width": "narrow" // Sets the width of the cookie consent message. Possible values: "narrow", "wide".
  },
  "i18n": {
    "languages": [ // Defines the languages available in the Private Cloud instance.
      "en",
      "zh"
    ],
    "defaultLanguage": "en" // Defines the default language of the instance.
  },
  "documentTitle": "AnyLogic Cloud", // Defines the common part of the browser tab title for all indexable pages.
  "sharingButtons": {
    "enable": true, // Defines whether social network sharing buttons are available on the "General" tab of the model screen.
    "buttons": [ // Set "visible" to false to disable an individual social network button.
      {
        "name": "facebook",
        "visible": true
      },
      {
        "name": "twitter",
        "visible": true
      },
      {
        "name": "linkedin",
        "visible": true
      },
      {
        "name": "telegram",
        "visible": true
      },
      {
        "name": "wechat",
        "visible": true
      }
    ]
  }
}

frontend:
  cookieConsentMessage:
    enable: true # Set to false to disable the cookie consent message.
    message: "We and our partners use cookies to give you the best online experience, including to personalize content, advertising, and web analytics." # The cookie consent message text.
    privacyPolicyLinkText: Cookie Policy # The text of the cookie policy link.
    privacyPolicyLink: https://www.anylogic.com/upload/privacy_policy/cookie-policy.pdf # The cookie policy link.
    position: top # Defines where to display the cookie consent message in the Private Cloud UI. Possible values: "top", "bottom".
    width: narrow # Sets the width of the cookie consent message. Possible values: "narrow", "wide".
  i18n:
    languages: # Defines the languages available in the Private Cloud instance.
      - en
      - zh
    defaultLanguage: en # Defines the default language of the instance.
  documentTitle: AnyLogic Cloud # Defines the common part of the browser tab title for all indexable pages.
  sharingButtons:
    enable: true # Defines whether social network sharing buttons are available on the "General" tab of the model screen.
    buttons: # Set "visible" to false to disable an individual social network button.
      - name: facebook
        visible: true
      - name: twitter
        visible: true
      - name: linkedin
        visible: true
      - name: telegram
        visible: true
      - name: wechat
        visible: true

Starting with version 2.8.0, Private Cloud requires a separate configuration file license-server.yaml which specifies the address of Team License Server used for Cloud activation. Previously, this configuration was stored in .../controller/teamlicense-server.conf.

license-server:
  ipAddress: "" # The IP address or host name of Team License Server.
  port: 0 # The Team License Server port.

Prior to version 2.8.0, Private Cloud included the configuration file default-policy-groups.json Starting with version 2.8.0, this file is no longer used. In earlier versions, this file defined policy groups inherited from public Cloud. Since Private Cloud does not distinguish between subscription and free users, changing these policies had no practical effect.

{
  "experimentRunLimits": "experimentRunLimits:privateCloud",
  "sandboxing": "sandboxing:soft",
  "accountType": "accountType:free",
  "experimentRunMaxMemoryMB": "experimentRunMaxMemoryMB:privateCloud"
}

How can we improve this article?

Send