|
|
SAP Internet Transaction Server 4.6BRelease Notes (4620.0.0.306)IntroductionThis document contains last minute information about the Internet Transaction Server that could not be included in the official ITS documentation.PrintingChoose the "Print" command from the "File" menu to print this file.Further informationAdditional information can be found at http://www.saplabs.com/devarea/its.htm.The latest updates and beta version downloads of current and upcoming ITS releases are available on http://www.saplabs.com/devarea/itssoft.htm. Content1. WebGUI 2. Installation Notes 3. New Features 4. Fixed Problems/Bugs 5. Known Problems/Bugs 6. FAQ - Frequently Asked Questions
1. WebGUIDisclaimerThis setup contains an early WebGUI package. At this time, WebGUI is not a released product. Comments are always welcome, but please don't expect a speedy response from us since we are still finishing up the product. If you have any comments, please send them to the CSS queue BC-FES-ITS and give the message a short text starting with "WebGUI" and the release number of this ITS version. Example: WebGUI 4620.0.0.300: Problems with Dynpro layout ... 2. Installation Notes
ITS supports two ways of defining a connection to the R/3 System:
You may choose the option which best suited for your needs in the ITS setup program. For test and development systems we recommend that you select a specific application server. To get more detailed information about how to set this up, see the FAQ section below.
The setup program asks for an R/3 user account. This user account is placed in the global.srvc file and will be used as the default for all Internet applications (or services). For security reasons it is strongly recommended that you set up an individual user account for each service after the initial installation has completed in order to limit the user rights on a per application basis. The application specific account should be placed in the application's service file (*.srvc) with the SAP@Web studio. It overrides the global setting.
The Internet Transaction Server is supported on Windows NT Server 4.0. The SAP@Web Studio is supported on Windows NT 4.0 Server and Workstation. The supported Web servers are Microsoft Internet Information Server 4.0 (3.0 can still be used), and Netscape Enterprise Server 3.5 (2.0/3.0 can still be used). The NT Service Pack 3 must be applied to the Windows NT server. Make sure that you reboot your Windows NT host after the ITS installation.
If you choose to install the HTML sample files during the ITS setup, the setup procedure will copy new versions of the files default.htm and index.html to your server's document directory. The existing files are renamed to default.bak and index.bak. 3. New FeaturesNew in ITS 2.2
ITS now features a new HTML based administration tool that allows to configure, control and monitor ITS instances. For example:
The ITS Administration Tool is installed using the standard ITS setup program. The setup program will prompt whether a standard ITS installation is being performed or an installation of the ITS Administration Tool. The file security of the Administration Tool instance should be set to be the same as that of other ITS instances.
Internet and Intranet users may change their passwords interactively at the login time via a Web browser. This new feature has significantly changed login.html in the system template directory.
Give the radio button group the name of a field that is not on the SAPGUI screen and use the Dynpro field as the value of the radio button, for example <INPUT TYPE="RADIO" NAME="GROUP1" VALUE="OPTFIELD1"> <INPUT TYPE="RADIO" NAME="GROUP1" VALUE="OPTFIELD2"> Example: <INPUT TYPE="CHECKBOX" NAME="CHECKFIELD1"> <INPUT TYPE="CHECKBOX" NAME="CHECKFIELD2"> Popup-windows in SAPGUI are now supported. The default behaviour up to ITS 2.1 was to always suppress popups. Now you can set the switch ~popups to 1 and ITS 2.2 will not suppress popups any more and will genereate a HTML template for the popup. Please note, that synchronisation will be very difficult to implement so we suggest that you also set ~syncBehaviour to NoResync. You can use the variable ~windowtitle to use the SAPGUI window title in HTML business.
When using Netscape browsers, ITS dynamically determined to which frame an HTML template had to be sent by determining which R/3 subscreen had changed. If more than one subscreen had changed, the whole browser was refreshed with a _parent target. Since a proprietory Netscape feature Window-target in the HTTP header was used that the W3C did not standardize, Microsoft consequently did not supported this feature in their Internet Explorer product. Therefore, ITS no longer supports this feature. As a consequence, application developers now always have to specify a target using the ~target attribute in wgateUrl(). As ITS is no longer supporting dynamic target determination, the option ~forcetarget is no longer applicable. ~exitURL can now be set dynamically by the application either in the service file or using the field-set macro in ABAP. When using wgateUrl() the parameter ~secure can be set to "on" and "off" to determine if http or https should be used. Please note, that ~hostsecure must be set to a fully qualified domain name (e.g. www.acme.com) when the service was started with a fully qualified URL (e.g. http://www.acme.com/scripts/ww20/!). Consequently, ~hostsecure must be set to a non-fully qualified domain name (e.g. itshost) when the service was started with a non-fully qualified domain name (e.g. http://itshost/scripts/ww20/!). This is because at service startup a Cookie ~Session is set and for security a host may only be allowed to set Cookies for hosts in its own domain. Since hosts with non-fully qualified domain names and hosts with fully qualified domain names are not considered to be in the same domain, a ~Session cookie can not be set at service startup, that is then also recognized if the the domain name changes from non-fully qualified to fully qualified. This problem does not exists, if Cookies are not used by setting the variable ~Cookies to 0 in the service file. Functions to compare and output strings are now supported. Check the online documentation. Function is available to include files at runtime. Check the online documentation. All NLS related configuration data has been moved to the NT registry. You can use the ITS Administation Tool to edit these settings. Additionally, a mapping from 2 to 1 character language names is provided. For example, you can specify ~language to be En. If you connect to a 3.X R/3 system ITS will map this language and will connect with E to the SAP system. This way, ITS now uses 2-character language names in login.html. Please note, that ITS will only accept double character language identifiers if you connect to an R/3 release greater or equal than 4.0A.
Wgate is now available on UNIX and AS/400. Check the online documentation how to install the wgates since the NT ITS setup program does not support installation of UNIX wgates. New in ITS 2.1
ITS 2.1 now fully supports IIS 4.0. You can use the IIS 4.0 virtual site concept to run several independent virtual ITS instances on a single machine. For setting up several virtual IIS 4.0 sites, please consult the FAQ section in this document.
ITS 2.1 now fully supports Netscape Enterprise Server 3.5. New in ITS 2.0
The WebTransaction programming model has been further improved to simplify and speed up development of internet applications.
ITS 2.0 now allows to install several independant instances on a single machine. Each virtual ITS instance has its own set of service, template and resource files as well as separate configuration settings. To make use of this new feature you need to install one web server for each virtual ITS server (e.g. use Netscape's Enterprise Server which allows to configure multiple "virtual" web servers on a single machine). To support you in setting up and removing virtual ITS instances on your machine, a set of command-line utilities has been provided. The ITS setup procedure and the command-line utilities now provide support for three security models for the ITS: full access for everyone, full access for an ITS administrator account and restricted access for an ITS users group, and full access for the ITS administrator account only. To protect the communication link between the WGate and the AGate component (e.g. in a dual-host configuration) products like the SECUDE(C) security environment of the SECUDE GmbH are now supported via SAP's secure network communication (SNC) layer. Furthermore the SAProuter product can be used as a firewall to restrict access to the AGate host to the WGate component.
To enhance usability of intranet applications ITS 2.0 now comes with improved user management that allows you to log in once and then use several independent internet applications without repeated login. Please note, that user management only is supported, if Cookies are switched on in ITS (i.e. ~Cookies set to 1) and if the browser accepts Cookies. Support for Microsoft Internet Explorer 4.0 and Netscape Communicator 4.0 has been added.
Multiple languages for HTML templates can now be used in combination with an R/3 system that is configured to support a single login language only (see below). The default HTML system templates send by the ITS can now be overriden by individually customized versions. Simply create a copy in the PM theme of the system template folder or into the service specific template folder; you can then modify this template and e.g. change it to fit your corporate web site design. ITS 2.0 allows you to switch off the use of HTTP cookies to store information that needs to be persistent for the lifetime of a session. This allows you to run sessions within browsers that do not accept HTTP cookies.
4. Fixed Problems/BugsFixed in ITS 2.2
When ITS was installed on a backup domain controller ITS 2.2 installation failed with a message Failed to add the 'logon as a service" right for the NT account [account] where [account] is the name of the ITS administrator that was specified in the ITS setup program. This problem is now fixed. When installing ITS on a German NT and applying the security properties under "everyone", ITS failed to do so because the German NT does not recognize "everyone" (German NT's equivalent "jeder") as a valid name. The problem is now fixed. ITS will not process completely the data present on SAPGUI screens if their compressed data volume (DIAG data) is more that 30KB. This problem is not fixed when using a R/3 system of release 4.0B or higher. If an R/3 system of release 4.0A or smaller is used the application needs to transfer mass data using the field-set macro. Please read the online documentation about how to use this macro. When installing ITS on a different drive (other than the "C:" drive), with the directory name containing a space, you used to get an "access denied" error message with error code #5. This problem is now fixed. Fixed in ITS 2.1
When returning responses containing more than 30 KBytes data via Microsoft IIS 3.0, the connection between the web browser and the web server was closed too early if instead of HTTP the HTTPS protocol was used. If this occured, usually no data was displayed in the browser at all. This problem is known to be Microsoft IIS 3.0 problem and has been fixed by Microsoft in IIS 4.0. To allow you to still use IIS 3.0 with the ITS, ITS 2.01 contains a workaround for this problem.
The CGI version of the web server extension of ITS 2.0 (WGate) added a newline character after the HTTP header. Even though this additional character did not harm responses that were plain HTML pages, binary data (e.g. file downloads) was rendered invalid. This bug has been fixed with ITS 2.1. When trying to connect from the WGate component to the AGate component via SAPRouter, the WGate returned an error message ("Connect failed") if SNC was not enabled. A work-around to this problem was setting the registry key : hkey_local_machine/software/sap/its/2.0/<virtualITS>/ connects/type to 1 (meaning: do not use SNC) instead of 2 (default setting, meaning: use SNC). This problem has been fixed with ITS 2.01.
The ITS setup program now creates scripts that allow you to uninstall a virtual ITS instance independent of other instances. Previous versions allowed you to only deinstall the whole ITS, not just a single instance. To uninstall a virtual ITS, go to the Windows NT taskbar and select Start/Settings/Control Panel. In the Control Panel window, double-click on the "Add/Remove Programs" control. Select the virtual ITS you want to remove (item "ITS Manager 2.0 - virtualITS") and confirm your selection if you are sure about the deinstallation. Fixed in ITS 2.0
A bug in ITS 1.1 resulted in the AGate.exe process crashing sometimes with an NT protection fault. This error occured if a large HTML page was to be sent to the browser and after beginning to send a runtime error occured (e.g. context overflow). This problem is resolved with ITS 2.0. When copying a large number of files to the ITS' services directory, the cache update procedure failed to update the cached service descriptions completely.
When using an HTTP-proxy access to a previously started session was sometimes denied by the ITS due to a change in the requesting IP address. This problem has been solved by checking the IP adress after filtering with the subnet mask defined in the NT registry (hkey_local_machine/software/sap/its/2.0/<virtualITS>/ programs/agate/ipchecking). Previous beta releases of ITS 2.0 experienced problems in multi-boot NT environments. These problems have been solved with this version. When using the type "image" with an HTML input tag, ITS supported only the syntax (e.g.)
Previous beta releases of ITS 2.0 experienced problems when using language-dependent template files instead of resource files to store multi-byte characters. This issue has been resolved with this version. ITS 1.10 sometimes crashed if a resource file exceeded the maximum size configured for HTML resources. This has been corrected. Fixed in ITS 1.1
Random "R/3 connection lost" ITS administrative messages that were not due to a timeout expiration will no longer occur. Fixed in ITS 1.0
It is no longer necessary to restart the ITS if you are changing the code page settings in a service file (e.g. ~codepage_j) at runtime. 5. Known Problems
Under certain circumstances WW20 can get into an infinite loop communicating with an R/3 4.0A application server . If this happens, please stop and restart the ITS from the Windows NT Service Control Manager. Upgrade to R/3 4.0B as soon as possible. Throughout a Web session, the ITS keeps the IP address of the host running the Web browser. If you want to use the ITS debugger (SAPgui) to debug a Web transaction, the SAPgui must be running on the same host (IP address) as the Web browser. Otherwise, a "connection reset by peer" error message is displayed. The ITS identifies the Web transaction to be debugged by matching IP addresses. To enable the ITS to obtain the IP address of the origin host you need to ensure that neither the SAPGUI nor the Web browser are running over a firewall (saprouter, proxy server). When using the CGI version of the WGate on Windows NT, you have to use a slightly different URL to start a specific service; whereas with the Microsoft IIS and the Netscape Enterprise Server versions you could use http://<www.myhost.com>/scripts/wgate/<service>/! you have to type the following with the CGI WGate: http://<www.myhost.com>/scripts/wgate.exe/ <service>/! The current setup does not automatically take this difference into account. If you want to use the default homepages installed with the setup to start the SAP delivered IACs, you have to rename the directory webServerDocumentRoot/sap/its/homepages.cgint to webServerDocumentRoot/sap/its/homepages. 6. FAQ - Frequently Asked Questions
The ITS 2.0 supports R/3 release 4.0a and is fully backward compatible with all 3.x releases starting 3.0d. A service is the process by which an Internet Application Component (IAC) is called. A service is defined in a service description file (*.srvc). The service description file lists all parameters that the ITS needs in order to run the Internet application component (i.e. R/3 transaction, R/3 connection parameters, etc.) ITS 2.0 supports two methods of connecting to an R/3 system:
The following information needs to be provided in either the file global.srvc or in the service specific .srvc-file: The following information needs to be provided in either the file global.srvc or in the service specific .srvc-file: Whenever a specific R/3 application server is specified this setting overrides the existance of a message server definition! This means that if there is a ~appServer entry present in the file global.srvc and you specify a message server (~messageServer) in a service specific .srvc-file, the application server definition in the global.srvc file will be used instead of your message server definition! You have to set ~appServer and ~systemNumber to blank in the service specific .srvc file if you want to let your ~messageServer setting take presedence over the application server definition in the file global.srvc. a) Mapping HTML checkboxes to R/3 screens b) Behavior of HTML checkboxes in your HTML templates, please be aware that only those variables will be returned to the Web server whose checkmarks have been set. In the above example - assuming that the user has not changed the default settings - the Web server would only receive "XYZ=X" but not ABC="" c) Deselection of checkboxes on the Web As a result of the behavior described in section b) above, the deselection of checkboxes can cause problems in the R/3 System because input fields of length 1 are not reset. Therefore you should always combine an HTML "input type=checkbox" tag with an HTML "input type=hidden" tag as shown below: <input type=checkbox name="XYZ" value="x"> <input type=checkbox name="ABC" value=""> When developing Web transactions you can use several debugging tools. To use these tools, set the Windows NT registry key HKEY_LOCAL_MACHINE/Software/SAP/ITS/2.0/virtualITS/ Programs/AGate/AdminEnabled" to 1 and restart the ITS. You can then use The URL fielddump command http://<www.myhost.com>/scripts/wgate/<service>/ ?~command=fielddump This command lists all parameters received by the ITS including those currently displayed on the R/3 screen for this session. By specifying the field ~templateLanguage either within the URL or in a .srvc-file a language can be defined that will be used to generate the HTML pages; this language is independent of the login language, i.e. even if you are loging in in English to the R/3 system you can still use e.g. Japanese HTML templates. To do this simply place the following line into the file global.srvc or service specific .srvc-file: or include into the service start URL: http://<www.myhost.com>/scripts/wgate/<service>/! ?~templateLanguage=<yourLanguage> The ITS setup program offers you a list of all currently available IIS 4.0 web sites on your computer. It also configures the one you selected to automatically run the ITS web server extension (WGate) when the setup finishes. The only change you might have to apply manually, is to enable the ITS web server extension to run in a separate process/memory space. By default all ISAPI extensions loaded into IIS 4.0 share a single process. This causes problems with the WGate extension. You therefore have to separate multiple WGate extensions into several independent processes. To do so, please proceed as follows: © 1996-1998, SAP AG
| |||||||||
|
