IBM WAS ND v8.0

 

+

Search Tips  |  Advanced Search

1. Task overview: Globalizing applications
   • Globalization
   • Work with locales and character encodings
   • Task overview: Internationalizing application components (internationalization service)
     • Internationalization service
     • Assembling internationalized applications
     • Set the internationalization type for servlets
     • Configure container internationalization for servlets
     • Set the internationalization type for enterprise beans
     • Configure container internationalization for enterprise beans
     • Use the internationalization context API
     • Gaining access to the internationalization context API
     • Access caller locales and time zones
     • Access invocation locales and time zones
     • Internationalization context
     • Internationalization context: Propagation and scope
     • Internationalization context: Management policies
     • Internationalization type
     • Container internationalization attributes
     • Administer the internationalization service
     • Enable the internationalization service for servlets and enterprise beans
     • Enable the internationalization service for EJB clients

   • Task overview: Internationalizing interface strings (localizable-text API)
     • Identify localizable text
     • Create message catalogs
     • Composing language-specific strings
     • Create a formatter instance
     • Set optional localization values
     • Composing complex strings
     • Nesting formatter instances for localized substrings
     • Generate localized text
     • Customize the behavior of a formatting method
     • Prepare the localizable-text package for deployment
     • Mail, URLs, and other J2EE resources
     • Enable J2EE applications to use mail resources with JavaMail
     • Use URL resources within an application
     • Messaging resources
     • Choosing a messaging provider
     • Choosing messaging providers for a mixed environment
     • Naming and directory
     • Use naming
     • ORB
     • Enable HTTP tunneling
     • Manage ORBs
     • ORBs
     • Tune ORBs
     • Administer ORBs
     • Develop ORBs
     • WAS default directories
     • Troubleshoot ORBs
     • Enable HTTP tunneling
     • OSGi applications
     • Develop and deploying an OSGi application
     • Create a service bundle
     • Create a client bundle
     • Create an OSGi application
     • Create an OSGi application using Apache Ant
     • Deploy an OSGi application as a business-level application
     • Add an EBA asset to a composition unit
     • Add an EBA asset to a composition unit using wsadmin
     • Add an EBA asset that includes composite bundles using the addCompUnit command
     • Debug bundles at run time using the command-line console
     • Update bundle versions in a deployed OSGi application
     • Check the bundle download status of an EBA asset
     • Update bundle versions for an EBA asset
     • Update bundle versions for an EBA asset using the editAsset command
     • Check the update status of an OSGi composition unit
     • Update an OSGi composition unit
     • Update an OSGi composition unit using the editCompUnit command
     • Extend a deployed OSGi application
     • Develop a composite bundle
     • Add or removing extensions for an OSGi composition unit
     • Add or removing extensions for an OSGi composition unit using wsadmin
     • listOSGiExtensions command
     • listAvailableOSGiExtensions command
     • addOSGiExtension command
     • addOSGiExtensions command
     • removeOSGiExtension command
     • removeOSGiExtensions command
     • Check the update status of an OSGi composition unit
     • Update an OSGi composition unit
     • Update an OSGi composition unit using the editCompUnit command
     • Convert existing applications to OSGi applications
     • Convert an enterprise application to an OSGi application
     • Convert a Spring application to an OSGi application

   • Portlet applications
     • Task overview: Managing portlets
     • SCA composites
     • Use existing Java EE modules and components as SCA implementations
     • Use non-SCA enhanced Java EE applications as SCA component implementations
     • Use SCA enhanced Java EE applications as SCA component implementations
     • Use SCA annotations with web modules
     • Use SCA annotations with session beans
     • Use SCA annotations with message-driven beans
     • Rewiring EJB references to SCA references
     • Use Spring 2.5.5 containers in SCA applications
     • WAS default directories
     • Schedulers
     • Use schedulers
     • Security
     • Configure LTPA and working with keys
     • 1. Configure LTPA and generate the first LTPA keys.
     • Configure the LTPA authentication mechanism
     • Start and logging off the administrative console
     • 2. Generate keys manually or automatically, and control the number of active keys.
     • Generate LTPA keys
     • Disable automatic generation of LTPA keys
     • Work with nodes - groups of managed servers
     • Managed and unmanaged nodes
     • Node groups
     • Manage nodes
     • Recover or move nodes with addNode -asExistingNode
     • Change the node host names
     • Start and stop a node
     • WAS default directories
     • Configure node groups
     • Add node group members
     • Manage node agents
     • Configure remote file services
     • Start an application server
     • WAS default directories
     • Activating LTPA key versions
     • 3. Import and export keys.
     • Disable automatic generation of LTPA keys
     • Export LTPA keys
     • Import LTPA keys
     • Manage node agents
     • Start an application server
     • WAS default directories
     • 4. Manage keys from multiple cells.
     • Manage LTPA keys from multiple WAS cells
     • Start an application server
     • WAS default directories
     • Customize application login with JAAS
     • 1. Develop programmatic logins with JAAS.
     • Develop programmatic logins with the JAAS
     • Programmatic login for JAAS
     • 2. Configure programmatic logins with JAAS.
     • Configure programmatic logins for JAAS
     • Manage Java 2 Connector Architecture authentication data entries for JAAS
     • 3. Customize an application login to perform an identity assertion using JAAS.
     • Customize an application login to perform an identity assertion using JAAS
     • 4. Configure a server-side JAAS authentication and login configuration.
     • Customize a server-side JAAS authentication and login configuration
     • Get the caller subject from the thread for JAAS
     • Get the RunAs subject from the thread for JAAS
     • Ovveride the RunAs subject on the thread for JAAS
     • Revoking users from a cache for JAAS
     • Enable identity assertion with trust validation using JAAS
     • Create a single sign-on for HTTP requests using SPNEGO Web authentication
     • 1. Create a Kerberos service principal (SPN) and keytab file on your Microsoft domain controller machine
     • Create a Kerberos service principal (SPN) and keytab file on your Microsoft domain controller machine
     • 2. Create a Kerberos configuration file
     • Create a Kerberos configuration file
     • 3. Configure and enable SPNEGO web authentication on your WAS machine
     • Enable and configuring SPNEGO web authentication
     • Set SPNEGO web authentication filters
     • 4. Configure the client application on the client application machine
     • Configure the client browser to use SPNEGO
     • 5. Create SPNEGO tokens for J2EE, .NET, Java, web service clients for HTTP requests (optional)
     • Create SPNEGO tokens for J2EE, .NET, Java, web service clients for HTTP requests
     • Set up Kerberos as the authentication mechanism for WAS
     • 1. Create a Kerberos service principal name and keytab file
     • Create a Kerberos service principal name and keytab file
     • 2. Create a Kerberos configuration file
     • Create a Kerberos configuration file
     • 3. Configure Kerberos as the authentication mechanism for WebSphere Application Sever
     • Configure Kerberos as the authentication mechanism
     • 4. Map a client Kerberos principal name to the WebSphere user registry ID
     • Map of a client Kerberos principal name to the WebSphere user registry ID
     • 5. Set up Kerberos as the authentication mechanism for the pure Java client (optional)
     • Configure a Java client for Kerberos authentication
     • SIP applications
     • Use SIP

   • Web applications
     • Task overview: Developing and deploying web applications
     • Task overview: Managing HTTP sessions
     • Web services
     • Task overview: Implementing web services applications
     • Create a monitor for WAS for WSDM resources (deprecated)
     • Implement web services applications with JAX-WS
     • 1. Set up a development environment for web services.
     • Set up a development environment for web services
     • 2. Determine the existing JavaBeans or enterprise beans to expose as a JAX-WS web service.
     • 3. Develop JAX-WS web services with annotations.
     • Develop JAX-WS web services with annotations
     • WAS default directories
     • 4. Generate Java artifacts for JAX-WS applications.
     • Generate Java artifacts for JAX-WS applications
     • WAS default directories
     • 5. (optional) Enable MTOM for JAX-WS web services.
     • Enable MTOM for JAX-WS web services
     • WAS default directories
     • 6. (optional) Enforce adherence to WSDL bindings in JAX-WS web services.
     • Enforcing adherence to WSDL bindings in JAX-WS web services
     • 7. (optional) Develop and configure a webservices.xml deployment descriptor for JAX-WS applications.
     • Develop a webservices.xml deployment descriptor for JAX-WS applications
     • WAS default directories
     • 8. Complete the implementation of your web services application.
     • Complete the JavaBeans implementation for JAX-WS applications
     • Complete the EJB implementation for JAX-WS applications
     • 9. (Optional) Customize URL patterns in the web.xml file.
     • Customize URL patterns in the web.xml file for JAX-WS applications
     • 10. Assemble the artifacts for your web service.
     • Assembling web services applications
     • Assembling a JAR file that is enabled for web services from an enterprise bean
     • Assembling a web services-enabled enterprise bean JAR file from a WSDL file
     • Assembling a WAR file that is enabled for web services from Java code
     • Assembling a web services-enabled WAR file from a WSDL file
     • Assembling an enterprise bean JAR file into an EAR file
     • Assembling a web services-enabled WAR into an EAR file
     • Enable an EAR file for EJB modules that contain web services
     • Enable an EAR file for web services with the endptEnabler command
     • 11. Deploy the EAR file into the application server.
     • Deploy web services applications onto application servers
     • JAX-WS application deployment model
     • Use a third-party JAX-WS web services engine
     • 12. Test the web service to make sure that the service works with the application server.
     • Test web services-enabled clients
     • Implement web services applications from existing WSDL files with JAX-WS
     • 1. Set up a development environment for web services.
     • Set up a development environment for web services
     • 2. Develop Java artifacts for JAX-WS applications using the wsimport command-line tool.
     • Generate Java artifacts for JAX-WS applications from a WSDL file
     • 3. (optional) Enable MTOM for JAX-WS web services.
     • Enable MTOM for JAX-WS web services
     • WAS default directories
     • 4. (optional) Enforce adherence to WSDL bindings in JAX-WS web services.
     • Enforcing adherence to WSDL bindings in JAX-WS web services
     • 5. (optional) Develop and configure a webservices.xml deployment descriptor for JAX-WS applications.
     • Develop a webservices.xml deployment descriptor for JAX-WS applications
     • WAS default directories
     • 6. Complete the implementation of your web service application.
     • Complete the JavaBeans implementation for JAX-WS applications
     • Complete the EJB implementation for JAX-WS applications
     • 7. (Optional) Customize URL patterns in the web.xml file.
     • Customize URL patterns in the web.xml file for JAX-WS applications
     • 8. Assemble the artifacts for your web service.
     • Assembling web services applications
     • Assembling a JAR file that is enabled for web services from an enterprise bean
     • Assembling a web services-enabled enterprise bean JAR file from a WSDL file
     • Assembling a WAR file that is enabled for web services from Java code
     • Assembling a web services-enabled WAR file from a WSDL file
     • Assembling an enterprise bean JAR file into an EAR file
     • Assembling a web services-enabled WAR into an EAR file
     • Enable an EAR file for EJB modules that contain web services
     • Enable an EAR file for web services with the endptEnabler command
     • 9. Deploy the EAR file into the application server.
     • Deploy web services applications onto application servers
     • JAX-WS application deployment model
     • Use a third-party JAX-WS web services engine
     • 10. Test the web service to make sure that the service works with the application server.
     • Test web services-enabled clients
     • Customize URL patterns in the web.xml file for JAX-WS applications
     • Use handlers in JAX-WS web services
     • Implement static JAX-WS web services clients
     • 1. Obtain the WSDL document for the web service to access.
     • 2. Develop JAX-WS client artifacts from a WSDL file.
     • Develop a JAX-WS client from a WSDL file
     • Develop deployment descriptors for a JAX-WS client
     • 3. Complete the client implementation.
     • 4. (Optional) Assemble a web services-enabled client JAR file into an EAR file.
     • Assembling a web services-enabled client JAR file into an EAR file
     • 5. (Optional) Assemble a web services-enabled client WAR file into an EAR file.
     • Assembling a web services-enabled client WAR file into an EAR file
     • 6. (Optional) Deploy the web services client application.
     • Deploy web services client applications
     • 7. Test the web services-enabled client application.
     • Test web services-enabled clients
     • Implement dynamic JAX-WS web services clients
     • 1. Develop a dynamic web services client.
     • Develop a dynamic client using JAX-WS APIs
     • 2. (Optional) Assemble a web services-enabled client JAR file into an EAR file.
     • Assembling a web services-enabled client JAR file into an EAR file
     • 3. (Optional) Assemble a web services-enabled client WAR file into an EAR file.
     • Assembling a web services-enabled client WAR file into an EAR file
     • 4. (Optional) Deploy the web services client application.
     • Deploy web services client applications
     • 5. Test the web services-enabled client application.
     • Test web services-enabled clients
     • Configure a web services client to access resources using a web proxy
     • Implement web services applications with JAX-RPC
     • Develop JAX-RPC web services
     • Set up a development environment for web services
     • Develop a service endpoint interface from JavaBeans for JAX-RPC applications
     • Develop a service endpoint interface from enterprise beans for JAX-RPC applications
     • Develop a WSDL file for JAX-RPC applications
     • Develop JAX-RPC web services deployment descriptor templates for a JavaBeans implementation
     • Develop JAX-RPC web services deployment descriptor templates for an enterprise bean implementation
     • Complete the JavaBeans implementation for JAX-RPC applications
     • Complete the EJB implementation for JAX-RPC applications
     • Configure the webservices.xml deployment descriptor for JAX-RPC web services
     • Configure the webservices.xml deployment descriptor for handler classes
     • Configure the ibm-webservices-bnd.xmi deployment descriptor for JAX-RPC web services
     • Assembling web services applications
     • Assembling a JAR file that is enabled for web services from an enterprise bean
     • Assembling a web services-enabled enterprise bean JAR file from a WSDL file
     • Assembling a WAR file that is enabled for web services from Java code
     • Assembling a web services-enabled WAR file from a WSDL file
     • Assembling an enterprise bean JAR file into an EAR file
     • Assembling a web services-enabled WAR into an EAR file
     • Enable an EAR file for EJB modules that contain web services
     • Enable an EAR file for web services with the endptEnabler command
     • Deploy web services applications onto application servers
     • JAX-WS application deployment model
     • Use a third-party JAX-WS web services engine
     • Implement web services applications from existing WSDL files with JAX-RPC
     • Develop JAX-RPC web services with WSDL files (top down)
     • Set up a development environment for web services
     • Develop Java artifacts for JAX-RPC applications from a WSDL file
     • Develop EJB implementation templates and bindings from a WSDL file for JAX-RPC web services
     • Complete the JavaBeans implementation for JAX-RPC applications
     • Complete the EJB implementation for JAX-RPC applications
     • Configure the webservices.xml deployment descriptor for JAX-RPC web services
     • Configure the webservices.xml deployment descriptor for handler classes
     • Configure the ibm-webservices-bnd.xmi deployment descriptor for JAX-RPC web services
     • Assembling web services applications
     • Assembling a JAR file that is enabled for web services from an enterprise bean
     • Assembling a web services-enabled enterprise bean JAR file from a WSDL file
     • Assembling a WAR file that is enabled for web services from Java code
     • Assembling a web services-enabled WAR file from a WSDL file
     • Assembling an enterprise bean JAR file into an EAR file
     • Assembling a web services-enabled WAR into an EAR file
     • Enable an EAR file for EJB modules that contain web services
     • Enable an EAR file for web services with the endptEnabler command
     • Deploy web services applications onto application servers
     • JAX-WS application deployment model
     • Use a third-party JAX-WS web services engine
     • Use WSDL EJB bindings to invoke an EJB from a JAX-RPC Web services client
     • Implement JAX-RPC web services clients
     • Develop JAX-RPC web services clients
     • Develop client bindings from a WSDL file for a JAX-RPC Web services client
     • Change SOAP message encoding to support WSI-Basic Profile
     • Configure the JAX-RPC web services client deployment descriptor with an assembly tool
     • Configure the JAX-RPC client deployment descriptor for handler classes
     • Configure the JAX-RPC web services client bindings in the ibm-webservicesclient-bnd.xmi deployment descriptor
     • Implement extensions to JAX-RPC web services clients
     • Custom data binders for JAX-RPC applications
     • Custom binding providers for JAX-RPC applications
     • Send implicit SOAP headers with JAX-RPC
     • Receive implicit SOAP headers with JAX-RPC
     • Send transport headers with JAX-RPC
     • Retrive transport headers with JAX-RPC
     • Web services - RESTful services
     • Implement JAX-RS web applications
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 5. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use XML content in JAX-RS application requests and responses
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement a resource method using JAXB objects for XML content.
     • Implement a resource method using JAXB objects for XML content
     • Use JAXB for XML data binding
     • Use schemagen to generate an XML schema file from a Java class
     • Use JAXB xjc tooling to generate JAXB classes from an XML schema file
     • Use the JAXB runtime to marshal and unmarshal XML documents
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use JSON content in JAX-RS application requests and responses
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement a resource method using JSON content for a request and response entity.
     • Use Jackson with plain old Java objects (POJOs)
     • Implement a JSON representation of a resource with Jackson and JAXB annotated objects
     • Implement a resource method using IBM JSON4J
     • WAS default directories
     • Implement a JSON resource method using JAXB annotated objects with IBM JSON4J
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use Atom content in JAX-RS application requests and responses
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement JAXB-based ATOM content for requests and responses
     • Use the JAXB-based Atom model for requests and responses
     • WAS default directories
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use custom entity formats
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement custom entity formats.
     • Implement custom entity formats
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use content negotiation to serve multiple content types in JAX-RS applications
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement content negotiation to serve multiple content types.
     • Implement content negotiation based on URL patterns
     • Implement content negotiation based on request parameters
     • Implement content negotiation based on HTTP headers
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use JAX-RS context objects to obtain more information about requests
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Add context fields and parameters to obtain information about requests.
     • Obtaining HTTP headers using HttpHeaders objects
     • Obtaining information about URIs using UriInfo objects
     • Evaluate request preconditions using Request objects
     • Determine security information using SecurityContext objects
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Implement RESTful views of EJB applications using JAX-RS
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement RESTful views of enterprise beans.
     • Implement RESTful views of a no-interface EJB
     • Implement RESTful views of an EJB with local interfaces
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use Java contexts and dependency injection with JAX-RS
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implementing JAX-RS resources with JCDI functionality.
     • Implement JAX-RS resources with dependency injection
     • Implement JAX-RS resources with different lifecycle scopes
     • Implement a JAX-RS resource with decorators and method interceptors
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Use handlers to enhance request and response processing
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement user handlers for your JAX-RS application.
     • Implement user handlers for JAX-RS applications
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use multipart content in JAX-RS application requests and responses
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement a resource using multipart messages
     • Implement resources using multipart messages
     • WAS default directories
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use multipart/form-data content in JAX-RS application requests and responses
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Implement a resource method to receive multipart/form-data parts from an HTML form submission.
     • Configure a resource to receive multipart/form-data parts from an HTML form submission
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Implement secure JAX-RS applications
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Secure JAX-RS applications within the web container.
     • Secure JAX-RS applications within the web container
     • WAS default directories
     • 5. Secure JAX-RS resources using annotations.
     • Secure JAX-RS resources using annotations
     • 6. (optional) Secure downstream JAX-RS resources.
     • Secure downstream JAX-RS resources
     • 7. (optional) Secure JAX-RS clients using SSL.
     • Secure JAX-RS clients using SSL
     • 8. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 9. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • 10. Administer the secure JAX-RS application.
     • Administer secure JAX-RS applications
     • Use WADL to generate service documentation
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Define the resources in JAX-RS web applications.
     • Define the resources in RESTful applications
     • Define the URI patterns for resources in RESTful applications
     • Define resource methods for RESTful applications
     • Define the HTTP headers and response codes for RESTful applications
     • Define media types for resources in RESTful applications
     • Define parameters for request representations to resources in RESTful applications
     • Define exception mappers for resource exceptions and errors
     • 3. Configure the JAX-RS application.
     • Configure JAX-RS web applications
     • Configure JAX-RS applications using JAX-RS 1.1 methods
     • Configure the web.xml file for JAX-RS servlets
     • Configure the web.xml file for JAX-RS filters
     • 4. Use WADL to generate service documentation.
     • Serving a WADL document for your resources
     • Disable generation of WADL documents for HTTP OPTIONS requests
     • 5. Assemble JAX-RS web applications.
     • Assembling JAX-RS web applications
     • Assembly tools
     • 6. Deploy JAX-RS web applications.
     • Deploy JAX-RS web applications
     • Use the Apache Wink REST client inside server applications to issue requests
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Implement a client using the Apache Wink Rest client.
     • Implement clients using the Apache Wink REST client
     • Use the Apache Wink REST client as a stand-alone thin client
     • 1. Configure the development environment.
     • Set up a development environment for JAX-RS applications
     • Assembly tools
     • WAS default directories
     • 2. Implement a client using the unmanaged RESTful web services JAX-RS client.
     • Implement a client using the unmanaged RESTful web services JAX-RS client
     • Web services - Security (WS-Security)
     • Secure web services applications at the transport level
     • 1. Develop and assemble a web services application.
     • Configure HTTP outbound transport level security with an assembly tool
     • 2. Deploy the application.
     • 3. Configure transport level security for the application.
     • Configure HTTP outbound transport level security with the administrative console
     • Configure HTTP outbound transport level security using Java properties
     • 4. Define additional HTTP transport properties for the Web services application.
     • Authenticate web services clients using HTTP basic authentication
     • 1. Develop and assemble a web services application.
     • Configure HTTP basic authentication for JAX-RPC web services programmatically
     • Configure HTTP basic authentication for JAX-RPC web services with an assembly tool
     • 2. Deploy the application.
     • 3. Configure HTTP authentication for the application.
     • Configure HTTP basic authentication for JAX-RPC web services with the administrative console
     • Secure JAX-WS web services using message-level security
     • 1. Learn about Web Services Security.
     • Web Services Security concepts
     • What is new for securing web services
     • Web Services Security enhancements
     • Supported functionality from OASIS specifications
     • Web Services Security specification - a chronology
     • Web Services Security provides message integrity, confidentiality, and authentication
     • High-level architecture for Web Services Security
     • Security model mixture
     • Overview of platform configuration and bindings
     • Keys
     • Key locator
     • Trust anchor
     • Trusted ID evaluator
     • Hardware cryptographic device support for Web Services Security
     • Default configuration
     • General sample bindings for JAX-WS applications
     • Default sample configurations for JAX-RPC
     • Default implementations of the Web Services Security service provider programming interfaces
     • XML digital signature
     • Collection certificate store
     • Certificate revocation list
     • XML encryption
     • Security token
     • LTPA and LTPA v2 tokens
     • Username token
     • XML token
     • Binary security token
     • Kerberos token
     • Kerberos message protection for web services
     • Kerberos usage overview for web services
     • Kerberos configuration models for web services
     • Kerberos clustering for web services
     • Kerberos authentication in a single or cross realm environment
     • SAML token
     • Time stamp
     • Nonce, a randomly generated token
     • Basic Security Profile compliance tips
     • Distributed nonce cache
     • Web Services Security token propagation
     • 2. Decide which programming model, JAX-WS or JAX-RPC, works best for securing your web services applications.
     • Overview of standards and programming models for web services message-level security
     • 3. Configure the security bindings, or migrate an application and associated bindings.
     • Configure default Web Services Security bindings
     • Migration of JAX-WS Web Services Security bindings from v6.1
     • 4. Develop and assemble a JAX-WS application.
     • Develop message-level security for JAX-WS web services
     • Web Services Security API programming model
     • Service Programming Interfaces (SPI)
     • Develop SAML applications
     • Create a SAML bearer token using the API
     • Create a SAML holder-of-key token using the API
     • Create a SAML sender-vouches token using the API
     • Propagation of SAML tokens using the API
     • Web services client token cache for SAML
     • Secure web services applications using the WSS APIs at the message level
     • Secure messages at the request generator using WSS APIs
     • Configure encryption to protect message confidentiality using the WSS APIs
     • Encrypting the SOAP message using the WSSEncryption API
     • Choosing encryption methods for generator bindings
     • Add encrypted parts using the WSSEncryptPart API
     • Configure generator signing information to protect message integrity using the WSS APIs
     • Configure signing information using the WSS APIs
     • Configure signing information using the WSSSignature API
     • Add signed parts using the WSSSignPart API
     • Configure request signing methods for the client
     • Attach the generator token using WSS APIs to protect message authenticity
     • Configure generator security tokens using the WSS API
     • Secure messages at the request generator using WSS APIs
     • Configure encryption to protect message confidentiality using the WSS APIs
     • Encrypting the SOAP message using the WSSEncryption API
     • Choosing encryption methods for generator bindings
     • Add encrypted parts using the WSSEncryptPart API
     • Configure generator signing information to protect message integrity using the WSS APIs
     • Configure signing information using the WSS APIs
     • Configure signing information using the WSSSignature API
     • Add signed parts using the WSSSignPart API
     • Configure request signing methods for the client
     • Attach the generator token using WSS APIs to protect message authenticity
     • Configure generator security tokens using the WSS API
     • Send self-issued SAML bearer tokens using WSS APIs
     • Insert SAML attributes using WSS APIs
     • Send self-issued SAML sender-vouches tokens using WSS APIs with message level protection
     • Send self-issued SAML sender-vouches tokens using WSS APIs with SSL transport protection
     • Send self-issued SAML holder-of-key tokens with symmetric key using WSS APIs
     • Send self-issued SAML holder-of-key tokens with asymmetric key using WSS APIs
     • Request SAML bearer tokens from an external STS using WSS APIs and transport level protection
     • Request SAML sender-vouches tokens from an external STS using WSS APIs and message level protection
     • Request SAML sender-vouches tokens from an external STS using WSS APIs and transport level protection
     • Request SAML holder-of-key tokens with symmetric key from external security token service using WSS APIs
     • Request SAML holder-of-key tokens with asymmetric key from External Security Token Service using WSS APIs
     • Send a security token using WSSAPIs with a generic security token login module
     • Secure messages at the response consumer using WSS APIs
     • Configure decryption methods to protect message confidentiality using the WSS APIs
     • Decrypting SOAP messages using the WSSDecryption API
     • Choosing decryption methods for the consumer binding
     • Add decrypted parts using the WSSDecryptPart API
     • Verify consumer signing information to protect message integrity using WSS APIs
     • Verify signing information for the consumer binding using the WSS APIs
     • Verify the signature using the WSSVerification API
     • Verify signed parts using the WSSVerifyPart API
     • Configure response signature verification methods for the client
     • Validate the consumer token to protect message authenticity
     • Configure the consumer security tokens using the WSS API
     • Configure Web Services Security using the WSS APIs
     • Encrypted SOAP headers
     • Signature confirmation
     • Develop JAX-WS based web services client applications that retrieve security tokens
     • Develop JAX-WS based web services server applications that retrieve security tokens
     • 5. Deploy the JAX-WS application.
     • 6. Configure and administer the Web Services Security runtime environment.
     • Auditing the Web Services Security runtime
     • Secure web services using policy sets
     • Configure policy set and bindings to encrypt a UsernameToken
     • Configure the username and password for WS-Security Username or LTPA token authentication
     • Secure requests to the trust service using system policy sets
     • Enable secure conversation
     • Web Services Secure Conversation
     • Scoping of Web Services Secure Conversation
     • Secure conversation client cache and trust service configuration
     • Derived key token
     • Enable secure conversation in a mixed cluster environment
     • Enable distributed cache and session affinity when using Secure Conversation
     • Flow for establishing a security context token to secure conversations
     • Flow for establishing a security context token to secure reliable messaging
     • Enable the distributed cache using synchronous update and token recovery
     • Configure the token generator and token consumer to use a specific level of WS-SecureConversation
     • Web Services Secure Conversation standard
     • Trust service
     • Security context token
     • System policy sets
     • Web Services Trust standard
     • Configure system policy sets
     • Define a new system policy set
     • Configure attachments for the trust service
     • Create a service endpoint attachment
     • Configure the security context token provider for the trust service
     • Modify the security context token provider configuration for the trust service
     • Trust service token custom properties
     • Disable the submission draft level for the security context token provider
     • Configure trust service endpoint targets
     • Assign a new target for the trust service
     • Update the Web Services Security runtime configuration
     • Configure the Web Services Security distributed cache
     • Configure the Kerberos token for Web Services Security
     • Configure the Kerberos token policy set for JAX-WS applications
     • Configure the bindings for message protection for Kerberos
     • Update the system JAAS login with the Kerberos login module
     • Configure Kerberos policy sets and V2 general sample bindings
     • 7. Configure policy sets through metadata exchange (WS-MetadataExchange).
     • Secure JAX-RPC web services using message-level security
     • 1. Learn about Web Services Security.
     • Web Services Security concepts
     • What is new for securing web services
     • Web Services Security enhancements
     • Supported functionality from OASIS specifications
     • Web Services Security specification - a chronology
     • Web Services Security provides message integrity, confidentiality, and authentication
     • High-level architecture for Web Services Security
     • Security model mixture
     • Overview of platform configuration and bindings
     • Keys
     • Key locator
     • Trust anchor
     • Trusted ID evaluator
     • Hardware cryptographic device support for Web Services Security
     • Default configuration
     • General sample bindings for JAX-WS applications
     • Default sample configurations for JAX-RPC
     • Default implementations of the Web Services Security service provider programming interfaces
     • XML digital signature
     • Collection certificate store
     • Certificate revocation list
     • XML encryption
     • Security token
     • LTPA and LTPA v2 tokens
     • Username token
     • XML token
     • Binary security token
     • Kerberos token
     • Kerberos message protection for web services
     • Kerberos usage overview for web services
     • Kerberos configuration models for web services
     • Kerberos clustering for web services
     • Kerberos authentication in a single or cross realm environment
     • SAML token
     • Time stamp
     • Nonce, a randomly generated token
     • Basic Security Profile compliance tips
     • Distributed nonce cache
     • Web Services Security token propagation
     • 2. Decide which programming model, JAX-WS or JAX-RPC, works best for securing your web services applications.
     • Overview of standards and programming models for web services message-level security
     • 3. Configure Web Services Security.
     • 4. Specify the application-level configuration.
     • Configure message-level security for JAX-RPC at the application level
     • Configure generator signing using JAX-RPC to protect message integrity
     • Configure the signing information using JAX-RPC for the generator binding on the application level
     • Configure consumer signing using JAX-RPC to protect message integrity
     • Configure the signing information using JAX-RPC for the consumer binding on the application level
     • Configure the key information using JAX-RPC for the generator binding on the application level
     • Configure the key information for the consumer binding on the application level
     • Configure token generators using JAX-RPC to protect message authenticity at the application level
     • Configure token consumers using JAX-RPC to protect message authenticity at the application level
     • Configure encryption using JAX-RPC to protect message confidentiality at the application level
     • Configure encryption to protect message confidentiality at the application level
     • 5. Specify the server-level configuration.
     • Configure message-level security for JAX-RPC at the server or cell level
     • Configure the signing information using JAX-RPC for the generator binding on the server or cell level
     • Configure the signing information using JAX-RPC for the consumer binding on the server or cell level
     • Configure the key information for the generator binding using JAX-RPC on the server or cell level
     • Configure the key information for the consumer binding using JAX-RPC on the server or cell level
     • Configure encryption using JAX-RPC to protect message confidentiality at the server or cell level
     • Configure encryption to protect message confidentiality at the server or cell level
     • Configure token generators using JAX-RPC to protect message authenticity at the server or cell level
     • Configure token consumers using JAX-RPC to protect message authenticity at the server or cell level
     • 6. Specify the cell-level configuration.
     • Configure message-level security for JAX-RPC at the server or cell level
     • Configure the signing information using JAX-RPC for the generator binding on the server or cell level
     • Configure the signing information using JAX-RPC for the consumer binding on the server or cell level
     • Configure the key information for the generator binding using JAX-RPC on the server or cell level
     • Configure the key information for the consumer binding using JAX-RPC on the server or cell level
     • Configure encryption using JAX-RPC to protect message confidentiality at the server or cell level
     • Configure encryption to protect message confidentiality at the server or cell level
     • Configure token generators using JAX-RPC to protect message authenticity at the server or cell level
     • Configure token consumers using JAX-RPC to protect message authenticity at the server or cell level
     • 7. Specify the platform-level configuration.
     • Configure Web Services Security using JAX-RPC at the platform level
     • Configure a nonce on the server or cell level
     • Distribute nonce caching to servers in a cluster
     • Configure the key locator using JAX-RPC for the generator binding on the application level
     • Configure the key locator using JAX-RPC for the consumer binding on the application level
     • Configure the key locator using JAX-RPC on the server or cell level
     • Configure trust anchors for the generator binding on the application level
     • Configure trust anchors for the consumer binding on the application level
     • Configure trust anchors on the server or cell level
     • Configure the collection certificate store for the generator binding on the application level
     • Configure the collection certificate store for the consumer binding on the application level
     • Configure the collection certificate on the server or cell level
     • Configure trusted ID evaluators on the server or cell level
     • 8. Develop and assemble a JAX-RPC application, or migrate an existing application.
     • Migrate JAX-RPC Web Services Security applications to v8.0 applications
     • Migrate the JAX-RPC server-side extensions configuration
     • Migrate the client-side extensions configuration
     • Migrate the server-side bindings file
     • Migrate the client-side bindings file
     • Develop message-level security for JAX-RPC web services
     • Develop web services clients that retrieve tokens from the JAAS Subject in an application
     • Develop web services applications that retrieve tokens from the JAAS Subject in a server application
     • 9. Deploy the JAX-RPC application.
     • Secure web services using Security Markup Assertion Language (SAML)
     • 1. Learn about SAML.
     • SAML concepts
     • SAML assertions defined in the SAML Token Profile standard
     • Default policy sets and sample bindings for SAML
     • Overview of API for SAML
     • SAML usage scenarios
     • Limitations of the SAML implementation
     • 2. Configure SAML application support.
     • Secure messages using SAML
     • Signing SAML tokens at the message level
     • Configure policy sets and bindings to communicate with STS
     • Configure client and provider bindings for the SAML bearer token
     • Configure client and provider bindings for the SAML holder-of-key symmetric key token
     • Configure client and provider bindings for the SAML sender-vouches token
     • Manage self-issue SAML token configuration using wsadmin
     • 3. Develop and assemble a SAML application.
     • Develop SAML applications
     • Create a SAML bearer token using the API
     • Create a SAML holder-of-key token using the API
     • Propagation of SAML tokens using the API
     • Web services client token cache for SAML
     • 4. Deploy the SAML application.
     • Deploy applications that use SAML
     • Propagate SAML tokens
     • Create SAML attributes in SAML tokens
     • SAML user attributes
     • Establishing security context for web services clients using SAML security tokens
     • Authenticate web services using generic security token login modules
     • 1. Learn about generic security token login modules.
     • Generic security token login modules
     • Generic security token login module for the token generator
     • Generic security token login module for the token consumer
     • 2. Administering a generic security token login module.
     • Configure a generic security token login module for an authentication token: Token generator
     • Configure a generic security token login module for an authentication token: Token consumer
     • Web services - Addressing (WS-Addressing)
     • Develop applications that use Web Services Addressing
     • Web services - Resource framework (WSRF)
     • Create stateful web services by using the Web Services Resource Framework
     • Web services - Policy (WS-Policy)
     • Use WS-Policy to exchange policies in a standard format
     • WS-Policy
     • Web service providers and policy configuration sharing
     • Web service clients and policy configuration to use the service provider policy
     • WS-MetadataExchange requests
     • Use WS-Policy to exchange policies in a standard format
     • Configure a service provider to share its policy configuration
     • Configure a service provider to share its policy configuration using wsadmin.sh
     • Configure the client.policy to use a service provider policy
     • Configure the client.policy to use a service provider policy using wsadmin.sh
     • Configure the client.policy to use a service provider policy from a registry
     • Configure security for a WS-MetadataExchange request
     • Web services - Reliable messaging (WS-ReliableMessaging)
     • Add assured delivery to web services through WS-ReliableMessaging
     • Develop a reliable web service application
     • Configure a WS-ReliableMessaging policy set by
     • Deploy web services applications onto application servers
     • Attach and binding a WS-ReliableMessaging policy set to a web service application by
     • Web services - UDDI registry
     • Get started with the UDDI registry
     • Use the UDDI registry
     • Web services - Transaction support (WS-Transaction)
     • Create an application that uses the Web Services Business Activity support
     • Use WS-Transaction policy to coordinate transactions or business activities for web services
     • WS-Transaction
     • Web Services Atomic Transaction support in the application server
     • Web Services Business Activity support in the application server
     • Web services transactions, high availability, firewalls and intermediary nodes
     • Transaction compensation and business activity support
     • WS-Transaction and mixed-version cells
     • Use WS-Transaction policy to coordinate transactions or business activities for web services
     • Configure a JAX-WS client for WS-Transaction context
     • Configure a JAX-WS web service for WS-Transaction context
     • Configure a WS-Transaction policy set using wsadmin.sh
     • Configure Web Services Transaction support in a secure environment
     • Configure an intermediary node for web services transactions
     • Enable WAS to use an intermediary node for web services transactions
     • Configure a server to use business activity support
     • Create an application that uses the Web Services Business Activity support
     • Web services - Transports
     • Use HTTP session management support for JAX-WS applications
     • Use HTTP to transport web services requests for JAX-RPC applications
     • Assembling web services applications
     • Assembling a JAR file that is enabled for web services from an enterprise bean
     • Assembling a web services-enabled enterprise bean JAR file from a WSDL file
     • Assembling a WAR file that is enabled for web services from Java code
     • Assembling a web services-enabled WAR file from a WSDL file
     • Assembling an enterprise bean JAR file into an EAR file
     • Assembling a web services-enabled WAR into an EAR file
     • Enable an EAR file for EJB modules that contain web services
     • Enable an EAR file for web services with the endptEnabler command
     • Deploy web services applications onto application servers
     • JAX-WS application deployment model
     • Use a third-party JAX-WS web services engine
     • Develop JAX-RPC web services clients
     • Develop client bindings from a WSDL file for a JAX-RPC Web services client
     • Change SOAP message encoding to support WSI-Basic Profile
     • Configure the JAX-RPC web services client deployment descriptor with an assembly tool
     • Configure the JAX-RPC client deployment descriptor for handler classes
     • Configure the JAX-RPC web services client bindings in the ibm-webservicesclient-bnd.xmi deployment descriptor
     • Implement extensions to JAX-RPC web services clients
     • Custom data binders for JAX-RPC applications
     • Custom binding providers for JAX-RPC applications
     • Send implicit SOAP headers with JAX-RPC
     • Receive implicit SOAP headers with JAX-RPC
     • Send transport headers with JAX-RPC
     • Retrive transport headers with JAX-RPC
     • Make deployed web services applications available to clients
     • Configure web services client bindings
     • Configure endpoint URL information for HTTP bindings
     • Configure endpoint URL information for JMS bindings
     • Configure endpoint URL information to directly access enterprise beans
     • Publish WSDL files
     • Publish WSDL files using a URL
     • Use HTTP to transport web services requests for JAX-WS applications
     • Deploy web services applications onto application servers
     • JAX-WS application deployment model
     • Use a third-party JAX-WS web services engine
     • Define and managing secure policy set bindings
     • Configure the SSL transport policy
     • Configure web service binding for SCA transport layer authentication
     • Transformation of policy and binding assertions for WSDL
     • Secure message parts
     • Signing and encrypting message parts using policy sets
     • Configure the callers for general and default bindings
     • Change the order of the callers for a token or message part
     • Configure web service binding to use SSL
     • Configure web service binding to perform LTPA authentication
     • Use HTTP session management support for JAX-WS applications
     • Invoke JAX-WS web services asynchronously using the HTTP transport
     • Use the JAX-WS asynchronous response servlet
     • Use the JAX-WS asynchronous response listener
     • Make deployed web services applications available to clients
     • Configure web services client bindings
     • Configure endpoint URL information for HTTP bindings
     • Configure endpoint URL information for JMS bindings
     • Configure endpoint URL information to directly access enterprise beans
     • Publish WSDL files
     • Publish WSDL files using a URL
     • Use HTTP to transport web services
     • Configure additional HTTP transport properties using the JVM custom property panel in the administrative console
     • Configure additional HTTP transport properties using the wsadmin command-line tool
     • Configure additional HTTP transport properties for JAX-RPC web services with an assembly tool
     • Configure a permanent reply queue for web services using SOAP over JMS
     • Configure a permanent replyTo queue for JAX-RPC web services using SOAP over JMS (deprecated)
     • Use SOAP over JMS to transport web services