Child pages
  • Server Properties

This is the documentation of the release 2.2 of automaIT. The documentation of the latest stable release can be found at AUTOMAIT.

Skip to end of metadata
Go to start of metadata

The following properties may be used to configure the server. These must be set in the context.xml file of the server which is usually located at $CATALINA_BASE/conf/context.xml.

The default and current values of all server properties are shown under the menu item "Maintenance / Server properties" in the web interface.

Example:

$CATALINA_BASE/conf/context.xml
<Resource name="properties/np"
    ...
    agent.remote.update.enabled="false"
    ...
/>

Product Version: 2.2.0

 

Property key

Type

Default value

Category

Description

 

agent.reconnect.interval

duration

1m

EXPERT

time to pass before a target host becomes eligible for connect checking
Details: During model execution, remote agents will be locked and connected, before executing any commands. This property configures the minimum time to pass, before a previously connected host should be reconnected. This represents an optimization mechanism, so that subsequent lock/connect operations within a plan or component do not result in too many connects to the remote agent host.

 

agent.remote.update.enabled

[ true, false ]

true

EXPERT

configures if agent remote updates are enabled or not

 

agent.remote.update.package

url

classpath:np-agent.zip

INTERNAL

location of the agent package ZIP to be used for remote updates

 

agent.remote.update.restart.delay

duration

${ssh.client.agent.startup.timeout}

EXPERT

time to wait after an update for the remote agent to restart

 

agent.script.interpreter.timeout

duration

10s

EXPERT

the timeout to use when invoking scripts to determine OS information

 

cache.statistics.enabled

[ true, false ]

false

INTERNAL

enables/disables cache statistics exposed via JMX

 

cli.display.format.date

string

dd.MM.yyyy HH:mm:ss

EXPERT

display format for date/time

 

cli.display.format.duration

string

HH:mm:ss

EXPERT

display format for durations

 

cli.job.process.output.size

byte size

1M

EXPERT

maximum size when retrieving the output of an execution job

 

cli.session.id.expiration.period

duration

5m

EXPERT

time after which an idle CLI session id will expire
Details: A CLI session ID is considered idle for the given amount of time, when there has been no CLI authentication using it. This means, that one can use a CLI session ID continuously, as long as the duration between two CLI calls does not take longer than the configured value.

 

db.check.enabled

[ true, false ]

true

EXPERT

enables/disables diverse data consistency checks at server start-up time.

 

db.current.schema.statement

string

 

EXPERT

configures the SQL statement to be executed in order to set the current database schema
Details: This must be set to a DB-specific SQL statement string, which is able to set the schema for an existing SQL connection, e.g. 'SET search_path TO <schema>' for PostgreSQL. This property should only be used in environments, where multi-tenant database connections are required, i.e. the desired schema cannot be configured directly with the data-source itself. It may eventually create a performance overhead, as an additional statement is being executed for every connection retrieved from the data-source. Be aware that there is no schema 'unset' operation, so all application instances sharing the same data-source MUST use this property with their corresponding schema.

 

db.migration.enabled

[ true, false ]

true

INTERNAL

configures the automatic DB migration during startup

 

event.filter.configuration.xml

url

/WEB-INF/config/spring-server-event-nocustom.xml

STANDARD

location of the Spring configuration file for event filter configuration

 

event.max.shutdown.time

duration

10s

EXPERT

maximum time to wait for event engine to shutdown

 

extensions.custom.xml

url

/WEB-INF/config/extensions-nocustom.xml

STANDARD

location of configuration file for custom model extensions
Details: The default contains no custom model extensions.
Example:

file:///data/extensions.xml

 

extensions.protocol.prefix

string

ext:

EXPERT

prefix to be used in execution protocol representing command executions of custom model extensions.

 

faces.flow.builder

bean id

facesFlowBuilder

INTERNAL

internal bean reference

 

file.io.tmp.dir

path

${java.io.tmpdir}

STANDARD

server temporary directory used for file handling

 

