URL Error

[Former Member]

Hi...All,

we are handling eBanking interfaces, sender side is SAP system and receiver side is Webserver, we r planing to do the RFC-SOAP scenario with out having the WSDL file, we want to connect to the banker system through URL...

https://XXXX.XXXXXX.com/XX/XXXX. i am giving that URL in internet explorer it was not opening. it was showing this error...

The website declined to show this webpage

HTTP 403

Most likely causes:

This website requires you to log in.

What you can try:

Go back to the previous page.

More information

This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.

For more information about HTTP errors, see Help.

how can i rectify this error, i asked to our client they were saying that URL is working...

pls suggest me..

Regards,

Pasi.

[Former Member]

Hello ,

You need WSDL file...If client not providing that create it.

check the link

http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm

Configuring Your WSDL File

Applicable to: remote role assignment, remote delta link, WSRP application sharing

This procedure is relevant only for producer portals running NW7.0 SPS7 and earlier. Later versions use an automated service for providing WSDL information to registering consumers over HTTP and HTTPS protocols.

Use

To describe the WSRP services provided by your portal server (the producer) and the set of operations within each service, you need to setup a WSDL file on your portal. When a consumer connects to your portal to retrieve content, the system administrator connects to this WSDL file.

A standard WSDL template file is automatically created for you when you install the portal. You need to configure the settings in the file based on your system landscape.

You can generate multiple WSDL files and configure each one for a specific use case. For example: one for a regular network proxy and another for a reverse proxy; or (ii) one for HTTP connectivity and another for HTTPS. Make sure you supply your content consumers with the URL to the appropriate WSDL file.

In a cluster environment, the WSDL file needs to be configured, as described below, on every server node.

Once a consumer has registered on your portal, the WSDL file is no longer needed by the consumer, unless the consumer needs to reregister after unregistering. You can therefore edit its contents at any time.

If you move the WSDL file to a new location, you need to provide the updated path to consumers that have not yet registered or need to reregister. These consumers need to update the WSDL path in the properties of their existing producer object (see Editing Connection Properties to Producers).

Procedure

...

1. In the producer server, browse to the following folder:

Windows: c:usrsap<SID>JC<x>j2eeclusterserver<node_number>appssap.comirjservlet_jspirj ootportalappscom.sap.portal.ivs.wsrpservicewsdl

UNIX: /usr/sap/<SID>/JC<x>/j2ee/cluster/server<node_number>/apps/sap.com/irj/servlet_jsp/irj/root/portalapps/com.sap.portal.ivs.wsrpservice/wsdl

2. In any text-based editor, open the file: wsdl.html

3. Note that all four services in the WSDL file reference the same servlet. The relevant WSDL information regarding your producer portal is described in this servlet. In most cases, you do not need to modify referenced servlet.

By default, each service references the WSRP servlet at:

For each service, do the following:

a. Specify the Web protocol through which the WSRP servlet is accessible: http or https

b. Replace the default localhost value with the host name of your portal.

c. Replace the default 51000 value with the port number of your portal (the port must match the Web protocol you have defined).

If you are using a reverse proxy, enter instead the protocol, host address, and port of the reverse proxy.

4. Save the WSDL file.

[aashish_sinha]

Hi,

Error: HTTP 403 Forbidden

Description: The server understood the request, but is refusing to fulfill it

Possible Tips:

Path sap/xi/engine not active

HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856

Because of Inactive Services in ICF –Go to SICF transaction and activate the services. Refer SAP Note -517484

Error in RWB/Message Monitoring- because of J2EE roles – Refer SAP Note -796726

Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. –Because of the URL is incorrect or the adapter is not correctly deployed.

So check alll these and do your settings accordingly.

Regards

Aashish Sinha

PS : reward points if helpful

[former_member556603]

Hi,

You just go through this blog..

Http Errors in XI

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Error: HTTP 403 Forbidden

Description: The server understood the request, but is refusing to fulfill it

Possible Tips:

Path sap/xi/engine not active

u2022 HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856

u2022 Because of Inactive Services in ICF u2013Go to SICF transaction and activate the services. Refer SAP Note -517484

u2022 Error in RWB/Message Monitoring- because of J2EE roles u2013 Refer SAP Note -796726

u2022 Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because of the URL is incorrect or the adapter is not correctly deployed.

Edited by: SATYA KUMAR AKKARABOYANA on May 21, 2008 9:38 AM

[vijay_b4]

Hi Pasi,

Apart from these roles you also require write access to the SLD. have assigned that. Please check.

Reward points if this helps

Regards

Vani.