Impact of instance command execution on Adobe Campaign Classic - Refresh for deliverability

[GayatriBa1]

We have created a project in Adobe Admin console and want to run below instance command. We are having on-premise instance.

Command: nlserver config -instance:<instance_name> -setimsoauth:ims-org-id/client-id/technical-account-id/client-secret.
But before executing above command, we would like to understand certain things as our instance name is same for lower & production environment. Last time when we executed this command in lower environment it also affected the production environment.

1-Can you please help us in understanding the impact of running instance command?
2-What will happen if the command works successfully?
3-What will happen if the command doesn't work? What all parts in Adobe Campaign Classic it can affect?
4-If we stop the services of production environment and execute this command in lower environment, will it still affect the Production? If yes, then how we can avoid this?
5-What all areas of Adobe campaign classic this command can affect?
6-What changes will be done to config files?
7-Refresh for deliverability workflow is failing for 2 years so what was impact till now?
8-Do we need to roll back to previous environment if workflow still fails after execution of instance command?
9-If executing his command in lower environment and workflow works in prod as well, do we need to run command again for prod?
10- Do we need to perform any kind of testing if command execution is successful & workflow executes without error? 

[Parvesh_Parmar · Accepted solution]

Hi,

This workflow downloads the deliverability rule.

Normally, you need to set up a project in your developer console and configure the client ID in the config file.

When I tried this, it worked fine without any issues. I recommend running it in a lower environment first, and if it works, proceed with production. You can use the same command across all your environments.

Best regards,

Parvesh