file.repository.deletion.refresh

positive integer

50

INTERNAL

number of deletions before the resource repository pointer is being refreshed

 

file.repository.max.item.size

positive integer

500

INTERNAL

maximum number of items per folder within the resource repository

 

file.repository.root

path

 

REQUIRED

absolute path to the server's resource repository
Details: This is the location where all the resources are stored, which have been checked in as part of the component model, i.e. file and directory resources.

 

file.transfer.max.chunk.size

byte size

1M

EXPERT

maximum chunk size when transferring files to the remote agent host

 

file.upload.max.size

byte size

${resource.file.upload.max.size}

STANDARD

general maximum file upload size
Details: In contrast to the other maximum upload size properties general maximum upload size will already be checked during upload process.

 

hibernate.cache.use_query_cache

[ true, false ]

true

INTERNAL

configures if Hibernate query caching is to be used

 

hibernate.cache.use_second_level_cache

[ true, false ]

true

INTERNAL

configures if Hibernate second-level caching is to be used

 

hibernate.dialect

class

org.hibernate.dialect.PostgreSQLDialect

INTERNAL

Hibernate database dialect
Details: This configures the Hibernate database dialect to be used for DB-compliant SQL creation and interpretation.

 

hibernate.format_sql

[ true, false ]

true

INTERNAL

configures if Hibernate SQL statements shall be formatted before being printed to the console

 

hibernate.hbm2ddl.auto

[ validate, update, create, create-drop ]

validate

INTERNAL

configures the Hibernate schema export/validation mode

 

hibernate.jdbc.fetch_size

positive integer

100

INTERNAL

configures the JDBC fetch size used by Hibernate

 

hibernate.jdbc.use_streams_for_binary

[ true, false ]

true

INTERNAL

configures if streams shall be used when reading/writing binary data

 

hibernate.show_sql

[ true, false ]

false

INTERNAL

configures if Hibernate SQL statements shall be printed to the console

 

hibernate.statistics.enabled

[ true, false ]

false

INTERNAL

enables/disables Hibernate statistics exposed via JMX

 

host.default.ssh.agent.command

path

agent.sh

STANDARD

default remote agent startup command

 

host.default.ssh.login.user

string

automait

STANDARD

default SSH login user name

 

host.default.ssh.remote.http.port

positive integer (0-65535)

9999

STANDARD

default TCP HTTP listen remote port for newly created SSH hosts
Details: This merely represents the default value for the web front-end/cli and may be overridden by the user.

 

host.default.ssh.remote.keep-alive.port

positive integer (0-65535)

9998

STANDARD

default TCP remote port for SSH keep-alive control channel
Details: This merely represents the default value for the web front-end/cli and may be overridden by the user.

 

http.client.connection.acquisition.timeout

duration

20s

EXPERT

maximum time to wait for client-side HTTP connection acquisition
Details: This value limits the waiting time, in case the number of currently available HTTP connections reaches zero. Any new connection request will be aborted after the time configured hereby.

 

http.client.connection.so.timeout

duration

5m

EXPERT

maximum time to wait for data read from an established HTTP connection
Details: This value limits the time to wait for data on an established HTTP connection, that is the maximum time before any data must be sent from the server side.

 

http.client.connection.stale.check

[ true, false ]

false

INTERNAL

enables or disables HTTP connection stale checking
Details: Stale checks are performed prior to sending a request in order to determine if an HTTP connection is valid. However, stale checks represent an expensive operation and thus should be enabled with respect to performance considerations.

 

http.client.connection.timeout

duration

10s

EXPERT

maximum time to wait for client-side HTTP connection to be established
Details: This value limits the waiting time, in case a new connection is being established with a remote host.

 

http.client.idle.connection.close.interval

duration

10s

INTERNAL

time to wait before checking for HTTP idle connections

 

http.client.idle.connection.timeout

duration

5m

EXPERT

time after which an idle client-side HTTP connection will be closed
Details: This value configures the maximum idle time for pooled HTTP connections, that is the time they need to remain idle (not in use) before being closed and removed from the pool.

 

