Informacion sobre Websphere 5

[abuenog]

Web projects, which may contain JSP files, HTML files, servlets, and beans
EJB projects, which contain enterprise beans
Enterprise Application projects, which may contain java archive (JAR) files or web archive (WAR) files or both, and pointers to other Web or EJB projects.

Supported run-time environments
Server Tools uses servers and server configurations to test your projects. Servers identify where you can test your projects. Server configurations contain setup information. Server Tools allows you to test your applications in different run-time environments that can be installed locally or remotely:

The Server Tools feature includes a local copy of the full WebSphere Application Server run-time environment, where you can test Web projects, EJB projects, and Enterprise Application projects.
You can also test on a remote copy of the WebSphere Application Server. To do this, you must install on your remote machine:
WebSphere Application Server
IBM Agent Controller (included with WebSphere Studio as a separate install)
Server Tools also supports the Apache Tomcat run-time environment, running locally. With Tomcat, you can only test Web projects that contain servlets and JSPs.
A test environment called the TCP/IP Monitoring Server is also packaged with Server Tools. This is a simple server that forwards requests and responses, and monitors test activity. This run-time environment can only be run locally, and it only supports Web projects. You cannot deploy projects to the TCP/IP Monitoring Server.
For more information about testing and publishing to a server, refer to the online help.

Profiling and logging tools

Performance profiling
WebSphere Studio provides tools that enable you to test your application's performance early in the development cycle. This allows enough time to make architectural changes and resulting implementation changes. This reduces risk early in the cycle, and avoids problems in the final performance tests. The Profiling tools bring together a range of techniques that let you explore many aspects of your program.


Visualization

Graphical and Statistical profiling views
The Profiling tools collect data related to a Java program's run-time behavior, and present this data in graphical and statistical views. In addition to being memory leak diagnostic aids, which the statistical views also are, the graphical views afford pattern extraction and information exploration capabilities.


Sequence diagram views
Sequence Diagram views are specialized views that provide a means to visualize the execution of Java applications in the form of sequence diagrams that are defined by the Unified Modeling Language (UML) notation. These views are best put to the following uses:

Software development management personnel can verify a software implementation with the design documentation for the purpose of accuracy.
Software developers can use the views to understand the execution flow of an application and to analyze its performance.
Business application administrators can monitor the state and performance of such applications, where the monitoring may be performed at any level: that of the agent, the process, the host, or the monitor (cluster of hosts).
Computer network administrators can monitor interactions among hosts on the network.

Distributed process monitoring
The Profiling tools also give you the ability to launch remote applications. You can concurrently monitor multiple, live processes that may reside on different machines.


WebSphere Application Server profiling
The ability to profile Java projects from WebSphere Studio is supplemented by the ability to effortlessly start and profile either a local or a remote WebSphere Application Server using Server Tools.


Logging
The logging capabilities of WebSphere Studio are manifested in the Activity Log view within the Profiling perspective for graphically and textually displaying real-time and batch-loaded logs. The WebSphere Application Server activity logs can only be viewed in the Activity Log view. The other log views are the Message Log view for viewing default records, and the Default Log view that displays all other log records.


The XML symptom database
The Logging tools can also present current solutions to known patterns found within the displayed logs. Log entries can be analyzed using an XML symptom database to interpret known events and error conditions. As Support staff locate reasons and solutions for unique errors and events cited within logs, entries are added to an XML symptom database with the appropriate search data for log entry and pattern matching. This provides the ability to analyze one or more log entries based on the most current symptom database for detailed information on error resolution and event significance.


Note:
Searching of symptom databases of any format is supported. But, currently only the WebSphere Application Server version 4.x and WebSphere Application Server version 5.x symptom databases are used.

Data transport and agent control technologies
The Agent Controller provides a means for extending application behavior so that information regarding the application's execution can be externalized and then collected either locally or remotely. The Profiling tools use this facility, as do various other IBM testing and debugging tools.

For more information about profiling and logging, refer to the online help.

Debugger
All products based on Eclipse include a debugger that enables you to detect and diagnose errors in your programs running either locally or remotely. The debugger lets you control the execution of your program by setting breakpoints, suspending execution, stepping through your code, and examining the contents of variables.

You can debug live server-side code as well as programs running locally on your workstation. The debugger includes a Debug view that shows threads and stack frames, a Processes view that shows all currently running and recently terminated processes, and a Console view that lets you interact with running processes. There are also views that display breakpoints and let you inspect variables.

The following debug components, all of which can be used for debugging locally and for remote debugging, are included:

The WebSphere Application Server debug adapter, which allows you to debug Web objects that are running on WebSphere Application Server. These objects include EJBs, JSPs, and servlets. Through use of the debug adapter, you can also debug server-side JavaScript.
The Java development tools (JDT) debugger, which allows you to debug Java.
The SQL Stored Procedure Debugger, which allows you to detect and diagnose errors in SQL procedures that are running on a DB2 server.
The Compiled language debugger, which allows you to debug compiled-language applications.