Copyright by Fujitsu Technologie Solutions, 2009 Alle Rechte vorbehalten

Size: px

Start display at page:

Miranda Wood
5 years ago
Views:

2 1 INTRODUCTION WTBEANS STAND-ALONE WTBEANS INLINE WTBEANS WTBEANS AND WEBLAB PROPERTIES LISTS WTBEANS INLINE COMPONENTS wtcsmtp wtctabs wtcpopupdate wtcpopupbox wtcmagneticbox wtcpopupmenu wtcmenu wtcctrltree wtcrecover wtcosdconsole STAND-ALONE COMPONENTS wtcframe wtcactiveportal wtcsinglesignon wtcterminal...60 Seite 2 von 64

3 1 Introduction WTBeans and their interfaces are described and explained in this document using examples. The WTBeans created from project solutions will help you to design visually appealing applications quickly and easily. A general description of handling WTBeans with WebLab can be found in the WebTransactions manuals and in the WebLab Help system. You will find additional explanations in Chapters 1.2 through 1.4. In following table you will find short descriptions of the WTBeans described in this document and their classification by type, language, processing and browser. The names of the WTBeans are listed in the column "WTBean". An explanation of the corresponding WTBean is found in the column "Short description". The only types are stand-alone and inline. The language in which the corresponding WTBean is written is shown in the column "Language". The values in the "Processing" column specify if the WTBean is executed on the client and/or server. Finally, the browser that is used to execute the WTBean is specified in the "Browser" column. WTBean Short description Type Language Processing Browser wtcsmtp wtctabs wtcpopupdate wtcpopupbox wtcmagneticbox wtcpopupmenu This WTBean can send s from the WebTransactions server. This WTBean provides a tab as an interface element in the browser. This WTBean implements a calendar window in the browser so you can select dates as input with the mouse. This WTBean creates pop-up boxes that you can position in your browser anywhere you want. You can also define the contents of these boxes as you wish. This WTBean generates areas in the browser in which tables can be defined. This WTBean allows the selection of values from a pop-up menu. inline WTScript server IE 4.0 or higher Netscape 4.0 or higher inline inline inline inline inline HTML/ JavaScript HTML/ JavaScript HTML/ JavaScript HTML/ JavaScript HTML/ JavaScript wtcmenu This WTBean generates a menu with HREF links. inline HTML/ JavaScript wtcctrltree This WTBean constructs a treeview menu. inline HTML/ JavaScript wtcrecover wtcframe wtcsinglesignon wtcactiveportal wtcosdconsole This WTBean (inline version of the former standalone WTBean wtcstart) allows you to recover an existing session that was interrupted (implemented using cookies). This WTBean provides a Web interface with which you can define and control several parallel threads (dialog objects). This WTBean is an extension of the WTBean wtcframe. The additional feature is a single sign on mechanism. This WTBean enables a WebTransactions session to run within TIBCO s Active Portal. This WTBean controls the access to a OSDconsole. inline HTML/ JavaScript stand-alone HTML/ JavaScript stand-alone HTML/ JavaScript stand-alone HTML/ JavaScript client client client client client client client client/server client/server client/server client/server IE 4.0 or higher IE 4.0 or higher IE 4.0 or higher IE 4.0 or higher IE 4.0 or higher IE 4.0 or higher IE 4.0 or higher IE 4.0 or higher Netscape 4.0 or higher IE 4.0 or higher Netscape 4.0 or higher IE 4.0 or higher Netscape 4.0 or higher IE 4.0 or higher inline WTScript server IE 4.0 or higher Netscape 4.0 or higher 1.1 WTBeans WebTransactions provides reusable components, the WTBeans, for programming the templates. There is a difference between inline and stand-alone WTBeans: inline WTBeans correspond to part of a WTML document Seite 3 von 64

