InfoCenter Home >
6: Administer applications
6: Administer applications
Typically, one or more application developers with different areas of
expertise (such as architects, Java programmers, legacy programmers, and
Web programmers) design and create a new application or
migrate an existing application to support new Java
specifications based on input from business users.
After the files comprising an application have been developed, then
the application can be added to the application server for access by users.
This section of documentation helps you learn the flow of administrative
activities, whether you are a code developer introducing an application
into a test environment, or an administrator responsible for the
production environment.
A feasible end-to-end administrative procedure
The following procedure provides links to more information about
each step. To practice the procedure using an application provided
with WebSphere Application Server, perform the application
configuration and deployment tutorials.
- Install the product. Plan and install a topology comprised of one or more
product installations and the necessary prerequisites.
- Assemble the application. Assemble the application modules from the application files.
Set values for the deployment descriptor. For applications containing EJB modules,
generate code for deployment.
For example, for an EJB module, the enterprise bean developer writes and compiles the enterprise bean components.
The developer assembles the components and a deployment descriptor into an EJB JAR
file and then generates code for deployment.
For entity beans (BMP or CMP), the developer also generates the database
tables the beans will use to store their data.
The developer transfers the JAR file to the WebSphere administrator, or
informs the administrator of its location on a machine in the WebSphere
administrative domain.
- If migrating from Version 3.5, prepare the application for workload management.
- Secure the application. Configure security in the application.
- Configure the runtime and resources. Create application servers and other resources
that will support applications.
- Install the application. Install the application into the test environment.
Installing an application refers to the process of
placing the Enterprise Archive (EAR) file in a runtime environment comprised of an application server.
During this step, the administrator can optionally edit the application's
deployment descriptor.
- Configure resources for application clients (if applicable). Create
resources for the Java clients that will access your application.
- Test the application. Test the application prior to enabling runtime security
so that you can tell the difference between security-related problems and other problems.
- Who: Systems administrator
- How: Using a Web browser or other application client
- Configure runtime security. Configure and enable security in the application server runtime.
- Test application security. Test the application again, this time with security
enabled.
- Perfect the test environment. Debug and verify the application in the test environment.
Perform preliminary tuning.
- Who: Tester, systems administrator
- How: Using the administrative console
- Port the application to production environment. Configure the production environment and
move the application there.
- Who: Network administrator, systems administrator
- How: Using the administrative console
- Manage the production environment. Manage the production application, tuning the application files and configuration as needed.
Update the production application as needed.
- Uninstall applications as needed.
- Remove security, as needed.
More information
To obtain more information
about a step in the above procedure, see the links to sub-topics.
|
|