ActiveControl is an ABAP Add-On. Most of the data/configuration of ActiveControl resides in a Domain Controller SAP system elected by the Customer.
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 the ActiveControl implementation.
It is recommended that you perform these steps with the support of a Basis Technologies’ Solution Specialist to ensure that all activities are completed and checked correctly.
| Activity | Details |
|---|---|
| ActiveControl software transports (ActiveControl Domain Controller) |
Please refer to this Knowledge Article for full details of the transports and sequence. |
| ActiveControl software transports (Development Satellite Systems) |
Please refer to this Knowledge Article for full details of the transports and sequence that need to be deployed in Development satellite systems. |
| ActiveControl software transports (Non-Development Satellite Systems) |
Please refer to this Knowledge Article for full details of the transports and sequence that need to be deployed in non-Development satellite systems. |
| Create RFC user (Domain Controller) |
Use SU01 to create a service AC_RFC user in the ActiveControl Domain Controller. This RFC user needs the following ActiveControl role assignments: /BTI/TE:CTS_RFC /BTI/TE:CTS_ADMIN_USER /BTI/TE:CTS_ADMIN |
| Create RFC users (all remote Satellite systems, all clients) |
Use SU01 to create a system AC_RFC user in all clients of all remote satellite SAP systems (Ie Dev, QA, Production, Training etc) to be managed by ActiveControl. This RFC user needs the following ActiveControl role assignments: /BTI/TE:CTS_RFC |
| Create RFC destinations out to all satellite managed systems (Domain Controller) |
Use SM59 (>> Create Connection) to create RFC destinations in your ActiveControl Domain Controller. The following nomenclature must be used: RFC Name: TRANSPORT EXPRESS XXX (where XXX is the SID of the SAP system) Connection Type: 3 Target Host: Hostname of an application server of the SAP system. Client: The main client of the SAP system. User: AC_RFC Password: _______ 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. |
| Create RFC destination pointing back at itself (Domain Controller) |
An RFC destination should be created in the ActiveControl Domain Controller, pointing back to itself. The same nomenclature as the previous step should be used. After set up, test the connection via Utilities -> Test -> Authorization Test. |
| Create RFC Destinations (in Development Systems) |
Use SM59 (> Create Connection) to create RFC destinations in all your development SAP systems to connect to the AC Domain Controller. The following nomenclature is recommended: RFC Name: TRANSPORT EXPRESS CONTROLLER (it does not have to be exactly this) Connection Type: 3 Target Host: Hostname of an application server of the SAP system. Client: The main client where users connect to ActiveControl in the Domain Controller. User: AC_RFC (it does not have to be exactly this) Password: _______ After set up, test the connection via Utilities -> Test -> Authorization Test. |
| Create ActiveControl Administrators and allocate ActiveControl roles | 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. |
| Create ActiveControl Batch job user | Using SU01, create a Batch job user (suggested username AC_BATCH) for use in all background jobs. The First and Last names should be ‘Active’ and ‘Control’ 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 |
| Update rdisp/max_hold_time system parameter (Domain Controller + Development System) |
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. |
| 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. |
Post your comment on this topic.