Definition of Terms

1. DOM - Document Object Model.
   
2. EJB - Enterprise JavaBean
   
3. JAX-WS - Java API for XML Web Services
   
4. JAXB - Java Architecture for XML Binding
   
5. JAXP - Java API for XML Processing
   
6. JAXR - Java API for XML Registries
   
7. JMS - Java Message Service
   
8. JSON - JavaScript Object Notation
   
9. REST - Representational State Transfer
   
10. SAAJ - SOAP with Attachments API for Java
    
11. SAML - Security Assertion Markup Language
    
12. SAX - Simple API for XML
    
13. SOAP - Simple Object Access Protocol
    
14. StAX - Streaming API for XML
    
15. UDDI - Universal Description Discovery and Integration. UDDI is a directory service where businesses can register and search for Web services. It is a platform-independent framework for describing services, discovering businesses, and integrating business services by using the Internet.
    
16. WCF - Windows Communication Foundation
    
17. WS-I - Web Services Interoperability
    
18. WSDL - Web Services Description Language. WSDL is an XML-based language for describing Web services and how to access them.
    
19. WSIT- Web Services Interoperability Technology
    
20. XACML - eXtensible Access Control Markup Language
    
21. XKMS - XML Key Management Specification
    
22. XML - Extensible Markup Language
    
23. XSLT - Extensible Stylesheet Language Transformations
    

Section 12: Endpoint Design and Architecture

12.1 Given a scenario, design Web Service applications using information models that are either procedure-style or document-style.

12.2 Describe the function of the service interaction and processing layers in a Web service.

12.3 Design a Web service for an asynchronous, document-style process and describe how to refactor a Web Service from a synchronous to an asynchronous model.

12.4 Describe how the characteristics, such as resource utilization, conversational capabilities, and operational modes, of the various types of Web service clients impact the design of a Web service or determine the type of client that might interact with a particular service.

Section 11: General Design and Architecture

11.1 Describe the characteristics of a Service Oriented Architecture (SOA) and how Web services fit to this model.

11.2 Given a scenario, design a Java EE web service using Web Services Design Patterns (Asynchronous Interaction, JMS Bridge, Web Service Cache, Web Service Broker), and Best Practices.

11.3 Describe how to handle the various types of return values, faults, errors, and exceptions that can occur during a Web service interaction.

11.4 Describe the role that Web services play when integrating data, application functions, or business processes in a Java EE application.

Section 10: Web Services Interoperability Technologies

10.1 Describe WSIT, the features of each WSIT technology and the standards that WSIT Implements for each technology and how it works.

10.2. Describe how to create a WSIT client from a Web Service Description Language (WSDL) file.

10.3 Describe how to configure web service providers and clients to use message optimization.

10.4 Create a Microsoft Windows Communication Foundation (WCF) client that accesses a Java web service.

10.5 Describes the best practices for production and consumption of data interoperability between WCF web services and Java web service clients or between Java web services and WCF web service clients.

Section 9: Developing Web Services

9.1 Describe the steps required to configure, package, and deploy Java EE Web services and service clients, including a description of the packaging formats, such as .ear, .war, .jar, annotations and deployment descriptor settings.

9.2 Given a set of requirements, develop code to process XML files using the SAX, StAX, DOM, XSLT, and JAXB APIs.

9.3 Given an XML schema for a document style Web service create a WSDL file that describes the service and generate a service implementation.

9.4 Given a set of requirements, create code to create an XML-based, document style, Web service using the JAX-WS APIs.

9.5 Implement a SOAP logging mechanism for testing and debugging a Web service application using Java EE Web Service APIs.

9.6 Given a set of requirements, create code to handle system and service exceptions and faults received by a Web services client.

Section 8: Security

8.1 Explain basic security mechanisms including: transport level security, such as basic and mutual authentication and SSL, message level security, XML encryption, XML Digital Signature, and federated identity and trust.

8.2 Identify the purpose and benefits of Web services security oriented initiatives and standards such as Username Token Profile, SAML, XACML, XKMS, WS-Security, and the Liberty Project.

8.3 Given a scenario, implement Java EE based web service web-tier and/or EJB-tier basic security mechanisms, such as mutual authentication, SSL, and access control.

8.4 Describe factors that impact the security requirements of a Web service, such as the relationship between the client and service provider, the type of data being exchanged, the message format, and the transport mechanism.

8.5 Describe WS-Policy that defines a base set of constructs that can be used and extended by other Web specifications to describe a broad range of service requirements and capabilities.

Tutorial:

• http://www.netbeans.org/kb/60/websvc/wsit.html
  

Section 7: Java EE Web Services

7.1 Identify the characteristics of and the services and APIs included in the Java EE platform.

7.2 Explain the benefits of using the Java EE platform for creating and deploying Web service applications.

7.3 Describe the functions and capabilities of the JAXP, DOM, SAX, StAX, JAXR, JAXB, JAX-WS and SAAJ in the Java EE platform.

7.4 Describe the role of the WS-I Basic Profile when designing Java EE Web services.