SSIS - Change Config File Path LOCATION in SQL Agent Job Step (NOT USING DTEXEC)

Question

SSISers;
I am not new to ssis but am trying to deal with promoting of ssis config files differently for a specific project. We are using SQL 2008 R2.
As a standared pattern used for years, we just use SQL Agent, build a job step for the ssis package, add the ssis package as SQL Integration Services Package type from fileshare (not using Integration Services), and add the necessary production
config files in the configutation tab of the job step. Easy.  We do not execute our packages with DTEXEC command line.
A new project has the developers leaving the config files in the package - not removing the config files for deployment. Is there a way to override JUST THE CONFIG FILE PATH LOCATION in the job step for ssis package? Remember, we are NOT using dtexec. 
I was told that /SET might do it but I do not see a good example anywhere of hooking this in and how it works for a CONFIG FILE PATH LOCATION - I see variable overrides but not CONFIG FILE PATH LOCATION. The packages were written with Absolute config file
path and not Relative path.
Please understand that my goal is to let them leave the packages as is, we move the config files to the production sever and all we have to do is flip the location of where the config files are sitting for the ssis pacakge to look for them.  We would
rather NOT have to use DTEXEC command  line with the job step for reasons that I do no need to get into on this forum.
Any suggestions are appreciated.

Answer 1

Hi mg30,
There is no way to overwrite the XML configurations file just through modifying the SQL Server Agent job steps.  The Dtexec utility will apply the default package configurations for the second time after applying the options specified in the command
lines or other package configurations configured in the job step.
If the package is not deployed/installed, the Dtexec utility looks for the XML configurations file according to the file path defined in the Package Configurations Organizer window. In this situation, you need to either disable the package configurations
or modify the XML file path in the BIDS.
If the package is already deployed/installed, you need to modify the package as above or re-specify the install folder for the package configurations file. 
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support