isNeatPublish Scenarios

Below is a list of options that are available to allow a flexible range of implementations.

Importing SSIS project file (.dtproj) Vs Importing SSIS deployment file (.ispac)

The population of details in the isNeatPublish.XmlGenerator UI depends on the desired deployment approach

  • If it is desired to deploy the compiled .ispac file (along with complementary details) directly, import the .ispac file. This approach has the benefit of deploying one compiled file. Because the .ispac file contains all of the details of the package(s), and parameters to be deployed these cannot be changed within the deployment process and hence these areas of the isNeatPublish.XmlGenerator interface will be disabled. Also, there is only one environment that can be deployed to
  • The alternative is to import the .dtproj file which imports the package and parameter names as well as build configuration information (which among other details represents environment(s)). This approach allows more flexibility in so far as multiple environments can be deployed at once. On deployment the SSIS packages are compiled and environments created depending on the isNeatPublish.XmlGenerator XML configuration file

Different Configurations

Different environments (eg. Development, UAT, Staging, ModelOffice, PreProduction, Live/Production, etc) will generally require database connection strings (data sources), target (and sometimes source locations), etc. isNeatPublish supports placing all environments into the one configuration file or, if desired separate configuration files for each environment

SQL Agent Jobs

When the SSIS packages are deployed and parameters/environments are setup, there are several ways to execute the SSIS packages. To fully automate the running of the deployed SSIS packages, isNeatPublish supports deployment of SQL Agent jobs which can be configured to utilize the packages, environments, parameters published.