When you install our Power portfolio apps SIL Engine™ is also automatically installed to your Jira, a mandatory dependency for all our apps. SIL Engine™ is the layer that bundles together some of the most important features of the apps. Specifically, it offers:
- The Simple Issue Language™ (or SIL™) itself and on top of it the pluggable module that adds all Jira functionality. It is the variable resolver that able to resolve an issue from a given context, new specific types, and many additional routines dealing with various aspects of Jira.
- Utilities of any kind.
- STL extension (SIL Template Language) used when rendering mails for instance.
- Common ground for all features: SQL access, LDAP access, remoting capabilities, and so on.
- SIL™ editor.
For our paid apps one additional app is installed. Warden app keeps track of the license status for all installed apps.
The configuration of any power portfolio app actually happens at two levels:
- Global (within SIL Engine™) – where you configure all the above-mentioned features.
- Local (within the respective app) – where you configure the app features.
In other words, an SQL pool is defined at global level, and it can be shared between our apps and used by them. The configuration of that pool must cater the usage from all power portfolio suite apps installed on that system.
Installing and updating SIL Engine™
SIL Engine™ is a usual app. The installing and updating procedure is the same as for any app, and is described in the Atlassian documentation.
Sometimes we release only SIL Engine™ to fix bugs, add improvements, and so on. We only guarantee upward compatibility within the same major / minor version. To avoid unexpected results follow the UPM, install only compatible versions of SIL Engine™, and try to keep it at the last available compatible level. Doing otherwise may result in Jira install failure.
SIL Engine™ is provided free of charge. The general terms governing licensing are provided in our EULA.
- SIL™ configuration — Basic configuration page lets you specify a directory on the disk where you will keep your SIL™ programs, the charset used to interpret those files, and the cache size of the SIL™ scripts.
- SQL data sources — These pages represent a guide for SQL connection pool definition, declared either in the Apache's Tomcat context.xml (JNDI) or directly via our pages and dialogs.
- Mail configuration — The mail sender configuration refers the mail templates directory and templates localization.
- Asynchronous runner — Thread pool configuration is easy, however you must understand the implications of each parameter since they may affect the tasks that are run in the background.
- Remote systems — Using remote systems you are able to execute SIL™ programs on some other Jira instances running SIL™. These are usually other Jira or Confluence.
- LDAP configuration — Starting with version 4.0 we support multiple LDAP servers.
- Script storage — 'Virtualization of a SIL™ script' means that a script may be stored either on disk (default) or in the database (optional).
- Custom Field Mappings — SIL™ custom field mappings are used to translate the custom field value into a valid SIL™ value.
- Configure Jira logging — There are two ways of configuring logging for our apps. One is permanent, and survives Jira restarts, the other is just temporary and is reset either from the Jira's UI or at the next restart.
- SMS Sender configuration — As of today, we provide support for two Romanian SMS gateway providers.
- Webhooks configuration — Webhooks give you the possibility to run existing SIL scripts from outside of the Jira / Confluence instance, by using a REST/HTTP client and retrieve the results of the run script.
- Integration with Stride and Slack — Starting with version 4.0.13 of Power Scripts™, we have added the ability to use SIL™ scripts in order to send messages to Stride and Slack.