Skip to Content
When accessing a SAP Enterprise Portal in a clustered environment, you enter through a common cluster address. After this you are transparently redirected to one of the cluster nodes. In order to properly debug problems with the application, it is often essential to be able to do the following actions:

  1. Identify which cluster node is being accessed by a client
  2. Be able to access a particular cluster node

There are many things which can cause problems that are only apparent on one cluster node, such as OS problems (full disk, hardware trouble, etc.) and application problems (synchronization problems).

1. HowTo: Identify which cluster node is being accessed by a client

The easiest way to identify which cluster node a client is accessing is to use the web-browser’s built-in cookie handling.

By typing javascript:document.cookie in the address field in the window where the portal is accessed, you can see the cookies of the page(except http-only cookies like MYSAPSSO2 if you are using IE6). You will get output similar to the image below.


You can now find the name of the server by looking at the first few characters of the JSESSIONID cookie. In the example above the name is portal1.
This might help you to get a bit closer to the problem, but to uniquely identify the cluster node being accessed you need the cluster ID. You can find the number by looking the numbers after the ID characters in the JSESSIONID or looking using the value of sapj2ee_* cookie. Here the value is 354385894

For more details on the JSESSIONID cookie see this document on .

2. HowTo: Be able to access a particular cluster node

In order to access a particular cluster node, there are three things which must be done:

  1. Delete all cookies
  2. Access the server directly and not through the cluster address
  3. Add the sapj2ee_* parameter to the request, not as a standard HTTP get parameter, but separated with a ; from the URL.If you have any HTTP get parameters, add them after the clusterId (include the ? before the values)

a.)To delete all the cookies use the Internet Options->Delete Cookies.. functionality

b.)If you only have the cluster address of the portal, add a DNS alias (or just put it in your local host file) for each portal server and use this in the url

c.)Use an URL of the following syntax;sapj2ee_*=354385901
If you don’t have the cluster ID, you can among others find it in the config tool.

You can use this information to create a simple dynamic page which provides links to all the cluster nodes as well as functionality for deleting the cookies. But that is left as an exercise to the reader ๐Ÿ™‚

Thanks to Sigi for information on how to do the second part of this weblog.

To report this post you need to login first.


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

    1. Former Member Post author
      The important thing to remember is to delete the cookies for each attempt (it is best to close the browser).

      External loadbalancer also might stop this from working.

  1. Former Member

    at least in 6.20 PL24 this only works when using<br/>; instead of ? <br/><br/>Instead of writing …portallauncher.default?sapj2ee_=<cluster_ID>                                                              <br/>write it like this …portallauncher.default;sapj2ee_=


Leave a Reply