Training Agenda
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Training Agenda

on

  • 1,580 views

 

Statistics

Views

Total Views
1,580
Views on SlideShare
1,580
Embed Views
0

Actions

Likes
0
Downloads
63
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 2 pm

Training Agenda Presentation Transcript

  • 1. I/PM 11g Training – Product Overview Sancho Pinto, Director of Product Management
  • 2. Introductions
    • Name
    • Location
    • Role/Organization
    • Background:
      • UCM? Attended UCM 11g training?
      • IPM 10g? ODC?
    • Familiarity with Accounts Payable concepts?
    • What are you looking for from this class
  • 3. Agenda
    • Day 1
      • I/PM 11g Overview
        • I/PM 11g and UCM
      • AP Concepts and Solution Overview
      • Pre-Sales Enablement
    • Day 2
      • Imaging Solution Components Overview
      • ODC for Invoices
        • POC configuration
      • OFR for Invoices
        • POC configuration
  • 4. Agenda
    • Day 3
      • IPM 11g
        • Architecture
        • Administration
      • FMW integrations
      • Scalability
      • High Availability
    • Day 4
      • AP Concepts Recap
      • EBS Adapter/AXF Overview
      • Invoice Solution Overview
      • Other Integration Options
  • 5. Agenda
    • Day 5
      • Product Installs
      • Solution Template Install
  • 6. Imaging Market Trends Decreasing Value of Point Imaging Systems
    • Application Imaging
    • Most imaging deployments are initiated by one LOB to decrease reliance on paper and automate processes
    • Their priority is to find the imaging solution that fits their operations, with seamless ERP integration
    • They like point systems that are designed to support only one department’s processes, but do it well
    • Enterprise Imaging
    • IT is brought in to evaluate technologies based upon LOB requirements
    • Their priority is to keep LOBs happy, while also ensuring that IT investments provide current and future value
    • They don’t like point systems because they are costlier to maintain and expand over time, and don’t fit with global IT strategy
    LINE OF BUSINESS GLOBAL IT SERVICES
  • 7. Imaging Requirements What organizations are looking for now Batch & Remote Capture Forms Recognition Imaging Viewer (Markups/Annot.) Packaged Solutions for ERPs Process Monitoring Application Imaging req’s Enterprise Imaging req’s Multi-tenancy Deployment COLD / ERM Management Print & Fax Platform-based ECM & BPM Productized, Open Integrations Business User Process Modeling LOWER COSTS IT MANAGEABILITY DEPARTMENTAL EFFICIENCY
  • 8. Oracle Imaging and Process Management I/PM 11g – from point to platform Batch & Remote Capture Forms Recognition Imaging Viewer (Markups/Annot.) Packaged Solutions for ERPs Process Monitoring Application Imaging req’s Enterprise Imaging req’s Multi-tenancy Deployment COLD / ERM Management Print & Fax Platform-based ECM & BPM Productized, Open Integrations Business User Process Modeling LOWER COSTS IT MANAGEABILITY DEPARTMENTAL EFFICIENCY I/PM 11 g
  • 9. Oracle Imaging and Process Management I/PM 11gR1 – Release Themes Batch & Remote Capture Forms Recognition Imaging Viewer (Markups/Annot.) Packaged Solutions for ERPs Process Monitoring Application Imaging req’s Enterprise Imaging req’s Multi-tenancy Deployment COLD / ERM Management Print & Fax Platform-based ECM & BPM Productized, Open Integrations Business User Process Modeling LOWER COSTS IT MANAGEABILITY DEPARTMENTAL EFFICIENCY I/PM 11 g
  • 10. Imaging and Process Management 11g 11gR1 Release Themes
    • Oracle IPM 11 g is the most complete, integrated and cost-effective platform for end-to-end management of document images within enterprise applications:
      • Complete:
        • Single-vendor, end-to-end document process automation – applications, capture, imaging and workflow
      • Integrated:
        • Out-of-the-box support for E-Business Suite, PeopleSoft– all on one platform
      • Cost-effective:
        • Reuses and extends IT infrastructure investments and skill sets in Applications and Middleware
        • Provides long term strategic value as the default imaging solution for Applications Unlimited and Fusion Applications
  • 11.
    • Support for more heterogeneous IT environments
      • Porting to Java and WLS
      • Broad directory support and SSO through FMW infrastructure
    • Leverage UCM services for metadata and document storage
    • Embedded workflow capability from Oracle BPM Suite
    • Integrations
      • URL tools and comprehensive web services
      • Updated application integration framework
    Imaging and Process Management 11g Technology Stack in IPM 11g
  • 12. Imaging and Process Management 11g Fusion Middleware Infrastructure Content IPM Config TopLink IPM Services IPM Public API ADF UI Layer Web Services Input Agent Input File Directory BPEL Injection BPEL Metadata UCM Repository BPEL Web Services IPM (WLS application) IPM Applet Viewer WLST MBeans OPSS LDAP Storage, Searching, Export, etc Security
  • 13.
    • Modernized user interface and new web-based administration UI
    • Fully translated and accessible
    • Viewer re-written as a Java applet with cross browser support
      • Leverages Outside In rendering technology
      • Simplified security model and improved usability
    Imaging and Process Management 11g UI Improvements
  • 14. Imaging 11g Roadmap Support for Enterprise Imaging
    • Other 10g missing features – not currently planned for 11g: distributed cache, embedded workflow, intelligent routing, windows client, DSMS,
  • 15.
    • Storage – Create Application
    • Retrieval – Define Search
    • Input – Configure Input Mapping
    • Re-use - Definition Import/Export
    • Capture - I/PM 11g Commit Driver
    Demonstration Agenda Configuring an Imaging Solution
  • 16.
    • Storage – Create Application
    • Retrieval – Define and Execute Search
    • Input – Configure Input Mapping
    • Re-use - Definition Import/Export
    • Capture - I/PM 11g Commit Driver
    Demonstration Configuring an Imaging Solution
  • 17. Feature: Application General Properties
    • An application models a collection of documents and their properties
      • Manage documents for different solutions, e.g. invoices vs claims, which have need different metadata and security
      • Manage related documents which have different security e.g. employee submitted documents vs employee appraisals
    • I/PM can be associated with multiple Content Servers for scalability
    • An application is configured to use a single Content Server
    If Content Server has been configured to use Oracle Text for search an I/PM application can take advantage of it for metadata searches. If this option isn’t selected, I/PM searching will be ignore any Oracle Text configuration
  • 18. Feature: Application Fields
    • An application can have any number of metadata fields
      • An application must have at least one field
      • Note - Number may be restricted by underlying Content Server and may require an additional Content Server
    IPM supports string, date, integer and decimal types. For each type the appropriate properties may be set. Fields can be marked as required, and indexed for faster searching. Making too many fields indexed can be detrimental to performance Defaults and pick lists can be specified if appropriate
  • 19.
    • Delegated security model enables administration to be separated from document access.
      • Document security is modeled in Content Server with a security group
      • Application security and annotation security are modeled in IPM
    Feature: Application Security Groups are retrieved from LDAP via OPSS. They are provisioned as UCM roles as necessary Specifies which users can grant other users access Application security is used to model the administrators of the application. Admins do not have access to documents in the application Document security controls user access to documents in the application
  • 20.
    • Leverages File Store Providers – allows admin to specify which file store provider is used for documents in each application
      • Note – web layout directory should be disabled for file store providers used by IPM applications
    Feature: Application Storage Supporting documents e.g. annotations can be stored in a different file store provider from the main documents e.g. WORM for documents but file system for supporting documents
  • 21.
    • Configure mapping between documents and BPEL processes
      • Can integrate with multiple BPEL servers and initiate any deployed SOA composite
    Feature: Application BPEL Integration
  • 22.
    • When processes are initiated IPM system and customer defined fields can be passed to process payload elements
      • The configuration UI inspects the BPEL process and provides a graphical tool to map between I/PM and BPEL fields
        • Note – the mapping tool only support simple XML types e.g. integer, string etc
      • Format values allows a combination of metadata fields and strings to be concatenated e.g. it could construct URLs like http://host:port/imaging?search=relatedDocs&ClaimNum=[ClaimNum]
    Feature: Application BPEL Integration
  • 23.
    • Storage – Create Application
    • Retrieval – Define and Execute Search
    • Input – Configure Input Mapping
    • Re-use - Definition Import/Export
    • Capture - I/PM 11g Commit Driver
    Demonstration Configuring an Imaging Solution
  • 24.
    • The search results are specified
      • Results from multiple applications can be unioned into a single search e.g. show HR documents and Appraisals
        • Note – A single search can return documents that may be stored in multiple content servers
    Feature: Search Search Results Specify the applications that should be searched and the fields to return Specify the name of the columns in the search results Map fields from different applications into the same column when appropriate Columns that only show fields from one app will be blank for docs from other apps
  • 25.
    • Flexible search builder allows complex, nested queries to be configured
    Feature: Search Query Criteria
  • 26.
    • Parameters can be prompted, fixed or derived based on field type e.g. date parameters can be relative
    Feature: Search Query Criteria
  • 27.
    • Searches relative to current date allow queries such as – show docs for employees who have already started work
    Feature: Search Query Criteria
  • 28.
    • Since IPM searches are unions a query must be specified for each application that is included in the search
    Feature: Search Query Criteria
  • 29.
    • To ‘join’ the search results you can specify that a single parameter should be passed into multiple queries
    Feature: Search Query Criteria
  • 30.
    • Specify what parameters are exposed to users when executing the search
    Feature: Search Search Parameters Note only one parameter is available as emp num was ‘mapped’ and hire date was derived Specify how the operand should be rendered in the search screen Specify additional search screen behavior – defaults, picklists, required parameters and non-editable fields
  • 31.
    • Security to control access to searches
      • Users can only access documents through searches so search security further controls document access
    Feature: Search Search Security
  • 32.
    • Browser based document viewer (leverages OIT)
      • Advanced viewer (Java applet plug-in)
      • Basic viewer( zero-foot print HTML viewer)
        • Document conversions/rendering occurs on the server
        • No annotations – redactions are burned into rendition
    • Advanced Viewer
      • Annotations – text, rectangles, lines, sticky, redactions, stamps
      • Document manipulations – rotation,
    Feature: Viewer
  • 33.
    • Annotations security options are controlled by the application – which groups can apply which type
    • Simple security model
      • Regular – all users with ‘regular’ permission can see/edit
      • Restricted – users must have ‘restricted’ permission to apply, all others cannot remove
        • Restricted annotations are ‘burned in’ for other users – can only download burned image of document
      • Hidden – users must have ‘hidden’ permission to edit/view
    Feature: Viewer Annotation Security Model
  • 34.
    • Scenario: Student Applications
      • Students have access to their documents but don’t need annotations – no annotation permission
        • Students should get the basic viewer by default
      • Admissions staff use annotations to comment on documents – only admissions staff have hidden annotation permission so others can’t see comments
      • Faculty advisors have access to student documents but shouldn’t see social security numbers – no annotation permission
        • Admissions staff have restricted annotation permission and apply redactions to hide sensitive info
    Feature: Viewer Annotation Security – contd
  • 35.
    • Storage – Create Application
    • Retrieval – Define Search
    • Input – Configure Input Mapping
    • Re-use - Definition Import/Export
    • Capture - I/PM 11g Commit Driver
    Demonstration Configuring an Imaging Solution
  • 36.
    • Scalable tool for uploading documents
      • Wizard based configuration UI for mapping from control file to I/PM fields.
      • Scalable message driven architecture – all server instances will process batches
    • Globalized
    • Support for commands e.g. locale,
    • Coming soon : Additional commands e.g. append page, add supporting doc
    • (Input Agent will be covered in more detail on Day 3)
    Feature: Input Mapping
  • 37.
    • Storage – Create Application
    • Retrieval – Define Search
    • Input – Configure Input Mapping
    • Re-use - Definition Import/Export
    • Capture - I/PM 11g Commit Driver
    Demonstration Configuring an Imaging Solution
  • 38.
    • Configurations exported in XML format
      • Move configurations across test/stage/production
      • Enable development of re-usable configurations
    • Designed to survive across product versions
    • Repair facility on import – missing users, UCM connection, BPEL connections etc
    • Coming soon : WLST command to import definitions to allow scripted configuration
    Feature: Definition Import/Export
  • 39. Feature: Application Integrations (AXF) Key Differences from AXF 10g
    • Integrated with IPM
      • Install, Config
      • Directory, SSO
      • BPEL connection
    • UI enhancements:
      • Integrated comments UI
      • Categorized task actions
    • Security – secured web services
    • (AXF will be covered in more detail on Day 4)
  • 40.
    • Storage – Create Application
    • Retrieval – Define Search
    • Input – Configure Input Mapping
    • Re-use - Definition Import/Export
    • Capture - I/PM 11g Commit Driver (covered during ODC lesson on Day 2)
    Demonstration Configuring an Imaging Solution
  • 41.
    • URM and IRM are enabled via global profile rules
    • To configure a basic association of a URM or IRM policy to all documents in an application
      • Create a profile rule that sets xLifeCycleId or xCategoryId (for URM) or xIRMProtection (for IRM)
        • Select ‘Is derived field’
        • Value must be a valid retention category/lifecycle or IRM context
          • Note – using an invalid value will prevent IPM from checking-in content
      • Associate this profile rule with the appropriate application’s profile
        • Note – updating an application through IPM e.g. changing the name or changing security will require the profile rules to be re-applied
    Feature: Application URM and IRM Integration
  • 42.
    • URL: http://coscontext.us.oracle.com:16000/imaging
    • Use IE 7, 8 or FireFox 3.5
    • Connect as userX/welcome1
    Hands-On Exercise Logistics
  • 43.
    • Create an HR Docs application
      • Fields: Employee Number, First Name, Last Name, Document Type (add a pick list to the Document Type field)
      • Grant the Administrators group all the documents permissions
      • Skip the BPEL configuration step
    • Upload a document to the HR Docs application
    • Create a search to return HR Docs by employee number
    • Execute the search and view the document
      • Try both advanced and basic viewers and apply annotations: sticky note, redaction
    • Note: Please add your username to all applications and searches you create e.g. HR Docs – User50
    Hands-On Exercise
  • 44.
    • Create a search that will return all appraisal documents and HR documents for an employee
      • Use the existing Appraisal application that has been created (you may need to upload some additional files to match your data)
    • Note: Please add your username to all objects you create e.g. HR Docs – User50
    Hands-On Exercise
  • 45. Agenda
    • Day 1
      • I/PM 11g Overview
        • I/PM 11g and UCM
      • AP Concepts and Solution Overview
      • Pre-Sales Enablement
  • 46.
    • Content Server 10g pre-requisites
      • ‘ CS10gR35CoreUpdate for IPM’ component is required
      • Upgrade default file store and define storage rules
        • Note: Disable the Weblayout for any file store provider used with I/PM content
      • Content Tracker is encouraged
    • Install IpmRepository component. This creates/configures:
      • Required IPM system fields – and global profile rules to group them and hide them by default
      • IPM document types
      • IPM repository admin user and role
      • Security groups to secure IPM system content – annotations and supporting documents
    IPM 11g and UCM Installation
  • 47.
    • The application fields are added to doc info table
    • Profile rules are created:
      • Group the application fields
      • Enforce defaults, required fields as configured in I/PM
      • Global rule to hide the app fields so they don’t show in unrelated profiles
    • A profile created to show just the fields related to this application
      • Shows IPM system fields, app specific fields, and enforces config
    • A security group is created with the grants corresponding to the groups that have been granted permission to the application
      • If necessary the underlying Content Server roles are created
    IPM 11g and UCM Application Definition