cancel
Showing results for 
Search instead for 
Did you mean: 

System Landscape Directory: HTTP response code: 403 (Forbidden)

Former Member
0 Kudos

Hi,

After upgrading PI 7.1 (with local SLD) Stack06 -> Stack09 we have the following error in the runtime workbench. It seems that the connection

between PI and SLD is not working:

1) error in RWB -

Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)

2) another error:

8 Message(s) : SLD agent unable to specify domain - Error class com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden) - Attempt to create JCo connection object failed for domain domain.00.hfasapxi1 - Integration Server unable to specify a JCo client - No component names available from Integration Server - SLD agent unable to specify domain - Error class com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden) - Attempt to create JCo connection object failed for domain domain.00.hfasapxi1

3) in the sld:

INFO com.sap.sld.api.builder.app.DefineHostedSystem: Communication exception in SLD ping (HTTP 403 = FORBIDDEN): http://hfasapxi1:50000/sld/cimom, namespace sld/active.

sldcheck is working and the users are not locked or not valid. All seems to be ok but I still get these errors.

Any idea ?

Dimitry Haritonov

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

there is a progress on this issue, it seems that the adpter framework fails to register itself in the SLD with the following errors in the default trace:

Unable to instantiate com.sap.aii.adapter.axis.ra.AdapterManager

The AdatperEngine has not been registered with the SLD due to: com.sap.aii.af.lib.sld.SLDException: Could not register AdapterFramework to SLD. Reason: Self-registration of instance af.xid.hfasapxi1 of class SAP_XIAdapterFramework failed

Since the AdatperEngine has not been registered with the SLD, no adapter services can be registered.

any idea ?

Former Member
0 Kudos

hi,

This is problem with PI-> Business sytems has issues in SLD.

Just check Buiness system (created for PI) that has properly technical system and properly all the parameters.

Role of business system correct URL and host in Business system level. and do the complete Cache refresh once you check the parameters.

please check the below link..

/people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory

Regards,

Venu.

Former Member
0 Kudos

Hi Venu,

thanks for the answer but it seems to be something else. After searching for that problem I also ran the configuration wizard->PI self registration. This activity registers all the component of the PI, unfortunately it only registered the "integration server" part without the Adapter engine, domain, RWB and etc.

Also, when I trigger the registration of the adapter engine I get the following error in the default trace:

The AdatperEngine has not been registered with the SLD due to: com.sap.aii.af.lib.sld.SLDException: Could not register AdapterFramework to SLD. Reason: Self-registration of instance af.xid.hfasapxi1 of class SAP_XIAdapterFramework failed

the reason is unknown ... any idea ?

Dimitry Haritonov

Former Member
0 Kudos

Hello Dimitry,

When I was trying to add PI system to central SLD by running Initial Configuration, it was not working.

So, I ran Initial Configuration added it to local SLD.

Then all components (Integaration Server, Adapter Engine, RWB and so on) will be registered. You can see this in Techincal systems and Business System in Local SLD.

Then, you need to add your PI System to Central SLD.

NOTE :- PI* users password should be same in all landscape ( DEV, QA and PRD).

Then, you will be able to by pass HTTP response code : 403 (Forbidden).

Regards,

Ananda

Former Member
0 Kudos

Dear Ananda,

I'm not using central SLD. The registration to the local SLD is not working as I stated before, It can't register the adapter engine and all the adapters.

the errors above are from the default trace ...