Installing Figaf DevOps Suite on your PC

Installing Figaf DevOps Suite on your PC


Installing Figaf DevOps Suite on your PC

In this section tutorial, we show how to install Figaf DevOps Suite on your PC for a PoC. Mac would be much the same except the script should be a little different command to start the tool with. 



Requirements for a PoC

  1. Windows/Mac 
  2. 2 GB Ram free
  3. 2 GB Disk
  4. Java 8 either oracle or adoptium


The installation comes with a build-in database, but if it is not suited for productive use, then use Postgresql or MSSQL database. 



1. Go to Figaf.com/devops

2. Enter name and email to get a trail license

3. Check the email you registered with to check for the license


4. Go to the download site, https://figaf.com/trial/download-page/  

5. Scroll down to the download section and download the file "irt-22*.jar"

6. Save it in a folder on your computer

7. Create a new file in notepad, notepad++  or your favorite editor

8. On the install page copy the following content

9 Paste the values into your bat file.

Check the file name and make sure it is the same as your have in your folder. 

10. Save the file in the same folder as your file. Call it "run.bat".

Notepad can have a hard time saving as a  BAT file

11. Run the BAT file. This should start the tool in a command prompt

You can also see a log file

Note: Here are possible errors to look out for at this step

If you do not have Java the command will not work. You will need to install a java see above and then update the bat file with content. 


If you have run Figaf before you may have a file in c:\users\<USER>\FigarIRT delete this folder to reset everything and start over

Information to terminate the tool and find the command prompt and press CTRL-C to start the termination. 

It can take a little while before it reacts try a few times. 

You want to terminate like this to ensure the database is persisted correctly. 

13. Wait for 30-60 seconds to see

14. Open "http://localhost:8089/irt/" in your internet browser

15. fill in email  prompt with "superUser" and password  with "default". Press "login"

16. Press "close" on the password switch. 

If you decide to change the passwordremember it because the password cannot easily be recovered.

For a productive scenario, do change the password and save it in your password save. 

17. Now you are on the front page of the application

18. Click on  "Load license"

19. Insert your license from the email and press "load license"

20. Now you have Figaf running. Now you can add agents to connect to systems

SAP CPI agents

SAP PI agents (coming later)

 


    • Related Articles

    • Onboarding/Installation (Figaf DevOps Suite - Cloud Version)

      In this mission you will see how to connect to your SAP Cloud Integration system.   1) Open the email you have received 2) Click on the link to open the page and enter a new password 3) Now you are in the Figaf Tool The screen may change a little ...
    • Requirement before installation

      We recommend the following prerequisites Registration for a trial at figaf.com/devops so you will get a license key Download the Figaf runtime jar file at irt.figaf.com/download. Have a server/laptop with 8Gb of memory. Figaf can run on a laptop but ...
    • How to download logs from Figaf app in SAP BTP

      SAP BTP cockpit allows accessing only the last 1000 lines of logs. Sometimes it's enough for debugging but in most cases, it's not. So there is a way to download all needed logs directly from the app. First of all, you need to execute next two ...
    • Deploy to SAP BTP, Cloud Foundry

      This article describes how to deploy the Figaf tool to CPI BTP, Cloud Foundry. Install "cf" command on your computer https://github.com/cloudfoundry/cli/wiki/V7-CLI-Installation-Guide#installers-and-compressed-binaries. Log in to your SAP BTP account ...
    • Installation

      Here you can find an example of the structure that you need to have to run the Figaf IRT application. This is just an example and you need to put your own values if you have another jar version, DB credentials, etc. There are two ways of how to ...