AMF (Agile Messaing Framework)
  • Agile Messaging Framework
    • Get Started
      • Install
        • Pre-requisites
        • CockroachDB
        • NATS for Queuing
        • Hashicorp Vault
          • Configure Vault
        • Python 3.9
        • AMF Bundle
        • Installation of AMF
          • Configure and install
          • Post Install Steps
        • IBM SFG Integration
          • Configure and Install
            • Install jars in SFG
            • Add amf.properties
            • Add CRDB pool details
            • Import Sterling Artifacts
          • Post Install Steps
            • Create user with API permissions
            • Changes in BPs
    • Concepts
      • Providers
      • Users
      • Message Type
      • Message Mapping
      • Workflow
      • Communication profiles
        • SFTP Profiles
          • Customer Initiated
          • MFT Initiated
            • MFT Initiated Send
            • MFT Initiated Receive
        • Connect Direct
          • Customer Initiated
          • MFT Initiated
        • SharePoint
          • MFT Initiated
            • MFT Initiated Send
            • MFT Initiated Receive
        • S3
          • MFT Initiated
            • MFT Initiated Send
            • MFT Initiated Receive
        • Azure ADLS
          • MFT Initiated
            • MFT Initiated Send
        • HTTP with Token
          • MFT Initiated
            • MFT Initiated Send
        • UFA
          • Customer Initiated
            • Customer Initiated Send
            • Customer Initiated Receive
      • Communication Rules
        • Immediate
        • Scheduled
    • Management
      • AMF UI Operations
      • AMF Services Operations
    • User Manual
      • Signup and Login
      • Dashboard
      • Track N Trace
        • Message Activity
        • Failed Message Activity
        • Onboarding Activity
        • Session Activity
        • Service Availability
        • Scheduler Activity
        • Delivery Queue
        • Audit Log
      • Onboarding
        • Customers
        • Users
          • Communication Profiles
        • Message Types
        • Message Mapping
        • Workflow
          • Definitions
          • Actions
          • Rules
        • Communication Rules
    • Troubleshooting
    • Tutorials
      • UFA Installations
        • Linux Installation
        • Windows Installation
      • Schedules
        • Run based on timer
        • Run daily
        • Run based on day(s) of the week
        • Run based on day(s) of the month
      • UseCases
        • UC01
        • UC02
        • UC03
        • UC04
        • UC05
        • UC06
        • UC07
        • UC08
        • UC09
        • UC10
        • UC11
        • UC12
        • UC13
        • UC14
        • UC15
        • UC16
        • UC17
        • UC18
        • UC19
        • UC20
        • UC21
        • UC22
        • UC23
        • UC24
        • UC25
        • UC26
Powered by GitBook
On this page
  1. Agile Messaging Framework
  2. Tutorials
  3. UFA Installations

Linux Installation

PreviousUFA InstallationsNextWindows Installation

Last updated 2 years ago

Use Case: Install UFA agent in Linux environments.

Linux Installation Steps:

  1. Create a User with Provider type as AMF (Agile Messaging Framework).

  2. Create UFA config and assign to the user created in step 1.

  3. Download the agent software and copy to the respective system.

  4. Install the agent and verify the status in Service availability screen.

Linux Installation Process:

  1. Create a User with Provider type as AMF

  • Login to AMF

  • Go to Users page under Onboarding

  • Click on + icon in the top right corner

  • Select Customer and give details of PartnerA, select UserType, AuthenticationType and click next.

    1. UserType: Which Zone does the Partner belongs to send or receive files? (DMZ or Trusted)

    2. AuthenticationType: Where do we store the Partner credentials? (LDAP or local (SFG/AMF) or Both)

  • Select the provider the Partner belongs to and click next

    1. AMF: AMF provider is used to onboard Partners which use UFA.

    2. IBM: This will come from the provider's config. We can choose several types based on the provider's config.

    3. OpenLdap: We need to select this if we selected the AuthenticationType as LDAP in the step d-ii.

  • Verify the Partner details and click Onboard User.

Note: We can also use existing users if we have any

2. Create UFA config and assign to the user created in step1.

  • Go to UFA page under configuration

  • Click on + icon at the top right corner

  • Give details of the UFA agent

  • Click Save after giving the below details.

    1. Ufa User: Partner name which this agent belongs

    2. Host Name: Host/IP of Partner system where UFA agent will be installed.

    3. Operating system: Operating system type of Partner

    4. OS Type: Weather its 64 or 32(X86) bit system

    5. UFA Version: Option to choose different version (Version 2.0 by default)

    6. Assigned To: Admin user who will operate the agent installation

    7. Log Level: Log level for the UFA agent logging

    8. UFA Type: Where the UFA was installed (In DMZ or Trusted Zone)

3. Download the agent software and copy to the respective system:

  • Go to UFA page under configuration

  • Click on Download Icon for the UFA agent that we configured earlier

  • Copy the Zip file to respective Linux box

  • Unzip and give executable permissions to the ufav2_linux

    $ chmod +x ufav2_linux (Command to give executable permissions)

4. Install the agent and verify the status in Service availability screen

  • Install the UFA agent using the below command

$ ./ufav2_linux

  • Agent was successfully installed in Linux.

  • Go to Service availability under Track N Trace

  • We can see the UFA agent status as Active

Graphical user interface, text, application Description automatically generated