Optional Parameters during Initial Configuration¶
In addition to the mandatory init parameters, there are also optional init parameters that can be used to set certain configuration values during the initial configuration. These options are described on this page.
Enabling the Messaging REST API in init.conf (since version 7)¶
By default, the new sedex client behaves the same as the old one, i.e. the new REST API is not enabled. In order to be able to use the new "sedex Messaging REST API" instead of the classic file system interface, the following parameters must be included during initialization phase
To enable the Messaging REST API:
File: /path/to/sedex-data/init.conf
...
MESSAGING_INTERFACE_REST_API_ENABLED=true
To route all incoming messages to the rest api:
File: /path/to/sedex-data/init.conf
...
MESSAGING_INTERFACE_SELECTOR_RULE_DEFAULT=rest-api
Messaging Rest API and file-system mixed
If some messages are to be received in the file-system and some via rest-api, the configuration for incoming messages is described in Configuring the Messaging REST API
Configure Messaging Rest API later on
The Messaging Rest API can be activated any time after the initial configuration (see Configuring the Messaging REST API.
Defining an outgoing HTTP proxy in init.conf¶
If an HTTP proxy is required to access the Internet, the proxy server can be configured in the init.conf file for the initial configuration phase. This configuration is then included in the generated configuration of the sedex Client.
Example:
File: /path/to/sedex-data/init.conf
...
OUTGOING_WEB_PROXY_HOST=proxy.example.ch
OUTGOING_WEB_PROXY_PORT=8080
OUTGOING_WEB_PROXY_USER=example-user
OUTGOING_WEB_PROXY_PASSWORD=1234
You have no username/password?
If no username is required, the two optional parameters OUTGOING_WEB_PROXY_USER and OUTGOING_WEB_PROXY_PASSWORD can be omitted.
Configure HTTP proxy later on
An HTTP proxy can also be configured any time after the initial configuration (see Configuration Options - Available Configuration Parameters).
Disabling the sedex Webservice Proxy in init.conf¶
If the functionality of the sedex Webservice Proxy for secure access to defined Web services is not needed, it can be deactivated with the init.conf file for the initial configuration phase. This configuration is then included in the generated configuration of the sedex Client.
Example:
File: /path/to/sedex-data/init.conf
...
SEDEX_WSPROXY_START=false
Default value is true
If this parameter is missing in init.conf a default value of "true" will be set in the configuration file.
Re-enabling sedex Webservice Proxy
The sedex Webservice Proxy can be activated any time after the initial configuration (see sedex Webservice Proxy - Basic Configuration).