System Setup
1 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights rese...
2 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also re...
3 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also re...
4
CI – Corporate IT
Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights...
5 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also re...
6 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also re...
7 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also re...
8 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also re...
9 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also re...
10 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
11 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
12 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
13 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
14 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
15 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
16 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
17 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
18 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
19 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
20 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also r...
Upcoming SlideShare
Loading in …5
×

Daniel Glueck - How Bosch develops for IBM Connections

1,924 views

Published on

The session will give a technical overview about the deployment of IBM Connections at Bosch. It covers information about the infrastructure of IBM Connections, the development process and used tools. A live demonstration of the build and deploy process will be given.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,924
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Daniel Glueck - How Bosch develops for IBM Connections

  1. 1. System Setup 1 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. How Bosch develops for IBM Connections June 28th 2013, Daniel Glück, Developer Corporate IT Sector
  2. 2. 2 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Bosch: a global network Four business sectors Energy and Building Technology Industrial Technology Automotive Technology Consumer Goods
  3. 3. 3 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Bosch: four business sectors 2012 key figures  World's largest supplier of cutting-edge automotive technology Industrial Technology Consumer Goods Bosch Group Automotive Technology  World's leading manufacturer of large gearboxes, drive and control, packaging, and process technology  World's largest power tool manufacturer  Leading the field in household appliances 59 % share of sales 41 % share of sales Energy and Building Technology  Leading manufacturer of thermo-, solar- and building security technology  World‘s largest supplier of heat pumps  52.5 billion euros in sales  306,000 associates including 42,800 in research and development  264 manufacturing sites
  4. 4. 4 CI – Corporate IT Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. CI Presentation Automotive Technology Industrial Technology Consumer Goods Corporate Sector for Information Systems and Services Energy & Building Technology
  5. 5. 5 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. IBM Connections at Bosch General information  Bosch Connect is the only internal social software platform at Bosch  35.000 Bosch users have access as of June 2013  Very good system performance and decent stability, but lots of tuning and tweaking needed to get there  Timeline  07/2013: Upgrade to IBM Connections 4.5 CR1  09/2013: Bosch Connect to be opened to all 220.000 Bosch users  1st half of 2014: Upgrade to IBM Connections ‘Next’
  6. 6. 6 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. System Setup Development Systems (D) Integration System (I) Quality Assurance System (Q) Productive System (P) D-1 D-2 D-N I Q1 Q2 “current” “next” P1 P2 “current” “next” I- and Q Systems have “nearly” the same setup like the productive system Developer commits finished implementations Release a build SoP: Activate P2 as the “current” system
  7. 7. 7 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Product Setup Completely scripted  With IC45 the setup of IBM Connections fully scripted  Product setup (Installation of WAS, Connections) including post- configuration (generate Webserver-Plugin, Security-Roles, Certificates etc.) is fully automated for IC45  Scripts can be used for IC5 and all future versions  Parameterized with environment settings iim_repos_basepath=D:IBMInstallationFiles iim_shared=D:IMShared iim_install_root=D:InstallationManager was_install_root=D:WebSphereAppServer plugins_install_root=D:WebSpherePlugins cellName=SomeCell ihs_nodeName=SomeNodeIHS01 ic_install_root=D:Connections ic_admin=foo ic_admin_password=bar …
  8. 8. 8 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Plan a release Release Management  Issue tracking and release management with JIRA  Versioning with Subversion  Release Process 1. We define a release date an plan backwards what we can achieve in the time-frame (at least 3 weeks) 2. We pick requirements/bugs from our backlog which shall be included in the release and implement/test them until Code- Freeze (ca. 1 week before release) 3. ca. 1 Week of testing on Q-System (automated & manual) 4. Release approval? Within an announced downtime we deploy the changes and restart the servers of our P-system Footer represents Version-Build information
  9. 9. 9 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Build a release Build (1)  Build is based on Ant  Files to be deployed contain placeholders (e.g. @interService.href.address@) which are replaced during build and / or deploy Build a release <sloc:href> <sloc:hrefPathPrefix>/activities</sloc:hrefPathPrefix> <sloc:static href="@static.href.protocol@://@static.href.address@" ssl_href="@static.sslHref.protocol@://@static.href.address@"/> <sloc:interService href="@interService.href.protocol@://@interService.href.address@"/> </sloc:href> </sloc:serviceReference>
  10. 10. 10 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Build a release Build (2)  Every release has a release_<version>.properties file which defines the content of the release. Scopes can be defined e.g.  release.complete=yes  release.connections.<application>.config=yes  release.feature.someFeature=no  Based on the scopes the required WAS restarts are determined  Output of the build is a zip-Archive which can be deployed to all environments  <env>_env.properties: Defines the environment specific settings  targetbuild.properties: Contains the global and environment specific values for the placeholders which are replaced during deploy
  11. 11. 11 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Build a release Example build zip-Archive release.connections.application.news.config=yes release.any.application.config=true restart.news.cluster=true release.properties restart.properties @scheduledTasks.EmailDigestDelivery.scope@ = cluster targetbuild.properties target.customization.dir = pathtoIC_data target.httpserver.list=pathtows1,pathtows2 target.as.session.cookieName = SESSIONID-Q q_env.properties
  12. 12. 12 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Deploy a release Deploy (1)  Deploy script is based on Ant  During runtime the environment specific placeholders are replaced  Backup of files before they are overwritten  Deploy is split into deploy_content and deploy_websphere because of different access rights to Dmgr, Fileshare and Webservers “Change-Server” deploy.xml deployContent deployWebSphere - IC_Data customizations - Webserver (htdocs, conf) Target: <dev-system>, i, q, p Path to Build-archive file DMGR-hostname, user, password - LCC config - WebSphere config - Application deployment - Restarts
  13. 13. 13 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Deploy a release Deploy (2)  Usage of the wsadminThinClient to perform wsadmin commands from ant during deploy  The deploy Script is shipped as “Deploy-Tool” and can be executed everywhere where access rights to the Dmgr are available <exec executable="${deploy.wsadmin.dir}/wsadmin.bat" dir="${deploy.wsadmin.dir}" resultproperty="wsadminResult" timeout="600000"> <arg value="${dmgr.host}" /> <arg value="${dmgr.port}" /> <arg value="${wsadmin.username}" /> <arg value="${wsadmin.password}" /> <arg value="${deploy.wsadmin.lang}" /> <arg value='"${tmp.scripts.dir}/${pythonscript}"' /> <arg value='"${tmp.propertyfile}"' /> </exec>
  14. 14. 14 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Developing, Tooling General overview about our developments  Tooling: Eclipse, RSA, Ant, Subversion, yui-compressor, ivy, wsadminThinClient  Coding-Guidelines: Checked with Eclipse-Plugins, Sonar  Continuous-Integration: Jenkins, Test-Automation  So far we developed  Community widget which embeds an internal system (with JS)  A build & deploy system for a stable release process  Prototype Servlet returning a specific Blogs Post  Upcoming developments:  A lot of integrations of / into other systems  Integration of Third-Party extensions  Framework evaluation for server-side implementations
  15. 15. 15 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Developing, customizing Our development workflows  For customization / htdocs adjustments  Files are edited directly  reload browser  For config / strings etc.  Files edited within eclipse  Usage of build & deploy scripts with dynamically generated release.properties  For websphere-config (Jython) scripts  Usage of Ant scripts to test the Jython-scripts  Once a day we build & deploy our Dev-System via Jenkins with the corresponding release_<version>.properties file to test if the changes will work if they are deployed to I-System in the nightly build
  16. 16. 16 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Developing, Continuous Integration D-1 D-2 D-N I Jenkins Manual build & deploy to development systems when needed Nightly build & deploy incl. Regression tests “potentially shippable” release build each night
  17. 17. 17 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Live-Demo
  18. 18. 18 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Summary Recommendations  Setup a development environment for each developer  Use Continuous integration tools such as Jenkins and Regression tests  Don‘t do anything „by hand“ – you can script everything 
  19. 19. 19 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Questions?
  20. 20. 20 Daniel Glück, Robert Bosch GmbH - Corporate IT | June 28th 2013 | © Robert Bosch GmbH 2013. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Thank you for your attention.

×