WebTransactions V7.1. Supplement

Transcription

1 WebTransactions V7.1 Supplement Edition: December 2006 This manual describes the new functions in WebTransactions V7.1. It is intended to supplement the WebTransactions V7.0 manuals.

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs. Fax forms for sending us your comments are included at the back of the manual. There you will also find the addresses of the relevant User Documentation Department. Certified documentation according to DIN EN ISO 9001:2000 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2000. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and Trademarks Copyright Fujitsu Siemens Computers GmbH Alle Rechte vorbehalten. Liefermöglichkeiten und technische Änderungen vorbehalten. Alle verwendeten Hard- und Softwarenamen sind Handelsnamen und/oder Warenzeichen der jeweiligen Hersteller.

3 Contents 1 Unicode support Unicode in WebTransactions WebTransactions for OSD System object attribute TERMINAL_TYPE System object attribute HOST_CHARSET Notes WebTransactions for openutm The host data object attribute Unicode Host control object WT_HOST_MESSAGE Notes System object attributes Global system object attribute LT_REPLACE_STRING System object attributes for the HTTP host adapter COMMUNICATION_FILE_NAME COMMUNICATION_FILE_TYPE Related publications Index WebTransactions V7.1

4

5 1 Unicode support Unicode is an alphanumeric character set standardized by the International Standardisation Organisation (ISO) and the Unicode Consortium. It is used to represent various different types of characters: letters, numerals, punctuation marks, syllabic characters, special characters and ideograms. Unicode brings together all the known text symbols in use across the world into a single character set. Unicode is vendor-independent and system-independent. It uses either two-byte or fourbyte character sets in which each text symbol is encoded. In the ISO standard, these character sets are termed UCS-2 (Universal Character Set 2) or UCS-4. The designation UTF-16 (Unicode Transformation Format 16-bit), which is a standard defined by the Unicode Consortium, is often used in place of the designation UCS-2 as defined in ISO. Alongside UTF-16, UTF-8 (Unicode Transformation Format 8 Bit) is also in widespread use. UTF-8 has become the character encoding method used globally on the Internet. Increasing numbers of BS2000/OSD customers are opening up their BS2000/OSD applications for use with the Internet. The character set used on the Internet is UTF-8, and the Java language uses UTF-16 to encode data. Java Database Connectivity (JDBC) is used to connect Java applications and Java applets to BS2000/OSD databases. In the future, it is likely that simply converting data from the Internet into a single-byte code will no longer be sufficient. In addition, one-to-one transliteration of words from scripts that do not use the Latin alphabet into Latin script is neither desired nor possible, as the required diacritics may not be available in the character set which is currently set. The international postal regulations covering the addressing of mail require that the name of the sender and the address of the recipient must be written in the language of the destination country and the script used for that language. The destination city for overseas addresses must furthermore be written in capital letters in the script and spelling used in the destination country. This means that if Eastern European address data is to be stored in a database table alongside Western European address data, the character set used in an EBCDIC table is no longer sufficient. In other words, the character set used for the Name, City and Street columns of the database table must be able to accommodate Latin, Greek and Cyrillic symbols. You will find detailed information on Unicode support in BS2000/OSD in the manual Unicode in BS2000/OSD [1]. WebTransactions V7.1 5

6 Unicode in WebTransactions Unicode support 1.1 Unicode in WebTransactions The text below describes the interfaces that have been modified in WebTransactions since Version 7.0 in order to provide Unicode support. You will find a description of Version 7.0 in the relevant WebTransactions manuals (see Related publications on page 15). The following application-specific host adapters support Unicode: WebTransactions for OSD (see page 8) WebTransactions for openutm (see page 10) The following WebTransactions components and application-specific host adapters do not support Unicode: the WebTransactions kernel (see section page 7) WebTransactions for AS400 WebTransactions for MVS WebTransactions for UNIX Systems BizTransactions WebLab (Unicode characters cannot be represented) 6 WebTransactions V7.1

