PI Transports getting stuck before activated and blocking the next ones

[former_member69608]

Hi everyone,
When transporting IB Objects (channels) it is required to enter credentials like password etc. However, we experience a problem when importing many transports.

When a transport is transported, it is "blocking" the next transport until the previous transport is activated with all the credentials. This is very time consuming for both developers and Basis-team.

Is it possible to somehow transport all the transports and THEN enter the credentials?

[former_member69608]

Hi anna.winterholler ,

Thank you for your input. A communication component that is only referenced by one ICO is a rare case where I work at. I mean, we have multiple integrations from the same communication component, so the same component will almost always be included in two or more ICO's.
Does this mean it is not possible to activate them at all once?

[anna_winterholler]

Hi Stefan,

The ICO's are most probably not the issue. I guess, the same communication component is contained in several transports? Just try to avoid this. Is your communication component changed frequently? If not, may be you can transport it only once and let it out in the subsequent transports as long as it is not changed. And regarding communication channels: non-transportable attributes like passwords/host/port must be maintained only after initial transport. All subsequent transports should take over the values from the previous object version in the target system.

Best regards,

Anna

[former_member69608]

Hi manoj.khavatkopp ,

Thank you for your reply.
I understand this is a expected behaviour when its the same object. However, what I mean is that it blocks even if its another object - is this also expected?

[manoj_khavatkopp]

Can you please add the detailed error screen shot.

[anna_winterholler]

Hello Stefan,

please check if there is an object, which is contained in both transports. It could be a communication component or a channel which is referenced by other objects. Try to cut your transports that way, that they do not contain any intersections. Then it should be no problem to transport multiple times and later activate all change lists.

Best regards

Anna

[manoj_khavatkopp]

Hi Stefan,

When you Transport any ID object it stays in the change list, until and unless anyone activates it. If you are trying to move the same object again before activating the earlier one then it will throw an error this is expected behavior.

If you want to move all the objects at one and activate it in one go , then i would suggest add all the required IB objects in one TR and then transport it .

Thanks,

Manoj