http.client.max.connections

positive integer

100

EXPERT

maximum number of pooled HTTP client connections
Details: This value limits the number of outgoing HTTP client connections from the server process, including both direct HTTP/HTTPS connections and tunneled HTTP-over-SSH connections to remote agents or gateways, respectively.

 

http.client.max.connections.host

positive integer

${http.client.max.connections}

EXPERT

maximum number of pooled HTTP client connection for a single target host
Details: This value limits the number of outgoing HTTP client connections from the server or agent process to a single remote agent or gateway.

 

http.client.request.max.retries

positive integer

3

INTERNAL

maximum number of retries when sending an HTTP request
Details: This configures the maximum number of retries upon I/O errors when sending a request or establishing a connection.

 

http.client.request.sent.retry.enabled

[ true, false ]

true

INTERNAL

configures if already sent HTTP request will be retried or not
Details: This is a low-cost alternative to HTTP stale connection checking, that allows HTTP requests to be resent up to the configured request retries, in case of an I/O error. Be aware, that this may cause undesired side-effects on the receiving side, since the previous request may have been received successfully, but no response could be transmitted.

 

javax.persistence.validation.mode

[ auto, callback, ddl, none ]

none

INTERNAL

configures Hibernate bean validation mode

 

job.export.max.output.size

ByteSize

1M

STANDARD

1 MB
Details: This limits the maximum output size of xml files generated during job export. Only binary output of steps is charged against this limit.

 

job.parallel.default

positive integer

10

STANDARD

default maximum number of parallel host or component based executions per job
Details: This limits the number of concurrent threads per job when running plans or components against multiple hosts or instances, potentially increasing the overall job execution time, as there are less threads available for execution. This value only represents a default for the UI and CLI, that is the user may override the given value.

 

job.parallel.max

positive integer

50

STANDARD

global limit of the maximum number of parallel host or component based executions per job
Details: Maximum value of parallel executions when running plans or components against multiple hosts or instances. The property for maximum parallel executions set in the UI or CLI cannot exceed this value.
Note: this value is related to the property value of job.threads.max.

 

job.threads.cancel.max.lock.wait.timeout

duration

2s

INTERNAL

maximum timeout to wait for locks and latches
Details: This configures a timeout waiting for locks and latches. This is to assure that waiting for locks or latches is interruptable when job threads are cancelled.

 

job.threads.core

positive integer

10

EXPERT

number of core threads used for concurrent job execution

 

job.threads.keep.alive.time

duration

1m

EXPERT

maximum time an idle job thread is kept alive before deactivating it
Details: Threads are only deactivated/dropped, if the total number of current threads is still above the configured core size.

 

job.threads.max

positive integer

50

EXPERT

maximum number of threads used for concurrent job execution
Details: This number defines the maximum number of threads used to spawn concurrent interpreter jobs, i.e. plan and component executions. A single thread is required per host or component-instance based job execution.
This value must be smaller than the number of concurrent database connections (PostgreSQL defaults to 100). Otherwise automaIT will need to wait for database connections and possibly freeze in the UI while waiting.
Note: this value is related to the property value of job.parallel.max.

 

job.threads.max.shutdown.cancel.time

duration

5s

INTERNAL

maximum time to wait for running thread cancellation during application shutdown
Details: This configures an additional sleep time, in case threads were cancelled because they did not shut down during the waiting period. This is to assure that they can process their cancellation logic, before dependant service, such as the database access layer, are being shutdown. Be aware, that the maximum shut down time may also be limited by the servlet container as well, so increasing this value may or may not produce the desired results.

 

job.threads.max.shutdown.wait.time

duration

10s

EXPERT

maximum time to wait for running threads during application shutdown
Details: The server will wait for running jobs to complete during shutdown. This property configures the maximum time to wait for them to complete, before the server will continue to shut down. Be aware, that the maximum shut down time may also be limited by the servlet container as well, so increasing this value may or may not produce the desired results.

 

