Skip to Content
avatar image
Former Member

Address Bar in SDN

Hi,

Everyone using this forum know that SDN is built using SAP EP 6.

When you are accessing SDN, the address bar(of the browser) clearly indicates where you are.

For example, the collobaration area will have a URL

https://www.sdn.sap.com/sdn/collaboration.sdn

the downloads area has the URL

https://www.sdn.sap.com/sdn/downloads.sdn.

My Question is,

In EP6 implementation in my company, the url always remains

http://domain:port/irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default

Why is it like that?

Can anyone tellme how this has been done in SDN? (The change of URL in address bar)

I appreciate your help.

Thanks and Regards,

K. Prasanna

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Mar 31, 2004 at 12:52 PM

    Did anyone notice this?

    Do anyone has answer to this?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 31, 2004 at 05:23 PM

    Yes, it look like it is built on EP6. But if you look closer, you see that it not much left of a "standard" portal installation.

    All of the "crappy" html, js and css from a "standard" portal is gone and replaced with nice looking optimized code. There is a little bit of CM left, but hey, even the forum is replaced!

    I would say that .sdn is just another suffix for standard jsp files deployed on a J2EE Engine.

    I would love to see a case study with details about how SDN is built!

    Regards,

    Mikael

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 01, 2004 at 10:47 AM

    Hello,

    i dont know who you can do this for a SAP-Portal, but on a normal apache Webserver you can use the Apache Module mod_Rewrite and some rewrite rules in the .htaccess to have more pretty URLs.

    Best regards,

    Patrick

    Add comment
    10|10000 characters needed characters exceeded

    • Hi

      Just to clarify how SDN has been built. It is not, in fact, built on EP6, but primarily on EP5. We have built a framework using the standard Netweaver software (J2EE engine) and created a web application ontop of this. All of the documents, and other areas of SDN use the content from EP5, and all of the views of information are also standard iViews. i.e. The search is an iView running on the EP5 portal which searches using Trex over the standard CM components. The framework is simply another alternative for the presentation of the information.

      This has been done for a myriad of reasons, i.e. ability to bookmark pages, quick response times for navigation, etc

      I hope this answers some of your questions

      D