WebSphere Application Server V6.1: System Management and Configuration
WebSphere Application Server
- WebSphere Application Server
- Packaging
- Supported platforms and software
- Operating systems
- Web servers
- Database servers
- Directory servers
Technics
- System management overview
- System management in a stand-alone server environment
- System management in a distributed server environment
- Java Management Extensions (JMX)
- JMX architecture
- JMX distributed administration
- JMX MBeans
- JMX usage scenarios
- J2EE management
- Distributed administration
- Distributed process discovery
- Centralized changes to configuration and application data
- File synchronization
- Configuration and application data repository
- Repository directory structure
- Variable scoped files
- Application data files
Profiles
- Understanding
- Types
- Directory structure
- Building a system
- Stand-alone server environment
- Distributed server environment
- Creating profiles on distributed systems (non z/OS)
- Deployment manager profile
- Application server profile
- Cell profile
- Custom profile
- Federating a custom node to a cell
- New appserver on an existing node
- Federating an appserver profile to a cell
- z/OS systems
- Managing
- manageprofiles command
- Deleting
- Managing
- Starting a distributed server environment
- Stopping the distributed server environment
- Enabling process restart on failure
Administration
- Introducing the WebSphere administrative console
- Starting the administrative console
- Logging in to the administrative console
- Changing the administrative console session timeout
- The graphical interface
- Finding an item in the console
- Updating existing items
- Adding new items
- Removing items
- Starting and stopping items
- Using variables
- Saving work
- Getting help
- Securing the administrative console
- Working with the deployment manager
- Deployment manager configuration settings
- Starting and stopping the deployment manager
- Working with appservers
- Creating an appserver
- Viewing the status of an appserver
- Starting an appserver
- Stopping an appserver
- Viewing run time attributes of an appserver
- Customizing appservers
- Working with nodes
- Adding (federating) a node
- Removing a node
- Renaming a node
- Node agent synchronization
- Starting and stopping nodes
- Node groups
- Working with clusters
- Creating clusters
- Viewing cluster topology
- Managing clusters
- Working with virtual hosts
- Creating a virtual host
- Managing applications
- Using the administrative console to manage applications
- Installing an enterprise application
- Uninstalling an enterprise application
- Exporting an enterprise application
- Starting an enterprise application
- Stopping an enterprise application
- Preventing an enterprise application from starting on a server
- Viewing application details
- Finding a URL for a servlet or JSP
- Managing your configuration files
- Backing up a profile
- Restoring a profile
- Exporting and importing profiles
Administration with scripting
- Overview of WebSphere scripting
- Using wsadmin
- Jacl versus Jython
- Launching wsadmin
- Configuring wsadmin
- Command and script invocation
- Overview of wsadmin objects
- Management using wsadmin objects
- Common operational tasks using wsadmin
- General approach for operational tasks
- Examples of common administrative tasks
- Managing the deployment manager
- Managing nodes
- Managing appservers
- Managing enterprise applications
- Managing clusters
- Generating the Web server plug-in configuration
- Enabling tracing for WebSphere components
- Common configuration tasks
- General approach for configuration tasks
- Specific examples of WebSphere configuration tasks
- Help creating wsadmin scripts
- Using Java for administration
- Online resources
WebSphere resources
- WebSphere resources
- JDBC resources
- What are JDBC providers and data sources?
- WebSphere support for data sources
- Creating a data source
- Creating a JDBC provider
- Creating JDBC data source
- JCA resources
- WebSphere Application Server JCA support
- Installing and configuring resource adapters
- Configuring J2C connection factories
- Using resource adapters from an application
- JavaMail resources
- JavaMail sessions
- Configuring the mail provider
- Configuring JavaMail sessions
- Example code
- URL providers
- Configuring URL providers
- Configuring URLs
- URL provider sample
- Resource environment providers
- Resource environment references
- Configuring the resource environment provider
- Resource authentication
- More information
Web servers
- Web server support overview
- Request routing using the plug-in
- Web server and plug-in management
- Working with Web servers
- Defining nodes and Web servers
- Viewing the status of a Web server
- Starting and stopping a Web server
- IBM HTTP Server remote administration
- Mapping modules to servers
- Working with the plug-in configuration file
- Regenerating the plug-in configuration file
- Propagating the plug-in configuration file
- Modifying the plug-in request routing options
Asynchronous messaging
- Messaging concepts
- Loose coupling
- Messaging types
- Destinations
- Messaging models
- Messaging patterns
- JMS
- JMS API history
- JMS providers
- JMS domains
- JMS administered objects
- JMS and JNDI
- JMS Connections
- JMS sessions
- JMS messages
- JMS message producers
- JMS message consumers
- JMS exception handling
- Application Server Facilities
- JMS and J2EE
- Messaging in the J2EE Connector Architecture
- Message endpoints
- MessageEndpointFactory
- Resource adapters
- JMS ActivationSpec JavaBean
- Message endpoint deployment
- Message endpoint activation
- Message delivery
- Administered objects
- Message-driven beans
- Message-driven bean types
- Client view of a message-driven bean
- Message-driven bean life cycle
- Message-driven beans and transactions
- Message-driven bean activation configuration properties
- Associating a message-driven bean with a destination
- Message-driven bean best practices
- Managing WebSphere JMS providers
- Managing the default messaging JMS provider
- Managing the WebSphere MQ JMS provider
- Managing a generic JMS provider
- Configuring WebSphere JMS administered objects
- Common administration properties
- Configuring the default messaging JMS provider
- Configuring the WebSphere MQ JMS provider
- Configuring listener ports
- Configuring a generic JMS provider
- Connecting to a service integration bus
- JMS client run time environment
- Controlling messaging engine selection
- Load balancing bootstrapped clients
- References and resources
Default messaging provider
- Service Integration Bus
- Messaging engines
- Message stores
- Destinations
- Mediations
- Foreign buses
- SIB service
- Message stores
- Exception destinations
- Service integration bus links
- WebSphere MQ links
- WebSphere MQ Servers
- Cluster bus members for high availability
- Cluster bus members for workload management
- Partitioned queues
- JMS clients connecting into a cluster of messaging engines
- Preferred servers and core group policies
- Best practices
- One server in the cell is a member of one bus
- Every server in the cell is a member of the same bus
- A single cluster bus member and one messaging engine
- A cluster bus member with multiple messaging engines
- Mixture of cluster and server bus members
- Multiple buses in a cell
- Service integration bus and message-driven beans
- Message-driven beans connecting to the bus
- MDBs and clusters
- Service integration bus security
- Problem determination
- Configuration and management
- SIB service configuration
- Creating a bus
- Configuring bus properties
- Enabling bus security
- Adding a bus member
- Creating a queue destination
- Creating a topic space destination
- Creating an alias destination
- Adding messaging engines to a cluster
- Setting up preferred servers
- Setting up a foreign bus link to a service integration bus
- Setting up a foreign bus link to an MQ queue manager
- Creating a foreign destination
Session management
- HTTP session management
- Session manager configuration
- Session management properties
- Accessing session management properties
- Session scope
- Session identifiers
- Choosing a session tracking mechanism
- SSL ID tracking
- Cookies
- URL rewriting
- Local sessions
- General properties for session management
- Session affinity
- Session affinity and failover
- Persistent session management
- Enabling database persistence
- Memory-to-memory replication
- Session management tuning
- Persistent sessions and non-serializable J2EE objects
- Larger DB2 page sizes and database persistence
- Single and multi-row schemas (database persistence)
- Contents written to the persistent store using a database
- Invalidating sessions
- Session listeners
- Session security
- Session performance considerations
- Session size
- Reducing persistent store I/O
- Multirow persistent sessions: Database persistence
- Managing your session database connection pool
- Session database tuning
- Stateful session bean failover
- Enabling stateful session bean failover
- Stateful session bean failover considerations
WebSphere naming
- Features
- WebSphere naming architecture
- Components
- JNDI support
- JNDI bindings
- Federated name space
- Local name space structure
- Interoperable Naming Service (INS)
- Bootstrap ports
- CORBA URLs
- Distributed CosNaming
- Configured bindings
- Types of objects
- Types of binding references
- Initial contexts
- Setting initial root context
- Federation of name spaces
- Foreign cell bindings
- Interoperability
- WebSphere V4.0 EJB clients
- WebSphere V4.0 server
- EJB clients hosted by non-WebSphere environment
- Examples
- Single server
- Two single servers on the same box
- Network Deployment appservers on the same box
- WebSphere Application Server V4 client
- Naming tools
- dumpNameSpace
- Configuration
- Name space bindings
- Foreign cell bindings
- CORBA naming service users and groups
Class loaders
- A brief introduction to Java class loaders
- WebSphere class loaders overview
- WebSphere extensions class loader
- Application and Web module class loaders
- Handling JNI code
- Configuring WebSphere for class loaders
- Class loader policies
- Class loading/delegation mode
- Shared libraries
- Class loader viewer
- Learning class loaders by example
- Step 1: Simple Web module packaging
- Step 2: Adding an EJB module and Utility jar
- Step 3: Changing the WAR class loader delegation mode
- Step 4: Sharing utility JARs using shared libraries
- Additional class loader diagnostics
Packaging applications
- Plants by WebSphere sample application
- Plants by WebSphere resources used
- Packaging using the Application Server Toolkit
- Import source code
- Working with deployment descriptors
- Setting application bindings
- Defining EJB JNDI names
- Binding EJB and resource references
- Defining data sources for entity beans
- Setting the context root for Web modules
- IBM EJB extensions: EJB caching options
- EJB container caching option for entity beans
- EJB container caching option for stateful session beans
- Stateful EJB timeout option
- IBM EJB extensions: EJB access intents
- Transaction isolation levels overview
- Concurrency control
- Using EJB 2.x access intents
- Using read-ahead hints
- Tracing access intents behavior
- IBM EJB extensions: inheritance relationships
- IBM Web module extensions
- File serving servlet
- Web application auto reload
- Serve servlets by class name
- Default error page
- Directory browsing
- JSP attributes
- Automatic HTTP request and response encoding
- IBM EAR extensions: Sharing session context
- Exporting the PlantsByWebSphere EAR file
- WebSphere Enhanced EAR
- Configuring a WebSphere Enhanced EAR
- Packaging recommendations
Deploying applications
- Preparing the environment
- Creating the Plants by WebSphere DB2 database
- Creating an environment variable
- Creating the Plants by WebSphere appserver
- Defining the Plants by WebSphere virtual host
- Creating the virtual host for IBM HTTP Server and Apache
- Creating a DB2 JDBC provider and data source
- Generating deployment code
- Using EJBDeploy command-line tool
- Deploying the application
- Using a bindings file
- Deploying application clients
- Defining application client bindings
- Launching the J2EE client
- Updating applications
- Replacing an entire application EAR file
- Replacing or adding an application module
- Replacing or adding single files in an application or module
- Removing application content
- Performing multiple updates to an application or module
- Rolling out application updates to a cluster
- Hot deployment and dynamic reloading
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index