job.threads.stack.size

ByteSize

256K

EXPERT

stack size used for job execution threads
Details: The stack size needs to be adjusted if complex tasks would otherwise throw StackOverflowError.

 

job.timeout.default

duration

5h

STANDARD

default maximum job timeout for plan and component executions
Details: This limits the maximum job duration for model executions. This value only represents a default for the UI and CLI, that is the user may override the given value. Be sure to increase this value, if you set the number of maximum parallel host executions to a low value.

 

job.timeout.max

duration

24h

STANDARD

global limit of the job timeout for plan and component executions
Details: Upper bound for the maximum job duration of model executions. The job timeout set in the UI or CLI cannot exceed this value.

 

job.timeout.native.default

duration

1h

STANDARD

default maximum timeout for native process executions on the remote agent
Details: This limits the maximum duration of native process executions (per execution). This value only represents a default for the UI and CLI, that is it may be overridden by the user as well as the value provided in the XML model element. The latter one always takes precedence.

 

job.timeout.native.max

duration

6h

STANDARD

global limit for the timeout for native process executions on the remote agent
Details: Upper bound of the maximum duration of native process executions. The native timeout set in the UI or CLI cannot exceed this value.

 

log.memory.buffer.size

positive integer

2048

STANDARD

configures the maximum number of log events to be buffered in-memory

 

mbean.export.prefix

string

#{servletContext.contextPath.length() <= 1 ? 'np' : servletContext.contextPath.substring(1)}

EXPERT

configures the JMX export prefix for exposing MBeans
Details: This property is useful, when running multiple application instances in a single JVM. In this case, a unique JMX prefix must be defined per application instance. The default value is derived from the application's context path, if not '/' or ''.

 

model.xml.upload.max.size

byte size

128K

EXPERT

maximum file upload size in bytes for xml files containing plans, components, and variable sets

 

plugin.jar.upload.max.size

byte size

1G

EXPERT

maximum file upload size in bytes for plug-ins including contained resources
Details: Plug-in uploads will be temporarily saved in the directory referenced by the property file.io.tmp.dir. If the value of this property is increased then make sure that the referenced directory is large enough.

 

process.execution.max.record.error.size

byte size

${process.execution.max.record.output.size}

EXPERT

maximum size of all error output of a single execNative that will be recorded.

 

process.execution.max.record.output.size

byte size

1M

EXPERT

maximum size of all output of a single execNative that will be recorded.

 

process.execution.output.assign.size

byte size

4K

EXPERT

maximum size to be considered when assigning process output to variables
Details: Be aware that increasing this value, may cause out of memory errors, especially when concatenating the affected variables.

 

process.execution.output.match.size

byte size

1M

EXPERT

maximum size to be considered when matching process output using regular expressions
Details: Be aware, that outputs extending the match size may not be properly matchable, since relevant output will be disregarded, thus leading to different success criteria.

 

process.execution.polling.chunk.size

byte size

256K

EXPERT

maximum chunk size when polling process output from the remote agent

 

process.execution.polling.interval

duration

3s

EXPERT

time to wait when polling process output from the remote agent host
Details: When executing processes on the remote agent (execNative), the command is first sent to the remote agent for asynchronous execution, immediately followed by a first polling request for available output (stdout/stderr). Subsequent polls will be sent within the interval specified in this property. This value should be decreased, if your experience truncated process outputs, e.g. when executing processes with high output ratio.

 

property.validation.fail.on.warning

boolean

true

EXPERT

configures if the server will fail during startup, if an invalid property configuration is detected

 

regex.matching.stack.size

ByteSize

512K

EXPERT

stack size used for regex matching threads
Details: The stack size needs to be adjusted if complex tasks would otherwise throw StackOverflowError.

 

regex.matching.threads.keep.alive.time

duration

15m

EXPERT

maximum time an idle regex matching thread is kept alive before deactivating it
Details: Threads are only deactivated/dropped, if the total number of current threads is still above the core size (which here means always, as the core size is 0).

 

