Tivoli Workload Scheduler Alert:
Tivoli Workload Scheduler default certificates must be renewed!
Workload Scheduler provides a secure, authenticated, and encrypted connection mechanism for communication based on the Secure Sockets Layer (SSL) protocol, which is automatically used with Workload Scheduler.
Workload Scheduler also provides default certificates to manage the SSL protocol that is based on a private and public key methodology. If you do not customize SSL communication with your own certificates, Workload Scheduler uses the default certificates that are stored in the default directories to communicate in SSL mode.
They will expire on Feb 10 2014 but you need to renew them as soon as you could since eWAS automatic renewal feature can replace them before that date.
You need to perform the actions described below to avoid impact on your TWS environment.
IBM's Support team published the following Alerts for TWS and TWSz Customers:
TWS for z/OS default certificates needs to be renewed!
For your convenience this is a summary of additional Technotes published on that topic:
Technotes (troubleshooting) # 1660256
"TWS 8.5,8,5,1 and 8.6 GA release installation failure after December 10th"
Technotes (troubleshooting) # 1659608
"TWSServerTrustFile.jks is not updated by the TWS renewal certificates procedure. "
Technotes (troubleshooting) # 1657823
"TWSServerTrustFile.jks is not replaced by the TWS renewal certificates procedure."
Technotes (troubleshooting) # 1657223
"TWS Recovery procedure from the December 10, 2013 when TWS default certificates will be automatic renewed. "
Technotes (FAQs) # 1592682
"How to check the SSL certificate expiration date. "