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 environment descriptors. Generate code for deployment either before or during application assembly.
Some details: The enterprise bean developer writes and compiles the enterprise bean components.
The developer packages the components and a deployment descriptor into an EJB JAR
file containing a manifest.
For entity beans (BMP or CMP), the developer 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.
The developer tells the administrator whether the JAR file has been
deployed.
A developer using VisualAge for Java can deploy the JAR file before
giving the file to the administrator. A deployed JAR file
consists of the EJBHome and EJBObject classes, persistor and finder
classes, and stub and skeleton files.
Otherwise, the administrator makes a note to deploy the JAR file while
installing it in the WebSphere administrative domain.
There are special considerations for deploying
entity beans with container-managed persistence (CMP) and any enterprise
beans with EJB inheritance.
- If migrating from Version 3.5, prepare the application for workload management.
- Install the application files. Install the application into the test environment.
Some details: If the beans in a JAR file reference classes outside of the JAR file, the
administrator adds the referenced classes to the CLASSPATH environment variable
of the machine on which the beans are installed.
The bean JAR file itself is automatically added to the CLASSPATH when the
administrator installs the bean JAR file in the WebSphere domain. If the
referenced classes are contained in the JAR file, no action is required.
- Configure the runtime, supporting resources, and the application itself. Create application
servers and other resources that will support applications.
- 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 -- see the tutorial for examples
- 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.
Some details: After changing an enterprise bean, the developer provides a replacement
JAR file to the administrator. The administrator adds the file to the WebSphere
administrative domain.
More information
To obtain more information
about a step in the above procedure, see the links to sub-topics.
|
|