regex.matching.threads.max

positive integer

10

EXPERT

maximum number of threads used for xsd validation
Details: This number defines the maximum number of threads used to spawn concurrent regex matching tasks, whose usage is triggered by @UseThread Annotation. A single thread is required per matching task.

 

resource.config.upload.max.size

byte size

2M

EXPERT

maximum file size for configuration resources
Details: Configuration resources allow substitutions which will be replaced with specific values while installing. The maximum size of these resources is limited because the substitutions will be processed in memory.

 

resource.directory.upload.max.size

byte size

${resource.file.upload.max.size}

EXPERT

maximum file size for file resources

 

resource.file.upload.max.size

byte size

2G

EXPERT

maximum file size for directory resources
Details: Directory resources are internally converted to a compressed archive file. Therefore maximum file size is checked for whole compressed file in this case.

 

security.custom.providers.xml

url

/WEB-INF/config/spring-server-security-nocustom.xml

EXPERT

location of the Spring configuration file defining additional security authentication providers

 

server.address

string

 

STANDARD

the optional address of the automaIT server.
Details: The configured address is returned by the system variable 'sys.serverAddress'. If empty (default) the server address is determined automatically.

 

server.port.http

positive integer (0-65535)

 

REQUIRED

HTTP listening port of the servlet container
Details: This value must be supplied, so the application can switch between secured and unsecured page contents.

 

server.port.https

positive integer (0-65535)

 

REQUIRED

HTTPS listening port of the servlet container
Details: This value must be supplied, so the application can switch between secured and unsecured page contents.

 

simulation.locking.host.connect

[ true, false ]

true

EXPERT

defines whether connects to hosts should be executed during simulation.
Details: This setting only takes effect for simulation runs. If this setting is true, the connect will be executed. If it is false, it will not be checked, if the host is available. This setting does never take effect for execution runs.

 

spring.profiles.active

a valid combination of [ caching, jmx, support-mode, none ]

caching,jmx

INTERNAL

list of active Spring profiles
Details: This property enables/disables different configuration profiles of the application and should be configured with extreme care.

 

ssh.client.agent.shutdown.timeout

duration

5s

INTERNAL

time to wait for the agent to shut down.
Details: The agent shutdown takes some time to be completed. This is the maximum time that the SSH client will wait for the agent to shutdown

 

ssh.client.agent.started.timeout

duration

3s

INTERNAL

time to wait to check if the remote agent startup failed immediately.
Details: The agent startup may fail because the start script does not exist or the parameters are invalid. In this case it is not necessary to wait for ${ssh.client.agent.startup.timeout}.

 

ssh.client.agent.startup.timeout

duration

60s

EXPERT

maximum time to wait for a remote agent to start via SSH tunneling
Details: This value limits the time to wait for a remote SSH agent to start, that is the maximum time that the client will wait for a response from the remotely started agent.

 

ssh.client.command

string

ssh {0}@{1} -p {2} -o BatchMode=yes -A -L {3}:{4}:{5} -R {6}:{7}:{8} {9}

STANDARD

SSH command used to establish the SSH tunnel.
Details: The tunnel forwards two ports:

  • a dynamically assigned local port will be forwarded to the remote http port.
  • the remote control port will be forwarded to a dynamically local port.
    This tunnel will be used to start the remote agent which then listens on the remote http port.
    By default agent forwarding is enabled (-A).
    The BatchMode is enabled to avoid the user interaction (querying for passwords).
    The following replacements will be performed:
    {0}: user name used to connect to the target host
    {1}: the host name of the target host
    {2}: the port of the target host
    {3}: the local http port of the tunnelled remote http port
    {4}: the remote host of the tunnelled http port
    {5}: the remote http port of the tunnelled http port
    {6}: the remote control port
    {7}: the local host of the tunnelled remote control port
    {8}: the local port of the tunnelled remote control port
    {9}: the command used to start the remote agent

 

ssh.client.idle.connection.close.interval

