Search results

Your search returned following contents:

Choose your product

FRENDS⁴ On-prem

FRENDS⁴ has over 25 year's track record for being an exceptionally powerful but easy-to-manage integration platform. Dozens of active customers are using it for solutions and integration needs both large and small. Brokered message and agent architecture ensures that your integrations are always online and not dependent on other services.


FRENDS⁴ supports native cloud installation out-of-the-box. There are two options with the cloud: use FRENDS⁴ exclusively from the cloud (iPaaS) or install the FRENDS⁴ Agents to your on-premise servers (a hybrid model). The cloud enables low entry-level costs and attractive pricing opportunities, without the hassle of purchasing integration hardware.


FRENDS⁴ allows you to easily create automation processes or automation services. Follow the paths below for more information.

Process path

Define the process

Define the business needs and the purpose of the process. The definition can range from the simple transfer of a single file to the complex management of a whole invoicing system.

The definition phase of building the process is usually done outside of FRENDS⁴ with an advanced BPMN tool or with more conventional pen and paper.

Define FRENDS⁴ tasks

Once you know what your process needs to achieve, identify the FRENDS⁴ tasks to use in the process. FRENDS⁴ Tasks should clearly match with the logical operations of the process.

If an existing FRENDS⁴ task can’t fulfill the needs of the process out-of-the-box, HiQ will implement a new generic task to tackle the problem.

FRENDS⁴ also offers an additional library of more specialized tasks with a fixed price to speed up development times.

Build and configure

Build the process using the FRENDS⁴ Iron Process Builder tool. Add the required tasks to a canvas and then determine the execution order, decisions and fault operations.

Now that your process scaffolding is in place, define parameters for each of the tasks. For example, a simple file transfer task needs the location of the source file and the destination of transfer.

Each task is configured by simply clicking on it, which brings up the configuration menu with available parameters and possible configuration settings offered through predictive input.

Finalize and activate

Finally, define the schedule and/or conditions when your process should be run by adding triggers to the process. Most common triggers include scheduling trigger or for example a file trigger.

All the triggers contain similar configurable parameters as tasks, for example a schedule could be configured to only run on weekdays at 18:00 except on banking holidays.

Service path

Define the service

Identify what you need the service to do and whether it should receive an input from the user and return an output.

This is the most basic step in designing any service based solution. As such non-functional requirements should be clear at this time as well to identify for example required response times and possible logging and alert behaviour.

Define FRENDS⁴ tasks

Identify which FRENDS⁴ tasks to use in building the service. This means that you should split the service into manageable parts and select the appropriate FRENDS⁴ tasks for each part, from the existing list of FRENDS⁴ tasks.

If a task that you require doesn't yet exist HiQ will implement said task for you.

Splitting the process into different parts can usually contain tasks such as validating the request, selecting variables from the request for later use, accessing a database based on the variables and constructing a response message.

Assemble and configure

Create the service scaffolding using FRENDS⁴ Iron Process Builder tool. Configure each task with execution parameters, so that each task knows what its supposed to do inside the service.

You need to also specify what kind of input or output your service is going to have and to specify how that output is used by the tasks in your service.

Each task is configured by simply clicking on it, which brings up the configuration menu with available parameters and possible configuration settings offered through predictive input.

Publish the service

Publish the service, so that consumers can start using it. Decide the way your service is to be exposed using SOAP or a simple HTTP REST protocol, in the cloud or on premise and choose an authentication method.

After this step your service is ready for use by clients at the specified URL.

Both paths can be executed with any of the delivery models:

FRENDS has been a synonym for cutting-edge integration for over 25 years. To learn how FRENDS has simplified some of our customers’ business processes, visit the Cases page.

Read FRENDS Case Studies