LMe - Sequence of Deployment set processing when deploying collections that span across multiple releases

Hi Team,

I am needing to find out the sequence that deployment sets are generated and processed when a collection spans across multiple releases in LMe.

1. We have a collection that has parts in the Base and Delta release. We want to promote and deploy that collection, so what is the sequence that the deployment sets are generated and or processed in?

2. We have a collection that has parts that belong to 2 different application / releases. We want to promote and deploy that collection, so what is the sequence that the deployment sets are generated and or processed in?

I have not found anything in the documentation and am looking for the rules related to the sequence that deployment sets are generated and processed in during the above scenarios.

Thank you in advance.

------------------------------
Gary Woodcock
Kantion IT Pty Ltd
Chirnside Park Vic AU
------------------------------

Gary,
I don't see that documented, but will take a look around the shoppe.
I'll include update here in Forum, but curious to know customer details. Possible to create a case for review and any further details (pre-/post-install requirements in targets, environments for the tasks, etc.)?
Thanks in advance,
d

------------------------------
Dale
L3 Support for the enterprise bits, portals and plugins...
Rocket|Aldon
Somewhere on the Oregon coast...
------------------------------

Hi Dale,

Are there any updates to the sequencing of deployment processing.
Not looking at pre/post install processing, however if that impacts the sequence would like to know details.

Regards,
Gary

------------------------------
Gary Woodcock
Technical Consultant
Kantion IT Pty Ltd
Chirnside Park Vic AU
------------------------------

Gary,
Still waiting on the lab to review the code for the details. For the last updates for multiple target processing, we appear to have not included all detail in the LM gui Help. Requesting updated details on the prepare and deployment installation steps that have $PD in base/delta or cross-release/cross-application/cross-group scenarios (including multiple targets on a common computer).
d

------------------------------
Dale
L3 Support for the enterprise bits, portals and plugins...
Rocket|Aldon
Somewhere on the Oregon coast...
------------------------------

Gary,
Here is the summary from the lab for a Task with parts crossing applications, releases...
~~

The promoting sequence under crossing releases situation is decided by the part name sort.
The sort is the first character of the part name in the ASCII code table.
All the parts in the task crossing the releases will be arranged under their releases.
The release with the first part name in the sequence will be promoted first.

Our client Help has these details on the Prepare processing:

~~
The Deployment Prepare Step
Several processes occur in the Prepare step. For a manually created deployment set, the Prepare step cannot proceed until the user has associated a candidate parts list with the deployment set. For deployment on check in/promote and an ad hoc deployment, the candidate parts list is defined as part of invoking the action. The processing in the Prepare step includes the following:

The assemblies in the candidate parts list are expanded to their constituent parts

Each part in the candidate parts list is resolved to a specific part instance (environment)

The part instances are expanded to the item instances (files)

The selection criteria in the deployment profile are applied to the list of candidate item instances to determine which items will be distributed to which target computers.

Once a file has been selected for inclusion in the deployment, the path where that file will be installed on the target computer is determined by concatenation of the path segment in the location definition and the path segment in the mapping definition.

The end result of the Prepare step is a list of files with fully qualified paths to be distributed to each of the target computers identified in the deployment profile.

When all of the selection and file path mappings are finished, the list of files to be sent to each target computer is packaged into a "zip" file and the file is sent to the Deployment Manager Server.

~~
The lab had this additional comment on the deployment sequence:

...the deploying sequence is decided by the promoting sequence.
The [deployment] sequence is decided by the release name and release version.

They are also noting that the sequence of the promoting operation is different from the sequence of the individual deployment operation.
Promote sort is using:

order by p.prtnm

Deploy is using:

group by e.envid, e.envnm, e.envdsc, e.dstprfid, e.alwdprfovr, e.relid, g.grpnm, a.appnm, r.relnm, r.relver
order by r.relnm, r.relver

I'm trying to get more details on the group and sort for the installation. I have this initial comment from the lab, but I think you need details on the Targets and Path Designators:

------------------------------
Dale
L3 Support for the enterprise bits, portals and plugins...
Rocket|Aldon
Somewhere on the Oregon coast...
------------------------------

Gary,
Here is the summary from the lab for a Task with parts crossing applications, releases...
~~

The promoting sequence under crossing releases situation is decided by the part name sort.
The sort is the first character of the part name in the ASCII code table.
All the parts in the task crossing the releases will be arranged under their releases.
The release with the first part name in the sequence will be promoted first.