IBM SPSS Data Collection Publish Assets Utility

The IBM® SPSS® Data Collection Publish Assets Utility and the command-line Publish Assets Utility allows you to manage your customized files for web-deployed IBM® SPSS® Data Collection products (for example, IBM® SPSS® Data Collection Author Server Edition, IBM® SPSS® Data Collection Survey Reporter Server Edition.

Running the IBM SPSS Data Collection Publish Assets Utility

Backup the appropriate web-deployed applications that are installed on your workstation (for example, if you have installed Survey Reporter Server Edition, backup the directory C:\InetPub\wwwroot\SPSSMR\Reporter).

Prepare your custom files in the web-deployed application's sub-directory Custom Files (for example, for Survey Reporter Server Edition, the sub-directory is C:\InetPub\wwwroot\SPSSMR\Reporter\Custom Files).

Run the Publish Assets Utility (PublishAssetsUI.exe). The utility is installed with Survey Reporter Server Edition at: C:\InetPub\wwwroot\SPSSMR\Reporter.

Expand Show details

Click Browse... next to the Application Name field and select the appropriate *.application file (for example, Author.application for Author Server Edition or Reporter.application for Survey Reporter Server Edition).

If necessary, increase the Revision number (the number automatically increments by one).

Click Browse... next to the Path field and select your Personal Information Exchange (.pfx) file. The file is used to sign the manifest.

If necessary, enter an appropriate password in the Password field.

Click Browse... next to the Custom Files Path field and select the Custom Files directory for the appropriate web-deployed application. The directory contains the custom files that you want to deploy.

Click Save to deploy your custom files.

The command-line IBM SPSS Data Collection Publish Assets Utility

The command-line Publish Assets Utility (PublishAssets.exe) provides command-line options that serve the same function as the Publish Assets Utility.

Switched and arguments
ParameterDescription
-AppManifest <path>
-appm
Optional. The application's manifest file. By default, the first *.application file in current directory is searched.
-CustomFolder <path> Optional. The custom files folder. The default location is the Custom Files folder in the current directory.
-CertFile <path> Required. A Personal Information Exchange (.pfx) file contains a public key and a private key. The file is used to sign the manifest file.
-Password
-pwd
Optional. The password for the .pfx file (if required).
-RevVersion <version> Optional. The revision version to publish for the application. By default, the value is incremented by one.
-Help
-?
- h
Help for the utility.

Running the Publish Assets Utility for Survey Reporter Server Edition

The Publish Assets Utility executable file PublishAssets.exe is located in the directory where Survey Reporter Server Edition is installed (the default directory is C:\InetPub\wwwroot\SPSSMR\Survey Reporter).

Supported custom files
File\Directory NameDescription
Reporter.exe.configThe application's configurations file.
Styles Directory that contains the style sheet (.css) files.

Obtaining a Personal Information Exchange (.pfx) file

You must provide a Personal Information Exchange (.pfx) file in the Publish Assets Utility in order to protect your deployed files. The following files are required to generate a .pfx file:

• A public key (.cer) file

• A private key (.pvk) file

If you do not have these files, you can use the Microsoft Certificate Creation Tool makecert.exe (available in the Microsoft Windows SDK). The tool is intended for testing purposes. For example:

makecert.exe -sv MyKey.pvk -n "CN=MyCompanyName" MyKey.cer

You will be prompted to provide a password for the private key. When you have your public key (.cer) and private key (.pvk) files, you can then generate a Personal Information Exchange (.pfx) file by using the Microsoft PVK/SPC to PFX file converter pvk2pfx.exe. For example:

pvk2pfx.exe -pvk MyKey.pvk -spc MyKey.cer -pfx MyPFX.pfx -po MyPassword

Note: You can obtain the makecert.exe and pvk2pfx.exe utilities from the Microsoft Windows SDK or Microsoft Windows Drive Kit.