We have created a new industry leading exam! The Sun Certified Developer for Java
(TM) Web Services certification exam. The certification exam number for the beta: 311-220.
The FREE beta starts on April 29 � May 23, 2004 and worldwide registration begins on April 28, 2004. You can start to send an email to sunbeta@Prometric.com
as of Monday, April 12, but you WILL NOT be able to register to take the exam - with your electronic voucher - until April 28. You CANNOT register for the beta online.
To get a free voucher:
Send an email to: SunBeta@Prometric.com
Subject Line: SCDJWS Voucher
Include in your email...
Web Services Experience:
Prometric id number:
Confirm you have passed the Sun Certified Programmer (prerequisite)
PLEASE ALLOW 5-7 BUSINESS DAYS FOR A RESPONSE, DO NOT SEND DUPLICATE EMAILS.
This exam does have a prerequisite, Sun Certified Programmer (any version), you MUST have passed this certification to take the beta. If you take the beta and do not have the prerequisite you will NOT receive your certification package and will NOT receive a score until you have passed the prerequisite.
I will send you the scheduled time (hours) for the exam and how many questions next week.
If you pass the beta exam, you will receive your full certification package (including a lapel pin, ID card, business card logo and the certificate itself) from Sun upon the formal release of the certification in the SUMMER of 2004. The cost of a certification voucher is normally $150.
Please DO NOT send emails asking about the status of your score.
I promise when I find out when score reports will be sent out I will let you know on this forum.
If you have any problems or have any questions please send me a direct email at email@example.com
and I will be more than happy to help you.
Java Certification Program Manager
OBJECTIVES: (For Studying)
Section 1: XML Web Service Standards
1.1Given XML documents, schemas, and fragments determine whether their syntax and form are correct (according to W3C schema) and whether they conform to the WS-I Basic Profile 1.0a.
1.2Describe the use of XML schema in J2EE
1.3Describe the use of namespaces in an XML document.
Section 2: SOAP
1.1 Web Service Standards
2.1List and describe the encoding types used in a SOAP message.
2.2Describe how SOAP message header blocks are used and processed.
2.3Describe the function of each element contained in a SOAP message, the SOAP binding to HTTP, and how to represent faults that occur when processing a SOAP message.
2.4Create a SOAP message that contains an attachment.
2.5Describe the restrictions placed on the use of SOAP by the WS-I Basic Profile 1.0a.
2.6Describe the function of SOAP in a Web service interaction and the advantages and disadvantages of using SOAP messages.
Section 3: Describing and Publishing (WSDL and UDDI)
3.1Explain the use of WSDL in Web services, including a description of WSDL's basic elements, binding mechanisms and the basic WSDL operation types as limited by the WS-I Basic Profile 1.0a.
3.2Describe how W3C XML Schema is used as a typing mechanism in WSDL 1.1.
3.3Describe the use of UDDI data structures. Consider the requirements imposed on UDDI by the WS-I Basic Profile 1.0a.
3.4Describe the basic functions provided by the UDDI Publish and Inquiry APIs to interact with a UDDI business registry.
Section 4: JAX-RPC
4.1Explain the service description model, client connection types, interaction modes, transport mechanisms/protocols, and endpoint types as they relate to JAX-RPC.
4.2Given a set of requirements for a Web service, such as transactional needs, and security requirements, design and develop Web service applications that use servlet-based endpoints and EJB based endpoints.
4.3Given an set of requirements, design and develop a Web sevice client, such as a J2EE client and a stand-alone Java client, using the appropriate JAX-RPC client connection style.
4.4Given a set of requirements, develop and configure a Web service client that accesses a stateful Web service.
4.5Explain the advantages and disadvantages of a WSDL to Java vs. a Java to WSDL development approach.
4.6Describe the advantages and disadvantages of web service applications that use either synchronous/request response, one-way RPC, or non-blocking RPC invocation modes.
4.7Use the JAX-RPC Handler API to create a SOAP message handler, describe the function of a handler chain, and describe the role of SAAJ when creating a message handler.
Section 5: SOAP and XML Processing APIs (JAXP, JAXB, and SAAJ)
5.1Describe the functions and capabilities of the APIs included within JAXP.
5.2Given a scenario, select the proper mechanism for parsing and processing the information in an XML document.
5.3Describe the functions and capabilities of JAXB, including the JAXB process flow, such as XML-to-Java and Java-to-XML, and the binding and validation mechanisms provided by JAXB.
5.4Use the SAAJ APIs to create and manipulate a SOAP message.
Section 6: JAXR
6.1Describe the function of JAXR in Web service architectural model, the two basic levels of business registry functionality supported by JAXR, and the function of the basic JAXR business objects and how they map to the UDDI data structures.
6.2Use JAXR to connect to a UDDI business registry, execute queries to locate services that meet specific requirements, and publish or update information about a business service.
Section 7: J2EE Web Services
7.1Identify the characteristics of and the services and APIs included in the J2EE platform.
7.2Explain the benefits of using the J2EE platform for creating and deploying Web service applications.
7.3Describe the functions and capabilities of the JAXP, DOM, SAX, JAXR, JAX-RPC, and SAAJ in the J2EE platform.
7.4Describe the role of the WS-I Basic Profile when designing J2EE Web services.
Section 8: Security
8.1Explain 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.2Identify 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.3Given a scenario, implement J2EE based web service web-tier and/or EJB-tier basic security mechanisms, such as mutual authentication, SSL, and access control.
8.4Describe 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.
Section 9: Developing Web Services
9.1Describe the steps required to configure, package, and deploy J2EE Web services and service clients, including a description of the packaging formats, such as .ear, .war, .jar, deployment descriptor settings, the associated Web services description file, RPC mapping files, and service reference elements used for EJB and servlet
9.2Given a set of requirements, develop code to process XML files using the SAX, DOM, XSLT, and JAXB APIs.
9.3Given an XML schema for a document style Web service create a WSDL file that describes the service and generate a service implementation.
9.4Given a set of requirements, develop code to create an XML-based, document style, Web service using the JAX-RPC APIs.
9.5Implement a SOAP logging mechanism for testing and debugging a Web service application using J2EE Web Service APIs.
9.6Given a set of requirements, develop code to handle system and service exceptions and faults received by a Web services client.
Section 10: General Design and Architecture
10.1Describe the characteristics of a service oriented architecture and how Web services fits to this model.
10.2Given a scenario, design a J2EE service using the business delegate, service locator, and/or proxy client-side design patterns
and the adapter, command, Web service broker, and/or fa�ade server-side patterns.
10.3Describe alternatives for dealing with issues that impact the quality of service provided by a Web service and methods to improve the system reliability, maintainability, security, and performance of a service.
10.4Describe how to handle the various types of return values, faults, errors, and exceptions that can occur during a Web service interaction.
10.5Describe the role that Web services play when integrating data, application functions, or business processes in a J2EE application.
10.6Describe how to design a stateless Web service that exposes the functionality of a stateful business process.
Section 11: Endpoint Design and Architecture
11.1Given a scenario, design Web service applications using information models that are either procedure-style or document-style.
11.2Describe the function of the service interaction and processing layers in a Web service.
11.3Describe the tasks performed by each phase of an XML-based, document oriented, Web service application, including the consumption, business processing, and production phases.
11.4Design a Web service for an asynchronous, document-style process and describe how to refactor a Web service from a synchronous to an asynchronous model.
11.5Describe 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.
These objectives are a DRAFT, most likely very minor changes.