WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

How do I administer applications and their environments?

Hold your cursor over the task icon (Task icon) to see a description of the task.

See also the overview:
Profiles are the files that define a stand-alone Application Server node, a managed node, or a deployment manager node. A profile also includes all of the files that the node can change. Create WebSphere profiles Documentation linkDocumentation Show me demonstration linkShow me: Presentation link Tell me

 

Blank

 

Blank
A node is a grouping of managed servers. Use this task to view information about and manage nodes. Administer nodes Documentation link Documentation Show me demonstration link Show me Presentation link Tell me:

 

Blank

 

Blank
Node agents are administrative agents that represent a node to your system and manage the servers on that node. Node agents monitor application servers on a host system and route administrative requests to servers. A node agent is created automatically when a node is added to a cell. Administer node agents Documentation link Documentation Show me demonstration link Show me Presentation link Tell me

 

Blank

 

Blank
When you installed the WebSphere Application Server Network Deployment product, a cell was created. A cell provides a way to group one or more nodes of your Network Deployment product. You probably will not need to reconfigure the cell. Use this task to view information about and manage a cell. Administer cells Documentation link Documentation Show me demonstration link Show me Presentation link Tell me

 

Blank

 

Blank
Application server configuration files define the available application servers, their configurations, and their contents. You should periodically save changes to your administrative configuration. You can change the default locations of configuration files, as needed. Administer configurations Documentation linkDocumentation

 

Blank
Presentation link Tell me:

 

Blank

 

Blank
Configuration data for the WebSphere Application Server product resides in files. Two services help you reconfigure and otherwise manage these files: the file transfer service and file synchronization service.  By default, the file transfer service is always configured and enabled at a node agent, so you do not need to take additional steps to configure this service. However, you might need to configure the file synchronization service. Configure remote file services Documentation linkDocumentation

 

Blank
Presentation link Tell me

 

Blank

 

Blank
Create, configure, and operate application server processes. An application server configuration provides settings that control how an application server provides services for running enterprise applications and their components. Administer application servers Documentation linkDocumentation: Show me demonstration link Show me Presentation link Tell me

 

Blank

 

Blank
One step in the process of creating an application server is to specify a template. A server template is used to define the configuration settings of the new server. You have the option of specifying the default server template or choosing a template that is based on a server that already exists. The default template will be used if you do not specify a different template when you create the server. You can create other types of servers, to represent Web servers in your topology, or for other purposes. There are two types of generic servers: (1) Non-Java applications or processes, or (2) Java applications or processes. A custom service provides the ability to plug into a WebSphere application server to define a hook point that runs when the server starts and shuts down. Administer other server types Documentation link Documentation:

 

Blank
Presentation linkTell me (generic servers) Cheat sheet link Guide me (Web servers)

 

Blank
To monitor application servers and manage the workloads of servers, use server clusters and cluster members provided by the Network Deployment product. Balance workloads by clustering application servers Documentation link Documentation: Show me demonstration link Show me Presentation link Tell me: Cheat sheet link Guide me

 

Blank
Planning ahead for high availability support is important in order to avoid the risk of a failure without failover coverage. The application server runtime of the infrastructure managed by a high availability manager includes such entities as cells and clusters. These components relate closely to core groups, high availability groups, and the policy that defines the high availability infrastructure. In a properly configured high availability environment, a high availability manager can reassess the environment it is managing and accept new components as they are added to the environment. Establishing high availability (HA) for failover Documentation linkDocumentation

 

Blank
Presentation link Tell me:

 

Blank

 

Blank
The UDDI Registry is supplied as a J2EE application file, uddi.ear. Change its configuration properties using the assembly tools. You can use either the WebSphere Application Server administrative console or the Java Management Extensions (JMX) management interface to manage UDDI Registries. Administer the UDDI registry Documentation linkDocumentation:

 

Blank
Presentation link Tell me

 

Blank

 

Blank
The product provides plug-ins for supported Web servers, to enable the Web servers to pass requests to the application server, for applications running on the application server. See also the Web server related tasks in How do I install an application serving environment? Administer communication with Web servers (plug-ins) Documentation link Documentation: Show me demonstration link Show me Presentation link Tell me Cheat sheet linkGuide me

 

Blank
Configure the service that the product provides for managing HTTP sessions: Session Manager. Administer HTTP sessions Documentation linkDocumentation: Show me demonstration link Show me

 

Blank

 

Blank

 

