- Created by Annegret Bernhardt, last modified by Kirstin Seidel-Gebert on Dec 20, 2022
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
This option is only available for type xuml-service (= containerized xUML services).
The administration application allows you to change the configuration of a containerized xUML service.
The administration application allows you to change the configuration of a Docker container. You have two options to open the configuration of a container: | |
| |
In the Configuration section you can directly modify xUML service settings . When you save your changes, the container will be re-created and restarted. Changes are possible after the first deployment of the containerized service . | |
You can change a setting in field Current Value. If you want to reset the setting to its default, use the Reset icon . The Default Value is displayed next to the current value. Click Save after you have completed your changed. Please note:
| |
As there are many available settings, use the filter field to search for the setting you want to modify. The content of the filter field is applied to the columns Category, Section and Key. | |
Click the filter icon to display the extended filter options:
If a filter is applied, the filter icon changes: . | |
In the main filter window, you can reset all selected filters. Click icon Reset Filter. In the filter option window, you can also reset the selection. |
xUML Service Settings
The settings are categorized into the following:
- Global Settings: In this category, you can change setting values that are global to the xUML service. Deployment information retrieved with deployment macros can be overwritten in this category, too (see Global Settings below).
- Add-ons: In this category, the settings comprise add-on related values like tagged values, interface URIs, and others. For instance, data of the SQL adapter, File System adapter, Timer, or SOAP service request may be overwritten. For more details, refer to the example in Add-on Settings.
You can modify settings of a service no matter if the service is running or if it has been stopped. Saving the changes triggers a re-create and restart of the container. Settings will be stored, so if you stop the service and restart it, the settings are restored.
If you delete a service, all settings are lost and cannot be recovered.
Global Settings
Settings Group | Setting | Description | Allowed Values | |
---|---|---|---|---|
Settings / Deployment Macros | Service Composite | |||
getCompositeCategory | Value returned by Action Language macro getCompositeCategory(). Initial value of this setting is the category specified in the service details (see Managing the Service Details). | any string | ||
getCompositeName | Value returned by Action Language macro getCompositeName(). Initial value of this setting is the service name. | any string | ||
getCompositeVersion | Value returned by Action Language macro getCompositeVersion(). Initial value of this setting is the service version in the service details (see Managing the Service Details). | a version string | ||
PAS Platform | ||||
AuthenticatorEnabled | Specify whether users are allowed to identify themselves using an x-pas-user header instead of a bearer token. For compatibility reasons true (x-pas-header allowed) is the default option but this is deprecated and may lead to security issues. If you do not rely on the x-pas-header, we recommend setting this option to false. | true | Allow using an x-pas-header or a bearer token for authentication (default). | |
false | Authentication only by bearer token. | |||
PasSecurityService::allowAnonymous | Specify whether anonymous users (no PAS users) should be allowed to send requests to the PAS BPMN service. In contrast to anonymous users, PAS users are identified by a bearer token or x-pas-user header). If this setting is set to false, requests of unauthenticated users will return HTTP error 401. This setting does not disable any role configuration within the BPMN. If there are lanes configured in the BPMN, the service can only be accessed by authenticated users. | true | Allow anonymous access (default). | |
false | Access for identified users only. | |||
Service | ||||
<service settings> | In your Designer service, you can define name-value pairs using the setting macro in an implementation. These values can be modified here. |
Add-on Settings
Each xUML service adapter has its own settings that are initialized in the xUML model and can be changed in the configuration.
If you are running an xUML service that is connecting to a database backend, you can modify the tagged values of the database interface respectively dependency. Before starting a deployed xUML service that connects to a database backend, you may want to redefine required database parameters.
SQL Adapter Connection Settings
Key | Value |
---|---|
DBType | Name of the SQL Service component, e.g. SQLite |
DBName | Name of the database, e.g. ScheerACME_Customers |
Connection Pooling | This tagged value controls the connection pooling. If true, each connection is put into a pool after use. If an SQL adapter requires a connection, it is taken from the pool. If no connection is available, a new connection is being created and put into the pool after use. The time the connection is kept in the pool depends on the other pooling parameters. |
Max Connection Reuse | This tagged value controls how often a connection can be re-used. After the connection has been re-used for maxConnectionReuse , it will be closed and not put back into the pool. This feature has been introduced because some databases had problems if the connection was re-used too often. Value -1 means the connection will be re-used forever. In this case you should define reasonable values for maxConnectionAge or maxConnectionIdleTime (see above). Note that the pooling is implicitly switched off, if maxConnectionReuse is set to 0. |
Max Connection Age | After a given connection age (in minutes) the connection will be closed and removed from the pool. |
Max Connection Idle Time | Connections not used for the time specified (in minutes) will be closed and removed from the pool. |
For more information on the SQL adapter settings (other tagged values, default values, ...) refer to the xUML Services Reference Guide.
SQL Adapter Authorization Settings
These settings allow you to adapt the SQL database user and password of the xUML service.
Key | Value |
---|---|
customers: DBUser | Database user |
customers: DBPassword | Database password |
Other Add-on Settings
Generally, most of the add-on settings that are related to an xUML Service Adapter have a corresponding tagged value in the component diagram. Refer to the documentation of the corresponding adapter for these settings.
Find below a list of other add-on settings and their description. For the sake of completeness, we also mentioned settings coming from the model for some setting groups (see column Specified in Model on).
Settings Group | Setting | Specified in Model on | Description | Allowed Values | |
---|---|---|---|---|---|
Dump Configuration | Caught Error Code | Only dump errors with the specified code.Specify a Bridge user defined error code. This setting takes no effect if Dump not Caught Errors/Dump Context on Error is disabled. | a string | ||
Caught Error Domain | Only dump errors of the specified error domain. Specify a Bridge user defined error domain. This setting takes no effect if Dump not Caught Errors/Dump Context on Error is disabled. | a string | |||
Dump Caught Errors: enabled | Enable/Disable writing an error dump file for errors that have been caught in the xUML service model. This setting takes no effect if Dump not Caught Errors/Dump Context on Error is disabled. | true | Create a service dump for caught errors. | ||
false | Disable service dump for caught errors (default). | ||||
Dump not Caught Errors: enabled | Enable/Disable writing an error dump file at all. This setting corresponds to the xUML service preference Dump Context on Error (refer to Integration Platform User's Guide > Preferences of an xUML Service). | true | Create a service dump for not caught errors (default). | ||
false | Disable service dump for not caught errors. This disables error dump at all. | ||||
Persistent State | Owner | Change the name of the persistent state object owner here. Each persistent state object is owned by a persistent state engine. If you change the owner setting, all subsequently created persistent state objects will belong to the new owner. All existing persistent state objects of the old owner will not been processed anymore by this service as they belong to a different owner now. | |||
Worker Limit | Composite | Specify the worker limit. Workers defines the maximum number of parallel threads used to process pending events. The default setting is 5, which is used if none or 0 workers are configured. The implications of more or less workers are discussed in xUML Service Reference Guide > Performance Considerations of Persistent State . | |||
REST Service HTTP Server | Descriptor: Cache Control: value | Specify the Browser caching options for the YAML file by setting a value for HTTP header | |||
Test Tool: Cache Control: value | Specify the Browser caching options for the Swagger UI by setting a value for HTTP header Cache-Control .For more information on this header, refer to Cache-Control on the Mozilla pages. | ||||
REST Service Base | <your service name>: enabled | Switch the service port on / off. When the service port is deactivated, it will not accept any request anymore. | true | Service port is active (default). | |
false | Service port is deactivated. | ||||
<your service name>:JSONComposerOptions: compact | REST Service | Specify the JSON compose option for the REST request/response. When jsonCompact is true, the JSON composer will generate compact JSON, otherwise it will generate pretty JSON. jsonCompact defaults to true - also on re-compile of an older model with Builder as of 7.0.0-beta3. | true | Generate compact JSON (default). | |
false | Generate pretty JSON. | ||||
<your service name>: JSONComposerOptions: keepNulls | REST Service | Specify the JSON compose option for the REST request/response. When jsonKeepNulls is true, attributes of the REST response object having NULL values will be rendered to the REST response, otherwise they will be left out completely (refer to xUML Service Reference Guide > NULL Values ). | true | Render attributes with NULL values to the REST call. | |
false | Leave out attributes with NULL values in the REST call (default). | ||||
<your service name>: MaximumConnections: | Change the maximum number of parallel requests to the service port. | ||||
<your service name>: Port | Change the port the xUML service listens to. The original value comes from the SOAP service component. | a valid port number | |||
<your service name>: ResolveHostnames | Define whether the host name is logged to the service logs instead of the IP address. | true | Resolve the IP address to the hostname in the service logs (default). | ||
false | Write the IP address to the service logs. | ||||
SOAP HTTP Server | Allow Tracing | Switching tracing on / off. | true | The Runtime returns tracing information on request (default). | |
false | The Runtime does not return tracing information. | ||||
Maximum Connections | Change the maximum number of parallel requests to the service port. | ||||
ResolveHostnames | Define whether the host name is logged to the service logs instead of the IP address. | true | Resolve the IP address to the hostname in the service logs (default). | ||
false | Write the IP address to the service logs. | ||||
<your service name>Port | Change the port the xUML service listens to. The original value comes from the SOAP service component. | a valid port number | |||
SOAP HTTP Server Request | <your service name>: <your port type>: enabled | Switch the service port on / off. When the service port is deactivated, it will not accept any request anymore. | true | Service port is active (default). | |
false | Service port is deactivated. | ||||
<your service name>: <your port type>: URI | Component diagram | Change the service URI. The default value comes from the component diagram of the xUML service. | |||
SOAP HTTP UI Server | Library Cache Control: value | Specify the Browser caching options for the UI files (HTML, CSS, ...) by setting a value for HTTP header | |||
WSDL: <your service name> | WSDL: <your service name> host | Specify the host name of the server for the xUML service WSDL. | ${server_hostname} | Name of the Bridge node instance the service is deployed to. | |
a fully qualified system name |
Expert Mode
Use the checkbox Expert Mode to display further options:
Option | Description |
---|---|
RAM | Use the slider to increase or decrease the RAM of a service. This option allows you to avoid that one service can comsume all resources. Default is 256 MB, the RAM maximum is 4 GB. You can change the RAM in steps of 64 MB. |
Name | If you want to set xUML service settings for containerized services from the outside using the xuml-tool, you will need the Name (= friendly Id) as the environment variable. Refer to Integration Platform User's Guide > xUML Runtime Tool for details. |
- No labels