Reaching backend systems through portal is a problem via dispatcher--

Hi Experts,
I am having problem when I try to reach backend systems through the portal from internet. I have configured WebDispacher according to information taken from help.sap.com, but unfortunately the result is not satisfactory. Reaching Portal EP7.0 from internet is successful, but when I changed to iviews that are referring to backend systems then browser comes to a blank page with error. If any of you having an idea on the subject that will much be appreciated.
Regards,
Ali Taner

Hi Hari,
I am sorry that it has been a bit sharp response from my side, but I am confused with what you mentioned. Is the Alias that you mentioned reside on R3 side or Portal side that I should look for, and secondly the Alias should address to local URL or External URL? In my understanding if Alias referring to local URL address than it gets error when somebody tries to reach from internet because local address is not known on the internet. I really appreciate your kind help
Kind Regards,
Ali Taner

Similar Messages

  • Could not connect to backend system through portal via Web Dispatcher

    Web dispatcher redirecting problem
    Dear Experts,
    I have implemented a scenario which comprised of customizing that is developed in Portal EP7. What customizing does is getting report from backend system (ERP 6.0)
    According to the needs for reaching the portal from internet I configured the SAP Web Dispatcher in the environment as you may see its contents below.
    The problem is when I run the customizing in portal system then it requires connecting to backend system (ECC 6.0) to get the data (report). But from this point on web browser comes to a blank page, could not view the data that is from backend system via portal. Because in the time when it tries to retrieve data in backend system, on the left bottom of the explorer the indicator shows internet address that system uses connecting to the backend system as local network address of the backend system which is not known in internet therefore I get blank page.
    The question is how to configure the web dispatcher in a way that both portal and backend systems could be reachable from internet?
    Contents of profile file of Web Dispatcher as;
    SAPSYSTEMNAME = WDP
    SAPGLOBALHOST = portald
    SAPSYSTEM = 02
    INSTANCE_NAME = W02
    DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
    DIR_EXECUTABLE = $(DIR_CT_RUN)
    Accesssability of Message Server
    rdisp/mshost = portald
    ms/http_port = 8101
    Configuration for medium scenario
    icm/max_conn = 500
    icm/max_sockets = 1024
    icm/req_queue_len = 500
    icm/min_threads = 10
    icm/max_threads = 50
    mpi/total_size_MB = 80
    SAP Web Dispatcher Ports
    #icm/server_port_0 = PROT=HTTP,PORT=81$$
    SAP Web Dispatcher Ports
    icm/server_port_0 = PROT=HTTP,PORT=60000
    icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/index.html
    icm/HTTP/redirect_0 = PORT=50000
    #maximum number of concurrent connections to one server
    wdisp/HTTP/max_pooled_con = 500
    wdisp/HTTPS/max_pooled_con = 500
    Configuration for medium scenario
    icm/max_conn = 500
    icm/max_sockets = 1024
    icm/req_queue_len = 500
    icm/min_threads = 10
    icm/max_threads = 50
    mpi/total_size_MB = 80
    Regards,
    Ali Taner

    Hi,
    To resovle this you must have registered FQDN for your backend system as well. When you call the report from Portal using internet it should call that FQDN of your backend system then DNS will resolve this & you will get the expected page. This way only you can resolve this issue.
    Thanks,
    Sachin Sable

  • Error while trying to open an added backend system in portal

    Hi All,
    I need one help.
    I have added our Backend SAP SRM system in the Enterprise portal and it worked good.
    But now if I try to open the added SRM system in the below path
    System Administration à System Configuration à System Landscape -> portal contents -> system backends -> MY SRM(added system)
    I am facing the error page cannot be displayed error as below
    The page cannot be displayed
    Explanation: There is a problem with the page you are trying to reach and it cannot be displayed.
    Try the following:
    u2022     Refresh page: Search for the page again by clicking the Refresh button. The timeout may have occurred due to Internet congestion.
    u2022     Check spelling: Check that you typed the Web page address correctly. The address may have been mistyped.
    u2022     Access from a link: If there is a link to the page you are looking for, try accessing the page from that link.
    Technical Information (for support personnel)
    u2022     Error Code: 500 Internal Server Error. The request was rejected by the HTTP filter. Contact the server administrator. (12217)
    Please help me to solve it, Thanks a advance.
    Thanks,
    Senthil

    Hi,
    Are you using any webdispatcher or some proxy? Is there any URL filter configured in between?
    If yes then I think you have to allow these pages.
    Regards,
    Vamshi.

  • Failure to connect to backend system in Portal

    Hi Experts,
    I was hoping someone could help, quickly!!
    We are having an issue with transporting our VC model.  We are on VC 7.0 SP17
    I created a model in our development environment using a variable input form and adding the value help feature.  After we deploy in our dev environment the model looks perfect!!!
    We transported the VC model as an iview through the portal and we get a Failure to connect to back end system error.  We ruled out that it is not a transport problem using the portal.
    Can someone help!! 
    Thanks so much, Anna

    Hi Again,
    Thanks for both of your response, however, there is nothing in the log files andt we still have the Application error message, failure to connect to backend system.
    We were able to bypass the error and the model starts to "semi-function" - but we cannot access the characteristic through value help, we just get empty drop downs.   We all have the proper authorization in BI....
    Do you think there is a permission problem in the back end portal?
    Hopefully you can help.
    Thanks so much, Anna

  • Change backend system of portal

    Hi,
    We want our EP7 portal to point to a different backend system. We want no references to the old backend system.
    I know the following steps:
    1) create new system
    2) Change the Webdynrpo Jco connections
    Please let me know the other steps that needs to be taken care off while changing the backend system?
    Thanks,
    Antar

    No other steps needed. It is fine.
    Once you delete the old system then you can test it by creating a SAP Transaction iview
    during the creation it will give you a drop down of all system aliases in the portal.
    Raghu

  • Will SSO accepts "Alias name" in bakend system  through portal?

    Hi All,
    Our issues comes here.... Our client user ids are different from backend user ids...let's say.. <b>pradeep.venkat</b> in portal and <b>pradeep</b> in R/3. we want to use microsoft ADS as LDAP. if i want to user SSO deftly the user names must be same..or i need to make reference system.
    My question is:
    Whether SSO accepts "Alias name" in backend system(<b>Pradeep</b> as <b>pradeep.venkat</b>.
    If yes then what all the services of ITS which needs to be activated?
    how to integrate portalw with R/3 using Alias name when sso is active?
                          <b>OR</b>  
    Is there any possibility of using usernames as alias names in ADS(LDAP).
    Ur suggestions are highly appreciated with rwds points..
    Does this issues occured any where...with anybody...
    rgds
    pradeep

    The ADS admin can add a SAP entry to the schema which can include user name in the different systems such as BW, R/3, etc. This can then be populated by the admin or user to include the different logons and passwords in each system. Modifying the schema is not what they like to do but the hassle of syncronizing the users logon to the NT logon is more then your end uses can handle. I know because I had to do it once. It took months for everything to settle down. See notes 608781, 386762. These should explain the proccess.
    Please award points if this was helpfull.
    Greg

  • How to find the backend system in portals

    Hi Gurus,
    How to determine the number of backend systems referred in portals.
    Higher points will be rewarded for useful inputs.
    Thanks in Advance,
    Dharani

    Hi Dharani,
    if u have the system Administration role,
    u navigate thro System administration -> System configuration -> System landscape Overview.
    this iview will list all the system created for connection.
    If u want further clarification , feel free to raise q in forum

  • Unable to connect backend applications through EP in DMZ1 firewall?

    Dear all,
    To brief our landscape, its look like below.
    Internet -> DMZ1(Webservers)->Portal(DMZ2)->Internal(Backend Systems).
    We tried to access the backend systems through portal in DMZ2..its working fine. When we tried to access the portal in DMZ1...its coming perfectly, when we access the backend applications through portal in DMZ1...its not coming...it says...operation timed out...
    Kindly suggest me what would be the problem...all the ports are open in DMZ1 and DMZ2... But we hav not done reverse proxy in DMZ1(Webservers), Can we try after doing Apache reverse proxy in DMZ1. Pl suggest me
    Rgds
    PRadeep

    Hi Netanel,
    Thanks for ur reply...
    See, we hv writen a rewrite rule for all three systems like R/3, BW and SCM
    RewriteRule ^/sap(.)/public(.) http://myr3sever.company.domain.com:r3port/R3$1 [P]
    RewriteRule ^/sap(.)/bc/bsp/sap(.) http://myscmsever.company.domain.com:scmport/SCM$1 [P]
    etc..
    We are differentiating the systems with their names...but when it rewrites..its taking R3 string as well in the path...
    Like
    http://webserver.company.domain.com/R3/sap/bc/gui/sap/its/webgui.
    I think if we remove R3 string at the time of rewrite, then we should be able to get i belive.
    kindly suggest me
    Rgds
    PRadeep

  • How to develop portal application connecting to SAP R/3(backend system)

    Hello Everyone,
                            Can anyone guide me on how to create portal aplication(JSPDYNPAGE), that will connect to backend SAP R/3 system, & it will fetch the data from some table from that R/3 system. Any reference material will be appriciated, it will be of great help.
    Thanks
    Chetan.

    Hi Chetan,
    Connection to R/3 systems through Portal can be done in many ways. Since you have mentioned that you are using jspdynpage then its better that you use JCo for connecting to R/3 system.
    U can write the JCo code using the jspdynpage component. I hope you have pdfs related to JCO. Incase u dont have then give me you mail id. OK
    Another approach could be developing a web dynpro java application that access a r/3 table using a BAPI. You can a dynpro model to easily connect to R/3 system.
    Just develop an iview based on this web dynpro application. And finally navigate to this iview through your jspdynpage.
    I hope this helps you in some way
    Regards,
    Prasanna

  • How to create 'system' in Portal for backend

    Hi Basis Gurus,
    Please let me know how to create a 'system' for a backend system in Portal 'system administration'       --> 'system configuration' --> 'system landscape'.
    i.e. which properties I need to fill up, assuming the backend system is release 700 ABAP system and Portal is at release 640.
    Thanks & Regards,
    Kunal.

    Hi,
    Please check the following links..
    [Creating Systems|http://help.sap.com/saphelp_nw70/helpdata/EN/ec/0fe43d19734b5ae10000000a11405a/content.htm]
    [Editing Systems|http://help.sap.com/saphelp_nw70/helpdata/EN/42/11e43d19734b5ae10000000a11405a/content.htm]
    Regards,
    Murthi...

  • Publishing through Portal - "Connection to backend system failed"

    We are having a problem publishing documents through our SAP Portalu2019s service u201CPublish Course Contentu201D under Course Administration.
    When we go to publish, we get a status u201CConnection to backend system failedu201D with the message u201CNo message availableu201D.
    We are running:
    Portal on NW 7.0 EhP1, Support Package 04.
    ABAP on ERP 6.0, EhP4, Support Package 18.
    Both the Portal and ABAP systems are running on Linux RHEL5, with an ORACLE 1.0.2.4 database. 
    Portal and ABAP are on different servers.
    Not certain if this is significant but under System Configuration, if I open my ABAP back-end systemu2019s configuration and perform connection tests, the overall Connector test fails.
    We also have a sandbox system on which we did the configuration first. We have compared all of the values for the configuration we have done to ensure they are configured the same. On the sandbox, the connection test is successful and we can publish content without error.
    I have been trying to review the various trace files, increase trace levels, etc. both on the ABAP back-end system and on the Portal. I have been able to find anything that appears significant but this is probably due to my not knowing what to look for.
    Which specific trace files should be reviewed for the root cause of the issue? What are the exact steps the Publish process takes to accomplish its work? If we know the exact steps it takes (how it communicates, what modules it uses, what accounts) we might be able to determine the root cause.
    We are using a SAML login to our portal for authentication and have removed the Basic password login module from the Authentication Stack u201Cticketu201D. We have established trusted RFCu2019s between the ABAP and Java instances for the Publishing function. When authentication is configured, we try to use the highest form available in the configuration. We use Assertion tickets if available, it not, we use Logon Tickets, if not available, we would then select X.509 certificates and if that were not available, would select Username and password. 
    Any ideas as to what we should be looking at would be greatly appreciated. I have searched both SDN and SAPNet for similar situations and not yet found something that corrects the problems.
    Thank-you in advance,
    Deb Nugent.

    Arun,
      Thank-you for your suggestions. The ABAP back-end system is up and I have verified the connection properties. I have had others verify as well. All appears correct.
      The default trace files, through NWA, show the messages:
    BackenConfig not correct. processId = 78775D8D1053B855;
     com.sap.hcm.ls.shared.config.backend.BackendConfigException: Destination Exception 
    Can not get Destination com.sap.security.core.server.destinations.api.DestinationException: The properties for destination ZZ_LSOCP_JP3 of type RFC could not be located.
    I have checked all of the trace files both on the ABAP and Java sides and cannot determine the root cause. I have repeatedly tried things suggested by other threads in SDN and others (consultants) have tried as well. We cannot determine the root cause of the connection errors and now, cannot get the Publishing to work properly.
    The only system where the connector test works is our sandbox. Our dev and test systems all fail the connector test. We configured them all using the same documentation.
    Is there some way to increase trace levels to try and get more details? And what objects would need to have traces increased?
    Deb.

  • Multiple ESS's in one Portal connected to different backend systems?

    Hi,
    We have two backend systems installed.
    We have one portal.
    We want to create a second copy of the ESS Portal content connected to the the second backend.
    Datawise this is not a problem.
    But what about the JCo's and the Homepage Framework?
    The WebDympro application seems to look for two specific JCo (for example SAP_R3_HumanResources and ...MetaData) and then both copies of ESS want to use this. Is it not possible to have each copy of ESS use it own JCo's and connect to its own backend system for the Homepage Frameworks?
    Thanks,
    Adriaan

    Adriaan,
    Its NOT possible to even talk to different clients in same backend system because you cannot duplicate the JCos and while creating them you need to specify the system and client details.
    Also it uses a system alias which also has to be unique.
    Per my knowledge one portal instance can talk to only backend client and to talk to another backend / client you will need to create a new instance within the Portal.
    This [help|http://help.sap.com/saphelp_nw2004s/helpdata/en/82/76a2406546ba15e10000000a1550b0/frameset.htm] talks sometihng on multiple backend support. I am not much aware about it but see if it helps you.
    Chintan

  • Creating system in portal for the backend SRM

    Dear All,
    We are in the process of setting up a system  in portal for the backend SRM system
    I have tried to create system in System admin--> System configuration --.>System landscape
    For SAP Web AS Connection , the parameters maintained are:
    Hostname : <FQ hostname>:8000  ( 8000 is the HTTP port for ICM)
    Web AS path: /sap/bc/webdynpro
    protocol :8000
    But test is failing as 'An HTTP/S connection to http://xxxxxxxxx::8000/sap/bc/webdynpro was not obtained successfully; this might be due to a closed port on the Firewall:
    test details:
    SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    7. Checks HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (bhidfwao06.ent.bhicorp.com:8000)
    5. The host name bhidfwao06.ent.bhicorp.com was resolved successfully.
    6. The Web AS ping service http://bhidfwao06.ent.bhicorp.com:8000/sap/bc/ping was pinged successfully.
    7. An HTTP/S connection to http://xxxxxxxxx::8000/sap/bc/webdynpro was not obtained successfully; this might be due to a closed port on the Firewall.
    Is there any problem with the port, I doublechecked and the port for HTTP is 8000.
    If I give the Web AS path: /sap/bc/bsp  test is successful.
    Any pointers please?
    Regards,
    Arun

    hi arun,
    u may have to activate some more services in sicf
    u can follow this link what are the neccesary applicaiton need in sicf
    http://help.sap.com/saphelp_nw70/helpdata/EN/46/d28dfa34bb12bee10000000a1553f7/frameset.htm
    let me know u need any further information
    ravindra

  • Language  configuration Portal/ backend system

    hi all
    I have a Iview that launch some backend system  R/3 with SAP GUI
    if i open the R/3 with some language the language of the portal changes too
    this is a problem  i don't like that portal language changes
    have you got any  ideas
    regards

    Hi Ruben,
       Try changing the property "Forced Request Language" for that iview. Let me know whether it works out.
    Regards,
    Siva
    P.S: Award points if you find this useful.

  • Exposing SAP systems directly through Portal

    Hello All,
    If we expose the SAP systems directly through the Portal by creating transaction iviews, Are there any security lapses. I could see a great advantage of users having the internet enabled usage of SAP systems of their organisation.
    Is this a recommended approach for an organization who doesnot any external users to the organisation and have only just internal users.
    Thanks in adavnce.
    Regards,
    Kalyan.

    > Is this a recommended approach for an organization
    > who doesnot any external users to the organisation
    > and have only just internal users.
    Yes, because to create transaction iviews you also need to specify the system object representing the backend sap system which has a property called Logon Method which can be either "User Mapping" or "Logon Tickets".
    In either case you have to map a portal user to the backend user.
    So only if a portal user also has some mapping done by means of Logon ticket/User mapping to the backend system can he/she see the transaction.
    P.S. Do let me know if you need more help.

Maybe you are looking for