This section focuses on development environments, including:
- Developing application components
- Assembling components into modules
- Configuring deployment descriptors
- Deploying modules onto servers
- Administering applications - basic tasks
- Designing applications (finding best practices)
- This topic highlights Web sites and other ideas for finding best practices for designing
WebSphere applications, particularly in the realm of WebSphere extensions to the Java 2 Platform,
Enterprise Edition (J2EE) specification.
- Obtaining an integrated development environment (IDE)
- This topic describes obtaining an integrated development environment (IDE). Use Rational
products from IBM to design, construct, and manage changes to applications for deployment on
your WebSphere Application Server products.
- Developing WebSphere applications
- This topic provides development, assembly, and deployment instructions
that are specific to various types of applications. For example, you can focus
on developing Web applications or Web services; or extending your applications
with the application programming interfaces of the messaging or security subsystems.
- Rapid deployment of J2EE applications
-
The rapid deployment tools extends the mechanism for generating deployment artifacts,
packaging the application and preparing the application to run only on WebSphere
Application Server v6.0.
- Debugging applications
- To debug your application, you must use your application development tool
(such as Rational Application Developer) to create a Java project or a project with
a Java nature. You must then import the program that you want to debug into the project.
By following these steps, you can import the WebSphere Application Server examples
into a Java project.
- Assembling applications
- Application assembly consists of creating Java 2 Platform, Enterprise Edition
(J2EE) modules that can be deployed onto application servers. The modules are created
from code artifacts such as Web application archives (WAR files), resource adapter
archives (RAR files), enterprise bean (EJB) JAR files, and application client archives
(JAR files). This packaging and configuring of code artifacts into enterprise application
modules (EAR files) or standalone Web modules is necessary for deploying the modules onto
an application server.
- Class loading
- Class loaders are part of the Java virtual machine (JVM) code and are responsible
for finding and loading class files. Class loaders enable applications that are deployed
on servers to access repositories of available classes and resources. Application developers
and deployers must consider the location of class and resource files, and the class loaders
used to access those files, to make the files available to deployed applications. Class
loaders affect the packaging of applications and the run-time behavior of packaged
applications of deployed applications.
- Deploying and administering applications
- Deploying an application file consists of installing the application file on a
server configured to hold installable modules.
- Troubleshooting deployment
- This topic describes how to identify and handle a variety of problems
encountered during development, assembly, and deployment activities.
- Adding tracing and logging to your application
- Designers and developers of applications that run with or under WebSphere Application Server,
such as servlets, JavaServer Pages (JSP) files , enterprise beans, client applications, and
their supporting classes, might find it useful to use Java logging for generating their
application logging.