FlexDeploy Product Technical Overview
- 2. 2 Challenges with Software Delivery Too costly, slow, error prone, and high risk Cost • Manual activities are very costly • Creating & maintaining environment and scripts • Outages in test and production environments Speed • Delays for environment provisioning/setup • Slow deployment and release, impacting test cycle times • Time spent troubleshooting issues vs. ‘productive work’ Quality • Poor Visibility to what, when, who, how • Lack of Controls lead to compliance issues & failed audits • Increased Risk for quality delivery
- 3. 3 Comprehensive, Integrated, Open Note: FlexDeploy runs on premises or cloud
- 4. 4 Improvements Realized Higher quality software faster, with less cost and risk Cost • Eliminate manual activities and scripts • Reduce or eliminating outages in test and production • Utilize resources for value-add activities Speed • Quickly provision and access environments • Rapid deployment of changes; faster feedback cycles • Eliminate time spent troubleshooting issues and outages Quality • Visibility to what, when, who, how • Easily respond to compliance and audit requirements • Risk reduction via consistent and repeatable processes
- 5. 5 Features across the toolchain Automation • Topology Management • Graphical Workflow Design • Workflow Execution • Build/Package Management • Continuous Integration • Provisioning & Configuration • Artifact Repository • Deployment/Release Automation • 3rd Party Plugins & Integrations • Test Automation Framework • Integration via REST APIs • Plugin SDK Controls • Role-based Security • Environment Modeling • Application Management • Project Management • Approvals • Scheduling • Deployment Windows • Issue/Change Integration • Pipeline Management Visibility • Dashboards • Reports • Notifications • Test View • Logs View
- 6. 6
- 7. 7 FlexDeploy Differentiators • Comprehensive and Integrated Solution – Provisioning and Configuration Management – Build and Continuous Integration Automation – Artifact Repository – Deployment Automation – Test Automation – Dashboards and Reports • Oracle Plugins and Integrations – Fusion Middleware: WebLogic, SOA, OSB, B2B, BPM, ODI, MFT – Fusion Middleware: WebCenter, OBIEE, Application Test Suite – Database & Developer: Oracle DB, JDeveloper, ADF, APEX, Forms – Applications: E-Business Suite, SaaS Extensions, Salesforce – Cloud IaaS: Compute, Storage, Network – Cloud PaaS: Database, Java, SOA, Application Container
- 8. 8 Software Delivery Process • Environments have a designated purpose and controls
- 9. 9
- 10. 10 FlexDeploy Topology • Topology resembles software delivery environments – FlexDeploy Administrator configures topology in FlexDeploy – Middleware Administrator configures various properties – Operations team can control approval and schedules – Developers can submit code deployment requests
- 11. 11 Topology - Environments • Represents Environments defined in Software Delivery Process
- 12. 12
- 13. 13 Topology - Instances • Logically represents Technology (Applications, Middleware etc.) running in various environments
- 14. 14
- 15. 15 Environment Instances • Represents Build or Deployment Target
- 16. 16
- 17. 17 Topology - Endpoints • Represent connection to VM or Physical Server (SSH) – Need Cygwin for Windows servers
- 18. 18
- 19. 19 Topology Configurations • Environments – Define to match Physical Environments • Instance – Logical name for each Technology – Map to Environments – Map plugin operations that will execute (WebLogic – deploy, WebLogic – managedWebLogicStart etc.) • Endpoints – SSH connection to target server • Environment Instance – Configure properties like URL, User, Password etc. – Map various endpoints
- 20. 20 Workflow • Steps that define build or deployment process – Export or checkout source – Compile code – Deploy EAR – Deploy OSB – Stop Server – Start Server • Types – Build or Deploy • Graphical Editor with drag and drop • Use pre-built plugin operation in most case • Utilize generic plugins like Shell, Groovy, WLST when necessary, even using Plugin SDK for custom plugins
- 21. 21
- 22. 22 Projects • Project is for deployment artifact – EAR – WAR – SOA Composite SAR – OSB Jar – SQL files – Configuration Files • Project defines – Build and Deploy Workflow – SCM details – Code Streams (branch)
- 23. 23
- 24. 24 Project Build - Deploy • Developers commit code to SCM • Manual, Schedule or CI to initiate Build workflow – FlexDeploy runs Build workflow and creates new Project Version – Saves artifacts in Artifact Repository • Developers can deploy Project Version to one or more environments – FlexDeploy runs Deploy workflow and updates current state
- 25. 25
- 26. 26 Folders & Applications • Application can contain one or more Projects. – Build and Deploy can be executed on Applications as well • Folders can contain Folders and/or Applications • Approvals and Deployment Window configurations are done on Folder and/or Applications • Finer grained Security configurations are done on Folder/Application/Project tree
- 28. 28
- 29. 29 Q&A