End-to-end paths
Start here for step-by-step guidance in using the product to reach your goals. First, identify the scenario that most closely matches your own project goal, such as updating and redeploying an existing application to include telephony services. Follow one of the linear paths to reach your goal. Conceptual background is provided to help you to adapt each path to your specific situation.
次主題
End-to-end paths for ActivitySessions
This page provides a starting point for finding information about ActivitySessions, a WebSphere extension for reducing the complexity of commitment rules and limitations that are associated with one-phase commit resources.應用程式設定檔作業的端對端路徑
此頁面提供了一個起始點,可尋找應用程式設定檔作業,也就是用來定義策略以動態控制並行性、預先提取和先讀的 WebSphere 延伸的相關資訊。End-to-end paths for client applications
This page provides a starting point for finding information about application clients and client applications. Application clients provide a framework on which application code runs, so that your client applications can access information on the application server.資料存取資源的端對端路徑
此頁面提供尋找資料存取相關資訊的起始點。各種企業資訊系統 (EIS) 利用不同的方法來儲存資料。這些後端資料儲存庫可能是關聯式資料庫、程序化交易程式或物件導向資料庫。動態快取的端對端路徑
這個頁面提供了一個起始點,可用來尋找動態快取服務的相關資訊,這項服務可快取 Servlet、指令、Web 服務和 JavaServer Pages (JSP) 檔的輸出,進而提昇效能。End-to-end paths for Dynamic and EJB query
This page provides a starting point for finding information about dynamic query, a WebSphere programming extension for unprecedented application flexibility. This information also includes Enterprise JavaBeans (EJB) query, the Java feature upon which the WebSphere extension is built.EJB 應用程式的端對端路徑
此頁面提供尋找 Enterprise Bean 相關資訊的起始點。End-to-end paths for internationalization service
This page provides a starting point for finding information about globalization and the internationalization service, a WebSphere extension for improving developer productivity.End-to-end paths for Mail, URLs, and other Java EE resources
This page provides a starting point for finding information about resources that are used by applications that are deployed on a Java Enterprise Edition (Java EE)-compliant application server. They include:End-to-end paths for messaging resources
This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WebSphere Application Server.使用指令行工具來移轉 Cell
End-to-end paths for naming and directory
This page provides a starting point for finding information about naming support. Naming includes both server-side and client-side components. The server-side component is a Common Object Request Broker Architecture (CORBA) naming service (CosNaming). The client-side component is a Java Naming and Directory Interface (JNDI) service provider. JNDI is a core component in the Java Platform, Enterprise Edition (Java EE) programming model.End-to-end paths for Object Request Broker (ORB)
This page provides a starting point for finding information about the Object Request Broker (ORB). The product uses an ORB to manage communication between client applications and server applications as well as among product components. These Java™ Platform, Enterprise Edition (Java EE) standard services are relevant to the ORB: Remote Method Invocation/Internet Inter-ORB Protocol (RMI/IIOP) and Java Interface Definition Language (Java IDL).End-to-end paths for OSGi applications
This page provides a starting point for step-by-step guidance in working with OSGi applications.End-to-end paths for scheduler service
This page provides a starting point for finding information about the scheduler service, a WebSphere programming extension responsible for starting actions at specific times or intervals.End-to-end paths for security
- End-to-end paths for service mapping
This page links to step-by-step guidance in working with service mapping. 階段作業起始通訊協定 (SIP) 應用程式的端對端路徑
這個頁面提供了一個起始點,可用來尋找 SIP 應用程式的相關資訊,SIP 應用程式為使用至少一個已寫入 JSR 116 規格之「階段作業起始通訊協定 (SIP)」Servlet 的 Java 程式。Web 應用程式的端對端路徑
此頁面提供了一個起始點,可尋找 Web 應用程式的相關資訊;這些 Web 應用程式是由可以當作一個單元來管理的一或多個相關檔案組成,其中包括:Web 服務的端對端路徑
此頁面提供尋找 Web 服務相關資訊的起始點。End-to-end paths for web services - RESTful services
You can use Java™ API for RESTful Web Services (JAX-RS) to develop services that follow Representational State Transfer (REST) principles. RESTful services are based on manipulating resources. Resources can contain static or dynamically updated data. By identifying the resources in your application, you can make the service more useful and easier to develop.End-to-end paths for web services - Security (WS-Security)
The Web Services Security specification defines core facilities for protecting the integrity and confidentiality of a message, and provides mechanisms for associating security-related claims with a message.End-to-end paths for web services - Addressing (WS-Addressing)
The Web Services Addressing (WS-Addressing) support in this product provides the environment for web services that use the World Wide Web Consortium (W3C) WS-Addressing specifications. This family of specifications provide transport-neutral mechanisms to address web services and to facilitate end-to-end addressing.End-to-end paths for web services - Resource framework (WSRF)
Web service interfaces often need to provide stateful interactions with the clients of the service. For example, a web service interface such as a shopping cart, where the result of one operation influences the carrying out of the succeeding operations. The OASIS Web Services Resource Framework (WSRF) defines a generic framework for modelling and accessing stateful resources using web services, so that the definition and implementation of a service and the integration and management of multiple services is easier.End-to-end paths for web services - Policy (WS-Policy)
WS-Policy is an interoperability standard that is used to describe and communicate the policies of a web service so that service providers can export policy requirements in a standard format. Clients can combine the service provider requirements with their own capabilities to establish the policies required for a specific interaction. This product conforms to the WS-Policy specification, so that policy information can be exchanged and received in accordance with the WS-Policy standard.End-to-end paths for web services - Reliable messaging (WS-ReliableMessaging)
To configure a web service application to use WS-ReliableMessaging, you attach a policy set that contains a WS-ReliableMessaging policy type. This policy type offers a range of qualities of service: managed persistent, managed non-persistent, or unmanaged non-persistent.End-to-end paths for web services - UDDI registry
The Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about web services. The UDDI specification defines a standard for the visibility, reusability, and manageability that are essential for a service-oriented architecture (SOA) registry service. The UDDI registry is a directory for web services that is implemented using the UDDI specification. It is a component of WebSphere® Application Server.End-to-end paths for web services - Transaction support (WS-Transaction)
WS-Transaction is an interoperability standard that includes the WS-AtomicTransaction, WS-BusinessActivity, and WS-Coordination specifications. The Web Services Atomic Transaction (WS-AT) support in the application server provides transactional quality of service to the web services environment. Distributed web services applications, and the resources they use, can take part in distributed global transactions. With Web Services Business Activity (WS-BA) support in the application server, web services on different systems can coordinate activities that are more loosely coupled than atomic transactions. Such activities can be difficult or impossible to roll back atomically, and therefore require a compensation process if an error occurs. Web Services Coordination (WS-COOR) specifies a CoordinationContext and a Registration service with which participant web services can enlist to take part in the protocols that are offered by specific coordination types.End-to-end paths for web services - Transports
Transport chains represent a network protocol stack that is used for I/O operations within an application server environment. Transport chains are part of the channel framework function that provides a common networking service for all components.
Related concepts:


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=welc6topthreads
檔名:welc6topthreads.html