The Figaf tool offers comprehensive capabilities for managing SAP Integration Suite (IS) as a DevOps solution, with a significant focus on the transport process. The primary goal is to make the process from development to production support faster. A big part of this is our transport tool.
Core Transport Process
Figaf facilitates the transport process by:
- Synchronized Objects and Versioning Figaf maintains synchronized versions of integration artifacts within its own database, enabling robust versioning. This ensure proper handling of ticket.
- Ticket-Based Development When development begins or is completed on an integration, changes can linked with your ITSM tool like Jira or Cloud ALM”.
- Integrated Testing Changes associated with a ticket can be tested directly within the Figaf tool.
- Transport Creation and Deployment: Transports can contains configuration of external parameters making it possible to import, configure and deploy in one action.
- Documentation of changes: Precise tracking of all artifacts and transports to ensure it is know what is being transported and documented. This allows users to track all changes.
Landscape Management Figaf simplifies the management of complex integration landscapes through:
- Virtual Tenants This feature addresses the challenge of managing numerous iFlows by allowing attributes to be prefixed (e.g., QA_) when moved to a QA environment. This is what developers normally are doing but with Figaf you can add governance.
- Git for extra validation: It is possible to use git based services and integrate it to the validation. Figaf will automatically replicate all iflows to a git repository that can be used to improve development experience, but not designed for normal git workflows.
- Rules and Automation within Transports The Figaf tool allows for the definition of various rules to automate and control the transport process:
- Approval and Import Permissions You can define who is authorized to approve transports and who can import them into the production environment.
- Parameter Mapping Rules The tool simplifies the management of technical objects and iFlow names by automatically translating externalized parameters (e.g., hostnames) between environments, making transports more resilient and saving time. It also ensures that iFlow names are unique across tenants in production.
- Automated Deployment An option to deploy automatically after transport is available.
- Naming Validations The tool supports adding naming requirements for transported items.
- Transport Validation Tags Warnings can be generated for XSLTs, and transports can be denied or allowed based on specific tags.
- Notifications Figaf can send email notifications to specific individuals or trigger webhooks (preferably to Integration Suite for routing to backend systems) to inform about landscape activities, such as imports or ticket creation.
Managing Transports and Design Reviews
Figaf provides several features for architects to approve transports with two eye principle.
- Landscape Overview The landscape overview displays differences between configured and deployed iFlow versions, helping to identify discrepancies in productive systems.
- Configuration Management The tool supports automatic replacement of configuration values (e.g., hostnames) and helps identify missing security artifacts like OData passwords across tenants.
- Design Guideline Checks The tool assists in checking Design Guidelines .
- Diff and Viewer Tools Figaf includes various viewers, such as a BPMN model viewer that shows where two iflows differs.
- Excel-based Sanity Checks For large transports, configurations can be exported to Excel for sanity checks and then re-uploaded with changes.
- Approval Process Transports can be sent for approval including configurations.
- Deployment and Monitoring After approval, items can be scheduled for import and deployed to the Integration Suite. The tool monitors deployed items and shows warnings if design time versions differ from deployed versions.
For small and large customers
Figaf is created for both small and large customers.
- Large clients
- The ability to have both support and project landscape in one landscape
- Replication between two tenants prod and failover, so each time an iflow is deployed on production it is automatically moved and configured the same way on failover tenant.
- Transport to multiply production system. You can add a transport to multiply productive systems for geographical or regional distribution.
- Governance
- Small clients
- Enjoy the fact they can use Non prod for both Dev and Test without sacrificing governance.
- Faster development
End-to-End Process
Figaf tool is about empowering users to be more productive allowing them to develop faster while improving the transport process. While improve the quality and documentation.