7 Unicode support Unicode in WebTransactions WebTransactions kernel The interpreter for the template language WTML (WebTransactions Markup Language and WTScript) does not support Unicode: WTScript templates are still interpreted as ISO-8859 characters. Each byte of a string will still be interpreted as one character. WebTransactions for OSD and WebTransactions for openutm create data encoded in UTF- 8, which is passed straight through to the browser and back. To achieve this, the following rules must be observed with respect to the templates: The templates must use charset to inform the browser what character encoding is to be used to display the data and to send the response. The browser receives this information either in the meta tag: <meta http-equiv="content-type" content="text/html;charset=utf-8" /> or by setting the attribute charset in the HTTP header field Content-Type. The templates are only allowed to contain ASCII characters. If a template contains special characters (such as German umlauts) directly in the form of ANSI characters in character strings, these must be replaced by HTML escape sequences. The escape sequences themselves are made up of ASCII characters only and can therefore be used in UTF-8. String operations can produce incorrect results if UTF-8 characters are included in the string (see also the notes on page 9 and page 12). Operations of this sort do not occur in the templates generated by WebTransactions. WebTransactions V7.1 7

8 WebTransactions for OSD Unicode support 1.2 WebTransactions for OSD WebTransactions for OSD supports the 9750 terminal protocol. The Unicode support provided in BS2000/OSD in turn makes this protocol Unicode-capable. You must explicitly enable Unicode support for 9750 by setting the relevant terminal type, otherwise WebTransactions for OSD behaves in the same way as the predecessor version (see the WebTransactions manual Connection to OSD Applications [6]) System object attribute TERMINAL_TYPE The system object attribute TERMINAL_TYPE specifies the terminal type to be simulated by WebTransactions. In order to enable Unicode support, enter the value 9763-UNICODE for TERMINAL_TYPE. Once this value has been specified, the emulation integrated in WebTransactions for OSD declares itself as Unicode-capable when a connection is established to BS2000/OSD. The OSD host application can now make use of this capability System object attribute HOST_CHARSET If the host application switches to Unicode mode, WebTransactions for OSD interprets field contents passed to and from BS2000/OSD as UTF-EBCDIC, and interprets the relevant contents of the host objects as UTF-8-encoded on assignment and outputs them in UTF-8 encoding on evaluation. The host adapter indicates this by the value UTF-8 in the system object attribute HOST_CHARSET. All templates that WebTransactions generates for this host adapter assign the system object attribute HOST_CHARSET to the global system object attribute CHARSET. The field Content-Type thus has the correct contents in the HTTP header and the browser can interpret the data correctly (see section WebTransactions kernel on page 7). 8 WebTransactions V7.1

9 Unicode support WebTransactions for OSD Notes Operations on strings Since the WebTransactions kernel itself does not support Unicode, you should take care when applying operations to strings. String operations can return incorrect results if the string contains UTF-8 characters. The length method does not return the number of characters, but rather the number of bytes. When comparing and manipulating such strings, you must take account of the representation of the UTF-8 characters. Such operations do not occur in the templates generated by WebTransactions. If only a substring is required for a field on screen, you can make use of the facilities provided by WebTransactions for OSD (see the WebTransactions manual Connection to OSD Applications [6] and the section on Host data objects, Generic names for host data objects ). P keys PKEY objects can only be supplied with Unicode characters by the host application. The PKEYS-ASSIGNMENT window does not support Unicode characters (see the WebTransactions manual Connection to OSD Applications [6] and the section on P key support ). The special characters EM and LZE can only be represented using ASCII characters. Diagnostics Unicode characters are represented by replacement characters in traces and in online displays of host objects. In WebLab, host objects can only be overwritten by 8-bit characters. WebTransactions V7.1 9

