What is new for administrators
- Set up routing rules for WAS traditional
Use the Intelligent Management for web servers feature of the Web Server Plug-ins for IBM WAS to route HTTP requests to the same application in multiple cells or to a subset of available servers.
- Administer concurrency
Deprecated feature: 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
facilities.depfeat
We 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 Resources > Asynchronous beans > Work managers to Resources > Concurrency > Work managers.
See Concurrency.
- Configure Java EE default resources
The Java EE specification defines six default resources, which WAS v9 provides in its default configuration. We configure a Java EE default resource provider by binding the JNDI name for a default resource to the JNDI name of a configured resource. We can view and set bindings for Java EE default resources in the administrative console...
-
Resources | Java EE default resources
We can also use the wsadmin commands in the JavaEEDefaultResources group to get and set bindings for Java EE default resources.
- 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.
- Identify and modify the JPA specification level
We can find information about supported JPA specification levels and JPA providers using the wsadmin tool or the administrative console.
To list JPA specification levels and default JPA providers supported by the product, run the wsadmin AdminTask listSupportedJPASpecifications 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, go to the Default Java Persistence API settings page and select the JPA specification level to use for the provider from the list.
Related: