Asset Management > Bundles > Creating and publishing bundles
  

Creating and publishing bundles

You can create bundles to share assets with other organizations.
When you create a bundle, you specify the bundle type. The bundle type determines who can use the bundle and also determines how the bundle is published.
You can create the following types of bundles:
Public bundles
A public bundle is available to all Informatica Intelligent Cloud Services organizations. When you create a public bundle, you submit the bundle to Informatica for approval. When the bundle is approved, Informatica makes the bundle available to all organizations.
Private bundles
A private bundle is available to a parent organization and its sub-organizations. You create a private bundle in the parent organization and then publish the bundle to the sub-organizations. Published private bundles appear on the Add-On Bundles page for sub-organizations.
After you publish a private bundle, you can push the bundle to all of the sub-organizations. When you push a private bundle, you install the bundle on all sub-organizations.
The Informatica review team does not review private bundles.
Note: If a pushed bundle contains objects with changes that are incompatible with existing sub-organization tasks, it might cause the sub-organization tasks to become invalid or be removed.
If your organization does not have any sub-organizations, the option to create a private bundle is not available.
Unlisted bundles
An unlisted bundle is similar to a public bundle. However, only users who have the bundle access code have access to the bundle. When you create an unlisted bundle, Informatica Intelligent Cloud Services generates a bundle access code. The review team does not review unlisted bundles.
When you create a bundle, you specify how users can use the bundle assets. You can allow users to use bundle assets in one of the following ways:
Copy bundle assets
With this option, users can copy bundle assets to their projects and edit the assets.
In Data Integration, these bundles can include mappings, mapping tasks, mapplets, and user-defined functions.
Reference bundle assets
With this option, users can use bundle assets in tasks but they cannot copy or edit the bundle assets.
In Data Integration, these bundles can include mappings and mapplets. All of the mappings must use parameterized connections.
Copy or reference bundle assets
With this option, users can either copy and edit bundle assets or reference bundle assets in tasks.
In Data Integration, these bundles can include mappings and mapplets. All of the mappings must use parameterized connections.

Creating a bundle

Create a bundle to share assets with other organizations.
Before you create a bundle, put all of the assets that you want to include in the same folder. This helps to ensure that the bundle is versioned correctly if any of the assets are modified.
    1Click Bundles > New Bundle.
    The image shows the Bundle page with details for the b_CrossSell bundle including the bundle name, version, bundle type, and indicates that copying the bundle is allowed. The Bundle Content list includes two mappings that will be included in the bundle.
    2Configure the following details:
    Bundle Property
    Description
    Name
    Name of the bundle. Bundle names must be unique across all organizations.
    Description
    Optional description of the bundle.
    Version
    Version number of the bundle. The initial version number defaults to 1.0. The new version number must be greater than the current version in the format #.#, for example, 1.2.
    Bundle Type
    Select the bundle type that you want to publish:
    • - Public. Available to all organizations after the bundle is approved by the Informatica Intelligent Cloud Services review team.
    • - Private. Available to publish or push to from a parent organization to its sub-organizations.
    • - Unlisted. Available to users who have a valid bundle access code.
    Allow
    Select one of the following options:
    • - Reference. Allows others to select the assets in the bundle to use in their projects. The assets remain in the bundle folder and cannot be edited.
    • - Copy. Allows others to copy and edit the assets in the bundle.
    • - Reference and Copy.
    3To add assets to the bundle, in the Bundle Content list, click Add and select an asset that you want to include. You can select any asset with a Valid status.
    Repeat this step until you have selected all of the assets for the bundle.
    4Click Save.
    5When the bundle is complete, you can choose one of the following options based on the bundle type:
After you create a bundle, you can open the saved bundle and edit the bundle contents at any time, unless you are awaiting review and approval by Informatica. After a bundle is published, you must update the version number to save the changes.

Submitting a public bundle for review

You can submit a public bundle to Informatica for approval when you are satisfied with the bundle design. The Informatica Intelligent Cloud Services team reviews the bundle and responds to you by email.
You cannot edit the bundle until the review team completes the review or you withdraw your review request.
    1To submit a bundle, click Bundles and open the bundle.
    2Click Submit for Review.
    3Create a support ticket with Informatica Global Customer Support to provide additional details about the bundle.
    The support ticket must describe the bundle use case in detail and include documentation on how to use the bundle contents. Bundles submitted without this documentation cannot be approved.
After the bundle is submitted for review, you can cancel the review before the bundle is approved. To cancel the review, open the bundle and click Withdraw from Review. If desired, you can edit the withdrawn bundle and send it for review again.
After the bundle is approved, the Informatica Intelligent Cloud Services team publishes the bundle so that it is available to all Informatica Intelligent Cloud Services organizations.

Sharing a private bundle

When you work in a parent organization, you can share a private bundle with sub-organizations. After you publish a private bundle, the bundle is available for sub-organizations to install. You can also push a published private bundle to install the bundle on all sub-organizations.
Note: If a published bundle contains asset changes that are incompatible with existing sub-organization tasks, it might cause those tasks to become unavailable. For example, in Data Integration, adding a new parameter in a mapping could invalidate the existing task when a new bundle is published.
    1Click Bundles and open the bundle.
    2Perform one of the following steps:

Generating a bundle access code

Use a bundle access code to share a published unlisted bundle with other organizations.
When you publish an unlisted bundle, Informatica Intelligent Cloud Services provides a system-generated bundle access code. You can give the bundle access code to users in other organizations. With the bundle access code, a user can view and install the unlisted bundle. When a user installs the unlisted bundle, the bundle becomes usable in the organization like other bundles.
To see the bundle access code, open the bundle from the Bundles page. The bundle access code displays in the Bundle Details area.
The bundle access code is reusable so you can use a single code to share an unlisted bundle with multiple organizations. You can generate a new access code at any time, which invalidates the previous bundle access code.
  1. 1Click Bundles and open the bundle.
  2. 2To generate an access code, click New Bundle Access Code.
The Bundle Details page shows the current bundle access code and has an option to copy the access code and an option to generate a new access code.

Deprecating a bundle

If a bundle is outdated, you can deprecate the bundle so that it is no longer available to other organizations.
When you deprecate a bundle, organizations that have installed the bundle can continue using the bundle. Organizations that have not installed the bundle cannot see it listed as available to install.
Note: If the bundle is published, only the bundle approver can deprecate the bundle.
    1Click Bundles and open the bundle.
    2Click Deprecate.

Deleting a bundle

You can delete a private or unlisted bundle when the bundle's status is Deprecated.
You can delete an unpublished public bundle if the bundle status is Unpublished or Withdrawn. If a public bundle is published, the bundle approver must deprecate the bundle before you can delete it.
When you delete a bundle, it no longer appears on the Bundles page.
    1Click Bundles.
    2In the row that contains the bundle, click Actions and select Delete.