2119647

1. 2119647 - Guidelines for setting up URL to IPC JSP UI in
CRM scenario
Version 2 Type SAP Note
Language English Master Language English
Priority Recommendations / Additional Info Category Consulting
Release Status Released for Customer Released On 09.07.2015
Component CRM-BF-CFG ( Product Configuration )
Please find the original document at https://launchpad.support.sap.com/#/notes/ 2119647
Symptom
You are using the configuration user interface (IPC JSP UI) in CRM scenario (i.e. embedded in CRM UI).
This note provides guidelines to set up the URL to IPC JSP UI in this scenario correctly.
Other Terms
ConfigUI, JSP-UI, IPC JSP-UI, IPC UI, domain relaxation
Reason and Prerequisites
The IPC JSP UI is a separate web-application that is embedded into the CRM UI. The URL to the IPC JSP UI
is maintained via transaction spro or in table COMM_IPC_URL.
Transaction spro:
-> "SAP Reference IMG"
-> "Customer Relationship Management"
-> "Basic Functions"
-> "Product Configuration"
-> "Define URLs"
In order to embed the IPC JSP UI the CRM UI reads the URL from this customizing by using destination
"UI_CFG". Therefore it is only possible to maintain one URL to the IPC JSP UI.
General remarks:
The CRM UI embeds the IPC JSP UI (configuration user interface).
Both applications need to run in the same domain and use the same protocol (HTTP/HTTPS) for security
reasons ("same-origin policy") as the CRM UI triggers Javascript-events in the IPC JSP UI.
If both UIs don't have the same domain (and protocol) the interaction between those UIs is not working and
configuration results cannot be passed from IPC JSP UI to CRM UI in sales processes.
This requirement is not implemented by SAP but by the browser vendor (e.g. Microsoft).
This requirement is due to the so-called "same-origin policy", which is an important concept in the web
application security model.
For a general description of the "same-origin policy" see also .http://en.wikipedia.org/wiki/Same-origin_policy
The integration of the IPC JSP UI into the CRM UI uses domain-relaxation in a way as it is roughly described
in section "Relaxing the same-origin policy" (part "document.domain property") in this Wikipedia-article.
2017-07-17 Page 1/4
© 2017 SAP SE or an SAP affiliate company. All rights reserved

2. It is not allowed to maintain an IP address as URL to the IPC JSP UI as domain-relaxation would not be
possible in this case.
See documentation in spro at the following IMG activity:
"Customer Relationship Management -> Basic Functions -> Product Configuration -> Define URLs."
Solution
Important: Set up URL to CRM UI and URL to IPC JSP UI in a way that both applications use the same
domain and the same protocol (HTTP/HTTPS).
Examples for valid/invalid domain/protocol combinations:
Example 1:
CRM UI is using domain/protocol " ".https://crmhost.example.com
IPC JSP UI is using domain/protocol " ".https://j2eehost.example.com
-> Correct. Both applications use the same domain "example.com" and same protocol "HTTPS".
Example 2:
CRM UI is using domain/protocol " ".https://crmhost.example.com
IPC JSP UI is using domain/protocol " ".http://j2eehost.example.com
-> Incorrect. Both applications use the same domain "example.com" but use different protocols ("HTTPS" for
CRM UI but "HTTP" for IPC JSP UI).
Example 3:
CRM UI is using domain/protocol " ".https://crmhost.example.org
IPC JSP UI is using domain/protocol " ".https://j2eehost.example.com
-> Incorrect. Both applications use the protocol "HTTPS" but are running in different domains ("example.org"
for CRM UI but "example.com" for IPC JSP UI).
Example 4:
CRM UI is using domain/protocol " ".https://crmhost.example.com
IPC JSP UI is using domain/protocol " ".https://j2eehost.corp.example.com
-> Incorrect. Both applications use the protocol "HTTPS" but are running in different domains ("example.com"
for CRM UI but "corp.example.com" for IPC JSP UI, which is considered different).
Example 5:
CRM UI is using domain/protocol " ".https://crmhost.example.com
IPC JSP UI is using domain/protocol " ".https://127.0.0.1
-> Incorrect. Both applications use the protocol "HTTPS" but are running in different domains ("example.com"
for CRM UI but IP address for IPC JSP UI).
Special requirement: External/Internal access of CRM UI and IPC JSP UI
In your organization you have set up your CRM UI that it is accessible from inside your company's network
as well from outside via e.g. SAP Web Dispatcher.
In this case you have to keep the following in mind for setting up the IPC JSP UI:
If a URL is maintained for the IPC JSP UI in COMM_IPC_URL that is not accessible e.g. from outside
the company's network, the IPC JSP UI would not be accessible in that case when the CRM UI is
accessed from external.
2017-07-17 Page 2/4
© 2017 SAP SE or an SAP affiliate company. All rights reserved