10 WebTransactions for openutm Unicode support 1.3 WebTransactions for openutm The host adapter in WebTransactions for openutm can also interpret data as Unicode characters at the UPIC interface. The BS2000/OSD program IFG2FLD reads format descriptions from an IFG library and stores them in a format description source. The fields in an IFG library can contain the new attribute Unicode. As of Version 8.3, IFG2FLD calculates the offsets of the individual fields in the UPIC buffer independently of this attribute. You can use WebLab to generate templates and field files (FLD files) from the format description source. During this conversion, the Unicode marker is automatically taken into account as of IFG2FLD Version 8.3 (see the WebTransactions manual Connection to openutm Applications via UPIC [5] and the section Generating templates ). FLD files The FLD files must be re-generated for all the formats that contain Unicode fields. Templates Existing templates can be retained unchanged if the only change in a format was the change to Unicode fields. However, the assignment of the value UTF-8 to the global system object attribute CHARSET must be inserted (see section Host control object WT_HOST_MESSAGE on page 11). 10 WebTransactions V7.1

11 Unicode support WebTransactions for openutm The host data object attribute Unicode The host data object attribute Unicode is one of the static attributes from the IFG format definition. These attributes are valid for all host objects (see the WebTransactions manual Connection to openutm Applications via UPIC [5] and the section Host objects for the individual format fields ). Unicode == 'Y' The host data in the UPIC buffer is converted to and from UTF-8 for forwarding to and from the browser for all fields marked Unicode == 'Y'. No ASCII-to-EBCDIC conversion is performed. Unicode == 'N' The host data is not converted to UTF-8. ASCII-to-EBCDIC conversion is carried out in dependence on the system object attribute HOST_CHAR_CODE Host control object WT_HOST_MESSAGE If the attribute Unicode is assigned to the host control object WT_HOST_MESSAGE, this indicates that at least one field where Unicode == 'Y' is contained in the current message. The global system object attribute CHARSET can be set to the value UTF-8 depending on this attribute. In this event, the field Content-Type thus has the correct contents in the HTTP header and the browser can interpret the data correctly (see section WebTransactions kernel on page 7). All templates that WebTransactions generates for this host adapter automatically include this assignment. This assignment must be manually inserted into existing templates which are not to be re-generated. WebTransactions V7.1 11

12 WebTransactions for openutm Unicode support Notes Operations on strings Since the WebTransactions kernel itself does not support Unicode, you should take care when applying operations to strings. String operations can return incorrect results if the string contains UTF-8 characters. The length method does not return the number of characters, but rather the number of bytes. When comparing and manipulating such strings, you must take account of the representation of the UTF-8 characters. Such operations do not occur in the templates generated by WebTransactions. Diagnostics Unicode characters are represented by replacement characters in traces and in online displays of host objects. In WebLab, host objects can only be overwritten by 8-bit characters. ASCII-to-EBCDIC conversion WebTransactions applications that have previously used the ASCII-to-EBCDIC conversion facility integrated in UPIC must be converted to use the ASCII-to-EBCDIC conversion facility provided by WebTransactions (see the WebTransactions manual Connection to openutm Applications via UPIC [5] and the section on Controlling communication - HOST_CHAR_CODE ). 12 WebTransactions V7.1

13 2 System object attributes The text below describes the system object attributes that have been introduced in WebTransactions V7.1 in addition to Unicode support (see page 5). 2.1 Global system object attribute LT_REPLACE_STRING The global system object attribute LT_REPLACE_STRING is one of the system object attributes that control the behavior of the WebTransactions kernel (see the WebTransactions manual Concepts and Functions and the section on Global session control ). HTML tags may be present in data coming from the browser (attributes of the object WT_POSTED). The attribute LT_REPLACE_STRING specifies a string used to replace the character < (less than) in such HTML tags. This allows you to deactivate HTML tags in input fields, for instance in order to prevent execution of code on an HTML page. 2.2 System object attributes for the HTTP host adapter COMMUNICATION_FILE_NAME The system object attribute COMMUNICATION_FILE_NAME has been introduced to the host adapter for dynamic web content (see the WebTransactions manual Access to Dynamic Web Contents and the section on Controlling communication ). You use this attribute to specify a file in which data received during a receive operation is to be stored. The body of the message is stored. The file must be located below the base directory. It is not permitted to store the file in the directory wwwdocs. You can use this attribute to transfer graphical images, for example. You can also specify a filter for storing the data in the COMMUNICATION_FILE_TYPE attribute (see page 14). WebTransactions V7.1 13

