Resolution:
Unlike TIBCO Administrator, there is a limitation in the current AMX versions. After uploading the service and assigning GV/Substation variables to the service, the values will remain the same when you assign the services across different nodes. These values cannot be edited at the respective node level.

The second limitation is that you cannot upload the same SAF into the AMX Admin console as it results in a namespace collision error.

Workaround and Steps :

Add the following FT properties defined in bwengine.xml which is under BW_HOME/lib/com/tibco/deployment/directory and restart the Designer before EAR creation. For deploying BW engines in DQ, declare a global variable for a CMQ Name which can be substituted during deployment.

# FT related properties
Engine.FT.UseFT=true
Engine.FT.Weight=100
Engine.FT.HeartbeatInterval=3000
Engine.FT.ActivationDelay=6000
Engine.FT.ActivationInterval=10000
Engine.FT.GroupName=RUDRA.xyz
Engine.FT.Subject=TEST

#FT transport, set these properties if non-default FT params are used.
Bus.Default.Service=6532
Bus.Default.Daemon=tcp:6532
Bus.Default.Network=

After EAR creation, in Business Studio at the composite level, create multiple BW components based on the number of instances you would like to deploy, referring to the same imported EAR file. Once you upload the SAF, these components will appear as services which can be associated to the Nodes. Assign the FT transport/CMQ Group Names values using Substitution and GVs for these instances.