Downloaded 12 times
Uploaded byOliver Busse
Transformations
Oliver Busse presented techniques for transforming legacy applications to take advantage of modern patterns in XPages. This includes migrating profile documents to Java beans to improve performance and usability. The presentation also covered extending full text search to faceted search by filtering results based on metadata tags. Demo code was provided to illustrate migrating profile documents to beans and implementing a faceted search.
More Related Content
![Lect 1 Number systems and base conversions. [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/lect1numbersystemsandbaseconversions-260111134109-67c2d865-thumbnail.jpg?width=640&height=640&fit=bounds)
Transformations
- 1. Transformations Smart Application Migration OliverBusse, 31.03.2015, 13:30, Room D
- 2. Agenda •About me •What‘s this? •Preamble •Migratedatabase and user profiles • Legacy profile documents vs. Java Beans • Value lists made available over the whole application •User and environment information • What can a user see and use? •Extending Fulltext search to a facetted search • Filtering your data with meta tags
- 3. Oliver Busse • „BleedingYellow“ since 2000 • OpenNTF Board Member • IBM Champion for ICS in 2015 • Engage.UG first-timer
- 4. Overview •What‘s this? • Transforming& re-using commonly used legacy patterns in XPages • Don‘t fear Java • Avoid @Formulas in SSJS • Ideas for best practices •What‘s it not? • An XPages Introduction • A Java beginner‘s guide • A complete application migration strategy
- 5. Preamble •Why not touse SSJS „excessively“? • SSJS is interpreted at runtime • SSJS is compiled at runtime (every time you call it!) • Compiled SSJS is hard to debug while executed
- 6. 6#engageug Migrating database anduser profiles
- 7. What we findin legacy apps: profile documents Disadvantages • You cannot see them without using tools • You can edit and create them only programmatically • Sometimes replication issues • Unwanted Caching ;-) Advantages • Quick access without using lookup views • Caching
- 8. What we missedin many cases DatabaseScript != Global Declarations Encapsuled, no access from outside (except Database Events)
- 9. Performance-Killer Numerous usage ofthose formulas slow down the app one of many...
- 10.
- 11. Ingredients •Transformation of profiledocuments to „standard“ documents 1. Create a corresponding lookup view 2. Optional: corresponding forms for maintenance 3. Create the Java Bean classes 4. Define those Bean classes in faces-config.xml
- 12. Preparation: Lookup Views •Keyfor Database Profiles = dbprofile •Key for User Profiles = Canonical Name •Key for Value Lists = free but unique
- 13. Preparation: Java Beans •3 Classes: • DatabaseProfileBean • AppConfigBean • UserProfileBean • The DatabaseProfileBean initializes the document if it doesn‘t exist • The UserProfileBean initializes the document when the user saves it for the first time
- 14. faces-config.xml <faces-config> <!-- Database ProfileBean --> <managed-bean> <managed-bean-name>dbprofile</managed-bean-name> <managed-bean-class>com.icsug.DatabaseProfileBean </managed-bean-class> <managed-bean-scope>application</managed-bean-scope> </managed-bean> <!-- User Profile Bean --> <managed-bean> <managed-bean-name>userprofile</managed-bean-name> <managed-bean-class>com.icsug.UserProfileBean </managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean> <!-- Application Configuration --> <managed-bean> <managed-bean-name>application</managed-bean-name> <managed-bean-class>com.icsug.AppConfigBean </managed-bean-class> <managed-bean-scope>application</managed-bean-scope> </managed-bean> </faces-config>
- 15. Digression: Bean Scopes& Lifecycles •Request • Lives beginning with the request to receiving the response •View • Within a page until changing the page, even during partial refreshes •Session • Per user session •Application • During the life time of th application (e.g. until server restart or calling an initialization method)
- 16.
- 17. 17#engageug User and EnvironmentInformation
- 18. User and EnvironmentInformation Name variations Access Level ACL Options notes.ini variables Environment Bean
- 19. faces-config.xml: EnvironmentBean 19#engageug <?xml version="1.0"encoding="UTF-8"?> <faces-config> <!-- Environment Bean --> <managed-bean> <managed-bean-name>env</managed-bean-name> <managed-bean-class>com.icsug.EnvironmentBean </managed-bean-class> <managed-bean-scope>view</managed-bean-scope> </managed-bean> </faces-config>
- 20.
- 21. Example: ACL Options Thedelete button is only visible if the user can delete documents
- 22. Even in themes! 22#engageug <theme extends="flatly" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="platform:/plugin/com.ibm.designer.domino.style kits/schema/stylekit.xsd"> <!-- displaya submit type button only if user can create documents via ACL --> <control> <name>Button.Submit</name> <property type="boolean"> <name>rendered</name> <value>#{env.createDocuments}</value> </property> </control> </theme>
- 23.
- 24. 24#engageug Extending Fulltext-Search toa Facetted Search
- 25. Facetted Search „Faceted search,also called faceted navigation or faceted browsing, is a technique for accessing information organized according to a faceted classification system, allowing users to explore a collection of information by applying multiple filters.“ http://en.wikipedia.org/wiki/Faceted_search
- 26.
- 27.
- 28. Facetted Search withDomino? 1. Fulltext Search 2. Filtering result from extra meta data 1. Meta data search with facet selection 2. Fulltext Search in results
- 29. FacettedSearchBean (Session scoped) FacetsSearchTerm FacettedSearch Bean DocumentCollection (ArrayList<SearchResultEntry>)
- 30.
- 31. Facetted Search: Outlook& Alternatives •Using OpenNTF API‘s Graph-DB functions •Using a 3rd party Graph-DB like Apache Solr 31#engageug
- 32.
- 33.