{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

a WebSphere Application Server

a WebSphere Application Server - involved before an...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
As a  WebSphere Application Server  ( WAS ) administrator, you will soon find that doing administration  manually becomes laborious when you have a large number of administration tasks to perform. Whether you  work for a large organization or not, you will need to deploy many applications into your WAS environments.  Sometimes the same deployment will be repeated time and time again. In  Chapter 3 Deploying your  Applications , we learned how to manually deploy an EAR file using the Administration console. We found  that, depending on the type of application being deployed, there could be many configuration elements 
Background image of page 1
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: involved before an application is considered ready for runtime use. To speed up deployments and make them more consistent and controllable, we need to look at how we can automate our deployments. It is also important that we are able to automate the configuration of WAS, which can save many hours of manual administrative efforts. In this chapter, we will cover the following topics: Automation ws_ant (Ant) wsadmin tool Jython scripting • Configuring applications using...
View Full Document

  • Spring '12
  • abcd
  • large number, WebSphere Application Server, large organization, Jython scripting, administration tasks, EAR file

{[ snackBarMessage ]}

Ask a homework question - tutors are online