Scribd
Upload
40 views2 pages

IIB Design and Development Considerations

The document outlines key design considerations for developing interfaces between source and target systems using IBM Integration Bus (IIB), including details about the source and target systems, data formats, exception handling, logging, version control, and adherence to service-oriented architecture (SOA) principles and best practices. Non-functional requirements like performance, security, availability, and maintainability are also addressed.

Uploaded by

marina14350
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
40 views2 pages

IIB Design and Development Considerations

The document outlines key design considerations for developing interfaces between source and target systems using IBM Integration Bus (IIB), including details about the source and target systems, data formats, exception handling, logging, version control, and adherence to service-oriented architecture (SOA) principles and best practices. Non-functional requirements like performance, security, availability, and maintainability are also addressed.

Uploaded by

marina14350
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

IIB Design and Development Considerations

Design Considerations

Source System Details


What is the is Source system and how we get the data
into IIB and protocol used Eg:
MQ,HTTP,FTP,Webservice, HTTP,Data Base etc
according to that choose the Output Node

Source System Format In which format Source system send us the data Eg:
XML,CSV,SOAP,JSON,Flat File (BLOB) etc

Target System Details What is the is target system and how we should send
the data from IIB and protocol used Eg:
MQ,HTTP,FTP,Webservice, HTTP,Data Base etc
according to that choose the Output Node

Target System Format In which format Target system requires the data Eg:
XML,CSV,SOAP,JSON,Flat File (BLOB) etc

No of Source and Target Systems – How many source and target systems required,
Coordinate Request and Reply Synchronous / Asynchronous/Coordinating Request and
Response

Exception Handling Design and develop Exception handling

Logging & Auditing Design and develop Logging and Auditing

Version Control & Management Which Version Control to be used like IBM Clear case /
Harvest/ Perforce / SVN / GIT Hub etc

Automatic Build & Deploy Do we have any Automatic Build & Deployments tools
like IBM Urban Code Build and Deploy or Simple ANT
script

SOA Principles / Guidelines

Follow SOA Principles / Guidelines / Standards – Refer IBM / Wikipedia for more details.
Non-Functional /Qualitative Requirements
Security How we handle security, SSL / TSL /
Encryption / Decryption / LDAP
Performance i. How many transactions we get in
Production.
ii. Volume Testing.
iii. No of Additional Instances required.
High Availability Do we have Data Centers / Clustered
Environment / Back up plan in case of System
Failure
Maintainability Design and Develop the interfaces which are
easy to maintain
Scalability Design and Develop the interfaces which are
easy to scale up as per new demands
Reusability Design and Develop the interfaces which are
loosely reusable – Eg : Sub flows , Reusable
Flows etc
Loose Coupling Design and Develop the interfaces which are
Loosely Coupled.

Check lists / Best Practices

i. Get Access to all the required Environments like Development / QA / SIT / UAT etc
except Production (Only AMS / Production Support team supposed to get access to
Production Environment).
ii. Get IIB Tool Kit / MQ etc softwares installed and ensure about their versions.
iii. Get access to Version control and details about the code base if exists already
iv. Get KT / Overview, functional document, technical design document, Mapping sheet,
Artifacts like XSD. WSDL, Test cases, Test Data etc for the interface which you
develop.
v. Check-In the code you develop into Version control and ensure to take backup
regularly.
vi. Once you finish development and unit testing then Check-Out your code and another
workspace, build, deploy and test it – This makes sure that your Check-In was
successful.
vii. Give proper comments wherever required and don’t use CARDINALITY inside loop and
try to avoid loop inside loop – Refer ESQL Coding and Naming standards pdf for more
details
viii. Document your work and upload it in a share repository periodically.
ix. As far as possible try to externalize all the UDP’s so that they can be ne changed
dynamically at runtime without touching the source code.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy