Serrano, Mart�in.
Technical Innovation, Solving the Data Spaces and Marketplaces Interoperability Problems for the Global Data-Driven Economy : I3-MARKET Series - Part III: the I3-MARKET FOSS Handbook. - 1st ed. - 1 online resource (190 pages) - River Publishers Series in Computing and Information Science and Technology Series . - River Publishers Series in Computing and Information Science and Technology Series .
Cover -- Half Title -- Series Page -- Title Page -- Copyright Page -- Table of Contents -- Preface -- Who Should Read this Book? -- What is Addressed in the i3-MARKET Book Series? -- What is Covered in this i3-MARKET Part III Book? -- Acknowledgements -- List of Figures -- List of Tables -- List of Contributors -- List of Abbreviations -- Chapter 1: i3-MARKET Overview -- 1.1: Context -- Chapter 2: General Description -- 2.1: Deployment and Operational Concepts -- 2.1.1: Consider the requirements of the software -- 2.1.2: Evaluate the deployment environment -- 2.1.3: Consider automation and orchestration -- 2.1.4: Evaluate containerization options -- 2.1.5: Consider monitoring and reporting tools -- 2.2: Deployment Specification -- 2.3: Terminology -- 2.4: i3-MARKET Artifacts Overview -- 2.5: Deployment Architecture View -- 2.6: i3-MARKET Network Infrastructure -- 2.7: Software Stack -- 2.8: i3-MARKET Master Environment -- 2.9: i3-MARKET Pilot Environment -- Chapter 3: Backplane API Gateway -- 3.1: Objectives -- 3.2: Solution Design/Blocks -- 3.2.1: Authentication and authorization -- 3.2.1.1: Authentication -- 3.2.1.2: Authorization -- 3.2.2: Subsystem implementation -- 3.2.3: Data flows -- 3.2.4: Service Integration Manager -- 3.2.5: Automatic integration mechanism -- 3.2.6: Subsystem OAS repository -- 3.2.7: Backplane repository -- 3.2.7.1: Remote images -- 3.2.8: Final deployment -- 3.2.9: Multiple environments support -- 3.3: Interfaces -- 3.3.1: Developers -- 3.3.2: OIDC discovery -- 3.3.3: OIDC core -- 3.3.4: RegistryBlockchainController -- 3.3.5: RegistryController -- 3.3.6: AuthController -- 3.3.7: Conflict-resolver service -- 3.3.8: FarewellController -- 3.3.9: HelloController -- 3.3.10: OpenApiController -- 3.3.11: Notifications -- 3.3.12: Queues -- 3.3.13: Subscriptions -- 3.3.14: PingController -- 3.3.15: Cost-controller. 3.3.16: Price-controller -- 3.3.17: RatingService -- 3.3.18: Agreement -- 3.3.19: Explicit user consent -- 3.3.20: Registration-offering -- 3.3.21: TokenizerController -- 3.3.22: Credential -- 3.3.23: Issuer -- Chapter 4: Deployment Guides -- 4.1: Artifact Deployment Guides -- 4.2: MDS1: Manual Deployment -- 4.3: ADS1: Automatized Deployment with Ansible Scenario One -- 4.4: ADS2: Automated Deployment with Ansible and CI/CD GitHub Pipelines Two -- 4.5: ADS3: Automated Deployment with Docker Compose -- 4.6: Tagging Releases Strategy -- 4.7: Deployment Process -- 4.7.1: Docker Compose -- 4.7.2: Technical Requirements -- 4.7.3: Specification and configurations -- 4.7.4: Deployment -- Chapter 5: Operative Specification -- 5.1: Libraries -- 5.2: i3-MARKET APIs -- 5.3: SDKs -- 5.4: User Interfaces -- 5.5: Install i3M Wallet -- 5.6: Create a Wallet and a Consumer and/or Provider Identity in the Wallet -- 5.7: Creating a Wallet 2/3 -- 5.8: Register a New OIDC Client -- 5.9: SDKs -- Chapter 6: SDKs and WEB-RI -- 6.1: Approach -- 6.2: SDK-Core Specification -- 6.2.1: SDK-core implementation -- 6.2.2: Core technology -- 6.3: SDK Reference Implementation (SDK-RI) -- 6.4: WEB-RI -- 6.4.1: Purpose -- 6.5: IMPLEMENTATION -- 6.6: Navigation: -- Chapter 7: Deployment Tools -- 7.1: Solution Design -- 7.1.1: MDS1: manual deployment -- 7.1.2: ADS1: automated deployment with Ansible -- 7.1.3: ADS2: automated deployment with Ansible and CI/CD GitHub pipelines -- 7.1.4: ADS3: automated deployment with Docker Compose -- 7.2: i3-MARKET: Onboarding Process -- Chapter 8: SDK-RI Specification -- 8.1: Objectives -- 8.2: Technical Requirements -- 8.3: SDK Reference Implementation -- 8.4: Core Technology -- 8.5: Continuous Integration and Deployment -- Chapter 9: SDK-RI Installation using Docker -- 9.1: Setup -- 9.2: Running the SDK-RI with Docker. 9.3: Configuring and using SDK-RI -- Chapter 10: WEB-RI -- 10.1: Purpose -- 10.2: Architecture -- 10.3: Sitemap -- 10.4: Run WEB-RI in Docker -- Chapter 11: Central Administration Guide -- 11.1: Cloud Management -- 11.2: Infrastructure Monitoring -- Chapter 12: Repositories and Open Source -- 12.1: GitLab/GitHub -- 12.2: GitLab Repository -- 12.3: GitHub Repository -- 12.4: Developers' portal with MKDocs framework -- 12.5: Open-Source Portal -- 12.5.1: Developers, users, and respective roles -- 12.5.2: Roles and activities of developers and experts in the governance model -- Chapter 13: Other Content -- 13.1: Local Development using Node.js -- 13.2: Local Development using Docker -- 13.2.1: Development scripts in the docker container -- Chapter 14: Conclusions -- References -- Index -- About the Editors.
This book focuses on the best practices and simplest software methods and mechanisms that allow the i3-MARKET backplane reference implementation to be instantiated, tested and validated.
9781040092460
Electronic books.
Technical Innovation, Solving the Data Spaces and Marketplaces Interoperability Problems for the Global Data-Driven Economy : I3-MARKET Series - Part III: the I3-MARKET FOSS Handbook. - 1st ed. - 1 online resource (190 pages) - River Publishers Series in Computing and Information Science and Technology Series . - River Publishers Series in Computing and Information Science and Technology Series .
Cover -- Half Title -- Series Page -- Title Page -- Copyright Page -- Table of Contents -- Preface -- Who Should Read this Book? -- What is Addressed in the i3-MARKET Book Series? -- What is Covered in this i3-MARKET Part III Book? -- Acknowledgements -- List of Figures -- List of Tables -- List of Contributors -- List of Abbreviations -- Chapter 1: i3-MARKET Overview -- 1.1: Context -- Chapter 2: General Description -- 2.1: Deployment and Operational Concepts -- 2.1.1: Consider the requirements of the software -- 2.1.2: Evaluate the deployment environment -- 2.1.3: Consider automation and orchestration -- 2.1.4: Evaluate containerization options -- 2.1.5: Consider monitoring and reporting tools -- 2.2: Deployment Specification -- 2.3: Terminology -- 2.4: i3-MARKET Artifacts Overview -- 2.5: Deployment Architecture View -- 2.6: i3-MARKET Network Infrastructure -- 2.7: Software Stack -- 2.8: i3-MARKET Master Environment -- 2.9: i3-MARKET Pilot Environment -- Chapter 3: Backplane API Gateway -- 3.1: Objectives -- 3.2: Solution Design/Blocks -- 3.2.1: Authentication and authorization -- 3.2.1.1: Authentication -- 3.2.1.2: Authorization -- 3.2.2: Subsystem implementation -- 3.2.3: Data flows -- 3.2.4: Service Integration Manager -- 3.2.5: Automatic integration mechanism -- 3.2.6: Subsystem OAS repository -- 3.2.7: Backplane repository -- 3.2.7.1: Remote images -- 3.2.8: Final deployment -- 3.2.9: Multiple environments support -- 3.3: Interfaces -- 3.3.1: Developers -- 3.3.2: OIDC discovery -- 3.3.3: OIDC core -- 3.3.4: RegistryBlockchainController -- 3.3.5: RegistryController -- 3.3.6: AuthController -- 3.3.7: Conflict-resolver service -- 3.3.8: FarewellController -- 3.3.9: HelloController -- 3.3.10: OpenApiController -- 3.3.11: Notifications -- 3.3.12: Queues -- 3.3.13: Subscriptions -- 3.3.14: PingController -- 3.3.15: Cost-controller. 3.3.16: Price-controller -- 3.3.17: RatingService -- 3.3.18: Agreement -- 3.3.19: Explicit user consent -- 3.3.20: Registration-offering -- 3.3.21: TokenizerController -- 3.3.22: Credential -- 3.3.23: Issuer -- Chapter 4: Deployment Guides -- 4.1: Artifact Deployment Guides -- 4.2: MDS1: Manual Deployment -- 4.3: ADS1: Automatized Deployment with Ansible Scenario One -- 4.4: ADS2: Automated Deployment with Ansible and CI/CD GitHub Pipelines Two -- 4.5: ADS3: Automated Deployment with Docker Compose -- 4.6: Tagging Releases Strategy -- 4.7: Deployment Process -- 4.7.1: Docker Compose -- 4.7.2: Technical Requirements -- 4.7.3: Specification and configurations -- 4.7.4: Deployment -- Chapter 5: Operative Specification -- 5.1: Libraries -- 5.2: i3-MARKET APIs -- 5.3: SDKs -- 5.4: User Interfaces -- 5.5: Install i3M Wallet -- 5.6: Create a Wallet and a Consumer and/or Provider Identity in the Wallet -- 5.7: Creating a Wallet 2/3 -- 5.8: Register a New OIDC Client -- 5.9: SDKs -- Chapter 6: SDKs and WEB-RI -- 6.1: Approach -- 6.2: SDK-Core Specification -- 6.2.1: SDK-core implementation -- 6.2.2: Core technology -- 6.3: SDK Reference Implementation (SDK-RI) -- 6.4: WEB-RI -- 6.4.1: Purpose -- 6.5: IMPLEMENTATION -- 6.6: Navigation: -- Chapter 7: Deployment Tools -- 7.1: Solution Design -- 7.1.1: MDS1: manual deployment -- 7.1.2: ADS1: automated deployment with Ansible -- 7.1.3: ADS2: automated deployment with Ansible and CI/CD GitHub pipelines -- 7.1.4: ADS3: automated deployment with Docker Compose -- 7.2: i3-MARKET: Onboarding Process -- Chapter 8: SDK-RI Specification -- 8.1: Objectives -- 8.2: Technical Requirements -- 8.3: SDK Reference Implementation -- 8.4: Core Technology -- 8.5: Continuous Integration and Deployment -- Chapter 9: SDK-RI Installation using Docker -- 9.1: Setup -- 9.2: Running the SDK-RI with Docker. 9.3: Configuring and using SDK-RI -- Chapter 10: WEB-RI -- 10.1: Purpose -- 10.2: Architecture -- 10.3: Sitemap -- 10.4: Run WEB-RI in Docker -- Chapter 11: Central Administration Guide -- 11.1: Cloud Management -- 11.2: Infrastructure Monitoring -- Chapter 12: Repositories and Open Source -- 12.1: GitLab/GitHub -- 12.2: GitLab Repository -- 12.3: GitHub Repository -- 12.4: Developers' portal with MKDocs framework -- 12.5: Open-Source Portal -- 12.5.1: Developers, users, and respective roles -- 12.5.2: Roles and activities of developers and experts in the governance model -- Chapter 13: Other Content -- 13.1: Local Development using Node.js -- 13.2: Local Development using Docker -- 13.2.1: Development scripts in the docker container -- Chapter 14: Conclusions -- References -- Index -- About the Editors.
This book focuses on the best practices and simplest software methods and mechanisms that allow the i3-MARKET backplane reference implementation to be instantiated, tested and validated.
9781040092460
Electronic books.