!--a11y-->
Customizing the Integrated Communication
Interface 

With regard to the options below, the Interaction Center WebClient runs only with the non-Java option. The communication management software simulator (CMSS) runs only with the Java option. If you want to demonstrate and test the Integrated Communication Interface (ICI) using the CMSS, you need to install the Java option.
Java Option Only
You can customize the environment using the Business Communication Broker (BCB) administration user interface, which you can access at http://<hostname>:<port>/bcb.
Under System Information, you can see whether SAP is connected to one or more communication management software systems, and the connection status. The BCB version number and the SAP SOAP URL (URL given to the communication management software to return events) are also displayed.
Non-Java Option Only
You can customize the environment using the Business Communication Broker (BCB) administration transaction CRMM_BCB_ADM. For example, you can see whether SAP is connected to one or more communication management software systems.
Java Option Only
You have installed the J2EE Engine, which includes the ICI. For more information, see Installing the ICI.
The HTTP port on the firewall has been released for communication with the external communication management software.

If you have installed the ICI in a cluster other than a single-node cluster on a single physical machine and you want to use the CMSS, the customizing settings outlined below are not sufficient. This is because the standard CMSS is designed to run in a single-node cluster. For details of the changes that must be made to these customizing settings if you are installing the ICI in a multinode cluster and you want to use the CMSS, see Demonstrating and Testing the ICI Using the CMSS ® Demonstrations using the Communication Management Software Simulator.
Java Option Only
...
1. Go to http://<hostname>:<port>/bcb.
2. Choose Settings.
A page is displayed where you can make the settings required for both the live environment (actual communication management software) and the test environment (communication management software simulator). Default values are included.
3. In the Connections section, enter the individual components of the destination URLs for the transmission of SOAP messages from SAP.

You can define values for the communication management software simulator (CMSS always exists and cannot be removed) and multiple real communication management software systems. If you want to add a communication management software system, choose Add connection, and enter the values as described below. You then use the radio button Default to define the default environment. The default values for the CMSS are valid if the CMSS is running on the same J2EE Engine as the ICI. If you are running the CMSS on a different machine or J2EE Engine instance, then you have to change the settings.
...
a. For Protocol, enter http.
b. For Host Name, enter the full physical IP address of the CMSS host or the external communication management software, as applicable.
c. For Port, enter the port at which the messages are to be received, usually 80 for HTTP.
d. For Path, enter the application that processes the SOAP messages. For the CMSS, leave the field empty.
e. You can also choose to use a proxy and specify the relevant host name and port.
4. Choose Save Settings.
This creates the customizing files.
Java Option Only
The
ICI writes administrator logs into the system/server log by default. This can
be customized in the
Visual
Administrator of the J2EE Engine.
To examine the SOAP messages that are exchanged between SAP and the communication management software, you can activate traces depending on the direction:
· To trace SOAP messages sent by SAP, set the flag SOAP Message Trace in the Trace Settings section on the Settings page of the BCB administration UI.
· To trace SOAP messages sent by the communication management software, settings have to be made in the Visual Administrator of the J2EE Engine.
You can activate additional traces for troubleshooting in the Visual Administrator of the J2EE Engine.
Non-Java Option Only
You can activate ICI traces in transaction CRM_ICI_TRACE.
Once these customizing settings have been made, implementation of the ICI is complete. It does not have to be explicitly started or activated.
Java Option Only
You can use the communication management software simulator to test the ICI without having real communication management software connected. For more information, see Demonstrating and Testing the ICI Using the CMSS.