Integration Projects

Technical specifications Template: ESB/API Vendor product or open-source Architect will prepare technical spec Template.
1) API’s
2) Real-time ESB Service
3) Near real-time service
4) Batch service and
5) Bulk service. Building the technical specification with all interface details. Review technical specification and sign off.

Enterprise Architecture Goals & Objectives

• API Architecture Goals & Objectives
• Infra and Security architecture Goals & Objectives
• Current CLIENTS/CUSTOMERS Mainframe integration and SOA architecture review.
• Current integration any percentage of available tech specs documents review.
• Existing services inventory and integration patterns review.
• Current transformation mapping logic review.
• Review existing Java transformation logic.
• Current integration connectivity with Mainframe and other external systems.
• Current gateway, security, and data encryption review.
• Review existing internal and external Gateway.
• Review the integration daily volume of batch jobs, SOAP Web services.
• Identify, Analyze and Document Target State Architecture.

Enterprise Architecture Strategy document and guidelines.

• Infrastructure Architecture Strategy and alignment with Target Architecture
• High level API Strategy and Roadmap and define API governance model.
• Micro Services Strategy and Approach and High level ESB Strategy and Roadmap
• Observations, drivers and best practices required for target state API three/two layered architecture
• Document Patterns, Protocols and Models for existing Mainframe integrations.
• Document Key Observations and possible API strategy considerations.
• Identify the commonality from the existing services to build API's
• List all the existing connections and co-relate with out-of-box mule connectors and APIKIT's.

Design

• API Design considerations, strategy and roadmap.
• Defining experience, process and system API guidelines.
• Defining external, internal and partner APIs based on the audience.
• Leveraging the process layer capabilities by reusing across.
• API Led connectivity and decision making of two-layer and three-layer architecture. (API Identification, Design, Implementation, and operations)
• Defining functional and non-functional requirements and dependencies. (SLAs, TPS, Response Time, Size of Payload, High Availability services, Disaster Recovery, Environments - access and connectivity.)

Connector configurations: Defining connector configuration and properties for the entire/required/selected ESB/API Vendor product or open source out-of-box connector stack specific to non-prod and prod environments and externalize the parameters.

Reusable components: Our early detection of generic/common and reusable components during the build will/should reduce lot of development time.

Error Handling Framework: ESB/API Vendor product or open-source Architect will prepare Default exception strategy. Error handling framework consists of custom error handling, API related error notifications (Related to APIKIT’s) connector specific error handling. Defining error handling framework specific to real-time, near-real-time, batch and bulk API services. Building both default and custom error handling frameworks.

Retry and Resubmit Strategy: Defining the resubmit, retry/reconnect / reprocessing strategy based on the connector stack. Handling failed events efficiently in real-time and reprocessing efficiently without any data loss in near-real-time.

Parallel Processing Strategy: Configure and leverage Configured parallel processing functionality at component and connector level.

Logging framework: Logging framework and configuring log4j2 file for non-prod and prod env's enabling custom logging on CloudHub.

Memory and Thread Management:Experience configuring mule components and connectors for proper memory allocation and efficient thread management.

Data Encryption and Security: Data encryption strategy to define security for API authentication and authorization.

Infrastructure - Cloud Environment Infrastructure tuning - Non-Prod and Prod env’s tuning aligning with Infrastructure team for deployments.