1. Advanced Integration and Deployment Techniques
Inessa Gerber
iWay Product Manager

2. Agenda Robust Integration Architecture Deployment Styles
Managed Configuration
iWay Integration Applications (iIAs)
iWay Software Development Kit (iSDK)
Source Control Management

3. Robust Integration Architecture

4. Robust Integration Architecture
Key Design Features
Modulation
Separation of protocol, message, and processing logic
Simplifies maintenance
Centralization of error handling & Event Flows
Use of Internal Queues, Ordered Queues, and other transport services across channels
Data Acquisition
Data Processing
Data Disposition
Error Handling IQ

5. Robust Integration Architecture
Key Design Features
Performance and 24/7 up-time
Reverse Verified Invocation (RVI) for access through Firewall, and message distribution across iSM servers
Load balancing across multiple iSM instances and Applications
Hot-Backup for ensured 24/7 uptime
Data Acquisition
Multiple iSM Servers
Backup Server
Heartbeat
External Server
RVI
Error handling

6. Robust Integration Architecture
Key Design Features
Externalized Configuration
Utilization of external property files, lookups, templates
Authentication Realms
Provider based implementation
Externalized Monitoring and Management
Integration with SNMP monitoring
iWay Sentinel for Monitoring, Management and Updates
Scheduled and Scripted tasks
Schedule Provider with Calendar support
Scripting support via services, iWay Sentinel, iWay SDK

7. Deployment Styles
Configurations vs iWay Integration Applications

8. What channels are running? V1 or V2???
Deployment Styles
Managed Configurations
Registry dependency – all managed configs share same registry
Versioning discrepancies – need to rebuild channels after archives are moved between environments
Archive v1
Channels v2
What channels are running? V1 or V2???
Archive v2
Channels v2
Channels v3
Archive v1
Channels v1
Export/rebuild
Double effort for moving across environments
Archives: contain components such as channels, processes, etc…
Packages: runtime definition such as
Runtime Conflicts
No disposable Test Environment

9. Deployment Styles iWay Integration Applications comprised of
iWay Integration Applications (iIAs)
iWay Integration Applications comprised of
Integration Components (channels, processes, registers, properties)
Deployment Template defining runtime characteristics
Facilitate Team Work
Dedicated Runtime
No iSM Registry or Configuration dependency
The low-touch, automated, scriptable iWay Deployment
ANT/Maven based
Scriptable via SDK

10. Deployment Styles iWay Integration Applications (iIAs)
Application Deployment Lifecycle
iWay Integration Tools
Integration Application
Deployment Template
Build iIA
Deploy iIA

11. Deployment Styles iWay Integration Applications (iIAs)
Application Propagation
iWay Integration
Tools
DEV - Template
Integration Application
QA - Template
Integration Application
PROD - Template
Integration Application

12. Deployment Styles iWay Integration Applications (iIAs) Server 1
Tools
Server 1
DEV - Template
Integration Application
QA - Template
Integration Application
PROD - Template
Integration Application
PROD - Template
Integration Application
Server X

13. Deployment Styles
iWay Integration Applications (iIAs)
Test-Run process against a Test Server automatically:
Builds, Deploys, Starts a dedicated runtime
Executes the pFlow against the runtime
Stops, Un-deploys, destroys the runtime iIA after test completion
Based on default or user configured Application runtime

14. Deployment Styles ANT Support Default iIA build process utilizes ANT
iWay Integration Applications (iIAs)
ANT Support
Default iIA build process utilizes ANT
Ordered set of Integration Tasks are exposed
Build.xml is available for management and updates

15. Deployment Styles Maven Support Available Option upon iIA creation
iWay Integration Applications (iIAs)
Maven Support
Available Option upon iIA creation
Each goal can be explicitly executed from command line or specified in the execution portion of the POM file
Fully documented with external repository

16. Deployment Styles iWay Integration Tools
iWay Integration Applications (iIAs): Summary
iWay Integration Tools
Build and Manage iIAs (deploy, start, stop, etc..)
Support for ANT/Maven and customized scripts
iWay Service Manager Console
Manage iIAs
Monitor iIAs and its components
iWay SDK
Scripted & Scheduled management of iIAs
Integrate into existing build systems
iWay Sentinel
Manage iIAs and distribute updates
Monitor iIAs and its components.

17. iWay Software Development Kit (iSDK)

18. iWay SDK Scripted management of deployments and updates
No need for iSM, works with existing build systems
Deploy, Distribute and Manage Applications
Ensures application integrity
Packaged sample ANT-based build solution that can be invoked using batch script
Build WAR files
iWay Integration Tools
SCM
iSDK
Runtime
Build System 18

19. iWay SDK
Sample Integration Tasks
Sample ANT Tasks 19

20. iWay SDK
Intuitive Documentation with Samples preinstalled with product 20

21. Source Control Management

22. Source Control Management
iWay Integration Tools (iIT) provides Version Control by implementing Eclipse Team APIs
Abstraction via Team APIs enables iWay to support various SCM systems such as SVN, ClearCase, TFS, etc…
It is highly recommended for all Integration Project components in iIT be source managed from the project level
Simply install SCM plug-in into iIT and connect to your repository for version control 22

23. Source Control Management
Usage example with SVN
Additional Options for Team selection
Utilize Navigator View
Note the Ignore List

24. Questions?