4 stand-alone WTBeans are independent HTML or WTML documents WTBeans are also divided into categories according to their function: WTBeans for prompting with the browser The components control the frameset of one or more dialog steps. For example, they specify if the dialog will be executed in a simple window, in several windows or in different frames. WTBeans for dialog elements in the browser The components serve mainly to present data in the browser. HTML tags as well as more complex interfaces that can be defined using several HTML tags and client JavaScripts are some of these components. WTBeans for processing The components do not create an interface, but instead contain a section of processing logic for communicating with a host or connecting to a user exit library, for example. With WTBeans WebTransactions provides a collection of reusable components you can use to control communication with the browser as well as with the host application. Only the WTBeans for communication with the host application are preinstalled in the WebTransactions V4.0 package. See also the descriptions in the manuals for the specific protocols. You can download additional WTBeans from the WebTransactions home page ( as ready-to-run sample solutions. These additional WTBeans must be installed separately, i.e. in addition to WebLab or on the computer on which WebLab is installed. Each WTBean has a unique name, and since this name is also used as a variable name, the names are case-sensitive. The names begin with wtc (which stands for WebTransactions Component). Example: wtcstartosd Every WTBean is defined by a description file that contains the interface and prototypes of a WTBean. Furthermore, additional files can belong to a WTBean (for images, style definitions, etc.). The name of this description file is a combination of the name of the WTBean and the suffix.wtc. Example: wtcstartosd.wtc By modifying its properties, each WTBean can be customized for the corresponding WebTransactions application. An interface is also generated for WebLab from the description file so that you can comfortably edit the properties. After installation the WTBeans supplied are located in the corresponding inline, stand-alone or html subdirectory of the wtccollection subdirectory in the WebLab platform installation directory. These directories, except for html, in turn contain more subdirectories with the name of the corresponding WTBeans. The description files are located in these subdirectories. The subdirectory wtcusage is created in the current base directory as soon as you use a WTBean in WebLab. All description files for the WTBeans that you use to program your template are copied to wtcusage. This ensures that the WTBean used can also be edited later by another WebLab installation in which the corresponding WTBean may not have been installed. The HTML WTBeans play a special role. They are to be understood as HTML input aids from WebLab and are therefore only present on the WebLab computer. They are installed with WebLab and not copied to the base directories. The commands are different depending on if you want to insert a stand-alone or inline WTBean with WebLab. Important: A connection to the WebTransactions server must exist in order to insert or edit WTBeans. 1.2 Stand-alone WTBeans Seite 4 von 64

To insert a stand-alone WTBean, you first connect to a WebTransactions application. In WebLab you then select the command File/New. The WTBeans available that you can select from appear in a submenu.

5 To insert a stand-alone WTBean, you first connect to a WebTransactions application. In WebLab you then select the command File/New. The WTBeans available that you can select from appear in a submenu. The stand-alone WTBeans used to create a start template are preinstalled. Important: You can download additional WTBeans from the WebTransactions home page ( as ready-to-run sample solutions. These additional WTBeans must be installed separately, i.e. in addition to WebLab or on the computer on which WebLab is installed. The additional stand-alone WTBeans also appear in the submenu after installation. The available properties can be edited in a dialog box in one or more tab windows. The names of the parameters you must specify a value for are highlighted red. All other parameters are set to default values when you do not specify anything. Example of a dialog box for inputting properties: Confirm the data you have entered with OK. The corresponding template is created from your specifications and the description file and is then displayed in the WebLab work area. 1.3 Inline WTBeans To insert an inline WTBean you first open the template in which you want to insert the WTBean in WebLab. Place the cursor in this template at the corresponding location and select the command Insert/WTBean. The WTBeans available are displayed in a submenu from which you can select the desired WTBeans. You are supplied with inline WTBeans for creating a communication object for the various host adapters. Important: You can download additional WTBeans from the WebTransactions home page ( as ready-to-run sample solutions. These additional WTBeans Seite 5 von 64

must be installed separately, i.e. in addition to WebLab or on the computer on which WebLab is installed. The additional stand-alone WTBeans also appear in the submenu after installation.

6 must be installed separately, i.e. in addition to WebLab or on the computer on which WebLab is installed. The additional stand-alone WTBeans also appear in the submenu after installation. WebLab displays an interface so that you can edit the properties of the WTBeans. The available properties can be edited in a dialog box in one or more tab windows. The names of the parameters you must specify a value for are highlighted red. All other parameters are set to default values when you do not specify anything. Example of a dialog box for inputting properties: Confirm the data you have entered with OK. The corresponding WTML code is created from your specifications and the description file and inserted in the template. The description file for the WTBean used is stored in the wtcusage subdirectory of the base directory. 1.4 WTBeans and WebLab You can insert and edit WTBeans with WebLab. A WTBean consists of the actual code and blocks of HTML text in which you can insert any text, scripts or additional WTBeans. The code for a WTBean, regardless of whether the WTBean is a stand-alone or a inline WTBean, cannot be edited. For this reason this area is highlighted in gray in the template (see the following figure). You can subsequently change the properties of a WTBean. WTBeans are highlighted in WebLab by colored backgrounds in the Edit window. The boundaries of a WTBean are red, the boundaries of a wtcblock are blue and the boundaries of a wtclist are green (see the following figure). Display of WTBeans in WebLab: Seite 6 von 64

7 Blocks are the areas of a WTBean in which you are allowed to enter text and other WTBeans. What you are allowed to insert in this block is also specified in the description file of the WTBean: When you are allowed to insert text in the block, you can enter blank lines after the beginning of the wtc block or, when there are lines after the beginning which may not be overwritten, after these lines. When you are allowed to insert additional WTBeans, then these WTBeans are displayed in the submenu of the Insert/WTBean command. 1.5 Properties You cannot change the code of a WTBean, but you can subsequently edit the properties. Click with the right mouse button on the start line of the WTBean to open the context menu. Select the Edit WTBean command. The dialog box with the tabs for editing the properties is opened. The properties are initialized to the current values. 1.6 Lists Some WTBeans contain lists where the list elements are areas that appear several times in a row but with different parameters. Example: the WTBean wtctabs can divide the contents among several tab windows; each tab window is a list element in this case. The start and end lines of a list contain the keyword wtclist and are highlighted in green (see the figure above). The dialog to edit the list can be opened via the context menu of the start line. The parameters of the list elements can be changed in this dialog, list elements can be added and deleted and the order of the list elements can be changed. It is not possible to edit the properties of list elements individually. Example of a dialog box for inputting list properties: Seite 7 von 64

The list elements are displayed in a table in the Edit dialog. A row in the table corresponds to a list element, and each column corresponds to a parameter.

8 The list elements are displayed in a table in the Edit dialog. A row in the table corresponds to a list element, and each column corresponds to a parameter. You select a list element by clicking on the arrow in the first column of the corresponding row in the list. Change a parameter To change a parameter value, click on the corresponding field in the table. You can then enter the desired value in the input field in the lower part of the dialog. Add a new list element You create a new list element with the Add button. This button is inactive when the list already contains the maximum number of list elements allowed. In the subsequent dialog box you can enter all attribute values for the new list element. The new element is added to the end of the list. If a list element was selected before the new element was added, then the follow-up dialog box is initialized with the values of this element and the new element is inserted under the marked element. Delete a list element Mark the list element to be deleted by clicking on the flag on the left border of the corresponding line, and then activate the "Delete" switch. This switch is inactive when the list contains only the minimum allowable number of list elements. When deleting a list element, all contents of this list element are also deleted. Move a list element "Grab" a list element by clicking on the flag on the left border and holding down the mouse button. You can then drag the list element to the desired position and release the mouse button there. Seite 8 von 64

9 2 WTBeans WTBeans are reusable components that consist of client code (HTML/JavaScript) and/or of server code (WMTL/WTScript). The WTBeans are divided into two primary components, stand-alone or inline components. The stand-alone WTBeans describe a complete WTML document while inline WTBeans describe part of such a document. 2.1 Inline Components wtcsmtp The WTBean wtcsmtp allows WebTransactions to send electronic mail, also known as . To accomplish this the SendMail() function in the WTSystemExits library is used. Since WTScript statements can be created from this WTBean, this WTBean can only be used in WTScript tags (<wtoncreatescript>... </wtoncreatescript>, <wtonreceivescript>... </wtonreceivescript>). You can only send text messages (no MIME support) with the SendMail() function Properties The following properties can be changed via the Properties dialog of the WTBean. Property SMTP Mail Server From Subject Text Name or IP address of the SMTP mail server Sender's address in the form: name@domain Subject of the message ASCII text in quotes or a WTScript variable without quotes can be specified as the value for the Text parameter in the corresponding input field. The following properties can only be changed via the list elements of the WTBean. Property To Cc Bcc Receiver's address in the form: name@domain or in the form: alias<name@domain> Address for recipients of "carbon copies" in the form: name@domain or in the form: alias<name@domain> Address for recipients of "blind carbon copies" in the form: name@domain or in the form: alias<name@domain> The following property is generated dynamically. Property wtcsmtp_return The return value of the SendMail() function call is stored in this variable and can be queried there; possible return values are the character strings: OK Incomplete function call. Memory allocation failed. Function call: WSAStartup() failed. Creation of a socket failed. Function call: gethostbyname() failed. Connection to socket failed. Receive from socket failed. Send to socket failed Example The following lines are generated after this inline WTBean has been inserted in a template in WebLab. The lines that cannot be overwritten (gray) are not shown in this example. Seite 9 von 64

10 <wtoncreatescript>... <wtc SMTP Userexit> <wtclist Mail To List> </wtclist> <wtclist Mail Cc List> </wtclist> <wtclist Mail Bcc List> </wtclist> </wtc>... </wtoncreatescript> The generated WTScript code mainly contains the following two statements: wtcsmtp_smtpexit = new WT_Userexit( WTSystemExits ); wtcsmtp_smtpexit.sendmail(mailserver,mailfrom,mailto,mailcc,mailbcc,mailsubject,mailtext); The parameters for the SendMail() user exit call are supplied with values by WTBean. One or more addresses for the recipient (Mail To List), the "carbon copy recipient (Mail Cc List) and the "blind carbon copy" recipient (Mail Bcc List) can be entered with the green wtc tags (list tags) by clicking with the right mouse button on the corresponding wtc tag and then selecting the "Edit List" function from the pop-up menu wtctabs The WTBean wtctabs provides a tab for the browser interface of your application. You can distribute the contents of your interface amongst several tab windows. The corresponding tab window is activated by clicking with the mouse on one of the tabs. The full range of WTML functions can be used to assemble the contents of the tab windows. The label of the tab can also be modified using HTML tags. The WTBean wtctabs consists solely of browser functions. The WTBean will organize the tabs in several rows if necessary. If you do not like the automatic distribution function, then you can define a minimum width for the tab with the optional parameter Title Width. For example, you can make some tab windows a little wider and thereby move it to a back row so that a single tab is not alone in the last row. A hidden field with the name wtctabs_ident_activetab is created for each tab window on a page, where ident is the parameter Identifier. If the tab is located in a FORM element that will be sent to WebTransactions, then you can use this to determine which tab window was most recently activated Properties The following properties can be changed via the Properties dialog of the WTBean. Property Object Name Identifier Width Tab Height Name of the JavaScript object to be created; you use these object names in client JavaScripts when you call methods (see below) of your WTBeans. The optional parameter Identifier specifies a unique name for the tab. The index of the last tab window selected is sent with the name wtctabs_ident_activetab to WebTransactions, where ident is the identifier. If no identifier is specified, then the sequential number of the tab window (starting with 0) is used on the page. The numerical parameter Width specifies the width of the tab window. The numerical parameter Tab Height specifies the height of the tab window of the corresponding tab. Various colors can be selected as additional, optional properties via the Properties dialog of the WTBean. The following properties can only be changed via list elements of the WTBean. Property Seite 10 von 64

11 Title Text Title Width The parameter defines the label of the tab. The parameter defines the width of the tab Methods The following methods are defined for the WTBean object. They can be used in client JavaScripts. Object method Examples Object.activate(n) Object.enable(n) Object.disable(n) The tab window n (starting with 0) is brought to the foreground. The tab window n (starting with 0) is enabled. Clicking with the mouse on the tab now brings the corresponding window to the foreground. The color of the label changes. The tab window n (starting with 0) is disabled. Clicking with the mouse on the tab has no effect now. The color of the label changes. MyTabs.activate(0); index = 2; MyTabs.enable(index); MyTabs.disable(2); Example The following lines are generated after this inline WTBean has been inserted in a template in WebLab. The lines that cannot be overwritten (gray) are not shown in this example. <html><body>... <wtc Tab Control mytabs> <wtclist List of Tabs> <wtcblock tab1 > <BR>Contents of <STRONG><I>new tab 1</I></STRONG><BR><BR><BR><BR> </wtcblock> <wtcblock tab2 > <BR> Contents of <STRONG><I>new tab 2</I></STRONG><BR><BR><BR><BR> </wtcblock> </wtclist> </wtc>... </body></html> In this example a WTBean with two tab windows is created. The contents (WTML/HTML code) to be seen in the tab can be defined between the blue wtcblock tags of the corresponding tab. Output in the browser: Seite 11 von 64

2.1.3 wtcpopupdate The WTBean PopupDate provides a calendar window to allow you to input a date using the mouse.

The month and the year are displayed in the title bar and there are 5 control elements in this window that can be activated by clicking on them with the mouse.

Element Switch the display to the previous year Switch the display to the previous month Switch the display to the next month Switch the display to the next year Close the window

Property Object Name Year Name of the JavaScript object to be created; you use these object names in client JavaScripts when you call methods (see below) of your WTBeans

12 2.1.3 wtcpopupdate The WTBean PopupDate provides a calendar window to allow you to input a date using the mouse. An area for outputting a message can optionally be displayed on the bottom of the calendar window. The window can be moved by clicking on the title bar and dragging it. The month and the year are displayed in the title bar and there are 5 control elements in this window that can be activated by clicking on them with the mouse. These elements are described in the following table. The tag (date) is selected by clicking on it with the mouse. Element Switch the display to the previous year Switch the display to the previous month Switch the display to the next month Switch the display to the next year Close the window Examples: Properties The following properties can be changed via the Properties dialog of the WTBean. Property Object Name Year Name of the JavaScript object to be created; you use these object names in client JavaScripts when you call methods (see below) of your WTBeans Initialization for this property. If 0 was assigned, then the current year and month is displayed Month Initialization for this property. Please note that the months are counted from 0-11 Message Close Window Any text you want, appears at the bottom of the window If this property is set to true, then the window is closed when the mouse leaves the window; false means that the window is not automatically closed Seite 12 von 64

13 The font and various colors can be selected as additional, optional properties via the Properties dialog of the WTBean. The following property can only be defined dynamically using the parameters of the show() method. Property userdata Property that is defined if a user-defined parameter is specified for the show(userdata) method. In this manner you can pass a context to the show method that is then taken into account in the handledate(year,month,day) callback method. A reference to an input field is often passed that then is set to the selected date in the handledate(year,month,day) method Methods The following methods that can be used in client JavaScripts are defined for the WTBean object. Object method Examples Object.show(userData) Object.handleDate(year,month,day) Object.setYear(year) Object.setMonth(month) Object.setText(text) Object.setCloseWindow(bool) Object.setSize(size) Object.setBorderColor(color) The calendar window is displayed; the user-defined parameter userdata is defined as a property of this object The method handledate(year,month,day) is a callback function that is called after the user has clicked on a tag in the calendar window. The body of this function can be defined directly in the WTBean (blue wtcblock area). The selected date is passed in the parameters year, month and day. If the value true is returned, then the calendar window is closed, if false is returned, the calendar window will continue to be displayed. Initialization value for this property. If 0 is assigned, the current year and month is displayed. Calling this method will cause the initialization value from the properties dialog to be overwritten. Initialization value for this property. Please note that the months are counted from Calling this method will cause the initialization value from the properties dialog to be overwritten. User-defined text that appears at the bottom of the window. Calling this method will cause the initialization value from the properties dialog to be overwritten. If this property is set to true, then the window is closed when the mouse leaves the window, and if set to false, the window is not closed. Calling this method will cause the initialization value from the properties dialog to be overwritten. With this method it is possible to specify the size of the window. The default value for the size is 10. The color of the frame can be changed with this method. The default value for the color is # MyDate.show(document.forms[0].myField); MyDate.show(); Only called implicitly. year = 1998; MyDate.setYear(year); MySecondDate.setMonth(9); Start = Enter departure date: ; MyDate.setText(Start); MyDate.setCloseWindow(true); MyDate.setSize(20); MyDate.setBorderColor( red ); Seite 13 von 64

14 Object.setMessageBgColor(color) Object.setWorkdayNamesBgColor(color) Object.setTitleBgColor(color) Object.setWeekendNamesBgColor(color) Object.setWorkdaysBgColor(color) Object.setWeekendBgColor(color) Object.setCurrentDaysColor(color) Object.setFurtherDaysColor(color) Object.setWeekdayNamesColor(color) Object.setTitleColor(color) Object.setMessageColor(color) The Message area (see below) in the calendar window is set to the color specified in color. The default value for the color is #ffffff. The workdaynames area (see below) in the calendar window is set to the color specified in color. The default value for the color is #ffffff. The Title area (see below) in the calendar window is set to the color specified in color. The standardvalue the color is # The weekendnames area (see below) in the calendar window is set to the color specified in color. The standard-value the color is #dddddd. The Workdays area (see below) in the calendar window is set to the color specified in color. The default value for the color is #ffffff. The Weekend area (see below) in the calendar window is set to the color specified in color. The default value for the color is #dddddd. The color of the text for the day of the current month in the calendar window is set to the color specified in color. The default value for the color is # The color of the text for additional days of the previous and next month in the calendar window is set to the color specified in color. The default value for the color is # The color of the text for the abbreviations of the weekdays in the calendar window is set to the color specified in color. The default value for the color is # The color of the text for the name of the current month in the calendar window is set to the color specified in color. The default value for the color is #ffffff. The color of the text for the optional message in the calendar window is set to the color specified in color. The default value for the color is # MyDate.setMessageBgColor( #6699CC ); MyDate.setWorkdayNamesBgColor( # ); MyDate.setTitleBgColor( red ); MyDate.setWeekendNamesBgColor( white ); color = green ; MyDate.setWorkdaysBgColor(color); MyDate.setWeekendBgColor( # ); MyDate.setCurrentDaysColor( black ); MyDate.setFurtherDaysColor( white ); MyDate.setWeekdayNamesColor( #ffffff ); MyDate.setTitleColor( orange ); MyDate.setMessageColor( firebrick ); Background areas: The names of the methods in the table of object methods (see above) are defined according to the following table. workdaynames Title weekendnames Seite 14 von 64

15 Workdays Weekend Message Example The following lines are generated after this inline WTBean has been inserted in a template in WebLab. The lines that cannot be overwritten (gray) are not shown in this example. <html> <body>... <wtc pop-up Date: mydate> <wtcblock Body of function wtcpopupdate_handledate(year,month,day) of object: mydate> // The return value controls the closing of the date control window: // return true; - closes the window after return // return false; - displays the window after return // The parameters of the callback function wtcpopupdate_handledate are: // year - the selected year // month - the selected month // day - the selected day this.userdata.value = day+. +(month+1)+. +year; return true; </wtcblock> <wtcblock Sample of PopupDate control> <INPUT TYPE= TEXT NAME= example VALUE= ONCLICK= ##wtcpopupdate_name#.show(this); > </wtcblock> </wtc>... </body> </html> The body of the method handledate(year,month,day) is defined in the first blue overwritable wtcblock. Here you can specify the format to be used for the date. The selected date is passed to this method with the parameters year, month and day. Furthermore, an object specified in the call of the show(userdata) method is accessed with the property userdata. In this example this object is an input field that is specified in the second overwritable wtcblock. The output in the browser then appears as follows: Seite 15 von 64

16 Notice: The line in the second overwritable wtcblock only serves as an example: <INPUT TYPE= TEXT NAME= example VALUE= ONCLICK= ##wtcpopupdate_name#.show(this); > In general you will delete this line and define a corresponding event handler (for example OnClick) for an existing field, for example: <INPUT TYPE= TEXT NAME= myfield ONCLICK= mydate.show(this) > wtcpopupbox With the WTBean PopupBox you can distribute the contents of your page across several pop-up boxes. The user can position these boxes in his browser window. You can also hide individual boxes, cause them to reappear, drag or arrange them using the corresponding method calls. You can use any HTML elements in the pop-up boxes themselves. You can provide small tools for editing the contents of the page in the boxes. It is also possible to distribute the input fields of a host mask amongst several boxes. The WTBean PopupBox consists of browser and server functions. The WTBean should be used in <BODY> tag sections. The user can drag the boxes in his browser window. When the page is reloaded in the browser, the boxes should appear at the location they were dragged to and not at their original location. The coordinates are stored for the entire duration of a session. If you create a box in this manner with a key that was already used in a previous page, then the box will appear at the location it was last located at on this page. To transmit the coordinates back to WebTransactions, the WTBean must be located in the <wtdataform> area and this form must be sent to WebTransactions. The boxes can now be moved like windows by dragging them using the title bar. You can also use the pop-up boxes in Web pages containing statistics. In this case the coordinates of the moved boxes are lost when you leave the page. Examples: Seite 16 von 64

2.1.4.1 Properties The following properties can be changed via the Properties dialog of the WTBean.

17 Properties The following properties can be changed via the Properties dialog of the WTBean. Property Object Name Key Title X-coordinate Y-coordinate Width Name of the JavaScript object to be created; you use these object names in client JavaScripts when you call methods (see below) of your WTBeans You specify a unique identifier for this page here. If you create a pop-up box with the same identifier on a later page, then the coordinates of the former pop-up box on the page are used. In this manner you can ensure that a box moved by a user appears at the same location on the next pages. Title for the pop-up box. X-coordinate of the upper left corner of the pop-up box. Y-coordinate of the upper left corner of the pop-up box. Width of the pop-up box. Various colors can be selected as additional, optional properties via the Properties dialog of the WTBean Methods The following methods that can be used in client JavaScripts are defined for the WTBean object. Object method Examples Object.moveTo(x,y) The pop-up box is moved to the specified coordinates. The coordinates are the absolute coordinates of the Web page in the browser. X1 = y1 = 100; MyBox.moveTo(x1,y1); Object.activate() The pop-up box is brought to the foreground. MyBox.activate(); Object.hide() The pop-up box is hidden from view. MyBox.hide(); Object.show() The pop-up box is made visible. MyBox.show(); Object.toggle() The visibility of pop-up box is toggled. MyBox.toggle(); Object.order(mode) All pop-up boxes are arranged depending on the mode: 'column', 'row' and 'cascade' arrange the boxes next to each other, on top of each other or overlapping each other. MyBox.order(cascade); Example The following lines are generated after this inline WTBean has been inserted in a template in WebLab. The lines that cannot be overwritten (gray) are not shown in this example. <html> <body> Seite 17 von 64

If you do not want to display the pop-up box when the Web page is loaded, then you can add the Object.hide() method call after the end tag </wtc> of this WTBean, for example.

18 ... <wtc PopupBox Control mybox > <wtcblock> <TEXTAREA NAME= mytextarea COLS= 30 ROWS= 12 ></TEXTAREA> </wtcblock> </wtc> <SCRIPT> mybox.hide(); </SCRIPT>... </body> </html> The contents of the pop-up boxes are define between the blue wtcblock tags. You can use all HTML elements there, for example. If you do not want to display the pop-up box when the Web page is loaded, then you can add the Object.hide() method call after the end tag </wtc> of this WTBean, for example. The output in the browser would appear as follows when this WTBean is displayed: wtcmagneticbox The WTBean MagneticBox creates areas in which tables can be defined in the browser. The WTBean displays several user-definable columns in a rectangular area on your Web page. The order of these columns can be changed by dragging on the column header with the mouse. The width can be changed by grabbing the right side of the column header. The columns are always shown flush with each other and next to each other. Complex tables can easily be rearranged by the user with this component so that one or more interesting aspects are more easily recognized. You can specify the number of the columns by adding or deleting columns by clicking with the right mouse button on the green start tag of the list. Examples: Seite 18 von 64

2.1.5.1 Properties The following properties can be changed via the Properties dialog of the WTBean.

19 Properties The following properties can be changed via the Properties dialog of the WTBean. Property Object Name Width Height Name of the JavaScript object to be created; you use these object names in client JavaScripts when you call methods (see below) of your WTBeans Width of the object. Height of the object. Various colors can be selected as additional optional properties via the Properties dialog of the WTBean. The following properties can only be changed via list elements of the WTBean. Property Title Text The parameter defines the label of the column. Title Width The parameter defines the width of the column Example The following lines are generated after this inline WTBean has been inserted in a template in WebLab. The lines that cannot be overwritten (gray) are not shown in this example. <html> <body>... <wtc name= wtcmagneticbox type= inline version= 4.0 > <wtclist name= List of columns > <wtcblock> Meier<BR> Müller<BR> Huber<BR> </wtcblock> <wtcblock> München<BR> Berlin<BR> Passau<BR> </wtcblock> <wtcblock> <BR> Seite 19 von 64

22222222<BR> 33333333<BR> </wtcblock> </wtclist> </wtc>... </body> </html> The output in the browser appears as follows: 2.1.

20 <BR> <BR> </wtcblock> </wtclist> </wtc>... </body> </html> The output in the browser appears as follows: wtcpopupmenu The WTBean PopupMenu has almost the same functionality as an HTML selection box. Lists can be specified with internal and external values. The results of the selection are assigned to a text box in the simplest case. However, it is also possible to specify separate result handlers that process the results of the selection. In contrast to the HTML selection box, the PopupMenu does not require any space on the Web page when it is not active. It is only visible during the selection process. It is closed again after a selection has been made. The WTBean PopupMenu consists solely of browser functions and should be inserted in a BODY tag section. You can now connect the menu to a field by calling the show() method in one of its event handlers. The selected value then appears in the input field, for example: <INPUT TYPE= TEXT ONCLICK= mymenu.show(); > When you want to process individual return values, you pass a suitable script as an argument of the show() method. The return value from the pop-up menu is available in the variable "value". The following handler only displays sufficiently large values in a text box: MyMenu.show( if(value>10) document.forms[0].myfield.value=value; ); Properties The following properties can be changed via the Properties dialog of the WTBean. Seite 20 von 64

21 Property Object Name Name of the JavaScript object to be created; you use these object names in client JavaScripts when you call methods (see below) of your WTBeans Various colors can be selected as additional, optional properties via the Properties dialog of the WTBean. The following properties can only be changed via list elements of the WTBean. Property External The parameter defines the external value (interface). Internal The parameter defines the internal value Methods The following methods that can be used in client JavaScripts are defined for the WTBean object. Object method Examples Object.show() The pop-up menu is made visible. MyMenu.show(); Object.hide() The pop-up menu is hidden. MyMenu.hide(); Object.setColors(fg,bg,fgSel,bgSel) With this method you change the color of the menu entry fg, the background color of the menu bg, the color of the selected menu entry fgsel and the background color of the selected menu entry bgsel. Col1= red ; Col2= steelblue ; Col3= orange ; Col4= lightblue ; MyMenu.setColors(Col1,Col2,Col3,Col4); Example The following lines are generated after this inline WTBean has been inserted in a template in WebLab. The lines that cannot be overwritten (gray) are not shown in this example. <HTML> <BODY>... <wtc name= wtcpopupmenu type= inline version= 4.0 > <wtclist name= ValueList > </wtclist> <wtcblock> <INPUT TYPE= TEXT ONCLICK= ##wtcpopupmenu_name#.show(); > </wtcblock> </wtc>... </BODY> </HTML> The input tag in the wtcblock is an example of a call for this WTBean. The internal and external values of the menus are defined with the wtclist tag. Output in the browser: Seite 21 von 64

2.1.7 wtcmenu This WTBean wtcmenu creates a menu with drop-down boxes for selecting HREF links. This menu can also be established and modified dynamically by executing of the methods objekt.

22 2.1.7 wtcmenu This WTBean wtcmenu creates a menu with drop-down boxes for selecting HREF links. This menu can also be established and modified dynamically by executing of the methods objekt.addmenuitem() and objekt.deletemenuitem(). Every entry has four parameters: 1. Name of the menu, which should list the new entry. 2. Target of the entry. 3. Caption of the new entry. 4. HTML attribute target. The attribute target specifies one of the following values: target name The name of the target window or frame. _blank Load the linked document into a new blank window _parent Load the linked document into the immediate parent of the document the link is in. _search Load the linked document into the browsers search pane. Available in IE 5 or later. _self Default. Load the linked document into the window in which the link was clicked (the active window). _top Load the linked document into the topmost window Properties The following properties can be changed via the Properties dialog of the WTBean. Property Object name Name of the JavaScript object. The following properties can only be changed via list elements of the WTBean. Property Menu item name Name of the item within the menu bar. Seite 22 von 64

Menu entry href Menu entry text Menu entry target Hyper reference of the anchor tag. Name of the menu entry. Target property of the anchor tag. 2.1.7.

23 Menu entry href Menu entry text Menu entry target Hyper reference of the anchor tag. Name of the menu entry. Target property of the anchor tag Methods The following methods that can be used in client JavaScripts are defined for the WTBean object. Object method Examples objekt.setbgcolormenu(color) The background color is set to color. MyMenu.setBgColorMenu( steelblue ); objekt.setbordercolor(color) The color of the border is set to color. MyMenu.setBorderColor( gainsboro ); objekt.setshadow(boolean) Menus with shadow. (MS IE V5.5 or later) MyMenu.setShadow(true); objekt.setfade(boolean) objekt.setbgcolormenuitem(color) objekt.addmenuitem(item,href,text,tar get) objekt.deletemenuitem(item,text) Menus with fading display. (MS IE V5.5 or later) The background color of the menu items is set to color. Adding one element to a menu. The entry text of the menu item is going to be deleted. MyMenu.setFade(true); MyMenu.setBgColorMenuItem( red ); MyMenu.addMenuItem( WebTransactions, Fujitsu Technology Solutions, appframe ); MyMenu.deleteMenuItem( Microsoft, Works hop ); Example There are three entries within the menu: WebTransactions, Microsoft and ZDF. The drop-down list of the entry WebTransactions is displayed with shadows and there is one item in it: Fujitsu Technology Solutions. Output in the browser: Seite 23 von 64

24 2.1.8 wtcctrltree The WTBean wtcctrltree creates a JavaScript tree control in a way very similar to the windows explorer s treeview. You can expand or collapse a branch by clicking the corresponding icon or by clicking at the caption of the item. Clicking at an item means also that the click handler for this item will be executed. You can assign a specific context handler or a click handler for every item and for the WTBean itself. If the mouse pointer is over an item then a custom tool tip will be displayed Properties The following properties can be changed via the Properties dialog of the WTBean. Property Object name Root CSS file Click handler Context handler Width Name of the JavaScript object to be created; you use these object names in client JavaScripts when you call methods (see below) of your WTBeans Identifier for the root entry. Parameter used to address a style sheet. Click handler of the WTBean. Context handler of the WTBean. The parameter defines the width of the WTBean. The following properties can be changed via list elements of the WTBean. Property Item ID Identifier of the new entry. Parent node Identifier of the parent node. Icon Possible values: Plus or Atom, according to tree nodes or tree leaves. Text Text (caption) of the entry within the tree. Help text Contents of the tool tip. Click Handler The parameter defines the click handler of the WTBean. Context Handler The parameter defines the context handler of the WTBean. The following properties can only be changed via list elements of the WTBean. Property Handler name There will be generated a wtcblock area for every user defined handler. Seite 24 von 64

25 Methods The following methods that can be used in client JavaScripts are defined for the WTBean object. Object method Examples objekt.setbgcolor(color) The background color is set to color. MyMenu.setBgColor( cyan ); objekt.setfont(font) The font is set to font. MyMenu.setFont( bold 14pt Comic ); objekt.setborder(border) This method defines the border. MyMenu.setBorder( thick outset darkcyan ); objekt.setheight(height) objekt.setpadding(value) The height of the container is set to height. The HTML attribute padding is set to value. MyMenu.setHeight( 200 ); MyMenu.setPadding( 10px ); objekt.setposition(pos) This method defines the position. MyMenu.setPosition( absolute ); objekt.setitemcolor(color,mode) objekt.setitembgcolor(color,mode) objekt.setitemwidth(width,mode) objekt.seticon(icon,type) objekt.addelement(itemid,parentid,ico n,text,help_text,click_handler,context _handler) objekt.deleteelement(itemid,parentid) Example Output in the browser: This method sets the color if an item for the following modes: normal, selected or clicked. This method defines the background color of an item according to the following modes: normal, selected or clicked. This method defines the width of an item according to the following modes: normal, selected or clicked. This method defines the icon for an branch or leaf. Possible types are Plus (collapsed branch). Minus (expanded branch) or Atom (leaf). This method adds a new element to the tree. (for description of the parameters see above). This method deletes a element (itemid/parentid) from the tree. MyMenu.setItemColor( gray, Normal ); MyMenu.setItemColor( yellow, Selected ); MyMenu.setItemColor( orange, Clicked ): MyMenu.setItemBgColor( transparent, Normal ); MyMenu.setItemBgColor( gainsboro, Selected ); MyMenu.setItemBgColor( transparent, Clicked ): MyMenu.setItemWidth( 250, Normal ); MyMenu.setItemWidth( 250, Selected ); MyMenu.setItemWidth( 250, Clicked ): MyMenu.setIcon( pic1.gif, Plus ); MyMenu.setIcon( pic2.gif, Minus ); MyMenu.setIcon( pic3.gif, Atom ); MyMenu.addElement( id1, id2, Atom, new item, new item help text,, ); MyMenu.deleteElement( id1, id2 ); Seite 25 von 64

26 2.1.9 wtcrecover This WTBean allows you to recover a running session. This recovery function is implemented with cookies. The components of the WTBean wtcrecover consist of the description file wtcrecover.wtc, a file with browser functions wtcrecover_browserfunctions.js, and of the file wtrecover_update.htm. After inserting this WTBean into a start page, you have access to the object in order to use the methods described below. The file wtcrecover_update.htm must be included in all templates which should support the recovery. Important: You must add the following line to all your templates to transport the recovery information to the browser: <wtinclude name="wtcrecover_update"> Properties The following properties can be changed via the Properties dialog of the WTBean. Property Object Name WTPublish/WTCluster Session ID Domain Coupler Basedir/ClusterID Start Template Name of the JavaScript object to be created You specify with this parameter if a cluster session is to be used instead of a normal WebTransactions session. The Session ID property is a user-defined character string that identifies the session for the recovery procedure. The names of the cookies contain this identifier as part of their names. In this manner it is possible for several sessions (possibly of the same type) to maintain recovery information in parallel. The identifier can consist of letters, numbers and underscores. The Domain parameter specifies the domains in which the server used is to be found. The server with the start page and the server with the WebTransactions application or the members of the cluster must all be located in the same domain. If the start template and application are located on the same server, then an empty string can be specified here. The Coupler parameter defines the path to the WTPublish.exe or WTCluster.exe program. The WTPublish base directory is specified for this property or, if WTCluster was selected, the cluster identifier is specified here. The Start Template parameter designates the start template. The following properties can only be changed using the list elements of the WTBean. Property Name Value If additional data is to be sent at the start of the session, the name of a name/value pair that is to be added to your URL object can be defined here. If additional data is to be sent at the start of the session, the name of a name/value pair that is to be added to your URL object can be defined here Methods Seite 26 von 64

27 The following methods that can be used in client JavaScripts are defined for the WTBean object. Object method Examples object.loadstarturl() object.loadrecoverurl() The HTML anchor parameter location.href is set with the start URL of a WebTransactions application. The HTML anchor parameter location.href is set with the recoverurl of a WebTransactions application. object.addnamevaluepair(name,value) You can add a name/value pair to the start URL with this method. object.isrecoverable() object.clearcookies() object.writestartform() This method is checking if there is a cookie with a session to be recovered. Return values are true or false. You can clear the cookie of the session with this method. This method creates a form tag to start a WebTransactions application. You must add the closing end tag (</form>) and the content (e.g. a submit button) of the form tag. <script> document.write('<br><a href="javascript:myrecoverobject.loadstartu RL();">start new session</a>'); </script> <script> document.write('<br><a href="javascript:myrecoverobject.loadrecov erurl();">recover session?</a>'); </script> <script> myrecoverobject.addnamevaluepair("myna me","myvalue"); </script> <script> if( myrecoverobject.isrecoverable() ) {... } </script> <script> document.write('<br><a href="javascript:myrecoverobject.clearcooki es();">clear cookies?</a>'); </script> <script> myrecoverobject.writestartform(); </script> <BR><INPUT TYPE="SUBMIT" VALUE="start new session "> </form> Files The following files are components of the WTBean wtcstart. Files wtcrecover.wtc wtcrecover_browserfunctions.js wtcrecover_update.htm file of the WTBeans wtcstart. The JavaScript methods that belong to this WTBean are defined in this file. The statement <wtinclude name="wtcrecover_update"> should be placed at the very end of the template, i.e. after any statements used to change the WT_SYSTEM.TIMEOUT_USER attribute or a call to the exitsession() method, for proper synchronization with the timeout value or to explicitly end the session. The statement shown above should be placed in every template if possible to achieve consistency between the browser cookie and the running session. Notice: Note, however, that any recovery information for a currently running session may be overwritten when this is done. If, for example, you want to sign on to a UTM application, then it makes sense to send the recovery information only after the sign on procedure is successful. Otherwise the end user, by ignoring the link used for recovery, may find himself in a situation in which he is signed on as a UTM user to a WebTransactions application that he does not have access to anymore Instructions for using wtcrecover You must perform the following steps in order to open a new start page with restart. Seite 27 von 64

28 1. Modify the start page Create a start page and put it under <base directory>/wwwdocs/html Insert the WTBean wtcrecover into this page You specify the following properties under the general settings for the WTBean (see 1.5 Properties): Specify a unique identifier as the Object Name. You specify which CGI coupler program you want to use with WTPublish/WTCluster. You specify a character string for recovery with Session ID. The optional Domain parameter specifies the domain of the server used. You specify the name of the CGI program and the corresponding URL prefix with Coupler. The Basedir/ClusterID parameter defines your WebTransactions base directory or a cluster identifier when you want to work with WebTransactions clusters. You specify the Start Template of your application here. Your start page is created when this Properties dialog is confirmed. 2. Provide restart information in the templates The following statement must be added for recovery purposes at the end of each template in which recovery is to be made possible: <wtinclude name="wtcrecover_update"> 3. Start the start page You start the page then in the browser with the following URL: path>/<base directory>/wwwdocs/html/start.htm The name of your start page is to be specified as the start page (for example Start.htm). The <virtual path> parameter is the character string you specified in the WebTransactions administration as the virtual path to the directory in which you created the base directory for your application. 4. Test the restart function After your start page is loaded in the browser, start your application using the HTML type that you specified when generating the WTBean. Now close the browser when you are in a dialog page of your application. Reopen the browser and reload your start page (see above). You should now receive a message that there is a session present, and you can then continue with this session at the location you were at when you closed the browser. 5. Possible causes of error Check to make sure that the wtcrecover_update.htm template is included in all thread templates, even in the template in which you terminate your session. Check to make sure that the start page is not loaded from the cache (browser or proxy cache). Check to make sure that the cookie stored on your computer was not deleted during an earlier, improper program termination before you load the start page wtcosdconsole This WTBean controls the access to an OSD console. The components of the WTBean wtcosdconsole are the description file wtcosdconsole.wtc, and the files wtcosdconsole_frames.htm, wtcosdconsole_input.htm and wtcosdconsole_output.htm. Two OSD connections are established for the user account defined with the attribute userid. Afterwards the input stream for a console is linked to the first connection and the output stream for a console is linked to the second one. The browser window is divided into two parts. The top part allows entering the input to the console and displays a history of the last three input commands. The lower part displays the output of the console. The content of the window is refreshed at regular time intervals. Seite 28 von 64

29 Note: The user account for the OSD identification must possess the necessary rights, to access the console application. Additionally the user account has to be linked to the used operator role. If the software product SECOS is installed you may enable any user account with these rights. Otherwise you have to use the predefined user account SYSOPR. Properties The following properties can be changed via the properties dialog of the WTBean. Property Host Userid Account Password Operator Role Use of prefix Name of the host computer, which is to be administered. A valid identification, which has the right for console administration. Account for the user identification. Password for the user identification. Operator role the is linked to Userid. If the templates are using prefixes, then this flag has to be set. All further properties are described with the WTBean wtcosd. Files Files wtcosdconsole.wtc wtcosdconsole_frames.htm wtcosdconsole_input.htm wtcosdconsole_output.htm file of the WTBean wtcosdconsole. This file represents the frame for Console access. Two different OSD connections are displayed. In the top part inputs to the console can be made and a history of up to three commands is displayed. The console output (asynchronous) is displayed in the lower part.. This file represents the connection for input to Console. A history of up to three commands is displayed. This file represents the connection for output of Console. The console output (asynchronous) is refreshed. Seite 29 von 64

30 2.2 Stand-alone Components wtcframe Short description The WTBean wtcframe allows you to create a portal interface. Mainframe applications, Web applications, along with static Web pages can easily be integrated. Various sources of information can extend the portal flexibly by using portlets. A characteristic of this portal is the support of threads (dialog objects). These are stateful web dialogues. The concurrent usage of several of such threads and changing between them is already realized by wtcframe. The portal supplies two logically equivalent interfaces, which are optimized for the Browser and for the small display of a PDA. By interaction with the WTBean wtcsinglesignon (see ) the portal becomes role-based. Then the available information can be restricted more or less depending on the roles of a user. There are personalized menus and pages, which the user can adjust to create a personal Webtop within the portal. It is also possible to control the access to information or contents dependent on specific users or roles and thus enable a deliberate exchange of information over the portal. By combining wtcframe with the WTBean wtcsinglesignon (see ) the portal becomes restartable. After a loss of the connection or a crash of the browser the session can be started again. It is then continued smoothly in the same state as before the connection was lost. The session can also be resumed from another device. If the user switches from the Browser to a PDA or vice versa the interface is switched accordingly. For a mobile user this functionality is used to change between stationary Business PC, Notebook, PDA, or access from an internet terminal etc., in order to provide him with his personal working environment everywhere; therefore this feature is called Roaming Support. In the following sections, Interfaces, Personalizing, and Administration, the functionality is described from the point of view of the user. Starting from the characteristics, methods and functions are described for developers, who want to install and configure the Bean and wish to combine it with other functionalities User Interfaces The WTBean wtcframe allows you to combine several parallel threads (dialog objects) in a Web interface. The WTBean can administer any number of such threads. These threads are started by selecting them in the start menu, and the current page of the thread is then displayed in the main window. You can generally enter data and go from screen to screen in the thread in the main window. It is possible to start another thread in the start menu or switch at any time to a thread that has already been started using the selection menu. The current screen of this thread is then shown in the main window. For example, a thread can be prepared for display of a terminal interface for a mainframe application. You therefore have a simple way of obtaining multiple emulations with this WTBean. When reengineering a dialog, certain procedures that may need to be performed in a mainframe application by going through several masks (for example to search for customers, create offers, create invoices, etc.) are often controlled by WebTransactions and displayed in a single interface. Such procedures can then be easily integrated with this WTBean PC User Interface The WTBean provides a frameset for the interface. The browser window is divided into 4 visible areas (frames). These areas are defined as the information window, main window, start menu and selection menu. There is also a hidden area (frame) that implements support for asynchronous messages and for printers (see the WebTransactions manuals). Diagram of the frames of the WTBean interface: Seite 30 von 64

31 Logo, Personalizing, Portal Menu (Information Window) Open Threads (Selection Menu) Possible Threads (Start Menu) Dialog (Main Window) You can select a thread from a menu of different thread types in the start menu. A thread of this type is then started and displayed in the main window. In addition, an extra button for this open thread is displayed in the selection menu. You can now work with your thread in the main window. You can go to the start menu at any time to open another thread or switch between open threads using the buttons in the selection menu. A button is also provided in the start menu so you can cancel the execution of the currently open thread shown in the main window. The corresponding button then disappears from the selection menu, the context switches to a neighboring thread (if there is one) and this thread is then displayed in the main window. You also have the opportunity in the start menu to terminate the entire session and all threads. The actual processing of the thread is performed in the main window. Such a thread can consist of an interface that is presented to the user only once or several times (for example a search mask that displays the results and also allows you to start a new search). The thread can also consist of a series of different interfaces (for example the display of a terminal interface, see the "$DIALOG" thread in the example). In the information window you find also a two-level menu, that can be personalized. If you select a menu option, a submenu is displayed or the special thread Portal page is started, in order to display the desired information. It can be a portlet for the visualization of a source of information or it can be a page with several portlets aggregating several sources of information. It is also possible to display the contents of a portal page in its own new browser window. The menu can also be configured to display the information always in a new window. In addition the name of the user, who is currently logged on, is shown in the information window You can start a dialog from here to change your personal settings. The background of the information window can be adapted specifically for each usage. For each us the portal administration can define corresponding styles. The user can change his portal settings in order to display a personal picture, which he would like to see in the header of his web page. If this WTBean is operated from a pocket PC, the interface is automatically adapted to the reduced screen size of the Pocket Internet Explorer: Seite 31 von 64

Possible Threads (Start Menu) Open Threads (Selection Menu) Dialog (Main Window) Footer (Additional Keys) The selection of new or open threads is made by two drop down lists.

The thread $DIALOG uses this frame for example to supply the function keys (wtcframe_wtkeysdialog.htm). The template to be displayed is can be configured in the list of threads (see 2.2.1.

32 Possible Threads (Start Menu) Open Threads (Selection Menu) Dialog (Main Window) Footer (Additional Keys) The selection of new or open threads is made by two drop down lists. There is no Logo Frame, but each application can use an additional frame at the lower edge for control elements. The thread $DIALOG uses this frame for example to supply the function keys (wtcframe_wtkeysdialog.htm). The template to be displayed is can be configured in the list of threads (see ) Personalizing The portal supplied by wtcframe offers the possibility to personalize the interface. Apart from the representation and the language the users can also add individual information and entrances to applications in the portal. These are stored permanently and are then available on each device in the net. The personalized information can also be made available for different users. Thus a network of related information develops. The administrator essentially administers the users and roles, which regulate the access rights. Contents management and their administration are controlled by the users themselves. If you log in to the portal for the first time as a new user the interface will look as in the diagram above. You find the threads specified for your roles in the left lower start menu. At the beginning no thread has been opened yet. The personalized horizontal menu in the upper frame is still empty. The personalizing was intentionally kept simple. You can gather the information very intuitively always directly in the place, in which they are to appear later. Thus step for step an empty menu and an empty page become a rich interface.this procedure is described in the following chapters. A short definition of the most important terms is placed in front Terms In the following sections some terms for the portal are used, which are defined here briefly. Menu: A list of menu entries, which are displayed in the information window as colored, horizontally arranged links. Seite 32 von 64

33 Main Menu: This topmost menu is always visible in the information window. It can activate sub-menus, which are then represented in the information window in a second line. Menu Entry: A menu entry stands for an option from a menu. A menu entry has a label, which is displayed as option of the menu in the information window, and a description. The label should not be long too, since it is displayed in full width in the information window. The description appears as a tool tip, if the mouse cursor is moved over the menu entry in the information window; therefore this description can be somewhat in more detail. The most important part of a menu entry is its action. This can be a menu, then clicking on this entry displays the appropriate sub-menu in the information window. If the destination is a page or a portlet, then the appropriate information is displayed. In this case you can specify whether the information is to be displayed in the main window or in a completely new separate browser window. Page: This is a presentation interface, which at the same time displays several sources in different boxes. According to the layout of the page the boxes are arranged in one or more columns. Box: Rectangular area within a page, in which the interface of a portlets is displayed. A box has a title, which is shown in the header of the box, a description, a height and the reference to a portlet. No width is specified for a box. This width depends on the column, in which the box is placed on the page. Portlet: A portlet is a small information unit presentable in the portal. A portlet has a name and a description, which are important for locating the portlet. The reference to a master portlet specifies the backend system supplying the information. Dependent on the master portlet there are a number of additional parameters for the selection of the desired information; these can be specified individually. A portlet can be displayed alone in a window or in a box on a page together with other portlets. Master Portlet: A master portlet stands for a procedure to present data from a certain type of backend system in a Web interface (e.g. access to external web server, data base, mainframe). Each master portlet defines a certain set of parameters, which address the requested information in the backend system. (e.g. URL, SQL statement, mainframe application and user name). For its specific parameters the master portlet supplies an interface, where each user can enter the values of the parameters individually. Portal Page Thread: If, by clicking on a menu entry, a portlet or a page is called for representation within the main window, the special thread Portal Page is started, in order to display the desired information. In the selection menu the corresponding entry appears. After you have worked with other threads in the main window a click on the thread Portal Page within the selection menu will display the last requested portlet or the last started page again. The thread portal page is not started multiple times, so only the last page but no history can be fetched back Menus At first you have to specify your own menu entries, which you want to use to find your information later. In the upper frame on the right side there is an icon next to each menu. Click on this icon to edit the menu. When you first start the portal your menu will still be empty, so that only this icon is displayed at the right edge of the window. You will encounter the icon again wherever things can be adapted. Here it opens a new window for the definition of menu entries. In the header of the dialog you find two icons and, for confirming and/or canceling your changes. Click on the icon to insert a new menu entry. Seite 33 von 64

On the next page you can select a sub-menu, a page, or a portlet as a destination of the menu entry. You see here both your own contents and the contents other users released for your use.

For contents provided by other users you see the icon ; When moving the mouse cursor over this icon a, tool tip is displayed containing the name of the author. You cannot change such contents.

34 On the next page you can select a sub-menu, a page, or a portlet as a destination of the menu entry. You see here both your own contents and the contents other users released for your use. For your own contents an icon is displayed in the third column, which you can use to edit the characteristics of this resource. For contents provided by other users you see the icon ; When moving the mouse cursor over this icon a, tool tip is displayed containing the name of the author. You cannot change such contents. Here, you can create also new menus, pages and portlets. You create menus and pages, by entering a name and a description, selecting the radio button of the entry and confirming with. For portlets you have to use the icon to open a subsequent dialog, which defines the characteristics of a portlet. Seite 34 von 64

Enter name and description of the portlet, select the desired master portlet and enter your user specific data for the portlet (here e.g. a URL) and confirm with.

This name is taken from the selected action (sub-menu, page or portlet),; likewise the description of the entry is filled with the description of the destination.

35 Enter name and description of the portlet, select the desired master portlet and enter your user specific data for the portlet (here e.g. a URL) and confirm with. Then you will return to the main dialog. Now you see a new column for your new menu entry. In the header you will see the label of the menu entry. This name is taken from the selected action (sub-menu, page or portlet),; likewise the description of the entry is filled with the description of the destination.. You can change these defaults anytime, but changes here will only affect the menu entry itself, name and description of the addressed action remain unchanged. If you create several menu options in this way, the menu dialog may look as follows: Seite 35 von 64

You can change the sequence of the menu entries by dragging the columns with the mouse cursor. In addition the label and description can be specified again.

) Every menu entry has several icons in the row Action : With a new action for the menu entry can be defined, with or you specify for pages or portlets whether they are displayed in the main

36 You can change the sequence of the menu entries by dragging the columns with the mouse cursor. In addition the label and description can be specified again. (So far the name and the description of the destination of this menu entry were used.) Every menu entry has several icons in the row Action : With a new action for the menu entry can be defined, with or you specify for pages or portlets whether they are displayed in the main window of the portal or in a separate browser window, and with individual menu entries can be removed, but the destination (menu, page, portlet) is not removed along with the menu entry. If you finally confirm the menu definition with, the window is closed and the menu is displayed in the header of your portal interface Pages Seite 36 von 64

New pages are created when you create menu entries (see 2.2.1.3.

In order to fill the page with contents, you must first put the page into a menu and then call the menu

With the icon the header of the page you add a new box to your page.

37 New pages are created when you create menu entries (see ) or when you maintain your contents (see ). In order to fill the page with contents, you must first put the page into a menu and then call the menu entry. Several boxes, which each contain the interface of a portlet can be placed on a page. With the icon the header of the page you add a new box to your page. in With the icon in the title of the new box you can open a dialog for the settings of this box. Enter title and height of the box and create or select a portlet for the content of the box similar to creating menu entries. Seite 37 von 64

38 Once you have created several boxes, you should select a suitable layout for the page. Use for this the icon in the header of the page. Select a layout with suitable column number and width, confirm with the mouse cursor into the desired columns. and afterwards drag your boxes with Seite 38 von 64

2.2.1.3.4 Portlets During the adjustment of your menus (se 2.2.1.3.2) or pages (see 2.2.1.3.3) or the maintenance of the contents (see 2.2.1.3.6) you can create new portlets or modify their settings.

If you have very many portlets, it is recommended to add elements to define a structure to your names. In the field you can describe the contents of the portlet briefly.

39 Portlets During the adjustment of your menus (se ) or pages (see ) or the maintenance of the contents (see ) you can create new portlets or modify their settings. When doing so you will see the following dialog: Enter a name to identify the portlet later in your lists. If you have very many portlets, it is recommended to add elements to define a structure to your names. In the field you can describe the contents of the portlet briefly. This is particularly useful, if you want to make your portlet accessible to other users (see ), in order to inform them about the contents of the portlets. In the selection list Master you can select the desired master portlet. Depending on the selected master portlet you can define different data in the User area. Thus you specify your personal contents for this portlet Personalized Preferences In the information window on the top right next to the name of the user there is an icon for the change of the personal settings. A dialog with the most important interface options opens. Use the key Maintain Seite 39 von 64

contents to start a thread for the maintenance of personalized contents (see 2.2.1.3.6). The two selection lists let you set the desired language and the color pattern (style).

40 contents to start a thread for the maintenance of personalized contents (see ). The two selection lists let you set the desired language and the color pattern (style). In addition you can enter a URL of a personal picture as background for the information window. The key returns to the most recently stored settings. This affects language and style and all personal contents, menu structures etc. You should use this button only if you want to undo very many inadvertent changes when you adjust your contents. With the current settings are explicitly stored. Only pressing this key will store the settings permanently before the end of the session. Confirming dialog with will apply the settings for language, style and picture without storing them; however the settings are stored permanently at the end of the session. In all three cases the interface is displayed immediately according to the changed settings. In addition the published contents of other users (see ) are loaded once more and will also be available Contents maintenance and publishing Using the adjustment of the personal settings you can start a thread for maintaining of your own contents. All contents are displayed similar to the selection dialog during the menu settings. In contrast to the menu selection dialog however, only your own contents are displayed. You can create, adapt, and publish menus, pages, and portlets with this dialog. In order to create a menu or a page, you can write the name and the description into the first row in the section Menu and then click on the icon. To create a new portlet you should click on the icon in the first row in the section Portlets and enter the necessary data in the subsequent dialog (see ). You can adapt existing menus, pages, or portlets: To do so click the icon in the appropriate row and change the data in the subsequent dialog. In the third column you find the icon for all available menus, pages, and portlets. Pressing this icon you can open a release dialog, where you can release the contents to other users. If resources are released, then the icon will get a blue background. If you adapt released contents, this change is not published automatically. Instead background of the icon is switched to red, indicating that the released content is no longer valid. That allows you to test a content first, before you make the changed content accessible to other users by a renewed release. If you release resources for certain roles, then users, who have this role, can integrate these into their interface. If it is a menu or a page, then the user sees only the menu options and/or portlets, for which he also holds a suitable role. That means that you must release the contents addressed by the menu and/or the page too, so that other users can see them. This offers you the possibility of limiting the amount of the visible information for menus and pages role-dependently Pre-defined contents Contrary to all other users the administrator admin can release his main menu as Portal Menu. This released menu is then available to all other users role-dependently as left part of their main menu. This part Seite 40 von 64

41 then is a default for all users; it is already available during the first registration (log-in) and cannot be changed by personalizing. The administrator admin can add menu items to his main menu, which do not belong to him, but were published by other users. In this way contents from other users can also belong to the pre-defined contents. The administrator only puts the access on highest level into the main menu; the maintaining of contents remains the responsibility of the owners of the contents Administration The administrator(s) of the portal has to perform the following tasks: Creating and assigning users and roles Defining color patterns (styles) for the interface Translating and adapting messages For each of these tasks there is an corresponding role: administrator_user, administrator_style, administrator_language, the role administrator covers all these tasks. For the administrators there are buttons in the start menu according to their roles for starting the users administration, style administration and language administration User and roles The administration interface for users and roles is subdivided into four property sheets. Seite 41 von 64

For new users and after resetting of the password of an existing user, the password in the field at the bottom is used.

42 The users are administered on the first sheet. You can enter a name for a new user and by clicking of the button the user will be created. If you select a user from the list, you can remove the user with the button or you can reset the user s password with the button. For new users and after resetting of the password of an existing user, the password in the field at the bottom is used. The roles are administered in the second sheet. You can enter the name of a new role and by clicking the button the role is created. If you select a role from the list, then you can remove this role with. Seite 42 von 64

Similarly you can remove roles, if you click on an already selected role while pressing the control key.

43 You assign roles to users on the third sheet. To do so, select a user in the left list. Now some fields in the right list may be selected also. Those are the roles, which are already assigned to this user. Now you can add further roles in the right list. Click at the desired role with pressed control key. Similarly you can remove roles, if you click on an already selected role while pressing the control key. If you click on a role and then click on a second role with shift key held, then a sequential range of roles is selected. If you click on a role without pressing any key, then all roles with the exception of this one are deselected (caution!). The fourth sheet also serves for the role assignment. Here you proceed in reverse. Select a role in the left list. Now all users, who are representing this role, appear in the right list. As on the third sheet the roles you can change here the quantity of the assigned users. All changes made in the administration, are only temporary at first. Only by clicking the buttons or the changes are stored permanently. With the button the administration is also terminated Translating Messages Seite 43 von 64

44 With the button Administrate Language in the start menu you receive a thread, in which all messages are displayed in the current language. Use the icon to switch to another language or to define a new language for the portal. Enter the name of the language and confirm with. If the language is already available, the appropriate messages are loaded and displayed. If not, the messages of the current language are stored under the new name and will be displayed. In both cases you can continue immediately with modifying the messages. With you restore the messages stored last. With the icon you can apply the current messages to the interface without storing them. With you apply the messages and store them permanently at the same time. With you apply the message, store them permanently and leave the thread. You can enter a short name for the language in the header of the table. The system attribute LANGUAGE of WebTransactions is set to this value. This means for example, that the messages of WebTransactions will be displayed in this language Defining Interface Styles With the button Administrate styles in the start menu you start a thread, which displays all colors and background pictures in the current. Seite 44 von 64

45 Use the icon to switch to another style or to create a new style. Enter the name of the style into the field and confirm with. If the style already exists, the appropriate colors are loaded and displayed. If the style is new, then the colors of the current style are stored under this name and displayed. In both cases you can immediately continue with modifying the colors and background pictures. With you restore the settings stored last. With the icon you can apply your settings to the interface without storing them. With you apply the current settings and at the same time store them permanently. With you apply the current settings, store them permanently and leave the thread Properties The following properties can be changed via the Properties dialog of the WTBean. Property General Start Menu Templates Here you can set general properties of the interface like a the default language or the default style Here you can specify the height of the start menu. The default value is 250 (pixels). You can also define if the frames for the open threads and the possible threads should be located at the right/left side of the main window. An end template is defined here. This template is output at the end of the session (Terminate Session in the start menu). Here you can unload the frameset and terminate the session, for example. The possible threads are specified in a list. The following properties can be defined for the threads. Property Thread Name Label Startmenu Unique identifier used to identify this thread Text for the button that represents the corresponding thread. This text is used in the start menu and in the selection menu. The labels used in the selection menu can be changed individually for each started thread using the attribute wtc_framebuttonlabel If Startmenu was selected, a button for this thread is displayed in the start menu, otherwise the button for Seite 45 von 64

46 PC PocketPC Role Multiple Start Template Key Template this thread is not displayed in the start menu If this option is switched on the thread is shown, if the portal was is displayed on a PC If this option id switched on the thread is displayed, if the portal runs on a Pocket PC. If a role was selected, then the button for this thread is displayed only for that role. If function was selected, then the return value of the function wtcframe_allowconversation decides if the button for this thread is displayed. If Multiple was selected, then this thread can be started several times in parallel, otherwise this thread can only be executed once at a time Here you specify a start template with which the first page of a new thread of this type is created Template fort he Footer-Frame that is automatically displayed, when the thread is displayed on a pocket PC The order of the buttons of the individual threads in the start menu depends on the order of the threads in this list (see 1.6 Lists). If you want to change their order in the start menu, then you must sort this list accordingly. If you want to add a new thread to the list, then please note that empty callback methods are generated. In particular, when you want to define a thread with HOST communication, then you must complete this callback method by adding the appropriate code (see the $DIALOG thread) Methods and Functions There is a global callback method to control the display of the buttons for threads. Callback method wtcframe_allowconversation(classname) If function is selected for the parameter role, then this method controls the display of the thread buttons. The parameter for this method is the current name of the class of the thread. The following methods are defined for each thread (dialog object) of the wtcframe object. These methods are callback methods that are called for certain actions and whose bodies are accessible as wtcblocks and can therefore be edited or modified to meet the requirements of the corresponding thread. These methods are available for every thread after a new thread has been defined. Callback method wtcframe_constructor() wtcframe_finalize() wtcframe_activate() wtcframe_passivate() wtcframe_handlebrowserresponse() Constructor for a dialog object; only for initialization of attributes of the dialog object; methods must be called using a prototype (see the TestThread thread) This method is called when the dialog object is deleted (see the TestThread thread); any cleanup actions of the thread are performed here, for example This method is called, for example, when the initialization of the thread is performed for reactivation; for example, you can restore the previously saved values of the WT_POSTED object This method is called when the dialog object is deactivated (see the TestThread thread); for example, actions to be performed after switching threads are defined here; for example, you can save the values of the WT_POSTED object here This method is called after the reply from the browser is received (see the TestThread thread); you may use the functions described below to control the dialog here In addition there are two wtcblocks for the methods and prototypes of the methods. WtcBlock Examples Seite 46 von 64

47 Methods Area for methods function mymethod() { } Prototypes Area for prototypes wtcframe_constructor.prototype.mymethod = mymethod; The following functions are used to control the individual threads (dialog objects) within wtcframe. These global functions are defined in the file wtcframe_prolog.htm. Function wtcframe_opennewthread(wtcframe_dlgobj) wtcframe_setactivethread(n) wtcframe_getactivethread() wtcframe_removeactivethread() wtcframe_numberofthreads() wtcframe_activateactivethread() wtcframe_passivateactivethread() Creates a new thread with the dialog object wtcframe_dlgobj and activates this newly created thread Thread n is activated The dialog object of the active thread is returned The active thread is deleted The number of currently open threads is returned Activates the active thread Deactivates the active thread All these functions affect the control of the dialog except for wtcframe.getactivethread(). To guarantee smooth interaction with the processing control performed using the start menu and selection menu, these functions may not be used at arbitrary locations (for example in the start template of a thread). The control functions may only be called in the callback method wtcframe_handlebrowserresponse() Files The following files are components of the WTBean wtcframe. Files file for the WTBean wtcframe.wtc Files for controlling the threads wtcframe_prolog.htm wtcframe_cmdfields.htm wtcframe_epilog.htm General files for any threads wtcframe_end.htm file for the WTBean wtcframe. The global methods for controlling the threads are defined here. This template is used to the control the threads (dialog objects). The wtonreceive rules that control the thread are defined here. This end template is loaded at the end of the wtcframe session, and you have the ability to start another new wtcframe session here. It is possible to set up the end template via the properties dialog of the WTBean (see the table of properties). Every thread template that is displayed in the main window must contain the following components: the wtcframe_prolog.htm must be included at the beginning of the template, the template must contain a "FORM WEBTRANSACTIONS" and these forms must include the template wtcframe_cmdfields.htm. At the very end, after the last wtonreceivescript, the template must include wtcframe_epilog.htm. The templates generated from version 4.0 upwards (automask, templates created with "Capture" and master templates) are already prepared accordingly. You only need to define the PROLOG, FORMTPL and EPILOG attributes of the communication-specific system object, and to be more precise, using the corresponding name of the wtcframe_prolog, wtcframe_cmdfields and wtcframe_epilog templates. Seite 47 von 64

48 The following files implement some sample threads and are always included in the software package. You can modify these files to meet your requirements. Files Files for the sample Test thread wtcframe_example.htm wtcframe_examplehelp.htm Files for the "empty" sample thread mythread wtcframe_startmythread.htm Files for the sample thread $DIALOG wtcframe_startas400.htm wtcframe_startmvs.htm wtcframe_startosd.htm wtcframe_startunix.htm wtcframe_error.htm wtcframe_disconnect.htm This is the start template of the Test thread. This template is a thread template of the Test thread. This is the start template of the thread mythread. This template is a sample template to demonstrate the layout of a template for use in a wtcframe thread. You can use this template as a model for the templates you write yourself. This template opens a connection to a AS400 application. Adapt the WTBean in this template with the parameters of the application. The template AutomaskAS400.htm is used to display the first screen of the host application. Therefore the base directory must have been created for the communication with AS400. You can use this template as a start template for the thread $DIALOG or a copy of that thread This template opens a connection to a MVS application. Adapt the WTBean in this template with the parameters of the application. The template AutomaskMVS.htm is used to display the first screen of the host application. Therefore the base directory must have been created for the communication with MVS. You can use this template as a start template for the thread $DIALOG or a copy of that thread This template opens a connection to a OSD application. Adapt the WTBean in this template with the parameters of the application. The template AutomaskOSD.htm is used to display the first screen of the host application. Therefore the base directory must have been created for the communication with OSD. You can use this template as a start template for the thread $DIALOG or a copy of that thread This template opens a connection to a UNIX application. Adapt the WTBean in this template with the parameters of the application. The template AutomaskUNIX.htm is used to display the first screen of the host application. Therefore the base directory must have been created for the communication with UNIX. You can use this template as a start template for the thread $DIALOG or a copy of that thread This template demonstrates the way error messages of WebTransactions can be handled by the thread $DIALOG. To do so in the start template of the thread wtcframe_startosd. $DIALOG, the output of communication errors is switches off and the corresponding call-back functions of the thread the $DIALOG are adjusted. This template is used as the Disconnect-Template for connections in the templates wtcframe_startas400.htm, wtcframe_startmvs.htm,. wtcframe_startosd.htm and wtcframe_startunix.htm. The thread $DIALOG tests in the function wtcframe_handlebrowserresponse, if this template had been activated. In this case the thread is terminated immediately Instructions for using wtcframe You must carry out the following steps to design the interface of your application using the WTBean wtcframe. 1. Create a base directory Create a new base directory with the WebLab function Generate->Base Directory. The usage of wtcframe needs the HTTP host adapter, which you must select when creating the base directory. If you want to use the demo thread for the OSD connection, you must select additionally the host adapter OSD. You can also add the adapters to an existing base directory later, by creating this base directory once more with the WebLab function ( Generate->Base Directory ). 2. Generate wtcsinglesignon For the user and role administration the WTBean wtcsinglesignon is used and required. Insert the WTBean wtcsinglesignon (see ) and enter as starting template and administration template the names defined by the next step. Seite 48 von 64

49 3. Create a start menu Create a stand-alone WTBean of type wtcframe (see 1.2 Stand-alone WTBeans) in your base directory. Enter a file name for the WTBean (for example config/forms/frame.htm). This template will be the start template for the entire application later on. You specify the style of the interface in the optional, general settings for the WTBean, i.e. you can specify the color of the buttons, the size of the start menu, the size of the buttons, etc. You can use the default settings at first and then subsequently change these settings (see 1.5 Properties). 4. Specify the threads Now specify the different threads. To do this, open the list of threads of the wtcframe "WTBean" created in section 1 (see 1.6 Lists). You will find 3 threads: mythread, $DIALOG and Test. These examples are explained below, and you can change or delete them. You can also add new threads. To do this, move the mouse onto the green title bar of the list, activate the context menu with the right mouse button and select 'Edit List'. You create a new list entry and set the following parameters in the dialog box for changing or adding threads. (Note: If you mark a list entry (Click on the arrow in the first column of the list) before you click at the add button, the marked entry is copied and you have to modify the values only. The callback methods are copied also. If you want to establish e.g. a thread for BS2000 communication, mark the thread $DIALOG. Then you have to change only the name and description and the name of the start-template and then you have to create the start-template with this name.) Use a unique identifier as the thread name for this list. In Label you specify the text that will be shown on the button in the start menu or in the selection menu for the thread. In Display you specify if a button is to be shown for this thread in the start menu. In Role you specify if a button for this thread is displayed only for that role. In Multiple you specify if the thread can be started several times in parallel. In Start Template you specify a template that will be used to create the first page of a new thread of this type. Once you have completed this list, 7 wtcblocks are created for each thread type (see Methods) in which you write the statements used to control your thread. In many cases you can simply leave these blocks empty. However, you can also define initialization values, cleanup tasks and special dialog controls here. The sample Test thread demonstrates this ability (cleanup functionality when the session is closed; implicit thread termination when a connection is lost) and you will understand how to initialize threads, implicitly start other threads or terminate them, for example. The sample thread $DIALOG shows a thread with host communication (detailed explanation in section ). If you want to change the labels of the buttons in the selection menu, then the property wtcframe_buttonlabel should be used. You can set it in the constructor of the thread (first block out of seven) as in the following example: this.wtcframe_buttonlabel = 'Vorgang '+ (WT_SYSTEM._myThreadCount? ++WT_SYSTEM._myThreadCount : WT_SYSTEM._myThreadCount=1); You can also change the label in the start-template of your thread. Use for it the method wtcframe_getactivethread : wtcframe_getactivethread().wtcframe_buttonlabel = 5. Create the templates Each thread template that is shown in the main window must contain the following components: the wtcframe_prolog.htm must be included at the beginning of the template, the template must contain a "FORM WEBTRANSACTIONS" and these forms must include the template wtcframe_cmdfields.htm. At the very end, after the last wtonreceivescript, the template must include wtcframe_epilog.htm. All templates generated from version 4.0 upwards (automask, templates created with "Capture", master templates) are already prepared accordingly. You only need to define the PROLOG, FORMTPL and EPILOG attributes of the communication-specific Seite 49 von 64

50 system object, and to be more precise, using the corresponding name of the wtcframe_prolog, wtcframe_cmdfields and wtcframe_epilog templates. Copy the template wtcframe_sample.htm, for example, and save this file under the name that you specified as the start template for your thread. Your start template is now created, and since the template wtcframe_sample.htm must already fulfill the conditions specified above, the template wtcframe_sample.htm can be used as a model for the templates in your thread. Specify your interface and your receive scripts in the appropriate area (denoted by the following lines in your start template): <wtrem>******************************************************************** Place your page contents and wtonreceivescripts here. *******************************************************************</wtrem> 6. Start you your thread Start a session using the stand-alone WTBean as a (session) start template (for example config/forms/frame.htm). You then start your thread using the corresponding button for your new thread in the start menu. The WTBean can manage many such threads. These threads are started by selecting them in the start menu, and the current page of the thread is then shown in the main window. In the main window you can enter general data and go from screen to screen in the thread. It is possible to switch at any time to another thread. The current screen for this thread will then appear in the main window. The thread can be terminated with the 'Cancel' button in the start menu. The session is terminated with the 'End Session' button in the start menu Examples $DIALOG thread Here are short descriptions of the templates that are important for this thread. 1. The start template wtcframe_startosd.htm Since this start template was originally created from a wtcstartosd WTBean, you can change the settings for the communication object in this start template (see 1.5 Properties). The following settings were changed for this thread in the start template: OSD connection parameters Three properties were changed here: A unique, user-defined character string can usually be specified as the name for the communication object. However, if the same communication name were to be used for threads that can be started several times in parallel (see Properties) then conflicts would result. The character string OSD_$ is used here to dynamically create the name of the communication object to avoid these conflicts. In this case the name OSD_0 is created as the name of the first communication object. If another communication object is created in parallel to the first, then this communication object is assigned the name OSD_1. Generally, the part of the name represented by the dollar sign is replaced by the first natural number not yet used for a communication name (including the number 0). For host applications the name of the application is used, for example $dialog here. The symbolic name (or IP address) of your computer is to be specified as the name of the host computer. This is the only change you need to make in order to successfully start this thread on your computer. WT_SYSTEM attributes One attribute was changed here: Seite 50 von 64

51 The 'Disable messages for communication errors' option was activated because no messages are to be generated by WebTransactions for communication errors and the error template wtcframe_errorosd.htm is to be loaded instead. Other options Several properties were set under Templates: The 'Automask' attribute was set to the value wtcframe_automaskosd.htm. This template was created with the WebLab function 'Create Automask', and the reference wtcosd_host was specified as the name of the communication object. In this manner this template can be used for all communication objects that support this reference. The 'Terminate Connection' attribute was set to the value wtcframe_sampleosd.htm. This value is then used in the thread method wtcframe_handlebrowserresponse() to decide if the thread is to be terminated. The 'Prolog Control' attribute was set to the value wtcframe_prologosd.htm. This ensures that all WebTransactions V4 templates (see above) satisfy the condition stipulating that the template wtcframe_prolog.htm is to be included in all thread templates. The 'Form Control' attribute was set to the value wtcframe_cmdfieldsosd.htm. This ensures that all WebTransactions V4 templates (see above) satisfy the condition stipulating that the template wtcframe_ cmdfields.htm is to be included in all thread templates. The 'Epilog Control' attribute was set to the value wtcframe_epilogosd.htm. This ensures that all WebTransactions V4 templates (see above) satisfy the condition stipulating that the template wtcframe_epilog.htm is to be included in all thread templates. 2. The start menu The following callback methods for this thread with host object communication were changed in the file that represents the stand-alone WTBean wtcframe (see above: for example config/forms/frame.htm),. Method: wtcframe_finalize() Since this method is called at the end of the thread, this method ensures that the communication object of this thread will be terminated. The typeof operator determines the type of the this.comm operand and returns the result as a string. If the comm attribute for this dialog object (the 'this' reference) contains a WTML object of type 'object', then this object is the communication object of the thread because the comm attribute was created in the start template of the $DIALOG thread after a communication object was created with 'New WT_Communication()', and the comm attribute was then finally initialized with a reference to the communication object just created. The close() method of the communication object is then called to close the connection since the thread is to be closed. if( typeof this.comm == 'object' ) this.comm.close(); Method: wtcframe_activate() This method is called when the corresponding thread is activated. The comm attribute for this dialog object (this) is stored as a wtcosd_host attribute of the host root object WT_HOST in addition to all other communication objects (one communication object per started $DIALOG thread). The attribute wtcosd_host is then also used by the template wtcframe_automaskosd.htm and must be used by all templates created with 'Capture' by specifying the character string wtcosd_host as the communication name. WT_HOST.wtcOSD_host=this.comm; Method: wtcframe_handlebrowserresponse() This method is called after the reply from the browser appears. The thread is terminated with the function wtcframe_removeactivethread() if a communication error occurs or if the FLD attribute of the system object WT_SYSTEM was set to the character string wtcframe_sample.htm. Since the 'Disable messages for communication errors' option was activated, no error messages are generated for communication errors (see the manual), and an error template is loaded instead (see Seite 51 von 64

52 the forward("wtcframe_errorosd.htm") statement in the start template wtcframe_startosd.htm). A button is provided at the end of the thread in the wtcframe_errorosd.htm error template. This Submit button is named endwitherror, which is 'posted' to WebTransactions when the button is pressed. This allows WebTransactions to be informed that the thread is to be terminated. The WT_POSTED attribute endwitherror can now be queried in the thread method wtcframe_handlebrowserresponse(). If the attribute exists, the thread is finally terminated with wtcframe_removeactivethread(). The thread should also be terminated, however, when the character string 'wtcframe_sample.htm' is stored in the FLD attribute of the connection-specific system object WT_SYSTEM referenced by the comm attribute of the communication object of this thread ('this') (the template wtcframe_sample.htm is not loaded in this case, rather the name of the template is only used as an identifier; any other character string could be used instead). This is the case, for example, after a controlled disconnection because the DISCONNECT attribute also contains the character string wtcframe_sample.htm (see the DISCONNECT attribute in the start template wtcframe_satrosd.htm). Just to be sure, a check is conducted in this case to see if the communication object of the current thread is present (this.comm) and if the connection-specific system object WT_SYSTEM (this.comm.wt_system) is also present. The function wtcframe_removeactivethread() is also executed in the case of a controlled disconnect. if( WT_POSTED.endWithError ( this.comm && this.comm.wt_system && this.comm.wt_system.fld=='wtcframe_sample.htm')) { wtcframe_removeactivethread(); } 3. The automask template wtcframe_automaskosd.htm This file was generated as an automask file. It is based on the communication object wtcosd_host. This variable is created in the start template wtcframe_startosd.htm during the generation of the communication object and contains a reference to the communication object created in the start template. 4. The error template wtcframe_errorosd.htm The template wtcframe_errorosd.htm demonstrates the handling of error messages from WebTransactions in the $DIALOG thread. Messaging for communication errors was disabled in the start template wtcframe_startosd.htm of the $DIALOG thread (see above). The template is loaded when a communication error occurs (see the start template: forward( wtcframe_errorosd.htm )) and also outputs the ERRORLIST attribute of the system object WT_SYSTEM that contains the error messages. Finally, you have the choice of terminating this thread or starting a thread. 5. The master template wtcframe_osd.wmt The master template, which is the same as the master template OSD.wmt but with an additional background image in the BODY tag. This master template can naturally be changed to meet your requirements and can be used for 'Capture', for example. An automask template and all generated templates can also be created with this master template. Of course you can also modify this master template to meet the requirements of your application Test Thread The important templates for this thread will be described here. 1. The template wtcframe_example.htm This template is the start template of the thread Test-thread. The start template contains the following interface elements: Seite 52 von 64

53 An index number that uniquely identifies a thread of this type is output In the 'Index of this Test thread' area. This number is created or assigned in the constructor method wtcframe_constructor() (see section 3 below), stored in the object WT_SYSTEM as a _numberofexamplethreads and then saved as an indexofthread property of this thread (dialog object). A number is output in the 'Number of running Test threads' area that specifies the number of threads of this type currently running. This number is created or assigned in the constructor method wtcframe_constructor() (see section 3 below) and stored in the object WT_SYSTEM as the numberofrunningexamplethreads. This variable is then decremented by 1 in the finalize method wtcframe_finalize() because a running thread was terminated. You can select an action in the 'Next Action' area. You switch to this help page with Help. The Continue button performs a step in the dialog of the thread. You start and transfer control to a new test thread with New Thread. Delete History deletes the history display at the bottom of the page. The current test thread is terminated with Terminate. (see section 3 below). You can determine if the thread was terminated by the function wtcframe_removeactivethread() during the 'Terminate' action and if a new thread was started with the function wtcframe_opennewthread() during the 'New Thread' action in the thread method wtcframe_handlebrowserresponse(). A history of the actions performed is displayed in the Previous Action' area. The actions last executed are at the top. To do this, an array is created in the constructor method wtcframe_constructor() in which your actions are recorded using the unshift() array method. The thread methods insert log information here regarding the fact that they were called. 2. The template wtcframe_examplehelp.htm This template is used to display help information when the 'Help' button of the Test thread is pressed. 3. Thread methods The thread methods of the Test thread are listed here again. A short description of the statements of this method can be found in section 1 above. wtcframe_constructor() Seite 53 von 64

54 // create/increment counters for total/running test threads WT_SYSTEM._numberOfExampleThreads = ( WT_SYSTEM._numberOfExampleThreads 0 ) +1; WT_SYSTEM._numberOfRunningExampleThreads = ( WT_SYSTEM._numberOfRunningExampleThreads 0 ) +1; // store index and empty history to dialog object this.indexofthread = WT_SYSTEM._numberOfExampleThreads; this.actionlist = new Array; this.actionlist[0] = 'started'; wtcframe_finalize() // decrement counter for running test threads WT_SYSTEM._numberOfRunningExampleThreads--; wtcframe_activate() // write activation message to history this.actionlist.unshift('activated'); wtcframe_passivate() // write passivation message to history this.actionlist.unshift('passivated'); wtcframe_handlebrowserresponse() switch(wt_posted.action) { case 'terminate': // remove thread and switch to next active thread if any wtcframe_removeactivethread(); break; case 'new thread': // save reference to current thread previousthread = wtcframe_getactivethread(); // create and switch to new thread wtcframe_opennewthread(new WT_SYSTEM._wtcFrame_DlgClasses.testThread()); wtcframe_getactivethread().actionlist[0]='started by thread '+previousthread.indexofthread; break; } The mythread thread This is an 'empty' sample thread. An 'empty' thread means that the thread methods (wtcframe_handlebrowserresponse(), for example) are empty and do not contain any statements. You can use this thread as a starting point for your new thread, for example. The template important for this thread is described below. The template wtcframe_startmythread.htm This template is the start template of the thread mythread. You can modify this for your thread (corresponds for the most part to the template wtcframe_sample.htm). Seite 54 von 64

55 2.2.2 wtcactiveportal This WTBean supports the integration of a WebTransactions session into TIBCO s ActivePortal. It creates a HTML start page for a WebTransactions application with a cookie-based recovery. Important: You must add the following line to all your templates to transport the recovery information to the browser: <wtinclude name="wtcrecover_update"> Properties The following properties can be changed via the Properties dialog of the WTBean. Property Object Name WTPublish/WTCluster Session ID Domain Coupler Basedir/ClusterID Start Template Name of the JavaScript object to be created You specify with this parameter if a cluster session is to be used instead of a normal WebTransactions session. The Session ID property is a user-defined character string that identifies the session for the recovery procedure. The names of the cookies contain this identifier as part of their names. In this manner it is possible for several sessions (possibly of the same type) to maintain recovery information in parallel. The identifier can consist of letters, numbers and underscores. The Domain parameter specifies the domains in which the server used is to be found. The server with the start page and the server with the WebTransactions application or the members of the cluster must all be located in the same domain. If the start template and application are located on the same server, then an empty string can be specified here. The Coupler parameter defines the path to the WTPublish.exe or WTCluster.exe program. The WTPublish base directory is specified for this property or, if WTCluster was selected, the cluster identifier is specified here. The Start Template parameter designates the start template. The following properties can only be changed using the list elements of the WTBean. Property Name Value If additional data is to be sent at the start of the session, the name of a name/value pair that is to be added to your URL object can be defined here. If additional data is to be sent at the start of the session, the name of a name/value pair that is to be added to your URL object can be defined here Methods There are also two wtcblocks for HTML statements. wtcblock BEGIN END HTML block at the beginning of the start page. You can modify the start page here. HTML block at the end of the start page. You can modify the start page here Files The following files are components of the WTBean wtcactiveportal. Files wtcactiveportal.wtc file of the WTBeans wtcactiveportal. wtcactiveportal_exittemplate.htm Template, used to end a session. It removes the information stored for recover. The contents between <BODY> and </BODY> can be changed at will Instructions for using wtcactiveportal You must perform the following steps in order to integrate a WebTransactions session into TIBCO/ActivePortal with recovery. 1. Create the start page Create a standalone WTBean of type wtcactiveportal in your home directory (WebTransactions base directory). Seite 55 von 64

56 Enter a file name for the WTBean (for example wwwdocs/html/portal.htm). This template is then the start page for your application later on. You specify the following properties under the general settings for the WTBean (see 1.5 Properties): Specify a unique identifier as the Object Name. You specify which CGI coupler program you want to use with WTPublish/WTCluster. You specify a character string for recovery with Session ID. The optional Domain parameter specifies the domain of the server used. You specify the name of the CGI program and the corresponding URL prefix with Coupler. The Basedir/ClusterID parameter defines your WebTransactions base directory or a cluster identifier when you want to work with WebTransactions clusters. You specify the Start Template of your application here. Your start page is created when this Properties dialog is confirmed. 2. Provide restart information in the templates The following statement must be added for recovery purposes at the end of each template in which recovery is to be made possible: <wtinclude Name="wtcRecover_update"> You can also include this statement into the master-template. Then all generated templates will have contained this statement. Please use the template wtcactiveportal_exittemplate.htm for clearing the cookies. If you are using a WTBean (for example wtcstartosd) for creating a start template, you have to enter this exit-template at the parameter Disconnect. If you are using the WTBean wtcstartutm or if you are not using any WTBean, then you can control your dialog steps by: setnextpage(' wtcactiveportal_exittemplate.htm'); This statement will exit your session by loading the template wtcactiveportal_exittemplate.htm and it also clears your recovery cookie. 3. Create a layout template for the WebTransactions session The,layout template consists of one HTML-Tag: <IFRAME SRC= wtcactiveportal_user=%%_user%%&wtcactiveportal_servleturl=%%servleturl%% &wtcactiveportal_subscriptionid=%%subscriptionid%%" width="100%" height="500"> </IFRAME> Important: the attribute src must have no word wrap The attribute src is to be specified as the start page (for example Portal.htm). The <virtualpath> parameter is the character string you specified in the WebTransactions administration as the virtual path to the directory in which you created the base directory for your application. You should also enter the width and height parameter of the iframe tag. This ensures that no scroll bars will be displayed. You should also change your start page in order to fit in with a pane of TIBCO s PortalBuilder. 4. Create a category (TIB /PortalBuilder ) Create a category for your start page ( layout template). If you have created a new layout template, please keep in mind to call the function Recache Portal, to be displayed in the selection list. Please set the refresh ratio to zero in order to avoid unauthorized usage of the current WebTransactions session. Allow this category only in panes with an appropriate width. 5. Test the restart function Start the portal, perform a login and choose the WebTransactions category. Step into your application beyond the start page. Minimize and restore the WebTransactions category. The content of your dialog must be restored correctly. 6. Possible causes of error Check to make sure that the wtcactiveportal_update.htm template is included in all thread templates, even in the template in which you terminate your session. Check to make sure that the start page is not loaded from the cache (browser or proxy cache). Seite 56 von 64

57 Check to make sure that the cookie stored on your computer was not deleted during an earlier, improper program termination before you load the start page wtcsinglesignon This WTBean wtcsinglsignon allows you to perform a single sign on. That means you have to enter your logon and password only once. Then all other performed tasks will use this authentication. Addintionally wtcsinglesignon supports the session roaming of WebTransactions, that means if a client should crash or you wish to change the end device, a renewed login will continue the running session. The log-in data will be evaluated by a WebTransactions service, which will only start a session if the authentication was successful. Therefore only registered users can start a new session Properties The following properties can be changed via the Properties dialog of the WTBean. Property Administrator Template Default Template Coupler Basedir/ClusterID User Login Anonymous Login This template defines the initial start template for the role administrator. The default value is wtcsinglsignon_admin.htm, which start the administration of users. This template defines the initial start template for an user who is not administrator or whose role does not define a specific template. The default value is wtcsinglesignon_user.htm. URL of the coupler program (generated by WebLab). Base directory or cluster-id (generated by WebLab). The users will be allowed to create new login accounts. Anonymous login is enabled Methods and Functions The following functions and methods are used to control the user administration. They are located within the file wtcsinglesignon_mgmt.htm. You can use them to create your own user administration or to enhance the default user administration. Function wtcsinglesignon_getallusers() wtcsinglesignon_newuser(user,pwd) wtcsinglesignon_deleteuser(user) wtcsinglesignon_getroleusers(role) wtcsinglesignon_getallroles() wtcsinglesignon_addrole(role) wtcsinglesignon_deleterole(role) wtcsinglesignon_getroles(user) wtcsinglesignon_adduserrole(user,role) wtcsinglesignon_deluserrole(user,role) wtcsinglesignon_getuserinfo(user,pwd) wtcsinglesignon_chnguserpwd(user,oldpwd,newpwd) wtcsinglesignon_writeuserinfo() wtcsinglesignon_isuserexisting(user) Lists all users Adds an user Deletes an user Lists an user for a specified role Lists all roles Adds a role Deletes a role Lists all roles for a specific user Assigns a role to an user Deletes an user from a list of roles Checks a password and sets specific attributes of WT_SYSTEM Changes the password of a specific user Saves the attributes of WT_SYSTEM into the file Checks whether a user account is already existing Files The following files are components of the WTBean wtcsinglesignon: Files wtcsinglesignon.wtc wtcsinglesignon_signon.htm wtcsinglesignon_pdasignon.htm wtcsinglesignon_mgmt.htm wtcsinglesignon_admin.htm wtcsinglesignon_admine.htm wtcsinglesignon_startroaming.htm wtcsinglesignon_dosignon.service file for the WTBean wtcsinglesignon. Login page for the PC (in wwwdocs/html) Login page for PocketPCs (in wwwdocs/html) This template defines a set of WT-Script functions belonging to this WTBean. A template for administering users and roles. Last template of the administrator session Roaming template to support restart of a session Service-template used for user authentication Seite 57 von 64

58 wtcsinglesignon_user.htm.roles admin.dat An empty template. A file for administering roles the default role is administrator for the default user admin. A file for additional information for this WTBean. The default value is the password admin for the default user admin Instructions for using wtcsinglesignon You must perform the following steps in order to use this WTBean for authentication with WebTransactions. 1. Creating a start page Create a stand-alone WTBean of the type wtcsinglesignon in your base directory. Enter a file name for the WTBean(e.g. wwwdocs/html/singlesignon.htm). This HTML-page is he the start page for your application later on. Define a start template for users belonging to the role administrator and a second one for all other users. If you use the wtcsinglesignon-wtbean in combination with wtcframe, you have to enter in both cases the template created by wtcframe. 2. Starting the administration Open the newly created start template in the browser. Login as user admin (password admin ). For security reasons you should change the password of the user admin. To do so select the option Passwort ändern and enter a new password. Auf der Seite Benutzer können Sie neue Benutzer definieren oder schon definierte Benutzer aus der Verwaltung löschen. On the page Rollen you can define new roles or remove existing ones. On the page Rollenzuordnung you can review and change the roles of a user. When you click on a user in the left list, the roles of this user will be selected in the right list. To change the role select in the right list all the roles the user should get. On the page Bdenutzerzuordnung can review and change the users belonging to a role. When you click on a role in the left list, the users belonging to this role will be selected in the right list. To change the users select in the right list all the users that should belong to this role. All changes are saved, when you click on the button Übernehmen. Zurücksetzen will discard all changes. You can terminate the administration using the button Abmelden, changes will not be stored. 3. Developing a single sign on application with WebLab The WTBean wtcsinglesignon handles the authentication, starts a new or connects to an existing session, loads in the session all user specific data and switches to the start template configured for the role the user belongs to. If you want to start from WebLab a similar session during development and test, you have to carry out the following steps: When starting the session from WebLab enter wtcsinglesignon_startroaming.htm as start template. This template executes the log in using the additional start parameters. Press Additional Start Parameters and supply the following parameters: Parameter WT_ADMIN_TEMPLATE WT_START_TEMPLATE WTUser WTPwd Specify the template you want to display, when a user belonging to the role administrator is logged in. This parameter corresponds to the property Administrator Template in the property dialog of the bean Specify the template you want to display, when a user not belonging to the role administrator is logged in. This parameter corresponds to the property Start Template Template in the property dialog of the bean. Specify the user for which you want to test the application. This parameter corresponds to the field Benutzer in the start page created by the WTBean. Specify the password fort he user. This parameter corresponds to the field Passwort in the start page created by the WTBean. Seite 58 von 64

59 Additional Templates User specific information for applications In order to avoid multiple logins, you have to supply some additional user specific information used by applications controlled by WebTransactions. That information is accessible within WT_SYSTEM.wtcSingleSignOn after authentication. For every application there should be an object under WT_SYSTEM.wtcSingleSignOn (see below). Every single information for a specific application is defined as an attribute of this object. For example: WT_SYSTEM wtcsinglesignon TRAVEL NAME Password DIALOG Login Pwd account number For an initial setup for this information, you can create a temporary template which creates a object wtcsinglesignon under the object WT_SYSTEM and which creates the user specific information too. The function wtcsinglesignon_writeuserinfo() enables you to save the user specific information in a file. The following WT-script shows an example: WT_SYSTEM.wtcSingleSignOn.TRAVEL = new Object(); WT_SYSTEM.wtcSingleSignOn.TRAVEL.Name = hugo ; WT_SYSTEM.wtcSingleSignOn.TRAVEL.Passwort = secret ; wtcsinglesignon_writeuserinfo(); Access to user specific information The following attributes are also accessible for user specific actions after authentication: - WT_SYSTEM.WTUser Name of the current user - WT_SYSTEM.WTPwd Password of the current user - WT_SYSTEM.WTRole Roles of the current user (concatenated with blanks) - WT_SYSTEM.wtcSingleSignOn User specific information Seite 59 von 64

60 2.2.4 wtcterminal The WTBean wtcterminal provides an improved terminal view to OSD, MVS and AS400 host applications. Special features of the wtcterminal automask are : Improved function key panel with controls for font and color settings Automatic font resizing Optional block cursor Preferences for nil character simulation and overwrite mode Together with WTBean wtcsinglesignon (s.2.2.3) all settings are saved for each user logged on. If wtcterminal is used with WTBean wtcframe (s.2.2.1) these settings are even saved separately for each thread. In addition the portlet connecthost is enhanced with the host type OSDclassic (s ). By using it every portal user can create his own BS2000 connection with improved terminal functions inside the portal Properties The WTBean wtcterminal has no properties. When created only a message box showing the usage pops up Methods and functions The WTBean wtcterminal offers no methods and functions. All settings are configured with the settings page Files Following files are components of WTBean wtcterminal: Dateien wtcterminal.wtc Beschreibung Beschreibungsdatei des WTBeans wtcterminal. Seite 60 von 64

wtcterminal_automask.htm wtcterminal_keysosd.htm wtcterminal_keysmvs.htm wtcterminal_keysas400.htm wtcterminal_configcolortableline.htm wtcterminal_configdialog.htm wtcterminal_configinlinematrix.

61 wtcterminal_automask.htm wtcterminal_keysosd.htm wtcterminal_keysmvs.htm wtcterminal_keysas400.htm wtcterminal_configcolortableline.htm wtcterminal_configdialog.htm wtcterminal_configinlinematrix.htm wtcterminal_configmatrix.htm wtcterminal_configsettings.htm wtcterminal_configstylereload.htm wtcterminal_default.css wtcterminal_autocharsize.htm wtcterminal.wmt OSDclassic.htm Automask template for OSD, MVS or AS400. Dieses This template must be assigned to the communication attribute AUTOMASK. Function key panel wtcterminal_automask.htm Templates for the settings dialog Cascading Stylesheet for standard color settings Functions for automatic character resizing Mastertemplate for captured screens with wtcterminal style Portlet for WebTA portal wtcframe Instructions for the use of wtcterminal Activation After the WTBean is created in the application directory only wtcterminal_automask.htm has to be configured as automask template for the communication. If a communication WTBean is used this acn simply be done with the WTBean dialog: Function key panel Modify settings Resize font to autmatically fit host screen into window reload screen from host (Refresh) terminate connection to host use a smaller font use a larger font set font size to particular point size print a hardcopy reset form Seite 61 von 64

2.2.4.4.3 Settings page With the button the settings page is called: Anmeldeinformationen (logon data) There are three boxes available to store frequently used logon data for a user.

62 Settings page With the button the settings page is called: Anmeldeinformationen (logon data) There are three boxes available to store frequently used logon data for a user. This data can be used in a start template of a host communication to do an automatic signon. The object names depend on whether wtcterminal_automask.htm is used as a stand alone feature or inside a thread of wtcframe (additional path dlgclasses.thread, where thread is the nameof the wtcframethread): WT_SYSTEM.wtcSingleSignOn.wtcTerminal[.dlgClasses.thread].kennung WT_SYSTEM.wtcSingleSignOn.wtcTerminal[.dlgClasses.thread].passwort WT_SYSTEM.wtcSingleSignOn.wtcTerminal[.dlgClasses.thread].account Not available if used with portlet connecthost. Copyright by Fujitsu Technology Solutions, 2009 All rights reserved

63 Anzeige (Display) Import Nilzeichen (nil characters) (only OSD) Nil characters in input fields are simulated. Hostfarben (host colors) If the host application uses color attributes these are used for the field colors. Overwrite Overwrite mode is default on each screen. Blockcursor A blinking block cursor is shown Autoresize Automatic font resizing as default. If used with portlet connecthost these settings are done in the portlet properties dialog. Complete configuration files can be imported directly from the client pc. At the moment.frb-files of Intrasys emulation AllInOne V6 are supported. Not available if used with portlet connecthost. Vorschau (Preview) The current screen with the configured attribute mappings is shown here. With a click on a character inside this view the attributes for this character are shown in the area Attributumsetzung. Attributumsetzung (Atribute mapping) Here the color and font style of the browser representation for all possible attribute combinations can be set. If you want to change the browser rendering of a special attribute combination follow these Steps : 1. Choose the attribute combination by clicking the character representing this combination in the preview area. With the link Matrix... you can open this preview in a seperate window showing the complete screen. Pay attention that all check boxes beneath? are checked. 2. Now choose the desired font style and color for this attribute combination in the area Darstellung (Representation). The example text (Beispieltext) shows the chosen representation. Click into the box for text or background color and afterwards into a field of the color chooser to get the HTML representation of this color into the box. All check boxes must be checked here too. 3. Click on to assign the representation to the attribute combination. You can check the result in the preview area. By using the check boxes you can also assign a representation to many attribute combinations with one click. For example: you want to show all underlined host fields in red with a bold and not underlined font. To do this you need the following settings: After a click on the representation for all host attribute combinations with the underline bit on is set to red, not underlined and bold. The setting for background color and italic style (kursiv) is not changed. Page 63 of 64

How to lay out a web page with CSS

How to lay out a web page with CSS You can use table design features in Adobe Dreamweaver CS3 to create a simple page layout. However, a more powerful technique is to use Cascading Style Sheets (CSS).