1 / 24

Common Component Concept Presentation DENK 2010

Common Component Concept Presentation DENK 2010. Daniel Friedrich First Data Deutschland CCM Administration 03/15/2010. Agenda Common Component Concept – Presentation DENK 2010. First Data – Quick Introduction. 1. 2. CCM at First Data Germany. 3. Common Component Concept.

flint
Download Presentation

Common Component Concept Presentation DENK 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Common Component Concept Presentation DENK 2010 Daniel Friedrich First Data Deutschland CCM Administration 03/15/2010

  2. AgendaCommon Component Concept – Presentation DENK 2010 First Data – Quick Introduction 1 2 CCM at First Data Germany 3 Common Component Concept

  3. First Data – Quick IntroductionCommon Component Concept – Presentation DENK 2010 First Data Facts First Data powers the global economy using virtually any form of electronic payment. First Data Deutschland GmbH, head office in Bad Vilbel. First Data, headquarter in Atlanta, Georgia. In Europe First Data is located in 22 countries. Number of employees 26.600 world wide, 700 in Germany. First Data is ranked No. 1 for the Financial Data Services Industry on the Fortune 500 list in 2007, 2008 and 2009.

  4. First Data – Quick IntroductionCommon Component Concept – Presentation DENK 2010

  5. AgendaCommon Component Concept – Presentation DENK 2010 First Data – Quick Introduction 1 2 CCM at First Data Germany 3 Common Component Concept

  6. CCM at First Data GermanyCommon Component Concept – Presentation DENK 2010

  7. System APP2 System APP1 System APP3 Subsystem Subsystem Subsystem Type Type Type PG PG PG Out1 Out2 Out1 Out2 Out2 Out2 CCM at First Data GermanyCommon Component Concept – Presentation DENK 2010 Application Systems in Environment ENV1

  8. CCM at First Data GermanyCommon Component Concept – Presentation DENK 2010 Endevor Systems Application 1 Application 2 Tools / Functionality within the Application Date- & Time Functions Date- & Time Functions Protocol Functions Conversion Functions Separate Output Libraries LOADs, COPYs LOADs, COPYs LOADs, COPYs LOADs, COPYs

  9. AgendaCommon Component Concept – Presentation DENK 2010 First Data – Quick Introduction 1 2 CCM at First Data Germany 3 Common Component Concept

  10. DefinitionCommon Component Concept – Presentation DENK 2010 Critical factors/ Requirements Central functionalities, bundled as tools, are developed and maintained redundant. These tools are accessible for each system. Tools contains site specific Know How and the source has to be protected. Release migration is separated between different application systems. No Solution: common libraries. Impact to all related systems and releases. Bad maintenance, high costs and high risks.

  11. Endevor Systems New System ‘GCOM’ Tools / Functionality within the Application Date- & Time Functions Protocol Functions Conversion Functions DefinitionCommon Component Concept – Presentation DENK 2010 Separate Output Libraries LOADs, COPYs LOADs, COPYs LOADs, COPYs

  12. DefinitionCommon Component Concept – Presentation DENK 2010 “GCOM – What is it?” New System in site architecture to bundle central functionalities and offers them for other applicative systems. GCOM stands for "Common Component System”. GCOM is a separate system for tools and applications that can be used by multiple application systems. The various tools and functionalities in GCOM are divided by subsystems. Responsible persons only have access to system GCOM. The ownership is connected to a technical department.

  13. DefinitionCommon Component Concept – Presentation DENK 2010 New System ‘GCOM’ Application 1 Application 2 Date- & Time Functions Date- & Time Functions Date- & Time Functions Protocol Functions Protocol Functions Conversion Functions Conversion Functions LOADs, COPYs LOADs, COPYs (COPY) LOADs, COPYs (COPY) LOADs, COPYs LOADs, COPYs (COPY) LOADs, COPYs LOADs, COPYs (COPY) Endevor Systems Tools / Functionality within the Application Separate Output Libraries

  14. ENV1 System: GCOM Subsystem: DATETIME Type: PGMBCOB PG: COB LOAD LIST DefinitionCommon Component Concept – Presentation DENK 2010 Development in GCOM Element name: FEIERTAG

  15. DefinitionCommon Component Concept – Presentation DENK 2010 Development in GCOM GCOM has its own software lifecycle. Elements are developed and transformed in GCOM. The common types and respectively the common conversion techniques (processors) are used. Responsible persons coordinate the development in GCOM and the announcement of the functionalities to the application systems. Application systems can access to GCOM output libraries via Endevor processors.

  16. ENV1 System: GAPP1 Subsystem: COMMON Type: PGMBLOAD PG: CPY LOAD (copiedfrom GCOM) (new) LIST DefinitionCommon Component Concept – Presentation DENK 2010 Create functionality in application system Element name: FEIERTAG

  17. DefinitionCommon Component Concept – Presentation DENK 2010 Create functionality in application system In application systems elements are created with identical names. The GCOM elements in the application system are called “common elements”. The distinction between common elements in the application and the other application elements is done via subsystem. The element source has no impact to the element processing. Standard migration/ processes, e.g. Release migration. When transforming, the LOAD module is copiedfrom the GCOM libraries along the map to the application systems output library.

  18. GCOMElement Key ENV: GPP SYS: GCOM SUB: DATETIME ELM: FEIERTAG Processing GCOMCommon Component Concept – Presentation DENK 2010 GCOMSource Code IDENTIFICATION DIVISION PROGRAM-ID XXBCOB. ENVIRONMENT DIVISION. Common Element Key ENV: GPP SYS: GAPP1 SUB: COMMON ELM: FEIERTAG Common Element Source Code - THIS ELEMENT IS POINTERED TO A COMMON COMPONENT ENTITY -

  19. FEIERTAG LOAD CCM Environment DEVELOP DEVELOP TEST TEST PROD PROD Common element in Application FEIERTAG Processing GCOMCommon Component Concept – Presentation DENK 2010 CCM Environment GCOMelement and output library LOAD (copy)

  20. Processing GCOMCommon Component Concept – Presentation DENK 2010 Processing GCOM entities in application system Supported types are programs (+/- DB2) and copybooks.Common elements are processed with it’s own processor. Step GETLOAD calls BSTCOPY to copy the LOAD module fromthe GCOM output library to the applications system output library. Endevor R12 feature ALLOC=LMAP is used to determine the input library in system GCOM. The footprinted GCOM LOAD module is input component in the component list of the common elements. Same footprint process is valid for copybooks. Therefore, common copybook elements have input components.

  21. Centralized functionalities and tools Separation of source and output libraries Security aspect , source code protection Avoid redundancies and maintenance Benefit (1/2)Common Component Concept – Presentation DENK 2010

  22. Activate applicative updates on demand. Independency between the application systems. Central functionalities are tested separately before rollout. No additional education needed. Reduce maintenance and costs. Benefit (2/2)Common Component Concept – Presentation DENK 2010

  23. Thank you!Common Component Concept – Presentation DENK 2010 Do you have any questions?

More Related