Below you will find links to some of the TSuite products in action. If you click on the actual T-Suite icon it will open a new window to explain more.

TSuite was built to assist organizations in processing batch information from one information source to another completely independent system at the same time. TSuite is agnostic to both the source and the destination as long as both can be accessed using a standards based provider. The rich SQL interface allows users to refine and optimize the request. Fields can be split to add even more functions. The destination logic can be based on a true test condition path, a false condition path or a perform always path. The full request is logged and the TWatcher function of TSuite provides for a mechanism for those conditions that need further investigation in order to be processed.

Iconography

T-Suite's iconography was created to provide a clear and understandable User Experience.

The JAAT logo is comprised of two main colours.

JAAT Green is used for all icons of a general nature. Icons such as save, edit, delete, previous, next etc… are in JAAT Green. This colour is also used to highlight active job, batches, monitors and other active grid functions.
JAAT Orange is used for functions that require the user to engaged and pay head to the function. Functions like Run, Stop, and Exit are in JAAT Orange as a visual cue of its importance.

The components

T-Loader		The T-Loader component is the main component and it drives all other components. This is where the user creates a job to be scheduled and executed. The job definition includes the source collection method, source data separation, output field mappings and destination logic. The job definition can then be scheduled for execution. Advance features such as; testing mode, error log review, history log review are inherit in the T-Loader component of T-Suite Conditional job execution that all allows for a SQL condition check. The result of the condition then provides for a true path SQL function, a false path SQL function and an execute always path SQL function. This creative approach provides for intelligent updates and of course full logging of all SQL paths.
T-Batch		T-Batch allows you to create a script of jobs to run. The script can be controlled by following a path of successful completions or execute specific T-Loader jobs based on failed execution.
T-Scheduler		Once a job is created and a schedule has been defined, The T-Scheduler service then submits the jobs for execution based on the user defined schedule. T-Scheduler is only setup once and is a fully compliant Windows Service
T-Runner		T-Runner is the component that reads the job file, executes the job file and writes to the appropriate logs. T-Runner can be engaged manually by the user or automatically by the T-Scheduler service component.
T-Watcher		T-Watcher is used to monitor the logs of any job. The user can set the timing for T-Watcher to check the logs. T-Watcher can be on as many machines as required so your users can monitor logs and address those entries that need user intervention to complete. Since the T-Suite tool is a row by row tool, the user can adjust the row logic of a failed entry and resubmit for reprocessing. All successful insert and updates are processed and any failed rows are available for edit and maintenance to the T-Watcher component.
T-Transform		T-Transform is the work horse that allows you to manipulate your data before T-Loader is engaged . This provides for data efficiency and ease of job development. Remove all the data issues prior to needed the data for down stream processes. T-Transformwill allow you to; Extract header information from the title row to make columns Perform functions at the row level Perform functions for all rows Perform functions for columns Perform functions for specific columns
T-Monitor		T-Monitor will watch for files to added to windows directories. You can select what directory to look for, what type of file to look for and/or what pattern of file to look for. Once the file is dropped in the directory you can have it execute a T-Loader job or a T-Batch job.
T-Launcher		The drag and drop function of the T-Suite product. It can be used to launch a T-Loader job or a T-Batch Job.
T-Output		The ability to create a flat file output from one or many input sources. Most common formats are CSV and XML.

Click HERE to return to the TSuite Main Page.

Click HERE to contact JAAT Solutions to learn more about the T-Suite product.

T-Launcher Screenshots

T-Launcher

T-Launcher is the drag and drop facility for the T-Suite product. Any Comma separated Variable and/or spreadsheet source job can be utilized by the T-Launcher function.

Main Screen

This is where a user select the job or batch to be processed.

Drag and Drop Screen

The user then drags the CSV or Spreadsheet file to the green area to be processed.

Click HERE to return to the TSuite Main Page.

Click HERE to contact JAAT Solutions to learn more about the T-Suite product.

T-Loader Screenshots

	T-Loader This is the main job creation and designer of the T-Suite Product
