E framework overview

Uploaded on


More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Enkitec eFrameworkEnterprise Edition1
  • 2. WELCOME2
  • 3. About Enkitec— Oracle Platinum Partner— Established in 2004— Headquartered in Dallas, TX— Locations throughout the US & EMEA— Specialties include— Exadata Implementations— Development Services— PL/SQL / Java / APEX— DBA/Data Warehouse/RAC— Business Intelligence3
  • 4. Agenda— Overview— eFramework— Licensing4
  • 5. OVERVIEW5
  • 7. Problem: User & Role Management7— Multiple user repositories— Different applications manage roles differently— Or not at all...— Lack of auditing when managing and/or assigningroles— Especially in home-grown systems— No central view of what applications & roles asingle user has access to
  • 8. Problem: Too Much Access8— APEX instance administration console gives a usercomplete access to the instance— Users with access to this can:— Create or Delete Workspaces— Create or Delete Schemas— Assign a Developer to Any Workspace— Alter the instance options andsecurity settings— Approve Requests— Monitor Usage— Deploying in Runtime Mode makes even this optionunusable
  • 9. Problem: Not Enough Access9— On the other hand, there are several commonlyneeded management features that are notavailable from the APEX admin console— Enable/Disable an Application— Secure Pages with Roles— Manage Application Help— View Errors— View Feedback— Alter Log Retention Period
  • 11. Solution: Enkitec eFramework11— The Enkitec eFramework is an APEX-basedplatform for deploying, managing & monitoringmultiple APEX applications— Provides a central Management & Monitoringconsole that can be discretely delegated to anyuser— On either an application or workspace basis
  • 12. Requirements— APEX 4.1 & 4.2— Oracle Database 10gR2 or later— SE One, SE or EE12
  • 13. How it Integrates— eFramework provides a set of APIs that can easilyand non-intrusively be integrated into existingAPEX applications— Configuration Typically less than 5 minutes per application— Built-in Verification Tool to assist with integration13• Application Item• Page Zero Region• Error Handling Call• Authentication Scheme• Authorization Scheme(s)• PL/SQL Init & Cleanup• Navigation Bar Entries• Label Templates
  • 14. eFrameworkHow its Configured14Administration ManagementManage Application 100,101 & 102Monitor all Applications in Workspace PRODManage Help Text in Application 100Equivalent to APEX Instance AdministratorCustomer Applications
  • 15. eFramework DomainHow it Works15Launchpad Customer ApplicationsRepository
  • 16. Key Features— User Repository Integration— Discrete user-to-app or user-to-workspacemanagement— Role Management— Page Security— Centralized Help— Monitoring Reports & Charts— Error Management— Auditing— Application Control16
  • 17. Enkitec eFramework17— The Enkitec eFramework is an APEX-basedplatform for deploying, managing & monitoringmultiple APEX applications— Support for APEX 4.1 & 4.2— Oracle Database 10gR2 or later— Provides a set of APIs that can easily and non-intrusivelybe integrated into existing APEX applications— Typically less than 5 minutes per application
  • 18. Key Features— User Repository Integration— Discrete user-to-app management— Role Management— Page Security— Centralized Help— Monitoring Reports & Charts— Error Management— Auditing— Application Control18
  • 19. User Repository Integration— eFramework can be configured to work withvirtually any user repository— LDAP, Active Directory, Oracle eBusiness Suite, Custom— Comes configured with built-in repository— Once integrated, a local copy of Users will beinstalled in an eFramework view— Authentication still occurs at the user repository source19
  • 20. Discrete User-to-App Management— Application Management & Monitoring can bediscretely configured on a per-user basis basedon a role or roles— Examples:— User A can manage all applications in Workspace A— User B can manage Application 100 in Workspace A andApplication 200 in Workspace B— User C can edit help in Application 100 in Workspace A20
  • 21. Role Management— Each application can have its own set of roles— Users from the corresponding repository are then mapped tothese roles— Roles are Hierarchal in Nature— Users will automatically inherit roles below their assigned roles— Role Assignments contain Start & End Dates— Allowing for temporary assignment of users to roles— Easy to use API can be added to an application’sAuthorization Scheme— RETURN SV_FWK_ROLES_API.is_member(p_role_key => PRODUCTS);21
  • 22. Page Security— eFramework allows an application manager tocontrol which role is required for which page— No need for an authorization scheme per page per role— Can all be managed from within the eFramework tool22
  • 23. Centralized Help— APEX embedded help is difficult to manage— Must give a non-technical person access to the builder— Changes require an application to be re-deployed— eFramework provides a centralized Help utility— Create content— Associate the content with multiple components— Pages, Regions or Items— Minimal changes required to APEX item templates23
  • 24. Monitoring Reports & Charts— Several reports & charts used to monitor theusage of applications— Page views by application, user, day, hour— Ability to automatically preserve APEX logsindefinitely— Done on a per-app basis24
  • 25. Error Management— eFramework provides an Error Managementfacility that integrates with APEX’s built-in errormanagement— Can be called either directly from APEX orindirectly from an existing APEX ErrorManagement function— Managers can add errors and messages in realtime from the eFramework tool— No need to access the development environment25
  • 26. Auditing— eFramework will audit all changes made withinthe tool— Application Settings— Users— Roles— Pages— Help26
  • 27. Application Control— Application Managers can control severalapplication attributes in real-time, withoutneeding access to the development environment— Availability— Message— Redirect to URL— Message— Log Retention— Session Duration— Session Idle Time27
  • 29. Demonstration29— Configuring eFramework from Start to Finish— Create a Domain— Create Mangers— Add Applications to a Domain— Create & Assign Roles— Create & Assign Help— Integrate Applications with eFramework
  • 30. Create a Domain— A domain is a mapping of a User Repository to aWorkspace— Can create as many Domains as required30WorkspaceDomainRepository
  • 31. Create Managers— Managers can be mapped to a specific Applicationor an entire Workspace— Discrete privileges can be assigned at either level31DomainManage All of Workspace ABCManage All of Application 101Manage Help in Application 101
  • 32. Add Applications to a Domain— Next, add applications from the Workspace tothe Domain— Each Domain will have its own Launchpad application— Once authenticated to the Domain, navigation betweenDomain Applications will be seamless32DomainApp 101 App 102 Launchpad
  • 33. Create & Assign Roles— Create Roles for each application and then assignusers to roles— Roles are hierarchal and will be automatically inherited— Assignments can have a start and end date33AdminCustomersProductsOrdersScottDougTimJorgeRoles Users
  • 34. Integrate Apps with eFramework— Ensure that your application has the requiredeFramework Components installed— Minimal, non-intrusive components must be added to yourapplications— Typically takes less than 5 minutes to complete— Use the Configuration Assistant to assist34
  • 35. Create & Assign Help— Create Help Content and associate it with items,regions and pages— One piece of Help Content can be associated withmultiple APEX components - items, regions or pages— Existing embedded APEX help can easily be imported35Help Content APEX Components
  • 36. LICENSING36
  • 37. Summary37— eFramework provides a robust development,management & monitoring platform for multipleAPEX applications— Can be integrated with any user repository— Provides a federated view of all APEX application activityand associated access controls— Simple to integrate with existing APEX applications
  • 38. eFramework Statement of Direction— Additional Reports & Analytics— Integration with eSERT— Alerts— Enhanced Auditing Capabilities38
  • 39. — Per “Production Stream”— Up to 4 instances of APEX in a Production instance of APEX— Any Number of Workspaces/Applications/UsersLicensing39DEV QA ProductionTEST
  • 40. Want More Details?— Contact us for details & pricing— sales@enkitec.com— +1 972 607 3751— http://www.enkitec.com40
  • 41. http://www.enkitec.com41