CIP package identification
Use the Package identification panel to specify a universally
unique identifier for the customized installation package (CIP).
Unique identifier for the CIP.
Type a descriptor. For example, if you work in a test environment, then we might use com.ibm.toronto.test to identify test CIPs that
you create. Suppose that you work at a local university. We might
use edu.abc.university.sid.was as an identifer for CIPs created
to install WAS 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.
Specifies a version number to help identify CIPs that you
create.
For example, the version field is populated with 1.0.0.0. We 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 WAS ND.
This read-only field shows the concatenation of the previous
two fields.
The Installation Factory uses this full 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:
Click Next.
Related reference
Last updated Nov 11, 2010 1:01:09 PM CST
Identifier
Version
Full package identifier
![[Windows] <p>](../../windows.gif)
Contain 35 or fewer characters on Windows platforms