3. The same applies if a URL is maintained that is not accessible from inside the company's network.
Then the IPC JSP UI would not be accessible in that case when the CRM UI is accessed from internal.
It is only possible to maintain one standard URL for the IPC JSP UI in COMM_IPC_URL.
There are several possible solutions if you need the IPC JSP UI to be accessible for internal and external
access.
Step 1:
First of all the URL of the IPC JSP UI maintained in COMM_IPC_URL has to be configured that it can be
accessed via an external URL (which can also be accessed from internally).
This can be achieved by configuring the SAP Web Dispatcher that it maps an external domain to the actual
internal one (see SAP Web Dispatcher documentation on details how to map external URLs to
internal URLs).
Example:
Actual internal domain of IPC JSP UI: " "https://j2eehost.internal.example.corp
External domain maintained in SAP Web Dispatcher: " "https://j2eehost.example.com
This external domain for the IPC JSP UI has to be maintained in table COMM_IPC_URL (destination
"UI_CFG") using
transaction spro:
-> "SAP Reference IMG"
-> "Customer Relationship Management"
-> "Basic Functions"
-> "Product Configuration"
-> "Define URLs."
After this step the IPC JSP UI is accessible from external and internal.
Step 2:
Depending on your current setup for the external/internal access to the CRM UI you have to do further
adaptations, because the URL for CRM UI and IPC JSP UI maintained in SAP Web Dispatcher have to use
the same protocol and domain (both for internal and external access).
Situation A:
You have set up same a domain for internal/external access to CRM UI
Example:
Current internal CRM UI URL: ...https://crminternal.example.com/sap/bc/bsp/sap/crm_ui_start
Current external CRM UI URL: ...https://crmexternal.example.com/sap/bc/bsp/sap/crm_ui_start
URL to IPC JSP UI (as set up in step 1 above): "https://j2eehost.example.com
Solution A:
In this case all 3 URLs (external, internal and IPC JSP UI) would use the same domain and protocol
("example.com" and "HTTPS").
With this solution the URL for the IPC JSP UI could be shared between internal and external accesses.
The entry in COMM_IPC_URL with destination UI_CFG would be sufficient pointing to the SAP Web
Dispatcher URL for the IPC JSP UI.
Situation B:
You have set up different domains for internal/external access to CRM UI
2017-07-17 Page 3/4
© 2017 SAP SE or an SAP affiliate company. All rights reserved

4. Example:
Current internal CRM UI URL: ...https://crmhost.corp.example.net/sap/bc/bsp/sap/crm_ui_start
Current external CRM UI URL: ...https://crmhost.example.com/sap/bc/bsp/sap/crm_ui_start
URL to IPC JSP UI (as set up in step 1 above): "https://j2eehost.example.com
In this example the external CRM UI URL and URL of IPC JSP UI use the same domain/protocol. So, the
IPC JSP UI would already work for the external access.
But the internal CRM UI URL uses a different domain than the IPC JSP UI ("corp.example.net" versus
"example.com"), which leads to the fact that the IPC JSP UI cannot be used if users log on to CRM UI using
the internal URL.
Solution B.1:
Advise all users to use the external URL to access CRM UI.
No further changes need to be done in that case (except the SAP Web Dispatcher setting for the IPC JSP UI
as described above).
From a complexity point of view this would be the easiest solution.
Solution B.2:
In order that the integration of the IPC JSP UI works also for the internal access, the internal CRM UI URL
need to use also domain "example.com".
The SAP Web Dispatcher needs to be set up for the internal access that also a URL with only domain
"example.com" is used for internal access to the CRM UI
Example:
Current internal CRM UI URL: ...https://crmhost.corp.example.net/sap/bc/bsp/sap/crm_ui_start
The SAP Web Dispatcher would define a URL like
..., which would route to the actual internal CRMhttps://internalcrm.example.com/sap/bc/bsp/sap/crm_ui_start
UI.
This new internal URL would be used for internal access. Please advise your business-users accordingly.
In this case all 3 URLs (external, internal and IPC JSP UI) would use the same domain and protocol.
With this solution the URL for the IPC JSP UI could be shared between internal and external accesses.
Other Components
Component Description
CRM-BTX-BF-CFG Product Configuration
| | | |Terms of use Copyright Trademark Legal Disclosure Privacy
2017-07-17 Page 4/4
© 2017 SAP SE or an SAP affiliate company. All rights reserved