Wissam Boulos

o Project Eurica – Core of Icare's information system, my mission is to maintain the existing system, evolve it, and digitally transform it towards a new Modular Eurica version.

Roles and activities:

•Software Architect and Backend Java Developer

1. Fix production issues and optimize processes (Struts, Hibernate, PostgreSQL, Java 8, 11).

2. Develop new modules in the Modular Eurica project, Rest Full services, real-time processing (Spring boot web, Kafka, PostgreSQL, Java 17, 21).

 Technical environment: Java 8, 11, 17, 21 Spring Boot 2, Spring Data, REST API, Kafka, Struts, Postgres, Tomcat, Postman, DBeaver.

OPTIMA Program – Digital transformation of a monolithic financial product management platform towards a microservices architecture and integration of a first client.

Roles and activities:

1. Pepit Project, an API interface between Azqore's financial product system

and its clients.

• Software architecture setup, technical specifications writing.

• Solution development

• Deployment and delivery

2. PMSV2 Project, modernization and exposure of the Cobol IS via Rest APIs

• Technical Support

• Recruitment of Engineers in India

o Refactoring of the extranet, O.N.E M&P project (2017 - 2021)

Roles and activities:

• Training on new technologies:

 "NoSQL" MarkLogic database: XQuery development, installation, and configuration.

 Vertx.io: familiarization with the framework that allowed us to set up a communication bus for feeding ONE MP data.

• Solution implementation

 Participation in software architecture workshops for ONE MP with the rest of the team.

 Participation in the development of different parts of the solution:

• Implementation of the communication bus and real-time synchronization features.

• Data modeling in MarkLogic and business modules in Xquery for retrieving this data.

• Implementation of REST APIs exposing data stored in MarkLogic using Java 8, Jersey, and Tomcat.

• Implementation of automated testing mechanisms, particularly to ensure the validity of authentication and authorization processes.

 Participation in setting up a DevOps chain for this project:

• TeamCity is used for scripting and automating builds, tests, and deployments across all our environments (DEV, Staging, Pre-production, and production).

• Nexus is used to store versioned artifacts produced by builds.

• GitHub is used for source code management and gitflow.

 L2 L3 Support, evolutions, and maintenance:

• The project continues to evolve with new features added daily to streamline the organization's interactions with its partners. The goal is the complete retirement of the old Extranet in Q1 2021.

 Technical environment: Java, J2EE, Jersey, Vertx, microservices, Marklogic, XQuery, Postman, Json

o Implementation of the Clearspace platform

Community and workgroup platform for document sharing.

Roles and activities:

• Technical evaluation of the platform when proposed by the project manager.

• Installation, configuration, and updates

• Software architecture and implementation of integrations with the rest of the organization's IT. Specifically:

 Authentication: integration with our SSO

 Authorization: integration with our CMS (Contact and List management System)

 Controlled exposure of the organization's official documents (permissions)

 Integration of an OECD theme for the visual aspect

 Evaluation and installation of plugins

• Technical environment: Java, J2EE, JiveSoftware, Struts, Spring, Tomcat, SQL Server, Linux

o Refactoring of the organization's website (2010 - 2012)

Migration and refactoring of the organization's website from the Vignette platform to the TerminalFour (T4) platform.

Roles and activities:

• Migration of the site from the Vignette platform to T4: due to the provider's inability to perform this task, we had to handle it ourselves. Learning the T4 SDK, architecture, and implementing a migration solution that could be executed multiple times incrementally.

• Information architecture, data structures, navigation, rendering, etc., in the new Web CMS in collaboration with our project manager and the communication department (PAC).

• Coaching and advising development teams responsible for setting up the new site, both on the T4 and OECD sides.

• Implementation of a site factory to host the multitude of satellite sites contributing to the organization's online presence:

• Configurable templates

• Library of configurable rendering blocks (slider, HTML block, accordions, etc.)

• Specific developments:

• Authentication: integration with SSO for the organization's secure satellite sites.

• Authorization: integration with the CMS (Contact and List management System) for the organization's secure satellite sites.

• Extensions of the standard tag library to cover the specific needs of certain satellite sites of the organization.

• Integration with other information sources via our communication bus: publications (KAPPA), data (Data Portal), etc.

• Technical environment: Java, J2EE, TerminalFour, Tomcat, Apache, Vertx, SQL Server

o OlisNext Project: Migration of the OlisNext system from Lotus Notes to Vignette V7

(Document management and publishing system)

Roles and activities:

• Design and implementation of web services

• Implementation of a PDF document indexing and search engine

• Definition of development rules and methods

• Technical environment: Vignette, Java, J2EE, Autonomy, Win Server 2003, SQL Server

o OECD.ORG Project: Maintenance and Evolution of the OECD website using

Vignette 7 technology.

Roles and activities:

• Implement a new look

• Evolution of the website http://www.oecd.org to incorporate new web services created in the OlisNext project.

• Implementation of a content and website page indexing and search engine.

• Technical environment: Vignette, Java, J2EE, Autonomy, Win Server 2003, SQL Server

• L2, L3 Support and maintenance

o Vignette v7 for the organization's website until 2012

o Vignette v8 for OLIS, the organization's Extranet, where official documents, meeting schedules, and various tools for interacting with our members and partners are shared.

o Jive - OECD's online collaboration platform for creating virtual work communities. This platform is widely used by our committees and working groups.