Installation

Figaf Tool is a web application that you install once and run against your own database, either on a machine of your own or in SAP BTP.

You can also read Installation on Windows or Linux to learn how to install and configure Figaf Tool.
Here you can look for articles with explained configurations and use cases.
New to Figaf Tool? Exploring Figaf is a guided introduction to the DevOps Suite that you can follow before installing anything.
If you have some question, please contact us by this email: [email protected].

Application components:

You can download application component from the following page: https://irt.figaf.com/download

  • irt-<version>.jar - Figaf Tool web application.

  • irt-agent-<version>.sca - (optional, only for PRO systems) this is the Agent Module. Install it on all SAP PI/PO systems where you are going to use Figaf Agent Module integration type. It’s not required because you can choose ICO Logging or SAP Log Module integration types.

The web application is also published as a Docker image, figaf/app, on Docker Hub.

To get the latest update about new functionality be sure to sign up to https://figaf.com/figaf-devops-tool.

1. Choose how to run Figaf Tool

The same application is distributed three ways. They differ in what you have to install and operate yourself, not in what the tool can do.

Local application running

You run the jar file with your own Java runtime, on a Windows or Linux machine you control. This gives you the most direct access to the instance and its libs folder, and it’s the only option where you manage the Java version yourself.

Docker container running

You run the figaf/app image as a container, anywhere Docker runs. The Java runtime comes with the image, and configuration is done with environment variables instead of command-line parameters.

SAP BTP deployment

You deploy to the Cloud Foundry environment of SAP BTP, next to the SAP systems Figaf Tool works with. SAP BTP provides the database and handles authentication, and there’s no server for you to maintain.

All three need a database and a license key, and all three are configured the same way once they’re running.

2. Versioning

Since 2101 release the following versioning concept is applied:

<global version number>.<patch version number>

Where

  • <global version number> - is a release date, has YYMM format where YY is year and MM is month.

  • <patch version number> - includes bugfix or minor updates of global version number.

3. Next steps

  1. Check the requirements for the machine you will run on.

  2. Run the application against your database, in the way you chose above: from the jar file, as a Docker container or on SAP BTP.

  3. Install the license.

  4. Configure an agent for each SAP system.

If something goes wrong, see Installation troubleshooting. To remove Figaf Tool again, see Uninstallation.