Phil Parkin (9/30/2016)
quinn.jay (9/30/2016)
John Rowan (9/30/2016)
All you need are the .dtsx files. If you need to open them in a solution for editing, create a new project in Visual Studios, start a blank project, right-click on the SSIS Packages folder in the Solution Explorer, and select 'Add Existing Package'. Then you have them in your solution for editing.Thanks, this helps. So as I learn, the next price I have to understand that you said was to place it where it is viewable by the Server Agent, and I'm not so sure what or how to assure that. I'm going to copy the .dtsx files to the share drive and step through what you outlined.
If you are on a recent version of SSIS, this is not necessarily true. Instead, packages can (and, I would argue, should) be grouped into projects in VS and then deployed to SSISDB. Setting up a SQL Agent job to run packages deployed this way is trivial.
Yes, this is absolutely true for project deployment, but it seemed from the OP's original post that this was all file system deployment. This does bring up the point that maybe he should completely reconsider their package deployment strategy and get away from file system deployment. Google SQL Server SSIS Deployment Model and you'll get a bunch of info that could help you make your decision.