Skip to Content

When talking with customers, one of the primary annoyances they have with the SAP Netweaver suite is the lack of adherence to some basic web standards. These standards have been around since the early days of the web and users are truly accustomed to them.

 

Whenever I am involved with a Netweaver rollout, I make an effort to customize the environment to meet the expectations of the general users. These users are not truly power users but the use SAP enough to understand its … quirks?

 

One of the big annoyances that users have is the unique default web address that the portal utilizes. Typically that URL is something like this:

 

            http://tds-prd.company.internal.adr:50000/irj/portal

 

For the Netweaver team this makes perfect sense.

  • The tsd-prd is the machine name
  • The company.internal.adr is the domain name
  • The 51000 port represents that it has a system number of 01
  • The irj/portal is just something that you have to deal with

 

Fortunately, there are ways around most of these issues. Today I would like to describe to you how to fix the last issue ( irj/portal ).

 

Solution:

 

  • Log into the Visual Admin

 

 

  • Enter an administrator user and password

 

  • After logging on, select the Services branch under the Server node

 

  • Select the HTTP Provider Service

 

 

  • The pane on the right-side of the Visual Admin will update. In the Properties box and under Location enter /irj in the Start Page field

 

 

  • Press the Save Properties button and restart the J2EE server

 

 

 

After you make these changes, users will only need to enter http://tds-prd.company.internal.adr:50000/ to reach the portal.

 For more information vist http://www.netweavercentral.com or email me directly (cgutjahr@spyvee.com)

To report this post you need to login first.

14 Comments

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

  1. Thorsten Franz
    Hi Craig,
    Thanks for this info. I noticed a typo which I’m pointing out to prevent confusion: Port 51000 means system number 10 — if the system number were 01, the port number would be 50100. 5nn00, where nn is the system number.
    Cheers,
    Thorsten
    (0) 
  2. Miklos Palfi
    Hi,

    I think using a SAP WebDispatcher would be a much better solution. That way you could reach your portal on port 80, and you could forward the client from the root to /irj. The WebDispatcher itself comes with the standard installation, it is a very small application without a database.

    Give it a try!

    Regards,
    Miklos

    (0) 
  3. Paul Parnofiello
    Thank you. I didn’t know that when implementing our Portal. Always interesting to learn 1 more out of the 10,000 Portal parameters!

    Our ISA firewall redirects the URL to SAP Web Dispatcher which appends the “irj/portal”.

    icm/HTTP/redirect_0 = PREFIX=/,TO=/irj/portal,HOST=tds-prd.company.internal.adr

    (0) 
  4. Naga Devisetty
    Kool stuff..!
    One of the observation i’d facing the customer is Portal ‘Look n Feel’, for a NetWeaver (technical) Consultants the UI(default framework page) make-sense. But the customer (most of the times, but not all) compares EP with the peer products or with their own portal(s).

    I knew your blog talks more about the URL part, now my question is whether do you’ve a comments or suggestions or links to improve EP look n feel wiht min. efforts.

    Thanks,
    MS

    (0) 
  5. Vinod Patil
    Hello ,

    You can even replace 50100 port by default HTTP port i.e.to 80 / 8080 by changing HTTP port property. So URL again becomes more readable.

    Regards,
    Vinod

    (0) 
  6. Sean Morgan
    Nice! I didn’t know that. It’s a better solution than what I’ve been using.

    BTW, if you redirect requests to the root directory (“/”) to “/irj”, there will still be a second redirect to “/irj/portal”. It’s better to just send them to “/irj/portal” in the first place: that’s especially noticeable in WAN environments with high latency (e.g., users with connection over satellite links).

    (0) 
    1. Thomas Harmon
      When I setup a portal, I don’t want the end users to know the actual host name, location, port numbers and choose http or https.  So, I replace all those parts with user friendly and branded URLs.

      For the example given, you can …

      The tsd-prd is the machine name – Use friendly, branded DNS name that references the Web Dispatcher instead of the CI or app servers.

      The company.internal.adr is the domain name – Use alternate friendly domain, but then setup multi-domain cookies to allow SSO to backends on the data center domain.

      The 51000 port represents that it has a system number of 10
      This should only be used for direct access to the system by the technical team.  Users should access via 80 or 443 to the friendly URL and then get redirected to the backend Portal by the Web Dispatcher.

      The irj/portal is just something that you have to deal with
      Use the custom start page /irj/portal set in the J2EE via VA as shown here, or redirect using the Web Dispatcher.

      I setup my current customer with a URL similar to:
      workplace.company.com

      Entering just “workplace.company.com” in the browser hits the Web Dispatcher on port 80 (http), gets redirected to port 443 (https) and hits the portal backend on 50000 which then appends the /irj/portal to the URL, as mentioned in this blog.

      So, users can use any of the URL’s listed below(and more), but all will end up on https access to the portal and load balanced between 3 servers with direct url’s similar to:
      https://epprd.dc.dal.net:50000/irj/portal

      Friendly, branded URL’s:
      workplace.company.com
      https://workplace.company.com
      http://workplace.company.com
      https://workplace.company.com/irj/portal

      Hope this makes sense and give you some ideas.

      (0) 

Leave a Reply