CIP package identification

Use the Package identification panel to specify a universally unique identifier for the customized installation package (CIP).

Identifier

Specifies a unique identifier for your CIP.

Type a descriptor. For example, if you work in a test environment, then you might use com.ibm.toronto.test to identify test CIPs that you create. Suppose that you work at a local university. You might use edu.abc.university.sid.was as an identifer for CIPs that you create to install WebSphere Application Server updates on machines used by the media.

The package identifier is designed to be universally unique. You can install multiple CIPs on a single installation. Each CIP installs customization assets in the installation in a unique directory. The unique directory name is modelled after the unique identifier provided. For this reason, the identifier must be unique, and therefore a unique reverse domain notation with a version number is recommended.

Click Next.

Version

Specifies a version number to help identify CIPs that you create.

For example, the version field is populated with 1.0.0.0. You might want to start with that value and increment later CIP versions. The version number of the CIP does not have to reflect the version number of the product.

Full package identifier

This read-only field shows the concatenation of the previous two fields.

The Installation Factory uses this unique identifier as the name of a directory that holds the customized installation package. For example, the full package identifier might be edu.abc.university.was_1.0.0.0.

File paths and file names must comply with the following guidelines:



Related reference
CIP Build Definition wizard panels
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 10:47:11 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-iseries&topic=uins_ifactory4a
File name: uins_ifactory4a.html