cancel
Showing results for 
Search instead for 
Did you mean: 

BI Installer issue with message" Error: ABAP Backend doesn't exist in SLD

Former Member
0 Kudos

Dear All

Please help me to solve this issue, during the BI Installer the process get errors message

"Error: ABAP Backend doesn't exist in SLD"

Follwoing the oss Note 983156 - BI configuration w. Template Installer

1.Logon to the SLD: http://<host>:<port>/sld. (Your configured SLD (central or local SLD))

Please check in Home -> Technical Systems -> select type ABAP. This

should have configuration of your ABAP (BI) system. yes the system already there.

2, goto http://host:port/index.html ->Web Dynpro ->Content Administrator-> Check SLD Connection

the connection is running well.

Please any one can help me to solve this issue,

Thanks and Best Regards,

Chrisna

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

I found your question because I wanted the answer to it too. I'm trying to connect my Java-only stack portal to my ABAP-only stack BI system using the template in NWA. I get through all the steps up to the creation of the WebDynpro JCO RFC destinations then it fails saying "ABAP Backend doesn't exist in the SLD".

I've checked the SLD and the ABAP backend most definitely DOES exist in the SLD and the SLD is being updated by both the ABAP backend and the Java portal systems thus proving a valid connection exists between the SLD and both systems I'm trying to connect.

I think I've solved it however.

I always define a TCP alias equal to the SID for any SAP system I build and I try to make all connections to <sid>.<fully.qualified.domain.name>. This separates, to a degree, the physical server from the SAP instance.

I used this alias in the BI installation template but I noticed that the ABAP backend was listed as <SID> <hostname> in the SLD (not <SID> <sid alias>). When I used the real hostname in the template it ran to completion.

The other change I made, and it's possible that this was the real reason instead of the alias/hostname issue, was that I restarted the BI system before retrying. I only did this because I was getting error messages saying there were too many active CPIC conversations and I couldn't find them to kill them off.

Hope one or other of these things might help.

Murray