Blank
The product provides a complementary Web server with its own documentation that can be installed into the information center. Administer IBM HTTP Server Version 6.x
Configure naming. Naming is used by clients of WebSphere Application Server applications to obtain references to objects related to those applications, such as Enterprise JavaBeans (EJB) homes. These objects are bound into a mostly hierarchical structure, referred to as a name space. The name space structure consists of a set of name bindings, each consisting of a name relative to a specific context and the object bound with that name. Provide access to naming and directory resources (JNDI) Documentation link Documentation:

 

Blank
Presentation link Tell me:

 

Blank

 

Blank
Configure data sources that applications use to access the data from databases.Provide access to relational databases (JDBC resources) Documentation link Documentation: Show me demonstration link Show me: Presentation link Tell me Cheat sheet link Guide me

 

Blank
Use one of various ways to implement a messaging provider for use with WebSphere Application Server. A messaging provider enables use of the Java Messaging Service (JMS) and other message resources in the product. Provide access to messaging resources (default messaging provider) Documentation linkDocumentation: Show me demonstration link Show me Presentation link Tell me

 

Blank

 

Blank
Need description Use IBM service integration technologies

 

Blank

 

Blank
Presentation link Tell me:

 

Blank

 

Blank
Description needed Establish workload balancing and high availability (HA) of messaging engines

 

Blank

 

Blank
Presentation link Tell me

 

Blank

 

Blank
Description needed Access Service Integration (SI) bus resources

 

Blank
Show me demonstration link Show me Presentation link Tell me:

 

Blank

 

Blank
Installable modules include enterprise archive (EAR), enterprise bean (EJB), Web archive (WAR), resource adapter (connector or RAR), and application client files. Install applications Documentation linkDocumentation Show me demonstration link Show me Presentation link Tell me

 

Blank

 

Blank
You can start an application that is not running (has a status of Stopped) or stop an application that is running (has a status of Started). Start and stop applications Documentation linkDocumentation: Show me demonstration link Show me Presentation linkTell me

 

Blank

 

Blank
Update deployed applications or modules using the administrative console or wsadmin scripting. Learn which changes are candidates for hot deployment and dynamic reloading, in which you can make various changes to applications and their modules without having to stop the server and start it again. Update applications Documentation linkDocumentation:

 

Blank
Presentation link Tell me

 

Blank
Tutorial link Teach me
Description needed Deploy enhanced EAR files

 

Blank

 

Blank
Presentation link Tell me

 

Blank
Tutorial link Teach me
To deploy Web services that are based on the Web Services for Java 2 platform, Enterprise Edition (J2EE) specification, you need an enterprise application, also known as an enterprise archive (EAR) file that has been configured and enabled for Web services. You can use either the administrative console or the wsadmin scripting interface to deploy an EAR file. Deploy and administer Web services applications Documentation linkDocumentation Show me demonstration link Show me Presentation link Tell me

 

Blank
Learn about and decide among the available administrative clients, including a graphical console, scripting (wsadmin), command line tools, and Java Management Extensions (JMX) programs. Choose an administrative client DocumentationDocumentation link

 

Blank
Presentation link Tell me

 

Blank

 

Blank
The administrative console is a Web-based tool that you use to administer the product. The administrative console supports a full range of product administrative activities. Use the administrative console Documentation link Documentation Show me demonstration link Show me Presentation link Tell me

 

Blank

 

Blank
Scripting is a non-graphical alternative that you can use to configure and manage WebSphere Application Server. The WebSphere Application Server <b>wsadmin</b> tool provides the ability to run scripts. The tool supports a full range of product administrative activities. Use scripting (wsadmin) Documentation link Documentation

 

Blank
Presentation link Tell me

 

Blank

 

Blank
Troubleshoot problems that occur either during deployment or shortly afterwards, when you try to access an application that you just deployed for the first time. Troubleshoot deployment Documentation link Documentation

 

Blank

 

Blank

 

Blank

 

Blank
Review some possible causes, based on the error you are seeing. Troubleshoot administration Documentation linkDocumentation

 

Blank

 

Blank

 

Blank

 

Blank
Legend for "How do I?..." links
Detailed steps Documentation link Show meShow Me demonstration link Tell mePresentation link Guide meGuided activity link Teach meTutorial link
Refer to the detailed steps and reference Watch a brief multimedia demonstration View the presentation for an overview Be led through the console pages Perform the tutorial with sample code
Approximate time: Varies Approximate time: 3 to 5 minutes Approximate time: 10 minutes+ Approximate time: 1/2 hour+ Approximate time: 1 hour+



Sub-topics
Setting up the application serving environment

Related concepts
Overview and new features for administering applications and their environments

Concept topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/welc_howdoi_tadm.html

© Copyright IBM Corporation 2003, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)