The package deployed to SQL Server can be queried and manipulated through the API provided by SSISDB

After deploying to SQL Server using Project Deployment model, SSISDB is responsible for managing this project,

Reference documentation url:integration Services Language Reference

Https://msdn.microsoft.com/en-us/library/dn198335.aspx

This section describes the Transact-SQL API for administering integration Services projects that has been deployed to an instance of SQL Server.

Integration Services stores objects, settings, and operational data in a database referred to as the integration Services Catalog. The default name of the integration Services catalog is SSISDB. The objects that is stored in the catalog include projects, packages, parameters, environments, and operational histo Ry.

The Integration Services catalog stores its data in internal tables that is not visible to users. However it exposes the information that's need through a set of public views so you can query. It also provides a set of stored procedures that's can use to perform common tasks on the catalog.

Typically manage integration Services objects in the catalog by opening SQL Server Management Studio. However you can also use the database views and stored procedures directly, or write custom code that calls the managed AP I. Management Studio and the managed API query the views and call the stored procedures that is described in this section To perform many of their tasks.

The package deployed to SQL Server can be queried and manipulated through the API provided by SSISDB