An Architectural Approach to IT Automation
Summary
The result is a “point” solution is implemented, e.g. writing a script, Windows Task Scheduler, Cron, SQL Server Agent, a tool for automating FTPs, etc. IT environments are growing in complexity while businesses are becoming increasingly dependent on IT-based services for commercial success in today’s 24/7, Internet-driven world. Nor does taking an “architectural” approach require an “all-in” strategy whereby the IT organization is consolidating multiple scheduling and automation solutions in one fell swoop. As the example highlights, taking an “architectural” approach lays the foundation for a policy-driven automation strategy that drives governance, visibility and control, allowing IT to more quickly respond to the demands of the business when something does break rather than looking for a script running on some disparate server. IT organizations need to take an “architectural” approach to IT automation in order to achieve IT service level assurance with true integration and orchestration across business processes, applications and the underlying infrastructure.
Classifications
AskAI Classifications
LabelsLinked Companies
