Web Server Postinstallation Steps 

Prerequisites

For the prerequisites, see section Best Practice.

Activities

As of SAPConsole release 7.10, it is no longer recommended to use SAPConsole with SAP J2EE Server. You should instead make use of the IIS web server which is part of the Windows 2003 server operating system.

Configuring IIS6

Proceed as follows to configure the IIS6 for the use with SAP Console.

...

       1.      From the Start menu, choose Settings  →  Control Panel  →  Administrative Tools  →  Services.

       2.      Check that the IIS Admin Service and WWW Publishing Service are started.

       3.      From the Start menu, choose Settings  →  Control Panel  →  Administrative Tools  →  Internet Information Services (IIS) Manager.

The Information Services (IIS) Manager window opens.

       4.      Expand the tree in the left frame.

       5.      Select the node Web Site.

       6.      Right-click Default Web Site in the right frame.

       7.      Choose New  →  Virtual Directory.

       8.      Name the virtual directory, for example SAP.

       9.      Set up the Web Site Content Directory, for example C:\Program Files\SAP\Console.

   10.      Assign Execute access permission to the virtual directory.

   11.      Choose Finish.

   12.      Select the node Web Service Extensions.

   13.      Right-click in the right frame.

   14.      Choose Add a new Web service extension.

   15.      Name the extension, for example WebSAPConsole.

   16.      At Required files, choose the Add button.

   17.      Browse to isapi_sapcnsl.dll, for example to C:\Program Files\SAP\Console\isapi_sapcnsl.dll.

   18.      Mark Set extension status to allowed.

   19.      Choose OK and close the Internet Information Services window.

   20.      Start the WebSAPConsole via the URL http://<host>/sap/isapi_sapcnsl.dll.

Troubleshooting in IIS6

Proceed as follows to troubleshoot in IIS6:

●      Check the <host> and <port> settings of the web site and use http://<host>:<port>/sap/isapi_sapcnsl.dll.

●      Check the authentication and access control for this virtual directory.

●      Check the application pool for this virtual directory.

●      Check the identity control of the application pool

●      Check the recycling scheme of the application pool.

In general most problems appear in user credentials and access control. This means that an isapi.dll cannot be executed, a trace file cannot be written, a configuration file cannot be read etc. all due to inappropriate credentials.