API Integrator, defined to create a task flow, is a chain of one or more tasks.

Task Flow Manager provides users with the ability to create these tasks visually, quickly and easily.

This section describes the server configuration required to be able to create tasks with the Apinizer API Integrator.

In order to activate and use the API Integrator or Task Manager product, it must be available in your license.

Configuring Server Settings for API Integrator Environment

First of all, if your language has an API Integration module, the configuration option will appear as follows.

After activating the configuration, click the Configure button.

Enter the necessary information for the deployment in the window that opens and click the Apply button.

Disabling its configuration will delete the namespace running on kubernetes and all the resources in it.

The image containing the server settings is given below:

The fields used for server configuration are shown in the table below.




It corresponds to the pod name of the created integration on the K8s.

Access Url

An external access address is written to the integration.

API KeyIt is the API Key information that will be used in the request to be made for the integration.


Equivalent to ReplicaSet in Kubernetes Cluster. Specifies the number of servers.

CPUThe maximum number of CPU cores that the pod will use is entered.


Enter the maximum memory capacity that the pod will use.

Memory Unit

The unit of memory is selected; MB, KB.

Service Port

It is the port information required to access the services running in the application.

Additional Variables

Default and optional variables and their values to be run in the pod are defined.

Host Aliases

If Host information will be used instead of IP address, Host Nickname(s) can be entered.

The following warning should be taken into account when configuring the Java Options setting in the additional variables area;

Please note that the -Xmx and -Xms settings disable automatic heap sizing.

Apinizer sets the JVM Heap values to use 75% of the memory allocated to the container because it runs inside the container.

UseContainerSupport is enabled by default.

Old (and somehow broken) flags -XX: {Min | Max} RAMFraction is now deprecated. There is a new -XX:MaxRAMPercentage flag that takes a value between 0.0 and 100.0 and defaults to 25.0. So if there is a 1GB memory limit, the JVM heap is limited to ~250MB by default.

Click for detailed information.