Loading

Subscribe to this Blog

Your email:

Are you preparing for an implementation or upgrade?

Kronos Implementation Strategy

Download the WFM Implementation Strategy White Paper

About Bryan

Resume Pic of Bryan deSilvaMusician & Yin Style Bagua practitioner. Over twenty years of software implementations and upgrades, project management, systems and applications development experience with a current focus on ADP eTime & Kronos Timekeeper/HR systems implementation. 

The "Kronos Guy" Blog

Current Articles | RSS Feed RSS Feed

Kronos Workforce Central New Feature: Integration Manager

  
  
  
  

MH900408863Continuing with the series on New Features with Workforce Central (WFC) version 6.1 and later, I’d like to talk about one of my favorite products: Workforce Integration Manager (typically referred to as WIM). What is Workforce Integration Manager? For those upgrading, WIM and the WIM Interface Designer are the two components that now replaces the older product known as Connect. For those familiar with Workforce Timekeeper, remember the Custom URLs feature? It's similar, but much more than that. Continue reading to find out more!

So let us talk about some of the benefits of moving from Connect to WIM. WIM is embedded inside of the Kronos Suite now, so that means it, like other Workforce applications, is web-based. This means tighter integration of interfaces with the existing Kronos Suite. Let’s think cloud computing.  WIM is now part of what I’ll refer to as the “Kronos Cloud”. Being web-based, eliminates the requirement for an individual payroll manager’s PC to have separate software loaded and interfaces copied. If I am a payroll manager substitute, I no longer have to locate the payroll manager’s PC to run an interface. Any manager with access can just log in to WFC, run it, and then view results (all without leaving the "Kronos Cloud", WFC)! During the last upgrade I performed, (WFC 5.2 to 6.2), we discussed their preferences. We either could use a web-based integration manager, or an older version of Connect. Without hesitation they stated their preference, a web-based integration application!

So what can web-based interfaces do for a larger organization? Imagine this organization has the same payroll interface and different regions running payroll. The person responsible for running the payroll interface runs 1 out of 14 interfaces (the other 13 are run by other managers) hard-coded for a “region”. If I have 14 payroll managers (one for each region), this required 14 installations of the Connect interface. Now with WIM I only need ONE WFC installation and I can delegate which WFC Manager(s) can run or view interface results!

Key benefits you will receive with WIM when upgrading from Connect:

  • Any interface written in Interface Designer can be run or scheduled from WFC
  • Results can be visible via WFC (with a web browser) to any manger given access to an interface
  • No separate client to install and maintain for running interfaces
  • No longer a separate service pack to maintain for just running the interface product
  • Simplified scheduling of interfaces (tighter integration with WFC Event Manager)
  • Tighter integration with WFC (no required ODBC drivers) for input and output connections
  • It is no longer necessary to backup interfaces or tables separately from the WFC database

Let’s talk about what WIM can do for your organization. Or maybe you have already upgraded and just happened upon this article? If so, what do you like or not like about WIM vs. Connect? As always, we welcome your comments.

 

How should one design and build Kronos interfaces?

Kronos InterfaceWhat's the best approach to interfacing Kronos and my ERP? Should one use Connect/WIM or SQL? Integration Guru Eugene Harrison has an opinion.

Download the Kronos Interface Design Strategy White Paper Now!

Comments

Hi, 
A good feature in WIM is the possibility to connect into MSQL databases using Windows Authentication. I’m not sure if it was possible on the old version. To do that, do the following: 
 
Step 1) Copy sqljdbc_auth.dll file to \Kronos\jdk\jre\bin  
 
Step 2) Stop WFC Service  
 
Step 3) Change jboss service account to a Windows account with access on the database  
 
Step 4) Start WFC Service  
 
Step 5) Add a parameter on Connection String (integratedSecurity=true)  
 
 
The DLL I was able to find on: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a737000d-68d0-4531-b65d-da0f2a735707&displaylang=en If you not add the DLL, you will receive the error mentioned on: http://blogs.msdn.com/b/jdbcteam/archive/2007/06/18/com-microsoft-sqlserver-jdbc-sqlserverexception-this-driver-is-not-configured-for-integrated-authentication.aspx 
 
 
I submitted a RFE for Kronos with these steps. 
 
Rafael. 
Posted @ Thursday, December 29, 2011 5:54 AM by Rafael
I like the way the data sources are handled in setup. I can repoint my interfaces to a different database quickly and easily if I program them to take advantage of the feature.
Posted @ Wednesday, January 04, 2012 1:50 PM by Jeffry Charnow
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics