IBM WAS Network Deployment v8.5

| Home | Next

IBM WAS Network Deployment v8.5 - Distributed

Overview

Profiles Different types of WAS runtime environments.
Application server Platform on which Java language-based applications run.
Node Administrative grouping of application servers for configuration and operational management within one operating system instance.
Deployment manager Central administration point of a cell that consists of multiple nodes and node groups in a distributed server configuration.
Node agent In distributed server configurations, each node has a node agent that works with the deployment manager to manage administration processes.
Cell A cell is a group of nodes in a single administrative domain.
Administrative agent Management capabilities for multiple stand-alone application servers.
Job Manager Management capabilities for multiple stand-alone application servers, administrative agents, and deployment managers.

See: WAS V8.5 Concepts, Planning, and Design Guide, SG24-8022.

System management tools

WebSphere Customization Toolbox

Web Server Plug-in Configuration Tool
Profile Management Tool
z/OS Migration Tool

Integrated Solutions Console Browser-based client that uses a web application running in the web container to administer WAS. It can provide remote administration access.
wsadmin Non-graphical scripting interface that administers WAS from a command-line prompt. It uses the Bean Scripting Framework (BSF), which supports a variety of scripting languages and can provide remote administration access.
ANT Used for task automation. We can use it to create build scripts that compile, package, install, and test applications on WAS.
Administrative applications Develop custom Java applications that use JMX based on the WebSphere API.
Command-line utilities Perform common administrative tasks, such as starting and stopping the application server and backing up the configuration Command-line utilities work on local application servers, nodes, and the deployment manager only.

Profiles	Different types of WAS runtime environments.
Application server	Platform on which Java language-based applications run.
Node	Administrative grouping of application servers for configuration and operational management within one operating system instance.
Deployment manager	Central administration point of a cell that consists of multiple nodes and node groups in a distributed server configuration.
Node agent	In distributed server configurations, each node has a node agent that works with the deployment manager to manage administration processes.
Cell	A cell is a group of nodes in a single administrative domain.
Administrative agent	Management capabilities for multiple stand-alone application servers.
Job Manager	Management capabilities for multiple stand-alone application servers, administrative agents, and deployment managers.

WebSphere Customization Toolbox	Web Server Plug-in Configuration Tool Profile Management Tool z/OS Migration Tool
Integrated Solutions Console	Browser-based client that uses a web application running in the web container to administer WAS. It can provide remote administration access.
wsadmin	Non-graphical scripting interface that administers WAS from a command-line prompt. It uses the Bean Scripting Framework (BSF), which supports a variety of scripting languages and can provide remote administration access.
ANT	Used for task automation. We can use it to create build scripts that compile, package, install, and test applications on WAS.
Administrative applications	Develop custom Java applications that use JMX based on the WebSphere API.
Command-line utilities	Perform common administrative tasks, such as starting and stopping the application server and backing up the configuration Command-line utilities work on local application servers, nodes, and the deployment manager only.