!--a11y-->
Web Application Specific
Parameters 
After you have deployed the Web application you need to configure your application. For this application configuration you have to maintain different parameters in Extended Configuration Management (XCM). These parameters define how the deployed Web application (e.g. B2B) specifically runs at the customer if the customer specific application configuration that stores the parameter values is used in the Web shop URL.
For more information about installation of Web components and the XCM tool, see the installation guides in SAP Service Marketplace under the address service.sap.com/crm-inst -> SAP CRM 2006s -> SAP CRM 5.1 Server and Standalone Components.
You can access XCM via the following URL:
http://<host>:<port>/<web application>/admin/xcm/init.do
The following tables give an overview on some important configuration parameters. For more information about the parameter settings, see the documentation in XCM.
If you use SSL you have to specify the HTTP and HTTPS port for each application participating in the secure communication.
Settings for SSL in XCM
Parameter |
Description |
Location in XCM |
http.port.core |
When using HTTPS you have to specify the HTTP port here. |
General Settings ® Customer ® <application name> (for example: b2b) |
https.port.core |
When using HTTPS you have to specify the HTTPS port here |
General Settings ® Customer ® <application name> (for example: b2b) |

The protocol between the Web server and the SAP Web As Java 7.0 is HTTP, the application is never accessed using HTTPS. That means, if you have the infrastructure Web Browser ® HTTPS ® Web Server ® HTTP ® J2EE Engine you need to start the application using the additional request parameter secure, for example “https://host:port/b2b/b2b/init.do?secure=true“.
The following parameters control the mime object (pictures, cascading style sheets, etc.) responsible for the look& feel of the web application.
Parameter |
Description |
Location in XCM |
theme.core |
Themes enable you to manage different records of mime objects. The parameter specified here determines which record is to be used. |
Components ® Customer ® ui |
mimes.core |
URL to mimes if placed on an external web server |
Components ® Customer ® ui |
Parameter |
Description |
Location in XCM |
reloginurl.core |
URL for logging on to the application after the session is lost. |
General Settings ® Customer ® <application name> (for example: b2b) |
Parameter |
Description |
Location in XCM |
imageserver |
This URL describes the server directory to which images from the R/3 system are published. |
Components ® Customer ® webcatalog |
You configure the connection parameters in XCM under Components ® Customer ® jco.

When you create a new connection parameter configuration you can select whether you want to connect using a message server or directly to the application server host by selecting the Base Configuration 'group_connect' or 'server_connect'.
Showing a stacktrace can be helpful when testing the application.
Parameter |
Description |
Location in XCM |
Showstacktrace.isacore |
If set to ‘true’ a stacktrace is shown if an application error occurs. For security reasons, the parameter must be set to ‘false’ in a productive environment. |
Components ® Customer ® ui |