InstallShield Integration with Application Catalog Software Repository

AdminStudio 2022 | 23.0 | InstallShield Editor

Edition:InstallShield Professional is included with AdminStudio Professional Editions. InstallShield Premier is included with AdminStudio Enterprise Edition.

Edition:The Software Repository feature is available in AdminStudio Enterprise Edition.

When you have a Basic MSI project open in InstallShield Editor, AdminStudio-specific settings are listed in the Publishing area on the Events tab of the Media > Releases view in the Installation Designer.

Events Tab Under Media > Releases

You can use these settings to specify information such as whether you want the Windows Installer package that you are building to be published to the software repository.

Publishing Settings on the Events Tab—for InstallShield with AdminStudio

Property	Project Type	Description
Publish to AdminStudio Repository	Basic MSI	Specify whether you want the Windows Installer package that you are building to be published to the software repository. If you use the software repository to manage a Windows Installer package, the .msi file and all of its other associated files and subfolders are stored in a subfolder of the software repository location that is identified for the package’s Application Catalog.
Group	Basic MSI	If you select Yes for the Publish to AdminStudio Repository setting and you want to associate the Windows Installer package with one or more groups in the Application Catalog, click the ellipsis button (...) in this setting. The Select Application Catalog Groups dialog box opens. Select the check box for each group that you want to contain the Windows Installer package.
Update Option	Basic MSI	Specify how you want to handle the importing of the Windows Installer package that is built for the selected release into the Application Catalog. Available options are: • New Package Version—A new build is treated as a new package in the Application Catalog. • Overwrite Existing Version—A new build overwrites the existing version in the Application Catalog. • New Package History Version—A new build is treated as a new version of the package that exists in the Application Catalog. • Ignore if Exists—A new build is imported only if it does not already exist in the Application Catalog.

Adding a Package to the Software Repository via the InstallShield Editor Build Process

To add a package to the Software Repository via the InstallShield Editor Build process, perform the following steps.

To add a package to the Software Repository via the InstallShield Editor Build process:

1.

In AdminStudio, connect to an Application Catalog that has the Software Repository enabled.

2.

Launch InstallShield Editor.

3.

Open an InstallShield project (.ism).

4.

In the Installation Designer, open the Events tab of the Releases View.

5.

Set the Publish to AdminStudio Repository property to Yes.

6.

Select the Group that you want the imported package to belong to.

7.

Select one of the following for Update Option:

•

New Package Version

•

Overwrite Existing Version

•

New Package History Version

•

Ignore if Exists

8.

Build the setup.

Upon completion of the build, the MSI package is published to the Software Repository. The progress messages are displayed in the Output window.

Note:If the setup is compressed, an administrative image must be created before the package can be published to the Software Repository.