Administer application servers

1. Directory conventions
2. Create application servers
   • Settings
3. Create clusters
   Configure the server startup process such that only server components initially needed are started. When the server is configured such that only the components initially needed are started during the startup process, the remaining components are dynamically started as needed. If we are running other WebSphere products on top of this product, make sure that those other products support this functionality before we select this property.
4. Add members to a cluster
5. Configure virtual hosts
6. Configure the JVM
7. Manage WebSphere variables
8. Manage shared libraries
9. Set up peer restart and recovery
10. Manage application servers
11. wsadmin scripting
    Start processes that run on the same profile with user IDs with compatible file permissions. Each process can read or update files that the other processes create, ensuring processes can access the same files without encountering a permission-denied error. For example, If we run the deployment manager as user wasuser and then also run wsadmin to generate plug-ins on that same profile, we should run the tool as user wasuser.bprac
12. Generic servers
13. Transport chains
14. Custom services
15. Define application server processes
16. Tune application servers
17. Tune the application serving environment
18. Commands for the AdminTask object
19. Server collection

System i

1. QWAS85 subsystem
2. System i Navigator

z/OS

1. Enable/disable the reusable ASID function
2. Application server custom properties
3. Testing and production phases