BMC Software is pushing forward with products to alleviate a problem that tech workers in the trenches have grappled with for years: system downtime.<\/p>\n","protected":false},"excerpt":{"rendered":"
“What BMC is proposing is a better way to manage applications, by creating models of how the application depends on the infrastructure,” said Jean-Pierre Garbani, an analyst at Forrester Research. “With a model, IT people can see that one component is not behaving normally…It’s a way to speed up and make problem management more intelligent,” Garbani said.<\/p>\n
On Tuesday, the software maker plans to introduce an update to its Control-M program for organizing computing jobs. The revamp, Batch Impact Manager, helps businesses head off glitches and prioritize problem reports, BMC said.<\/p>\n
Application failures are very costly to corporations, as they can prevent employees from doing their jobs or take revenue-generating applications, such as e-commerce Web sites, offline.<\/p>\n
Business service management products help operators spot more quickly the source of problems that affect application performance, such as problems with servers, networking hardware and other underlying components.<\/p>\n
The addition next week of the Batch Impact Manager to the Control-M software will enable system operators to get a consolidated view of scheduled batches of jobs, BMC said. If there is a failure in one of them, the software can send an alert and highlight possible problems with other applications. For example, the failure of a mainframe job to update customer transactions scheduled for the middle of the night could prevent a financial trading application from being available the following morning.<\/p>\n
http:\/\/zdnet.com.com\/2100-1104_2-5342278.html<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1323","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1323","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1323"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1323\/revisions"}],"predecessor-version":[{"id":3810,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1323\/revisions\/3810"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1323"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1323"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}