Managing your solution: Self-Help

Owned by Radu Dumitriu (Deactivated)
Last updated: Nov 19, 2024 by Jonathan Muse
4 min read

 

SIL Engine Lifecycle

Typically, your engine is always on. However, there might be situations where you need to complete an engine operation in Self-Help > SIL Engine Operations. Here, you can query the engine status and restart it.

 

image-20240607-152544.png

 

There are rare occasions when the UI works but attempts to contact the engine result in HTTP 401 errors. In these instances, reconfiguration may be required. Only press the Reconfigure button in these instances or when instructed by support. After pressing Restart or Reconfigure, allow up to three minutes for the engine to be operational.

Monitoring and Global Status

The global status handler displays:

  • System availability.

  • Maintenance operations.

  • Operational problems.

Use this page for instructions on how to remotely monitor your SIL Engine.

Backup and Restore

Backup and restore is used for for SIL Scripts and the accompanying files, including silprograms and kepler directories.

 

The following video explains these operations:

Engine Resize

When additional resources are required, request an engine resize by completing the form in Self-Help > Engine Resize. You can also review this page for more information.

Messages

When messages are available, they appear in administrative pages, similar to the example below. To read the messages, open Self-Help > Messages

 

 

Atlassian API Token

Starting with version 3.0.14, administrative functions that require an Atlassian API token were added to the system. The functions were furthers refined in subsequent versions and in version 3.2.0 we added the ability for the tokens to be auto-removed from the product after a certain period.

To obtain an Atlassian token, visit:

https://id.atlassian.com/manage-profile/security/api-tokens

To obtain an Organizational token, see:

Manage an organization with the admin APIs | Atlassian Support

Notes:

  • Atlassian Tokens are specific to individuals and should not be shared.

  • Organizational tokens should be treated as any secrets; they should not be shared.

  • The token must belong to a user with Jira administrative privileges otherwise the administrative functions will fail.

To use the token, simply enter the email address for the user who generated the token and the token itself.

The token is stored securely and is used for administrative functions. If these functions are not used, the token is not required.

 

If you specify the dates, the tokens will be removed from our product at that date. Note that the tokens may still be valid, so read the “Expires on“ more like “auto-remove after”.

We do not check the validity of the tokens and we do not communicate with Atlassian products on this matter. It is your responsibility. Specific administrative functions notify you in the documentation if a token is required or not. Therefore they are not mandatory to be filled in unless you use those administrative routines / functions.

TLS / SSL - Securing your endpoints

Starting with version 3.0.13, a method for configuring private keys and certificates was added to create a more secure Cloud environment.

Please check this page for details.

 

Peacock