1 IKAN ALM Architecture Closing the Gap Enterprise-wide Application Lifecycle Management
2 Table of contents IKAN ALM SERVER Architecture...4 IKAN ALM AGENT Architecture...6 Interaction between the IKAN ALM Server/Agent and the Phase Catalog...7 Glossary...8 For More Information IKAN ALM Architecture
3 Summary IKAN ALM is a server-agent Web Application Lifecycle Management (ALM) solution with a web-based Administrative console, and consisting of a number of main ALM services and a number of integrations with other ALM tools. All IKAN ALM actions are defined and executed through the Web application or the Commandline Interface (CLI). The Web application is used for defining the Global and Project Administration items and the User s personal Desktop Main ALM services that IKAN ALM provides are: Life Cycle Build Deploy Approval Notifications Integrations offered with other ALM tools are for: Version Control Repositories Requirements, Issue Tracking or Defect Tracking systems Build tools Deploy tools Reporting tools IKAN ALM Architecture 3
4 The Global Administration is used for defining the system settings, version control repository access, user groups, machines, transporters (FTP, FileCopy, Secured Shell),scripting tools (Ant, Maven or NAnt) and issue tracking systems (e.g., JIRA, HP ALM, Collabnet or other). The Project Administration is used for defining the project with its lifecycle and levels (one or more Build, Test and Production levels). IKAN ALM actions are called Level Requests. A Level Request consists of a Build Request or a Deploy (to Test or Production) Request. Level Requests are created through the Web Interface or the Commandline Interface. All Global and Project administration information is stored in a JDBC-compliant database, such as MySQL, Oracle, DB2 or SQL Server. It also contains the log of scripting actions executed while handling Level Requests. The actual Build Results are stored in an archived format (*.zip or *.tar.gz) in the Build Archive on the IKAN ALM Server, so that they can be retrieved for later Deploy Level Requests. The Web application runs on a Web or application server (preferably Apache Tomcat) on the IKAN ALM server machine. The same machine also runs the SERVER daemon process that handles the Build or Deploy Level Requests. The Level Request handling consists of running different steps, called Phases, such as the communication with the external systems (Versioning, Issue Tracking, ) and the interaction with the IKAN ALM Agent(s) via Web services to handle the actual Build and Deploy actions. As the Server process is OSGi-aware (see IKAN ALM SERVER Architecture) IKAN ALM has the possibility to not only execute Core Phases, but also Custom Phases that it retrieves from the Phase Catalog. An IKAN ALM agent is also an OSGi-aware daemon process (see IKAN ALM AGENT Architecture) which transfers sources (in case of Build) or a build result (in case of Deploy) from the Server Machine, executes a script by a Scripting Tool (ANT, Maven, ) and (in case of a Build) archives the Build result to the Build Archive on the Server. Next to those Core Phases, it can also run Custom Phases, whereby it retrieves the phases from the phase catalog as defined on the SERVER Machine. From a user s perspective, the Phase Catalog and the Core and Custom Phases you find there, are a key IKAN ALM feature. For each phase executed by the SERVER or an AGENT, an entry exists in the Phase Catalog. IKAN ALM comes with Core SERVER and AGENT Phases and any user can define and customize phases into the Phase catalog. In the Catalog, each phase consists of a physical JAVA Archive (JAR) on the SERVER file system and related metadata information of the phase. Custom phases are added and managed through the Web interface. The phase s metadata information is used by both the SERVER and AGENT when a phase is executed. The phase name and version are key parameters to identify a phase, whereby the versioning number allows you to execute different versions of the same phase on the same SERVER or AGENT(S). IKAN ALM SERVER Architecture The SERVER is a Java process (Daemon) with a Monitor and Scheduler sub process. It is executed in a JAVA Virtual Machine (JVM) and it handles Level Requests given by a user through the Web interface or initiated through the Commandline Interface. The monitor process steers the interaction with the Version Control Repositories when a Level Request is executed (check-out of source code, tagging of source code) and it will communicate with the AGENTS to make sure that the Build and Deploy processes are executed correctly (see IKAN ALM AGENT Architecture). Support for Continuous Integration, Nightly Builds or Continuous Delivery is handled by the Scheduler process. The Scheduler will trigger the Version Control Repository to see if source code has been changed. This project-based triggering is based on pre-defined moments (every night at 8PM) or time intervals (every hour, every 5 minutes, ) 1. 1 Note that Continuous Integration may also be realized by a hook script that calls the IKAN ALM Commandline interface when a commit is done in the versioning system. 4 IKAN ALM Architecture
5 IKAN ALM Server OSGI The SERVER is OSGi-aware and runs within Apache Karaf, a light weight OSGI runtime container. Karaf supports the Blueprint Service 2 Component Frameworks, that we selected and use. This Blueprint Service gives us the ability to make our Phases pluggable. Other benefits the Karaf container brings are the integrated JAAS security framework, the Feature Service, i.e., the provisioning system that allows us to install and update Phases automatically (see Interaction between the IKAN ALM SERVER/AGENT and the Phase Catalog), the OS integration (runs as a Windows service or Linux daemon) and the possibility of hot deployment of OSGi bundles. The SERVER code is packaged in an OSGi Server Megabundle wherein a number of key Blueprint Components are declaring: the Phase Tracker and the Server Core Phases. The Core phases are the basic building blocks for handling Level Requests: checking-out of source code from a Version Control Repository, the notification and management of Agents in order to ensure proper execution of Builds and Deploys, tagging of source code in the VCR. Each of these phases is registered as a Blueprint Service when the Server mega-bundle is started and is kept by the Phase Tracker that traces the Blueprint Phase services. The Server mega-bundle imports about 60 third party libraries that all are translated to correct OSGi Bundles. Most of them come from the SpringSource Enterprise Bundle Repository 3 ; others have been transformed by us as they were not available in a public repository. Finally, the Phase Tracker will also register the Custom Phases: these are the Phases that execute a specific script (Ant, NAnt or Maven), which are defined in the Phase Catalog by the user himself and that are used to execute specific processes (e.g., to interact with an external archive like Nexus, Jenkins or TFS) on the SERVER for a Level Request IKAN ALM Architecture 5
6 Each of these phases resides in a separate OSGi bundle that declares one Blueprint Service. At installation or update, the Phase Tracker will pick it up and the Server mega-bundle will consume it when it handles a Level Request that uses that specific Custom Phase. For the installation and update of the Custom Phases (and also of the Core phases) from within the Phase Catalog, the Karaf feature mechanism is used (see Interaction between the IKAN ALM SERVER/AGENT and the Phase Catalog). IKAN ALM AGENT Architecture The AGENT is a Java process (Daemon) with a Build and Deploy sub process. It is executed in a JAVA Virtual Machine (JVM) and it handles Builds and Deploys that are initiated by the SERVER. This process is so-called local when it is executed on the same physical machine as the SERVER. When it runs on a different physical machine, it is called a Remote agent. The AGENT interacts remotely with the Monitor process of the SERVER (via Web services) and locally with a Transporter (FileCopy, FTP of SSH) and a scripting tool (Ant, NAnt or Maven), whereby these scripting tools need to be configured correctly in the IKAN ALM Web application and on the AGENT machine. Like the SERVER, the AGENT is OSGi-aware. The AGENT also runs within Apache KARAF, giving the same benefits to the AGENT as it gives to the SERVER. The Agent code is packed into an OSGi Agent Mega-bundle where a number of key Blueprint Components are declared: the Phase Tracker and the Agent Core Phases. The Core phases are the basic building blocks for handling Level Requests: transport of source (build) or a build result (deploy) verification of a build or deploy script, execution of Builds and Deploys. Each of those phases is registered as a Blueprint Service when the Agent mega-bundle is started and is kept by the Phase Tracker that traces the Blueprint Phase services. Finally, the Phase Tracker will also register the Custom Phases: these are the Phases that execute a specific script (e.g., for an Update of a database, or a Deploy to a Web server) that eventually are defined in the Phase Catalog by the user himself and that are used in a Build IKAN ALM Agent OSGI 6 IKAN ALM Architecture
7 or Deploy environment that is linked to an AGENT. Each of those phases resides in a separate OSGi bundle that each time declares one Blueprint Service. For the installation and update of the Custom Phases (and also the Core phases) from within the Phase Catalog, the Karaf feature mechanism is used (see Interaction between the IKAN ALM SERVER/AGENT and the Phase Catalog). Interaction between the IKAN ALM Server/Agent and the Phase Catalog The following figure describes how the AGENT and SERVER interact with the Phase Catalog when executing a Level Request with a Build and Deploy action. The focus is put on the distribution of a missing Custom Phase during the execution of a Build by an AGENT. This process consists of the following sequential steps. The following steps happen before what is shown on the figure: 1. The SERVER Monitor process starts a Level Request. 2. The SERVER collects a list of phases that need to be executed from the database 3. This list may contain Server Core Phases and Custom Phases (for example: A, B). 4. The SERVER consults the Phase Tracker component to find the OSGi service objects from the Server phases. (We assume that all the phases from the Phase Tracker list are registered. If not, the same process as the one for the Agent applies). IKAN ALM Server/Agent and Phase Catalog interaction IKAN ALM Architecture 7
8 5. The SERVER starts the sequential execution of the phases. One of the Core Phases is a Build phase: The SERVER notifies the AGENT via a Web service that he needs to execute a Build. Now the figure from above comes into play: 6. The AGENT Build process picks up the Build request 7. The AGENT asks the SERVER a list of phases it needs to execute. 8. The AGENT gets a list of phases it needs to execute, whereby the list can contain both Agent Core Phases and Custom Phases. 9. The AGENT consults its Phase Tracker component to retrieve the OSGi service objects from the phases. All Core Phases are found, the Custom Phase W has not been registered yet. As a consequence, the Build process is temporarily stopped. 10. The AGENT/Phase Tracker asks the SERVER to install the missing Custom Phase W. 11. The SERVER reacts by sending an XML file with the phase description and an URL that can be used by the Phase Tracker to install the missing phase in the AGENT Karaf Container. The XML file is a Karaf feature file 4 ", with a URL that refers to the location of the correct version of the missing phase W in the Phase Catalog. The URL has as file type FTP or SSH, depending on the Transporter that has been defined for that specific AGENT (Machine). 12. The AGENT passes the feature file to the Karaf Feature Service. The Feature Service gets the Custom Phase bundle from the Phase Catalog by using the given URL and installs it in the OSGi framework. The Blueprint component framework detects that the Custom phase bundle contains a Blueprint descriptor, and registers the phase as an OSGi service. As a result, the Phase is registered in the Phase Tracker. 13. When the Build process starts again, the AGENT consults the Phase Tracker again to find the OSGi service objects for this phase. All Core Phases are found, including the missing Custom Phase W. 14. The AGENT starts the sequential execution of the phases for this specific Build. 4 Glossary Build Build Archive Build Phase Build Tool A Build is an action on a Build Environment which involves several sub processes, called Build Phases. It is always part of a Level Request, which may also contain other Builds or Deploys. [A Build is handled by the IKAN ALM Builder]. It starts from sources that were retrieved from the VCR to the Build Environment. A Build script is executed on those sources by a Scripting Tool and gives a Build Result that is transferred to the Build Archive. The physical location (path) on the IKAN ALM Server where the Build Results are stored in a compressed and archived format (*.zip or *.tar.gz). The Build Results are organized by Project and by Project Stream. A Build Phase is a sub process that must be performed to complete a Build action. Different Build Phases form the workflow of a Build and are inserted into a Build Environment. They are executed by the IKAN ALM Builder Thread of the IKAN ALM Agent. A Build Phase may be a Core Phase (e.g. Verify Build Script), or a Custom Build Phase created or imported by the User in the Phase Catalog. Scripting Tool installed on a Build Environment 8 IKAN ALM Architecture
9 Core Phase Custom Phase Deploy Deploy Phase Deploy Tool IKAN ALM Agent IKAN ALM Server Issue Tracking Core Phases form the IKAN ALM Core functionality. They can only be viewed, and cannot be altered nor deleted. Consider them an integral part of IKAN ALM. When a new Level, Build or Deploy Environment is created, its default workflow will be created and will completely consist of a sequence of Core Phases. This default workflow may be changed by removing Core Phases, by changing the sequence order, or by adding Custom Phases. A Phase added by the User is also called a Custom Phase. It may be created from scratch in Global Administration based on one or more working scripts and resources, or it may be imported, using the Import Phase functionality. Once defined in Global Administration, a Custom Phase may be inserted into (and consequently change) the default work flow of a Level, Build or Deploy Environment. All Custom Phases are stored in the Phase Catalog on the IKAN ALM Server, and are transported automatically to the IKAN ALM Server (Level Phase) or IKAN ALM Agent (Build or Deploy Phase) when they are to be executed. A Deploy is an action on a Deploy Environment which involves several sub processes, called Deploy Phases. It is always part of a Level Request, which may also contain (an)other Build(s) or Deploy(s). [A Deploy is handled by the IKAN ALM Deployer]. It starts from a Build Result which is retrieved from the Build Archive. A Deploy script is executed on this Build Result by a Scripting Tool. A Deploy Phase is a sub process that must be performed to complete a Deploy action. Different Deploy Phases form the workflow of a Deploy and are inserted into a Deploy Environment. They are executed by the IKAN ALM Deployer Thread of the IKAN ALM Agent. A Deploy Phase may be a Core Phase (e.g. Transport Build Result) or a Custom Deploy Phase created or imported by the User in the Phase Catalog. A scripting Tool installed on a Deploy Environment A process (daemon) running on a Machine with sub processes to handle Build or Deploys. An Agent running on the same Machine as the IKAN ALM Server is also referred to as local, whereas running on a different Machine it is indicated as remote. During a Build or Deploy the IKAN ALM Agent interacts remotely with the IKAN ALM Monitor, and locally with a Transporter and with a Scripting Tool that must be correctly configured on the Machine. The Machine hosting the IKAN ALM web application and the IKAN ALM Monitor and Scheduler processes. A system external to IKAN ALM, where Issues (defects, enhancements, tasks, ) may be defined for a Project. Samples are Atlassian JIRA, HP Quality Center, Collabnet TeamForge, Bugzilla or Trac. IKAN ALM can plug in to such a System and keep up with the Issues that were handled for a Level Request. The integration with JIRA, HP Quality Center and TeamForge is more advanced: Issues are automatically synchronized through the lifecycle, and it is possible to keep a link with the Level Requests in the JIRA Issue, HP Quality Center Defect or TeamForge Artifact. IKAN ALM Architecture 9
10 Level Request Life-Cycle Phase Catalog Project Scripting Tool Transporter A Level Request is an action on a Level which involves several sub processes, called Level Phases. In most cases, a Level Request will contain at least one Build or Deploy action, which will be executed on local or remote Machines. A Level Request may be created manually by the user via the Web interface or the Command Line interface, or automatically by the Scheduler Thread of the IKAN ALM Server. A Level Request is handled by the Monitor Thread of the IKAN ALM Server. A Life-Cycle is a sequence of Levels that is linked to a Project Stream. It enables to set up the step-by-step process to promote sources and build results from development, to test, QA,... to end up into production. One Project may have different Life-Cycles, e.g. for development on the next release, for maintenance or urgency fixes on the release currently in production, for parallel development, A Life-Cycle may be reused in more than one Project Stream. The physical location (path) on the IKAN ALM Server where the Custom Phases (created from scratch or imported) are stored in an archived format (Phase.name-Phase.version.jar, e.g. com.ikanalm.echoproperties jar). When an IKAN ALM Server or Agent needs to install a missing Custom Phase, it will be retrieved from that location. That will be done using the Transporter linked to the Server or Agent Machine. An IKAN ALM Project maps to a project or subproject in a versioning system (VCR) which bundles related sources. An IKAN ALM Project is a shell for one or more Project Streams in which the real actions (Level Requests, Builds, Deploys) are done. It is possible to set up dependencies between different Projects, also through the Project Streams. There are 2 types of Projects: Release-based Projects: IKAN ALM will work with the existing structure in the VCR system, so that the objects to be extracted will be retrieved automatically when starting the build process. Package-based Projects: this concept enables to work with isolated files from the VCR system. Objects must be selected manually in a Package structure created in IKAN ALM before starting the Build process. A system external to IKAN ALM which can execute user-created scripts and which is installed on a Machine. IKAN ALM integrates with ANT, NAnt and Maven2. When the Scripting Tool is linked to a Build respectively Deploy Environment it is also referred to as a Build respectively Deploy Tool. The script for executing a Build or Deploy must be stored in the VCR (together with the sources) or in the Script Location on the IKAN ALM Server. A Transporter is used for transporting files and directories between the IKAN ALM server and a local or remote Agent handling the Build or Deploy processes. Therefore, a Transporter must be defined for a specific Machine that is linked to the Build or Deploy Environment. IKAN ALM supports the local FileCopy, remote FileCopy, SecureCopy and FTP Transporters. A Transporter may transport checked-out sources from the Versioning System, a Build result from the Build Archive, but also Custom Phases from the Phase Catalog. 10 IKAN ALM Architecture
11 Version Control Repository (VCR) An external versioning system holding different versions of sources. Related sources are bundled in a Project or subproject (sometimes also called a Module). A VCR Project may contain different development streams, called head (=main or trunk) or branch streams. IKAN ALM integrates with the following VCR s: CVS, Subversion, Microsoft Visual SourceSafe, IBM ClearCase and Serena PVCS. In order to connect to the VCR, a VCR Client must be installed on the IKAN ALM Server and correctly configured. The IKAN ALM Monitor interacts with the VCR by retrieving or tagging sources. The web interface interacts with the VCR to show revision numbers, modified sources, related to a Level Request. For More Information To know more, visit Contact: IKAN ALM Architecture 11
12 Minerva SoftCare GmbH Unterer Dammweg Karlsruhe Tel. +49 (0) Copyright 2013 IKAN Development N.V. The IKAN Development and IKAN ALM logos and names and all other IKAN product or service names are trademarks of IKAN Development N.V. All other trademarks are property of their respective owners. No part of this document may be reproduced or transmitted in any form or by any means, electronically or mechanically, for any purpose, without the express written permission of IKAN Development N.V. IKAN Development N.V. Schaliënhoevedreef 20 A 2800 Mechelen Tel. +32 (0)
HP SAP Where Development, Test and Operations meet Application Lifecycle Management 1 Introduction 1.1 ALM CONCEPTS Application Lifecycle Management (ALM) empowers IT to manage the core application life-cycle,
IKAN ALM and Collabnet TeamForge Where Development, Testing and Operations meet Table of contents Executive summary...3 Problem statement...4 Solution Description...4 TeamForge and IKAN ALM...5 Versioning...5
An introduction to the benefits of Application Lifecycle Management IKAN ALM increases team productivity, improves application quality, lowers the costs and speeds up the time-to-market of the entire application
Continuous Integration Collaborative development issues Checkout of a shared version of software ( mainline ) Creation of personal working copies of developers Software development: modification of personal
IBM WebSphere Administration 8.5 Course ID: Page 1 Last Updated 12/15/2014 WebSphere Administration 8.5 Course Overview: This 5 Day course will cover the administration and configuration of WebSphere 8.5.
Oracle Fusion Middleware Installation Guide for Oracle Team Productivity Center Server 11g Release 2 (188.8.131.52.0) E17075-02 September 2011 This document provides information on: Section 1, "Oracle Team
An Oracle White Paper February 2014 Oracle Data Integrator 12c Introduction Oracle Data Integrator (ODI) 12c is built on several components all working together around a centralized metadata repository.
Software Development In the Cloud Cloud management and ALM First published in Dr. Dobb's Journal, February 2009: http://www.ddj.com/development-tools/212900736 Nick Gulrajani is a Senior Solutions Architect
Software Delivery Integration and Source Code Management for Suppliers Document Information Author Version 1.0 Version Date 8/6/2012 Status final Approved by Reference not applicable Subversion_for_suppliers.doc
FUNCTIONAL PRODUCT OVERVIEW: BOND ENTERPRISE RELEASE AND DEPLOYMENT MANAGEMENT BOND IS A READY-MADE SOLUTION FOR THE RELEASE MANAGEMENT AND DEPLOYMENT OF ENTERPRISE IT SYSTEMS. IT COMBINES PROCESS CONTROL
Jenkins: The Definitive Guide John Ferguson Smart O'REILLY8 Beijing Cambridge Farnham Koln Sebastopol Tokyo Table of Contents Foreword xiii Preface xv 1. Introducing Jenkins 1 Introduction 1 Continuous
Modern Mainframe development and Application Lifecycle Management Cost-effective and easy to implement Enterprise-wide ALM for both mainframe and non-mainframe environments Table of contents Traditional
Providing business intelligence for your software assets IBM Rational Asset Manager Highlights A collaborative software development asset management solution, IBM Enabling effective asset management Rational
Simba XMLA Provider for Oracle OLAP 2.0 April 23, 2013 Simba Technologies Inc. Copyright 2013 Simba Technologies Inc. All Rights Reserved. Information in this document is subject to change without notice.
Efficient Automated Build and Deployment Framework with Parallel Process Prachee Kamboj 1, Lincy Mathews 2 Information Science and engineering Department, M. S. Ramaiah Institute of Technology, Bangalore,
vcloud Automation Center 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions
A guide through the concepts of Serena Dimensions René Steg Steg IT-Engineering, Zurich (Switzerland) Introduction About René Steg and Steg IT-Engineering Owner of Steg IT-Engineering since 2000 and contracted
Software Engineering Theory Software configuration management Lena Buffoni/ Kristian Sandahl Department of Computer and Information Science 2015-09-30 2 Maintenance Requirements System Design (Architecture,
Source Control Systems SVN, Git, GitHub SoftUni Team Technical Trainers Software University http://softuni.bg Table of Contents 1. Software Configuration Management (SCM) 2. Version Control Systems: Philosophy
JobScheduler - Job Execution and Scheduling System JobScheduler Installation by Copying Deployment of multiple JobSchedulers on distributed servers by copying a template JobScheduler March 2015 March 2015
DEPLOYMENT ROADMAP March 2015 Copyright and Disclaimer This document, as well as the software described in it, is furnished under license of the Instant Technologies Software Evaluation Agreement and may
Parallels Panel Contents About This Document 3 Integration and Automation Capabilities 4 Command-Line Interface (CLI) 8 API RPC Protocol 9 Event Handlers 11 Panel Notifications 13 APS Packages 14 C H A
Enhanced Connector Applications SupportPac VP01 for IBM WebSphere Business Events 3.0.0 Third edition (May 2012). Copyright International Business Machines Corporation 2012. US Government Users Restricted
Contents Informatica Corporation Proactive Monitoring for PowerCenter Operations Version 3.0 Release Notes May 2014 Copyright (c) 2012-2014 Informatica Corporation. All rights reserved. Installation...
Converting Java EE Applications into OSGi Applications Author: Nichole Stewart Date: Jan 27, 2011 2010 IBM Corporation THE INFORMATION CONTAINED IN THIS REPORT IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
Apache Karaf in real life ApacheCon NA 2014 Agenda Very short history of Karaf Karaf basis A bit deeper dive into OSGi Modularity vs Extensibility DIY - Karaf based solution What we have learned New and
Implementing Cloud Solutions Within Your Existing IT Environment White paper DECEMBER 2012 Table of Contents Will Your Cloud Fit Within Your Existing IT Infrastructure?.... 3 The Importance of Cloud Management
IGEL Universal Management Installation Guide Important Information Copyright This publication is protected under international copyright laws, with all rights reserved. No part of this manual, including
Open EMS Suite by Nokia Software Development Kit Functional Overview Version 1.3 Nokia Siemens Networks 1 (21) Software Development Kit The information in this document is subject to change without notice
Profiling and Testing with Test and Performance Tools Platform (TPTP) 2009 IBM Corporation and Intel Corporation; made available under the EPL v1.0 March, 2009 Speakers Eugene Chan IBM Canada email@example.com
Open EMS Suite O&M Agent Functional Overview Version 1.2 Nokia Siemens Networks 1 (18) O&M Agent The information in this document is subject to change without notice and describes only the product defined
Siebel Installation Guide for UNIX Siebel Innovation Pack 2013 Version 8.1/8.2, Rev. A April 2014 Copyright 2005, 2014 Oracle and/or its affiliates. All rights reserved. This software and related documentation
Technical Guide Using EMC Documentum with Adobe LiveCycle ES Table of contents 1 Deployment 3 Managing LiveCycle ES development assets in Documentum 5 Developing LiveCycle applications with contents in
Build management & Continuous integration with Maven & Hudson About me Tim te Beek firstname.lastname@example.org Computer science student Bioinformatics Research Support Overview Build automation with Maven Repository
The future of middleware: enterprise application integration and Fuse Giuseppe Brindisi EMEA Solution Architect/Red Hat AGENDA Agenda Build an enterprise application integration platform that is: Resilient
What is Application Lifecycle Management? Increase productivity Stop wasting your time doing things manually by automating every step in your project s Life Cycle At lower costs Get a 30% return on investment
ALM Application Lifecycle Management White Paper Source Code Management Best Practice: Applying Economic Logic to Migration Summary: Is there a Business Case for Migration? Ultimately, what is the value
Automated Process Center Installation and Configuration Guide for UNIX Table of Contents Introduction... 1 Lombardi product components... 1 Lombardi architecture... 1 Lombardi installation options... 4
National Snow and Ice Data Center Supporting Cryospheric Research Since 1976 Continuous Integration and Delivery at NSIDC Julia Collins National Snow and Ice Data Center Cooperative Institute for Research
Maven or how to automate java builds, tests and version management with open source tools Erik Putrycz Software Engineer, Apption Software email@example.com Outlook What is Maven Maven Concepts and
White Paper Deploying Rule Applications with ILOG JRules Deploying Rule Applications with ILOG JRules White Paper ILOG, September 2006 Do not duplicate without permission. ILOG, CPLEX and their respective
ALERT installation setup In order to automate the installation process of the ALERT system, the ALERT installation setup is developed. It represents the main starting point in installing the ALERT system.
W H I T E P A P E R Best Practices for Building Virtual Appliances Table of Contents Objectives.................................................................................. 3 Design Principles...........................................................................
IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent vnext User's Guide - Beta 1 Draft SC27-2319-05 IBM Tivoli Composite Application Manager for Microsoft
CA Workload Automation Agent for Databases Implementation Guide r11.3.4 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the
IBM Campaign and IBM Silverpop Engage Version 1 Release 2 August 31, 2015 Integration Guide IBM Note Before using this information and the product it supports, read the information in Notices on page 93.
Content Server Installation Guide Version 5.3 SP3 July 2006 Copyright 1994-2006 EMC Corporation. All rights reserved. Table of Contents Preface... 11 Chapter 1 Server Installation Quick Start... 13 Installing
This presentation was originally given at DrupalCamp Scotland, 2014. http://camp.drupalscotland.org/ The University of Edinburgh 1 We are 2 of the developers working on the University s ongoing project
Meister Going Beyond Maven A technical whitepaper comparing OpenMake Meister and Apache Maven OpenMake Software 312.440.9545 800.359.8049 Winners of the 2009 Jolt Award Introduction There are many similarities
FileMaker 12 ODBC and JDBC Guide 2004 2012 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker, Inc.
IBM DB2 Universal Database Data Warehouse Center Administration Guide Version 8 SC27-1123-00 IBM DB2 Universal Database Data Warehouse Center Administration Guide Version 8 SC27-1123-00 Before using this
Perforce 2014.1 Defect Tracking Gateway Guide November 2014 This manual copyright 2006-2014 Perforce Software. All rights reserved. Perforce software and documentation is available from http://www.perforce.com.
SIEMENS Teamcenter 11.2 Windows Server Installation PLM00013 11.2 Contents Part I: Getting started with Teamcenter server installation Requirements and overview.............................................
Using DataTrust Secure Online Backup To Protect Your Hyper-V Virtual Environment. 1 P a g e Table of Contents: 1. Backing Up the Guest OS with DataTrustOBM 3 2. Backing up the Hyper-V virtual machine files
Installing and Administering VMware vsphere Update Manager Update 1 vsphere Update Manager 5.1 This document supports the version of each product listed and supports all subsequent versions until the document
Jenkins Continuous Build System Jesse Bowes CSCI-5828 Spring 2012 Executive summary Continuous integration systems are a vital part of any Agile team because they help enforce the ideals of Agile development
PRODUCT SHEET CA Datacom Server CA Datacom Server Version 14.0 CA Datacom Server provides web applications and other distributed applications with open access to CA Datacom /DB Version 14.0 data by providing
RES ONE Automation 2015 Task Overview Task Overview RES ONE Automation 2015 Configuration Tasks The library Configuration contains Tasks that relate to the configuration of a computer, such as applying
Ce document a été téléchargé depuis le site de Precilog. - Services de test SOA, - Intégration de solutions de test. 01 39 20 13 55 firstname.lastname@example.org www.precilog.com End to End Process Testing & Validation:
Talend Open Studio for ESB Release Notes 5.2.1 Talend Open Studio for ESB Copyleft This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about
Change Manager 5.0 Installation Guide Copyright 1994-2008 Embarcadero Technologies, Inc. Embarcadero Technologies, Inc. 100 California Street, 12th Floor San Francisco, CA 94111 U.S.A. All rights reserved.
FileMaker 13 ODBC and JDBC Guide 2004 2013 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker, Inc.
StreamServe Persuasion SP5 Control Center User Guide Rev C StreamServe Persuasion SP5 Control Center User Guide Rev C OPEN TEXT CORPORATION ALL RIGHTS RESERVED United States and other international patents
IBM WebSphere Partner Gateway V6.2.1 Advanced and Enterprise Editions Integrated SFTP server 2011 IBM Corporation The presentation gives an overview of integrated SFTP server feature IntegratedSFTPServer.ppt
Software- und Organisations-Service Open Source Scheduler Architecture and Mode of Operation Software- und Organisations-Service GmbH www.sos-berlin.com Scheduler worldwide Open Source Users and Commercial
Feith Rules Engine Version 8.1 Install Guide Feith Rules Engine Version 8.1 Install Guide Copyright 2011 Feith Systems and Software, Inc. All Rights Reserved. No part of this publication may be reproduced,
Lucid Key Server v2 Installation Documentation Contents System Requirements...2 Web Server...3 Database Server...3 Java...3 Tomcat...3 Installation files...3 Creating the Database...3 Step 1: Create the
FreeSB Installation Guide 1. Introduction Purpose This document provides step-by-step instructions on the installation and configuration of FreeSB Enterprise Service Bus. Quick Install Background FreeSB
TIBCO ActiveMatrix BusinessWorks Plug-in for TIBCO Managed File Transfer Software Installation Software Release 6.0 November 2015 Two-Second Advantage 2 Important Information SOME TIBCO SOFTWARE EMBEDS
Instant Chime for IBM Sametime For IBM Websphere and IBM DB2 Installation Guide Fall 2014 Page 1 Copyright and Disclaimer This document, as well as the software described in it, is furnished under license
Automated Data Ingestion Bernhard Disselhoff Enterprise Sales Engineer Agenda Pentaho Overview Templated dynamic ETL workflows Pentaho Data Integration (PDI) Use Cases Pentaho Overview Overview What we
1 sur 6 05/08/2014 14:17 ORACLE.COM TECHNOLOGY NETWORK PARTNERS STORE SUPPORT (Sign In / Register for a free DownloadsDocumentation Discussion Forums Articles Sample Code Training RSS Resources For PRODUCT
ODEX Enterprise Introduction to ODEX Enterprise 3 for users of ODEX Enterprise 2 Copyright Data Interchange Plc Peterborough, England, 2013. All rights reserved. No part of this document may be disclosed
Table of Contents Overview Defects aren t the only shared artifact Methods of sharing artifacts among systems Using Tasktop Sync The Quality Management System as a Dashboard 1 2 2 3 4 Overview The testing
Front cover Enabling Mobile Apps with IBM Worklight Application Center Hands-on guidance for installing, configuring, and using Worklight Application Center Guidance for Android, ios, and Blackberry Integration
Quest InTrust Version 8.0 What's New Active Directory Exchange Windows Abstract This document describes the new features and capabilities of Quest InTrust 8.0. Copyright 2004 Quest Software, Inc. and Quest
Talend Platform for Data Management Installation and Upgrade Guide 5.2.1 Talend Platform for Data Management Adapted for v5.2.1. Supersedes any previous Installation and Upgrade Guide. Copyright 2008-2012
SAS Marketing Automation 4.4 Unix Install Instructions for Hot Fix 44MA10 Introduction This document describes the steps necessary to install and deploy the SAS Marketing Automation 4.4 Hot fix Release