Legend for "How do I?..." links
Legend for "How do I?..." links
|
Documentation
|
Show me
|
Tell me
|
Guide me
|
Teach me
|
| 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+ |
Establish the application serving environment
The following tasks involve establishing application serving capability in your network environment, whether you use single or clustered application servers. Servers can be grouped into administrative domains known as nodes and cells. See also the overview:
--------------------------------------------------------------------------
Create WebSphere profiles 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.
| Show me:
|
|
|
|
--------------------------------------------------------------------------
Administer nodes A node is a grouping of managed servers. Use this task to view information about and manage nodes.
|
|
| Tell me:
|
|
|
--------------------------------------------------------------------------
Administer node agents 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 cells 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 configurations 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.
|
|
| Tell me:
|
|
|
--------------------------------------------------------------------------
Configure remote file services 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.
|
|
|
|
|
|
--------------------------------------------------------------------------
Administer application servers 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.
| Documentation:
|
|
|
|
|
--------------------------------------------------------------------------
Administer other server types 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.
| Documentation:
|
| Tell me:
|
Guide me (Web servers)
|
|
--------------------------------------------------------------------------
Balance workloads by clustering application servers To monitor application servers and manage the workloads of servers, use server clusters and cluster members provided by the Network Deployment product.
| Documentation:
|
| Tell me:
|
|
|
--------------------------------------------------------------------------
Establishing high availability (HA) for failover 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.
|
|
| Tell me:
|
|
|
--------------------------------------------------------------------------
Administer the UDDI registry 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.
| Documentation:
|
|
|
|
|
--------------------------------------------------------------------------
Set up Web access for applications
These tasks involve enabling HTTP requests for applications on the application server.
--------------------------------------------------------------------------
Administer communication with Web servers (plug-ins) 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.
| Documentation:
|
|
|
|
|
--------------------------------------------------------------------------
Administer HTTP sessions Configure the service that the product provides for managing HTTP sessions: Session Manager.
| Documentation:
|
|
|
|
|
--------------------------------------------------------------------------
Administer IBM HTTP Server Version 6.x The product provides a complementary Web server with its own documentation that can be installed into the information center.
--------------------------------------------------------------------------
Set up resources for applications to use
Make a variety of resources available to your applications that are deployed on the application server.
--------------------------------------------------------------------------
Provide access to naming and directory resources (JNDI) Configure naming. Naming is used by clients of WebSphere Application Server applications to obtain references to objects related to those applications, such as 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.
| Documentation:
|
|
|
|
|
--------------------------------------------------------------------------
Provide access to relational databases (JDBC resources) Configure data sources that applications use to access the data from databases.
| Documentation:
| Show me:
|
|
|
|
--------------------------------------------------------------------------
Provide access to messaging resources (default messaging provider) 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.
| Documentation:
|
|
|
|
|
--------------------------------------------------------------------------
Use IBM
service integration technologies
|
|
| Tell me:
|
|
|
--------------------------------------------------------------------------
Establish workload balancing and high availability (HA) of messaging engines
|
|
|
|
|
|
--------------------------------------------------------------------------
Access Service Integration (SI) bus resources
|
|
| Tell me:
|
|
|
--------------------------------------------------------------------------
Deploy and administer applications
These tasks involve deploying applications onto the application server, then administering the applications.
--------------------------------------------------------------------------
Install applications Installable modules include enterprise archive (EAR), enterprise bean (EJB), Web archive (WAR), resource adapter (connector or RAR), and application client files.
| Documentation
|
|
|
|
|
--------------------------------------------------------------------------
Start and stop applications 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).
| Documentation:
|
|
|
|
|
--------------------------------------------------------------------------
Update applications 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.
| Documentation:
|
|
|
|
|
--------------------------------------------------------------------------
Deploy applications rapidly (WebSphere Rapid Deployment) Take advantage of new rapid deployment capabilities. WebSphere rapid deployment offers the following advantages: You do not need to assemble your J2EE application files prior to deployment. You do not need to use other installation tools mentioned in this table to deploy the files. Refer to the Rapid deployment tools documentation in the information center.
--------------------------------------------------------------------------
Enhanced EAR files
|
|
|
|
|
|
--------------------------------------------------------------------------
Deploy and administer Web services applications 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.
|
|
|
|
|
|
--------------------------------------------------------------------------
Use the administrative clients
A variety of tools are provided for administering the product.
--------------------------------------------------------------------------
Choose an administrative client Learn about and decide among the available administrative clients, including a graphical console, scripting (wsadmin), command line tools, and Java Management Extensions (JMX) programs.
|
|
|
|
|
|
--------------------------------------------------------------------------
Use the administrative console 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 scripting
(wsadmin) Scripting is a non-graphical alternative that you can use to configure and manage WebSphere Application Server. The WebSphere Application Server wsadmin tool provides the ability to run scripts. The tool supports a full range of product administrative activities.
|
|
|
|
|
|
--------------------------------------------------------------------------
Troubleshoot deployment and administration
Troubleshoot problems that occur when you are deploying applications onto the application server, or when you are administering an established application serving environment.
--------------------------------------------------------------------------
Troubleshoot deployment 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 administration Review some possible causes, based on the error you are seeing.
|
|
|
|
|
|
--------------------------------------------------------------------------
