xUML Runtime Tool
The xUML Runtime Tool xuml-tool is a tool that provides means to work with xUML repositories. You can
System Requirements
This tool works on Linux and Windows operating systems, though not all commands are available on Windows.
Command | Linux | Windows | |
---|---|---|---|
| |||
| |||
| |||
| |||
|
On Linux, you need at least
Linux kernel 4.19
GLibc 2.28
Common Options
All commands of the xuml-tool accept the following common options:
Option | Description | Allowed Values | Example | |
---|---|---|---|---|
| Show either the help of the xuml-tool (including a list of all available commands), or the help of the selected command. |
| ||
| Show the complete help of the xuml-tool: all options, all commands. | |||
| Set the log level for the used command. | off | No logging. | |
critical | Only log critical errors. | |||
error | Log all errors. | |||
warning | Log errors and warnings. | |||
info | Log errors, warnings, and some general information (default). | |||
debug | Log errors, warnings, general and debug information. | |||
trace | Log a complete trace. | |||
| Disable all logging. | |||
| Enable debug logging. |
Commands
unpack
Unpack a given repository file to the destination directory. The repository will be unpacked to a sub-directory in the destination directory. The name of the sub-directory is derived from the repository file name.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file. | a valid path |
| |||
Path to a parent directory to extract the repository to. | |||||
| Create missing directories instead of aborting the command. |
| Do not create missing directories (default). | ||
| Create missing directories during the command. | ||||
| Specify whether to keep or remove temporary files used during the execution of this command. |
| Keep the temporary files. | ||
| Remove the temporary files (default). | ||||
| Specify the name of the deployment directory for the service. If not existent yet, the directory will be created automatically. | a valid directory name |
deploy
Deploy a given repository to a given destination. The repository will be unpacked to a sub-directory in the destination directory. The name of the sub-directory is derived from the composite service name.
Repositories that have been deployed with this command satisfy xUML Runtime requirements and can be run by starting the xUML Runtime as described on xUML Runtime Command Line Options.
They do not satisfy Bridge requirements, though, and cannot be managed with a Bridge. Do not use deploy
to deploy a repository to a Bridge data directory.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file. | a valid path |
| |||
Path to a parent directory to extract the repository to. | |||||
| Specify a value for setting
| localhost | Default value if not specified. | ||
a valid external host name | |||||
| Specify what to do if the repository being deployed is already existent in the target directory. |
| Remove the repository from the target folder if already existent, and deploy the new repository. | ||
| |||||
| Replace the complete repository, all files. | ||||
| Overwrite files of an already existing repository. | ||||
| Abort deployment if the repository is already existent (default). | ||||
| Set this value as a fix persistent state ower ID for this service. The owner ID can also be specified by environment variable | a positive integer | |||
| Replace global variables in setting values with the values specified in the given file. The file is a JSON file containing key/value pairs like
CODE
You need to manually create this file. | a valid JSON file containing the variable names and values | |||
| Create missing directories instead of aborting the command. | 0 | Do not create missing directories (default). | ||
1 | Create missing directories during the command. | ||||
| Specify whether to keep or remove temporary files used during the execution of this command. |
| Keep the temporary files. | ||
| Remove the temporary files (default). | ||||
| Specify the name of the deployment directory for the service. If not existent yet, the directory will be created automatically. | a valid directory name | |||
| Prevent certain files from being overwritten by the deployment. This option takes a file path relative to the instance home. It can be given multiple times, thus protecting multiple files. This option cannot be used together with If the protected file path already exists, it will not be overwritten. If it does not exist, it will be copied from the source. | a valid path |
|
Refer to xUML Service Configuration below for an explanation of how to provide global configuration variables for deployment.
run
Deploy and run a given repository. This command uses the deploy command described above in combination with Runtime command bridgeserver (see xUML Runtime Command Line Options).
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Provide the path to an an xUML Runtime configuration file containing Runtime command line options. The contents of such a file are described on xUML Runtime Command Line Options. This file must at least contain a minimal configuration consisting of
| a valid path to a configuration file | |||
| Specify a value for setting
| localhost | Default value if not specified. | ||
a valid external host name | |||||
| Specify what to do if the repository being deployed is already existent in the target directory. |
| Remove the repository from the target folder if already existent, and deploy the new repository. | ||
| |||||
| Overwrite files of an already existing repository. | ||||
| Abort deployment if the repository is already existent (default). | ||||
| Prevent certain files from being overwritten by the deployment. This option takes a file path relative to the instance home. It can be given multiple times, thus protecting multiple files. This option cannot be used together with If the protected file path already exists, it will not be overwritten. If it does not exist, it will be copied from the source. |
| |||
| Create missing directories instead of aborting the command. |
| Do not create missing directories (default). |
| |
| Create missing directories during the command. | ||||
| Start only the controler service of the specified service instance. | ||||
| Set this value as a fix persistent state ower ID for this service. The owner ID can also be specified by environment variable | a positive integer | |||
| Replace global variables in setting values with the values specified in the given file. The file is a JSON file containing key/value pairs like
CODE
You need to manually create this file. | a valid JSON file containing the variable names and values | |||
| Specify the name of the directory the service has been deployed to. | a directory containing a deployed service | |||
| Specify whether to keep or remove temporary files used during the execution of this command. |
| Keep the temporary files. | ||
| Remove the temporary files (default). |
dump-info
Display all information on a repository. This command prints the information returned by
show-addons
show-modules
show-notes
show-services
show-settings
show-ui
in one command.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Specify in which format the information should be displayed. |
| Display the results in a human-readable way. | ||
| Display the results in compressed JSON (default). | ||||
| Display the results in pretty JSON. | ||||
| Specify if passwords should be printed in clear text. |
| Hide passwords. | ||
| Display passwords (default). |
show-addons
Display the add-ons used by the repository.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Specify in which format the information should be displayed. |
| Display the results in a human-readable way (default). | ||
| Display the results in compressed JSON (default). | ||||
| Display the results in pretty JSON. |
Output
show-modules
Display information on the modules inside the repository.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Specify in which format the information should be displayed. |
| Display the results in a human-readable way (default). | ||
| Display the results in compressed JSON. | ||||
| Display the results in pretty JSON. |
Output
Output | Description | Values / Example | |||
---|---|---|---|---|---|
| Array containing model details within this repository as an array element each. | ||||
| Compilation timestamp. |
| |||
| Version of the xUML Compiler used for compilation. |
| |||
| Name of the module. |
| |||
| Name of the module source file. |
| |||
| Module type. |
| Module is a service composite. | ||
| Module is a library. | ||||
| Module version. |
|
show-notes
Display the documentation and model notes from a repository.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Specify in which format the information should be displayed. |
| Display the results in a human-readable way (default). | ||
| Display the results in compressed JSON. | ||||
| Display the results in pretty JSON. |
Output
Output | Description | Values / Example | |||
---|---|---|---|---|---|
| Array containing the service notes within this repository as an array element each. | ||||
| Service documentation text. |
| |||
| Origin of the documentation. |
| Model notes from main service. | ||
| Model notes from library or module. | ||||
| File name of the documentation in the repository. |
|
show-services
Display all information on services contained in a repository.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Specify in which format the information should be displayed. |
| Display the results in a human-readable way (default). | ||
| Display the results in compressed JSON. | ||||
| Display the results in pretty JSON. |
Output
Output | Description | Values / Example | |||
---|---|---|---|---|---|
| Array containing the service definitions within this repository as an array element each. | ||||
| Array of service endpoints (HTTP based services). | ||||
| Descriptor of the service (available for REST services only). |
| |||
| Name of the service endpoint. |
| |||
| Path of the service endpoint. |
| |||
| Version of the service endpoint (available for REST services only). |
| |||
| Name of the service as displayed in the Bridge UI. |
| |||
| Service port. |
| |||
| Service type. |
| Other service type than listed below. Service types that cannot be recognized by the xuml-tool will be listed as unknown. | ||
| xUML Controller service. | ||||
| |||||
| |||||
| |||||
| |||||
| JVM service for Java adapter. | ||||
| |||||
| |||||
| |||||
| SOAP shadow service for testing purposes. | ||||
| |||||
| |||||
| XSLT service for XSLT adapter. | ||||
| Relative link to the WSDL file (SOAP services only). |
|
show-settings
Display all information on the service configuration of a repository.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Specify in which format the information should be displayed. |
| Display the results in a human-readable way (default). | ||
| Display the results in compressed JSON. | ||||
| Display the results in pretty JSON. | ||||
| Specify if passwords should be printed in clear text. | | Hide passwords (default). | ||
| Display passwords. | ||||
| Specify whether to show incomplete configuration items or not. |
| Show all configurations. | ||
| Show all valid configurations. Exclude incomplete ones (default) | ||||
| Show all incomplete configurations. |
Output
Output | Description | Values / Example | |||
---|---|---|---|---|---|
| Array containing the service configurations as an array element each. | ||||
| Array of configuration name aliases. This array also includes the name property (see below). |
| |||
| Configuration category. In the Bridge UI, the configuration sections (see below) are grouped by this category (see xUML Service Settings). |
| |||
| Default value of the configuration item. |
| |||
|
| Label of the configuration item in the Bridge UI (default language). |
| ||
| External (friendly) name of the configuration item. Use this name to build the environment variable as described below (see xUML Service Settings). |
| |||
| Extended JSON schema of the configuration type. | ||||
| Type of the configuration. Possible types are: string, integer, boolean and password (masked string). |
| |||
| Configuration section within a category (see above). All configuration items of a section are listed together in the Bridge UI (see xUML Service Settings). |
|
show-ui
Display all information on UIs contained in a repository.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Specify in which format the information should be displayed. |
| Display the results in a human-readable way (default). | ||
| Display the results in compressed JSON. | ||||
| Display the results in pretty JSON. |
Output
Output | Description | Values / Example | |||
---|---|---|---|---|---|
| Array containing the UIs within this repository as an array element each. | ||||
| Name of the UI. |
| |||
| Relative path to the UI. |
| |||
| UI port. |
|
validate
Check the repository and report duplicate data items. This command is useful for support cases only.
Parameters / Options | Mandatory | Description | Allowed Values | Example | |
---|---|---|---|---|---|
Path to a repository file or to a deployed repository. |
| a valid path |
| ||
| Specify in which format the information should be displayed. |
| Display the results in a human-readable way (default). | ||
| Display the results in compressed JSON. | ||||
| Display the results in pretty JSON. | ||||
| Specify whether to keep or remove temporary files used during the execution of this command. |
| Keep the temporary files. | ||
| Remove the temporary files (default). |
Output
xUML Service Configuration
A service repository contains lots of tab files that describe the service. The xuml-tool provides you with several helpful options concerning the service configuration.
The tab files contain variable content that is substituted on deployment by default configuration values. You can overwrite those defaults by defining special environment variables on your system. The name format of these environment variables have to follow the following scheme:
XUMLT_S_<setting id>
.<setting id>
is the friendly id of a configuration item as displayed by theshow-settings
command, settings.name property of the output structure.In some cases, service configurations are missing friendly names. If their primary name would not form a safe environment variable name (e.g. name contains special characters or starts with a number), the configuration item will get a generated name.
Generated configuration names are stable. The generation algorithm uses a hashed primary name with a prefix (SETTING_
), and thus has minimal probability of collisions.Also, in rare cases, the repository may contain incomplete settings (without a
<Display>
section). These settings are skipped by the xuml-tool by default, and a warning is logged. If you want to see such settings, you can use the option--incomplete-settings
.You can replace global variables by values provided from a file with option
--global-variables-file
on thedeploy
and on therun
command.