BSP Services

To install the ActiveControl WebUI, the following services BSP need to be activated in the domain controller via transaction SICF:

• default_host -> BTI -> te_web_services
• default_host -> BTI -> tessocntl
• default_host -> sap -> bc -> bsp -> bti -> te_bsp_new

Other general BSP services may also need to be activated to enable the web interface to work.

• All subnodes in default_host -> sap -> public -> bsp -> sap
  

The following may also be required to enable the ActiveControl Reports to work in the Web UI:

• default host -> sap -> bc -> gui -> sap -> its -> webgui
  

By activating the services, this exposes the ActiveControl Web UI via the HTTP protocol to the ActiveControl domain controller server.

Once activated, you can test the ‘te_bsp_new’ service to determine the URL:

• http://[acdomaincontroller]:80[systemnumber]/sap/bc/bsp/bti/te_bsp_new/index.html
  

You will be prompted for a logon to the ActiveControl domain controller SAP system, and should use your SAP username and password. Once logged on, you will be able to access the WebUI functionality. This can be used simultaneously with the ActiveControl Windows GUI if you also have that installed.

!If the Domain Controller system is setup as a dual stack system (system/type = DS) then by default all /sap URLs get directed to the ABAP stack whereas everything else is sent to the Java stack. To mitigate this, the /bti URLs need to be added to the ICM URL prefix table so the ActiveControl web UI is directed to the ABAP stack. This is done in the ICM config transaction SMICM. This can be found in the following possible menu paths:
Goto -> HTTP Server -> Load URL Prefixes
Goto -> HTTP Plug-In -> Application Server -> Load URL Prefixes
In both cases above use the Display Data option to view the current settings. /bti/ should be displayed in the URL Prefix Table.

* For Single Sign On (SSO) rather than using the index.html page above please use the main.html page instead as this will bypass the login screen and use the current user logon ticket. Please note that this obviously requires SSO to have been setup within your ActiveControl Domain Controller as a pre-requisite.