Fast paths for WebSphere Application Server
This topic describes the most quick and simple paths to deploying an application, with links that pinpoint the relevant information for reaching your goals quickly. It also describes the audience roles and tasks assumed by this documentation. The fast path described in this topic is intended to help you gain a little experience. It does not showcase the advanced product features that some users need or want to use in their production environments.
Overview. Deploying any type of application involves the following tasks.
- Step 1: Install the product.
- The simplest scenario is to perform a typical installation of a single application server onto a Windows machine, perhaps with theTrial program code that is available.
If you have purchased the product already, see Operating system central for direct links to installation steps for Windows (or another operating system of your choice). Planning information is also available.
- Step 2: Obtain or develop your application.
- In the simplest scenario, you already have a packaged, J2EE 1.4 compliant Web application, perhaps from a vendor with whom you work. Other than that, a Web application is the most simple type of application to develop (see Task overview: Developing and deploying Web applications), or refer to the many Samples in the Samples Gallery.
- Step 3: Deploy and test your application.
- In the simplest scenario, you will use the application installation wizard available in the administrative console. See Installing application files with the console for a detailed walkthrough of this task. The task describes many contingencies, but many of these steps can be disregarded if:
- you are deploying a Web application
- you accept the default settings whenever possible
- your application does not require data access
- your application does not require security
Also, in many situations, one can get by without modifying the default application server configuration.
- Step 4: Administer your deployed application.
- In the simplest scenario, you will monitor your application with the Tivoli Performance Viewer functionality built into the administrative console. See Monitoring performance with Tivoli Performance Viewer (TPV) for an overview of this task.
ResultNow you should have some insight into the task flow for successfully deploying your applications.
To solidify and expand your understanding, view the following table. It shows the user role and task assumptions by which this documentation is organized, for predictability. If you know what role or task you are performing, one can disregard (at least temporarily) documentation that is labeled for other roles or tasks. By their nature, role and task models are simplified compared to reality. Also, one person might perform many roles and tasks in the course of a day.
User role User tasks
Install application serving environment
Migrate deployed applications and their environment
Administer applications and environment
Monitor and tune applications and their environment
Deploy applications into production
Develop or migrate application code
Assemble applications for deployment
Deploy applications for testing
Secure applications and their environment
Use tools to troubleshoot problems
Overview and new features for migrating, coexisting, and interoperating
Overview and new features for installing an application serving environment
Overview and new features for administering applications and their environments
Overview and new features for monitoring
Overview and new features for tuning performance
Overview and new features for developing and deploying applications
Overview and new features for securing applications and their environment
Overview and new features for troubleshooting
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
Tivoli is a trademark of the IBM Corporation in the United States, other countries, or both.