CA Gen. ASP.NET User Guide. Release 8.5

(1)

ASP.NET User Guide

Release 8.5

(2)

Thi s Documentation, which i ncludes embedded help systems a nd electronically distributed materials, (hereinafter referred to a s the “Documentation”) is for your i nformational purposes only a nd i s subject to change or wi thdrawal by CA a t a ny ti me. Thi s Documentation ma y not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or i n part, without the pri or written consent of CA. Thi s Documentation is confidential and proprietary i nformation of CA a nd may not be disclosed by you or us ed for a ny purpose other than as may be permitted in (i) a separate a greement between you and CA governing your us e of the CA s oftware to which the Documentation relates; or (i i) a separate confidentiality a greement between you and CA.

Notwi thstanding the foregoing, i f you a re a licensed user of the s oftware product(s) a ddressed i n the Documentation, you may pri nt or otherwise make available a reasonable number of copies of the Documentation for i nternal use by you a nd your empl oyees i n connection with that s oftware, provided that all CA copyri ght notices and legends a re a ffixed to each reproduced copy.

The ri ght to print or otherwise make a vailable copies of the Documentation is limited to the period during which the applicable l i cense for s uch software remains i n full force a nd effect. Should the license terminate for a ny reason, i t is your responsibility to certi fy i n writing to CA tha t all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The us e of any s oftware product referenced i n the Documentation is governed by the a pplicable license a greement a nd s uch l i cense agreement is not modified in a ny wa y by the terms of this notice.

The ma nufacturer of this Documentation is CA.

Provi ded wi th “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restricti ons s et forth in FAR Sections 12.212, 52.227-14, a nd 52.227-19(c)(1) - (2) a nd DFARS Section 252.227-7014(b)(3), as applicable, or thei r s uccessors.

(3)

CA Technologies Product References

This document references the following CA Technologies products:

■ CA Gen

■ AllFusion® Gen

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ _{CA Support policies and guidelines}

■ _{Other helpful resources appropriate for your product}

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

(4)

(5)

Contents 5

Chapter 2: Pre-Installation Planning

15

Technical Requirements... 15

Supported Features ... 16

Chapter 3: Installing ASP.NET Web Client

17

Installation Procedure for ASP.NET W eb Client... 17

Set Up the Development Environment ... 17

Set Up the Build Environment... 17

Set Up the Application Server Environment... 18

Set Up the Message Resources... 20

Set Up the End -User Environment ... 21

Chapter 4: Designing an ASP.NET Web Client Application

23

ASP.NET Web Client Modeling... 23

Common Edit Modifications... 24

Web Properties... 25

Hypertext Links ... 30

Display Push Buttons as Hypertext Links ... 32

(6)

6 ASP.NET User Guide

Dynamically Change Multi -State Images ... 34

Support for Themes and Skins ... 34

Support for Third-Party Web Controls ... 35

Toolset Support for Third-Party Web Controls ... 35

Restrictions on Use of Third-Party Web Controls... 39

Special Features... 39

Browser Event Queue... 39

Disabled By ... 39

DBCS Character Entry ... 40

Specify Images Dynamically with SetBitMapName... 40

Design Considerations ... 40

Chapter 5: Generating an ASP.NET Web Client Application

41

Generate ASP.NET Web Client Application from the Toolset ... 41

Generate ASP.NET Web Client Application from CSE ... 44

Chapter 6: Building and Running an ASP.NET Web Client Application

45

Images for ASP.NET Applications ... 45

External Action Blocks ... 46

Build and Assemble ASP.NET Web Client Applications ... 46

Configure ASP.NET Web Client Communications... 47

Pre-compile ASP.NET Application ... 47

Trace Generated Applications... 48

Trace Using web.config ... 48

Trace a Generated ASP.NET Application Using the Diagram Trace Utility... 49

Dynamic HTTP Compression ... 50

Support for Native Image Generation ... 51

Support for Encryption ... 52

Edit Encrypted Sections of Configuration Files ... 54

Run ASP.NET W eb Client... 55

Support for Tabbed Browsing ... 55

National Language Support (NLS) ... 56

Chapter 7: HttpRequest and HttpResponse Object Access

57

Access Mechanism ... 57

Access HttpRequest Object ... 57

(7)

Contents 7

Chapter 8: User Exits

59

Chapter 9: Messages

61

Consistency Check Messages ... 61

Runtime Error Messages... 61

Rebuilding the Error Messages ... 63

Chapter 10: Unsupported Features

65

Unsupported Events ... 65

Unsupported Presentation-Related Functions ... 66

Tips... 67

Unsupported OLE Functions... 68

Unsupported File-Related Functions ... 68

Other Unsupported Features ... 69

Tips... 70

Window and Dialog Properties ... 70

Web Graphics... 70

Colors... 70

MAKE in Internet Explorer ... 71

Considerations for Third-Party Web Controls... 71

Help Support ... 72

Chapter 11: ADO.NET

73

DDL Installation ... 73

Code Generation ... 74

Configure an ASP.NET W eb Client Application for ADO.NET Access ... 74

Index

77

(8)

(9)

Chapter 1: Overview 9

Chapter 1: Overview

The ASP.NET Web Client feature of CA Gen uses the Web as an access medium to connect to CA Gen servers. ASP.NET Web Clients build on Microsoft .NET technologies. The application logic is generated in C# and the user interface downloaded to browsers is HTML with JavaScript. Users who require Web browser access to CA Gen servers will benefit from reading this guide. This guide describes design, generation, and building by providing the following information:

■ Prerequisites for installing the ASP.NET Web Client software

■ Technical requirements for ASP.NET Web Clients

■ How to install the new software

■ How to generate the application

■ How to build files and use the application

■ _{Consistency check messages}

.NET Overview

Microsoft® .NET is a set of Microsoft software technologies for connecting information, people, systems, and devices. It spans clients, servers, and developer tools.

The following components are primarily used by CA Gen ASP.NET Web Clients:

■ _{Microsoft Visual Studio® .NET, which provides a rapid application integrated}

development environment for programming with the .NET Framework

■ _{.NET Framework}

.NET Framework

The .NET Framework is the programming model of the .NET environment for building, deploying, and running Web-based applications, smart client applications, and XML Web services. The key components of the .NET Framework are the common language runtime and the .NET Framework class library, which includes ADO.NET, ASP.NET, and Windows Forms.

(10)

.NET Framework

Common Language Runtime

