The following steps describe the procedure required to generate the user controls (form dlls) that are accessed by the VB.NET client at run time:
In Agile Business Suite Developer, create a new bundle, and specify the generator class as (case sensitive) com.unisys.jellygen.GenerateFormVBdotNET or
<CE Installation Directory>\bin\GenerateFormVBdotNET.dll for the .NET version of the generator.
This is the generator that creates individual VB.NET Windows Forms for each ispec and teach screen.
The Java and .NET generator produce the same files with the same content, however the .NET version does not require the Java development kit to be installed if you also set the 'Ispec Models Source Language' to 'C#'.
Generate the bundle. The generated files are created in the .views/langN directory, where N represents the language or locale number.
Open the <Application Name>Solution.sln file in the Ispecs directory. This solution contains all the individual projects for each ispec and teach screen. Build the solution to compile all the projects at once. You can open each project individually to make changes to particular forms if you want.
The compiled .dll files are placed in directories under the <bundle> directory, in a subdirectory of the locale number.
For example, d:\CE\classes\com\unisys\sample\all\1033.
Once the client and Windows Forms have been compiled, copy the example Config.xml file to the bin directory under the client directory. (this is where the project runs in the debugger, and where the .exe file is created) Open the config.xml file, and change the entries to reflect your runtime system, and the settings you used to generate the VB Windows Forms.
Under the directory specified in the LocalDownloadDirectory entry in the config.xml file, create subdirectories for the generated Windows Forms dll files. The subdirectories should be of the form <Package Prefix>\<Application Name>\<Bundle Name>\<locale number>.
For example, d:\CE\classes\com\unisys\sample\all\1033. Copy the individual generated Windows Form .dll files to the directory you just created.
You should now be able to run the VB.NET client application.
The Config.xml File Described
The contents of the Config.xml file are described below. These must be modified, to suit your host runtime system, by opening the file in a text editor and adding the required values. The values contain configuration parameters specific to the host runtime system. The parameters in the following table are those that have been added specifically for running the VB.NET Container via Component Enabler. The parameters to specify whether VB.NET Client session is recorded using the Automated Test Tool (ATT) is also listed in the table.
| Parameter | Description |
|---|---|
| system | The name displayed to the user. |
| PackagePrefix | The package prefix the system was generated with. |
| ApplicationName | The name the system was generated with. |
| BundleName | The bundle with which the system was generated. |
| HostURL | The URL of the host the runtime was deployed to. |
| HostViewName | The view name on the host the runtime was deployed to. |
| ConnectionMode | The terminal type that this client appears as in the Enterprise Application Environment System. |
| StationName | The station name that this client appears as in the Enterprise Application Environment System. |
| HostLogin | The user code to login with. |
| HostPassword | The password to login with. |
| HostDomain | The domain to use for the usercode/password. |
| DownloadServerURL | The URL of the web server to download new/updated forms, lists and images. |
| LocalDownloadDirectory | The directory on the client PC to download forms, lists and images. When using the CE.NET implementation, this is also the root directory where CE looks for the forms, lists and images. |
| DefaultImageType | The default file extension to use for image names. |
| DefaultImageSubDirectory | The sub directory to look for image files. When using the CE.NET implementation, this is a sub directory under the: LocalDownloadDirectory/PackagePrefix/ApplicationName. |
| DisableConsole | When set to true, this prevents the client from starting the console from the menu. |
| DataMaskingEnabled | When set to true, data is masked in the log file at runtime for those fields that have data masking enabled and defined in the model. |
| GIWCompatableBehaviour | When true, the handling of multiple button groups on a form mimicks the way that GIW handles them. that is, if you click a button, all other button groups is set to spaces. |
| LoggingEnabled | When set to true, client logging is enabled. |
| LogFile | The file name to use for the logging. |
| Enable | Specifies whether ATT recording is enabled. Set this to 'true' to enable recording with ATT. |
| Mode | Specifies whether you want to record in 'Connect' or 'Disconnect' mode. For example, Connect. |
| Server | Specifies the socket server used to connect to ATT. Configure this value based on your socket server setting. For example, 127.0.0.1 |
| Port | Specifies the Port used to connect to ATT. Configure this value based on your Port setting. For example, 8888. |
| XmlFile | Specifies the path and name of the file into which the Test Case is recorded when ATT is in the disconnected mode. For example, C:\Testcase.smtest. |
SslProtocolVersion | Defines the protocol version and the corresponding value of a TLS Protocol. The default version of the TLS Protocol is TLS1.2 and its corresponding value is 3072. Following is the list of other protocol versions and its corresponding values:
Refer to https://docs.microsoft.com/en-us/dotnet/api/system.security.authentication.sslprotocols?view=netframework-4.7.2 for more information. Note: The value must match the protocol version of the Server. |
Each configuration file can have multiple system tags. These are to allow for switching between systems by using SWITCH.TO, so that the reports and commands change depending on the system to which they are currently connected.
The system to start with is either the first in the config file, or is identified with the StartupSystem tag.
Tags/parameters that are specific to the VB Client are listed in the following table:
| Tag | Description |
|---|---|
| reports | A block tag to contain a number of report names and descriptions. |
| report | An element for the report name and description. |
| commands | A block tag to contain a number of command names and descriptions. |
| command | An element for the command name and description. |
The following sample is an example of a config.xml file with ATT parameters:
<configuration xmlns="http://tempuri.org/config.xsd" version="1.0">
<startupSystem name="Sample System"></startupSystem>
<system name="Sample System">
<PackagePrefix>com.unisys</PackagePrefix>
<ApplicationName>Sample</ApplicationName>
<BundleName>all</BundleName>
<HostURI>ACUS-IRVINE5</HostURL>
<HostViewName>fredddd</HostViewName>
<ConnectionMode>0</ConnectionMode>
<StationName></StationName>
<HostUserCode>irviner</HostUserCode>
<HostPassword>fredmk</HostPassword>
<HostDomain>.</HostDomain>
<DownloadServerURI></DownloadServerURI>
<LocalDownloadDirectory>d:\java\classes</LocalDownloadDirectory> <!-- also used as the location of files for CE.NET !-->
<DefaultImageType>.jpg</DefaultImageType>
<DefaultImageSubDirectory>images\</DefaultImageSubDirectory>
<DisableConsole>false</DisableConsole>
<DataMaskingEnabled>true</DataMaskingEnabled>
<GIWCompatibleBehaviour>true</GIWCompatibleBehaviour>
<LoggingEnabled>true</LoggingEnabled>
<LogFile>c:\temp\vbclient.log</LogFile>
<ATTRecord enable ="true" mode="connect" server="127.0.0.1" port="8888">
<Xmlfile>c:\Testcase.smtest</Xmlfile>
</ATTRecord>
<reports>
<report name="Report1" description="The description for the Report1 class">
</report>
<report name="Report2" description="The description for the Report2 class">
</report>
</reports>
<commands>
<command name="command1" description="The description for the command1 ">
</command>
<command name="command2" description="The description for the command2 ">
</command>
</commands>
</system>
<system name="SSwitchSeg">
<reports>
<report name="Report1" description="The description for the Report1 class">
</report>
<report name="Report2" description="The description for the Report2 class">
</report>
</reports>
<commands>
</commands>
</system>
</configuration>