BIE Packaging

Key questions

• How do BIE Packages relate to connectKits? (easy answer)

• How do BIE Packages relate to Business Contexts?

• What is the lifecycle of a BIE Package?

• Do component tags play a role?

Definition of the term “BIE package”

This is an everyday discussion definition, not a technical definition.

• A set of BIEs intended to be used together in an enterprise integration ecosystem or B2B integration scenario.

BIE package requirements/characteristics

• Consistency across the BIEs in the package. (What does “consistency” mean in this context?)

Motivation

• To communicate the current package version it is on. And the BIE versions inside it.

• The scope of the package can be at the enterprise level or at the business process level.

Information required in a package

Information requirement at the package level

1. connectSpec release number

2. Package release number: Version ID of the package.

   1. Format: [connectSpec release number] + [package version number]

3. Manifest of BIEs that shows ID, BIE Name, and version, categorized by same and new, compared to the previous package.

Information requirement at the BIE level

1. connectSpec release number

Constraints

1. All BIEs in the package must be based on the same connectSpec release?

How the user may manage a BIE Package

• BIE packaging may be similar to how a new connectSpec release is made. That is a new package can be created, BIEs can be assigned, package information can be edited. A new package can be created from copying a existing package.

• Functionality to assign BIE based on business context.