The Common Language Runtime (CLR) is responsible for runtime services such as language integration, security enforcement, memory management, process

management, and thread management. In addition, it has a role at development time when features such as life-cycle management, strong type naming, cross -language exception handling, and dynamic binding reduce the amount of code that a developer must write to turn business logic into a reusable component.

Framework Class Libraries

The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object-oriented, providing types from which your own managed code can derive functionality. Base classes provid e standard functionality such as input/output, string manipulation, security management, network communication, thread management, text management, user interface design features, and other functions. The Microsoft ADO.NET data classes support persistent data management and include SQL classes for manipulating persistent data stores through a standard SQL interface. XML classes enable XML data manipulation and XML searching and translations. The Microsoft ASP.NET classes support the development of Web-based applications and XML Web services. The Windows Forms classes support the development of Windows-based smart client applications. Together, the class libraries provide a common, consistent development interface across all languages supported by the .NET Framework.

Common Type System

The common type system defines how types are declared, used, and managed in the runtime, and is also an important part of the runtime's support for cross-language integration. The common type system performs the following functions:

■ Establishes a framework that enables cross -language integration, type safety, and high performance code execution.

■ Provides an object-oriented model that supports the complete implementation of many programming languages.

■ _{Defines rules that languages must follow, which helps ensure that objects written in}

(11)

ASP.NET Web Clients

Chapter 1: Overview 11

Common (Microsoft) Intermediate Language

One of the biggest advantages that the runtime framework provides is a

language-neutral execution environment. All code, irrespective of the source language, is compiled automatically into a standard intermediate language (IL) - either on command or when first executed (in the case of ASP.NET). The runtime framework then creates the final binary code that makes up the application and executes it. The

compiled IL code is used for each request until the source code is c hanged, at which point the cached version is invalidated and discarded.

Common Language Specification

To fully interact with other objects regardless of the language they were implemented in, objects must expose to callers only those features that are common to all the languages they must interoperate with. For this reason, a set of language features called the Common Language Specification has been defined.

Assembly

An assembly is a collection of one or more files grouped together to form a logical unit. Most assemblies contain just one file, but assemblies can and sometimes do include multiple files. All the files that make up a multifil e assembly must reside in the same directory. When you use the C# compiler to produce a simple EXE, it is referred to as an assembly.

Global Assembly Cache (GAC)

To share an assembly where any application can find it, it must be installed in the Global Assembly Cache (GAC). The GAC is a repository for shared assemblies. When the CLR attempts to load an assembly, it looks in the GAC even before it looks in the l ocal application directory.

ASP.NET Web Clients

ASP.NET Web Clients are applications generated by CA Gen. They use Microsoft ASP.NET technology, which provides a unified Web development model that includes the services necessary to build enterprise-class Web applications. ASP.NET is part of the .NET Framework and can take full advantage of the features of the common language runtime, such as type safety, inheritance, language interoperability, and versioning.

(12)

ASP.NET Web Client Environments

ASP.NET Web Client Architecture

ASP.NET Web Clients generate thin client applications, that are based on the GUI design model. The resulting client application logic resides primarily on the Web server, Internet Information Services (IIS), while the interface is downloaded to an Internet Explorer web browser. The following illustration shows the high level architecture of the CA Gen-generated ASP.NET Web Client application:

ASP.NET Web Client Environments

The following five environments are involved in ASP.NET Web Client generation, and these environments can be located on one machine or five physically separate machines:

■ Server environment

The CA Gen runtime is installed for generated server applications . No special setup is required for ASP.NET Web Client applications.

■ Application Server environment

The runtime engine and application logic for the client is installed on an Internet Information Services (IIS) Application Server, which enables CA Gen to run the generated ASP.NET Web Client application.

(13)

ASP.NET Web Client Highlights

Chapter 1: Overview 13 ■ _{Development environment}

The CA Gen Toolset provides the environment to develop and generate CA Gen ASP.NET Web Client applications. This environment contains the components that generate the application both locally and remotely. The client Server Encyclopedia can also be used to generate ASP.NET applications.

■ Build environment

This environment enables the generated files from the CA Gen Development environment to be compiled and packaged into an MSI file. The CA Gen Build environment is often located on the same machine as the CA Gen Development environment.

■ _{End user environment}

This environment enables end users to access CA Gen ASP.NET Web client applications through an Internet Explorer browser.

ASP.NET Web Client Highlights

The following list discusses the highlights of ASP.NET Web Client applications that are generated using CA Gen:

■ _{The application logic resides on the application server machine.}

■ _{ASP.NET Http Handlers (ASHXs) serve as entry points to generated applications.} ■ The User Interface is a combination of HTML, JavaScript, and Cascading Style Sheets

that are created dynamically by the Gen runtime and downloaded to the browser.

■ Permitted Value and Edit Pattern checking takes place on the browser using JavaScript.

■ The product lets existing users reuse their models by generating ASP.NET Web Client applications.

■ _{ASP.NET Web Client software can access databases by using Gen Server applications}

or using ADO.NET on the Application Server environment.

■ _{ASP.NET Web Client user interface must be on a Windows platform using a}

supported version of Internet Explorer.

■ TCP/IP, MQSeries, Web Services, and .NET Remoting are the only thread-safe middleware available for ASP.NET Web Client.

Note: Due to browser and HTML limitations, some CA Gen-related features have a different level of support than GUI applications when generated for ASP.NET Web Clients.

(14)

Related Information

More Information:

Unsupported Features (see page 65)

Related Information

For more detailed information on ASP.NET applications or related topics, see the following:

Prosise, Jeff. Programming Microsoft .NET. Microsoft Press, 2002.

For more information on ASP.NET web applications, see the relevant Microsoft documentation.

Note: Throughout this document, the environment variable %GENxx%Gen is used. xx

refers to the current release of CA Gen. For the current release number, see the Release Notes.

(15)

Chapter 2: Pre-Installation Planning 15

Chapter 2: Pre-Installation Planning

This chapter provides the infrastructure requirements you need to know as you prepare to install the ASP.NET Web Client software. The four different environments associated with this feature can be located on one machine or four physically separate machines. The end-user machine must have the supported version of Internet Explorer.

Note: For more information about the supported versions of Internet Explorer, see

Technical Requirements available at http://www.ca.com/support.

Technical Requirements

Third-Party software and CA Gen software each have requirements in addition to the ASP.NET Web Client requirements shown in the following table:

Environment Third-Party Software CA Gen Software

CA Gen Server No change required for ASP.NET Web Client applications.

