WAS v8.5 > New features > New features overview: AdministeringWhat is new for administrators
This topic highlights what is new or changed, for users who are going to customize, administer, monitor, and tune production server environments. It also addresses those who are going to deploy and operate applications.
- Configure a messaging engine data store to use a data source
This parameter specifies whether the active messaging engine must retain long running locks on the SIBOWNER table in the database.
- Configure checkpoints
Configure a checkpoint to back up copies of files from the master configuration repository. A full checkpoint is a complete copy of the entire configuration repository. A delta checkpoint is a subset snapshot of the configuration repository that is made when we change a product configuration. Use a checkpoint to restore the configuration repository back to a prior state.
- Configure the memory leak policy
Detect, prevent, and take action, if possible, on classloader memory leaks using the memory leak detection policy. For more information about memory leaks, read the Memory Leaks in Java Platform, Enterprise Edition applications topic.
- XCT
Identify the root cause of problems across components, which provides the following benefits:
- Enables administrators and support teams to follow the flow of a request from end-to-end as it traverses thread or process boundaries, or travels between stack products and WAS.
- Helps to resolve questions about which component is responsible for a request that fails.
- HPEL
- We can use the LogViewer command-line tool to filter records based on the content of log and trace record extensions. The application server automatically creates an appName extension for each log and trace record related to a Java EE application, indicating the name of that application. The application server also automatically creates a requestID extension for each log and trace record created during the processing of certain types of requests (for example HTTP or JMS requests), indicating the unique ID of that request.
- Developers can use HPEL to add custom extensions to log and trace records through a log record context API (com.ibm.websphere.logging.hpel.LogRecordContext). When HPEL stores log and trace records, it includes any extensions present in the log record context on the same thread. For example, a developer might write a servlet filter to add important HTTP request parameters to the log record context. While that servlet runs, HPEL adds those extensions to any log and trace records created on the same thread.
- Memory leaks in Java Platform, Enterprise Edition applications
WAS v8.5 provides a top down pattern-based memory leak detection, prevention, and action by watching for suspect patterns in application code at run time. WAS has some means of protection against memory leaks when stopping or redeploying applications. If leak detection, prevention and action are enabled, monitors application and module activity performs diagnostic actions to detect and fix leaks when an application or an individual module stops. This feature helps in increasing application up time with frequent application redeployments without cycling the server.
- recoverMEConfig command
This command recovers the configuration data of the messaging engine of queues and topics from the message store.
- SCA in WAS: Overview
v8.5 adds support for the SCA OASIS programming model implementation.
- Use the IBM Support Assistant Data Collector
The IBM Support Assistant Data Collector for WAS tool focuses on automatic collection of problem data. It also provides symptom analysis support for the various categories of problems encountered by IBM software products. Information pertinent to a type of problem is collected to help identify the origin of the problem under investigation. The tool assists customers by reducing the amount of time it takes to reproduce a problem with the proper RAS tracing levels set, as well as by reducing the effort required to send the appropriate log information to IBM Support.