Runtime Framework

The runtime is the main part of AREasy application, having capability to assume input parameters, to parse them and to compose runtime syntax to call different actions. The actions are already implemented Java classes, having a special coding format which are registered in the runtime configuration files.

When the runtime is called will be created an instance of Runtime Manager component that could run in one of these three options described before: server, client or standalone. If you want to execute an action (so to start the runtime in client mode or standalone) you need to specify all necessary parameters to define the complete command, and the most import is to specify the action name which can be pointed out using -action parameter name.

In case you need help to see how the command line looks like you need to execute help action or help option (parameter): areasy -action help -call <action name> or areasy -action <action name> -help. When you are starting runtime manager in the client mode you can use two optional parameters to specify the server host and the TCP/IP port for connectivity to the runtime server. So, in this scenario the runtime server is running on a specific machine and the runtime client is called from another machine (e.g. your workstation). To start the runtime in the standalone or client mode always you must call an action, specifying parameter -action and then a value indicating the action name registered in the runtime configuration sectors. This configuration is stored in properties files (the main file is cfg/default.properties) and the action name is given by app.runtime.actions properties. AREasy runtime is coming with a special set of already implemented actions to manipulate data and workflow objects from an AR System server or from ITSM applications. To start the execution of an action which should be connected to the AR System server you must use specific action parameterization to identify a specific AR System server or to configure the runtime instance (in cfg/default.properties configuration file) to have a permanent connection to AR System server. The most significant out-of-the-box action are:

• System actions - the runtime delivered a set of actions to work with the runtime container: start, stop, status, echo, clean, help, etc. As special workflows, system actions include a specialized one to install AREasy modules, plugins and service packs without to have downtimes in AREasy server instance. Also, there is a system action that can change online and in real time runtime configurations.
• Productivity actions for administration – AREasy provides a complete set of actions to manage Foundation layer from AR System server. These actions have been designed allow ARS administrators to bulk configure licenses, permissions, functional roles and support group membership to specific users. The most important actions provided in this area are:
• set/remote system licenses
• set/remote application permissions and the corresponding licenses
• set/remote unrestricted access
• set/remote restricted access for one or many company entities
• set/remote functional roles
• upload and rename support groups
• set/remove support group membership for specific user

These actions really are useful when you have to do specific admin operations many times or when you want to provide deployment packages for an ARS implementation, building procedure to upload and to initiate foundation layer. For instance if you want grant ten thousand Remedy users with different type of licenses (system and application licenses) you can create an excel file, put all the details there are then you can launch AREasy in runtime mode to execute this grant action (-action admin.set.system.license and/or -action admin.set.application.permission) reading data from that excel file.

• Data management – the runtime is able to execute standard data manipulation actions like:
• Data insert in any Remedy form, taking into account the Remedy server-side workflow and disable it.
• Data update using complex search and identification keys
• Data remove from any Remedy form (with or without workflow)
• Data merge taking into account all merging options supported by targeted AR System server.
• ITSM operations – AREasy is coming with large set of actions to manipulate ITSM specific data. The most important action are:
• Assign a specific support group to an incident
• Set incident owner
• Create/update configuration items
• Make relationships between two CIs
• Create/replace/remove people relationships with different CIs
• Remedy development objects operations - The actions from this area are able to export and import workflow definitions in standard format and also binary format. More than this, AREasy is able to extend the manipulation actions to the field level (but in binary format) and you’ll be able to transfer one or more fields (and other workflow objects) from one server to another.
• Specific system administration operations – The runtime include pre-prepared actions for AR System services administration like:
  • arsystem service monitor
  • email engine monitor
  • license usage monitor and reporting

Additionally, AREasy provides wrappers that can connect and read data from different data-sources and then to can call specific actions that will use extracted data from sources to compose the complete command. In addition, AREasy includes an advanced wrapper that makes possible to manage AREasy actions and to execute them using a specific GUI and related workflow developed as a Remedy deployable application.