Alliance Maintenance Integration Process Claude SAAM / Yves GRILL / Denis SCHITTER 29/Feb/2008

Agenda 1.Environments / Infrastructure 2.Development Process 3.Web Integration Process 4.SQL Integration Process 5.Questions / Answers

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Environments / Infrastructure 1

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Environments Clearcase (1/2)  Alliance Maintenance  Located in COSET_PVOB  3 development streams, one for each location –Each location « owns » its stream so it can initiate delivers  1 pre_integration stream : Alliance_Merged_PreInt_Gre (was used at Grenoble) –This stream is used to consolidate developments & create patches –To be used by integration team only  1 integration stream Alliance_Merged_Int_Gre (not used any more) –Do not use it

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Environments Clearcase (2/2)  Alliance R1.1.1 Project  Located in COSET_PVOB  3 development streams, one for each location –Each location « owns » its stream so it can initiate delivers  1 integration stream –This stream is used to consolidate developments & create patches –To be used by integration team only

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Environments Infrastructure Servers (1/2)  Alliance Maintenance  Integration site hosted on Illmisvmw136  Urls available on Microsoft Integration Bookmarks page –Illkirch users : –Mumbai users : Aventail / Microsoft Integration Bookmarks  SQL Database (user coset / pass password): –Illkirch DEV : server FRILLS063453, database COSET_B2BFE & COSET_B2BUP –Illkirch INT : server FRILLD \ESALES, database COSET_R11_B2BFE & COSET_R11_B2BUP –Mumbai DEV : server in Mumbai, database COSET_B2BFE & COSET_B2BUP  One set of dev databases for each release

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Environments Infrastructure Servers (2/2)  Alliance R1.1.1 Project  Integration site hosted on Illmisvmw134  Urls available on Microsoft Integration Bookmarks page –Illkirch users : –Mumbai users : Aventail / Microsoft Integration Bookmarks  SQL Database (user coset / pass password): –Illkirch DEV : server FRILLD , database COSET_DEV_R11Next_B2BFE & COSET_DEV_R11Next_B2BUP –Illkirch INT : server FRILLD \ESALES, database COSET_R11Next_B2BFE & COSET_R11Next_B2BUP –Mumbai DEV : server in Mumbai, database COSET_DEV_R11Next_B2BFE & COSET_DEV_R11Next_B2BUP  One set of dev databases for each release

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Environments Build Environment  Cruise Control server : Illmisvmw157  Used by Integration team (for now)  Allows to build web patches in semi-automated mode, after clearcase delivery  If needed, patches are available in a windows share : –Alliance Maintenance : \\illmisvmw157\Build_Alliance_Maintenance\SMS\\illmisvmw157\Build_Alliance_Maintenance\SMS –Alliance Maintenance : \\illmisvmw157\Build_Alliance_1.1.1\SMS\\illmisvmw157\Build_Alliance_1.1.1\SMS  Access (Illkirch only) :

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Development Process 2

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Development Process Solution Set-Up  On local dev computer  Create a snapshot view on the appropriate development stream –Depends on geographical location  Setup local IIS web sites to match solution’s required web sites –AllianceFE : front end web site, port 80 – Home directory : Alcatel.OrderPrep.Coset.FrontEnd\Alcatel.OrderPrep.Coset.FrontEnd.Web – Virtual directory : FrontEndAuth, in Alcatel.OrderPrep.Coset.FrontEnd\Alcatel.OrderPrep.Coset.FrontEnd.WebAuthentication –AllianceUM : user management web site, port 90 – Home directory : Alcatel.OrderPrep.Coset.FrontEnd.UserProfiling\Alcatel.OrderPrep.Coset.FrontEnd.UserProfiling.Web – Virtual directory : Auth, in Alcatel.OrderPrep.Coset.FrontEnd.UserProfiling\Alcatel.OrderPrep.Coset.FrontEnd.UserProfiling.WebAuthentication –AllianceWS : webservice web site, port 85 – Home directory : Alcatel.OrderPrep.Coset.FrontEnd\Alcatel.OrderPrep.Coset.FrontEnd.WebService  In ‘Resources’, configure regsetup file to connect to the proper SQL Database  In ‘Resources’, configure regconfig file to use ‘Dummy’ Authentication (local XML file)  In ‘Solution’, open VS2005 solution file, compile & check dependencies  Detailed process to be explained by Anne Chin

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Development Process Use of Clearcase  Read Developer’s manual  Available at \\illbur10\DSIPDATA\E-Techno\Alliance\g - Support & Maintenance\Integration  In VS2005, check out required files for development (use contextual menus)  Create a Clearcase activity following manual recommendations to record checkouts –Must be named « _ » –One activity = a consistent set of changes to the code (DR fix, functional evolution, …) –Each activity will be delivered in its entirety to the Integration environment –Do not re-use an activity once it has been successfully delivered  Once a development is complete, check-in all the files belonging to the activity  Make an Integration Request to have the activity delivered to Integration environment

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Web Integration Process 3

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Web Integration Process Big Picture

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Web Integration Process  Integration Request : New Tool !  Sharepoint website :  Fields similar to the previous Notes Tool  Description of the fields: –Title : explicit description of the request –Solution : Alliance Maintenance or Project –Module : Web and/or SQL delivery –Integrators : Yves GRILL / Denis SCHITTER –Backup : Claude SAAM –Description : must include the name of the activity to deliver and also the list of SQL files. Use this field to specify special points (ex: other parameter value for Integration server or Pre-production server …) –Status : set to « Submitted to Integration »  User manual writing in progress, will be available W10  Should be available to Mumbai via Aventail soon

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Web Integration Process  Multi-Site Specifics  For Grenoble & Mumbai, additional steps are necessary : –Initiate a Clearcase deliver from Dev to default target –Send a clearcase synchronization if it cannot wait the next schedule – 9h30 : Mumbai + Illkirch -> Grenoble (10h) – 10h30 : Grenoble -> Mumbai + Illkirch (11h) – 13h30 : Mumbai + Illkirch -> Grenoble (14h) – 15h : Grenoble -> Mumbai + Illkirch (15h30)  After a delivery from one site, other sites dev streams will be updated to reflect the changes (clearcase rebase) –This activity is done automatically by Integration Team  Delivery Request Life-Cycle  Integration Team updates the integration request to reflect the progress of the integration (retrieved, testing, etc…)  A mail is sent automatically to the requestor once the delivery is available in integration

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 SQL Integration Process 4

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 SQL Integration Process  SQL best practices and Alcatel-Lucent programming standards  Available at Microsoft team sharepoint:  Integration Process  The SQL Scripts are tested and executed on integration server after received on clearcase integration stream (status = « retrieved »).  Only the scripts listed in Sharepoint Delivery Tool are part of the delivery.  Once integrated with success the Delivery status changes to « testing on integration ».  Post-production reports  After maintenance patches have reached production, they’re passed on Illkirch project servers (development and integration). The patches are then send to Mumbai via ftp in order to reflect the changes to the current project.  After a project release has gone to production the whole production databases backups are restored on Illkirch maintenance servers (development and integration). The backups are send to Mumbai via ftp in order to restore the maintenance databases and create the next release integration server.

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 SQL Integration Process  Parameters  Some solution parameters are put into sql tables (SITE_PARAMETERS table for Alliance). In source control, the parameter values should be the production ones. In order to change these in Integration and Pre-production servers (if needed), the alternate values must be writen in the Sharepoint Delivery Tool (description field).  Content data  Scripts that only affects data (INSERT, DELETE, UPDATE) can be executed directly on integration server and send to Pre-production and Production using Alcatel-Lucent’s OPS tool:  These scripts must reside on Source control and a request must be made using Sharepoint Delivery Tool for tracing purpose.  Use this method only if needed (recurrent data update or urgent action).

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Questions / Answers 5

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb 2008 Question / Answers

All Rights Reserved © Alcatel-Lucent | Alliance Integration | Feb