Data Center Automation
Isabell Sippli(IBM) 060000X124 Tags:  saam hadr system-automation tsa automation 1 Comment 5,570 Views
We're very close to our first Open Program Call on Tivoli System Automation Application Manager(https://ibm.biz/BdxKhQ)
Main focus of this call is the new User Interface we intend to ship based on that new platform in a v3.next release.
We'll post a recording on our Open Program developerWorks community (https://ibm.biz/BdxSCL)- stay tuned!
Gareth Holl 100000C8M7 5,567 Views
I wrote a new tool I call "db2tsacheck" to help avoid unwanted surprises due to configuration problems. Its sole purpose is to look for as many configuration problems as possible for TSAMP managed DB2 HADR or DB2 HA Shared Disk environments. Its a tool you can run on a periodic basis to validate all is well with your configuration.
To download the new version, please visit the following URL:
Here's what it looks like after hitting <enter> to have db2tsacheck attempt to fix all the problems found :
The output is much more compact and makes it more immediately obvious what is and is not a problem.
Problems found can be selectively fixed by entering the individual numbers associated with each problem listed, or all problems can be fixed by simply hitting <enter> after all the problems are listed.
Here's what the output of db2tsacheck looks like when its shows a clean bill of health (no problems) :
"Consolidation drives value." "Manage less and do more."
These initiatives, and many others like them, make sense from a financial standpoint, but can often lead to sleepless nights for operations managers once they realize the majority of their business, sometimes as much as 85%, is now run out of a single datacenter or a single platform. What happens when the system goes down? What happens when my datacenter loses connectivity? How quickly can I recover from an outage? Do I even need to recover, can I just roll-over to an active or passive backup?
Many mission critical core business applications, from larger vendors such as SAP and their ERP solutions, are run in datacenters much like this. However through high-availability and disaster recovery (HADR) capabilities provided by IBM, these datacenters can establish a failover policy to prevent even the slightest interruption to your company’s centralized business processes and financial systems.
IBM’s core HADR capabilities are provided by the Tivoli System Automation family of products, which we’ll specifically touch on System Automation for Multiplatforms here. Tivoli System Automation for Multiplatforms (SA MP) is a high availability clustering solution with advanced automation capabilities. It includes out-of-the-box resiliency policies for many IBM products delivering mission-critical capabilities to our customers. SA MP is the default, built-in HADR solution for IBM DB2 for Linux, Unix, and Windows available at no extra charge to DB2 LUW customers. The expansive capability of System Automation to provide a single point-of-view into your HADR capabilities and manage them, whether your fail-over datacenters are across the street or across the continent, provides immense value to our customers in managing their heterogeneous environments.
One such customer leveraging these out-of-the-box policies from SA MP for DB2, and by extension SAP, is China Ocean Shipping (Group) Company. For a detailed overview of the entire solution implemented by COSCO, including IBM POWER hardware capabilties, please follow the link below. In this post, I’ll briefly touch on how COSCO was able to leverage HADR capabilities to prevent major damage to the business during multiple datacenter outages. COSCO consolidated much of their business operations onto a single SAP ERP solution, but required the highest levels of service availability from this single system. By putting their SAP solution on top of DB2 and leveraging the HADR capabilities provided by SA MP, this customer was able to deploy a single SAP ERP solution across multiple datacenters worldwide, offering near real-time replication. These HADR capabilities and benefits were fully realized multiple times when the customer’s main datacenters experience prolonged outages, including the historic 2011 Tōhoku earthquake. They were able to seamlessly switch over from their datacenter in Tokyo to the off-site datacenter in Beijing, with virtually no service interruption.
Now the actual definition of “disaster recovery” may not always come to mind when you are planning your HADR strategies, but Tivoli System Automation, along with the many other IBM products it is embedded in are available to minimize your key HADR metrics, both recovery point objective (RPO) and recovery time objective (RTO). Many additional policies are available for other IBM and third-party products to monitor and ensure the availability for your business services. For more information on how you can be completely confident in your business’s HADR solution, check out the links below for a deeper dive into Tivoli System Automation for Multiplatforms.
For more information:
berenss 1200009PF3 Tags:  dca tpm provisioning performance #smc servicemanagementconnect 5,256 Views
I just wanted to take a moment to spread the word about a new performance cookbook resource available from the IBM Service Management (ISM) Library. You can find it here:
This cookbook is based on the latest available version of TPM 7210 and combines all the most recent performance improvements available. Performance areas discussed in the cookbook include:
Grab your copy today!
Isabell Sippli(IBM) 060000X124 5,218 Views
The Tivoli System Automation development team just released a whitepaper on SAP High Availability with Tivoli System Automation for Multiplatforms on AIX and Linux.
Tivoli System Automation for Multiplatforms is a high availability cluster solution and automation product that provides several monitoring mechanisms to detect system failures and a set of rules to initiate the correct action without any user intervention. The set of rules is called a policy, this policy describes the relationships between applications or resources. This policy and the monitoring mechanisms provide System Automation for Multiplatforms with extensive up-to-date information about the system landscape so that it can restart the resource on the current node or move the whole application to another cluster node.
To protect the SAP Central Services, System Automation for Multiplatforms will be deployed on the cluster nodes and will be configured to monitor the SAP Central Services.
The paper will detail why companies need HA solutions for SAP, and introduce degrees of availability. Furthermore, it describes which components of an SAP system should be
Download the paper here.
If you're planning on asking IBM Support for help, more than likely there will be a minimum amount of detail they will need up front. The most obvious being details about your environment, such as platform/OS and product versions.
Should we or shouldn't we?
The typical question of the IT Manager when her/his datacenter automation software releases a new fixpack. This question stems from prior nightmares attempting to deploy fixes that were half-baked, poorly documented and delivered in haste.
I'm not an 'alpha' adopter but I certainly am an early adopter. The reasoning I take into deploying a new fix or new release fixpack is that I want the newest features, I want the bugs corrected - especially if there is a specific one that I'm subscribed to, and I want the latest enhancements in stability and serviceability. This will invariably cause some churn in my current calendar which may in turn force other projects to take a break, downtime will have to be scheduled, and service request tickets opened to alert dependent teams, but that short team pain will always bring a longer term gain.
Further reasons to keep up to date include the following:
To emphasize this point we'll look at the upcoming TPM 7210-IFIX03 release due at the end of October 2012. In it we include a host of fixes and enhancements which improve the overall function and quality of the product. In particular a migration function to upgrade your WebSphere version 6.1 to version 7.0. This is really key for shops that need to keep their web-hosting environments running at the latest technology and security levels. The IFIX03 installation is redesigned as well, moving many of the prior manual steps into scripted pre- and post- installation sections. This is really great and should be a major step forward at alleviating many common maintenance headaches. While you're at it you should also take a moment to register for the upcoming training on this TPM721 IFIX03 release,
In How Tivoli Provisioning Manager integrated usability testing in Agile - Part 1 we talked about 3 points on how usability testing fits into the development cycle. In part 2, I will be sharing some other points to make this activity successful.
4. We tested “anything”
For example, we tested various designs to validate the general flow of a task from the business perspective. The feedback received from a design validation session helped us determine the right choices to provide. We also tested draft documentation to identify gaps and to validate the effectiveness of search results.
In addition to testing working code and documentation during usability sessions, our team conducts validation sessions for features that are in the design phase. In these sessions, we are gathering feedback from customers from the start. This way, they are helping to shape the product functions.
5. We involved everybody
For all usability sessions, in-person and remote, our team encourages stakeholders to participate in listen-only mode. This process helps the team understand the customer’s perspective because everybody can see where the users are confused and if they are struggling to complete their tasks.
6. We recorded feedback
Our team uses a wiki to store the information that we collect for each sprint, session, and feature tested. We are using IBM Rational Team Concert (RTC) to open defects, to track how many defects have been fixed at any point in time (and for which feature), and to remind us what issues still need to be addressed.
7. We presented results
In the report, we summarize the ratings and overall task success, the positive feedback, and the number of defects opened. We also store this report in the wiki along with the notes from the sessions.
Conclusion: We improved usability
We took the following actions based on usability issues identified in our testing:
The IBM Tivoli Provisioning Manager development team continues to enhance the next release (TPM v8.1) with new features and usability improvements which are targeted for future delivery. We have just announced the availability of our first BETA.
If you are an existing TPM customer or stakeholder and would like to participate in the BETA and provide feedback, please contact Kimberly Mungal (email@example.com) to join the TPM 8.1 Early Access Program.
The tool appcmd can be used for testing policies of IBM Tivoli System Automation for Multiplatforms and policies of IBM Tivoli System Automation Application Manager Agentless Adapter. You can use it to instrument IBM.Application or IBM.RemoteApplication resources. appcmd simulates resources, allows to mimic failures and tracks the execution of commands which makes it a useful tool to develop and test policies.
We publish appcmd in version 4 for free in our IBM System Automation for Multiplatforms Wiki page here
New in version 4:
* appcmd is configured using the properties file /etc/opt/IBM/tsamp/sam/cfg/appcmd.properties
* The location where appcmd stores the state of the simultated resources can be configured
* The tool appcmd_policy_converter.pl which converts XML policies with real applications to appcmd
Automation with Tivoli System Automation products family in virtual environments has been presented on the GSE Power-Systems conference in Munich on 21.11.2011.
Virtualization technologies play an important role in datacenters – they also provide the base for currently hot discussed “cloud” infrastructures.
There is a lot of focus on virtualization technologies for distributed server platforms like zVM, VMware, System p’s Hypervisor, SUN Solaris Zones, and others.
Of course, virtualization provides several benefits this presentation concentrated on the aspects of availability, high availability and disaster recover.
More than 80% of enterprises have adopted server virtualization, but only 20% of all server workload is on virtual machines
Key points which have been addressed in the presentation:
These topics are addressed in the given presentation - if you are interested to learn more pls. contact us.
dplantz 1000003W46 4,866 Views
Caveat: You have TWS 9.x installed....What are the commands to stop and start TWS 9.x and WAS processes?
To stop/startTWS scheduler on master and ftas from command line (this stops batchman and mailman only, leaving the TWS WAS and TDWC JazzSM piecies up)
To shut down the TWS application all the way down on master and ftas from command line (this stops netman, mailman, writer and batchman processes but leaves the TWS WAS and TDWC JazzSM pieces up)
conman stop|conman start
conman shut | Startup
To stop TWS on master/bkm (this stops the TWS WAS piecie, and leaves batchman, mailman, writer, netman and TDWC JazzSM piece up)
Note: The stopWas.sh and startWas.sh kick off the conman "stopappserver;wait" and conman "startappserver;wait" commands respectively.
To stop/start TDWC on master/bkm (this stops the TWS JazzSM piecie, and leaves batchman, mailman, writer, netman and TWS WAS piece up)
...IBM/TWAUI/wastools/stopWAS.sh -direct -user -password
...IBM/TWAUI/wastools/startWAS.sh -direct -user -password
You also have stopmon for monitoring/event rules.
For this and other good tips and troubleshooting please visit the dWAnswers user forums at:
type in the core keywords TWS and now IWS ( IBM Workload Scheduler) to see other questions and answers
JoergErdmenger 100000AHDG Tags:  tsa-am agile open-program tsamp tsa system-automation appman 4,815 Views
The Open Program for IBM Tivoli System Automation started.
We are developing the next version of our products:
In the Open Program, we are going to show you selected features and improvements that we intend to include in future releases of SA AppMan and SA MP. We are looking forward to discuss these features and improvements with you and receive your feedback.
You have the chance to participate in this new development and
influence during the Open Program for IBM Tivoli System Automation
I'm also including the URL to the official guide
that shows how to set up and operate an SA MP cluster to keep TSM highly available.
A new paper has been released on the System Automation Application Manager WIKI:
It contains information and examples (in Java® and PERL) on how to control End-To-End resources via REST calls. For scripting this eliminates the necessity to log on to the node hosting the SA Application Manager and does not need to start a JVM (like eezcs does).
As always we are very interested in your feedback and any nice solutions (like handy scripts) you are developing.
- Sebastian Wegmann