Skip to Content

 

As you know PI7.1 new PI version from SAP has arrived. But it has some issue Central SLD, RWB etc..

For Central SLD issue kindly revert it to local SLD till the issue solved from SAP it self.

But here I am going to discuss issue on FQDN in RWB.

After the installation, Postinstalaltion and configuration when I had clicked on Alert configuration and Alert inbox on RWB the below mentioned screen comes with BSP error of FQDN. Hence I want to share my issue of FQDN and process for how to solve the issue in this blog. I have checked the FQDN related with RWB for PI7.1 in SDN and Marketplace but succeed hence I thought It will be helpful if I put my process into blog of SDN.

FQDN – Fully qualified domain name (example in my case abcd3125 is not fully qualified. But http://abcd3125.gbs.com is fully qualified). 

* *

Issue 

<font face=”Arial”>“The URL contains no complete domain specification (hostname instead of hostname.<domain>.<ext>) in alert configuration and alert inbox in RWB on PI7.1</font>

*</p><font face=”Arial” size=”2″><h1 style=”margin: 12pt 0in 6pt”><a name=”_Toc197507857″></a>Steps for Solution<font size=”3″ color=”#225a8d”> </font></h1><p style=”margin: 6pt 0in 0pt” class=”MsoNormal”>To solve the mentioned issue refer the below mentioned steps in j2ee side.</p><ul><li><div class=”MsoNormal” style=”margin: 6pt 0in 0pt”> Enter the URL as (http:// hostname.<domain>.<ext>:port/nwa) on portal side click on configuration <span style=”font-family: Wingdings”>à</span> <span> </span>Infrastructure and click on destination and check for host name and it should with FQDN.</div></li><li><div class=”MsoNormal” style=”margin: 6pt 0in 0pt”> Enter the URL as (http://hostname.<domain>.<ext>:port/nwa) and click on configuration <span style=”font-family: Wingdings”>à</span><span>  </span>Infrastructure and click on Jco RFC provider and check the host name entry and it should be FQDN.</div></li><li><div class=”MsoNormal” style=”margin: 6pt 0in 0pt”> Open browser and enter the URL (http:// hostname.<domain>.<ext>:port) and click on webdynpro <span style=”font-family: Wingdings”>à</span> Content administrator <span style=”font-family: Wingdings”>à</span> Maintain Jco connection (check each and every Jco connection) and check for host name and it must be with FQDN.</div></li><li><div class=”MsoNormal” style=”margin: 6pt 0in 0pt”> The last but not least go to SLD and click on administration <span>à</span> settings and Gateway host (data supplier) and object server and again it should be FQDN. </div></li><li><div class=”MsoNormal” style=”margin: 6pt 0in 0pt”> Enter the URL as (http://hostname.<domain>.<ext>:port/exchangeProfile) and enter the host name with FQDN in all the places of hostname entry.</div></li></ul></font><p style=”margin: 6pt 0in 0pt” class=”MsoNormal”></p><p style=”margin: 6pt 0in 0pt” class=”MsoNormal”></p><p style=”margin: 6pt 0in 0pt” class=”MsoNormal”>*</p>

To report this post you need to login first.

3 Comments

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

  1. Raghavendra Basavaraj
    Hi Rohit,

    Thanks for the useful blog.
    Could you please let us know what was the issue with Central SLD? (We are as of now using local SLD and are planning to configure Central one.)

    Regards,
    Raghu

    (0) 
    1. rohit mehta Post author
      Hi Raghu,

      There is some known issue in PI7.1 for Central SLD hence I have used the local SLD at the time of template installation configuration of j2ee side.
      The basic idea behind using the Local SLD instead of Central SLD is due to issue of SLD – “Incomplete Registration of PI components in SLD”. I have also referred the SAP Notes 1117249. But the issue of SLD, RWB, cache update etc.

      Regards,
      Rohit Mehta

      (0) 

Leave a Reply