Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to connect to InterQual environment

SA-11228

Summary



Integration does not work and you receive a blank frame and a script error when logging in.

You have followed the procedure stated in the below PDN document on McKesson InterQual Integration Solution For The Care Management Framework Technical primer.


https://pdn.pega.com/documents/mckesson-interqual-integration-solution-for-the-care-management-framework-711-technical-primer

Error Messages



Permission denied
Line: 96
Char: 9
Code: 0
URI: http://<InterQual>/rm/iqm/js/rm_login.js


Steps to Reproduce



1. Create a custom Auth flow.
2. Include the InterQual scripts in the harness. Update the CMFMKScript with the InterQual environment URL.
3. Create a flow action similar to InvokeGuidelines.
4. Create a data transform similar to GuideLineSetup.
5. Call the data transform in the pre-action of the flow action.
6. Create a section similar to what CMF uses in InvokeGuidelines.
7. Update the MKRequestFrame section to show the iframe (by updating the DIV visibility or by calling the function showCERMEDiv).
8.Run the flow.


Root Cause



The root cause of this problem is an error/omission in product documentation. 

The PRPC and McKession InterQual integration requires same domain orgin policy to be satisfied. The current design imbeds the InterQual application into an iframe in PRPC. There is communication from the PRPC UI to the iframe and from the iframe back to PRPC. This design therefore requires that both PRPC and Interqual are accessible from the same domain, that is the same hostname and port for the URL for accessing both applications.


Resolution



The explanation for this behavior is as follows

There are several ways to accomplish this same domain orgin policy:

1. Install the InterQual application on the same server as PRPC. Not the same JVM, but a different JVM on the same server. 

2. Use a proxy configuration so both applications can be accessible from the same hostname and port but are still installed on seperate servers. 


Using Apache mod_proxy example:

In this example PRPC is already accessible through Apache using a standard application server plugin, WebSphere or WebLogic plugin. The requirement is to also get the content for Interqual using the following mod_proxy rules:

ProxyRequests Off
ProxyPreserveHost On
ProxyPass /rm http://<Interqual Host:port>/rm nocanon
ProxyPassReverse /rm http:/<Interqual Host:port>/rm


These settings assume "/rm" is the context root of the Interqual server.

Apache would use the application server plugin for obtaining content from PRPC.
Apache mod_proxy would be used for getting content from InterQual.

Then both PRPC and InterQual can be accessed through the same apache server host:

http://<apache>/prweb/PRServlet
http://<apache>/rm/login
Suggest Edit

Published July 1, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us