1. Introduction to AppWorx
AppWorx provides a complete background-processing management system. With AppWorx, you can do all the traditional batch management tasks, as well as submit jobs and view output. However, instead of writing scripts to perform tasks, you create AppWorx modules that run programs. You combine modules to create chains. You create a schedule for each chain (or for each module if you wish) using a full complement of scheduling tools including custom calendars and execution conditions.
As with all modular systems, you create individual objects once, then use them in different combinations to accomplish a variety of tasks. In the context of batch management, this can save you hours of time compared to writing, debugging, and maintaining scripts. A diagram of the AppWorx modular approach to operations is shown in Figure A.
A Different Way of Thinking -
In a traditional operations environment, scripts drive operations. Scripts incorporate the information required to run one or more programs on a set schedule, direct output, and handle exceptions. The problem with scripts is the required time maintaining them when the system changes. For example, if a printer definition changes, you must change it in every script. AppWorx takes the individual components of a script such as programs, schedules, printers, and variables, and lets you define them as discrete objects. You can then combine the objects in an unlimited number of combinations to handle your operations. The advantage is being able to change an object in one place, and have the changes roll over to every use of the object.
 |
| Figure A. AppWorx uses a modular approach to replace the tedious tasks of writing and maintaining scripts. |
---------------------------------------------------------------------------------------------
2. Objects in AppWorx
1. User
The Users are created for Controlling access to AppWorx. You can assign names, access permissions, user options, and roles to AppWorx users.
2. User Authority
User authority is control user access to Application Manager window and can give Users and privileges for objects.
3. User Group
User group is control access to all areas of Application Manager. In a traditional system, you create a groups of User, Output, Devices and Applications. User groups can contain any combination of objects, and objects can be assigned to any User group.
4. Agent
Agents are instances of application manager. An agent is installed on each machine where new tasks are executed. An agent can be Local agent or Remote agent.
5. Module (Job)
Module is the basic building block in AppWorx. For each program which you want to run (for example: FTP, application, database load), you must create a module. A module contains all the information required to execute a program. Modules are run both individually and as components of AppWorx chains. Furthermore, a module can be a component of as many chains as you wish. If you change a module definition, the change is applied to every chain that includes it.
6. Chains (Process Flows)
Process flows are the combination of one or more jobs(Concurrent Programs from EBS), which are scheduled as per requirement. For running the chain, specific eligibility of its component and condition must meet.
7. Chain Components
Chain components are modules and chains assigned to the chain. When you add a component to a chain, AppWorx creates a pointer from the chain to the module or chain instead of adding a copy of it. This is in keeping with the AppWorx object-oriented approach. If you edit a module or chain definition, the update is effective immediately for all chains that include it.
8. Notification
Application Manager includes the notification which alerts you to unusual task runs. If you want to be notified when task does not completed or not completed task in expected time. You can receive notification by email.
9. Substitution Variables
It stores the values that can be used in Jobs and Process Flows. You can add the SQL statement to pull the value from database, variable name such as #XXOrganization_id, in prompts and execution conditions assigned to Jobs.