The difference is window.open is a client side action and it will open the URL in a new browser window and response.redirect is a service side action that directs the current browser to the URL. Please remember to click 'Mark as Answer' on this post if it helped you. Just append the url to the GET string and redirect based off that. UPDATE: As mentioned in the comments, it is probably a good idea to restrict the redirect from the GET parameter to only work for domain-less relative links, refuse directory patterns (./), etc. The data in a TempDataDictionary object persists only from one request to the next, unless you mark one or more keys for retention by using the Keep method, accoding to your code, if you redirect to login page, and then redirect to index, the value will be null. You can only read it at login page.
SAP Portal redirect method steps
The situations where it does work include the following methods of a browser loading a URL: clicking on a straight HTML link; submitting a form, using POST or GET, from a submit button, or client-side script (form.submit) The situations where it doesn’t work: using Response.Redirect / Server.Transfer. This causes null to be in the URL, even if you have no options. So I figured, because caching is off by default, this should be appending a timestamp. But it actually appends null. So I thought I'll set it to be cachable, which then forced me to put null which didn't fix the problem.
Summary:-
This document contains the information about to implement the redirect method on SAP Portal system.
Created by: Brindavan Mookaiah
Designation: SAP BASIS Consultant
Table of content
- JSPM tool……………………………………………………………………
- Deploy the redirect.ear……………………………………………………..
- How to use………………………………………………………………………..
Steps 1
How to use JSPM to install EAR files
Download the EAR file from service market place and copy it to the import directory similar to this: usr/sap/sapmnt/trans/EPS/in.
Start JSPM using additional config parameter. Typically you can find the batch file to start JSPM here: usr/sap/<SID>/J00/j2ee/JSPM/go
-config=/jspm/deployVersionRule=updateAll
Sap Redirect Url Is Null Hypothesis
-config=/jspm/forceMode=true
step 2
Starting JSPM
Please consider to use the <SID>adm or administrator user. Then choose package type Hotfix and click Next. Select the file to deploy and confirm by clicking Next.
We recommend to remove the EAR file from directory usr/sap/sapmnt/trans/EPS/in after a successful import.
Step 3)
How to use
1)Make the “sap.com/redirect*redirect” policy configuration use your specific authentication protocol (e.g. make it use SPNegoLoginModule or other specific authentication method)
2)Use an alias to access your application e.g. if you want to change the authentication for the Portal, instead of http://<host>:<port>/irj use http://<host>:<port>/redirect. To change the authentication for another application use: http://<host>:<port>/redirect?url=/customapp
As a result, the redirect application will force authentication and then redirect to the initially desired application.
Redirect Url In Html
Note: You find the file redirect.ear is applicable on SAP NetWeaver 7.01 and above and redirect_700_640.ear is applicable NetWeaver 6.40, 7.00, 7.01 and 7.02 .
Symptom
- Upon logging into the Enterprise Portal you are encountering a Portal runtime error exception across specific instances.
- When analyzing the default trace file you highlight several error exceptions as pointing to URL Caching:
- NavigationService.redirect: recieved exception when calling to redirectors with URL (null result is returned from redirect) [EXCEPTION] javax.naming.NamingException: The old URL is null at com.sap.portal.ivs.global.navigation.connector.NavigationRedirector.redirect
Read more...
Environment
Product
Keywords
Enterprise Portal 7.0, EP 7.0, Enterprise Portal 7.01, EP 7.01, Enterprise Portal 7.02, EP 7.02, Enterprise Portal 7.1, EP 7.1, Enterprise Portal 7.2, EP 7.2, Enterprise Portal 7.30, EP 7.30, Enterprise Portal 7.31, EP 7.31, Enterprise Portal 7.40, EP 7.4, FPN, Cache, clearing, old, URL, retained, null, NavigationService, redirect, recieved, exception, redirectors, clear, Navigation, FPN, , KBA , EP-PIN-NAV , Navigation , EP-PIN-FPN , Federated Portal Network , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.