Platform differences

In general, the IDK functions the same on packages from different platforms (operating systems). However, there are a few differences, as explained in the following sections.

Solaris differences

Solaris package names have a 9 character limit. By convention, the format is a set of capital letters, followed by a set of lower case letters that identify the application. Optionally, the final character may have a special meaning. Note that this format is a convention, not a requirement. Here are some examples of Solaris package names:

• SPROcc
• SPROcmpl
• SPROcodmg
• SUNWgssx
• SUNWgzip
• SUNWhea
• SUNWhiu8x
• SUNWhmd
• SUNWhmdu
• SUNWhmdx

When the ISMTool creates a Solaris package, it must use a package name that is no more than 9 characters in length. The package name constructed by ISMTool begins with ISM, followed by the five first characters of the ISM's name, followed by the letter c for the control package or a digit 0 for the first part of an application package, 1 for the second part, and so forth. For example, if the ISM name is foobar, the package names would be the following:

• ISMfooba0
• ISMfoobac

If truncation occurs, ISMTool generates a warning so that the developer can rename the ISM to avoid naming conflicts. To view the package names, use the Solaris pkginfo command.

If you upload a Solaris passthru package, the response file is not uploaded. You must manually upload the response file.

Windows differences

On Windows, when ISMTool creates the application and control Windows Installer (MSI) packages, it encodes the ProductName and ProductVersion as follows:

ProductName: <name>-<version>
ProductVersion: 0.0.<app|ctl release>

The <name>, <version>, and <release> correspond to an ISM's internal information, which can be viewed with the ISMTool’s --info command. This encoding scheme is by design and is required for the remediation process to work correctly.