Description:
During Archive Scaling, the existing deployed application instance will stop and restart before scaling up. This is the behavior observed in non Silver Fabric that is the Classic environment as well.
Symptoms:
While Archive is scaling up, if there is a running application for that archive already on TIBCO administrator, even those non scaled application will stop and restart. This is the behavior observed in non Silver Fabric that is the Classic environment as well.
Cause:
In TIBCO Administrator, when adding a new instance of the archive, the original setting for the initial archive's FTmode is set to true. As we don't want FTmode, we need to change the setting to non FT mode manually. This will change the deployment configuration of the service instance and it will be redeployed (and restarted). The second time, as the setting is already set to non FTmode, they won't be changed and won't be redeployed. In non SF classic TIBCO Administrator, deploy an archive, then add the the same archive to a new machine in non FTmode and redeploy. This is similar to archive scaling up in Silver Fabric world. You will see the first service instance will be redeployed as well.

During Archive Scaling,the running application instance (non scaled archive) will also stop and restart before scaling up.

The following is the workaround you may need to use until we get the fix from TIBCO Administrator and that will eventually resolve the Silver Fabric behavior.

- Deploy the archive using AppManage, not TIBCO Administrator (basically to change the value of isFT to false before deploying).

Eg:

   ./AppManage -export -out bw1par-5.xml -genEar -ear bw1par-5.ear -app bw1par-5 -user <user> -pw <pw> -domain <yourdomain>
    in the XML file you have the <isFt> set to false.

- Then if you delete the application you just created in TIBCOAdmin and then when the archive scale up is activated, it won't redeploy the original BW service instance. (By this step the isFT default setting is changed to false so further archive scaling up or adding will not affect the running application archives).

OR

- When you create the deployment configuration via TIBCO Administrator, add another instance to a machine in non FT mode. Save it, then remove the added service instance to the machine and save it. The isFT mode will be set in non FT mode and the service will not restart.