• Full logging of Process, Task and Error details.
  
  
• Built in automatic e-mails and text pager alert messages on error conditions.
  
  
• Auto-number feature that provides a unique value for each row during the transfer (i.e., primary key).
  
  
• Multiple source tables (i.e., INNER, LEFT and RIGHT OUTER joins).
  
  
• Use defined variables to facilitate common interfaces being called with different run-time parameters.
  
  
• Simple flow control (branching) based on the run-time status of jobs.
  
  
• Administrative programs to remotely control and monitor the progress of batches and jobs.
  
  
• Works with any ODBC (Level 2) compliant database.
  
  
• Tools to promote (or copy) interfaces between testing/development and production environments.

The SLIK server runs as an NT service. SLIK can talk to any ODBC compliant database running in any environment including AS400, UNIX, WINDOWS. Each batch runs in a separate thread (allocated from a thread pool). The number of threads is configurable to throttle the processing load on the machine. Interface definitions are held in the SLIK control database (currently MS SQL 7). SLIK reads all enabled definitions at run-time and schedules these internally. The SLIK server fires DCOM events to update any SLIK client(s) currently monitoring the servers processing.

SLIK takes a proactive approach  reporting all error conditions by e-mailing operators of any problems encountered.

All tasks are logged to a database and can be archived and later purged based on user-defined parameters.

If you are a JD Edwards OneWorld site SLIK provides comprehensive support of UBE's. It can also send rsh commands to any remote unix machine.

During database transfers a feature called Auto-number generates a unique sequential id that can be used as a primary key. 

A white paper on the SLIK architecture can be downloaded here »

A view of the architecture of SLIK can be found here »