Skip to Content

Alternative WSDL connection test for FPN

<p dir=”ltr”>Sometimes when setting up a federated portal network the producer registration fails because the consumer is not able to access the producer WSDL file but when you type the WSDL generator URL on the web browser you are able to fetch the file.</p><p dir=”ltr”> </p><p dir=”ltr”>In order to check if the consumer portal is able to access the WSDL file from the producer there is another simple test that can be performed. See the steps bellow:</p><p dir=”ltr”> </p><p dir=”ltr”>1) Build the WSDL file URL;</p><p dir=”ltr”>    1.1) As a portal administrator, go to: System Administration -> Federated Portal; </p><p dir=”ltr”>    1.2) On detailed navigation expand Myself as Content Consumer -> Manage My Producer;</p><p dir=”ltr”>    1.3) Browse the folder NetWeaver Content Producer for the desired Producer system object and open it;</p><p dir=”ltr”>    1.4) You will be able to see all the necessary data to build de following URL: <protocol>://<Host Name>:<port> <Path to WSDL Definition File></p><p dir=”ltr”>    It will look like this: http://</p><p dir=”ltr”> </p><p dir=”ltr”>2) Create an URL iView using the WSDL file URL; </p><p dir=”ltr”>*    ATTENTION*, in order to test the connection between portals the iView property “Fetch Mode” must be set to “server side”.</p><p dir=”ltr”> </p><p dir=”ltr”>3) Run the iView; </p><p dir=”ltr”>if you can see the WSDL file contents than the consumer portal is able to access the WSDL file. </p><p dir=”ltr”> </p><p dir=”ltr”>If the WSDL file is not displayed then probably there is a connection problem between the portals. If another error is seen, then It needs to be investigated further.</p><p dir=”ltr”> </p><h5 dir=”ltr”>What to do if I could not get the WSDL file?</h5><p dir=”ltr”>Bellow you will see some troubleshooting steps that can be followed.</p><p dir=”ltr”> </p><p dir=”ltr”>The first thing that should be checked is the defaultTrace file, the chances are that an exception is logged telling us what happened when the consumer tried to connect to the producer portal. Pay attention to the time you performed the test and look for defaultTrace entries near it (Remember that the time on defaultTrace file is logged in milliseconds and is does take into account your time zone).</p><p dir=”ltr”> </p><p dir=”ltr”>One example of exception that you might find is the following:</p><p dir=”ltr”>(…)</p><p dir=”ltr”>Caused by: Server returned HTTP response code: 401 for URL: http://<Portal_Host>/irj/servlet/prt/portal/prtroot/</p><p dir=”ltr”>(…)</p><p dir=”ltr”> </p><p dir=”ltr”>In this case the user was facing a know issue that occurs with FPN and SPNEGO. In order to register the producer portal the user had to disable to SANEGO before registering the producer portal and enable it when the registration was completed.</p><p dir=”ltr”> </p><p dir=”ltr”>Another example of exception that could cause this behavior is an SSLException (most common when using https between the portals) that could be caused by a problem in SAPCryptoLib and that can be solved by updating it (the SAPCryptoLib).</p><p dir=”ltr”> </p><p dir=”ltr”>The next tests that can be made are to check the network environment in which the portals are place and try to identify which component is the responsible. For example, the connection could be being blocked by a miss configured web-dispatcher, load balancer or missing or faulty proxy configuration of the http service in the portal. In this situation try to remove the points of failure in order to identify which component is responsible.</p>

You must be Logged on to comment or reply to a post.