These end-to-end paths feature the latest design. 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.
You can set up a single-server environment to use the computer telephony integration (CTI) and web collaboration capabilities of IBM® WebSphere® Application Server Version 8.0.
You can embed the ClickToCall widget in an existing application to enable users to enter their phone number and request an immediate callback from your company. You embed the communications enabled applications (CEA) widget using the Dojo Toolkit provided with the CEA feature.
You can embed the CallNotification widget in an existing application to enable users to enter their phone number and receive notifications of incoming calls. You embed the communications enabled applications (CEA) widget using the Dojo Toolkit provided with the CEA feature.
You can embed the Cobrowse widget in an application so that users can share the same browsing session, with one user controlling the session. You can use the Dojo Toolkit that comes with the CEA feature to embed the CEA widgets in your applications.
You can create and configure two-way forms in web applications using the communications enabled applications (CEA) TwoWayForm widget.
You can integrate telephony services into new and existing applications using the web services interface of communications enabled applications (CEA). Telephony services include making phone calls, receiving phone calls, and receiving call notifications within the web application.
You can configure communications enabled applications (CEA) to use an external web service provider that supports the CEA Web Services Description Language (WSDL) file.
You can integrate web telephony into new and existing applications using a Representational State Transfer (REST) API. Telephony features include making phone calls, receiving phone calls, and receiving call notifications within the web application.
You can build cobrowsing into applications using REST APIs. A cobrowsing session allows two web users to share the same browsing session using side-by-side modal windows. One user controls the session; the other user has no control, but can view the activity of the other user.
Use this task when you are implementing Enterprise JavaBeans (EJB) 2.x applications.
Use this task when you are implementing Enterprise JavaBeans (EJB) 3.x applications.
Use this task when you are implementing Enterprise JavaBeans (EJB) applications that use timers.
Transport-level security is a well-known and often used mechanism to secure HTTP Internet and intranet communications. Transport level security can be used to secure web services messages. Transport-level security functionality is independent from functionality that is provided by message-level security (WS-Security) or HTTP basic authentication.
A simple way to provide authentication data for the service client is to authenticate to the protected service endpoint by using HTTP basic authentication. HTTP basic authentication uses a user name and password to authenticate a service client to a secure endpoint.
Web Services Security standards and profiles address how to provide message-level protection for messages that are exchanged in a web service environment.
Standards and profiles address how to provide protection for messages that are exchanged in a web service environment.
The Security Assertion Markup Language (SAML) is an XML-based OASIS standard for exchanging user identity and security attributes information. Using SAML, a client can communicate assertions regarding the identity, attributes, and entitlements of a SOAP message. You can apply policy sets to JAX-WS applications to use SAML assertions in web services messages and in web services usage scenarios. Use SAML assertions to represent user identity and user security attributes, and optionally, to sign and to encrypt SOAP message elements.
You can use the generic security token login modules to issue, validate, and exchange security tokens using an external Security Token Service (STS).
You must configure Lightweight Third Party Authentication (LTPA) when you set up security for the first time. LTPA is the default authentication mechanism for WebSphere Application Server. After you have configured LTPA you can generate LTPA keys manually or automatically.
Using Java Authentication and Authorization Service (JAAS), you can customize your application login.
Creating single sign-ons for HTTP requests using the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) web authentication for WebSphere Application Server requires the performance of several distinct, yet related functions that when completed, allow HTTP users to log in and authenticate to the Microsoft® domain controller only once at their desktop and to receive automatic authentication from the WebSphere Application Server.
You must perform steps in this article in order to set up Kerberos as the authentication mechanism for WebSphere Application Server.
Various enterprise information systems (EIS) use different methods for storing data. These backend data stores might be relational databases, procedural transaction programs, or object-oriented databases.
Use this task when you are implementing the optimized local adapters support for calling inbound to WebSphere Application Server for z/OS® Enterprise JavaBeans (EJB) applications.
Use this task when you are implementing the optimized local adapters support for calling programs in external address spaces from WebSphere Application Server for z/OS applications.
When starting from existing JavaBeans or enterprise beans, you can use a bottom-up approach to developing Web services based on the Java API for XML-Based Web Services (JAX-WS) programming model.
When starting with an existing Web Services Description Language (WSDL) file, you can use a top-down approach to developing web services based on the Java API for XML-Based Web Services (JAX-WS) programming model.
You can develop static web services clients based on the Web Services for Java Platform, Enterprise Edition (Java EE) specification and the Java API for XML-Based Web Services (JAX-WS) programming model.
You can develop dynamic web services clients based on the Web Services for Java Platform, Enterprise Edition (Java EE) specification and the Java API for XML-Based Web Services (JAX-WS) programming model.
You can use Java API for RESTful Web Services (JAX-RS) to develop services that follow Representational State Transfer (REST) principles. Using JAX-RS, development of RESTful services is simplified.
XML is a common media format that RESTful services consume and produce. To deserialize and serialize XML, you can represent requests and responses by Java Architecture for XML Binding (JAXB) annotated objects.
JavaScript Object Notation (JSON) is a common media format that RESTful services consume and produce. You can use this lightweight data-interchange format that is based on the object-literal notation of JavaScript to exchange data.
A frequently used content type for submitting files through an HTML form is multipart/form-data. The IBM Java API for RESTful Web Services (JAX-RS) implementation greatly simplifies the processing of such data by automatically splitting the parts and automatically decoding them. If such automatic processing is not desired, the resource may instead receive the parts in an object so processing of the parts is under the complete control of the resource method.
You can use the Atom Syndication Format (Atom) to format web feeds, which communicate news and updates of episodic information about websites. Using Atom content in JAX-RS applications, you can take advantage of web content syndication that provides the same decentralized, dynamic mechanisms for adding new metadata and content supported by RSS, but does so in a way that helps protect core interoperability between implementations.
Even though the Java API for RESTful Web Services (JAX-RS) runtime environment includes several entity providers for handling serialization from and deserialization to Java types, it does not support all possible media types. You can develop a custom entity provider to handle binding Java types to message bodies.
One of the advantages of RESTful applications is the ability to return different representations of resources. With Representational State Transfer (REST), clients and servers can exchange resources of the same media type or use differing media types. Content negotiation enables clients and servers to agree on the content format that is used to exchange data.
Java API for RESTful Web Services (JAX-RS) provides different types of context to resource classes and providers. You can use context objects to access request information such as discovering the HTTP headers that are sent as part of the request. Context objects also provide convenience methods for evaluating a request and building an appropriate response.
If you have enterprise JavaBeans (EJB) applications, you can expose a RESTful interface to the enterprise bean using Java API for RESTful Web Services (JAX-RS). By implementing JAX-RS annotated enterprise beans, you keep the EJB functionality including transaction support, injection of Java EE components and resources, and other EJB session bean capabilities.
Java API for RESTful Web Services (JAX-RS) root resources and providers can be used in a Java Contexts and Dependency Injection (JCDI) enabled web archive (WAR). Simply add a valid WEB-INF/beans.xml file to your WAR file and any JAX-RS root resources and providers that are valid JCDI beans can use JCDI functionality.
You can implement handlers on the server-side of a Java API for RESTful Web Services (JAX-RS) application to enhance request and response processing.
Using multipart messages, servers and clients can transmit multiple messages using a single message. Multipart messages are useful when both the client and server need to send multiple requests but want to save the cost of sending and receiving entire HTTP request and responses for each part.
A frequently used content type for submitting files through an HTML form is multipart/form-data. The IBM Java API for RESTful Web Services (JAX-RS) implementation greatly simplifies the processing of such data by automatically splitting the parts and automatically decoding them. If such automatic processing is not desired, the resource may instead receive the parts in an object so processing of the parts is under the complete control of the resource method.
The IBM Java API for RESTful Web Services (JAX-RS) runtime environment is driven a servlet derived from the Apache Wink project. Within the WebSphere Application Server environment, the lifecycle of servlets is managed in the web container. Therefore, the security services offered by the web container are applicable to REST resources that are deployed in WebSphere Application Server.
Web Application Description Language (WADL) is a description language for HTTP-based applications. It is currently a World Wide Web Consortium (W3C) Member Submission. WADL can be used by programs to give information about the service in a machine-processable method. For instance, you can use an Extensible Stylesheet Transformation (XSLT) document to transform the WADL documentation by using a custom XSLT and a XSLT processor.
You can use the Apache Wink REST client as a client that can be run to send requests to your JAX-RS application.
Instead of using the Apache Wink REST client inside a server application, you can use the Thin Client for JAX-RS that is provided with WebSphere Application Server as a stand-alone thin client to send requests to your RESTful service. The Thin Client for JAX-RS is a stand-alone Java SE 6 client environment that enables running unmanaged JAX-RS RESTful web services client applications in a non-WebSphere environment to invoke JAX-RS RESTful web services that are hosted by the application server.