Get insights and control over your software development -and deployment processes, automate your tools, connect your teams, and standardize your workflow.
IKAN ALM is a highly customizable framework to implement DevOps (Continuous Integration, Continuous Deployment) and Toolchain Orchestration in mainframe, distributed and mixed environments.
Supported environments include: SAP, z/OS and ODI, but you can also use IKAN ALM to create a custom DevOps solution.
More details:
Automated Build
Release -and Package-based builds (Distributed and Mainframe). You can have continuous integration, scheduled or forced builds. Every build is stored in a build archive.
Automated Deployment
The automated deployment process moves the package or release to the appropriate Test or Production environment. That is done using pre-de?ned, yet customizable Deploy scripts which we call "Solution Phases".
Approvals & Notifications
You can make your deployments pre- or post-approval based, and you can also get notified by mail of any successful or failed build or deploy.
Toolchain Orchestration
Choose your preferred tools, to be integrated in your automated lifecycle. Based on the outcome of your tools (passed or failed) a next action will be executed and the information will be logged.
Compliancy and Security
Support for process standards (enterprises with strict regulations): CMM, ITIL, Six SigmaTM, Sarbanes-Oxley.
Compliancy and Security
User Access Control is handled by your company’s own security system: Active Directory, LDAP, Kerberos.
Standard tool integrations
Version Control Repositories: Git, TFVC, Clearcase, Subversion, CVS,...
Issue Tracking: JIRA, HP ALM, Collabnet, TFS,...
Enterprise-wide
Server/Agent architecture will offer you the needed flexibility and scalability.
Web-based interface
A multilingual web-based interface allows you to control your application life cycle from within your browser.
On-premise and Cloud supported
Platform -and environment independent
Runs on Linux, Unix or Windows and supports different development environments. Even if your applications have a distributed front-end (Java, .NET,...) and a Mainframe back-end: you can manage and release all your applications with the same application. Mix it however you like.
