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.
子主题
ActivitySession 的端到端路径
此页面为查找有关 ActivitySession 的信息提供了一个起始点,ActivitySession 是 WebSphere 扩展,用来降低与一阶段落实资源相关联的落实规则和限制的复杂性。应用程序概要分析的端到端路径
此页面为查找有关应用程序概要分析的信息提供了一个起始点,应用程序概要分析是 WebSphere 扩展,用来定义策略以动态地控制并行、预取和预读。客户机应用程序的端到端路径
此页面为查找有关应用程序客户机和客户机应用程序的信息提供了一个起始点。应用程序客户机提供了一个框架,应用程序代码可以在此框架中运行,这样您的客户机应用程序就可以访问应用程序服务器中的信息。数据访问资源的端到端路径
此页面为查找有关数据访问的信息提供了一个起始点。各种企业信息系统 (EIS) 使用不同方法来存储数据。这些后端数据存储可能是关系数据库、过程化事务程序或面向对象的数据库。动态高速缓存的端到端路径
此页面为查找有关动态高速缓存服务的信息提供了一个起始点,该服务通过对 Servlet、命令、Web Service 和 JavaServer Pages (JSP) 文件的输出进行高速缓存来提高性能。动态和 EJB 查询的端对端路径
此页面为查找有关动态查询的信息提供了一个起始点,动态查询是一个可以实现应用程序空前灵活性的 WebSphere 编程扩展。此信息还包括 Enterprise JavaBeans (EJB) 查询,WebSphere 扩展构建于这个 Java 功能之上。EJB 应用程序的端到端路径
此页面为查找有关企业 Bean 的信息提供了一个起始点。国际化服务的端到端路径
此页面为查找有关全球化和国际化服务的信息提供了一个起始点,此服务是用于提高开发者工作效率的 WebSphere 扩展。邮件、URL 和其他 Java EE 资源的端到端路径
此页面为查找有关资源的信息提供了一个起始点,这些资源供符合 Java Enterprise Edition (Java EE) 标准的应用程序服务器上所部署的应用程序使用。其中包括:消息传递资源的端到端路径
用户可以将此页面作为起点,开始查找有关将企业应用程序的异步消息传递资源与 WebSphere Application Server 一起使用的信息。使用命令行工具迁移单元
命名和目录的端到端路径
此页面为查找有关命名支持的信息提供了一个起始点。命名包括服务器端组件和客户端组件。服务器端组件是一个公共对象请求代理体系结构 (CORBA) 命名服务 (CosNaming)。客户端组件是一个 Java 命名和目录接口 (JNDI) 服务提供程序。JNDI 是 Java Platform Enterprise Edition (Java EE) 编程模型中的一个核心组件。对象请求代理 (ORB) 的端到端路径
此页面为查找有关对象请求代理 (ORB) 的信息提供了一个起始点。此产品使用 ORB 来管理客户机应用程序与服务器应用程序之间的通信以及产品组件之间的通信。以下 Java™ Platform, Enterprise Edition (Java EE) 标准服务与 ORB 相关:远程方法调用/因特网 ORB 间协议 (RMI/IIOP) 和 Java 接口定义语言 (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.调度程序服务的端到端路径
此页面为查找有关调度程序服务的信息提供了一个起始点,调度程序服务是一个负责在特定时间或以特定时间间隔启动操作的 WebSphere 编程扩展。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 Service 的端到端路径
此页面为查找有关 Web Service 的信息提供了一个起始点。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