Some preparatory activities need to be undertaken within your organisation before ActiveControl can be installed and configured, to define the scope of your ActiveControl rollout and map out the required processes and approvals workflow to be used.

Basis Technologies generally recommends that these preparation steps, and in particular the completion of the Self-Blueprint template are undertaken via a workshop involving the key internal SAP stakeholders and decision-makers within your organisation.

# Activity Details
1.1 Designate ActiveControl Administrators Installing and maintaining ActiveControl requires a basic working knowledge of SAP and an understanding of your organisation’s Change & Release processes.

Basis Technologies recommend 2-3 resources be assigned as ActiveControl Administrators, these will typically be Basis / Change & Release resources within most organisations.
1.2 Designate a ActiveControl Domain Controller The Domain Controller is a SAP system that hosts the ActiveControl application, is where ActiveControl configuration and application data is stored and is where users connect to access the tool.

Basis Technologies generally recommends to use a Solution Manager production system as the ActiveControl Domain Controller where possible. The Domain Controller system must be a Unicode system running NetWeaver 7.01 or above.
1.3 Setup CTS+ CTS+ is a pre-requisite for managing non-ABAP systems through ActiveControl.

This webpage provides some reference info to help your Basis team set up CTS+

Most customers use their Production Solman system as CTS+ domain controller but it does not have to be.
1.4 Setup SCOT SCOT is a pre-requisite on your elected ActiveControl Domain Controller for the AC email notifications to work.
1.5 Confirm all SAP systems Every system that is to be managed by ActiveControl needs to be listed and documented along with details of their versions.

Within the System tab of the Self-Blueprint, document all the SAP systems on which ActiveControl needs to be installed, including your elected Domain Controller.
1.6 Confirm if existing MDR / Diffuser customer Verify if customer is on an earlier release of MDR or Diffuser that might be overwritten and cause issues by ActiveControl installation.
1.7 Obtain ActiveControl License Key Request a ActiveControl license key from Basis Technologies. You will need to provide your ActiveControl Domain Controller SID and installation number.
1.8 Obtain Active Software & Documentation Request the ActiveControl server and client software from Basis Technologies along with the ActiveControl documentation.
1.9 Availability of Development system access Part of the ActiveControl Implementation will require developer access in all ABAP development systems. Please ensure that the relevant resource has Developer Key access in advance of BTI coming onsite to avoid delays in the Implementation.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment