Scribd
Upload
43 views26 pages

01 PreparingPackageComp Final

The document outlines the transition from legacy deployment to packaged components for Dell Boomi users, detailing the changes in deployment workflow and capabilities. It emphasizes the importance of understanding the new deployment options, the roll-out timeline, and the need for users to prepare for account conversion. Key changes include redesigned workflows, enhanced search capabilities, and separate privileges for managing packaged components, while ensuring no data migration or loss of version history occurs.

Uploaded by

vaarsh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
43 views26 pages

01 PreparingPackageComp Final

The document outlines the transition from legacy deployment to packaged components for Dell Boomi users, detailing the changes in deployment workflow and capabilities. It emphasizes the importance of understanding the new deployment options, the roll-out timeline, and the need for users to prepare for account conversion. Key changes include redesigned workflows, enhanced search capabilities, and separate privileges for managing packaged components, while ensuring no data migration or loss of version history occurs.

Uploaded by

vaarsh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 26

Preparing for Packaged

Component Deployment
Legacy to Packaged Components

Dell, EMC, Dell EMC, Dell Boomi, AtomSphere and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be
trademarks of their respective owners.
Two Parts to the Packaged Components Release
You are here:

Packaged Audience:
Boomi Legacy deployment users upgrading to
Components Packaged Components

Packaged
Components for Audience:
Process Library Boomi Legacy deployment users using Process
and Integration Library and Integration Packs
Packs
Agenda

Review Deployment Options

Demo of Legacy and Packaged


Components Deployments

Roll Out Timeline


OBJECTIVES
By the end of this presentation, you will be able to:

01 Understand what is changing with Packaged Components

02 Take advantage of new deployment capabilities

03 Review the roll out timeline

04 Prepare for converting your account


Understanding Deployment Options
Legacy Deployment

Majority of customers and partners are using this today!


Package Manager
1. Package Manager to
Packaged Components is a
minor change

2. Refer to the Knowledge


Base article in the
Community for information
on how to adopt
Packaged Components
Deployment Workflow
Deployment Work Flow

1. 2.
Legacy

Build Deploy
Components “Snapshot” + Deploy to
Environment
Packaged Components

1. 2. 3.
Create
Build Packaged Deploy
Deploy to
Components Component Environment
“Snapshot”
Why did we separate the steps?

1. Single Deployed Component Version across


environments

2. Enables future DevOps and solution bundling use cases

3. Allows user-defined version numbering


Single Deployed Component Version Across Environments:

Development QA Production

Deploy to QA
Initial
for testing
development
Deploy
Process Rev 4 DV 1, Rev 4

Found
issue

Fix Deploy fix Testing OK, deploy to production


issue
Deploy Deploy
Process Rev 6 DV 2, Rev 6 DV 1, Rev 6

2≠1
Single Deployed Component Version Across Environments:

Development Packaged Components QA Production

Initial Deploy to QA
development for testing
Create
Process Rev 4 PC Ver 1, Process Deploy
Rev 4 PC Ver1
Found
issue

Deploy fix
Testing OK, deploy to
Fix issue production
Create Deploy
Deploy
Process Rev 6 PC Ver 2, Process PC Ver2 PC Ver2
Rev 6

2=2
What’s Changing/What Stays the Same?
What IS Changing?

1. Redesigned the deployment workflow


and screens
2. Separate actions for creating a snapshot
process version and deploying it to an
environment
3. No attaching environments
4. Enhanced search capability
5. Separate privileges for creating and deploying
Packaged Components
6. New API endpoints
What IS NOT Changing?

1. “Snapshot” still exists for deployable component


2. “Snapshot” is a single process or deployable component
3. No data migration - purely a front-end change
 No version history or audit information is lost
 No impact to runtimes, deployed integrations,
extensions, etc.
 No Build tab impact
4. All API’s are forward compatible
5. Default Boomi versioning convention
What happens to existing deployment versions?
Legacy Deployment
What happens to existing deployment versions?
LEGACY Pack. Comp. Date
Ver
Environment Deployments – TEST
No new packaged component created for PROD
Deployment Ver Env Date V3 above because deployment was copied from
Test V2
2 TEST Jan 15
4.0 Jan 15 Created from TEST V2
1 TEST Jan 2 3.0 Jan 8 Created from PROD V2

2.0 Jan 3 Created from PROD V1


Environment Deployments – PROD
1.0 Jan 2 Created from TEST V1
Deployment Env Date
Ver
3 PROD Jan 16 Copied from Test V2
Env Pack. Date
2 PROD Jan 8 Comp.
Ver
1 PROD Jan 3
PROD 4.0 Jan 16 Note deployment of same packaged
component version to different
environment
TEST 4.0 Jan 15
PROD 3.0 Jan 8
PROD 2.0 Jan 3
TEST 1.0 Jan 2
Demonstrations
Roll Out Timeline
Roll Out Timeline
Existing accounts with legacy deployments will receive a feature switch account
Administrators can use to self-service convert when ready

Existing accounts will NOT be automatically converted


March
2020 Packaged Component deployment will be enabled by default for ALL new
accounts

All existing Package Manager accounts WILL be automatically updated with


the revised screens

Q3 2020: All legacy accounts will be converted automatically


Changes to make in advance

If using custom roles with deployment privileges:


 You must also grant access to Packaged Component Management to
maintain the same level of access for current users

If using Platform API’s to automate deployments:


 Start planning to switch to new packaged component related API’s
Additional Resources
 FAQ and Community Knowledge Articles

 Preparing for Packaged Component Deployment: Process


Library and Integration Packs Presentation
THANK YOU

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy