Utilized Code Gen To Save Our Efforts In Sap Integration
Download as PPT, PDF0 likes356 views
The document discusses using code generation to create data access objects (DAOs) for an SAP integration project. It describes using the Squirrel SQL Client and DAO4J tools to automatically generate DAO interface, implementation, and data transfer object classes based on the database schema. This allows focusing on workflow design rather than manual data access coding, improving productivity and reducing errors.
![Utilized code generation to save our efforts in SAP Integration Albert Guo [email_address]](https://image.slidesharecdn.com/utilized-code-gen-to-save-our-efforts-in-sap-integration-1212844237526178-8/85/Utilized-Code-Gen-To-Save-Our-Efforts-In-Sap-Integration-1-320.jpg)
Utilized Code Gen To Save Our Efforts In Sap Integration
- 1. Utilized code generation to save our efforts in SAP Integration Albert Guo [email_address]
- 2. Agenda Scenario SAP Implementation Data Access Object Pattern Squirrel SQL Client and DAO4J Summary
- 3. Scenario
- 4. Scenario
- 6. SAP Implementation But including the connectivity and data access code within these components introduces a tight coupling between the components and the data source implementation. Such code dependencies in components make it difficult and tedious to do modification if requirement change.
- 7. Data Access Object Pattern
- 8. Data Access Object Data Access Object (DAO) is an object that provides an abstract interface to some type of database or persistence mechanism, providing some specific operations without exposing details of the database. This isolation separates the concerns of what data accesses the application needs, in terms of domain-specific objects and data types (the public interface of the DAO), and how these needs can be satisfied with a specific DBMS, database schema, etc. (the implementation of the DAO). This design pattern is equally applicable to most programming languages, most types of software with persistence needs and most types of database, but it is traditionally associated with J2EE applications and with relational databases accessed via the JDBC API because of its origin in Sun Microsystems' best practice guidelines ("Core J2EE Patterns") for that platform.
- 9. DAO Structure © 2006 PTC The BusinessObject represents the data client. It is the object that requires access to the data source to obtain and store data. The DataAccessObject is the primary object of this pattern. The DataAccessObject abstracts the underlying data access implementation for the BusinessObject to enable transparent access to the data source This represents a Transfer Object used as a data carrier This represents a data source implementation. A data source could be a database such as an RDBMS, OODBMS, XML repository, flat file system, and so forth. A data source can also be another system (legacy/mainframe), service (B2B service or credit card bureau), or some kind of repository (LDAP).
- 10. Participants and Responsibilities © 2006 PTC Create Read Update, Delete
- 11. Strategies - Automatic DAO Code Generation Strategy Automatic DAO Code Generation Strategy Since each BusinessObject corresponds to a specific DAO, it is possible to establish relationships between the BusinessObject, DAO, and underlying implementations (such as the tables in an RDBMS). Once the relationships are established, it is possible to write a simple application-specific code-generation utility that generates the code for all DAOs required by the application. © 2006 PTC DAO, DTO Classes SQL Client Code Gen Tool Generated Results
- 12. Strategies - Automatic DAO Code Generation Strategy which will generate the following java source files: DTO (Data Transfer Objects): This is the DTO Class DAO Interface DAO Impl Class © 2006 PTC DAO Interface DAO Impl DTO
- 13. Advatnages The advantage of using data access objects is the relatively simple and rigorous separation between two important parts of an application which can and should know almost nothing of each other, and which can be expected to evolve frequently and independently. Changing business logic can rely on the same DAO interface, while changes to persistence logic do not affect DAO clients as long as the interface remains correctly implemented. In the specific context of the Java , Data Access Objects can be used to insulate an application from the particularly numerous, complex and varied Java persistence technologies , which could be JDBC , JDO , EJB CMP , TopLink , Hibernate , iBATIS , or many others. Using Data Access Objects means the underlying technology can be upgraded or swapped without changing other parts of the application.
- 14. Implementation Steps Squirrel SQL Client and DAO4J can generate these codes, so we does not need to do from the scratch. We can take it as black box. We just need to focus on workflow design and author business objects. We don’t need to know how to do CRUD.
- 15. Squirrel SQL Client and DAO4J
- 16. Definition Squirrel SQL Client SQuirreL SQL Client is a graphical Java program that will allow you to view the structure of a JDBC compliant database, browse the data in tables, issue SQL commands etc. The minimum version of Java supported is 1.5.x as of SQuirreL version 2.4. http://squirrel-sql.sourceforge.net For more features and screenshots, you can go to http://squirrel-sql.sourceforge.net/index.php?page=screenshots DAO4J DAO4J can generate clear and efficient Java source files to populate Database tables via standard JDBC. http://freehost04.websamba.com/dao4j/ © 2006 PTC
- 17. Demo
- 18. Demo Select specific table. Right click, then select Generate DAO . 1
- 19. Demo Define code gen to where Define package name for each class Refer to database specific properties file in dao4j\conf 2
- 20. Demo
- 21. Class Diagram DAO Interface DTO Class The DTO Class which contains only the PK fields and can be used as the key of HashMap This table has more than 80-column, I’ll not show all attributes in class diagram DAO Impl DTO Class
- 22. Class Diagram We does not need to know the detail method operation, just call create method if we need to insert data into ERP interface table.
- 23. Source code snippet . . We just need to focus on how to retrieve all the necessary attributes, and set values to DTO Provide DTO and connection to create method. Then, everything is done.
- 24. ATTENTATION – Poor Exception Handling We need to add catch clause before finally clause
- 25. ATTENTATION – Poor Exception Handling
- 26. Summary
- 27. Benefits Enables Transparency Business objects can use the data source without knowing the specific details of the data source's implementation. Access is transparent because the implementation details are hidden inside the DAO. Reduces Code Complexity in Business Objects Because the DAOs manage all the data access complexities, it simplifies the code in the business objects and other data clients that use the DAOs. All implementation-related code (such as SQL statements) is contained in the DAO and not in the business object. This improves code readability and development productivity. Centralizes All Data Access into a Separate Layer Because all data access operations are now delegated to the DAOs, the separate data access layer can be viewed as the layer that can isolate the rest of the application from the data access implementation. This centralization makes the application easier to maintain and manage. © 2006 PTC
- 28. Summary Code Generation We can focus on workflow design, and retrieve required value and call DAO method.