Navigation: » No topics above this level «

Background Scripts

In this screen you can register and change background scripts. Open screen in browser Open Form

With the help of background scripts management processes and other time-consuming manual processes can be automated.

An example of a background script that automated an administrative process, is ‘BUBS_EMPTY_INTERFACES’. With this script the contents of the ERP interface tables are removed.

If a background script requires parameters for processing they can be specified in the part of the screen with the name ‘Script Parameters’.

The registration of background scripts is a typical activity for application developers. See the warning under Application Development.

Background Scripts Screen

The meaning of the entry fields is:

Code	The unique code of the script.
Description	The description of the script.
Type of Program	The type of program, including: •Oracle PL/SQL; for executing database packages, ideally suited for database changes. •JJava Class; for executing a Java program, ideally suited for executing mathematically intensive or non-database processes. •System Shell; for executing everything that cannot be executed as Oracle PL/SQL or Java class.
Required Capacity Scheduler	The required skills of the scheduler to be allowed to process background jobs based on this script.
# Days to Keep	The minimum amount of days after which the background jobs based on this script may be automatically removed.
# Versions to Keep	The minimum amount of versions after which the background jobs based on this script may be automatically removed. The oldest versions are deleted first.
Runs Alone	The maximum number of simultaneously running background jobs based on this script is only one, when checked.
Rerun on Success	A successfully completed background job based on this script will automatically start again when checked.
Rerun on Warning	When a background job based on this script was completed with a warning, it will automatically start again when checked.
Rerun on Error	When a background job based on this script was completed with an error based on this script it is automatically restarted when checked.
Rerun Every (sec)	The amount of time in seconds after which a background job based on this script will automatically be requested, if one of the options ‘Rerun on Success ’, ‘Rerun on Warning’ and/or ‘Rerun on Error’ is checked.
MIME Type Output	The MIME type of the output of this script, for example ‘text/html’.
MIME-type Log File	The MIME type of the log output of this script, for example ‘text/html’.
Executable Program	The name of the executable program or the code of the script to be executed in case of Oracle PL/SQL. The following variables in the code are replaced by their respective values during the execution of the background script as a background process: •:bjb_id: ID of the background process. •:bjb_seq: number of the background process. •:sdr_code: code of the background planner. •:sdr_omschrijving: description of the background planner. •:gbr_naam: user that requested the background process.
Program is Expression	Indicates that the program text is a SQL expression when checked
Code	The unique code of the script parameters.
Description	Description of the script parameters.
Sort Order	Numerical value that determines the order in which the script parameters will appear in an entry form.
Required	Indicates if it is obliged to specify a value for the script parameter.

The meaning of the other fields:

Number of Executions	The total amount of finished background jobs that were based on this script.
Total Execution Time (sec)	The total time in seconds that background jobs have run, based on this script.
Minimum Execution Time (sec)	The minimum time in seconds that a background job has run, based on this script.
Maximum Execution Time (sec)	The minimum time in seconds that a background job has run, based on this script.

Scripts of the category ‘System Shell’ are executed with the applicable system shell (command.com for Windows 95, cmd.exe for other Windows versions and /bin/ksh for UNIX and Linux).

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Invantive Estate

Background Scripts

Important Safety and Usage Information