...
at.java_home.path
specifies a path to java executable to launch the Service with.It should be set only in one case - if Jira is not running on Java 8. Read more here.
Default Value: not set
at.java_startup.args
- defines the list of additional java command line options when starting the ActivityTimeline service.It is possible to set custom java heap memory settings, temp folder path etc.
Default Value: not set
at.service.port
- defines port that ActivityTimeline will launch the service on. By default, the app picks a random free port available in the operating system. You may set this setting and the app will always use the specified port number.Possible values: number in range between 1025 and 65536
Default Value: not set
at.manager_service.port
- defines port that ActivityTimeline manager service will listen to. It controls the state of ActivityTimeline service. By default, the app picks a random free port available in the operating system. You may set this setting and the app will always use the specified port number.Possible values: number in range between 1025 and 65536
Default Value: not set
at.jira_connection.url
- Defines a local accessible Jira home URL or IP address with context path. This setting is determined automatically and there is no need to customize it in 99% of environments.Allowed value: string, Url or IP address of Jira including context path. Example: https://1.2.3.4:8080/jira
Default Value: not set
at.jira.node1.url
,at.jira.node2.url
,at.jira.node3.url
,at.jira.node4.url
Status colour Blue title 9.4.0+ at.jira.node5.url
,at.jira.node6.url
,at.jira.node7.url
,at.jira.node8.url
Status colour Blue title 9.6.0+
These settings can override the connection URL of each Jira node. Allows to manually specify local URL of each Jira DC node (e.g. when using external proxy/lb, different docker public/private ports etc.). Supports up to 4 Jira DC nodes
or up to 8 Jira DC nodesStatus colour Blue title 9.4.0+
.Status colour Blue title 9.6.0+ Format: [node id]@[node url]
Example: "at.jira.node1.url=node-11111111@http://serveraddress:8080"
Default Value: not set
at.force_https_for_internal_communication_between_nodes
- This setting can force internal communication to use https scheme instead of http. By default, the system automatically picks the proper scheme based on available Jira instance Tomcat connectors. It could be set to true only if there is a Jira Connector on https scheme with configured SSL on Tomcat: SSLEnabled=”true”.Possible values: true; false
Default Values: not set
at.db_connections_max
- This setting specifies the maximum number of active connections to database the app can maintain at any given time. By default, it can maintain up to 25 simultaneous active connections. The value must be larger thanStatus colour Blue title 8.2.0+ at.db_connections_max_idle
andat.db_connections_min_idle
.Possible values: integer number starting from 10
Default Value: not set
at.db_connections_max_idle
- This setting specifies the maximum number of idle connections to database the app can maintain at any given time. By default, it maintains up to 15 idle connections. The value must be larger thanStatus colour Blue title 8.2.0+ at.db_connections_max_idle
and less thanat.db_connections_max
.Possible values: integer number starting from 5
Default Value: not set
at.db_connections_min_idle
- This setting specifies the minimum number of idle connections to database the app should maintain at any given time. By default, it maintains 1 idle connection. The value must be less thanStatus colour Blue title 8.2.0+ at.db_connections_max_idle
andat.db_connections_max
.Possible values: integer numbers starting from 1
Default Value: not set
at.use_v2_communication
- This setting specifies the approach version of communication between Jira DC nodes. Set it to “true” to enable the v2 of the communication mechanism. Remove the setting altogether or set it to an empty value to keep the current v1 approach.Status colour Blue title 9.8.1+
By default, it uses v1 communication mechanism.Possible values: true or empty
Default Value: not set
It is required to restart the “ActivityTimeline Service” from the Maintenance Page or disable/enable ActivityTimeline app from the “Manage apps” page for the changes to take effect.
...