Y2K on 01/14/2014 for Workforce Central?
I sat there alone, waiting. One phone hung on a wall in the adjacent hallway. A second phone, a vintage 1999 Audiovox model 9000 was prone on the kitchen table. We didn’t know if either would work, but if they did, the incoming barrage would come from our customers with NEC Automated Fingerprint Identification Systems (AFIS). Their software had lines of code with dates that represented the year with just 2 digits, i.e. MM/DD/YY. With that limitation, the system would interpret the year 2000 as 1900, and no one was quite sure of the impact. We did our best to patch the systems, but with thousands of lines of code, remediation was uncertain. I looked up at the clock. The 20th century was coming to a close, at least in my time zone. Hey, some thought the world was ending… From the adjacent living room in the old drafty farmhouse, I could hear the countdown from Times Square. Revelry and New Year’s kisses ensued for those participating, but in my apartment the celebration was bittersweet solitude.
One week from today, on January 14, Oracle will release JRE 1.7.0_51. The release changes the way signed applets are processed by a number of Java applications, including Workforce Central 6.1, 6.2, 6.3, and 7.0, which run the JRE 1.7 family. In other words, if you don’t apply a service pack or patch to Workforce Central, users accessing the system via workstations won’t be able to.
If you are running applications in the JRE 1.6 family, you are not impacted by this change. For more information and the latest release dates for patches and Service Packs, visit our Customer Portal and search on Technical Advisory TA101146.
It won’t be the and of the world, but why not fix it while you still have time?