(Diagram Source: AppWorx)The following is a brief overview of my experiences and research into the AppWorx application which interfaces with SunGard Higher Education or Banner. AppWorx is a job scheduling and application software for systems operators, programmers, and administrators while reducing IT costs.
AppWorx is unique since it follows a job process throughout the life cycle. AppWorx accelerates business processes and simplifies application management through schedule management through “point and click” instead of scripts which can be traced completely by the program’s administrator.
AppWorx allows for all the traditional batch management tasks, as well as submit jobs and view output. It allows the user to integrate batch processing requirements across many applications. For operations, AppWorx helps a data center with a “lights-out” processing.
Information knowledge, such as business rules, job parameters, passwords, log-ins, conditional processing logic, exception handling procedures, sit in the AppWorx repository simplifying the new process set up, change management, and production maintenance.
The following buttons/windows are running across the AppWorx screen which are listed in the following order: Explorer Window, Requests Window, Output Window, Modules Window, Chains Window, Agents Window, Agent Groups Window, Applications Window, AppMaster Administration Window, Calendars Window, Data Types Window, Export Window, Import Window, Libraries Window, Logins Window, Output Devices Window, Output Groups Window, Program Types Window, Queues Window, Roles Window, Role Authorities Window, Output Interfaces Window, Substitution Variables Window, Thread Schedules Window, and Users Window.
Audit ability is a key component to AppWorx which allows the Administrator to be able to see who accessed the system, what, and when they did. Encrypted passwords are undetectable - even when passed through the network.
Recorded history, audit function for tracking changes, audit reports, separation of production and development and QA environments, role-based security, encrypted server and database passwords, and immediate error alerts help to minimize the IT role in Corporate Reporting
It is recommended when assigning roles there is a good system of checks and balances that are customizable specifically to each user duties based upon the Administrator’s decision. Some times roles overlap their access. Inherited role access is when the functions of one role overlap with the function of another role. For example, if Role A overlaps with Role B, then the unshared functions in Role B will remain in a no-edit format to that user. Also, it is smart to assign more than one role to a user in which there is definition to the “edit” and “non-edit” roles. There is no limit to creating additional roles to the user.
Controls for AppWorx roles take place at these three levels:
- For the AppWorx client the control is in the user logins.
- For the objects in the AppWorx database the control of functions are with roles.
- For the Database the control of the database and hosts are through logins.
User access can further be restricted by designating edit authorizations to certain roles, but not to others. I find AppWorx very interesting and it is highly regarded in the IT world.
AppWorx is unique since it follows a job process throughout the life cycle. AppWorx accelerates business processes and simplifies application management through schedule management through “point and click” instead of scripts which can be traced completely by the program’s administrator.
AppWorx allows for all the traditional batch management tasks, as well as submit jobs and view output. It allows the user to integrate batch processing requirements across many applications. For operations, AppWorx helps a data center with a “lights-out” processing.
Information knowledge, such as business rules, job parameters, passwords, log-ins, conditional processing logic, exception handling procedures, sit in the AppWorx repository simplifying the new process set up, change management, and production maintenance.
The following buttons/windows are running across the AppWorx screen which are listed in the following order: Explorer Window, Requests Window, Output Window, Modules Window, Chains Window, Agents Window, Agent Groups Window, Applications Window, AppMaster Administration Window, Calendars Window, Data Types Window, Export Window, Import Window, Libraries Window, Logins Window, Output Devices Window, Output Groups Window, Program Types Window, Queues Window, Roles Window, Role Authorities Window, Output Interfaces Window, Substitution Variables Window, Thread Schedules Window, and Users Window.
Audit ability is a key component to AppWorx which allows the Administrator to be able to see who accessed the system, what, and when they did. Encrypted passwords are undetectable - even when passed through the network.
Recorded history, audit function for tracking changes, audit reports, separation of production and development and QA environments, role-based security, encrypted server and database passwords, and immediate error alerts help to minimize the IT role in Corporate Reporting
It is recommended when assigning roles there is a good system of checks and balances that are customizable specifically to each user duties based upon the Administrator’s decision. Some times roles overlap their access. Inherited role access is when the functions of one role overlap with the function of another role. For example, if Role A overlaps with Role B, then the unshared functions in Role B will remain in a no-edit format to that user. Also, it is smart to assign more than one role to a user in which there is definition to the “edit” and “non-edit” roles. There is no limit to creating additional roles to the user.
Controls for AppWorx roles take place at these three levels:
- For the AppWorx client the control is in the user logins.
- For the objects in the AppWorx database the control of functions are with roles.
- For the Database the control of the database and hosts are through logins.
User access can further be restricted by designating edit authorizations to certain roles, but not to others. I find AppWorx very interesting and it is highly regarded in the IT world.
