Glossary

  • Advanced Business Application Programming. A programming language used by SAP products.
  • An Object that defines an Alert that can be fired by a Job or Workflow (Modern UI) / Process Definition or Chain Definition (Classic and Legacy UI).
  • In the Modern UI, an Advanced Schedule is a cyclic calendar which forces a Job or Workflow to be executed repetitively. When a Job or Workflow Definition is run with an Advanced Schedule, the corresponding Job or Workflow will be restarted automatically by a Job Server according to the frequency defined in the Submit Frame. In the Classic and Legacy UI, this is referred to as a "Submit Frame."
  • A way of executing native processes on UNIX and Windows computers without having to install a Platform Agent. See also Proxy Platform Agent.
  • An Object that defines escalation routes for Alerts. If an Operator does not respond to an alert in a timely fashion, an Alert Escalation can notify a different user.
  • An Object used to forward Alerts by email. This name is used only by the Modern UI. In the Classic UI and Legacy UI, see Email Alert Gateway.
  • In the Classic UI and Legacy UI, an Application is a group of related Objects. Applications can be exported and imported. In the Modern UI, Applications are referred to as "Folders."
  • A proprietary API developed by Redwood Software BV together with SAP AG to allow connections from SAP AS ABAP to RunMyJobs. In RunMyJobs, BAE objects are named SAP Inbound. Also referred to as the "BAE API."
  • An older name for a type of IBM computer. Other names include the IBM eServer iSeries (iSeries), IBM i5, i5/OS, and IBM i.
  • An Object that specifies which Events should be audited.
  • A log containing audited Events.
  • Business Automation Enabler. An interface that lets SAP AS ABAP systems to connect to and control RunMyJobs. Avaiable only to SAP BPA customers.
  • A type of SAP job that processes incoming data. A directory is designated in SAP as the Batch Input Folder. Applications can send data, in an SAP format called iDocs, to the SAP System by placing the files in this directory. The ABAP program RSBDCSUB reads the batch input folder and submits a new SAP job for every file it finds.
  • SAP's Business Technology Platform.
  • A string that uniquely identifies an Object in RunMyJobs.
  • A compressed archive containing RunMyJobs Object definitions.
  • Computer Center Management System. Part of an SAP solution that provides common functionality such as user management, monitoring, and background jobs.
  • A background request in SAP's CCMS for the execution of one or more ABAP programs and/or repeating system commands.
  • Central monitoring system. The SAP monitoring architecture assumes that one system in your system landscape is the central monitoring system (CEN). The monitoring information for your system landscape is collected by this system and displayed in the Structure Alert Monitor.
  • An instance of a Chain Definition. Classic and Legacy UI only.
  • An Object that groups multiple Process Defiinitions and control the order in which they execute. Referred to as a "Workflow Definition" in the Modern UI.
  • A call to a Process Definition or child Chain Definition inside of a Chain Definition. Referred to as a Job Call in the Modern UI.
  • In SAP terminology, a self contained unit in an R/3 system with separate master records and its own set of tables. An SAP Mandanten identified by a 3 digit (numeric) field in RunMyJobs.
  • The Concurrent Manager manages your concurrent requests in the Oracle Applications suite. All concurrent programs that can be started from Oracle's web submit screen (for submitting concurrent programs) can also be scheduled by RunMyJobs.
  • A named, encrypted Object that centralizes all of the information necessary to create an authenticated connection with a particular third-party application. Connections are currently only used by Connectors, but you can store other types of credentials with a Credential.
  • Optional conditions that In Parameters must fulfill. See Parameters.
  • SAP's Cloud Platform Integration. Also known as SAP Business Technology Platform (SAP BTP).
  • An Object used to store simple login information in a secure and reusable way, without requiring process developers to know the logins and passwords for connected third-party systems. See also Connection.
  • An Object that defines a type of Credential. Different credential protocols are available for various operating systems and databases.
  • A type of report generated by SAP BusinessObjects. RunMyJobs can import and schedule Crystal Reports.
  • SAP objects that interface with third-party solutions. In SAP BusinessObjects, these can be exported as shell scripts, which can then be scheduled on Platform Agents.
  • When an Object is selected in a scrollable list, a Detail View displays on the right side of the tab, providing comprehensive information about that Object.
  • An Object that contains optional documentation for another RunMyJobs Object.
  • An Object used to forward alerts by email. This name is used only by the Classic UI and Legacy UI. In the Modern UI, see Alert Gateway.
  • Lets you define the email address of someone who should be notified when a particular Alert Source raises an Alert. You can chain Escalations to deal with situations where the first person to recieve a message does not respond promptly.
  • An Object that represents something that happened, such as a file arriving in a dirctory or a Job (Modern UI) or Process (Classic and Legacy UI) finishing. There are two kinds of Events: Raise Events and Wait Events.
  • An Export Rule Set contains a set of rules to be used when you export or promote a set of Objects.
  • Optional "plug-in" software packages that let you connect to other systems, set up inbound REST services, and more. Extensions that let you connect to other systems are called Connectors. You can install Extensions from the Catalog.
  • A File Event Definition is not a type of Event Definition. Rather, it is a rule associated with an Event Definition. A File Event Definition lets you specify that its parent Event should be raised when a file arrives in a particular directory.
  • In the Modern UI, a Folder is a container for a group of related Objects. Folders can be exported and imported. In the Classic UI and Legacy UI, Folders are referred to as "Applications."
  • If a field supports glob matching, that means you can use * to match any number of characters, and you can use ? to match a single character. Use * at the beginning and end of the pattern if you want to match a particular set of characters somewhere in a string instead of trying to match the whole string.
  • The SAP Generic Request and Message Generator. You can use the GRMG to monitor the availability of technical components and entire business processes. GRMG is suitable both for technical monitoring and for application monitoring.
  • SAP's HANA Cloud Integration platform. Used in SAP S/4HANA Cloud.
  • SAP's HANA Cloud Platform. Also known as SAP Cloud Platform Integration (SAP CPI) or SAP Business Technology Platform (SAP BTP).
  • SAP's HANA Enterprise Cloud. For older application servers such as SAP NetWeaver.
  • An Import Rule Set contains a set of rules to be used when you import Objects.
  • An administrative unit that groups components of an SAP System. The SAP System ID.
  • In the Modern UI, a Job is a single automated task. Jobs can be added to Steps in a Workflow. In the Classic UI and Legacy UI, a Job is referred to as a "Process."
  • A Job Call is an Object that is created when you run a Job Definition. It contains information about that specific execution of the Job Definition, including its Status. You can view Job Calls in the Monitor screen.
  • In SAP, a job count is a number that represents the ID of a job in an SAP System.
  • A Job Definition contains everything RunMyJobs needs to execute a Job. In the Classic and Legacy UI, this is referred to as a "Process Definition."
  • In SAP, a job ID is a number that represents the ID of a job in an SAP System.
  • In the Modern UI, a Job Server is the part of RunMyJobs that executes Job and Workflow Definitions. A Job Server typically connects with a separate system (such as a computer inside your network or an SAP instance) and performs its work there. In the Classic and Legacy UI, this is referred to as a "Process Server."
  • A Keep Clause defines how many executed Jobs (Modern UI) or Processes (Classic and Legacy UI) are kept in the system, or how long they are kept in the system.
  • An Object used to store RedwoodScript code so that it can be easily used by multiple Job Definitions (Modern UI) or Process Definitions (Classic and Legacy UI).
  • A license key provides you with access to a particular feature. Your license can include multiple license keys.
  • You can use a Lock to make sure particular Jobs (Modern UI) or Processes (Classic and Legacy UI) do not run concurrently.
  • RunMyJobs provides a number of ERP interfaces, utilities, and system tools in packages called modules. Your license specifies which modules are available to you.
  • A Monitor Alert Source uses Escalations to raise Alerts when a monitored component reaches a specific severity.
  • An object which lets you get information about the current state of a system, database or other application.
  • A monitor node is an element in the Monitor Nodes screen (Modern UI) or Monitor Tree screen (Classic UI and Legacy UI). A leaf node is a monitor node that does not have any children.
  • In RunMyJobs, an Object is basically anything you can configure. Job and Workflow Definitions, Job and Workflow Calls, Process Servers, and Queues are all examples of Objects. Objects can be organized into Folders (Modern UI) or Applications (Classic and Legacy UI), imported and exported, and edited in XML.
  • An Operator Message is an Object used to inform Operators about an Event.
  • A string that identifies a particular RunMyJobs instance. The Originator ID consists of the portion of a RunMyJobs instance URL after the domain, but with underscores instead of forward slashes. For example, if the URL is https://domain.runmyjobs.cloud/example-inc/test, the Originator ID is example-inc_test.
  • A Parameter is a variable value that is used by a Job or Workflow (Modern UI) or a Process Definition or Chain Definition (Classic UI and Legacy UI). A Parameter can be an explicit value such as a string of characters or a number, an output from a different process, or an expression.
  • A concept you can use to organize and isolate RunMyJobs Objects. Partitions are generally used for security purposes.
  • A function used to calculate dates.
  • The SAP PI interface lets youconnect to NetWeaver AS Java systems and control communication channels.
  • A Platform Agent is a small piece of software that is installed at the operating system level on a server inside the customer network. A Platform Agent can manage communication with sever-based parts of RunMyJobs, issue instructions to the local operating system, submit and monitor Jobs, handle File Events, and monitor local information such as CPU load and paging rate. There are different Platform Agents available for different operating systems.
  • In the Classic and Legacy UIs, a Process is an instance of a Job Definition, Chain Definition, or Report that has been scheduled to run, is running, or has already run.
  • A Process Definition is like a template for a specific process you want to automate. A Process Definition includes everything RunMyJobs needs to do a particular unit of work, including input files, output directories, scheduling information, and any required credentials. In the Modern UI, a Process Definition is referred to as a "Job."
  • In the Classic and Legacy UI, a Process Server is the part of RunMyJobs that executes Process and Chain Definitions. A Process Server typically connects with a separate system (such as a computer inside your network or an SAP instance) and performs its work there. In the Modern UI, this is referred to as a "Job Server."
  • The process of exporting Objects from one RunMyJobs instance and importing them into another RunMyJobs instance. For example, you might develop Objects in a Development instance, then promote them to a Test instance for testing, and finally promote them to the Production instance.
  • A way of executing native processes on UNIX and Windows computers without having to install a Platform Agent. See also Agentless Platform Agent.
  • Jobs (Modern UI) / Processes (Classic and Legacy UI) are executed in Queues. A Queue can be open or held. While a Queue is held, no new processes are started in the Queue.
  • Raise Events and Wait Events are not specific types of Event Objects. Rather, they are fields on a Job or Workflow Definition (Modern UI) / Process or Chain Definition (Classic and Legacy UI). Such a Definition with a Raise Event will raise that Event when the Job/Workflow/Process/Chain reaches a particular status.
  • In the Modern UI, a reaction Job Definition is a Job Definition that is executed in response to specific conditions. You might, for example, want to create a reaction Job Definition that generates an email or an Operator Message if a Platform Agent Job Server runs a check on an Oracle database and that check fails.
  • In the Classic and Legacy UI, a reaction Process Definition is a Process Definition that is executed in response to specific conditions. You might, for example, want to create a reaction Process Definition that generates an email or an Operator Message if a Platform Agent Process Server runs a check on an Oracle database and that check fails.
  • Redwood Server is the server-based part of RunMyJobs, as opposed to portions of the RunMyJobs software that run inside a customer network (such as Platform Agents). In an SaaS installation, Redwood Server is the portion of the solution that runs in the cloud.
  • A hierarchical set of key-value pairs used to control various settings in a RunMyJobs instance.
  • When you are setting up a Production instance of RunMyJobs, it is a Redwood best practice to also have instances named (for example) Development and Test. In such situations, the Development and Test instances of RunMyJobs are referred to as "remote systems."
  • An Object that stores the settings required to generate a specific summary of a situation or status. For example, Reports are frequently used to generate a monthly summary of Jobs (Modern UI) / Proceses (Classic and Legacy UI) that reached status Error.
  • A Resource is simply a named entity that represents a required feature, such as a printer, a particular OS, or an application. You can use Resources to make sure that Jobs (Modern UI) / Processes (Classic and Legacy UI) that require a feature are sent only to Job Servers (Modern UI) / Process Servers (Classic and Legacy UI) that support that feature.
  • An RTX file is an XML file that uses the Redwood RTX schema. RunMyJobs uses RTX format to store table data for various reasons. RunMyJobs can display RTX files in an interactive user interface that allows filtering and sorting.
  • The Secure Gateway is a designated Platform Agent that enables software inside the customer network to securely communicate with the server-based components of RunMyJobs. The Secure Gateway runs inside the customer network, behind the customer firewall, and communicates with the RunMyJobs server components via HTTPS. All traffic between the customer network and the RunMyJobs server passes through the Secure Agent. All communication is initiated from inside the customer network, for additional security. The Secure Gateway is only available to RunMyJobs SaaS customers.
  • A Spool Host is a Platform Agent that stores output from ERP processes. Spool Hosts let customers view and analyze ERP spool data from the cloud-based console without the data itself leaving the customer site.
  • A Step is a portion of a Workflow Definition (Modern UI) / Chain Definition (Classic and Legacy UI) that consists of one or more Job Calls (Modern UI) / Chain Processes (Classic and Legacy UI). Steps execute sequentially.
  • In the Classic and Legacy UI, a Submit Frame is a cyclic calendar which forces a Process to be executed repetitively. When a Process Definition or Chain Definition execution is submitted with a Submit Frame, the corresponding Process will be restarted automatically by a Process Server according to the frequency defined in the Submit Frame. In the Modern UI, this is referred to as an "Advanced Schedule."
  • A System User is an unnamed user with API access only.
  • An Object used to store values. Similar to a table in a database or a spreadsheet in Microsoft Excel.
  • This is a user account that is not tied to a specific user. Technical user accounts are useful in situations where something needs to be done, but a credentialed user is not available. Make sure your RunMyJobs administrator has access to this technical user account.
  • Raise Events and Wait Events are not specific types of event Objects. Rather, they are fields on a Job or Workflow Definition (Modern UI) / Process or Chain Definition (Classic and Legacy UI). Such a Definition with a Wait Event will not execute until that Event is raised.
  • In the Modern UI, a Workflow is a way to group multiple Job Calls and control the order in which they execute. This is referred to as a "Chain" in the Classic UI and Legacy UI.
  • In the Modern UI, a Workflow Definition contains everything RunMyJobs needs to execute a Workflow. This is referred to as a "Chain Definition" in the Classic and Legacy UI.