14 System object attributes for the HTTP host adapter System object attributes COMMUNICATION_FILE_TYPE The system object attribute COMMUNICATION_FILE_TYPE has been introduced to the host adapter for dynamic web content (see the WebTransactions manual Access to Dynamic Web Contents and the section on Controlling communication ). You use this attribute to define a filter for storing a message. The attribute contains the type of the message. Only when the type of the received message (Content-Type field in the HTTP header) corresponds to the value specified here is the body of the message stored in the file you specified with COMMUNICATION_FILE_NAME (see page 13). 14 WebTransactions V7.1

15 Related publications Unicode The manual is available as online manual, see or in printed form which must be paid and ordered separately at [1] Unicode in BS2000/OSD Introduction This manual gives an overview of the Unicode support in BS2000/OSD and describes basics, concepts and correlations, which apply for all BS2000/OSD products concerned by Unicode. Thus it completes the product-specific description in the respective manuals. Helpful tables from the Unicode conversion surroundings complete the manual. WebTransactions You can download all the WebTransactions manuals from the following Web address: [2] WebTransactions Concepts and Functions Introduction [3] WebTransactions Template Language Reference Manual [4] WebTransactions Client-APIs for WebTransactions User Guide [5] WebTransactions Connection to openutm Applications via UPIC User Guide WebTransactions V7.1 15

16 Related publications [6] WebTransactions Connection to OSD Applications User Guide [7] WebTransactions Connection to MVS Applications User Guide [8] WebTransactions Connection to AS400 Applications User Guide [9] WebTransactions Connection to UNIX Applications User Guide [10] WebTransactions Access to Dynamic Web Contents User Guide [11] WebTransactions Web Frontend for Web Services and Business Objects User Guide [12] BizTransactions Application Integration with Business Objects User Guide 16 WebTransactions V7.1

17 Index 9750 terminal UNICODE 8 A ASCII-to-EBCDIC conversion 11, 12 C CHARSET (system object attribute) 8, 10, 11 COMMUNICATION_FILE_NAME (system object attribute) 13 COMMUNICATION_FILE_TYPE (system object attribute) 14 Content-Type (HTTP header field) 8, 11, 14 F field files 10 FLD files 10 format description source 10 H HOST_CHARSET (system object attribute) 8 HTML deactivate tags 13 tags in input fields 13 I IFG library 10 IFG2FLD 10 L LT_REPLACE_STRING (system object attribute) 13 P P keys 9 PKEY objects 9 PKEYS-ASSIGNMENT 9 R receive storing data 13 S store message 13 filter 14 string operations 7, 9, 12 system object attribute CHARSET 8, 10, 11 COMMUNICATION_FILE_NAME 13 COMMUNICATION_FILE_TYPE 14 HOST_CHARSET 8 LT_REPLACE_STRING 13 TERMINAL_TYPE 8 T template 7 TERMINAL_TYPE (system object attribute) 8 traces 9, 12 U umlauts 7 Unicode (host data object attribute) 11 Unicode (WT_HOST_MESSAGE attribute) 11 UPIC interface 10 UTF-8 5 WebTransactions V7.1 17

18 W WebLab 6, 9, 12 WT_POSTED 13 WTML 7 WTScript 7 18 WebTransactions V7.1

19 Fujitsu Siemens Computers GmbH User Documentation Munich Germany Fax: (++49) 700 / Comments Suggestions Corrections manuals@fujitsu-siemens.com Submitted by Comments on WebTransactions V7.1 Supplement WebTransactions V7.1

20

21 Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions. Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at Copyright Fujitsu Technology Solutions, 2009 Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions. Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion. Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind. Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009