The Web-interface runs out of the box from the Transport Expresso domain controller.
You will need to activate the following services via the transaction SICF.
- default_host -> BTI -> te_web_services
- 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
By activating the services, this exposes the Transport Expresso web-interface via the HTTP protocol to the Transport Expresso domain controller server.
- If the TE 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.
The /bti URLs need to be added to the ICM URL prefix table so the Transport Expresso 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:
Once activated, you can test the service to determine the URL:
You will be prompted for a logon to the Transport Expresso domain controller SAP system. Use your SAP username and password.
Once logged on, you will be able to access the available functionality and this can be used simultaneously with the Transport Expresso windows client.
- 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.