Qorus developer tools for the Qorus Integration Engine.
This extension makes it possible to easily create, deploy, and test Qorus interfaces directly from the Visual Studio Code editor.
It is a perfect tool for creating no-code solutions for the Qorus Integration Engine. The Qorus Developer Tools allow to create building blocks that can be reused later and setup an initial configuration for them.
Version 2.3.23 overview - What's new:
- Passwords for Qorus with special characters are now supported
Existing passwords with special characters need to be updated manually in the environments view
Version 2.3.22 overview - What's new:
- Fixed a bug that would cause the webview to crash after creating new class with connectors from an FSM state
- Replaced the X icon with a trash icon on all FSM states
Version 2.3.21 overview - What's new:
- Fixed inherited config items not being deleted when the parent config item is removed
Version 2.3.20 overview - What's new:
- Moved the buttons inside class connections dialog under the box, so that the full connector name can be seen at all times
Version 2.3.19 overview - What's new:
- Fixed a bug that prevented setting and saving inherited config items to
- Qorus Webview
- Configuration manager helps to easily manage configuration data of the project (no need for manual work with qorusproject.json).
- Support for creating of Qorus interfaces such as jobs, services, steps, workflows, classes, mappers etc.
- Connecting building blocks using class-connections manager allows to create no-code solution for complex enterprise integration scenarios
- Release package management
- Hierarchy view of all interfaces in the project
- and more
How to use
There are three main user interfaces to use the extension:
- Hierarchy view
The webview can be opened using the Qorus icon, which placed in the hierarchy view and also in the VS Code action bar or by qorus webview command. The webview can be used for creation/editing of Qorus interfaces, project configuration, release package management and much more.
Creating Qorus mapper using the provider API support:
The hierarchy view provides an overview of the open project. In the
interfaces tab all interfaces that are currently present in the project and based on the
src directories configuration are shown. They can be sorted according to the folder hierarchy on the disk or according to interface types. Also the hierarchy view provides quick actions in order to perform operations on the server or make changes on local files such as deploying an interface to an active instance or creating a new interface.
instances tab of the hierarchy view displays all configured environments with instances and links to them based on the configuration file (qorusproject.json).
The interpretation of the data is depicted by a tree with three levels:
- development environments (here
- Qorus instances (here both environments have two Qorus instances)
- URLs: the Qorus instance "main" URL at the first position and then any custom URLs, if any (here only the 'dev 1' Qorus instance in the 'dev' environment has any custom URLs). Custom URLs are supposed to serve as shortcuts for opening project related sites - simply by clicking (the opened tool/browser depends on the operating system).
The corresponding tree looks as follows:
* main local Qorus instance
* main URL (http://localhost:8001)
* local Qorus instance
* main URL (https://localhost:8011)
* dev 1
* main URL (http://188.8.131.52:5678)
* abc (sftp://abc@def/ghi)
* xyz (sftp://xyz@uvw)
* dev 2
* main URL (https://184.108.40.206:6789)
There are several possible deployment methods:
- Deploy the file currently active in the editor. This can be done using keyboard shortcut
Ctrl+Alt+o or by using command
Qorus: Deploy current file from the Command Palette.
- Use the
Qorus: Deploy file command from a file's context menu (in the Explorer view).
- Use the
Qorus: Deploy directory command from a directory's context menu (deploys all deployable files in the directory including subdirectories).
- Use the Deploy buttons shown when hovering mouse cursor over an interface or a directory in the Qorus Interfaces tree view.
The deployment is targeted to a Qorus instance that is currently set as active.
A Qorus instance can be set as active in the Qorus Instances tree view, either from the context menu of a Qorus instance node (second level node) or simply by clicking a Qorus instance node directly.
Active Qorus instance is marked by a green light icon. At most one Qorus instance can be active at a time. Setting another instance active deactivates the previously active instance.
If a Qorus instance requires authentication (and the user has not yet logged in that instance) the
Set as active Qorus instance command opens a login dialog. After a successful login, the instance will become active. Also login can be performed in the webview.
Authentication tokens are stored, so that next time logging-in is not required.
(Tokens are only stored in memory while VSCode is running, not persistently.)
Context menus of instances in the Qorus Instances tree view contain also the following commands:
- Login without setting the instance active.
- Logout (if the instance was active it becomes inactive).
- Set the instance inactive while staying logged in.
If there can be a heavy filesystem traffic in a part of the project folder, such as running a build with make,
exclude that part from file watching otherwise the extension may get frozen:
- open settings (File -> Preferences -> Settings)
- switch to the Workspace tab
- search for "watcher exclude"
- add a pattern there
If you are not using the Qore programming language and would not like to see messages relating to missing Qore infrastructure for the Qore Language Server, unset the
Qore: Use QLS setting in Settings (or add
"qore.useQLS": false in