1>>Note 841873 - New HTTP path for the SAP Contact Center Simulator
Symptom
The SAP Contact Center Simulator in a SAP J2EE Engine up to and including a 6.30 installation can no longer be reached using the "soapdispatcher " HTTP path.
Reason and Prerequisites
The SAP Contact Center Simulator (CCS) in a SAP J2EE Engine 6.20 installation can be accessed using the HTTP path "soapdispatcher".
Due to enhancements in the SOAP framework of the SAP J2EE Engine 6.30, the CCS in a SAP J2EE Engine up to and including a 6.30 installation can no longer be accessed using a single HTTP path. This poses a problem for all implementations of the Integrated Communication Interface that want to use the CCS for test purposes, but can only address these using a single URL (for example, ABAP BCB).
Solution
(1) Implement SAP Netweaver 04 Support Package stack 13 or use the SDAs "bcb.sda" and "bcbici.ear" attached to this note with the Software Delivery Manager (SDM).
(2) Configure the destination for the SAP Contact Center Simulator as follows: http://<j2ee_host>:<port>/bcb/ccsdispatcher. (The HTTP path "soapdispatcher" is no longer available for technical reasons).
2 >> Note 1646876 - CCS Application unavailable in newer releases of NetWeaver
Symptom
You have installed the SAP Customer Relationship Management (CRM) ABAP Stack from release 7.10 or higher and a corresponding Java stack.
Now you want to simulate load on it via integration of multichannel management system, a SAP Contact Center Simulator (CCS), with the Interaction Center WebClient and the Interaction Center manager dashboard, provided by SAP CRM.
However you cannot find the CCS application on the Java stack.
Reason and Prerequisites
The SAP CCS application is present in older NetWeaver releases (7.0x and 6.40), but it is not available in NetWeaver releases 7.10 and higher.
Solution
Install a separate NetWeaver 7.0x Java system and use the CCS application on it to simulate load for newer CRM systems.
Regards,
Vaibhav Shah