Set up the full profile

Set up production environments and realistic test environments for the WAS full profile. This includes performing post-installation and customization tasks, setting up web servers and application servers, and administering the application serving environment.

Subtopics

• Configure 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.

• Manage profiles
  We 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.

• Administer nodes and resources
  We can monitor and control incorporated nodes and the resources on those nodes using these tasks with the console or other administrative tools.

• (dist)(zos) Notification email parameters
  Use this page to modify the cell-wide task notification email parameters.

• (dist)(zos) Runtime tasks collection
  Tasks are generated by runtime components . When a task generates, information is provided so that we can accept or deny the suggested action plan. There are various types of tasks, depending on the task actions and status.

• (dist)(zos) Task details
  This page defines information about the runtime task, the objects that the task targets, and the action plan for the task.

• Work with server configuration files
  This topic show how to manage application server configuration files.

• Administer application servers
  An application server configuration provides settings that control how an application server provides services for running applications and their components.

• (dist)(zos) Set 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 the 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.

• (zos) Enable request-level Reliability Availability and Serviceability (RAS) granularity
  We 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, we 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.

Subtopics

• Configure 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.

• Manage profiles
  We 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.

• Administer nodes and resources
  We can monitor and control incorporated nodes and the resources on those nodes using these tasks with the console or other administrative tools.

• (dist)(zos) Notification email parameters
  Use this page to modify the cell-wide task notification email parameters.

• (dist)(zos) Runtime tasks collection
  Tasks are generated by runtime components . When a task generates, information is provided so that we can accept or deny the suggested action plan. There are various types of tasks, depending on the task actions and status.

• (dist)(zos) Task details
  This page defines information about the runtime task, the objects that the task targets, and the action plan for the task.

• Work with server configuration files
  This topic show how to manage application server configuration files.

• Administer application servers
  An application server configuration provides settings that control how an application server provides services for running applications and their components.

• (dist)(zos) Set 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 the 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.

• (zos) Enable request-level Reliability Availability and Serviceability (RAS) granularity
  We 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, we 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.