GSA Connector 3.0 Webinar - June 2013
•
1 gostou•1,145 visualizações
Presented by Fishbowl Solutions 6-27-2013
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a GSA Connector 3.0 Webinar - June 2013
Semelhante a GSA Connector 3.0 Webinar - June 2013 (20)
Mais de Fishbowl Solutions
Mais de Fishbowl Solutions (14)
Último
Último (20)
GSA Connector 3.0 Webinar - June 2013
- 1. GSA Connector 3.0 for Oracle WebCenter Content Presented by Fishbowl Solutions 6-27-2013
- 2. www.fishbowlsolutions.com Agenda + Introduction + Google Search for WebCenter Content + 3.0 Connector Demo – New UI, Document Preview, User-Added Results and more… + Connector Details – How it works – New Security Options + Questions Version 3.0
- 3. www.fishbowlsolutions.com Fishbowl, Oracle, & Google Partnering with businesses to solve costly and frustrating knowledge sharing problems • Oracle & Google Partner • Specializing in portals & content management for 14 years • Enterprise consulting services • Packaged software for WebCenter • 100+ projects in last 2 years
- 4. www.fishbowlsolutions.com Why we’re here. Google + WebCenter. Better Together.
- 5. www.fishbowlsolutions.com Problems We’re Solving + User frustration with search within WebCenter + Spending too much time looking for content + Low user adoption of WebCenter due to poor result quality and user experience + WebCenter search experience can’t compare to internet search experience
- 6. www.fishbowlsolutions.com Problems in Enterprise Search 25% of employee's time is spent looking for information. of time is spent unsuccessfully searching for and recreating existing content. growth in enterprise data per year. 38% 61%
- 7. www.fishbowlsolutions.com Google Scale Drives The Experience • The Google index is larger than 30T URLs • Google crawls 20B pages per day • Google receives ~2B queries per day • The Google algorithm is made up of 200+ signals • Big Data analytics approach - 1% testing • Over 10,000 experiments annually • ~500 changes to the algorithm each year
- 9. www.fishbowlsolutions.com Query Interpretation Interpretation Web Center WebCenter WebCenter Portal WebCenter Content WebCenter Content Installation Web Center Type-Ahead Suggestions Initial query: Web Center Synonyms Example: WebCenter = UCM = Stellent
- 10. www.fishbowlsolutions.com Relevance Ranking and Signals • Document structure signals • Keywords, Proximity, Location • Metadata signals • Title, Occurrences • Freshness Signals • Last Modified • Frequency of Changes • Admin-Defined Result Biasing • Behavioral Signals • Self-Learning Scorer • 200+ signals (Oracle uses 2) Relevance ranking Signals
- 11. www.fishbowlsolutions.com Presentation – User Conversation Reach + Security + Speed Results Presentation
- 12. www.fishbowlsolutions.com Fishbowl Connector – Evolution Version Focus Version 1.0 May 2011 Indexing Public Content Server and SiteStudio websites with the GSA Version 2.0 Jan 2012 Added an out-of-the-box Content Server result template to expose Google Results with the native WebCenter UI Support for Secure Search Version 3.0 June 2013 Redesigned WebCenter search interface to expose the full Google search experience within WebCenter Content
- 14. www.fishbowlsolutions.com Demo – What You Saw + Type-Ahead + Document Preview + Dynamic Navigation + Search Category Segments + Advanced Search + User-Added Results + Related Queries + OneBox Modules + People Search + Spell Check + Multi-Repository Search Bold items are new in Version 3.0.
- 15. www.fishbowlsolutions.com Making it Happen: Google Search Appliance + Scalable hardware solution – Index up to 100 million items on a single appliance + Google-like search experience for your organization’s internal systems and data + Relevance and ease of use of Google.com, but with specific enterprise enhancements
- 16. www.fishbowlsolutions.com Making it Happen: Fishbowl Connector + Allows GSA to index content + Provide access to secured content + Allows incremental index updates + Provides metadata-indexing capabilities + Provides search Google search experience through WebCenter Content
- 17. www.fishbowlsolutions.com Extending Google Search: Developer API + Includes Fishbowl GSA Connector Google Search API to allow use in custom Content Sever templates, Site Studio websites, and Portals. + Features include: – Dynamic Navigation – User-Added Results – Related Queries – Dynamic Result Clusters – Spelling Suggestions – Type Ahead Search Suggestions – One Box Results – Document Previews – Support for Google /click protocol to enable Advanced Search Reporting and Self-learning Scorer
- 18. www.fishbowlsolutions.com What Else is New in 3.0 + Security – Feed Security Authorization Information (Policy ACLs) to GSA during indexing • Use metadata or specific values for users and groups – Support for Content Server ACLs • ACL Users, ACL Aliases, ACL Roles
- 19. www.fishbowlsolutions.com What Else is New in 3.0 + Ability to index display values for metadata fields – Ex: Option Lists with internal and visible values + Content Server as a OneBox Module – Real-Time Results • Recent News • My Content – Configurable Where Clause – Multiple Modules / Multiple Repositories – Can expose information not indexed by the GSA + Uses Google Connector Manager 3.0 Framework
- 20. www.fishbowlsolutions.com Upgrade Path, Benefits & Supported Versions + Current Customer Upgrade Path – Upgrade the Content Server Component – Upgrade the Connector Manager – Reconfigure the Connector + Benefits – Take advantage of new UI within WebCenter* – Leverage new features through search API – Security Flexibility + Supported Environments – GSA: 6.14**, 7.0+ – Oracle WebCenter Content: 10g, 11g *Customers may opt to retain version 2.5 interface after upgrading **Some features are only available with version 7.0 of the GSA
- 21. www.fishbowlsolutions.com Summary + Solving the WebCenter Search Problem with Google Search + Google Query Interpretation & Relevance + Transformed WebCenter Search Experience + Enhanced Security & Flexibility
- 22. Questions?
- 23. www.fishbowlsolutions.com Poll Question What value could the use of the GSA bring to your organization? Select all that apply. • Reduce user complaints & increase WebCenter adoption • Reduce time spent searching for content • Reduce time recreating content • Allow users to easily find content from multiple systems • Not sure
- 24. www.fishbowlsolutions.com One Stop Shop for GSA Software Hardware Services + + web: fishbowlsolutions.com email: info@fishbowlsolutions.com phone: +1.952.465.3400 blog: cfour.fishbowlsolutions.com
- 26. www.fishbowlsolutions.com GSA Enterprise Search Architecture
- 27. www.fishbowlsolutions.com Feeding Search Engine Content Connector Indexes content Asks for new or changed content items Feeds list of new or changed content to connector Feeds new or updated content to Search Engine Periodically Content Source
- 29. www.fishbowlsolutions.com Indexing Items from Oracle WebCenter Content Oracle WebCenter Content User Google Search Appliance Fishbowl GSA Connector Oracle WebCenter Content Checks in content item Indexes content Asks for new or changed content items Feeds list of new or changed content IDs to Connector Feeds new or updated content to GSA Periodically
- 30. www.fishbowlsolutions.com Searching Secured Content from within Oracle WebCenter Content Oracle WebCenter Content User Google Search Appliance Fishbowl GSA Connector Oracle WebCenter Content Performs search Forwards search request to the GSA Returns list of items back to WebCenterApplies result template and displays results to user Requests user ID Passes User ID back GSA Executes query against all content Requests which content is accessible by user (Batch Authorization) Requests security groups and accounts user has access to Passes security group and account information Evaluates which items user has access to Provides list of content items user can view
- 31. www.fishbowlsolutions.com Searching Secured Content from within Oracle WebCenter Content Oracle WebCenter Content User Google Search Appliance Fishbowl GSA Connector Oracle WebCenter Content Performs search Forwards search request to the GSA Returns list of items back to WebCenter Applies result template and displays results to user Requests user ID Passes User ID back GSA Executes query against all content Requests which content is accessible by user (Batch Authorization)Requests security groups and accounts user has access to Passes security group and account information Evaluates which items user has access to Provides list of content items user can view
- 32. www.fishbowlsolutions.com Searching Public Content from within Oracle WebCenter Content Oracle WebCenter Content User Google Search Appliance Fishbowl GSA Connector Oracle WebCenter Content Performs search Forwards search request to the GSA Returns list of items back to WebCenter Applies result template and displays results to user Executes query against all public content
- 33. www.fishbowlsolutions.com Searching Secured Content from the Google Search Appliance Front-End GSA Front-End User Google Search Appliance Fishbowl GSA Connector Oracle WebCenter Content Performs search Returns list of items to user with the GSA’s front-end interface Executes query against all content Requests which content is accessible by user (Batch Authorization) Requests security groups and accounts user has access to Passes security group and account information Evaluates which items user has access to Provides list of content items user can view Requests user credentials User credentials passed to GSA
- 34. www.fishbowlsolutions.com Searching Public Content from the Google Search Appliance Front-End GSA Front-End User Google Search Appliance Fishbowl GSA Connector Oracle WebCenter Content Performs search Returns list of items to user with the GSA’s front-end interface Executes query against all public content
- 35. www.fishbowlsolutions.com Google Solves the Search Problem
Notas do Editor
- Mention some 3.0 featuresDemo – focued on the new ui OOTB – it’s also possible to use this on portal, sitestudio, etc.
- Fishbowl’s overall mission is solving knowledge sharing and information management problems…We have over 12 years experience designing, implementing and supporting enterprise content management and portal systems to customers throughout North America and EMEA. We are both a Google Enterprise Search partner and an Oracle Gold partner and officially certified in Oracle WebCenter Content and PortalThis includes delivering off-the-shelfvalue-add software components for Oracle WebCenter Content and Portal– some of these are intranet in a box, mobile applications, and the google search appliance connector talking about today.
- These problems are the reason we’re here…User frustration with search within WebCenter – check something in and it get’s lost… don’t want to fill our metadata, or forgot and then no one else can find it.When they Can’t find anything – complain to IT. – many of you on the phone are IT, you have to deal with these complaints often.Spending too much time looking for content – wasted time, frustrationLow user adoption of WebCenter due to poor result quality and user experience – don’t like webcenter, poor user experience, want to use something else. Users or departments may resist using wcc, they want to use filesytem, or SharePoint, or their own desktop instead. We want to transform this so search at work, in WebCenter to make it as easy as search at home.Disparity between search at home and at work – users are used to google at home, they know a better way exists and they are impatient and frustrated that search at work doesn’t even come close.consumerization of IT. People have better tools to run their lives at home, and then they come to work and their forces to use old, clunky, less-intuative technology, which leaves them frustrated and confused. They feel like they don’t know if they have all the info they should have to most effectively do their job and that they have to work much harder than they should to find what info they do have. Google.com has trained users to expect easy, intuitive search. We want to solve the webcenter search problems by bringing Google search to WebCenter.
- Problems with webcenterarent unique to webcenter, they are shared across many enterprises using various technologies to search.you all have search– just about every system you have in place has some kind of search associated with it – but that doesn’t mean it works effectively – but they all have themEven though everyone has search research tells us that for most organizations don’t have effective search. Knowledge workers lose between 25 and 38% of their time to the inability to find necessary information. 25% is the amount of time spent search - looking for information they need to do their job. That’s more than a day a week.38% adds in the time people spend recreating content that already exists but that they were unable to find. 38% is almost two days a week.61%This problem isn't getting any easier either.Forrester reports organizations are seeing 61% data growth each year. 61% - if you think about that from a search perspective, that’s a lot of content change in one year. You need a robust search technology to be able to handle that growth and keep relevant content in front of your users. so this gets back to what is the value of search? Reducing these numbers. Doing your job more efficiently. Not spending 1-2 days a week, just getting ready to do your job. Not losing things after they get checked in because someone forgot to tag it right and now you need to recreate it. That’s the value to search.
- …So how do we do that?You can think about the search experience in 3 parts, interpretation, relevant ranking, and display. the GSA can bring these benefits to the search experience within Oracle WebCenter Content. What I’m going to do is walk through each of these pieces and talk about what they mean with regard to search and searching WebCenter Content and some of the features that address each of these areas.
- We talked about presentation, that has evolved with the connector over time. GSA & Connector So as we’ve looked to address these challenges the product has matured.Backend - indexingSecurity, Basic UIPresentation, Full Google Experience
- What youre going to see it the new ootbui – all of the functionally that you’re seeing can be integrated with portal, ss, etc.What you’re going to see:How the new interface…Have conversation with the searchFilter out the content - metadata facets, previews, and categoriesHow end users can directly improve the search experienceProvide access to content outside webcenterOPEN DEMO NOW
- Bold items are new in 3.0
- Ootb the gsa cannot index content from wcc.Connector allows that to happen.
- The connector includes the ootb UI you saw but also includes a fully documented and supported API for use with custom pages, site studio, portal, … RIDC –other APIsExpose all the features you saw – standard webcenter service calls, idoc, etc.Previews, UAR, Self-Learning Scorer.
- Google recommends feeding ACLs whenever possible for performance.
- Turing user intent into action to create value.Problems SolvedFeature Summary
- With that, let’s move on to some questions (move to last slide to show contact info).
- Problems we’re solving from first slide:User frustration with search within WebCenterSpending too much time looking for contentLow user adoption of WebCenter due to poor result quality and user experienceWebCenter search experience can’t compare to internet search experience
- As a google partner fishbowl can provide the hardware, software, and services necessary to meet your WebCenter or Enterprise search needs. World’s most popular search engine backed by best-in-class ECMSingle providerGSA Hardware, Software and ServicesGSA implementation and configuration expertsDeep domain expertise with Oracle WebCenterNumerous customers in productionEnd-to-End Consulting ServicesProject Scoping, Implementations, Support, Tuning
- The feeding process allows external sources to push content into the search index through content connectors instead of requiring the search engine to perform periodic crawls. The contents of the feeds typically contain metadata information about the content as well as a link to the location the search engine can retrieve the content for indexing or the actual content itself. Search engines typically include connectors for some common systems with the purchase of the software and may offer connectors for other content sources at an additional cost. Most of the search engines also include an SDK to allow custom development of connectors if necessary. One of the main advantages to using a feed is fact that the source is often aware of changes to content that have occurred since the last feed was sent. This allows for incremental inserts, updates, and deletes to be fed into the search index to reduce the amount of processing required by the index server and content source.Pros: More efficient and timely incremental index updates, ability to crawl non-HTML content.Cons: Page ranking may be indeterminate, or may require additional software or custom development to refine.
- --Crawling, also referred to as spidering, is one of the most common ways for a search engine to index website contents. The search index is configured with one or more URLs to begin processing, normally the website home page, or an index page with links to each of the sections to be indexed. The search index retrieves the contents of the page for indexing, as well as collecting a list of all of the links that exist on that page. It continues to process all of the links it finds throughout the site until all content in the site has been indexed. This process works best with traditional websites containing HTML with explicit links to other content located on the website vs. dynamic relationships built using JavaScript. After the initial index of the content, the indexer will periodically re-index the website to update the search index with any modified content. Pros: Easy to set up, search index can calculate page rank based on relationships through linksCons: Dynamically built pages and links can be difficult to index, difficult to index content other than HTML
- Index-Time ProcessTo begin generating the initial index of repository content, the connector manager starts a connector instance, which traverses the repository on a defined schedule. The connector manager formats the content and any associated metadata for a feed to the Google Search Appliance, which then creates an index of the documents. The following diagram shows these events in sequence: 1. The administrator uses the Admin Console to add a connector, define the traversal schedule, and set other parameters.2. The connector manager starts the connector instance on the schedule defined for the instance.3. The connector instance traverses the repository.4. The connector manager formats the documents and data for a feed to the Google Search Appliance.5. The feeds application programming interface (API) processes the document data.6. The Google Search Appliance indexes the documents and metadata.
- For public content in a repository, searches work the same way as they do with web and file system content. The Google Search Appliance searches its index and returns relevant results to the user without any involvement by the connector. To authorize access to private or protected content from a repository, the Google Search Appliance creates a connector instance at query time. The connector instance forwards authentication credentials to the repository for authorization checking. This diagram shows the event flow at a high level: 1. The end user submits a query to the Google Search Appliance.2. The Google Search Appliance prompts the end user for authentication credentials.3. The end user enters credentials, which are forwarded through the Google Search Appliance and connector manager to the repository. 4. The repository checks the user's credentials.5. The Google Search Appliance searches the index for relevant results. If the search results include protected documents, the connector instance contacts the repository to perform an authorization check.6. The repository performs an authorization check and restricts the result set to the documents to which the end user has access. 7. The end user views a page of the restricted results. The URL displayed depends on the connector instance configuration. Typically, the URL opens a repository summary page for the document.