Main Screen From this screen the user can filter what jobs they wish to look at and which jobs they wish to work on. The user can create new jobs, delete exiting job, edit the job details and / or execute the jobs for processing. Statistics are provided for run dates, and successful completions.
Step 1 This is where the user provides a meaningful name for the job and an extended descriptions. Optionally the user can choose a group and sub-group category for future filtering.
Step 2 This is where the user defines both the source and destination database connectors. Database connectors can be traditional databases, Comma Separated Variable text files or an XML file.
Step 3 This is where the source pull can be modified to meet the job's requirements. Any valid SQL statement can be used to isolate the number and types of rows requested for processing.	.
Step 4 Further processing can be done at the column level to isolate columns for additional processing. This is very useful when one column may contain more compartmentalized data within it.
Step 5 This step allows for the setting of default values, forcing elements to be required and further definition of column type of data.
Step 6 This step is where all the previous steps join to provide the commands to be fed to the destination database. You will notice that their are 4 tabs. Conditional test. The question must come back with a true or false (0,1) Execute if true. This block of SQL will be executed if the condition test comes back true. Execute if false. This block of SQL will be executed if the condition test comes back false. Execute always. This block of SQL will be executed regardless of the value of the condition test in tab ONE.
Step 7 This final step allow you to flag this job to be seen by the T-Watcher function and/or the T-Monitor function. Only jobs that have a CSV or Spreadsheet source database source are visible to T-Watcher and T-Monitor.

Click HERE to return to the TSuite Main Page.

Click HERE to contact JAAT Solutions to learn more about the T-Suite product.

T-Watcher Screenshots

This function comes with the T-Suite product. It also can be installed separately, on any user's computer to watch for specific jobs that they need to monitor. For example you have customer service needing to monitor customer bills coming into the system. Any data from the source that is not executed properly will alert the T-Watcher clients on the network. The user can then open T-Watcher to handle the handle for reprocessing with complete confidence.

T-Watcher

This functions watches the job queues and reports on any errors during processing. User can then just adjust the found errors and process again.

Main Screen

Historical errors

This screen is shown by clicking on the number of historical errors column. From this screen you can select several rows or just select one row to be edited.

Editor

From this screen the user can edit the row that faulted. The status of the error will changed to pending so it can be processed again.

T-Watcher allows good rows to pass to the destination database while maintaining any rows that may have failed. The user can then, correct the errors for reprocessing.

Click HERE to return to the TSuite Main Page.

Click HERE to contact JAAT Solutions to learn more about the T-Suite product.

T-Transform Screenshots

	T-Transform One of the gems of the T-Suite platform. This function will allow clients to manipulate source text files for job processing. As you will see, the ability and the power of the function is remarkable and very flexible.
Main Screen This is where a user select the T-Transform definition to be worked on. From here a user can Add Edit Delete Make inactive / active Run the transform
Step 1 This steps allow you to name the transform, and to provide a detailed description. Each job can also be assigned a group name and/or a sub-group name for future filtering reference.
Step 2 This is the step where you select the input file to be transformed and its field separator. At each step the user is able to preview the result of any decision made.
Step 3 T-Transform will allow you to split a large CSV file into smaller files if required. This is very powerful if the source file has more than one group of data held within it.
Step 4 This step allows you to globally deal with all rows in the inbound CSV file. In the example to the right, we have deleted all blank lines.
Step 5 The identification of the column headings is very important for downstream processes. The ability to glean, the column headings out of the actual file or to create your own column headings is what is accomplished at this step. T-Transform is capable of reading any row to garner the column headings.
Step 6 You can also read any row to create new columns based on the values seen in a row. For example if a row contained the dates of the report but no date columns were present in the larger data-set, a user could read the row, extract the dates and create new columns based on a value read from the row. A very powerful but easy to use function within the T-Transform job definition.
Step 7 This is a global step to deal with columns with the inbound source CSV. You could delete columns, add columns, clean columns or rename columns at this step.
Step 8 This step allows a user to manipulate specific columns. In the example to the right, we have set a default value to a column if the column is blank.
Step 9 This is the final step that allow the user to validate the transformation logic. You can browse for other sample CSV files and it will run through the logic to validate how your definition will be executed.