How can I use pinnacle21.conf with ECLI?

Learning extra parameters to simplify ECLI validations

Philipp Strigunov avatar
Written by Philipp Strigunov
Updated over a week ago

The following parameters can be provided in a pinnacle21.conf file which must be located in the same directory as the executable JAR.

Parameter

Command line

Default

Description

api.key

--api.key

None

Key used to validate the request on the server.

web.host

--web.host

None

Address where the request is sent.

enterprise.project

--project

enterprise_cli

Name of the project that contains the data to be validated.

enterprise.study

--study

enterprise_cli

Name of the study that contains the data to be validated.

enterprise.group

--group

enterprise_cli

Name of the group that the request is associated with.

create.always

--create.always

Yes

When set to yes, CLI will create the project and study with names specified in --project and --study if any of them don't already exist.
With --create.always=no CLI wouldn't create new projects and/or studies if it cannot find any project and/or study with provided names. It will return "Failed core process" error. However, if Project and Study do already exist and the data package doesn't, CLI will still create a new data package.

validator.http.max.socketTimeout

Not available

20000 (ms)

If validation fails with errors due to timeout, setting this value to 50000 may allow validation without error.

validator.http.max.requestTimeout

Not available

20000 (ms)

If validation fails with errors due to timeout, setting this value to 50000 may allow validation without error.

default.http.max.connectTimeout

Not available

20000 (ms)

If validation fails with errors due to timeout, setting this value to 50000 may allow validation without error.

default.http.max.requestTimeout

Not available

20000 (ms)

If validation fails with errors due to timeout, setting this value to 50000 may allow validation without error.

default.http.max.socketTimeout

Not available

20000 (ms)

If validation fails with errors due to timeout, setting this value to 50000 may allow validation without error.

define.http.max.requestTimeout

Not available

15000 (ms)

define.http.max.socketTimeout

Not available

15000 (ms)

default.http.proxy.host

Not available

default.http.proxy.port

Not available

default.http.proxy.username

Not available

default.http.proxy.password

Not available

A sample pinnacle21.conf file:

web.host = "https://{your␣company}.pinnacle21.net"  
api.key = {API key from the Enterprise Server}
group = enterprise_cli

default.http.proxy.host ={proxy␣server}
default.http.proxy.port = {proxy server port}
default.http.proxy.username = {proxy user name}
default.http.proxy.password = {proxy password}

validator.http.max.socketTimeout = 50000
validator.http.max.requestTimeout = 50000
default.http.max.connectTimeout = 50000
default.http.max.requestTimeout = 50000
default.http.max.socketTimeout = 50000
define.http.max.requestTimeout = 50000
define.http.max.socketTimeout = 50000


See also CLI Parameters for command-line configuration options.

👣 What's Next?

Email questions or feedback to support@pinnacle21.atlassian.net.

Did this answer your question?