duration

10s

INTERNAL

time to wait before checking for SSH idle connections

 

ssh.client.loopback.address

IP

127.0.0.1

INTERNAL

loop-back IP address used for SSH tunneling

 

ssh.client.max.connections

positive integer

50

EXPERT

maximum number of concurrent SSH client connections
Details: This value limits the number of outgoing SSH client connections from the server process. An SSH client connection is established on a per host basis, that is parallel HTTP connections to the same SSH target host share the same SSH connection.

 

ssl.client.key.password

string

987654

STANDARD

password used to access the SSL key within the key store

 

ssl.client.keystore

url

classpath:info/novatec/np/common/communication/ssl/default_keystore

STANDARD

the location of the client-side SSL key store used for authentication
Details: The configured key store is used on the client side, in case mutual authentication is enabled.

 

ssl.client.keystore.password

string

123456

STANDARD

password used to load the SSL key store

 

ssl.client.truststore

url

${ssl.client.keystore}

STANDARD

the location of the client-side SSL trust store used for authentication
Details: The configured trust store is used on the client side to verify the server SSL certificate, in case mutual authentication is enabled.

 

ssl.client.truststore.password

string

${ssl.client.keystore.password}

STANDARD

password used to load the SSL trust store

 

ssl.protocol

[ SSL, SSLv2, SSLv3, TLS, TLSv1, TLSv1.1 ]

TLS

INTERNAL

client/server-side SSL protocol version

 

step.depth.max

positive integer

50

EXPERT

Limits the maximum step depth during plan or component executions.
Details: If this value is increased, it is necessary to also increase the value for property job.threads.stack.size.

 

typesafe.id.generator.class

class

org.hibernate.id.SequenceHiLoGenerator

INTERNAL

full qualified class name of the Hibernate sequence generator to be used

 

ui.application.name

string

automaIT

STANDARD

the name of the application.
Details: The name of the application may be changed, e.g. to distinguish between multiple instances. The application name is shown in the browser's title and in the maintenance view.

 

ui.autocomplete.max.results

positive integer

20

STANDARD

maximum number of results to be queried for elements with autocompletion feature in the web front-end
Details: This merely represents the default value for the web front-end and may be overridden by the user.

 

ui.display.format.date

string

dd.MM.yyyy HH:mm:ss

EXPERT

display format for date/time

 

ui.display.format.duration

string

HH:mm:ss

EXPERT

display format for durations

 

ui.help.link

string

https://documentation.novatec-gmbh.de/display/AUTOMAIT?src=automait-webapp

STANDARD

link to open in a new tab/window of the browser when calling "help".

 

ui.host.default.connection.type

[ HTTP, HTTPS, SSH ]

HTTPS

STANDARD

default connection type/method for newly created hosts
Details: This merely represents the default value for the web front-end and may be overridden by the user.

 

ui.host.default.gateway

[ true, false ]

false

STANDARD

states if a new host will automatically be created as 'gateway'
Details: This merely represents the default value for the web front-end and may be overridden by the user.

 

ui.host.default.lock.physical

[ true, false ]

false

STANDARD

states if a physical host will automatically be locked when executing plans on any of its child hosts
Details: This merely represents the default value for the web front-end and may be overridden by the user.

 

ui.host.default.port

positive integer (0-65535)

9999

STANDARD

default TCP HTTP/HTTPS listen port for newly created hosts
Details: This merely represents the default value for the web front-end and may be overridden by the user.

 

ui.host.default.remoteagent

[ true, false ]

true

STANDARD

states if a new host will automatically be created as 'remote agent'
Details: This merely represents the default value for the web front-end and may be overridden by the user.

 

ui.host.default.ssh.port

positive integer (0-65535)

22

STANDARD

default TCP SSH server port for newly created SSH hosts
Details: This merely represents the default value for the web front-end and may be overridden by the user.

 

ui.job.execution.charsets

string

US-ASCII,ISO-8859-1,UTF-8,UTF-16BE,UTF-16LE,UTF-16,IBM850

