What 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 using WebSphere® Application Server 傳統版. It also addresses users who are going to deploy and operate applications.
- 管理並行性
已淘汰的特性: Asynchronous beans and CommonJ Timer and WorkManager are deprecated asynchronous scheduling facilities that offer performance enhancements for resource-intensive tasks by enabling single tasks to run as multiple tasks. Concurrency Utilities for Java EE replaces these deprecated scheduling facilitiesdepfeat
You can configure work managers to use this capability available in the Concurrency Utilities for Java EE 1.0 specification.
The administrative console navigation has changed from
to .For more information, see Concurrency.
- Configuring Java EE default
resources
The Java EE specification defines six default resources, which the product provides in its default configuration. You configure a Java EE default resource provider by binding the Java Naming and Directory Interface (JNDI) name for a default resource to the JNDI name of a configured resource.
You can view and set bindings for Java EE default resources in the administrative console. Click Java EE default resources page.
to access theYou can also use the wsadmin commands and parameters in the JavaEEDefaultResources group to get and set bindings for Java EE default resources. JavaEEDefaultResources command group for the AdminTask object describes the commands and parameters.
- Utility command group of the
AdminTask object
Use the renameCell command to change the cell name of stand-alone application server, deployment manager, administrative agent, job manager, and federated node profiles.
- Identifying and modifying the JPA specification level
You can find information about supported JPA specification levels and JPA providers using the wsadmin tool or the administrative console.
Run the wsadmin AdminTask listSupportedJPASpecifications command to list JPA specification levels and default JPA providers supported by the product. Run the AdminTask showJPASpecLevel command to identify the JPA specification level used by a server. Run the AdminTask modifyJPASpecLevel command to change the JPA specification level used by a server.
In the administrative console, select the JPA specification level to use for the provider from the list on the Default Java Persistence API settings page.