DB2 Task Scheduler and web UI

Introduction
DB2 Task Scheduler allows to run and maintain administrative tasks executed after the predefined schedule. "Administrative task" is nothing more then SQL Stored Procedure designed to do some job. Task scheduler is not enabled by default, in order to activate it one has to configure it manually. DB2 task scheduler is similar to Oracle DBMS_JOB package. Unlike to DMBS_JOB it does not allow to execute SQL code directly, stored procedure should be created before.
There are several DB2 routines which allows to define new task, modify or remove existing task and monitor the current task status. Unfortunately, everything should be done manually. There is no IBM tool which provides  GUI to make this task less painful. Neither IBM Data Studio nor   IBM Data Studio web console do not have any windows or view giving access to task schedule. Job manager available in IBM Data Studio web console is a different solution, it has nothing in common with native DB2 task scheduler.
So I decided to fill the gap and create my own web application covering the DB2 task scheduler.
Installation
Read readme.txt, install maven, copy and paste pom.xml file, run:

maven compile

ignore all warnings and deploy target/db2jobscheduler.war.
After launching application the following screen should appear.

The application was tested with Tomcat 7 and Glassfish.
Project
It is an open source project created by virtue of MVC JythonUI framework. This framework has been significantly enhanced ever since.
Java source code (minimalistic) is available here. XML files defining user interface are available here. The most important part, Jython scripts containing all business logic, is available here. zxJDBC  package was used for accessing the DB2 database.
Source code structure
Java code serves only as a glue for initializing and starting the application. The development is focused on XML file describing the UI and Jython script file for business logic. It was the purpose of the JythonUI framework.

Functionality	XML files (UI)	Jython files (business logic)
Main menu	start.xml
Adding and modifying single source list	datasource.xml	datasourcelist.py
Data source list	connectiondef.xml	datasourcelist.py
List of tasks	tasklist.xml	shed.py
Adding and modifying single task	taskdescr.xml	shed.py
Current task status	taskstatus.xml	taskstatuslist.py
Helper for displaying a list of SP in the schema	proclist.xml	proclist.py
Helper for list of schemas	typesenum.xml	typedef.py
Helper encapsulating access to database		db2action.py
Helper encapsulating access to datasource definition		datasource.py

Functionality implemented

• Defining data source (s).
• List of tasks already defined. ADMIN_TASK_LIST
• Add new task. ADMIN_ADD_TASK
• Modifying existing task. ADMIN_TASK_UPDATE
• Remove task. ADMIN_TASK_REMOVE
• Task status. ADMIN_TASK_STATUS

Datasource defining

Displays list of datasource available now. Allows adding, modifying and removing datasource definition.

Administrative tasks maintaining

Displays list of scheduled task. Allows adding, modifying and removing tasks.

Task status

Current status of the tasks. 

List is displayed in chunks (there could be thousands of tasks executed already). List can be filtered (display a subset only) and sorted by any attribute.

Current status of the project

It is the first version with simplistic user interface. But all functionality of DB2 task scheduler is implemented.

Future development

• Improve user interface, help texts, direct connection to appropriate entries in DB2 Infocenter. 
• Security, user authentication.
• Encode database credentials, now password is saved as plain text.
• User authorization, only authorized user can add new task or modify existing.
• The same for datasource definition.
• Make task handling more convenient for the user. "Task" in DB2 is a stored procedure. Current implementation requires defining administrative stored procedure outside application (for instance by  using IBM Data Studio) then enacting it in the task scheduler application. Add simple text editor for creating and modifying stored procedure body in the application and deploying it to the database server without leaving the application.
• More convenient way for defining the task schedule. 
• Keep and maintain task schedule off-line repository. Additional database (for instance in the shape of XML files) containing administrative stored procedure body and task header for later reuse.
• Copy and paste tasks between databases - for instance copy task definition from test database to production database.
• More convenient way of disabling/enabling tasks.
• Export and import of administrative tasks. Task header and stored procedure body.