Setting up the application serving environment
Set up production environments and realistic test environments for WebSphere® Application Server traditional. This includes performing post-installation and customization tasks, setting up web servers and application servers, and administering the application serving environment.
Subtopics
How do I set up the application serving environment?
Follow these shortcuts to get started quickly with popular tasks.Managing profiles on distributed and IBM i operating systems
You can create and delete profiles, which are sets of files that define the runtime environment. At least one profile must exist to run the product.Configuring port settings
When you configure WebSphere Application Server resources or assign port numbers to other applications, you must avoid conflicts with other assigned ports. In addition, you must explicitly enable access to particular port numbers when you configure a firewall.Administering nodes and resources
You can monitor and control incorporated nodes and the resources on those nodes by using these tasks with the administrative console or other administrative tools.Working with server configuration files
This topic show how to manage application server configuration files.Administering application servers
An application server configuration provides settings that control how an application server provides services for running applications and their components.Setting up Intelligent Management for dynamic operations
Dynamic operations monitor the middleware server environment and make recommendations or changes based on the data that is observed. To prepare the hosting environment for dynamic operations, federate middleware nodes, create the on demand router (ODR), create middleware servers and dynamic clusters, and deploy applications to your servers and dynamic clusters with an associated service policy.Balancing workloads
You should use server clusters and cluster members to monitor and manage the workloads of application servers.Enabling request-level Reliability Availability and Serviceability (RAS) granularity
You can enable request-level Reliability Availability and Serviceability (RAS) granularity for HTTP, IIOP, optimized local adapter, and certain MDB requests by defining RAS attributes in the workload classification document. With request-level RAS granularity, you can specify RAS attribute values for specific requests, such as a unique dispatch timeout value for all HTTP requests with a URI that ends in .jpg.


File name: welc6topserver.html