Faster and Safer of WebSphere Portal Environments at Daimler with IBM Auto Deploy

Transcription

1 Faster and Safer of WebSphere Portal Environments at Daimler with IBM Auto Deploy Andre Hagemeier, IT Specialist WebSphere Portal and IBM Connections

2 Please Note IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. 2

3 Andre Hagemeier IT Specialist for WebSphere Portal & IBM Connections JEE development, migration, integration, architecture, automation 3

4 Agenda Agile Development and Continuous Delivery Bridging the Gap What is Autodeploy? Features Customer Experiences 24/7h Golden Topology Support 4

5 Agile Development and Continuous Delivery Rapidly Changing Markets Require Fast Adoption of Processes as well as of the Software Supporting these Processes 5

6 Agile Development and Continuous Delivery Continuous Development Requires Quick Adaptation to Changing Market Demands In our Scrum team, we need to be able to deploy a new release every two weeks Our operations processes only allow one deployment every quarter Tom, software developer Gil, operator 6

7 Agile Development and Continuous Delivery Continuous Development Requires Quick Adaptation to Changing Market Demands We need to be able to reprioritize our requirements at the beginning of each Sprint Jack, scrum master We need a long time to plan and prepare for a deployment. We can't just deploy custom binaries and configurations at short notice. Gil, operator 7

8 Agile Development and Continuous Delivery Continuous Development Requires Quick Adaptation to Changing Market Demands My developers must continue to develop for the next sprint. They have no time to support the deployment. We're shipping self-contained releases anyway. Deploying these should work without our participation. Jack, scrum master Tom, software developer We need to know what configurations need to be changed and how to deploy the artifacts, though. Gil, operator 8

9 Bridging the Gap Autodeploy Helps Bridging the Gap between Continuous Development and Continuous Delivery 9

10 Bridging the Gap Autodeploy Helps Bridging the Gap between Continuous Development and Continuous Delivery 10

11 What is Autodeploy? Autodeploy allows your system administrators to concentrate on the complex what instead of the timeconsuming how supports any WebSphere Application Server environment: WebSphere Portal WebContent Manager IBM Connections, etc.. install custom components 11

12 What is Autodeploy? Autodeploy allows your system administrators to concentrate on the complex what instead of the timeconsuming how configure and administer the whole WebSphere Application Server environment from one interface deploys releases about 20-times faster than the manual way less error-prone through standarized, automated deployments 12

13 What is Autodeploy? Autodeploy allows your system administrators to concentrate on the complex what instead of the timeconsuming how troubleshooting support throughout all servers of the cell deploy and rollback a two-line golden topology with fade in/out Have your developers manage the dependencies between their releases on their own 13

14 What is Autodeploy? Autodeploy is Capable of Deploying Self-contained Release Archives in a Multi-stage Environment in an Automated and Reliable Manner. Any build system (Manual, Ant, Maven, Jenkins, Autodeploy Release builder) Engineers WebSphere Cell Stage-independent Archive Infrastructure Configuration Deployment Manager Stage-dependent Archives Application Servers Software developers Cell isolation Deployment Validation Deployment Execution Operator Portal Servers Web Servers 14

15 Features Core Features Cell isolation, backup, restore, Golden topology support Separation between stage-dependent and stage-independent data Transparent scope mapping Delta calculation between consecutive deployments Significant reduction of scope-restarts Full encryption of all passwords based on public keys Flexibility to integrate with build, monitoring, or other automation systems, e.g. Chef, Jenkins, IBM UrbanCode Deploy etc. 15

16 Features Core Features Dynamic Maven-like property-replacement mechanism Dependency definition between components Self-contained releases Easy extensibility 16

17 Features Roadmap Initial Release WebSphere Application Server WebSphere Portal Server 6 - Golden Topology - countless features - WebSphere Application Server 7, 8 - WebSphere Portal Server 7, 8 - more features - WebSphere Application Server WebSphere Portal Server AIX support - more features - WebSphere Application Server Liberty - IBM Connections 5 - Windows support - more features planned 17

18 Features Full Support of WebSphere Application Server and WebSphere Portal WebSphere Application Server 6, 7, 8, 8.5 WebSphere Portal 6, 7, 8, EARs, WARs - shared libraries - JBDC provider, datasources - workmanagers, schedulers - JVM settings - arbitrary filesets and script execution - WebContainer & timeout settings - servlet-caches & object-caches - LDAP, VMM, TAI configuration - threadpools - websphere variables - property sets - virtual portals, xmlaccess, pzn -. 18

19 Customer example How Autodeploy Helped Daimler Reduce the Complexity and Execution Time of their Deployment and Increased its Reliability. Standard deployment times: 90min Full Autodeploy deployment: 15min Diff Autodeploy deployment: 5min Many more features (WAS) Property encryption Cellmanagement (collecting logs, start, stop, restart, etc.) Deploymentmanagement (DU history, backup, restore) 19

20 Continuous delivery and 24/7 availability Autodeploy Fully Supports Golden Topologies Including Line-wise Deployments and Rollback Scenarios Web Portal Line A Load balancer Auth Line A Web Portal Line B Auth Line B content data config 20

21 Continuous delivery and 24/7 availability In prefer-b mode, the Remaining Sessions on Line A Will Be Maintained until They Terminate. All New Sessions Will Be Opened on Line B Web Portal Line A Load balancer Auth Line A Web Portal Line B Auth Line B content data config 21

22 Continuous delivery and 24/7 availability In Only-B mode, All Requests are Dispatched to Line B. Line A is Ready for Maintenance and Deployment. Web Portal Line A Load balancer Auth Line A Web Portal Line B Auth Line B content data config 22

23 Continuous delivery and 24/7 availability After the Deployment and Testing on Line A, the Mode is Switched to Prefer-A. All New Sessions will be Opened on Line A. Web Portal Line A Load balancer Auth Line A Web Portal Line B Auth Line B content data config 23

24 Continuous delivery and 24/7 availability In Only-A mode, All Requests are Dispatched to Line A. Line B is Ready for Maintenance and Deployment. Web Portal Line A Load balancer Auth Line A Web Portal Line B Auth Line B content data config 24

25 Continuous delivery and 24/7 availability After Line B has been Deployed and Tested, the Balanced Mode can be Reactivated and the Requests will be Equally Dispatched between both lines. Web Portal Line A Load balancer Auth Line A Web Portal Line B Auth Line B content data config 25

26 Backup slides Backup slides - EARs, WARs, Portlets - class loader order, startup weight, proxy settings - WebService client bindings - Shared Libraries (cell, node, server, cluster scope) - JDBC Provider, DataSources, J2C Entries - Resource Environment Provider - JVM Custom Properties, WebSphere Variables - Servlet / Object Cache - Security - KeyStores, SSL,Dynamic Outbound EndPoint - TAI, VMM, JAAS Login Modules - Scheduler, Workmanager - XML Access - Arbitrary File Sets 26

27 For Additional Information 2014 IBM Corporation 27

28 For Additional Information IBM Digital Experience Solutions WebSphere Portal and IBM Web Content Manager Information Center Wiki IBM Digital Experience Demonstrations: IBM Digital Experience Developer: IBM Collaboration Services Business Solutions Catalog IBM Corporation 28