Instances
Create the Instance
These steps are used to create an Instance in the Axual Self-Service.
We are writing the steps
to create a dta
instance using the local
cluster created in the previous step.
-
Open the
instances
menu and press theAdd instance
button -
Provide the Instance Details and press the
Continue
button-
Put
Dev Test Acceptance
as the Name -
Put
dta
as the ShortName -
Put
DTA Instance
as the Description
-
-
Press the
Select cluster
buttonDo not fill the Instance Manager URL field, this field is for older installation. It will be removed in future releases. -
Select the
local
cluster -
Provide the Schema Registry Credentials for this Instance/Cluster
-
Put
http://axual-axual-schema-registry-master:20000/
as the Rest Endpoint -
Select
No Authentication
as the Authentication Method
-
-
Verify the Schema Registry details by pressing the
Verify
button -
Once verified, you can press
Add listeners
button to add Schema Registry Listeners. This step is optional.-
Input
TLS
as the Protocol -
Input
localhost:25000
as the URLSchema Registry Listeners is a set of protocol:URL pair for setting various Schema Registry Listeners. They are used by the Kafka Clients to connect to the Schema Registry. You can add more listeners and there are no validation on our side.
-
-
You can close the Instance/Cluster modal by pressing the
Select Cluster
button -
You can click on
Show full configuration
to validate the selected cluster details -
You can close the full configuration modal
-
Enable the Authentication Method for this Instance
-
Toggle the
SSL (MUTUAL TLS)
-
Upload the Signing CA used to sign your application certificate
-
-
Press the
Add Instance
button
Now you have successfully created an Instance in the Self-Service

Environment Mapping
This setting allows Tenant Admin to enable or disable mapping environments under an Instance regardless of whether the user is an Environment Author.
When enabled, Environment Author can create an environment under that Instance.
When disabled (which is the default), creation of an environment under that Instance is not allowed regardless of whether the user is an Environment Author.
If Environment Mapping is disabled for Instance 1
then:
-
No user can create a new Environment using
Instance 1
-
No user can update an Environment to use
Instance 1
-
No user can update an Environment using
Instance 1
to use a different Instance
To enable environment mapping for an Instance
-
Log in as a Tenant Admin.
-
Move to the Instance page.
-
Select the Instance.
-
Click Edit Instance button.
-
Under
Governance Settings
, click on theEnvironment Mapping
toggle -
Click Update Instance button.
You can also enable environment mapping when creating an instance from the create instance page. |
Granular Stream Browse Permissions For An Instance
Granular stream browse permissions allows Tenant Admin to have an instance level access control over topics configured on all environments mapped to it.
When enabled, all environments in the instance will support granular authorization.
When disabled (which is the default), all environments in the instance have the same authorization for both stream configuration and browse, which means there is no granular browse permission applied over a topic.
To enable granular stream browse permissions for an instance
-
Log in as a Tenant Admin.
-
Move to the Instance page.
-
Select the Instance.
-
Click Edit Instance button.
-
Under
Governance Settings
, click on theEnable granular stream browse permissions
toggle -
Click Update Instance button.
Disabling granular stream browse permissions on an instance that had it enabled leads to deleting of all existing Permission Groups. |
You can also enable granular stream browse permissions when creating an instance from the create instance page. |