Tasks
Automation planning
To emphasize the need for automated administration, consider the fact that companies typically have multiple WAS environments to support activities in the different phases of the software development life cycle. Each of these environments is susceptible to being the target of the same type of admin tasks. What if there was a way to do a task manually once only, and have subsequent requests be done automatically or with a lot less effort? That is the main goal of automation.
Automating common procedures and actions is one of the keys to maintaining a stable and efficient WebSphere environment. We can reduce the possibility of human error by eliminating human intervention in complicated tasks or mundane procedures that are prone to mistakes. Automating WAS installation and configuration also provides an administrator the opportunity to schedule recurring maintenance and backup procedures, and any other types of admin tasks.
Every action that we can perform manually using the Integrated Solutions Console can be automated using WAS's wsadmin tool and command line utilities.
Installation response files Allow we to specify installation options once and use them for multiple installations of WAS.
Enable silent execution mode.Command line utilities Shell scripts on UNIX or batch files on Windows
Run from standard shell or command prompt
Allow we to control different aspects of the WAS environmentsWebSphere Ant tasks Facilitate build and deploy processes to WAS. JMX framework Provides standards-based capabilities to control and manage a WAS.
Allows we to create custom Java clients to access managed resources.wsadmin scripting tool Scripting interface that allows we to execute admin commands interactively or by running a script of commands. Installation factory Complementary tool to combine the installation of WAS with maintenance packages and fix packs in a single step. Although scripting requires up front development costs, in the long term it provides savings through automation and increases reliability. In addition, in many organizations, the Integrated Solutions Console is prohibited by security policy and infrastructural constraints. Scripted administration provides an alternative way to manage the WAS environment.
Automation is not necessary if the task is only a one off.