STANDARD

list of characters sets shown in the detail dialog of process executions used to decode stdout and stderr.
Details: This comma separated list is dynamically extended by the individual character sets of stdout and stderr.

 

ui.max.job.steps.fetch.size

positive integer

200

INTERNAL

maximum fetch size for job steps
Details: This sets the maximum on how many job steps will be fetched in job protocol as long the corresponding job is not terminated (only the last job steps will be shown then) When set to 0 unlimited job steps will be fetched (this may decrease performance for jobs with lots of steps)

 

ui.page.refresh.page.interval

duration

5s

INTERNAL

time between page refreshes

 

ui.pagination.model.list.default

positive integer

20

INTERNAL

default selected pagination size

 

ui.pagination.model.list.small.default

positive integer

10

INTERNAL

default selected pagination size for small data tables

 

ui.pagination.model.list.small.values

list of positive integers

${ui.pagination.model.list.small.default},50,100,500,1000

INTERNAL

list of pagination selections for small data tables

 

ui.pagination.model.list.values

list of positive integers

${ui.pagination.model.list.default},50,100,500,1000

INTERNAL

list of pagination selections

 

ui.variable.output.max.size

positive integer

150

STANDARD

maximum characters to be displayed when assigning values to variables

 

ws.client.xml.validate.request

[ true, false ]

false

INTERNAL

configures the XML validation of client web service requests
Details: The validation of outgoing client requests is disabled by default, since MTOM binary transfers would cause exceptions otherwise. This is due to the fact, that JAXP does not properly comply to MTOM-enabled web service requests.

 

ws.client.xml.validate.response

[ true, false ]

true

INTERNAL

configures the XML validation of client web service responses
Details: This enables/disables the validation of XML responses on the client-side.

 

xml.transform.format

[ raw, pretty ]

pretty

EXPERT

XML transformation output format to be applied to XML model documents, e.g. plans components etc.
Details: This setting affects the XML transformation applied to all model elements and should rarely be changed. XML documents may appear non human-readable, if raw format is chosen.

 

xml.transform.mapping.cts

url

/WEB-INF/config/mapping-component-types.properties

EXPERT

location of a transformation property file mapping component type names to components
Details: The default contains no mappings.
Example:

file:///data/mapping-component-types.properties

Note: Make sure to escape the spaces in the keys with backslashes. Example content: info.novatec.example#ProductComponentType=/examples/Product

 

xml.transform.mapping.system.services

url

/WEB-INF/config/mapping-system-services.properties

EXPERT

location of a transformation property file mapping system services names to components
Details: The default contains no mappings.
Example:

file:///data/mapping-system-services.properties

Note: Make sure to escape the spaces in the keys with backslashes. Example content: info.novatec.example#\ mySystemService=/examples/SystemService

 

xml.transform.preserve.cdata

[ true, false ]

true

STANDARD

configures the encapsulation of special code elements into CDATA blocks for better readability
Details: This setting is currently only enforced for 'inputText' elements contained within 'execNative'. However, the enforcement is obligatory, that is no matter if the input XML contains CDATA or not, the output will always be transformed into a CDATA element. Notice, that changing this property only affects upcoming model transformations and is not applied to existing model elements.

 

xsd.validation.stack.size

ByteSize

256K

EXPERT

stack size used for xsd validation threads
Details: The stack size needs to be adjusted if complex tasks would otherwise throw StackOverflowError.

 

xsd.validation.threads.keep.alive.time

duration

1m

EXPERT

maximum time an idle xsd validation thread is kept alive before deactivating it
Details: Threads are only deactivated/dropped, if the total number of current threads is still above the core size (which here means always, as the core size is 0).

 

xsd.validation.threads.max

positive integer

2

EXPERT

maximum number of threads used for xsd validation
Details: This number defines the maximum number of threads used to spawn concurrent xsd validation tasks, whose usage is triggered by @UseThread Annotation. A single thread is required per validation task.

  • No labels