Installed CA Gen cooperative server. Application Server Internet Information Services (IIS)

.NET Framework

ASP.NET Web Client*. Communications Runtime** Development Windows Operating System **

Internet Information Services (IIS) **, ***

Workstation Development Toolset or Client/Server Encyclopedia (CSE) for generation only. ASP.NET Web Client Build Windows Operating System **

Visual Studio**

Implementation Toolset ASP.NET Web Client End User Microsoft Internet Explorer**

Note:

■ _{* Only needed if not already installed in the GAC.}

■ _{** See the}_{Technical Requirements}_{available on http://ca.com/support for details.} ■ *** Internet Information Services (IIS) is only needed if third-party Web Controls

(16)

Supported Features

Due to limitations of the browser and HTML, some features have a different level of support than GUI applications when generated using CA Gen for ASP.NET Web Client.

More Information:

(17)

Chapter 3: Installing ASP.NET Web Client 17

Chapter 3: Installing ASP.NET Web Client

This chapter reviews the installation procedure for the ASP.NET Web Client feature. Before you start the installation, see Technical Requirements (see page 15).

Installation Procedure for ASP.NET Web Client

You must install ASP.NET Web Client as instructed from the CA Gen download folder to four different environments. These environments can be located on one machine or four physically separate machines.

Set Up the Development Environment

You must set up the development environment to generate and install ASP.NET Web Client applications.

Follow these steps:

1. Set up your environment to generate and install the ASP.NET Web Client component, in addition to other CA Gen development tools such as the Workstation Toolset.

2. Set up any third-party Web Controls used in the application.

Note: Steps 2 is only needed if third-party Web Controls are used in a model.

Set Up the Build Environment

The Build machine is where the application is built and packaged in preparation for installation. ASP.NET Web Clients can only be built on Windows platforms, so only the Implementation Toolset windows can be used.

This Implementation Environment must have the Implementation Toolset installed.

The following components are needed for ASP.NET Web Clients:

■ _{Build Tool}

Builds the source code generated from the Workstation or the Client Server Encyclopedia.

(18)

■ _{Assemble Option}

An option available on the Build Tool. It is required to package ASP.NET Web Client applications in preparation for installation on an IIS Application Server. Assembling creates an .MSI file that contains all the required components to install and run ASP.NET Web Client applications.

■ Communication Runtime Software

– .NET Remoting middleware, if flowing to a .NET Server

– TCP/IP middleware, if flowing to a CA Gen server using TCP/IP

– MQSeries middleware, if flowing to a CA Gen server using MQSeries

– Web Services middleware, if flowing to a CA Gen server using Web Services

■ _{Third-party Software} – Visual Studio

– Any third-party Web Controls used in the generated application

– The following if DDL installation is needed:

■ Database

■ ODBC driver

Set Up the Application Server Environment

ASP.NET applications use encrypted config files as the default assemble option and this option requires IIS to use RSA key container. The access to RSA Key container needs to be explicitly granted to the user account that runs ASP.NET applications. The user account to run ASP.NET application is different on each version of IIS. For example, the default user account for each IIS is listed in the table next:

IIS Version Default User Account

IIS 7.0, Windows Server 2008 NETWORKSERVICE IIS 7.5, Windows Server 2008 R2 and Windows 7 NETWORKSERVICE

The user account is configurable on IIS 7 with application pool configuration panel.

The following command is used to grant the access to RSA Key container.

aspnet_regiis -pa "NetFrameworkConfigurationKey" "<user account>"

You must set up the Application Server environment to generate and install ASP.NET Web Client applications.

(19)

Chapter 3: Installing ASP.NET Web Client 19

Follow these steps:

1. Invoke the setup program created by the Build Tool Assemble Option. The setup program installs the contents of the .MSI file under the Application Server automatically.

2. Install third-party Web Controls, if any are required.

Note: For more information about Microsoft Software setup, see Microsoft documentation.

(20)

Set Up the Message Resources

After installing the ASP.NET Web Client option, the message resource files automatically install in the <CA Gen install directory>\.net\localization\resources directory. This directory must contain, but may not be limited to the following files:

■ _{csumessages.txt} ■ _{fmrtmessages.txt}

Localization of these files uses the naming convention <manager type>+ “messages” + "." + <two letter language identifier> + ".txt".

CA Gen provides localized versions for a set of languages. If needed, you can create a variant of the resource file. The language identifier used is the two letters defined in the model under Dialect Definition, Properties, and Message Table Name.

Rules to Edit Message Resource Files

The following syntactical rules apply when editing the message resource files:

■ Set all parameters using <parameter>=<value> (with no spaces before or after the equals sign).

■ Enclose variables in curly braces {} and increment as needed. The increment is zero relative.

(21)

Chapter 3: Installing ASP.NET Web Client 21 ■ _{Use # for comments.}

■ _{Use \ for line continuations.}

Set Up the End-User Environment

ASP.NET Web Client application end users can access the application using Internet Explorer. No special setup is necessary.

(22)

(23)

Chapter 4: Designing an ASP.NET Web Client Application 23

Chapter 4: Designing an ASP.NET Web

Client Application

After installing the software, you are ready to use the Toolset to define ASP.NET Web Client components.

This section contains the following topics:

ASP.NET Web Client Modeling (see page 23)

Support for Third-Party Web Controls (see page 35)

Special Features (see page 39)

ASP.NET Web Client Modeling

The modeling for ASP.NET Web Client applications closely mimics that of GUI and Java Web Generation applications. The three types of applications share the same Action Diagram logic. GUI design is the basis for the user interface. However, you can also use specialized features for the other two target environments.

(24)

ASP.NET Web Client Modeling

Common Edit Modifications

With the Common Edit Modification menu, you can make common edits to a window across all the modes. They are:

■ _ASP.NET ■ _HTML ■ _Window

Moving a control in the Edit Window mode moves the field when the window displays in either Edit HTML mode or Edit ASP.NET mode. The same is true when editing a field in Edit HTML mode or Edit ASP.NET mode. This common functionality is the default for the Common Edit Modifications menu item and occurs when this option is checked.

If Common Edit Modifications is not checked, any edits causing updates to any of the visible properties of a window and its controls are considered a customization for the edit mode used in the current window (Windows, HTML, or ASP.NET). Control location, prompt text, control font, and color are examples of customizable properties. You can also add, update, or delete a control relative to one mode onl y.

(25)

Web Properties

The Web Properties node on the Business System Defaults Video Properties dialog provides configurable options at the level of Business System. You can specify the menu styles, and the images for Help, and Close buttons.

Menus

GUI applications support one style of menus only, horizontal. In ASP.NET Web Client applications, you have the choice of selecting whether to generate vertical menus (starting at the top left corner and expanded vertically down the side of the page) or horizontal menus (starting at the top left corner and expanded horizontally across the page). The default style is vertical menus. The option to switch between both styles is available on the level of the Business System.

Customizable Help and Close Buttons

ASP.Net Web Client Generation can create a Help button with a value of '?' and a Close button with a value of 'X' on a window if its Main Menu Bar's property: Generate

Window and Help Menus is selected. Those buttons also get generated for Dialogs when the System Menu property is selected. You can select at the Business System Level whether or not you want to generate these Help and Close buttons. At the Business System Level, you can also optionally place a bitmap of your choice for Help and Close Buttons, which will apply to all windows in the Business System.

(26)

You can browse and select the required images for the Help and Close buttons from the Business System Defaults Video Properties dialog. The Toolset will copy them into the html/images directory. The image will not be displayed at design time.

For more information about the Business System Defaults Video Properties dialog, see the Toolset Help.

Themes

A theme is a collection of appearance settings that you can define, and consistently apply across the application, and the application control types. You can apply a single theme across all the pages of CA Gen ASP.NET application. A theme for a CA Gen ASP.NET application consists of control skins, CSS files, and image files.

You can customize the appearance of ASP.NET applications by applying changes to the theme, without changing the appearance settings for individual windows, or controls in the application.

With the MSI .NET Assemble Details dialog in the Build Tool, you can specify the name of the theme, <themename>, for an ASP.NET application. The following image details the MSI.NET Assemble Details dialog in the Build Tool:

Note: For more information about the MSI.NET Assemble Details dialog, see the Build Tool Help.

(27)

When you specify a theme, CA Gen creates a directory, APP_Themes \<themena me>, in the application root directory when installing the application on the server. This directory stores the control skin files, the CSS files, and the image files for each theme. User can create, add, and maintain control skins, CSS files, or image files for each theme in this directory.

The web.config file in the application root directory includes a pages tag with the theme attribute, <pages theme=”<themena me>” />.

Skins

Skins are visual attribute definitions for application controls that are stored in the skin file, [set the File Name variable].skin. Control skins define only the visual attributes that are a part of a theme for an application.

In CA Gen ASP.NET applications, you can define control skins for eac h control type in a separate file, or you can define all the control skins for a theme in a single file. The <themename> directory for a theme must include all the control skins that are a part of the theme.

The control skin overrides the appearance settings for the control in the Navigation diagram. However, the appearance settings of a control through dynamic attributes or Dot Notation override the settings in the control skin.

CA Gen supports default control skins. A default control skin automatically applies to the all the controls of the same type when a theme is applied to the ASP.NET application. A default skin has the following format:

For example, this is the default control skin entry for a single line entry field:

<Gen:ASPXSingleLineEdit runat="server" Height="20px" Width="100px" ForeColor="Red" BackColor="#FFE4C4" Font-Name="Script" Font-Size="14pt" Font-Bold="false"

Font-Italic=”true” Font-Strikeout=”false” Font-Underline=”true” BorderStyle="groove" BorderColor="#FF0000" BorderWidth="1pt"/>

This default skin applies to all SingleLineEdit controls on pages that use the theme.

CA Gen provides a sample skin, Gen_Sample.skin, in the CA Gen samples\ASP.NET directory.

Note: CA Gen does not support named skins that apply to a specific instance of a control type.

(28)

Rules to Specify Visual Attributes in Control Skins

When you specify the visual attributes for a control skin, you can specify only the visual attributes that are supported for each control type.

The following rules apply when specifying the visual attributes for control skins that support a theme in an ASP.NET application:

1. The theme for an ASP.NET application can support only the following common

visual attributes: ■ Width ■ Height ■ ForeColor ■ BackColor ■ Font

– FontType (Font-Name, or Font-Names)

– Font-Size

– Font Style properties

(Font-Bold, Font-Italic, Font-Strikeout, Font- Underline, Font-Overline). The value of Font Style properties can be either true or false.

■ Border

– BorderColor

– BorderStyle (includes dotted, dashed, solid, double, groove, ridge, inset, and outset.)

– BorderWidth

Note: The color for the ForeColor, BackColor and BorderColor attributes may be represented by the name of the color or the hexadecimal RGB code for the color prefixed with #.

2. The control skins for the individual control types may support one, more, or all of the common visual attributes in the theme.

The following table lists the supported common visual attributes in a control skin for each control type in a CA Gen ASP.NET application:

Control Type Supported Common Visual Attributes Unsupported Common Visual Attributes

(29)

Control Type Supported Common Visual Attributes Unsupported Common Visual Attributes

Gen:ASPXBitmap Width, Height, Border ForeColor, BackColor

Gen:ASPXBitmapButton Width, Height, Border ForeColor, BackColor

Gen:ASPXButton All the common visual attributes.

Gen:ASPXCheckBox All the common visual attributes.

Gen:ASPXRadioButton All the common visual attributes.

Gen:ASPXSingleLineEdit All the common visual attributes.

Gen:ASPXMultiLineEdit All the common visual attributes.

Gen:ASPXGroupBoxLiteral All the common visual attributes.

Gen:ASPXStaticLiteral All the common visual attributes.

Gen:ASPXPermValueList ForeColor,BackColor,Width, Font Height, Border Gen:ASPXHyperLink All the common visual attributes.

Gen:ASPXLinkButton All the common visual attributes.

Gen:ASPXStatusBar All the common visual attributes. Gen:ASPXToolBar All the common visual attributes.

Gen:ASPXDropDownNoEntry ForeColor,BackColor,Width, Font

Height, Border

Gen:ASPXListBox ForeColor, BackColor, Font, Border Width, Height

Gen:ASPXFixedSizeTable ForeColor, BackColor, Font, Border Width, Height

Gen:ASPXVaryingSizeTable ForeColor, BackColor, Font, Border Width, Height

Gen:ASPXListBoxColumn (listbox/table prompt)

(30)

Control Type Supported Common Visual Attributes Unsupported Common Visual Attributes

Gen:ASPXMenuBar ForeColor, BackColor, Font, Width Height, Border

Hypertext Links

Hypertext links will be common to both HTML and ASP.NET modes even if the Common Edit Modifications Option is not selected. ASP.NET Web Clients and Java Web

Generation applications support two types of hypertext links:

■ Bookmark-This option links to a location on the current page.

■ _{Open New Browser Window-This option opens a new browser window with a}

user-specified page and transfers control to this new window.

Both types of hypertext links are available in ASP.NET and HTML modes, but are not available in Window mode. They are accessed from the Add menu item in the Navigation Diagram.

To access the Bookmark option, choose Hypertext Link from the Add menu, and click Bookmark. The Hypertext Link Bookmark Properties dialog appears:

The Display Text and Name fields are populated with default values that you can replace. Note that the bookmark name must be unique within the scope of its parent window. You must specify the target object the bookmark will link to. The Target Object can be any control on the window.

(31)

To access the Open New Browser Window option, choose Hypertext Link from the Add menu, and click Open New Browser Window. The Hypertext Link Open New Browser Window Properties dialog appears.

The Name and Display fields are populated with a default you c an change. The URL field is required. You can select properties for the window by checking any of the check boxes under the URL field. For example, if you check Location, the browser window would display a Location (or address) bar.

You can use the action diagramming statements: Enable and Disable to control the display of the hypertext link. Alternatively, you can get the details of the conditions under which a control is disabled or enabled by checking the Disabled By or Enabled By options.

(32)

Display Push Buttons as Hypertext Links

A push button can be displayed as a hypertext link by selecting a check box, Display as Hypertext Link, on a Push Button Properties dialog. This check box is enabled in HTML mode and ASP.Net mode. This feature l ets you perform functions associated with push buttons, such as Executes Click Event, while maintaining the appearance of a hypertext link.

(33)

Varying and Fixed Size Tables

HTML Tables are a type of list that can be associated with group views. ASP.NET Web Client application supports two types of HTML Tables:

■ _{Fixed Size Table}

The coordinates of a Fixed Size Table are specified at design time. A Fixed Size Table will only display the number of rows that can fit in the size designed for it. Any controls placed below a fixed size Table will retain their designed positions at Runtime.

■ _{Varying Size Table}

The vertical size of a Varying Size Table is directly proportional to the size of its associated Group View. Varying Size Tables grow or shrink in terms of the number of rows they display to ensure all the entries in their associated group views are displayed. Any controls located below Varying Size tables move to maintai n the designed distance between them and the Table.

(34)

Dynamically Change Multi-State Images

GUI applications have the ability to change images on push buttons according to their state, for example, disabled versus enabled. For GUI applications, a user specifies a bitmap that is divided into sections, each representing a different state. ASP.NET Web Client application provides a similar capability. Where for GUI applications you had a different section of the provided bitmap designated for each state, with Web

application, you have to provide a different image in a different file for each state. The alternative images will use the image name in the model as a base and append text to it for the four different states supported: enabled, disabled, pushed, and focused. If myimage is the name saved in the model, the series of images used will be of the forms myimage.jpg for the enabled state, myimage_disabled .jpg for the disabled state, myimage_ pushed .jpg for the pushed state and myimage_focused .jpg for the focused state. The images should be placed under the html \images\ directory, and the value in the Number of Pictures field on the Push Button Properties dialog must be set to the number of images.

Support for Themes and Skins

CA Gen provides support for themes and skins i n ASP.NET applications. Themes and skins let you create, and maintain common appearance settings across an ASP.NET application.

CSS Files

A theme may also include Cascading Style Sheet (CSS) files. When you add a [set the File Name variable].css file for a theme in the <themename> directory, the style sheet is applied automatically as part of the theme.

The CSS file consists of valid style sheet statements that specify the Type Selector, or the ID Selector for the windows or controls in a CA Gen ASP.NET application.

In CA Gen ASP.NET applications, the appearance settings of a control from the

Navigation Diagram, dynamic attributes, Dot Notation statements, or skin properties are saved as inline style attributes in each HTML tag. Hence, all controls in CA Gen ASP.NET applications contain inline style attributes.

The style attributes in a CSS file can only modify the attributes that are not specified in the inline style attribute because the inline style attributes have a higher precedence over the style settings from a CSS file,

For example, the following statements in a CSS file define the background color of a window, the color of the field prompt, and the controls with ID, Field1:

Body { background-color:#ffc0cb; }

Label { color: #00ff00; background-color: #32cd32; } #Field1 { color:#ff0000; background-color: ffc0cb;}

(35)

Support for Third-Party Web Controls

If you add this CSS file in the <themename> directory, the following appearance settings apply for the windows, controls, and field prompts:

■ All the windows in the application display with pink background color

■ The field prompts in the application display with green foreground color, and lime-green background color.

■ The controls with the ID, Field1, in the application display with red foreground color, and pink background color if the inline styles for the prompts and controls with ID, Field1, do not specify the foreground color or the background-color.

Image Files

A theme may include images that are referenced by the CSS file.

If the style statement of a CSS file references an image file, you must add the image file to the <themename> directory or the Images subdirectory under the <themename>

directory depending on the style statement in the CSS file.

Note: In CA Gen ASP.NET application, the ImageUrl property is not supported for ASPXBitmap, ASPXBitmapButton, and ASPXHyperLink controls in the theme. The control skin must not reference the image files.

Support for Third-Party Web Controls

Third-party Web controls and their event management is supported. This lets ASP.NET Web Client add capabilities specific to the ASP.NET environment, through the use of external controls that are not part of the traditionally available set of Gen controls. These controls can be used in a manner similar to the way in which ActiveX controls are currently supported in GUI clients. Web Controls can be rendered using Internet Explorer without the need to instal l any third-party software on the end-user machine. However, Web Controls need to be installed on the Development, Build, and Application Server computers.

Toolset Support for Third-Party Web Controls

The Toolset lets you add third-party Web Controls to windows and dialogs. To do so, you need to first install the third-party Web Control of your choice on your development machine. You can then add the third-party Web Control to the model through the ASP.NET Control Manager.

Note: If you want to upgrade the version of a third-party Web Control in a model, you must remove the earlier version and add the new version in the Toolset using the ASP.NET Control Manager. As a result, the toolset updates the file,

ThirdPartyControls.xml in the CA Gen directory. This file retains the controls' version information and must be updated when a third-party Web Control is upgraded.

(36)

Insert Third-Party Controls from the Navigation Diagram

You can insert third-party controls in a window or a dialog from the Navigation Diagram in the Toolset.

Follow these steps:

1. Click Edit, ASP.NET Control Manager in the Toolset. The Third-Party .NET Control Manager dialog opens. 2. Click Add on the Third-Party .NET Control Manager.

The Select an Assembly to Add Controls From dialog opens.

3. Select the required assembly, and click Open. The Web Controls in Assembly dialog opens.

(37)

4. Select the required controls in the Web Controls in Assembly dialog, and click Add. The selected controls appear in the Third-Party .NET Control Manager dialog, and the Web Controls in Assembly dialog closes.

5. (Optional) To delete a control, select the required control, and click Remove on the Third-Party .NET Control Manager dialog. A confirmation dialog appears.

6. Repeat Steps 2 to 5 to add all the required controls from different assemblies. 7. Click Close on the Third-Party .NET Control Manager dialog.

The Third-Party .NET Control Manager dialog closes and returns to the window or the dialog that you were designi ng in the Navigation diagram.

8. Select Edit, Control Design from the Toolset to insert the required third-party control in the window or dialog.

(38)

9. Select the required control in the Toolbox, and click Place to position the third -party control on the current window, or dialog

10. Select the required control, and click Detail, Properties to modify the properties of the control.

11. The Web Control Properties dialog appears.

12. Select Control Properties on the Web Control Properties dialog. The Properties dialog appears for the control.

13. Specify the required modifications for the control in the Properties dialog, and close the dialog.

The modified properties apply for the inserted third-party control at design time, and at runtime.

(39)

Special Features

Access Third-Party Controls from Action Diagram

Action Diagram statements can be used to access methods and properties of third -party Web Controls in a similar fashion to how ActiveX controls are manipulated in the Action Diagram. Dot Notation plays a major role in this aspect. For more information about the Action Diagram, see the Toolset Help.

Restrictions on Use of Third-Party Web Controls

More Information:

Unsupported Features (see page 65)

Special Features

This section describes some of the special features of an ASP.NET Web Client application.

Browser Event Queue

Simultaneous events (within several hundred milliseconds), such as gainfocus/losefocus, are sent to the .NET Runtime in a single request. The events are sorted and processed in a similar manner as GUI clients. This event handling technique closely mimics GUI and lets users who are migrating from GUI to ASP.NET achieve maximum transparency with respect to migration. For multiple events, such as repetitive clicks, the browser's default event handling mechanism is used in conjunction with the ASP.NET framework's event handling mechanism. Note that CA Gen ASP.NET solution does not queue repetitive events on the browser.

Disabled By

Many applications disable controls depending on the values or states of other controls on the same page. Disabled controls appear unavailable and cannot be selected by a user of the applicati on. Disabled By, which specifies the conditions under which a control is disabled, is supported. This facilitates porting GUI models to the Web.

(40)

Special Features

DBCS Character Entry

Double-byte character set (DBCS) characters can be entered into non-DBCS fields without triggering an error unless you use edit patterns to verify entry data. Also, non-DBCS characters can be entered into a DBCS field without triggering an error unless edit patterns are used.

Specify Images Dynamically with SetBitMapName

In GUI applications during design, you can use the function SetBitmapName for a control to set the Bitmap on a picture control. You can also use the function SetBitmapName in ASP.NET applications. By using Dot Notation in the Action Diagram and invoking

SetBitmapName you can set or modify a bitmap on its associated picture control. Unlike Web Generation applications, the specified bitmap needs to be manually included in an assembly by using the Additional File panel in the Build Tool. The specified bitmap has to be in the images folder.

Design Considerations

When creating the user interface for your client application, note that the toolset representation will not be identical to what you see at runtime. There are minor differences between what you see in different types of client applications: GUI, ASP.NET Web Clients, and Web Generation. Following are some of the differences you should expect, though the following items do notrepresent a comprehensive l ist of the differences between GUI, ASP.NET Web Clients, and Web Generation.

■ Prompts in list boxes-ASP.Net Web Clients show prompts above the Table while in Web Generation they appear as part of the Table.

■ Assembling of images-ASP.NET Web Client includes only images specified in the model. Web Generation includes all the contents of the HTML\images directory including subdirectories.

■ _{Blank line option for dropdown list-ASP.Net Web Clients show blank line option in}

the Dropdown list while in Web Generation the <NONE> option is shown.

User Interface Refresh-In certain instances, ASP.NET Web Client applications will reflect updates on a page more frequently than GUI applications. For example, if in your application you update an export view and call a MessageBox, you would not see the window updated in GUI until you acknowledge the MessageBox. In ASP.NET Web Clients, you would see the update as soon as the MessageBox is displayed.

(41)

Chapter 5: Generating an ASP.NET Web Client Application 41

Chapter 5: Generating an ASP.NET Web

Client Application

Generating ASP.NET Web Client components can be accomplished using either the Toolset or the Client Server Encyclopedia.

Generate ASP.NET Web Client Application from the Toolset

After the ASP.NET Web Client installation and design procedures are completed, you can generate ASP.NET Web Clients from the Toolset.

Follow these steps:

1. Start the Toolset and open your model.

(42)

3. From the Generation window, select the Options menu and then Generation Defaults. The Generation Defaults dialog appears:

4. Select CLR from the Operating System drop-down. 5. Select C# from the Language drop-down.

6. At the Type of Installation drop-down box, select Local or Remote.

For a Remote install, generated files are packaged into one installation file, which can then be manually transferred to any Windows target system. For a Local install, generated files are compiled and prepared for installation onto a server. This server can either be running on the same machine as the toolset or a different machine. The default is Local.

(43)

Chapter 5: Generating an ASP.NET Web Client Application 43

8. Optionally, you can select the Options menu from the Generation window, then Model Generation Properties and enter the designated information in the .NET section.

9. Click OK and you are ready to continue with generation of an ASP.NET Web Client Application.

Consistency check rules identify the unsupported features in ASP.NET Web Client applications. These unsupported features are identified in the form of warnings. For a complete list, see the chapter Unsupported Features (see page 65).

A load module is considered eligible for ASP.NET Web Client generation if the ASP.NET Web Client settings are reflected in any one of the following:

■ Generation Defaults panel (when the Override Business System Target Environment with the preceding defaults check box is selected)

■ Client Environment

(44)

Generate ASP.NET Web Client Application from CSE

You can also generate ASP.NET Web Client applications from the Client/Server Encyclopedia (CSE).

Follow these steps:

1. Start the Construction Client and open your model. 2. Select Code, Generate, Cooperative.

3. From Cooperative Application Generation, select Defaults; the following Generation Defaults dialog appears:

4. Select CLR from the Operating System drop-down. 5. Select C# from the Language drop-down.

After defining the ASP.NET Web Client components, you are ready to continue with the generation of an ASP.NET Web Client application.

(45)

Chapter 6: Building and Running an ASP.NET Web Client Application 45

Chapter 6: Building and Running an

ASP.NET Web Client Application

Assembling an ASP.NET Web Client application means creating an MSI package that contains components necessary to execute the generated application. The MSI file is used to set up generated ASP.NET Web Client applications on IIS (Internet Information Services). To accommodate generating your ASP.NET Web Client application, the following directories are created under the model's local directory:

■ C# directory

Contains the generated source files.

■ C#/build

Building area for the generated model and contains the built dlls and web.config files.

■ _C#/deploy

Contains the setup files, including the MSI file, for installing the generated application.

■ xml directory

Contains generated XML files.

■ html directory

Contains the html help files and the images directory

■ html/images directory

Contains converted images such as JPG, GIF, and PNG.

Images for ASP.NET Applications

Before installing the ASP.NET Web Client application, you should convert bitmap images (.bmp files) to a different format such as .jpeg, .jpg or .gif. Use a third-party tool (such as Netscape Composer or LView) to convert the images files to the forma t you prefer. Then copy the images into the images directory under the html directory. Since jpg is the default format assumed by the CA Gen generator, if a format other than jpg is chosen, you must set the HTML extension field on the Properties dialog from the Navigation diagram in the Toolset to match the file extension for the format you are using. Any images that are specified in SetBitMapName have to be manually included in the assembly images folder by using the Additional Files panel in Build Tool.

(46)

External Action Blocks

For more information about using External Action Blocks, see the Distributed

Processing-.NET Server User Guide.

Build and Assemble ASP.NET Web Client Applications

After generating your application, you have to build it on a Windows platform. The Build Tool can work with either ICM files that result from a Local generation, or RMT files that result from a Remote generation. You can set options that affect the build process of your application through the Build Tool Profile.

The deploy directory <model.ief>\C#\Deploy, contains files required to install the application under Internet Information Services (IIS):

Executing the windows installer package installs your ASP.NET Web Client application under IIS.

During installation, MSI displays a warning message if a COM+ server with same name exists. You can ignore this message if the application targets Component Base Development (CBD).

Note: For more details about the Build Tool and Assemble utility, see the Build Tool User Guide.

(47)

Configure ASP.NET Web Client Communications

The ASP.NET Web Client runtime requires data to identify the CA Gen servers that it needs to establish communications with. There are two methods to configure

communications. The first is through specifying the properties of each server in the CA Gen Toolset. The data is then saved in the model and results in the communication parameters being in the generated application. The second method uses the

commcfg.txt file. Commcfg.txt is delivered as a sample file installed with CA Gen. It is a simple text file that you can place under your Application Server, or package within the application MSI file.

For more information about the Commcfg.txt file, see the Distributed Processing - Overview Guide.

Pre-compile ASP.NET Application

You can pre-compile an ASP.NET application before deploying it. Pre-compiling the applications has the following benefits:

■ _{Improves application performance by avoiding the need to compile the first time}

the application is invoked from a browser.

■ _{Lets you verify if the code in the application compiles without errors before}

executing the application.

Gen provides the in place mode for pre-compilation of ASP.NET applications. Pre-compiling a site in place effectively performs the same compilation that occurs when users request pages from your site. Therefore, the primary performance

improvement is that pages do not have to be compiled for the first request. This feature is similar to the Load JSP/Servlets at startup feature that is available during assembly of a CA Gen Web Generation application.

With the MSI.NET Assemble Details dialog in the Build Tool , you can enable the pre-compiling of an ASP.NET Web Client application before deployment.

(48)

Trace Generated Applications

The following screenshot shows the MSI.NET Assemble Details dialog in the Build Tool:

Note: For more information about pre-compiling ASP.NET Web Client application, and the MSI.NET Assemble Details dialog, see the Build Tool Help.

Trace Generated Applications

To debug and test your application you can enable tracing. This section explains how to enable tracing.

Trace Using web.config

The web.config file can be used to enable and disable tracing within the ASP.NET Web Client Runtimes. The output is written to a file, trace-<appname>-<procid >.ou t, where <appname> is the application name and <procid> is the process id of the application. This file is created in the %USERPROFILE%\AppData\Local\CA\Gen xx\logs\net directory.

To enable tracing using the web.config file, set the cmidebug value to -1.

Note:xx refers to the current release of CA Gen. For the current release number, see the Release Notes.

(49)

Trace Generated Applications

Trace a Generated ASP.NET Application Using the Diagram Trace Utility

Follow these steps:

1. During generation, select to generate with Trace.

2. From the Build Tool, in the MSI .NET Assemble Details dialog, select Enable Diagram Trace under the Tracing node.

(50)

Dynamic HTTP Compression

3. To start the Diagram Trace Utility, click Start, All Programs, CA, Gen xx, Diagram Trace Utility.

Note: xx refers to the current release of CA Gen. For the current release number, see the Release Notes.

Note: Diagram Trace Utility executes only on Windows.

4. The Diagram Trace Utility will autostart and listen on port 4567. You may change the default port from within the Diagram Trace Utility.

5. Start the application normally from the browser by invoking the ASP Handler (<trancode>.ashx).

6. Step through the Action Diagram code. For more information, see the Diagram

Trace Utility User Guide.

Dynamic HTTP Compression

Compressing the content that is transferred across the network can improve application performance. Compression reduces the number of bytes of data that is sent over the network, resulting in faster transfer. The faster download outweighs the cost of expanding the compressed response at the browser.

Dynamic HTTP compression reduces the size of HTML and JavaScript content returned to the browser. Dynamic HTTP compressions use the GZIP compression technique. The dynamic content is sent through a filter and compressed on-the-fly by the CA Gen runtime.

(51)

Support for Native Image Generation

Dynamic HTTP decompression is a feature built directly into the browser. This feature does not require any plug-ins, and is enabled by default.

For CA Gen ASP.NET applications, you can enable or disable dynamic HTTP compression from the MSI.NET Assemble Details dialog in the Build Tool.

The following image illustrates the MSI.NET Assemble Details dialog in the Build Tool:

Note: For more information on dynamic HTTP compression, see the Build Tool Help.

Support for Native Image Generation

CA Gen supports native image generation of the Gen .NET runtime. Native images are files that contain compiled processor-specific machine code. The native images are installed in the native image cache on the local system. The .NET runtime can use the native images from the cache instead of using the Just-In-Time (JIT) compiler to compile the original assembly.

Native image generation lets assemblies load and execute faster because the .NET runtime reads code and data structures from the native image cache instead of dynamically generating code and data structures.

Note: To get the optimal performance from native images of Gen .NET Runtime assemblies, you must choose to install Gen .NET Runtime assemblies in the Global Assembly Cache (GAC) at the time of application assembly.

With the MSI.NET Assemble Details dialog in the Build Tool, you can enable the native image generation of Gen runtime for an ASP.NET Web Client application.

(52)

Support for Encryption

The following screenshot illustrates the MSI.NET Assemble Details dialog in the Build Tool:

Note: For more information on native image generation, and the MSI.NET Assemble Details dialog, see the Build Tool Help.

Support for Encryption

CA Gen stores the passwords of an ASP.NET Web Client application in the sessionState, and connectionStrings sections of the configuration files.

When building a CA Gen ASP.NET Web Client application, you have the option to encrypt the sessionState, and connectionStrings sections of the configuration files.

With the DataSources node on MSI .NET Assemble Details dialog in the Build Tool, you can enable the encryption of the following sections of the configuration files:

■ _{The connectionStrings section in web.config for the Gen ASP.NET Web Client}

application.

(53)

The following screenshot details the DataSources node on MSI .NET Assemble Details dialog:

You can also use the ASP.NET node on MSI .NET Assemble Details dialog in the Build Tool to encrypt the sessionState section in web.config for the client.

The following screeshot details the ASP.NET node on MSI .NET Assemble Details dialog:

Note: For more information about the MSI .NET Assemble Details dialog, see the Build Tool Help.

More information:

(54)

Edit Encrypted Sections of Configuration Files

After deployment, the user can edit the encrypted sessionState or connectionStrings sections in the application if the user has administrative privileges.

Edit the Encrypted sessionState Section in web.config

The user can edit the encrypted sessionState sections in web.config if the user has administrative privileges.

Follow these steps:

1. Decrypt the sessionState section by entering one of the following commands:

aspnet_regiis -pdf system.web/sessionState <IIS Root>\myapp aspnet_regiis -pd system.web/sessionState -app /myapp

2. Edit the web.config file and make the required changes.

3. Re-encrypt the sessionState section by entering one of the following commands:

aspnet_regiis -pef system.web/sessionState c:\inetpub\wwwroot\myapp aspnet_regiis -pe system.web/sessionState -app /myapp

Edit the Encrypted connectionStrings Section in web.config

The user can edit the encrypted connectionStrings sections in web.config if the user has administrative privileges.

Follow these steps:

1. Decrypt the connectionStrings section by entering one of the following command:

aspnet_regiis -pdf connectionStrings c:\inetpub\wwwroot\myapp aspnet_regiis -pd connectionStrings -app /myapp

2. Edit the web.config file and make the required changes.

3. Re-encrypt the connectionStrings section by entering one of the following commands:

aspnet_regiis -pef connectionStrings c:\inetpub\wwwroot\myapp aspnet_regiis -pe connectionStrings -app /myapp

(55)

Run ASP.NET Web Client

Edit the Encrypted connectionStrings Section in Application.config

The user cannot directl y edit the connectionStrings section in Application.config. However, the user can copy Application.config to a temporary file, rename the file as web.config, and make the required edits.

Follow these steps:

1. Copy the Application.config file to a temporary location and rename the file as web.config.

2. Decrypt the connectionStrings section in the temporary web.config file with the following command:

aspnet_regiis -pdf connectionStrings <web.config physical directory>

3. Edit the temporary web.config file and make the required changes.

4. Re-encrypt the connectionStrings section in the temporary web.config with the following command:

aspnet_regiis -pdf connectionStrings <web.config physical directory>

5. Copy the contents of the temporary web.config file to the original Application.config file.

Run ASP.NET Web Client

To invoke an ASP.NET Web Client application, an Http handler is used. This handler is of the form <trancode>.ashx or <loadmodule>.ashx. If the trancode and load module names are the same, <trancodeORloadmodule>.ashx will invoke processing for <trancode>.ashx. The load module can be explicitly invoked by specifying

<loadmodule>_Im.ashx. Using <loadmodule>_Im.ashx invokes the default procedure step for the load module specified.

There is a web.config file that gets created with ASP.NET Web Client applicati ons. This web.config contains mappings for Http Handlers to the runtime. The runtime infers the requested trancode from the mappings in web.config.

GUI applications allow you to define CLEAR SCREEN INPUTS at execution time, which affect the processing of the application. For ASP.NET Web Clients to use CLEAR SCREEN INPUTS, they must be sent on the URL as a parameter at request time:

<http://<hostname>/<application>/<trancode>.ashx? clearScreenInputs=myvalue

Support for Tabbed Browsing

CA Gen supports tabbed browsing in ASP.NET Web Client applications. Tabbed browsing lets the user concurrently open, access, and update an ASP.NET Web Client application from different tabs of a single browser instance.

(56)

National Language Support (NLS)

A tabbed session is comparable to an individual browser instance of the ASP.NET Web Client application. CA Gen independently manages the session states of an application running under different tabs in a Browser Window.

Note: Tabbed browsing support requires a minimum of Internet Explorer 7.x.

National Language Support (NLS)

All files generated for ASP.NET Web Clients are UTF-8 encoded. The model encoding is used to determine the translation used to convert the files to

UTF-8. In an effort to facilitate National Language Support (NLS), CA Gen creates satellite assemblies to represent each dialect. There are two ways to select the dialect:

■ On Internet Explorer, the Language Preference setting under Internet Options is used to determine the corresponding default locale. There is a configuration file installed with CA Gen, culture.ini, which is used to determine mappings from Gen's standard Message Table designation in the Dialect Definition to Microsoft's standard locales.

■ _{The dialect name or culture language code can be used as a context to reference}

the required dialect, for example:

http://hostname:portnumber/application/dialect/trancode.ashx or

(57)

Chapter 7: HttpRequest and HttpResponse Object Access 57

Chapter 7: HttpRequest and HttpResponse

Object Access

System.Web.HttpRequest and System.Web.HttpResponse are classes in the .NET Framework Class Library. HttpRequest lets ASP.NET read the HTTP values set by a client during a Web request. HttpResponse encapsulates HTTP response i