Modified on by Donatella
a new STE course is now available on 09/18 about the topic of "TWA default certificate expire on Febr 10 2014" !
TWS default certificates expires on Feb 14 2014: Procedure on how to renewal them
Live Event - https://sas.elluminate.com/d.jnlp?sid=2012136
Playback Recording - https://sas.elluminate.com/dr.jnlp?suid=D.7BDE1758280DA52FF1095F7148CE88&sid=2012136
Please notice the following IBM Alert:
IBM ALERT: Tivoli Workload Scheduler default certificates expire on 10 february 2014.
Tivoli Workload Scheduler provides a secure, authenticated, and encrypted connection mechanism for communication based on the Secure Sockets Layer (SSL) protocol, which is automatically installed with Tivoli Workload Scheduler.
Tivoli Workload Scheduler also provides default certificates to manage the SSL protocol that is based on a private and public key methodology.
Tivoli Workload Scheduler Distributed and zOS uses SSL by "default" for different TWS communications into TWS network.
If you did not customize SSL communication with your own certificates, Tivoli Workload Scheduler uses the default certificates that are stored in the default directories to communicate in SSL mode. The default certificates expire on February 10, 2014.You need to follow instructions on the following Alert to avoid broken communications at that time.
IBM team published the following Alert for TWSd and TWSz Customers:
Tivoli Workload Scheduler default certificates expire on 10 February 2014
Tivoli Workload Scheduler for z/OS default certificates expires on 10 February 2014
The alerts contain the information needed to manage that scenario along with links to IBM STEs for TWSd and TWSz customers which will be held in April by the IBM support team.
You can contact IBM support for any doubt/questions and also leverage IBM TWA Forum to post your questions (Visit IBM TWA Forum!
Do you want to know the "Next Feature" in the
world of Workload Automation/Scheduling?
Follow the new Webcast meeting for Demo day Sprint3
Save the Date
Octber 11th2012 - 3 PM CEST, 1 PM GMT, 9 AM ET (USA)
For registration send email to
The solution IBM Tivoli Workload Scheduler Plug-in for Netezza has
been published in the ISM Library.
Use the IBM® Tivoli Workload Scheduler Plug-in for Netezza® to manage the Netezza software, hardware, and databases using Tivoli Workload Scheduler. In this way, you take advantage of all the Tivoli Workload Scheduler scheduling functions to manage these jobs. Installing the Plug-in in your Tivoli Workload Scheduler environment, you can define, schedule, and monitor Netezza jobs using Tivoli Workload Scheduler. The IBM Netezza data warehouse appliance is a high performance, integrated database appliance that provides high performance, extensive scaling, high reliability, and ease of use. The Netezza appliance uses an architecture that combines current trends in processor, network, and software.
A typical Business Scenario is the following:
A large financial company performs business every day in many different countries. To succeed, the company manages and processes data from databases with hundreds of billions of rows and hundreds of terabytes. Their database management is based on a Netezza appliance solution, which allows data warehouse appliance to architecturally integrate database, servers and storage components into a single unit. The big data amount managed by the company is extremely important to analyze the historical trend of the financial operation and to perform specific actions in the financial market. The process that backs up the databases overnight, in a Netezza environment, is performed manually by an operator. To reduce costs and to ensure that the SLA requirement of having data backup available every morning is satisfied, the company wants to automate this process.
Using IBM Tivoli Workload Scheduler Plug-in for Netezza, the company can satisfy this objective because the product helps it to automate and control the entire process.
Want to know the "Next Practices" in the
world of Workload Automation?
Join us for the New Tivoli Workload Automation
Release and get to see the new Demo!
Save the Date
19th2012 - 3 PM CEST, 1 PM GMT, 9 AM ET (USA)
For registration send email to
To submit job streams from your mobile, even if you do not have any experience with Tivoli Workload Scheduler.
Launch the Self-Service Catalog from your mobile device by connecting to the following URL:
where host_name and port_number are the host name and port number of the Dynamic Workload Console you are connecting to.
Self-service Catalog is a solution to automate routine business tasks and run them from mobile devices without having to install and learn about the whole Tivoli Workload Scheduler product. By using the Self-service Catalog you can use your mobile device to submit service requests to Tivoli Workload Scheduler without knowing anything about engines,jobs, or job streams.
By launching Self-service Catalog application from your device, for example, you can see the available services, which basically are Tivoli Workload Scheduler job streams. You can open a catalog, view the services that it contains, and submit a service request very simply and easily from your mobile device.
Even though the Self-service Catalog has been primarily envisioned to be used from mobile device, you can efficiently use it also from your computer connected to a web browser. To submit a job stream from your mobile, an administrator must have previously created a service by associating it to a Tivoli Workload Scheduler job stream and engine. The service is linked to a job stream that runs on a Tivoli Workload Scheduler engine. By simply launching the service, you can submit the job stream. You define jobs and job streams using the Dynamic Workload Console to automate tasks that users perform routinely. You use the Self-service Catalog interface from your mobile device to start the job streams when needed.
Optionally, you can also use Self-service Catalog taking advantage of High Availability configuration so as to have multiple console instances working at the same time without reducing performance. If the Self-service Catalog you are using is connected to a Dynamic Workload Console in High Availability configuration, all the user settings, including the Self-service Catalog data, are stored in a DB2 repository. If you are connected to a Dynamic Workload Console in High Availability configuration using a load balancer, when you launch the Self-service Catalog, you are not connecting to a specific Dynamic Workload Console, but to a node in the High Availability configuration. Therefore, for example, if a node fails, new user sessions are directed to other active nodes in the configuration and this change is completely transparent to users.
Use your mobile device to monitor your jobs by accessing the dashboard and navigating to job details and log.
Connect to this URL using your mobile device: https://host_name:port_number/ibm/TWSWebUI/dash.jsp, log in using your Tivoli Integrated Portal credentials.
Select the engine that you want to see in the Dashboard.
The initial view is a pie chart, but optionally you can switch to the bar chart by clicking the icon in the toolbar below it. The pie is divided into slices of different
colors that indicate, in the same way as the bars of the bar chart, the current status of jobs in the plan. Below the chart, a legend identifies the status that is mapped to
each color and indicates the number of jobs in the plan that currently have that status.
In addition is possible to see also information about Critical jobs.
Critical jobs can be displayed only on engines on which the critical path can be displayed only on engines on which the critical path
feature is available and enabled. Touch the critical job icon to view the section that displays the risk level of critical jobs on each engine.
Scroll down to view the job statuses
Touch the status of a job and scroll down to view more details about that job, such as the name of its job stream, workstation, and scheduled time. Optionally, use the search box to search for a specific job.
Starting from the dashboard, you can access the status, properties and logs of any job in the TWS plan, either on distributed or zOS platforms. Nothing has been installed on your mobile device. Using the Dashboard, from your mobile device, you can see a graphical view that shows the progress of the current plan on the engines for which you have configured a connection and specified the option to show the engine in the dashboard. Optionally, you can scroll down the job details to view the job log, when available, and send the job log using email to someone. In the job log, you can also filter for specific strings to display.
The IT market is moving towards mobile devices, which help you perform a large number of tasks, such as manage your sales workforce, read your e-mail, check your accounting system, or attend a web conference.
Applications designed for mobile devices must be intuitive and user-friendly while remaining robust and reliable, and providing instant access to business and client data wherever they are.
Tivoli Workload Scheduler Mobile Applications are web applications designed to be used on mobile devices.
Mobile web applications are easier to maintain, can be accessed by any mobile device and doesn’t cost you a thing to distribute.
In addiction, you have also the following benefits:
- deploy once and view it anywhere
- applications are always updated, no installation or updates on the device, just a bookmark-able web link
- security is managed into the server side, the user need to know only credential
- many different kind of devices are supported at the same time: Android, iOS (iPhone, iPad) and also BlackBerry
- applications can be accessed using also the modern browsers like Firefox, Internet Explorer and so on
Tivoli Workload Scheduler propose two different mobile applications:
To monitor your workload in plan, see the job details, and send this information via e-mail.
- Self-Service Catalog
To submit job streams from your mobile, even if you do not have any experience with Tivoli Workload Scheduler.
These applications are automatically installed with the Dynamic Workload Console.
If you install the Dynamic Workload Console you are able to use our mobile applications.
So, you can use your mobile device to easily and quickly interact with the Tivoli Workload Scheduler.
Using our application you can monitor and run your workload from your mobile device by simply logging in to a URL.
Job interception is used in SAP systems to reduce or block uncontrolled background job workload submitted ad-hoc by users.
With Tivoli Workload Scheduler 8.6 FP1, Tivoli Dynamic Workload Console 8.6 FP1 and Tivoli Workload Scheduler for Applications 8.6 you can model XBP 3.0 job interception profiles, define job interception relaunch criteria and schedule a TWS job interception collector within the Dynamic Workload Console.
Watch the Demo Video
to understand the entire workflow cycle.
The Tivoli Dynamic Workload Console
8.6.0 fixpack 1 releases many improvements to work in conjunction
with SAP environment; one of these is the possibility to
model SAP R/3 jobs inside the workload editor.
The developer will be more comfortable
having a single point to complete design tasks.
Creation, search, edit and delete
actions of SAP R/3 jobs can be performed like any other TWS object
avoiding to jump to the “List jobs on SAP” dedicated portlet.+
Connect workload editor to a SAP environment
To accomplish this goal the workload editor needs some parameters to pass to TWS for Application in order to realize the connection to the SAP environment.
A new button “SAP Connection Data” has been added to the toolbar
opening a pop-up
The required parameter to insert is just the name of the XA workstation with r3batch method installed or the name of a dynamic workstation, like an agent, a pool or a dynamic pool since these workstations are now enabled to work with TWS for Application 8.6.
In this second case an option file to use for the connection can be also provided.
Users need to inserted the SAP connection data once since the workload editor will store and use them until the user will not change or remove them
If the test connection end successfully the workload editor is enabled to work with SAP R/3 jobs!
Create a SAP R/3 job inside the
You can now create a SAP R/3 job like
any other TWS object either on distributed and z/OS environment, but
it will be saved on the SAP system instead of the TWS database.
Both in the distributed and z/OS
environment it is identified by “Remote SAP R/3 Job”
This is the General properties panel of
the R/3 job:
From the details view the steps can be
added to the R/3 job:
After saving here it is the R/3 job as
displayed in the SAP GUI!
IBM has just announced a new evolution of Tivoli Workload Automation .
The new offering includes: Tivoli Workload Scheduler for Applications 8.6, Tivoli Workload Scheduler 8.6 Fix Pack1 and Tivoli Workload Scheduler for z/OS 8.6 SPE.
Here the link to the complete Announcement letter
that can provides you details with the specific enhancements and product improvements.
May 17: System
z Webcast "What's New with IBM Workload Automation" using
Workload Scheduler family
- Sharing infrastructure
among applications to reduce resources
- Reducing labor costs by
automating new workloads with the same staff resources
- Improving productivity by
reusing existing workload automation processes and procedures
Speakers: Flora Tramantano, Tivoli Workload Automation
Product Manager, IBM Software Group
Broadcast Date:May 17, 2012, 11 a.m., Eastern Daylight Time,
4:00 p.m. BST / 3:00 p.m. UTC
Developed for: IT and enterprise architects; IT managers; systems
analysts; systems programmers; and operations managers
Learn. Explore. Achieve. Results.
New in 2012 – ASAP expanded to FOUR
full business days!
Don’t miss the unique educational opportunities
available only at ASAP 2012 – premier TWS Education + Training!
April 29, 2012 - May 4, 2012 Austin, Texas
Have you ever
wanted access to what the development team is planning for the future,
along with the ability to provide direct feedback on each item within a
planned release? With Tivoli's shift towards transparent development,
now you can. Transparent
Development is the ongoing, open engagement between IBM development and
our users on the development of our products. The emphasis is on being
open and transparent about our direction and providing you with open
access to key release content, including:
- Release plans and details about the progress of the release
- Beta code downloads
- Product roadmaps
- Early designs
- Sprint demos
- Best practices and discussion around already generally available releases
Tivoli Workload Automation is one of the first products to adopt
transparent development within Tivoli. Through the new project dashboard
on Service Management Connect, you can view the current release plan
and provide direct feedback on what the team is developing. All you need
is a developerWorks ID and password to access the release plan, and to
provide your feedback. To access the Tivoli Workload Automation project dashboard and see
what's ahead, click here. To post comments and other feedback on the forum, click here.
What is Big Data?
Everyday, we create 2.5 quintillion bytes of data–so much that 90% of the data in the world today has been created in the last two years alone. This data comes from everywhere: from sensors used to gather climate information, posts to social media sites, digital pictures and videos posted online, transaction records of online purchases, and from cell phone GPS signals to name a few. This data is big data.
The Big Data platform
IBM InfoSphere BigInsights builds on open source Apache Hadoop with IBM unique innovations including a sophisticated text analytics module. BigInsights is able to ingest and analyze data in its native format, without imposing a schema/structure, enabling fast ad-hoc analysis.
Tivoli Workload Scheduler and Big Data
Use the IBM Tivoli Workload Scheduler Integrator for InfoSphere BigInsights to run IBM InfoSphere BigInsights jobs, using Tivoli Workload Scheduler. In this way, you take advantage of all the Tivoli Workload Scheduler scheduling functions to manage these jobs. Installing the integrator on your Tivoli Workload Scheduler environment, you can define, schedule, and monitor InfoSphere BigInsights jobs through Tivoli Workload Scheduler.
A business scenario
A large wind energy company performs business in wind power generation. To succeed, the company uses one of the largest supercomputer worldwide networks together along with a new big data modeling solution, based on InfoSphere BigInsights. To reduce data processing times in establishing the optimal turbine placement, the company runs InfoSphere BigInsights jobs every day to collect and analyze data. The process of establishing a location starts with its wind library, which incorporates data from global weather systems with data collected from existing turbines. Combined, this information helps the company not only to select the best site for turbine placement, but also to forecast wind and power production for its customers. The process that runs the InfoSphere BigInsights jobs overnight is performed manually by an operator. To reduce costs and to ensure that the SLA requirement of having analyzed data available every morning is satisfied, the company wants to automate this process.
Using IBM Tivoli Workload Scheduler Integrator for InfoSphere BigInsights, the company can satisfy this objective because the product helps it to automate and control the entire process.
TWA Rome Development team is pleased to announce the availability of the beta code driver 2 for the next release of Tivoli workload Scheduler for Application, TWA 8.6 FP1 and SPE 8.6 Features.
The Beta program provides participants with the opportunity to get an early look at the next release and provide feedback directly to the Development team to influence the future direction of the product.
Visit this page to read the key features which are included in the next TWA Release
Beta program participants can: receive education on the new features by webcast, beta exchange session or recorded talk, download Beta code from a web site, install it in their own test environment. However, to remove possible time and resource inhibitors, we have launched the Beta as a Service initiative that needs only 1 hour of your time.
Please contact firstname.lastname@example.org and me (email@example.com) if you are interested in this Beta or if you have any questions.