IBM® WebSphere® Everyplace® Deployment for Windows and Linux Version 6Access Services
IBM® WebSphere® Everyplace® Deployment for Windows and Linux Version 6 Access Services
This presentation introduces the Access Services provided by the IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 client.
Goals
Goals Understand the Access Services provided by the IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 client
The goal of this presentation is to understand the Access Services provided by the IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 client.
Agenda
Agenda Access Services Web Container Transaction Container JNDI Messaging Database Web Services Data Sync Framework
The agenda of this presentation is to provide an overview of the Access Services provided by the IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 client.
Section
Section Access Services
Here is the overview of the Access Services provided by the IBM WebSphere Everyplace Deployment for Windows and Linux Version 6 client.
Access Services
Access Services Value Extend backend programming model “out” to devices Services Web Container Transaction Container JNDI Messaging Database Web Services Data Sync Framework Standards J2EE subset, J2SE, J2ME W3C Web Services OMA JDBC 3.0 JMS 1.1 JNDI DB2 Everyplace DB2 Everyplace Isync Provider IBM Cloudscape IBM Cloudscape Isync Provider MQ Everyplace J2EE spec IBM providers IBM extensions JNDI Provider EJB 2.0 subset Transaction Container Servlet 2.4 JSP 2.0 Web Container Client Access Services Platform Management Managed Client Services Interaction Services SyncML4J/DS Web Services (Similar to JSR172) MicroBroker (Tech Preview) MQTT (Tech Preview) OSGi HttpService
Access Services provide a familiar programming model for J2EE developers so they can reuse their skills and components to develop applications that run on clients. Additionally, Access Services enable client applications to support offline operations. Access Services also enable you to move key components of your application to the client platform through the use of standard APIs.
J2EE Affinity Components
J2EE Affinity Components Web Container Servlet 2.4 / JSP 2.0 Servlet 2.3 / JSP 1.2 Embedded Transaction Container EJB 2.0 subset Database JDBC 3.0 DB2e or Cloudscape Supports offline operation via sync with Enterprise databases Point-to-Point Messaging JMS 1.1 WebSphere MQe Supports offline operation through local queuing of messages JNDI JDBC 3.0 JMS 1.1 JNDI DB2 Everyplace DB2 Everyplace Isync Provider IBM Cloudscape IBM Cloudscape Isync Provider MQ Everyplace J2EE spec IBM providers IBM extensions JNDI Provider EJB 2.0 subset Transaction Container Servlet 2.4 JSP 2.0 Web Container
Here are the specific Access Services that support affinity with the J2EE / WebSphere programming model. The client platform provides an embedded Web container to run Web applications that consist of JSP’s and servlets. The Web container enables you to move your Web applications from the server to clients to preserve the existing browser user interface, leverage your existing Web components, and provide a richer user experience through support of local and offline operations. The client platform also provides an embedded Transaction Container to run Embedded Transaction Applications that conform to a subset of the EJB 2.0 specification. This container enables you to move your business logic from the server to clients so you can leverage your existing beans to make business logic available to client applications, and support local and offline operations. These business logic components are referred to as Embedded Transaction applications. There are two key services that support local and offline operations. First, you can use the JDBC 3.0 API with DB2 Everyplace or IBM® Cloudscape™ as a local SQL database when more advanced data manipulations are required than can be supported by placing data in a local file store. These databases can periodically synchronize with Enterprise databases to capture data on the client for use by the client application when the user is offline. These databases can also protect local data through data encryption. Second, you can also use the Java Message Service (JMS) 1.1 API with WebSphere MQ Everyplace (MQe) to send and receive messages. MQe provides once-only, assured messaging and supports offline operations with local message queues that hold messages when the device is offline and then sends these queued messages to Enterprise applications when the device is back online. Similarly, messages destined for client applications are held in server-side message queues and then sent to the client applications when the device is back online. MQe encrypts messages to protect content over the network. As a result, the client platform enables your users to conduct secure e-business transactions. JNDI provides a name space so applications can utilize named objects.
Additional Components
Additional Components Mobile Web Services Similar to JSR 172 Publish and Subscribe Messaging MQ Telemetry Transport (MQTT) (Tech Preview) Microbroker (Tech Preview) SyncML4J Framework Open Mobile Alliance SyncML specification SyncML4J/DS Web Services (Similar to JSR172) MicroBroker (Tech Preview) MQTT (Tech Preview) OSGi HttpService XML Parsing
For online operations, the client platform supports Mobile Web Services so client applications can consume and provide Web Services in a secure manner. As a result, your users have access to a broad range of business data and consumer information. The client platform also supports a technical preview of the MQ Telemetry Transport and the MicroBroker, which is suitable for applications that require messaging, notification and event services. The MicroBroker supports publish and subscribe messaging. The SyncML4J (SyncML for Java) toolkit enables you to develop data synchronization client applications.
For more information…
For more information… To get more information on specific Access Services, please select from the following sub-topics: Web container and applications Embedded transaction container and JNDI Messaging Database Web Services
Slide 9
Trademarks, Copyrights, and Disclaimers The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM CICS IMS MQSeries Tivoli IBM(logo) Cloudscape Informix OS/390 WebSphere e(logo)business DB2 iSeries OS/400 xSeries AIX DB2 Universal Database Lotus pSeries zSeries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Other company, product and service names may be trademarks or service marks of others. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or program(s) described herein at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be used instead. Information is provided "AS IS" without warranty of any kind. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted, if at all, according to the terms and conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. IBM makes no representations or warranties, express or implied, regarding non-IBM products and services. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights-Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract and IBM Corp. Template Revision: 9/28/2005 5:50 PM