Unknown characters in URL iView

Hi,
I am working on EP 7 SPS14.
I am trying to create URL iView. Content of the URL iView is not in English language.
If I select full content , iView content is displayed correctly.
However, if I use captue method to select only part of iView language specific characters such as ð, í, á , ö are not displayed correctly.
I checked encoding of URL . It is ISO-8859-1.
My guess is that while using capture method portal is not able to convert it into UTF format.
Anyone faced this issue earlier?
Thanks & Regards,
Apurva

Hi Apurva,
Try setting the parameter "Forced Request Language" with the language which the original URL is in.
Hope this helps.
Thanks,
Ansar

Similar Messages

  • Authentication in an application placed in an URL iview in the portal

    Hi all gurus!
    I have a delicate problem: we have an application that we have deployed on the same WAS as the portal runs on and that application is presented through an URL iview in the portal.
    We want to use the LogonTicket created by the portal for authentication in the application and a colleague of mine put a "*" (asterisk) for requested roles in the web xml file. The problem is that the users had to be administrators in the portal in order for it to work and that is not very suitable. If you removed the admin role from the users the authentication stopped to work.
    Does anyone have a step by step guide on which files to configure and how to do it properly? I have googled the problem and also searched the forum but I haven't found any solutions. My colleague followed this description and that didn't help:
    [http://e-docs.bea.com/wls/docs70/webapp/security.html]
    I forgot to mention: it's 7.1 portal we are using.
    All the best!
    Benny

    Hi Sridhar.
    Thanks for the links. I followed them but I can see that SAP either are general in their instructions or, if specific, talking about Visual Admin, in any case they couldn't give a complete assistance.
    Never the less I have managed to come a bit further by creating a UME role from within Identity Management in the portal and adding the application of interest to the role under the tab "Assigned Actions".
    So now I'm also logged into the application when I logg on to the portal, I can see that in the portal logs. But, when I'm going to take the last step which invokes the call of a service I get a new error.
    Here are two entries from the "Default trace" and beneath are two entries from the "SAP Log". I comment further in a separate answer since I otherwise exceed the maximum character length...
    com.sap.security.core.server.jaas.
    Default Trace
    Message: Authentication failed. For details see log entry 0016D4475ED5021D0000000100000A84 in security log.
    [EXCEPTION]
    javax.xml.ws.soap.SOAPFaultException: Authentication failed. For details see log entry 0016D4475ED5021D0000000100000A84 in security log.
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.processFault(JAXWSUtil.java:407)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1164)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:818)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:759)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)
    at $Proxy1882.purchaseRequestCreate(Unknown Source)
    at com.q2d.jpetstore.model.PurchaseRequestFacade.createPurchaseRequest(PurchaseRequestFacade.java:43)
    at com.ibatis.jpetstore.presentation.OrderBean.newOrder(OrderBean.java:157)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.struts.beanaction.ActionInvoker.invoke(ActionInvoker.java:16)
    at org.apache.struts.beanaction.DefaultActionInterceptor.intercept(DefaultActionInterceptor.java:5)
    at org.apache.struts.beanaction.BeanAction.execute(BeanAction.java:246)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:471)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:462)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Date: 2009-07-06
    Time: 17:17:58:616
    Category: com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding
    Location: com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding
    Application: com.sap/wstore2EAR
    Message: process()
    [EXCEPTION]
    com.sap.engine.interfaces.webservices.runtime.ProtocolException: Authentication failed. For details see log entry 0016D4475ED5021D0000000100000A84 in security log.
    at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.logThrowable(ProviderSecurityProtocol.java:1074)
    at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.afterDeserialization(ProviderSecurityProtocol.java:710)
    at com.sap.engine.services.webservices.espbase.server.runtime.ProtocolProcessor.protocolsAfterDeserialization(ProtocolProcessor.java:156)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:421)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:246)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:176)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:112)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:70)
    at SoapServlet.doPost(SoapServlet.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:471)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:462)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.wssec.policy.exception.VerifyException: [_policy1000] Authentication failed. For details see log entry 0016D4475ED5021D0000000100000A84 in security log.
    at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.authenticate(ProviderSecurityProtocol.java:250)
    at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.afterDeserialization(ProviderSecurityProtocol.java:682)
    ... 45 more
    Date: 2009-07-06
    Time: 17:17:58:613
    Category: com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment
    Location: com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment
    Application: sap.com/WebShopEAR

  • URL iView in Web Page Composer

    Hi,
    I have created a URL iView in the PCD and I wanted to embed this iView in the container of the Web Page Composer page.
    I have created an entry point to the PCD folder that contains the URL iView.  The PCD URL to the iView is
    http://abc.abc.net:50000/irj/servlet/prt/portal/prtmode/default/prtroot/pcd!3aportal_content!2fcontentlib!2fcommercial!2fiviews!2fcollaboration_wpc!2fiviews!2fpetroleum_tmu!2fcom.bhpb.com.gen.url_iview
    The URL iView is a simple URL iView that redirects to http://www.google.com
    When I drag and drop the URL iView to the container, I saw from the container properties that the URL to the iView is change to
    http://abc.abc.net:50000//irj/servlet/prt/portal/prtmode/default/prtroot/pcd!3aportal_content!2fcontentlib!2fcommercial!2fiviews!2fcollaboration_wpc!2fiviews!2fpetroleum_tmu!2fcom.bhpb.com.gen.url_iview
    A additional "/" has been added to behind the port 50000.  This is weird.....!!!!
    It is causing me problems as we have an IIS Proxy that does redirection reading behind the URL characters after the port 50000.
    Can anyone explain????
    Thanks.
    Mike Lee

    Hello Arun,
    See http://help.sap.com/saphelp_nw73/helpdata/en/e2/44dc299bf548578ef9830c0c1c0f0b/frameset.htm
    Regards,
    Lorcan.

  • Dynamic URL iViews in EP70

    I need to be able to create an URL iView where by the domain and port must be dynamically set in the URL. Is there an easy way to accomplish this using EP70?

    Hello Chris,
    The error is:
    RuntimeException during appliction Java mapping com/sap/xi/tf/_mm_paymentClusterCreate_ Thrown: com.sap.aii.mappingtool.tf7.MessageMappingException: Runtime exception when processing target-field mapping /ns0:mt_newPaymentClusterData/merchant_name; root message: Exception:[java.lang.IllegalArgumentException: Value is too long (471/200):
    It's even in the SAP Help:
    http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce299c3a8e5430e10000000a42189b/frameset.htm
    The length of the attribute value is defined by the XI message protocol. Values can be a maximum of 200 characters long. If, for example, you assign longer values in the mapping or adapter modules then this can lead to processing errors at runtime or the values are shortened to 200 characters. This shortening can also lead to a processing error. The processing error that occurs depends on the components that access the attributes.

  • Set user Language in URL IView

    Hello,
    I am trying to put the Language of the user in the parameters of the URL.
    For example :
    http://sopraganesh.cr.infra.lab/redirect.asp?page=ECD&lang=en
    How can I parameter the URL IView to automatically retrieves the language of the connected user?
    Thanks for your help,
    AN

    Hi
    Once you have defined the iView’s URL to the targeted Web page, you may need to configure parameters that are passed to the information source as part of the URL. In the URL iView Editor, you can do the following to URL parameters:
    ·        Add, remove, and modify URL parameters
    ·        Determine whether or not portal end user can view and personalize URL parameters at runtime
    ·        Assign intuitive display names to URL parameters that are viewed or personalizable by portal end users
    ·        Specify the URL request method (GET or POST)
    If you navigated to the targeted Web page and defined the iView URL using the portal built-in browser, the URL parameters and request method may already been defined in the URL iView Editor.
    Procedure
           1.      Open the iView in the URL iView Editor.
    The editor does not display URL-specific parameters in the URL address within the URL box. URL parameters that were part of the URL referencing the selected Web page (the information source) are automatically removed from the source URL and displayed in the URL parameter list in the editor. At runtime, the portal automatically appends the URL and the listed parameters to the targeted URL request.
           2.      In the Request Method option, choose either GET or POST to specify the request method. The request method indicates how the browser sends information to the information source:
    Request Method
    Description
    GET
    This request method appends parameters to the URL when the data request is sent to the information source. The server receives the data in one long query string, which typically limits the length of parameters that can be passed.
    For example, a URL using the GET request method would be: http://www.google.com/search.asp?&querystring=SAP where querystring indicates the parameter identifier and SAP is the parameter value.
    POST
    This request method sends parameters for the URL in the header of the data request stream; parameters are not appended to the URL. This allows for long parameters to be passed to a script and parsed one element at a time.
    For example, a URL using the POST request method would be: http://www.google.com/search.asp.
    POST is only supported when the Fetch Method property defined in the iView is set to Server-side. For more information, see URL iView Properties.
    For iViews that have a mixture of parameters sent by GET and POST together, you must:
    §         Choose POST as the request method.
    §         Set the Fetch Mode property to Server-side
    §         Append the GET_EXPLICIT_ prefix to the parameter identifier of each parameter that is sent by GET. For example, a parameter defined as searchstring should be defined as GET_EXPLICIT_searchstring. When the iView sends a data request, the prefix is removed from the parameter identifier at runtime. Parameters sent by POST do not require a special prefix. 
           3.      To add a parameter, click Add below the table. A new entry is added to the parameter list.
    To remove a parameter, select the checkbox of the relevant parameter in the list and click Remove. Before doing so make sure the parameter is not required by the information source.
           4.      Define the attributes of existing or new parameters, as follows:
    Attribute
    Description
    URL Parameter
    Specifies the parameter identifier as recognized by the information source. For example, in the URL http://www.google.com/search.asp?&querystring=SAP, the parameter identifier is querystring.
    As stated above, parameters that need to be sent by GET when the request method is defined as POST, must have the GET_EXPLICIT_ prefix. For example: GET_EXPLICIT_searchstring.
    Enter special characters that are present in the parameter identifier as is. Do not convert them to ASCII code. For example, enter first name, and not first%20name. At runtime, the portal will encode special characters to ASCII when fetching the iView data.
    Value
    Specifies the value of the parameter. This is not mandatory.
    If you set the parameter as a variable that can be personalizable by end users (see following attribute), then this value will be the parameter’s default value. However, if you set the parameter as not personalizable, then this value is the fixed value of the parameter.
    Enter special characters present in the parameter value as is. Do not convert them to ASCII code.
    Type
    Specifies the data type of the parameter.
    Choose one of the following options:
    ·        String: Apply this option for all data types whose property is not a mapped user name or password; for example, an integer or string.
    ·        Mapped User: Apply this option when the URL parameter designates a “user name” that is required to authenticate the user with the information source at runtime.
    ·        Mapped Password: Apply this option when the URL parameter designates a “password” that is required to authenticate the user with the information source at runtime.
    §         When Mapped User and Mapped Password are selected, the Value and Personalize attributes cannot be edited.
    §         If you want to enable user mapping for the user name and password parameters, in the System drop down-down list, choose an appropriate system already defined in the portal, which contains the necessary settings. See Selecting a System.
    Personalize
    Specifies whether or not portal end users can view the parameter and its assigned value if they personalize the iView at runtime. This attribute also allows you to determine whether or not end users can personalize the parameter value.
    Choose one of the following options:
    ·        Hidden: The end user does not see the parameter and its value. This is the default setting.
    ·        Read / Write: The end user sees the parameter and is able to modify its value.
    ·        Read Only: The end user sees the parameter and the fixed value assigned to it. The end user cannot modify the parameter value.
    Name
    Specifies an intuitive display name for the parameter identifier. If you set the parameter to be viewable by end users at runtime, this name is displayed instead of the parameter identifier, which is often abbreviated and unintuitive.
    This attribute is available only if Read / Write or Read Only is selected in the Personalize attribute. If you do not specify a name, the Personalize attribute will be reverted to Hidden.
    with regards
    subrato kundu

  • Dynamic URL Iview

    Hi
    We need to show language specific content to the user logged in. We have different URL for each language.
    We are using URL iviews in portal.
    If a Arabic user logs into portal I want him to see the Arabic page by default. If a English user logs on I want him to see the English page by default.
    I wanted to know whether it is possible to change the URL dynamically depending on the user profile.
    Rgds
    NagaKishore V

    Hi
    My req is
    We are using url iviews for in portal. We have web pages for different languages.  Req. is when a user with Arabic as language preference logs in he should see the web pages in Arabic. If the user preference is Japanese he should see Japanese pages. We dont want to maintain mulitiple iviews for each language. The webpage urls are in this format
    For englisj ;--  www.xxx.com/yyy/en
    for japanese - www.xxx.com/yyy/jp
    for arabic - www.xxx.com/yyy/ar
    Since only the last 2 characters are differeent and rest of the url is same, Is there is a way where we can create 1 iview and depending on the user preference he is navigated to that page.
    Regards
    NagaKishore V

  • Unable to create HTTPS url iview

    Hi,
    We are unable to create https url iviews. Neither our own iview for adding url's or the standard template for creating url iviews are supporting the https protocol.
    The error message is: 'Unknown protocol: HTPPS'.
    We are using EP5 SP4, J2EE 6.20.
    Any ideas?
    Mohammed

    Hi,
    I left the default query as it is and specified my Search Component Set & Search Options Set in the Search Component Set and Search Options Set fields resp. Now when I do a Search, it does return the results and when I preview my iview, I see a text box and a Search button next to it. I also, see a "Show Options" link and I need to get rid of it. How can I do it? Can anyone please help me? Is this something which I need to do in the Search Component Set or Search Options Set? Any help will be greatly appreciated.
    Thanks,
    Sri

  • SSO to BW reports via URL iView

    Hi all,
    I've searched the forum on this but could not get a clear guide. Here's my scenario:
    1. We use Windows logon credentials to sign on to the Enterprise Portal
    2. Once signed in, authorized users load a URL iView.
    3. The iView contains URL links to SAP BW reports.
    4. Based on user's role, they can access only certain reports.(Available report URLs will be different)
    5. User clicks on the link and opens another Internet Explorer window to show the BW report <b>without signing on</b> again.
    Key question: How do we incorporate the SAP Logon Ticket into the URL and how do we configure BW server to accept SSO based on this URL?
    Any help is much appreciated. Thanks!

    Hi Kok,
    The first step is you need to create a system object under system administration --> system configuration --> system landscape. Expand the portal_content. Right click the folder and create a new folder. Then right click on the folder to create a new system. This system object should point towards the BW system. You need to give the details of the BW server. The right click the system object and create an alias.
    If you are using BW 3.5, you need to follow the 13 steps given under img. If BW version < 3.5 then you have to export the portal ticket to BW and BW ticket to EP.
    Regards
    Arun

  • Problem with URL iView regarding fetch mode and SSO to non-sap webapps

    Hi,
    I have created an URL iView which opens an internal webapp. When the fetch mode is set to client-side the page is displayed for the user. But when I set the fetch mode to server-side, the page cannot be displayed by the user.
    No proxy is needed. I tried to open the wepapp direcly on the portal server without any problem. Are there any additional points to be considered?
    On the other hand I want to realize SSO to this webapp (form based authentication) with user mapping. Is it correct, that I have to user server-side fetch mode, when I want to use the POST request method?
    Thanks ahead,
    Bernd

    >
    Bernd Speckmann wrote:
    > On the other hand I want to realize SSO to this webapp (form based authentication) with user mapping. Is it correct, that I have to user server-side fetch mode, when I want to use the POST request method?
    Yes.
    >Are there any additional points to be considered?
    Have a look at System Administration - System Configuration - Service Configuration - Applications - com.sap.portal.ivs.httpservice
    This is used to do the Server side fetch.
    Have fun
    Johannes

  • Configuring SSO to a URL iView

    hi everyone......
    i'm relatively new to EP....
    and my requirement is.....
    i've created a URL iView and when i logon to the portal.....i need my <b>yahoo or gmail inbox</b> to appear in this URL iView.....
    i read frm a thread that i need to confgure SSO for this by creating a system....
    can u plz guide me how to configure SSO and also the usermapping.......
    help is highly appreciated....
    thanks and regards,
    Sudheer

    Hi Sudheer,
    Please Ensure The following:
    SSO with Yahoo:
    UPLOAD:
    1.Upload the par in PCD
    SYSTEM CREATION:
    1)Create ->System from par -> select com.sap.portal.howtos.webapp -> web application->give name & Id
    2)Properties-->object->system definition
           Name of the server : login.yahoo.com
           Port : (empty)
           URI :/config/login
    3)create alias
    4)set user Mapping
    IVIEW CREATION:
    1)Iview from par
    2)Iview type:com.sap-appintegrator.sap
    3)template:generic
    4)Properties Setting:
         System : (system alias name )
         URL Template :<System.protocol>://<System.server><System.uri>?<Authentication>
         URL Template fragment for UserMapping: <System.protocol>://<System.server><System.uri>?<Authentication>
    Regards,
    Ramganesan K.

  • How to change the URL of a URL-iView over Code ?

    Hi all,
    i am getting started with the Portal-Application-Developement and want to change the URL of an URL-iView on runtime with java-code.
    i have read the context and can get the Property url with this statement.
    endContext.getProfile().getProperty("url")
    But if i change this property, nothing is done.
    endContext.getProfile().setProperty("url", "http://www.yahoo.com");
    Where is my fault.
    Thanks for help.
    Regards Jürgen

    Hi,
    the context is of Type IPortalComponentContext.
    I cant find no method getParameter() at the context or the profile.
    The methods to read the properties of the URL-iView are
    context.getProfile().getProperty("url")
    context.getProfile().getAttributeValue("url")
    But if i want to set (change) this attribute, nothing is done.
    Regards Jürgen

  • How to pass SSO Login Ticket to an URL iView

    Hello experts,
    We have an application running on Netweaver and it is setup to accept SSO Login Tickets for authorisation.
    I have the following question:
    We want to expose some of the portlets in our application in a portal page using URL iViews, but we don't know, how to setup this environment, so for each iView, the SSO Login ticket is passed to the portlet of our application (this way access to it can be granted)?
    How can we achive this? Or, is there another approach for this scenario?

    Hi Megha,
    The portlets are part of our application which is deployed on the same Netweaver App server as is the Portal.
    When the user log in into the Portal - SSO Tiket is being issued and we want this ticket to be passed to the URL of the URL iView, but currently HTTP 401 error is returned or HTTP Basic authentication login popup is displayed. We want to be able to use the SSO Ticket for this purpose.
    Regards,
    Georgi

  • Problem with JavaScript in URL iView

    Hi,
    I am facing a problem with javascript when i am trying to access my application through URL iView. In the javascript window.top is used to access the frames in the window. But the EP is not recognizing it as valid. what exctly the problem and please suggest me a solution.
    Ashok.

    Hi,,
    thanks for the quick reply. But what i asked was different. I will put it in different way. I have deployed a application in Web Application Server and trying to access it through URL iView. My application is pure J2EE application with html,jsp and JS files. In javascript we used window.top property of the java script which is working fine MS IE. The problem is window.top is a IE specific property which is not having any equallent open standerd so EP is throwing a java script error. As I know the only possible solution for this problem is inherating IE rendaring capabilities to iView(i.e iFrame). is there any way to do that?
    Ashok.

  • URL iView doesn't open link in new window

    Hi All,
    I'm have an URL iView that I want to display in the portal content area but whenever the user clicks on a hyperlink on that iView launch a new window for the link.
    I've tried using the 'Open iView links in new window' without any success. Is this supposed to work or this property is for another purpose...? Can someone point me to a solution.
    Thanks

    Hi Detlev,
    I checked what you said. I've already looked at that page but didn't saw that important disclaimer. My problem was that I didn't had a captured area-URL iView but a full page-URL iView as it says:
    +These properties are relevant in the following instances only:
    §         The iView content is displayed in its source format. The rendering type must be defined as Keep Source Formatting. See Defining the Look and Feel of the iView Content.
    §         The iView content displays a captured area, and not the entire Web page. See Selecting the Capture Area.+
    I only had to change the 'Open iView links in new window' to Yes after capturing a part of my page and it started working.
    Thanks for sharing

  • Open web page from URL iview in maximized window

    Hi,
    I would like to open a web page in a <b>maximized</b> browser window, using an URL iView.
    I know how to open a window in a separate window, I just can't get it maximized.
    N.B. I do <b>NOT</b> want to open in <b>fullscreen</b> mode, i.e. I want a title bar and menus.
    Does anyone know how to do it?
    I tried to play around with the "window function" property of the iView, but no luck so far. I can't specify a fixed width and height of the target window at design time, as these values may vary at runtime.
    regards
    Lothar

    Hi Lothar,
    Yes, That will require Java Coding, Its true. Basically what the problem here is that to maximize we are trying to fetch the Screen resolution dynamically through Portal that Portal is not allowing us. Thats why I feel that we should go for Java Programing, Create a Par, Deploy it in the server and then create iView for that.
    For Creating the Abstract Portal Component for Opening a Maximized Window You should do following steps.
    1. Open Your NWDS
    2. Create a project ie Portal Application
    3. Create Portal Object ie Abstract Portal Component.
    Now here is the piece of code that may help you
              response.write("<SCRIPT language=javascript>");
              response.write("function onOpenWindow()");
              response.write("{");
              response.write("window.open('http://abc.com','windowName','width=screen.availWidth,height=screen.availHeight,resizable=yes')");
              response.write("}");
              response.write("</SCRIPT>");
              response.write("<a href = \"javascript:onOpenWindow()\">abc.com</a>");
    Paste this code in doContent...
    I think it may help you
    Thanx & Regards
    Anish

Maybe you are looking for