WebSphere Commerce Server v7.0 Development - Hyderabad

Friday, 19 December 2014

Item details

City: Hyderabad, Andhra Pradesh
Offer type: Offer

Contacts

Contact name Rakesh
Phone 9700330693

Item description

Exercise 1.Introduction to the WebSphere Commerce development environment

Duration: 1 hour 30 minutes
Learning objectives: After completing this exercise, students should be able to:
•Start the development environment
•Identify common projects used in the development process
•Locate store artifacts to customize
•Launch the WebSphere Commerce test server
•Analyze server logs for debugging and error handling

Unit 2. Developing and customizing storefront pages

Duration: 1 hour 15 minutes
Learning objectives: After completing this unit, students should be able to:
•Describe the behavior of the presentation layer in WebSphere Commerce
•List the process for modifying the behavior of WebSphere Commerce storefront assets
•Work with JavaServer Pages
•Globalize storefronts
•Outline the business processes used in some common sample stores
•Prepare property files
•Manipulate data beans
•Comply with recommended development strategies and best practices

Exercise 2. Customizing storefront pages

Duration: 2 hours
Learning objectives: After completing this exercise, students should be able to:
•Display the Consumer Direct storefront
•Find the JSP file that produces a view
•Inspect the mappings in the Struts configuration file
•Update a property file to modify store text
•Review property-level changes in a store
•Record the unique identifier of a store
•Map a new view to a JSP file in the Struts configuration file
•Update the WebSphere Commerce registry with new view information
•Construct a new property file
•Create a new JSP file for use in WebSphere Commerce
•Create and load access policies to support new views

Unit 3. Developing and customizing store business logic

Duration: 1 hour 30 minutes
Learning objectives: After completing this unit, students should be able to:
•Explain the use of commands and the command API
•Name-value pair command processing
•Business object document processing
•Explain the process used to extend WebSphere Commerce business logic
•Relate business process from the storefront presentation to the underlying business logic
•Describe issues related to command behavior, such as business contexts and access controls

Exercise 3. Customizing store business logic

Duration: 1 hour 45 minutes
Learning objectives: After completing this exercise, students should be able to:
•Create new task command interfaces
•Create new task command implementations
•Create the new controller command interface
•Create the new controller command implementation class
•Register the new controller command
•Load access control policy
•Modify the JSP file to process the controller command
•Test on the WebSphere Commerce Test Servers

Unit 4. Developing and customizing the persistence layer

Duration: 1 hour 30 minutes
Learning objectives: After completing this unit, students should be able to:
•Provide a high-level description of the WebSphere Commerce data model
•Describe the implementation of EJBs in WebSphere Commerce
•Explain when and why it may be necessary to extend the WebSphere Commerce data model
•Add custom SQL to existing session beans
•Create new session and entity beans to extend the WebSphere Commerce data model
•Develop and utilize access beans and data beans in WebSphere Commerce
•Perform the process of extending WebSphere Commerce using EJBs

Exercise 4. Creating an Enterprise JavaBean in WebSphere Commerce

Duration: 2 hours
Learning objectives: After completing this exercise, students should be able to:
•Create a WebSphere Commerce table
•Create an entity bean
•Configure EJB properties
•Modify EJB methods and finders
•Map the database table to the EJB
•Generate the access bean for the EJB
•Test the entity bean

Unit 5. Developing and customizing the Web 2.0 presentation layer

Duration: 1 hour 15 minutes
Learning objectives: After completing this unit, students should be able to:
•Analyze the architecture of the Web 2.0 store
•Design interactive storefronts using the Dojo toolkit and WebSphere Commerce extensions
•Construct agile storefronts using Asynchronous Java and XML (Ajax)
•Customize a store that uses Web 2.0 elements following recommended development processes

Exercise 5. Customizing a Web 2.0 storefront

Duration: 2 hours
Learning objectives: After completing this exercise, students should be able to:
•Identify content for Ajax enablement
•Enable a JSP file for Web 2.0 content
•Declare a refresh controller
•Declare the shopping cart as a refresh area
•Declare services and contexts
•Add a Tooltip widget to catalog items
•Support products with drag-and-drop functionality
•Test a Web 2.0-enabled storefront

Unit 6. BOD command processing and the data service layer

Duration: 1 hour 15 minutes
Learning objectives: After completing this unit, students should be able to:
•Describe the purpose and function of BOD command processing in the business logic layer
•Customize or extend BODs
•Describe how Service Data Objects (SDOs) are used within the BOD command processing framework
•Leverage the Java Emitter Template (JET) to generate service modules and implementation code
•Transform logical objects to physical objects using Business Object Mediators in the Data Service Layer
•Use a query template to translate XPath into SQL statements

Exercise 6. BOD command processing and the data service layer

Duration: 3 hours
Learning objectives: After completing this exercise, students should be able to:
•Create a registered shopper
•Create a new WebSphere Commerce table
•Create a noun to support the logical model
•Generate the service module using the Java Emitter Template (JET)
•Configure the service module
•Generate SDOs for a noun
•Implement the persistence layer for the WebSphere Commerce BOD programming model
•Add language-specific exception messages
•Implement Business Object Mediators to transform logical SDOs and physical SDOs
•Configure the Data Service Layer for the service module
•Register the new Get command in the command registry
•Implement the client library
•Implement access control
•Deploy and validate the service module with JUnit