Before you start, please contact https://crossalm2.atlassian.net/servicedesk/customer/portal/6 to get receive the Transport Requests containing the SAP side of this solutionthe configu.
Option “SAP Solution Manager”:
...
The support package level of your SAP Solution Manager does not matter but should be up to date. We need a
Version 7.2 version.This is the preferred option if a SAP Solution Manager system is in place.
...
Please request a transport request to be imported into a domain controller system which is not a SAP Solution Manager system. This domain controller has to be connected to all involved systems and clients via TMS Trusted/Trusting services (TMSADM@…, TMSORG@…, TMSIMP@…). CTS_PLUGIN (or SAP_BASIS) software components and must be up to date. As workaround you can use your backup domain controller as well.
...
This is the preferred option if there are no SAP Solution Manager system is in place.
Involved Managed Systems:
There are no No implementation steps need to be performed in your managed systems. No transport request has need to be imported.
Dependent on your RFC destinations you might need to check/adjust the PFCG authorities of the users used to perform transport creation, deletion, release or import. As mentioned above, we are using standard users who should already exist and who should already have the necessary authorities.
There is one a special case: If you want to perform a transport activity in your SAP Solution Manager or domain controller system and client, the technical user used by the Jira plugin will need additional PFCG authorities. This issue is caused by the fact, that the transport activities will here be performed using RFC destination NONE exceptionally.