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

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

User cannot connect to backend system with user J2EE_ADMIN.

I am using Rapid Installer to initiate the second part of the installtion "ERP 6.0 EhP 3 Self-Service Scenarios and Automatic Roles". When I get to the J2EE User section to enter the parameters, the user is defaulted to "Administrator" and I enter my password. I click next and get this message "User cannot connect to backend system with user J2EE_ADMIN." Any ideas?

If this is a double stack installation, you need to enter J2EE_ADMIN as user, NOT administrator.
Markus

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.

Failed to connect to backend system

Hello,
I have installed visual composer and experience some errors.
My system fails to connect to the backend system in VC. I am able to create SAP transaction iviews for the system, see the alias, and user mapping is configured.
When I perform the System Connection test for my system which based on the load balancing template. All the test fail except the ITS test.
- SAP Web AS - SAP Web Application Server
- ITS Connection Tests the connection to an SAP
- Connection Test for Connectors Tests
- Connection Test Through DQE
Must all these test pass, or is it enough with only a subset of these tests. Does the alias have to be the same as the logical system.

Hi Jørgen,
It is a genuin problem. Just tell your Portal Administrator to give the userid (which you are using to log in to the portal from VC) the full authority for the alias you want to access from VC, as it is the portal administrator who has the rights to give access to various portal users. In the portal, the administrator can give a user the access to an alias by selecting that alias and change the required property.
Try the following flow to get the required document:-
help.sap.com->SAP Netweaver->SAP Netweaver 2004->people integration->portal->Administration Guide->System Administration->Permission,Role/User........
Check out the given help document, I hope it will help you in solving your problem.
Check out the section 3.2 (specially steps 25-30) in the pdf file provided in the following link :-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6209b52e-0401-0010-6a9f-d40ec3a09424
Thanks in advance,
Deep.

MSS Component not connected with Backend system

Hello All,
In our NW Portal 7.01 system, we have got old Business package of MSS 60.1 & when we are trying to connect to our backend system R/3 4.7, we are able to connect it.
Now we have upgraded portal to EHP1 and then we are trying to do the same, then we are not able to connect to MSS business package, as we are getting TP Host missing error and connection not able to do with R/3 system
Has anyone come across such scenario? please update us asap.

Just 1 correction, we are able to work successfully with NW 7.0, but not after upgrade to EHP1.
So need to know, whether anyone is able to work with NW 7.01?

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

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

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.

Connecting to backend system with parameters

Hi,
i am able to get connected to bakend system with sytem number, portno, sid, host or ip... and can get transcation ivews with that...
ex: i am able to see perticular SAP R3 Transactional iview with these parameters
Then what is the purpose of creating RFC destinations, go.bat configuration, certificate creation and all those things.....
Thanks
Kumar.

Hi Kumar,
This things are needed when you want to access any service from R3 to Portal or vice versa. Like <b>Adobe Document Service (ADS)...</b>It should be installed in Portal server..and if you want to use ADS for displaying/printing R3 form in pdf format then you need to access ADS from Portal. For this type of case you need only the creation of RFC destination, go.bat configuration for HTTP destination, certificate..etc..
Thanks,
Sekhar

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

Webdynpro application - connecting to backend system

Hi,
Iam developing an application in webdynpro.Iam able to generate the application in Frontend by using BAPI_BANK_GETLIST but its not taking the data from the backend system.
Is it necssary to create the application in backend.
Will any one please help me to sort out this.
Thanks & Regards
Sushma

Hi
To get the data from your BAPI you need to follow steps
1. create a Model.
2. open your data modele and add it.
3. Map with your Controller and the View.
4. Apply a table on your ivew
4. Excute your BAPI.
PS: IF data is still not pulling up from back end then you need to test BAPI on your backend ..it working fine or not
Thanks

Can't connect to a SAP backend system via portal/web dynpro/JCo destination

Scenario:
     Can't successfully set the JCo destination.. Always got a Java exception..
Solution:
     Use the router string "/H/sapserv3/S/3296/H/", instead of
"/H/sapserv3.wdf.sap.corp/S/3296/H/".
     This looks like a bug in portal NW2004s SP9.

Sorry for the delay, but I was not able to get access to this system until this afternoon. I ran the ARP command you suggested on the server, and it did return the correct IP and MAC address values for the problem workstation.
I then ran IPCONFIG/displaydns on the server. There was a record there for the problem workstation. The "record name" matched the machine name correctly. However, the "A <Host> Record" value was for the wrong IP address (192.168.1.4
rather than the actual workstation IP of 192.168.1.7). This could certainly explain why I am not able to RWA/RDP to the machine by name, although I can make an internal RDP connection via IP address.
Could you please tell me what I need to do to repair this problem? Should I run IPCONFIG/flushdns on the server?
Thanks again for your assistance.
John

No system available - When connecting to backend system

In the VC we have created our models, we then select data, then click on the portal connect button, the logon page is then displayed from which we log-on, the logon page disappears and the VC 'Data' page is displayed, the 'Connect to System' field display's a message 'NO SYSTEMS AVAILABLE'.
We have checked and tested the Portal settings which are all connect the R3.
The VC has previously been working and we have implemented a live application last year, however, we have recently re-built our server and ever since the VC has been displaying the above error message.
We are on EP6 SP2, and the VC version 6
Can anyone please help...

hi
since you said you rebuilt the server and all. you might want to check the user mappings for the systems you have in the portal.
plus try redeploying the portaladdons for the visual composer.
hope that helps.

JCO Connection to Backend System - CC 5.1

Hi All,
I have installed Virsa CC 5.1 on my server which is Netweaver 2004s system. Now i want to connect one of my servers which is a SAP 4.7 EE. For this i downloaded the RTA for 620. Now when i create the JCO from Webdynpro/COntent Administrator/maintain JCO Detination I'm getting the error below. We are trying to use the message server of the SAP 4.7 EE system and J2ee cluster of the 2004s system.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=mnr3472trg GROUP=PUBLIC R3NAME=CER MSSERV=sapmsCER PCS=1 ERROR hostname 'mnr3472trg' unknown TIME Thu Aug 23 11:13:45 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -2 MODULE ninti.c LINE 361 DETAIL NiPGetHostByName2: hostname 'mnr3472trg' not found SYSTEM CALL gethostbyname_r ERRNO 11004 ERRNO TEXT WSANO_DATA: Valid name, no data record of requested type COUNTER 1
Can any one please help me out?
Regards,
Vishal

Hi Vishal -
I'd double check that a) your SLD is running b) check with whomever is maintaining the SLD that it contains correct entry for message server to your target system - and that there aren't any cross - domain issues with this connection.
cheers
Paul

Failure to connect to backend system in Portal

Similar Messages

Maybe you are looking for