Jan De Nul implemented an API strategy to facilitate integration and data sharing between its various software applications and systems. It established an API Center of Excellence to define standards and processes for API development, management, and governance. Jan De Nul selected IBM API Connect as its API management platform, which provides capabilities for developer portals, analytics, security, and the full API lifecycle. The implementation of the API strategy and use of API Connect has resulted in a performant, secure, and high-availability integration platform to enable collaboration and data-driven decisions across the organization.

1. Supported by:
Connected Brains 2019
Implementing an API strategy at Jan De Nul

2. Topics
• Jan De Nul Presentation
• Challenges
• Solution
• Approach
• Conclusion & Lessons Learnt

3. Niek Jacobsen
Integration Architect
niek.jacobsen@loqutus.com

4. Michael Mangelschots
Architecture Team Lead
michael.mangelschots@jandenul.com

5. Jan De Nul IT – What do we do?
• We implement and support administrative services and process
automation for our projects around the world
• We gather data and provide reports that enable business decisions
• We facilitate internal and external collaboration
• And much more...

6. Hardware
• Laptops/desktops/tablets/printers/accessories
• Data centers (servers, storage, networking, firewalls,...)
• Telephony (PABX, handsets, smartphones)
• Audiovisual equipment (beamers, video conferencing).

7. Software
• Analysis and development of existing or new applications for the
whole group (~65% of the software is developed in-house)
• Market research and implementation of commercially available off-
the-shelf software for the whole group.

8. Communication
• Leased lines, MPLS connections between sites
• Wi-Fi vessels/offices/sites
• Telephony subscriptions
• E-mail
• SECURITY!

9. Support
• Service desk (~250 tickets each week)
• Installation and support on-site for offices/vessels/sites
• Constant monitoring of availability, stability, performance and security
to allow targeted adjustments and keep the environment solid.

10. Roadmap & Projects
• ICT supports business strategy
• Changes are implemented through a controlled project approach to
prohibit major disruption in the day-to-day business operations.

11. Integration
• Pre-history of 5+ years: introduction of SOAP services to facilitate
duplication of some master data concepts between applications
• Period of 2 years to define future integration landscape
• Gathering of requirements (governance, technical, security, make vs buy, ...)
• Conclusion: we need professional off-th- shelf software and an external
partner
• RFI to find a suitable software solution
• Evaluated 5 products
• Search for an integration partner
• Creation of an integration team
• 4-5 JDN FTE + external partner (2 FTE)

12. Challenges
Which applications consume which APIs?
Which APIs are available?
No consistent security mechanism for APIs
How to manage API lifecycle and versioning?
No overview of API usage and performance

13. API Management Reference Architecture
API Key Management
API Metadata Repository
Version & Lifecycle
Management
Analytics
Consumer
App
API Key
Authentication
Throttling
Access
Control
ESB
APIs
Identity
Management
Financials
Translation
Gateway Management
Billing
Developer
Portal
Self-service
Registration
Social Features
API
Repository
Backends

14. IBM API Connect

15. IBM API Connect
Customizable developer portal
• Self-service registration & subscription
• Discover & test available APIs
Customizable analytics dashboards
• Based on ELK stack
• Customizable Kibana dashboards
Easy security policy definition & application
Full lifecycle & version management capabilities

16. API Connect Architecture
Developer
Toolkit
API Management
Server
Developer
Portal
API
Gateway
Mobile apps Enterprise apps
Business partner
apps
Business partner
apps
Database Apllication server
ESB Cloud service
Belongs to
provider
org
Belongs to
developer
org
Belongs to
provider
org

17. Approach:API Center of Excellence

18. Center of Excellence - Aspects
API
reference
architecture
API
development
method
Training
&
coaching
API
governance
• Process
• Roles & responsibilities
• Deliverables
• Standards & guidelines
• Tooling
• Organization model
• Support process
• Guidelines
• Tooling
• Evangelization
• Training & coaching
for different roles
(API developer,
API manager, …)
Component
overview for
API delivery

19. Results
• Performant, secure and high-available platform
• Integrated with existing build & deploy tools
• Customized developer portal & dashboards
• Awareness through multiple training sessions for
different roles/teams
• Effective API Management

20. Non-production Cloud

21. Production Cloud

26. Conclusion and Lessons Learnt
• There’s more to it than installing & using the tools
• Make sure that everything is in place before using the
platform
• Set up an API CoE to centralize API platform activities
• Evangelize!

27. Thank you!