cancel
Showing results for 
Search instead for 
Did you mean: 

ICM custom error pages per SICF service?

Former Member
0 Kudos

Dear Sirs,

Is it possible to control the error pages

on a per service basis

in SICF ?

- the ICM connection timeout (controlled by the proctimeout)

- 400 Session timeout controlled by the rdisp/plugin_auto_logout)

I am aware of the parameter; cm/HTTP/error_templ_path. (mentioned in e.g thread However this works as I can see globally for all services.

The reason I need this is because different ITS services are targeted on different end user, and thus also a need to have different types/level of messages.

There is a tab in SICF for each service called Error pages, where it is possible to create different error pages. “Logon errors”, “Appl errors”, “Logoff page”, “Not accessible”. According to the documentation this allows to create an error page in the error page for 401 and 500 errors, however the session timeout error is a 400 error. Will these help me?

Any solutions to my problem.

Best regards,

Jørgen Ruud

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hey, as I had the same problem here comes my solution. I also had the requirement to show a neat page when an timeout appears but for the other dumps, the standard error page should appear.

How I did it:


  • go to transaction SICF
  • navigate to the service you want to have this custom error page
  • go to the "Error Pages"-tab and select below the "Application Error"-tab.
  • create a "Explicit Response Page Body"

There are certain tokens which can be found in the documentation, that will be parsed during run time.

A token you need for the timeout page is the <%=SYMSGNO%> token. "060" stands for the timeout.

Now back to the explicit response page body. As ABAP cleans out all the Javascript out of the page,

we need a little workaround here to make it happen.

  • First thing we need is a div, that is invisible and contains the parsed token for the

message number we want to use later to build our page

  • Second thing is we need an img-tag, which loads and image that can't be found and triggers

the "onerror"-event, where we can place our javascript so that it won't

get "cut" out by the ABAP environment

By doing that we achieve that the script gets executed without any user interaction

Body-tag will get cut out as well, so no "onload" is possible.

Keep in mind to use ' instead of "

  • Now you are able to get detailed information about the dump and you can

build you own custom page using Javascript

Here's a little snippet how I did it in our application:

<div id="symsgno" style="display:none">

        <%=SYMSGNO%>

</div>

<img style="display:none" src="i_dont_exist.png" onerror="

var symsgno = document.getElementById('symsgno').innerHTML;

if(symsgno == '060') {

  //build up custom timeout page

} else {

  //build up standard error page

}

">

If someone found a cleaner solution please let me know!

erik_hendrix
Explorer
0 Kudos

Jørgen, have you ever found a solution to this? Looking for the same item. 🙂

Appreciate it!

Former Member
0 Kudos

Have you tried implementing a custom ICF handler?