Administrator best practices
This reference information describes best practices and other considerations for administrators.

Subtopics
Access role assignments for bus security resources
Icons are used in the administrative console to represent users and groups that have access roles for service integration bus resources.A client program does not work
ActivitySession and transaction container policies in combination
This topic provides details about the relationship between the deployment descriptor properties that determine how the container manages ActivitySession boundaries.addNode command best practices
Use the addNode command to add a stand-alone node into a cell.Administration and administrative console troubleshooting
Administrative console - browser connection problems
This topic describes problems that you can have when logging into the administrative console from a browser.Administrative console does not start even though installation completes
This topic discusses problems that you can encounter when you attempt to access the console.Administrative problems with the wsadmin scripting tool
Use this information if you are having problems starting or using the wsadmin tool.Alarm Manager counters
Use this page as a reference for properties of alarm manager counters.Altered database tables
A data store uses a relational database management system (RDBMS), working through JDBC, to store data as rows in a set of tables. A few of the database tables are altered as a result of running the sibDBUpgrade command.Applet client security requirements
When code is loaded, it is assigned permissions based on the security policy in effect. This policy specifies the permissions that are available for code from various locations. You can initialize this policy from an external policy file.Application deployment problems
You might encounter problems when deploying, installing, or promoting applications. This topic suggests ways to resolve the problems.Application deployment troubleshooting tips
When you first test or run a deployed application, you might encounter problems.Application profiling performance considerations
Application profiling enables assembly configuration techniques that improve your application run time, performance and scalability. You can configure tasks that identify incoming requests, identify access intents determining concurrency and other data access characteristics, and profiles that map the tasks to the access intents.Application Server start or restart problems
If a server process does not start or starts with errors, the following topics might help you to diagnose the problem.Application startup errors
Use this information for troubleshooting problems that occur when starting an application.Application startup problems
When an application is not starting or starting with errors, the problem could be from one of various sources.Application uninstallation problems
When you try to uninstall an application or node, you might encounter problems. This topic suggests ways to resolve uninstallation problems.ARM application properties and transaction context data
Request metrics provides build-in instrumentation to monitor transaction flows. The data that is collected by request metrics can be sent to a supported Application Response Measurement (ARM) agent.Asynchronous request dispatcher application design considerations
Asynchronous request dispatcher (ARD) is not a one-size-fits-all solution to servlet programming. You must evaluate the needs of your application and the caveats of using ARD. Switching all includes to start asynchronously is not the solution for every scenario, but when used wisely, ARD can increase response time.Avoiding errors when creating a messaging engine with a file store or a data store by using the wsadmin tool
Using different combinations of parameters can create a file store or a data store according your requirements. The outcome varies in server and cluster scopes.Avoiding message store errors when creating a messaging engine
Using different combinations of parameters can create a file store or a data store according your requirements. The outcome varies in server and cluster scopes.Bus-enabled web services default configuration for accessing a secure bus
By default, the bus-enabled web services component can access a secure service integration bus. This means that your Web services clients, if they provide suitable credentials when making requests, can use bus-enabled web services when bus security is enabled. You can modify or override the default configuration, for example by defining an authentication alias that the service integration resource adapter uses to access the bus.Bus-enabled web services installation files and locations
Cannot restart the Deployment Manager monitoring policy
The Deployment Manager monitoring policy is permanently set to STOPPED and cannot be changed. Therefore, if the Deployment Manager fails it will never be restarted by WebSphere® Application Server monitoring.Character code set conversion support for the Java Object Request Broker service
The CORBA/IIOP specification defines a framework for negotiation and conversion of character code sets used by the Java™ Object Request Broker (ORB) service.Clusters on which stateful session beans will be deployed
For a cluster of servers that span multiple systems in a sysplex, and that will have stateful session beans with an activation policy of Transaction deployed in them, the passivation directory should reside on an HFS (hierarchical file system) that is shared across the multiple systems in the sysplex on which the clustered servers will be running.Command-line tool problems
Troubleshoot a variety of problems relating to using command-line tools.Communications counters
These service integration bus communications counters are part of the performance monitoring infrastructure (PMI), which provides server-side monitoring and a client-side API to retrieve performance information. Communications counters are maintained across all components of WebSphere Application Server.Configuration properties for the Resource Adapter for JMS with WebSphere Application Server
As part of deploying the Resource Adapter for JMS with WebSphere Application Server, you must configure a set of JMS resources that the deployed resource adapter instance supports.Configuring caching policies for portlets
Fragment caching for portlets requires that you define a cache policy in a cachespec.xml file, either within the portlet web application archives (WAR) file or globally. If no caching policy is defined and applicable to a particular portlet, that porlet is not cached.Connection and connection pool statistics
WebSphere Application Server supports use of PMI APIs to monitor the performance of data access applications.Container interoperability
Container interoperability describes the ability of the product clients and servers at different versions to successfully negotiate differences in native Enterprise JavaBeans (EJB) finder methods support and Java EE compliance.Controller and Servant WLM classifications
Applications are deployed on a server or a cluster of servers. Each server consists of a controller and one or more servants. Each controller is started by the deployment manager, or by an MVS operator command as an MVS started tasks. Each servant is started by the Workload manager (WLM) as it is needed.Database privileges
In order for a messaging engine to use its data store, the database user ID that the messaging engine uses must have sufficient privilege to enable the messaging engine to access the data store tables. If you want the messaging engine to create the data store tables automatically, the messaging engine user ID requires additional privileges.Data replication domains
Data replication domains and multi-broker domains both perform the same function, which is to provide data replication between application servers in a cluster. Even though you can still configure existing multi-broker domains with the current version of the product, after you upgrade your deployment manager, you can only create data replication domains in the administrative console.Data store tables
A data store uses a relational database management system (RDBMS), working through JDBC, to store data as rows in a set of tables. This data is important when you are backing up or restoring a data store.Default Application
WebSphere Application Server provides a default configuration that administrators can use to easily verify that the Application Server is running. When the product is installed, it includes an application server called server1 and an enterprise application called Default Application.Default authentication token
Do not use the default authentication token in service provider code. This default token is used by the WebSphere Application Server run-time code only and is authentication mechanism specific.Disabling servlet pooling: Best practices and considerations
You might want to disable request and response pooling if your application is creating threads inside of the application or if you are concerned about the web container reusing request and response objects.Distribution and consistency services (DCS) stack counters
You can use the Distribution and Consistency Services (DCS) counters that the Performance Monitoring Infrastructure (PMI) and Tivoli® Performance Viewer (TPV) collect to monitor communication between core groups.Dynamic cache counters
Use this page as a reference for properties of dynamic cache counters.Dynamic cache provider for the JPA 2.0 second level cache
Learn to use the WebSphere Application Server dynamic cache service as a Java Persistence API (JPA) second level (L2) cache provider. JPA 2.0 has standardized the L2 cache interface. WebSphere Application Server supports the JPA standard. The dynamic cache service plugs in as a level 2 cache provider to JPA. The L2 cache boosts the performance of your JPA application and you can configure and monitor the dynamic cache service for your JPA application in the WebSphere Application Server environment.Dynamic caching with Asynchronous Request Dispatcher
Asynchronous Request Dispatcher (ARD) improves servlet response time when slow operations are logically separated and performed concurrently with other operations that are required to complete the response.Enterprise Identity Mapping identity token connection factory parameters
The following table is a summary of the parameters or custom properties that are referenced by the Enterprise Identity Mapping (EIM) identity token connection factory. These parameters are necessary when you configure the EIM identity token connection factory.EJBDEPLOY relationships – troubleshooting tips
Use this information to troubleshoot information for EJBDEPLOY problems.EJB method Invocation Queuing
Method invocations to enterprise beans are only queued for remote clients making the method call. An example of a remote client is an Enterprise JavaBeans (EJB) client running in a separate Java virtual machine (JVM) (another address space) from the enterprise bean. In contrast, no queuing occurs if the EJB client, either a servlet or another enterprise bean, is installed in the same JVM on which the EJB method runs, and on the same thread of execution as the EJB client.Embeddable EJB container functions
According to the Enterprise JavaBeans (EJB) 3.2 specification, all embeddable EJB containers that vendors use must at least implement the EJB Lite subset of EJB functionality. The application server also contains additional features that support the EJB Lite subset. Refer to the EJB 3.2 specification for more information.Enterprise bean counters
Use this page as a reference for properties of enterprise bean counters.Example: Running the thin client with security enabled
Your Java thin application client no longer needs additional code to set security providers if you have enabled security for your WebSphere Application Server instance. This code found in IBM i Java thin clients should be removed to prevent migration and compatibility problems. The java.security file from your WebSphere instance in the properties directory is now used to configure the security providers.Example values for endpoint listener configuration
You can configure any number of endpoint listeners with values of your own choosing, including the example values given in this topic.Extension registry counters
Use this page as a reference for properties of extension registry counters.Federated repositories limitations
This topic outlines known limitations and important information for configuring federated repositories.High availability manager counters
You can use the high availability manager counters that the Performance Monitoring Infrastructure (PMI) and Tivoli Performance Viewer (TPV) collect to monitor activity within your high availability environment.IBM Tivoli Composite Application Manager for WebSphere Application Server counters
Use this page as a reference for properties of IBM® Tivoli Composite Application Manager for WebSphere Application Server counters.Implementing JAX-RPC handlers to access SDO messages
JAX-RPC handlers are invoked during the processing of request and response messages. For messages that are exchanged by using the SOAP protocol, each JAX-RPC handler is passed a SOAP-specific MessageContext object. For other protocols, the IBM web services runtime environment passes a MessageContext object that provides a Service Data Objects view of the message. Service Data Objects (SDO) is an open standard for enabling applications to handle data from different data sources in a uniform way, as data graphs.Initial context support
All naming operations begin with obtaining an initial context. You can view the initial context as a starting point in the namespace. Use the initial context to perform naming operations, such as looking up and binding objects in the namespace.Intelligent Management: application edition manager states
Intelligent Management: static clusters versus dynamic clusters
Static clusters in a WebSphere Application Server Network Deployment configuration are different from the dynamic clusters that you can define in Intelligent Management. Both types of clusters support workload balancing, however, dynamic clusters are controlled by autonomic managers that can optimize the performance of the cluster.J2C connection pool counters
Use this page as a reference for properties of J2C connection pool counters.Java Authentication and Authorization Service authorization
Java 2 security architecture uses a security policy to specify which access rights are granted to running code. This architecture is code-centric. The permissions are granted based on code characteristics including where the code is coming from, whether it is digitally signed, and by whom. Authorization of the Java Authentication and Authorization Service (JAAS) augments the existing code-centric access controls with new user-centric access controls. Permissions are granted based on what code is running and who is running it.JavaMail API security permissions best practices
In many of its activities, the JavaMail API needs to access certain configuration files. The JavaMail and JavaBeans Activation Framework binary packages themselves already contain the necessary configuration files. However, the JavaMail API allows the user to define user-specific and installation-specific configuration files to meet special requirements.JavaServer Pages troubleshooting tips
Use this tips to troubleshoot problems with JavaServer Pages.Java virtual machine counters
You can use the Java virtual machine (JVM) counters that the Performance Monitoring Infrastructure (PMI) and Tivoli Performance Viewer (TPV) collect to monitor JVM performance.JDBC connection pool counters
This topic defines the JDBC connection pool counters that are used to monitor the performance of JDBC data sourcesJNDI support in WebSphere Application Server
The product includes a name server to provide shared access to Java components, and an implementation of the javax.naming JNDI package which supports user access to the name server through the Java Naming and Directory Interface (JNDI) naming interface.JSP run time compilation settings
By default, the JavaServer Pages (JSP) engine translates a requested JSP file, compiles the .java file, and loads the compiled servlet into the run time environment. You can change the JSP engine default behavior by indicating that a JSP file must not be translated or compiled at run time, even when a .class file does not exist.Local transaction containment
IBM WebSphere Application Server supports local transaction containment (LTC), which you can configure using local transaction extended deployment descriptors. LTC support provides certain advantages to application programmers. Use the scenarios provided, and the list of points to consider, to help you decide the best way to configure transaction support for local transactions.Lookup names support in deployment descriptors and thin clients
Server application objects, such as enterprise bean (EJB) homes, are bound relative to the server root context for the server in which the application is installed. Other objects, such as resources, can also be bound to a specific server root. The names used to look up these objects must be qualified so as to select the correct server root. This topic discusses what relative and qualified names are, when they can be used, and how you can construct them.MBean cache statistics
Use this page as a reference for properties of MBean cache statistics.Mediation framework counters
These service integration bus mediation framework counters are part of the performance monitoring infrastructure (PMI), which provides server-side monitoring and a client-side API to retrieve performance information.Mediation thread pool properties
The following table describes the default thread pool properties for the mediationsThreadPool object for a messaging engine.Message processor counters
These service integration bus message processor counters are part of the performance monitoring infrastructure (PMI), which provides server-side monitoring and a client-side API to retrieve performance information.Message store counters
These service integration bus message store counters are part of the performance monitoring infrastructure (PMI), which provides server-side monitoring and a client-side API to retrieve performance information.Migration to the Thin Client for JMS with WebSphere Application Server
There are a number of differences to consider when migrating to the Thin Client for JMS with WebSphere Application Server from an earlier version of the client.Multiserver environment errors
Use this information to troubleshoot problems with setting up multiserver environments.Object and file security
This topic discusses the various objects and files that contain sensitive information and need to be protected.Object Pool counters
Use this page as a reference for properties of Object Pool counters.Object Request Broker counters
You can use the Object Request Broker (ORB) counters that the Performance Monitoring Infrastructure (PMI) and Tivoli Performance Viewer (TPV) collect to monitor ORB operations.Object Request Broker tuning guidelines
Use the guidelines in this document any time the Object Request Broker (ORB) is used in a workload.Performance: Resources for learning
Use the following links to find relevant supplemental information about performance. The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.Plug-ins configuration
The Web Server Plug-ins Configuration Tool configures an application server for a web server type and creates a web server definition in the configuration of the application server. Become familiar with the different processing paths that the Web Server Plug-ins Configuration Tool can use.PMI data classification
This topic describes the Performance Monitoring Infrastructure (PMI) data classification.PMI data organization
Use this page as a general overview of monitoring, data collection, and counters using Performance Monitoring Infrastructure (PMI) and Tivoli Performance Viewer.PortletContainer PMI counters
Use this page as a reference for properties of PortletContainer PMI counters.Port number settings for batch
Identify the default port numbers used in the various configuration processes to avoid port conflicts.Properties file syntax
To use the properties file based configuration tool, properties files must use supported syntax.Proxy counters
Use this page as a reference for properties of proxy counters.RACF keyring setup
Resolving application configuration conflicts
In a shared environment with multiple administrative users, it is possible that different administrative users might attempt concurrent updates of the same WebSphere Application Server configuration documents. The following information should help you detect and deal with any exceptions that might occur if multiple administrative users attempt to concurrently update the same configuration documents.Resource Recovery Services Operations
This topic provides tips for using the z/OS® Resource Recovery Services with this product.Sample custom adapters for federated repositories examples
Out of the box adapters for federated repositories provide File, LDAP, and Database adapters for your use. These adapters implement the com.ibm.wsspi.wim.Repository software programming interface (SPI). A virtual member manager custom adapter needs to implement the same SPI, irrespective of the type of repositories the adapter is interacting with. There is no restriction on the type of repositories that the custom adapter can interact with.Scalable Vector Graphics problems
Consult this topic for problems and solutions for Scalable Vector Graphics.Scheduler counters
Use this page as a reference for properties of Scheduler counters.Scheduler table definition
Schedulers require database tables and indices with a table prefix. This page provides reference information about the tables.Scheduler table management functions
The administration console and the WASSchedulerConfiguration MBeans provide simplified methods for creating scheduler tables and schema, verifying that the scheduler tables and schema are setup properly and are accessible and removing scheduler tables and schema.Security considerations for web services
When you configure Web Services Security, you should make every effort to verify that the result is not vulnerable to a wide range of attack mechanisms. There are possible security concerns that arise when you are securing web services.Security considerations when adding a base Application Server node to WebSphere Application Server, Network Deployment
You might decide to centralize the configuration of your stand-alone base application servers by adding them into a WebSphere Application Server, Network Deployment cell. If your base application server is currently configured with security, some issues require consideration. The major issue when adding a node to the cell is whether the user registries between the base application server and the deployment manager are the same.Security considerations when registering a base Application Server node with the administrative agent
You might decide to centralize the control of your stand-alone base application servers by registering them with the administrative agent. If your base application server is currently configured with security, some issues require consideration. These security considerations apply to the use of the registerNode command and the deregisterNode command.Security states with thread identity support
Different Java Platform, Enterprise Edition Connector Architecture (JCA) resource adapters and Java Database Connectivity (JDBC) drivers provide different support for authenticating threads that transact with application server resources.Server hangs during shutdown if it creates a Java core dump (Red Hat Linux)
When you run the stopServer.sh script on Red Hat Linux Advanced Server Version 2.1 with the latest operating system patches, it creates a Java core dump and hangs the terminal.Server process authorization checking
You can specify specific access restrictions to z/OS resources.Service integration bus counters
These service integration bus counters are part of the performance monitoring infrastructure (PMI), which provides server-side monitoring and a client-side API to retrieve performance information.Servlet session counters
Use this page as a reference for properties of servlet session counters.Session recovery support
For session recovery support, WebSphere Application Server provides distributed session support in the form of database sessions and memory-to-memory replication. You can use session recovery support when the user's session data must be maintained across a server restart or when the user's session data is too valuable to lose through an unexpected server failure.Session security support
You can integrate HTTP sessions and security in WebSphere Application Server. When security integration is enabled in the session management facility and a session is accessed in a protected resource, you can access that session only in protected resources from then on. Session security (security integration) is enabled by default.setupCmdLineXJB.bat, launchClientXJB.bat and other ActiveX batch files
Client applications and client services can use aids to access the ActiveX to EJB bridge. These aids enable the ActiveX to Enterprise JavaBeans (EJB) bridge to find its XJB.JAR file and the Java run-time environment.Single sign-on capability with SPNEGO TAI - checklist (deprecated)
WebSphere Application Server provides a trust association interceptor (TAI) that uses the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) to securely negotiate and authenticate HTTP requests for secured resources in WebSphere Application Server. To deploy and use the SPNEGO TAI you need to examine your installation and decide on how best to configure the SPNEGO TAI.SIP industry standards compliance
The product implementation of Session Initiation Protocol (SIP) complies with industry standards for both a SIP container and SIP applications.SIP PMI counters
The Session Initiation Protocol (SIP) provides the following counters in the WebSphere Performance Monitoring Infrastructure (PMI) to monitor the performance of SIP.SIP SipServletRequest and SipServletResponse classes
The SipServletRequest and SipServletResponse classes are similar to the HttpServletRequest and HttpServletResponse classes.SIP SipSession and SipApplicationSession classes
Possibly the most complex portions of the SIP Servlet 1.0 specification are the SipSession and SipApplicationSession classes.SPNEGO TAI configuration requirements (deprecated)
The configuration that is used by the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) trust association interceptor (TAI) on each selected application server is governed by various system requirements.States of the WebSphere MQ link and its channels
For each possible state of a WebSphere MQ link, this table lists the associated states of the link's sender and receiver channels.System counters
You can use the system counters that the Performance Monitoring Infrastructure (PMI) and Tivoli Performance Viewer collect to monitor how efficiently your system a specific machine (node) is running.Terminology from the WS-Notification standards
The terminology defined in this topic is defined by the WS-Notification specifications and is common to any vendor implementation of these specifications.The createQueue or createTopic method and the default messaging provider
You can use the Session.createQueue(String) method or Session.createTopic(String) method instead of using JNDI lookup to create a JMS Queue or JMS Topic with the default messaging provider.The SDO repository uninstall script
Use this script to uninstall a Service Data Objects (SDO) repository that was previously installed, or failed to install correctly.Third-party performance monitoring and management solutions
Several performance monitoring, problem determination, and management solutions are available that can be used with WebSphere Application Server.Thread pool counters
You can use the thread pool counters that the Performance Monitoring Infrastructure (PMI) and Tivoli Performance Viewer (TPV) collect to monitor your thread pool activity.Timeout condition resolutions
This topic gives an overview of how to resolve timeout conditions.Timeout conditions - possible causes and fixes
This file lists common timer variables and tools for monitoring these timeout conditionsTopic names and use of wildcard characters in topic expressions
Wildcard characters can be used in topic expressions to retrieve topics provided by the default messaging provider and service integration technologies.Transaction counters
Use this page as a reference for properties of transaction counters.Transport chain problems
Review the following topics if you encounter a transport chain problem.UDDI registry terminology
Some terms specific to the UDDI registry are explained. Also, the relationship between the versions of the UDDI registry, the Organization for the Advancement of Structured Information (OASIS) specification, and the WebSphere Application Server level are shown.Usage model for using ActivitySessions with HTTP sessions
This topic describes how a Web application that runs in the WebSphere Web container can participate in an ActivitySession context.Using the ktab command to manage the Kerberos keytab file
The Kerberos key table manager command (Ktab) allows the product administrator to manage the Kerberos service principal names and keys stored in a local Kerberos keytab file. With the IBM Software Development Kit (SDK) or Sun Java Development Kit (JDK) 1.6 or later, you can use the ktab command to merge two Kerberos keytab files.Web application counters
Web container troubleshooting tips
Web module or application server stops processing requests
If an application server process spontaneously closes, or web modules stop responding to new requests, it is important that you quickly determine why this stoppage is occurring. You can use some of the following techniques to determine whether the problem is a web module problem or an application server environment problem.Web resource is not displayed
Use this information to troubleshoot problems that occur when attempting to display a resource in a browser.Web server plug-in troubleshooting tips
The following topics might help you diagnose problems with the web server plug-ins.Web services client to web container optimized communication
To improve performance, an optimized communication path between a web services client application and a web container are located in the same application server process. Requests from the web services client that are normally sent to the web container using a network connection are delivered directly to the web container using an optimized local path. The local path is available because the web services client application and the web container run in the same process.Web services counters
Use this page as a reference for properties of web services counters.Web services gateway counters
These service integration bus web services gateway counters are part of the performance monitoring infrastructure (PMI), which provides server-side monitoring and a client-side API to retrieve performance information. Examples of web services gateway counters are the number of synchronous and asynchronous requests and responses.Web Services Security configuration considerations
To secure web services for WebSphere Application Server, you must specify several different configurations. Although there is not a specific sequence in which you must specify these different configurations, some configurations reference other configurations.WebSphere Application Server roles and goals
There are several different computing roles that members of your organization might undertake when working with WebSphere Application Server.WebSphere Application Server-specific WS-Notification terminology
This terminology is implementation-specific, beyond the terminology defined in the WS-Notification standards, and applies to the WS-Notification implementation in WebSphere Application Server.IBM MQ server: Restrictions with mixed level cells and clusters
If you are using a IBM MQ server with cells or clusters that include more than one version of WebSphere Application Server, you might need to be aware of the application server versions when you deploy applications that communicate with IBM MQ queues.WLM Delay Monitoring
WebSphere Application Server for z/OS uses Workload Manager (WLM) services to report transaction begin-to-end response times and execution delay times.Workload classification file
The workload classification document is a common XML file that classifies inbound HTTP, IIOP, message-driven bean (MDB), Session Initiation Protocol (SIP), optimized local adapter, and mediation work for the z/OS workload manager.Workload is not getting distributed
This information might help you diagnose the trouble if you are having a workload distribution problem.Workload management (WLM) tuning tips for z/OS
You can use the administrative console to provide the job control language (JCL) PROC name for the servant and the JCL Parm for the servant and thereby set up a dynamic application environment. Even if you set up a dynamic application environment, you must set the WLM goals for your environment.Workload management component troubleshooting tips
If the workload management component is not properly distributing the workload across servers in multi-node configuration, use the following options to isolate the problem.Workload Management counters
You can use the workload management counters that the Performance Monitoring Infrastructure (PMI) and Tivoli Performance Viewer (TPV) collect to monitor how efficiently your workload is managed.WS-Notification roles and goals
This topics lists a set of computing roles that members of your organization might perform, and explains how you can use WS-Notification to help meet the goals of each role.WS-Notification terminology
There is terminology that you must be aware of when working with WS-Notification. Most of this terminology is defined by the WS-Notification standards, and a few terms are defined to describe this implementation of WS-Notification for WebSphere Application Server.WS-ReliableMessaging: supported specifications and standards
WebSphere Application Server provides support for two levels of the WS-ReliableMessaging specification. This gives compatibility with vendors that provide WS-ReliableMessaging support at the February 2005 level, as well as meeting the requirements of the current OASIS specification. This implementation of WS-ReliableMessaging also composes with many other web services standards.WS-ReliableMessaging - requirements for interaction with other implementations
The information and configuration that is needed for another vendor's reliable messaging source to send messages to a WebSphere Application Server reliable messaging destination, or for a WebSphere Application Server reliable messaging source to send messages to another vendor's reliable messaging destination.WS-ReliableMessaging roles and goals
Computing roles that members of your organization might perform, and how you can use WS-ReliableMessaging to help meet the goals of each role.WS-ReliableMessaging - terminology


File name: welc_ref_adm_consid.html