Regardless of your SAP system scope and architecture, some general installation steps will need to be performed on your SAP systems to prepare them for ActiveControl.
| # | Activity | Details |
| 3.1.1 | Import ActiveControl Server and Web UI transports into Domain Controller | Import the transports provided by Basis Technologies into your designated ActiveControl Domain Controller. They must be imported in the order specified. |
| 3.1.2 | Import ActiveControl server transport into all other systems | Import the transport provided by Basis Technologies into all ABAP SAP systems that are running NW 7.01 or later. Important Note: A different transport is required if the remote systems are running an earlier version than NW 7.01 or are non-Unicode. If the system has multiple clients the ActiveControl roles transport needs to be imported into each client. |
| 3.1.3 | Create RFC users | Use SU01 to create a TE_RFC user in all clients of all SAP systems, including the ActiveControl Domain Controller. This RFC user needs the following TE role assignments: SAP_BC_TRANSPORT_ADMINISTRATOR /BTI/TE:CTS_RFC For all remote systems the TE_RFC user needs to be of type System User For the Domain Controller systems the TE_RFC user needs to be of type Service User Important: In the Domain Controller, TE_RFC user also needs /BTI/TE:CTS_ADMIN_USER and /BTI/TE:CTS_ADMIN |
| 3.1.4 | Create RFC destinations (in Domain Controller) | Use SM59 (>> Create Connection) to create RFC destinations in your ActiveControl Domain Controller: 1. To connect to All participating SAP systems (development, test, production, etc.) that will be managed by ActiveControl 2. To connect back to the ActiveControl Domain Controller system itself The following nomenclature must be used:  Note that RFC Destinations must be in ALL CAPITALS in the exact naming convention detailed above. (ie do not add client numbers) After set up, test the connection via Utilities -> Test -> Authorization Test. In addition, an RFC destination should be created on the ActiveControl Domain Controller, pointing back to itself. |
| 3.1.5 | Create RFC Destinations (in Development Systems) | Use SM59 (> Create Connection) to create RFC destinations in all your development SAP systems to connect to the TE Domain Controller. The following nomenclature must be used:  After set up, test the connection via Utilities -> Test -> Authorization Test. |
| 3.1.6 | Install ActiveControl Windows GUI | Install the ActiveControl Windows GUI on your ActiveControl Administrator’s PC. Note: ActiveControl can alternatively be installed/run from a central fileshare or Citrix server. |
| 3.1.7 | Create ActiveControl Administrators and allocate ActiveControl roles to | Using SU01, create the ActiveControl Administrator users and assign a valid email address for email notifications. Add the following ActiveControl roles (within the ActiveControl Domain Controller): /BTI/TE:CTS_ADMIN_USER /BTI/TE:STD_ADMIN_ROLE Although most other user assignments can be done closer to ActiveControl go-live, the above roles are needed for the ActiveControl Administrators to install and configure ActiveControl. |
| 3.1.8 | Create ActiveControl users and assign ActiveControl roles to ActiveControl users | Using SU01, create the ActiveControl users and assign a valid email address for email notifications. Add the appropriate ActiveControl roles identified earlier (within the ActiveControl Domain Controller). Some organisations choose to do this activity nearer to go-live but it is good practice to get a full user list as soon as possible. |
| 3.1.9 | Create ActiveControl Batch job user | Using SU01, create a Batch job user (suggested username TE_BATCH) for use in all background jobs. The First and Last names should be ‘Transport’ and ‘Express’ so it’s easy for users to see where notification emails have come from. Add the following ActiveControl roles (within the ActiveControl Domain Controller): /BTI/TE:CTS_ADMIN_USER /BTI/TE:CTS_RFC /BTI/TE:COMP_ADMIN_ROLE |
| 3.1.10 | Update system parameters (Domain Controller) | 1. (OPTIONAL) Activate table logging for the ActiveControl domain controller via SAP system profile parameter rec/client. This should be set to ‘all’ so that changes to TE configuration tables are logged by SAP. NB: As of TE 6.10, table logging of key ActiveControl configuration is done automatically via report /BTI/TE_RCHANGE_DOCUMENTS. 2. To stop the SAP GUI screens from timing out when entering a transport form or task whilst using the field exit functionality it is recommended to increase the rdisp/max_hold_time parameter on all application servers of the ActiveControl domain controller AND all ABAP Development Systems. The recommended value for this is 360. This will require a system restart. |
| 3.1.11 | Update system parameters (all ABAP Development systems) | Use standard SAP report RSPFPAR in SA38 to check that the system profile parameter abap/fieldexit is set to YES. This will require a system restart. |
Post your comment on this topic.