Creating a Replication Package
You can create a replication package from the Packages table, which appears on the Packages page for each application context.
The New Package window divides the creation of a new replication package into the following steps.
 |
If your site has security labels enabled, you may see the Set Security Labels step. For more information about setting security labels, see Setting Security Labels while Creating an Object. When setting security labels on a replication package, it is recommended to match label values set on the most restricted object included in the replication package or a more restrictive value present on the target system.
|
1. Set Attributes
a. If there are multiple package types available to you, you can select one from the Type list. Depending on your selection, the steps on the New Package window may change. To create a replication package, select the Replication Package type or one of its subtypes from the drop-down list. If you are creating a CDRL or SDRL package, see Creating a New CDRL or SDRL. If you are creating a package or technical data package, see Creating a Package.
b. Depending on your settings, you may be able to select a domain for the package. A domain is an administrative area that defines a set of policies, such as access control, indexing, and notification. Packages, like folders, are associated with a domain and are subject to the access control policies defined for the domain. To select a domain other than the default setting, click Find.
|
|
When selecting a domain, you cannot view its policies. To view the access policies, navigate to the Policy Administration utility.
|
c. If an organization identifier field appears, click the find icon 
to choose an organization identifier, such as a CAGE code or a DUNS number, for the package.
to choose an organization identifier, such as a CAGE code or a DUNS number, for the package.| | The display of organization information and its format depends on your system configuration. |
d. In the Package Attributes section, complete the applicable fields:
Attribute | Description |
|---|---|
Number | Set the unique identifier for the package. You may or may not be able to set your own number; depending on your site configuration, the number may be automatically generated. The number can be up to 32 characters. |
Name | Specify a name for the package. |
Description | Enter a short description of the package. The description can be up to 4000 characters. |
2. Select Contexts
The Select Contexts step allows you to select particular context or set of contexts. All versions of supported objects in the selected context or contexts are added to your package content. To add a context, click the add contexts icon 
. The Find Context window opens, allowing you to select a context type and specify all or part of the context name, description, owner, or state. Select a context from the Search Results table and click OK. The context appears in the Contexts table. To remove a context, select the context from the table and click the remove selected contexts icon 
.
. The Find Context window opens, allowing you to select a context type and specify all or part of the context name, description, owner, or state. Select a context from the Search Results table and click OK. The context appears in the Contexts table. To remove a context, select the context from the table and click the remove selected contexts icon .| | Only product or library contexts can be added to a replication package. |
3. Set Attachments
The Set Attachments step allows you to attach content files that are meaningful in the context of the package. Since packages are used to distribute information to external users, adding attachments to the package can distinguish what contents should not be sent to the external users. Attachments are not included in the delivery and can manage information that is not required for the external user, such as an internal procedure for information distribution. For more information, see About Attachments.
4. Click Finish to complete the creation of the new package.