Collaborate 2011-Site Studio versus Site Studio for External Applications: Smack Down!

Notas do Editor

1. Fishbowl Solutions is a recognized leader in the Oracle Enterprise 2.0 space. Wehave over 10 years experience designing, implementing and supporting enterprise content management and portal systems to customer throughout North America and EMEA. This includes delivering value-add software components for Oracle Enterprise Content Management and Oracle WebCenter with recent success delivering this components to hundreds of customers over the last 2 years. More recently, we have very proud to have become Officially certified Oracle ECM & WebCenter Specialized partner as well as a North American Public Sector Pillar Partner for Enterprise 2.0.
2. Ask how much experience individuals have – contribution and development
3. Essentially a framework to develop, manage, as well as store and host web sites.Also separates developer from contributor tasks.UCM = Universal Content ManagementAnd now with 11g, there are two options: SS and SSXA
4. A server-side component: runs on top of UCMA client-side application:used to design and build the web sitesAn optional web-based Contributor application: for easily editing site content
5. When SS first came out, one of the main goals was to separate the content from the presentation. This continues to be one of the main features but the functionality is evolving.In the 10gR4 release, the back-end architecture of SS was changed, focusing on more reusability of both assets and content. New services were also introduced allowing SS content to be displayed in alternate sources, e.g. portals.And now in 11g, there is a new feature called SSXA. While the functionality to call SS content from an external application existed in 10gR4, SSXA really formalized this process, providing a framework and set of libraries for referencing web content in external applications. There’s even a tutorial on how to setup a site this way using Jdeveloper.
6. Multi-site: can even re-use assets/contentContent Server storage: the main storage location, but not necessarily the only placeContribution: allow contributors to manage their own contentUCM features: get the basics of UCM: revisions, workflow, as well as the more advanced features.
7. Arch: SS sites run and are hosted within the UCM application, whether it’s 10g or 11g. SSXA sites are their own apps on Weblogic Server.Language: SS sites can be written in ASP and JSP, but I’ve found the most common is HCSP.
8. Connection: SS are within UCM so they can call services, often done using Idoc. SSXA sites need their own connection since they are separate apps. Deployment: SS sites can be published to a static folder,using Site Studio Publisher. If static content is your goal, SSXA is probably not the technology you will use for development & deployment.
9. SS: security is controlled the same for both developer and contributor assets.SSXA sites rely on Global Role and a Security Role Assignment (defined in weblogic.xml) to define contribution access.
10. Site Studio: Includes project file and all assets. No additional configuration or external files are required (OOTB).SSXA: In Patch Set 3 and later, all content and templates can be stored in UCM. There is still the option to deploy the templates in the EAR file. A number of application configuration files are also required, which are stored inside the application: /Web Content/WEB-INF/. E.g. web.xml, web-config.xml, any error pages.
11. Dev tool: I’ve had people ask if you can do SSXA development using SS Designer. The answer is yes to a certain degree, but you cannot create the EAR file with Designer.Caching:SS caching on sections by setting the Max Age section property.SSXA caching by setting certain parameters in the wcm:dynamicList or wcm:idcService tags.
12. SS: You may be able to integrate and SS sites without a custom component, e.g. RSS, but more complicated integrations likely require a component.SSXA: all of the same rules apply but it’s easier to develop the Java code and include it in the application as a library. Can also use scriptlets, which is not necessarily my recommendation.
13. SS: you create a section with an error page, display the error message with Idoc, and set the section as the Error Handler. Done.SSXA:Each error page must be a static file, and included in the EAR file.
14. SS: The first two are Administrator functions. Last one is a CSP.SSXA: Context root: defined in weblogic.xml, applies to the application as a whole. You can optionally choose to not have a context root, however, only 1 application can be defined this way in each domain. Site root: defined in wcm-config.xml in the <site> tag. Officially called urlPattern.We found the easiest way to hide either of these roots without dropping them completely was through the use of a proxy on the web server (or mod_rewrite, etc.).
15. SS provides more UI-based development options, you CAN use Design view (although a lot of people recommend against it)SSXA: Design view is incredibly slow, and also doesn’t really provide any value.
16. Why disable contribution? Useful on a consumption-only server, when you have separate servers for contribution and consumption.SS: this variable is added to the config file, and UCM must be restarted.SSXA sites enable contribution through the use of a servlet and servlet filter, which makes disabling contribution more complicated. Editing the JS file is the best I’ve found so far.
17. Proprietary development method - HCSP/IdocScript
18. Features of WLS - caching, security, etc.Easier integration with external systems and applications
19. Redeployment = change control.
20. Another: Do you simply want to learn something new? SSXA could be your tool to learn in 2011.
21. So we covered a lot of information today, and I want to point you to some additional resources where you can further explore our product and service offerings.