• If Version 5.5 was previously installed, the Version 5.5.1 installation upgrades the software to Version 5.5.1. The Versoin 5.5.1 code is merged into the Version 5.5 manager.
• If Version 5.5. was not previously installed, the Version 5.5.1 installation performs a full software install of Version 5.5.1.

You can download the latest product updates from the VisualAge Smalltalk service ftp site.

VisualAge Smalltalk Migration Guide
If you have a version prior to VisualAge Smalltalk Version 5.5 installed, please refer to the Migration Guide for important information before using VisualAge Smalltalk Version 5.5.1. The Migration Guide is installed with the VisualAge Smalltalk Client and is also available on the VisualAge Smalltalk web page .

Product Changes
VisualAge Smalltalk Enterprise has undergone some changes. Your feedback regarding these plans and directions is very important to us. Send comments to us at our vaweb@us.ibm.com email address.

VisualAge Smalltalk Server

VisualAge Smalltalk Server, the runtime environment for deploying server applications, is now included with VisualAge Smalltalk Server Workbench at no additional charge. There is no longer a runtime fee required to deploy VisualAge Smalltalk server applications on NT, Windows 2000, OS/2, Sun Solaris, or AIX.

RPC

The RPC Communications feature has been identified as an obsolete feature. It is still shipped and supported in this version of VisualAge Smalltalk, but it will be removed in the next version.

IMSSimulationSystem

The IMSSimulationSystem feature has been identified as an obsolete feature. It is still shipped and supported in this version of VisualAge Smalltalk, but it will be removed in the next version.

Version 5.5.1 is packaged according to client, manager, or server runtime installation. The files are further packaged according to the target operating system. You can download the files from the VisualAge Smalltalk service ftp site.

Version 5.5.1 Files

You can install the Version 5.5.1 manager and client in a team development environment or as a standalone installation.

Team development environment

To install VisualAge Smalltalk in a team development environment, a system administrator should install the library manager on a network attached server computer. The individual developers can then install the client code locally on their machine and connect to the library manager using EMSRV.

Standalone

If you are working independently of other developers you can install both the library manager and the client code on one machine. It is recommended that you install the library manager before installing the client. If you uninstall the products, uninstall the client first and then the library manager.

1. Download the appropriate files from the VisualAge Smalltalk service ftp site to a temporary directory.

Note:

On OS/2, the Version 5.5.1 files must be unzipped to an HPFS drive because the Version 5.5.1 files contain long file names. If the files are unzipped to a FAT driver, the unzip program will not give you any error messages. However, when you run the installation program it will return errors.

For Server Runtime installation, see the platform instructions under Installing VisualAge Smalltalk.
2. Unzip the Version 5.5.1 files using whatever option your unzip program provides to restore the subdirectory structure of the Version 5.5.1 file. Be sure that your unzip program restores the files with the same case that they were zipped with in the Version 5.5.1 file, or use whatever option your unzip program provides to restore the case of the zipped Version 5.5.1 files. For example:
• Winzip


Check the Use File folders option to restore the file directory structure of the zipped file.

• Pkunzip


Use the -d option to restore the file directory structure of the zipped file.

pkunzip -d va551_cw.zip

• Info-ZIP -- Info-ZIP is available for all VisualAge Smalltalk platforms. See Info-ZIP FTP site .


Info-ZIP restores the directory structure by default.

unzip va551_cw.zip

• Untar

tar -xvf va551_ml.tar

1. If EMSRV is running from the directory to be updated, stop EMSRV prior to installing Version 5.5.1. Use the File I/O option to update the library manager executables.
2. Stop any running VisualAge Smalltalk images.

Windows

Note:

On Windows NT or Windows 2000, logon as a user that is in the Administrator group.

To install on Windows, from the temporary directory where you downloaded and extracted the files from the Version 5.5.1 zipped file, do the following:

1. Change your current working directory to the manager or client subdirectory of the temporary directory:
• cd_m
• cd_c
2. Change directories:

cd install_w

3. Run setup

To install Server Runtime, do the following:

1. Create a directory into which you will install VisualAge Smalltalk on your machine. For example:

d:
mkdir d:\vast55
mkdir d:\vast55\server

2. Change directories to the directory where you will install VisualAge Smalltalk. For example:

cd d:\vast55\server

3. Unzip the server runtime files as follows:

unzip va551_sw.zip

OS/2

To install on OS/2, from the temporary directory where you downloaded and extracted the files from the Version 5.5.1 zipped file, do the following:

1. Change your current working directory to the manager or client subdirectory of the temporary directory:
• cd_m
• cd_c
2. Change directories:

cd install_o

3. Run install

To install Server Runtime, do the following:

1. Create a directory into which you will install VisualAge Smalltalk on your machine. For example:

d:
mkdir d:\vast55
mkdir d:\vast55\server

2. Change directories to the directory where you will install VisualAge Smalltalk. For example:

cd d:\vast55\server

3. Unzip the server runtime files as follows:

unzip va551_so.zip

Unix

Note:

On the Sun platform, create the \opt\IBMvast\5.5 directory before starting to install.

To install on Unix, from the temporary directory where you downloaded and extracted the files from the Version 5.5.1 zipped file, do the following:

1. Change your current working directory to the manager or client subdirectory of the temporary directory:
• cd_m
• cd_c
2. Change your current working directory to a platform-appropriate subdirectory:
• install_a for AIX
• install_h for HP-UX
• install_s for Sun Solaris
3. From the shell command line, run xterm -sb -e ./setup&

Note:

On some Unix platforms, problems have been reported on the Select Features screen. After selecting a new feature to install, sometimes the Next button is not enabled due to an error in synchronization of the features. To correct this problem, select the Back button and then on the License Agreement screen, select the Accept button. The Next button on the Select Features screen should then be enabled.

Note:

The installer writes installation status messages to its stdout stream. These messages will appear within the dtterm or xterm where the installer was started.

For Server Runtime on UNIX, the files are tarred to absoluate paths. You must decompress and untar them. To install Server Runtime, do the following:

AIX

Decompress and untar as follows:

mv va551_sa.taz va551_sa.tar.Z;zcat va551_sa.tar.Z|tar -xvf -

Sun

Decompress and untar as follows:

mv va551_ss.taz va551_ss.tar.Z;zcat va551_ss.tar.Z|tar -xvf -

Linux

To install a manager on Linux:

1. You should have already downloaded the Linux manager code va551_lm.taz to a temporary directory.
2. Move the Linux manager code into the /opt subdirectory tree:

mv va551_lm.taz va551_lm.tar.Z;zcat va551_lm.tar.Z|tar -xvf  -

3. Perform a VisualAge Smalltalk Manager install on one of the supported platforms (Windows, OS/2, AIX, HP-UX, Solaris) to populate the manager file.
4. FTP the <varoot>\manager\mgr55.dat file to the /opt/IBMvast/5.5/manager directory on your Linux machine.

NetWare

To install a manager on NetWare:

1. You should have already installed the executables by downloading the NetWare manager code, va551_nm.zip, and unzipping it into a temporary directory.
2. Copy emsrv.nlm into the SYS:\SYSTEM directory on your NetWare file server.
3. Install VisualAge Smalltalk Manager on one of the supported platforms (Windows, OS/2, AIX, HP-UX, Solaris) in order to populate the VisualAge Smalltalk Manager file.
4. Copy the <varoot>\manager\mgr55.dat file to its desired location on your NetWare file server.

If you had previously installed Version 5.5, before you use VisualAge Smalltalk Version 5.5.1, do the following:

1. Version and release all open editions of classes and subapplications, and version the applications.
2. Save to files any text from workspaces or from the Transcript window that you want to keep.
3. After you complete the install, you can then load your versioned work from the new Version 5.5.1 manager into the VisualAge Smalltalk Version 5.5.1 client.

After you install, you must unlock VisualAge Smalltalk Enterprise, and any features you installed. All products are initially installed as evaluation products. When you purchase a product, you receive a key which you use to unlock the evaluation product. If you load an evaluation feature into your image, even if you unlocked VisualAge Smalltalk Enterprise, your image will become an evaluation image. When you unload the evaluation feature, your image will still be an evaluation image.

For this reason, be sure to unlock all features you have purchased before you load them into your image. If you want to try a feature that you have not purchased, be sure to make a backup copy of your image file (abt.icx) before you load the evaluation feature. Then, try the feature. When you are through, you can restore the image you backed up before you loaded the evaluation feature.

• Support for FAT32 volumes on Windows 2000
• Support for PAM authentication on Linux and Solaris platforms
• Support for DCE authentication on AIX platforms
• Support for NetWare 5.1
• Support for Red Hat Linux 6.1 and 6.2
• Support for AIX 4.3.3
• Support for authentication using Active Directory Services on Windows 2000
• Support for cross-domain authentication on Windows NT

• Hardcopy documentation is no longer provided. All manuals are online documentation in HTML format, which you can view with a Web browser such as Netscape Navigator or Microsoft Internet Explorer. All manuals are also provided in PDF format at the VisualAge Smalltalk web page .
• The VisualAge Smalltalk Search page now allows you to select from different generic areas from which to narrow your search. For example, you can choose the Database Guide to search both the Database Guide and the Database Help. There are also pushbuttons to allow you to select the genre of books you would like to search:
• Select VisualAge items
• Select Smalltalk items
• Select Server items
• The following documents are new:
• VisualAge Smalltalk Server Smalltalk Guide, which includes information formerly in the VisualAge Smalltalk Server Guide.
• VisualAge Smalltalk Advanced Database Guide, which includes information about the Advanced Database feature for VisualAge Smalltalk .
• The following documents have had significant format changes:
• All part reference information was put into the VisualAge Parts Reference.
• Server information for features was moved from the VisualAge Smalltalk Server Guide to the specific feature guide.
• Help information for specific features was moved into the HTML manual for that feature.
• The following documents have been updated for Version 5.5.1
• VisualAge Smalltalk Installation Guide
• VisualAge Smalltalk Parts Reference
• VisualAge Smalltalk Server Guide
• VisualAge Smalltalk Server Smalltalk Guide
• VisualAge Smalltalk User's Guide
• VisualAge Smalltalk Web Connection User's Guide
• VisualAge Smalltalk Ultra Light Client Guide and Reference
• IBM Smalltalk Programmer's Reference
• IBM Smalltalk User's Guide

For example, if you wish to change to the en_US locale, set your LANG environment variable to en_US before starting VisualAge Smalltalk with the ksh command. For example:

export LANG=en_US

locale -k LC_MONETARY

int_curr_symbol="USD "
currency_symbol="$"
mon_decimal_point="."
mon_grouping="3"
mon_thousands_sep=","
positive_sign=""
negative_sign="-"
int_frac_digits=2
frac_digits=2
p_cs_precedes=1
p_sep_by_space=0
n_cs_precedes=1
n_sep_by_space=0
p_sign_posn=1
n_sign_posn=1
debit_sign="DB"
credit_sign="CR"
left_parenthesis="("
right_parenthesis=")"

The Slider part still functions normally.

Base


On Solaris version 8, UNIXProcess class>>#system: call may have problems On Solaris, if you are encountering odd behavior when using the UNIXProcess class>>#system: call to execute C shells, your problem might be that your call is using the wrong version of the libcurses.so library. When you start Smalltalk with the abt shell script, the LD_LIBRARY_PATH is set so that /usr/ucblib is searched before the /usr/lib path. Many Solaris executables will not work correctly if they are linked to /usr/ucblib/libcurses.so at runtime. To workaround this problem, in /opt/IBMvast/5.5/bin, create a link named libcurses.so.1 that points to /usr/lib/libcurses.so.1.

Clients and Managers should be in synch with each other You should install the same features on the VisualAge Smalltalk Client that you install on your Visual Smalltalk Manager. If you install features on the VisualAge Smalltalk Manager and do not have these same features installed on the VisualAge Smalltalk client, you will still see these features listed in the Load/Unload Dialog window of the VisualAge Smalltalk client. However, if you load these features on the VisualAge Smalltalk Client, VisualAge Smalltalk will not install the required code and they may not function properly due to missing files. Error messages such as unresolved strings (because of the missing cat files), missing ICs, missing sample files, and anything else that gets copied as part of the client install of that feature may then appear in the System Transcript window.

On MVS, INIs are optional for packaged applications. All other platforms, INIs are required for packaged applications On MVS, an .ini file is optional. On all other platforms, an .ini file is required. The .ini file may have the same name and be in the same directory as your executable (on Unix, the executable is es or esnx). The .ini file can also have the same name and be in the same directory as your .icx or .ic file.

In addition, you can specify your .ini file as a command line parameter. For example, you can launch your program by typing the following:

abt -imyapp.icx -ini:c:\any.ini

All methods supporting the ANSI Smalltalk protocol are categorized as ANSI-API. Methods associated with ANSI Smalltalk function that are not complete in this release are categorized as ANSI-Unimplemented.

The following restrictions with respect to ANSI Smalltalk are in force for this release:

1. The following DateAndTime methods are not functional:
• clockPrecision (factory method)
• now (factory method)
• year:day:hour:minute:second: (factory method)
• year:month:day:hour:minute:second: (factory method)
• timeZoneAbbreviation
• timeZoneName
2. The following Exception methods are not functional:
• isNested
• outer
• pass
• resignalAs:
• retry
• retryUsing:
3. The MessageNotUnderstood exception class is provided, but is not signaled by the standard #doesNotUnderstand: method.
4. The ZeroDivide exception class is provided, but is not signaled when a divide by zero occurs.

1. A ScaledDecimal literal is now supported. The format of this literal is:

<integer-part>[.[<decimal-part>]]s[<scale>].

Here are some examples of ScaledDecimal literals:

3.4s     1274s5     0.88s     0.96s1

2. The ScaledDecimal>>#printOn: format has been changed to match the format of the ScaledDecimal literal. The old format of printing ScaledDecimal is still available for compatibility purposes by using the ScaledDecimal>>#printOn:showDigits:pad: and specifying true for the showDigits parameter.
3. The format of the string parameter for ScaledDecimal class>>#fromString: has been changed to match the format of the ScaledDecimal literal. The old string format is still supported for comparibility purposes.
4. The ScaledDecimal>>#debugPrintOn: method has been added so that inspecting a ScaledDecimal object does not lose detail due to the new ScaledDecimal>>#printOn: format.

Additional Float literals are now supported by extending the possible values of the exponent character. The exponent character now has the following meaning:

d - Single Precision Float
e - Double Precision Float
q - Quad Precision Float

1. Change the LC_TIME definition for your desired locale. Consult the man pages for locale and localedef information.
2. To enable your timestamps to appear in 24-hour format, execute the following code in Smalltalk:

NlsGlobals::CurrentLCTime tFmt: '%H:%M:%S'

To enable your timestamps to appear in 12-hour format, execute the following code in Smalltalk:

NlsGlobals::CurrentLCTime tFmt: '%I:%M:%S %p'

Windows 95, Windows 98, Windows NT, Windows ME, and Windows 2000

1. If you are using a LAN adapter configuration, ensure the following:
• You must have DNS enabled with a valid host and domain name.
• Your LAN DNS must resolve localhost to 127.0.0.1
• You must run connected with the LAN adapter configuration.
2. If you are using a Dial-Up Adapter configuration, ensure the following:
• You must have DNS disabled.
• Your TCP/IP Address must be obtained automatically.

Note:

These configuration options will apply to all TCP/IP adapters even though they have only been changed for this particular Dial-Up adapter. You will not be able to use both LAN and Dial-Up unless you reconfigure.

3. If you are running standalone, you can enable the MS Loopback Adapter without enabling the other two adapters.

OS/2

1. Enable local loopback by performing the following steps:
1. Open the OS/2 TCP/IP folder.
2. Open the TCP/IP Configuration notebook..
3. View the Network page.
4. In the listbox labelled Interface to Configure, highlight the item labelled loopback interface.
5. Verify that the checkbox on the right labelled Enable interface is checked.
6. With loopback interface still highlighted, verify that the entry field for IP address is 127.0.0.1 and that the Subnet Mask is empty.
2. Verify that localhost is enabled on your system by doing the following:
1. On any OS/2 command line enter ping localhost. This command should return some data back rather than just hang. If it hangs, or if it returns localhost unknown, then localhost has not been enabled on your system. If you are on a network, then make sure loopback is enabled. If you are not on a network, enable localhost by performing the following steps:
1. Adding the following line after other ifconfig lines in the MPTN\BIN\setup.cmd command file:

 ifconfig lo 127.0.0.1

2. In the TCP/IP configuration:
1. Go to the Configure Name Resolution Services page (page 2 of Hostnames).
2. Add an entry to the table titled Hostname configuration without a Nameserver. Set the IP Address to 127.0.0.1 and the Hostname to localhost. If you have a host name specified for your machine on page 1 of "Hostnames" (titled Configure LAN Name Resolution Services), then you must add this host name as an alias while you are setting the IP Address 127.0.0.1 to localhost.
3. Check the check box underneath the table labeled: "Look through HOSTS list before going to nameserver." This will enable localhost to bypass any nameserver to resolve the name.
4. Close TCP/IP Configuration and reboot and the system.
5. You should be able to ping localhost without being connected to any network. If ping localhost still hangs, remove any nameservers from the TCP/IP configuration so that name resolution can be done only by looking at the HOSTS list.
3. Verify that your hostname is correct by doing the following:
• From an OS/2 command line, enter hostname.
• Verify that the hostname returned is the same as the one listed in the TCP/IP Configuration notebook on the Hostnames page and verify that the hostname is less than 32 characters.
4. If any TCP/IP settings were changed, be sure to reboot OS/2 and restart TCP/IP.

If you use Internet Explorer or Netscape with a firewall (proxies enabled), then you must modify the default settings for help to work properly.

Windows -- Internet Explorer 5

1. Select Tools... Internet Options.
2. Select the Connection tab.
3. Click LAN Settings.
4. Select the Bypass proxy server for local addresses checkbox.

Note:

This checkbox is only available if you are using a proxy or socks connection and have selected the "Use a proxy server" checkbox.

5. Select the Advanced button.


Type localhost:49213 in the Exceptions... Do not use proxy servers for addresses beginning with box. If you have other entries here, separate the new entry with a semi-colon.

6. Click OK, then click OK again to exit the LAN Settings dialog, and click OK again to exit the Internet Options dialog.

Windows -- Netscape 4 (Navigator)

1. Select Edit... Preferences...
2. Double-click Advanced in the Category tree.
3. Click Proxies in the Advanced subtree.
4. Click View at the Manual Proxy Configuration selection.
5. Type localhost:49213 in the Exceptions... Do not use proxy servers for addresses beginning with box. If you have other entries here, separate the new entry with a comma.
6. Click OK, then click OK again to exit the Preferences window.

1. Edit the Hummingbird configuration file SOCKS.CNF
2. Add the line:

 DIRECT 127.0.0.1 255.255.255.255

3. Save the file.

OS/2

1. If you are using a SOCKS client, be sure that 127.0.0.1 is accessed directly and not resolved by the SOCKS server.
2. You can tell if your SOCKS client needs to be configured by using FTP. Try to FTP to localhost or to 127.0.0.1. If you cannot FTP, then your SOCKS client may need to be reconfigured. You must also have the LoopbackAdapter enabled (see HTML Help TCP/IP requirements.)
3. Depending on your SOCKS client, you may need to restart your system for the new settings to take effect.

To workaround this problem, you must add the DB2 libraries. You may want to add the one of the following examples to your profile.

HP:   export SHLIB_PATH=/home/db2inst1/sqllib/lib:$SHLIB_PATH
Solaris: export LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib:$LD_LIBRARY_PATH

1. Logon to SQL*PLUS

sqlplus userid/password

2. Execute the file

SQL> @vast\samples\oracle\sample.sql

You can also check your DBRM for ODBC drivers. Most, if not all, major DBRMs now ship with ODBC drivers.

On AIX, database features require extracting shared library Before you can run the database features on AIX, you must extract a shared object from the appropriate archive file. This is true for IBM DB2, ODBC, and Oracle databases.

IBM DB2

1. Extract the shared object

ar -x libdb2.a

2. Rename the extracted file libdb2.so

mv shr.o libdb2.so

ODBC

1. Extract the shared object

ar -x libodbc.a

2. Rename the extracted file libodbc.so

mv libodbc.o libodbc.so

Oracle

1. Extract the shared object

ar -x libclntsh.a

2. Rename the extracted file libclntsh.so

mv clntsh.o libclntsh.so

If you package your application and get the error The attribute Pub <Attr name> does not exist at runtime, you need to include the AbtRecordStructureApp application.

On Unix, running Database Features On Unix, if you are using database features and experience a core dump when exiting VisualAge, comment out the PlatformLibrary>>shutDown method. An alternative solution for your packaged application is to execute the following code when exiting:

System primitiveExit

For example, at a command line, enter either: emsrv.shadow -w -xd21 -xd24 -lc -lf logfile or emsrv -w -xd21 -xd24 -lc -lf logfile.

This example should read:

For example, at a command line, enter either: emsrv.shadow -w -xd21 -xd24 -lc -lflogfile or emsrv -w -xd21 -xd24 -lc -lflogfile.

Starting EMSRV process In the Installation Guide, in the Configuration and Startup section, under VisualAge Smalltalk Manager, a step for starting the EMSRV process reads:

/opt/IBMvast/bin/emdevnum /opt/IBMvast/5.5/manager/mgr55.dat

/opt/IBMvast/5.5/bin/emdevnum /opt/IBMvast/5.5/manager/mgr55.dat

START EMSRV -u <userid> <password>

EMSRV -u <userid> <password>

• Backup the manager file regularly.
• Run library statistics utilities on a regular basis to ensure the integrity of the manager file.
• Protect the manager file.

semsys:seminfo_semmni = 2048
semsys:seminfo_semmap = 2050
semsys:seminfo_semmns = 4096
semsys:seminfo_semmnu = 4096
semsys:seminfo_semmsl = 50
shmsys:shminfo_shmmax = 6291456
shmsys:shminfo_shmseg = 300
shmsys:shminfo_shmmni = 300

If you have additional indexes that exist due to the installation of other products that use NetQuestion, then these values may need to be increased. Changing these values will require a reboot of the system. See the system(4) man page for further information on the /etc/system file on Solaris.

For HP-UX, there is help available inside of SAM. This is necessary because NetQuestion requires 9 semaphores plus 45 additional semaphores for every index.

On UNIX, Netscape 4.7 On the UNIX platform, if you use Netscape 4.7, VisualAge Smalltalk may not be able to bring up Netscape when you try to access the help system. To workaround this problem on HP and SUN, bring up Netscape manually before accessing the VisualAge Smalltalk Help. On AIX, bring up Netscape manually and type in the following URL :

http: //localhost:49213/cgi-bin/abtwebx.exe/en_US/q/Extract/5.5/abtzva55/vast.htm

1. Make <varoot>\inst your current directory.
2. Copy the netq.iss file to a directory name that does not require quoting (i.e., does not contain spaces or other special characters).
3. Edit the abtnq_b.cmd file.
4. Modify the line that starts with install.exe so that it points to the new location of the netq.iss file.
5. Save the abtnq_b.cmd file and execute it

• Direct connection to the Internet
• Manual proxy

aBO dataObject

aBO dataObject 
                pullDown: aBO;
                yourself

[VapDepartmentHome singleton findByPrimaryKey: aKey] when: 
   VapExceptions::ExVapException
     do: [:sig||abtError| (abtError := sig asVapAbtError) rc = 100
           ifTrue: [self log: 'Department not Found: ',abtError errorText]
           ifFalse: [sig signal "This handler is finished - re-signal for other handlers"]].

1. Select AbtNlsCfsSupportApp in the left pane.
2. Press the >> button. (It will be highlighted. There are two of these buttons. You want to press the one on the left that is below the left and/or center panes).

sstRmiClassName

Answers the Java class name the receiver is mapped to.

sstIsRmiSerializable

Answers true if the receiver is serializable (passed by value).

sstIsRmiRemotable

Answers true if the receiver is remotable (passed by reference).

By default, Smalltalk MQ calls will use the unthreaded libraries. To switch to the threaded libraries, before making your first MQ call, execute the call AbtMQSeriesBaseUnixSubApp threaded.

Server Runtime V5.5 incompatible with ServerWorkbench V4.5 and V5.0 Server Runtime V5.5 is not upward compatible with Server Runtime V4.5 or V5.0. This means that applications packaged with Server Workbench V4.5 or V5.0 will not run on a Server Runtime 5.5 system. To workaround the problem, use one of the following options:

1. Repackage your application using Server Workbench 5.5.
2. Keep Server Runtime V4.5 or V5.0 installed in parallel with Server Runtime V5.5 on those systems that need to run applications packaged from both releases.

Please refer to our web page located at http://www.software.ibm.com/ad/smalltalk/downloads/vacodepage.html for a Windows-only example that demonstrates usage of a custom code page routine.

ULC


ULC 3.0 supported The ULC feature of VisualAge Smalltalk Version 5.5 has changed since Version 5.0. VisualAge Smalltalk Version 5.0 supported ULC 1.5. VisualAge Smalltalk Version 5.5 supports ULC 3.0.

On OS/2, ULC Client must be installed on a HPFS Driver On OS/2, the ULC Client (UIENGINE) must be installed on an HPFS driver due to it's use of long file names.

Loading and Running the ULC Examples If you are using the Ultra Light Client Component of the Server Workbench Feature, you may want to load the examples that ship with the product. (To conserve space, these examples are not automatically loaded into your image.) To load these examples, select the VA: ULC - Examples feature from the Tools -> Load/Unload Features pulldown on the transcript window.

You must have a ULC UI Engine running on your development machine to run these examples. Also, to run the Hierarchy Browser or Dossier ULC examples directly from the transcript window pulldown (ULC -> Examples -> Hierarchy Browser or Dossier), you must first copy the bitmaps subdirectory in the ULCSamples directory to the image directory in your VisualAge Smalltalk root directory. One way to do this is to create a new bitmaps subdirectory in the image directory and copy the ULC bitmaps into this new bitmaps subdirectory.

Description of ULC files that must be installed separately When you install the Server Workbench Feature, a subdirectory named ulc is added to your VisualAge Smalltalk V5.5 root directory. In this subdirectory, you will find 4 files. If you plan to use the new ULC component of the Server Workbench feature, you will need to install these 4 files using the instructions in the appropriate readme files, as described below.

Ulcouie.exe

For all installations, a self extracting zip file with the OS/2 version of the UI Engine for your OS/2 client machines and your OS/2 development machine.

Ulcouie.txt

For all installations, a readme with installation instructions for the above file, Ulcouie.exe

Ulcwuie.exe

For all installations, a self extracting installation program for the Windows version of the UI Engine for your Windows client machines and your Windows development machine.

Ulcwuie.txt

For all installations, a readme with installation instructions for the above file, Ulcwuie.exe

1. Change directories (chdir) to the the VAST 5.5 installation directory (<vast55>\inst) and execute the following commands from the command line:
2. Execute the command:

abtrmixs.bat

3. Execute the command:

erase runrmixs.bat

4. Execute the command:

uninst.exe -z.c

1. In the AbtWebServerInterfaceBaseApp>>AbtWsiConnection>>#handleTransaction: method, change the ExAll exception reference to ExError.
2. In the AbtWebServerInterfaceBaseApp>>Block>>#abtWsiAtEndOrWhenExceptionDo: method, replace the code with the following:

abtWsiAtEndOrWhenExceptionDo: completionBlock
  " Code hacked to enable debugging in XD runtime image via
  the interactive debugger "
 
  self value.
  completionBlock value

After making the above changes, package the application and execute it as usual.

Note:

Be sure to load the original code prior to packaging the application for production.

Eventually, a Smalltalk debugger appears with the following error message: Could not create socket pair: ETIMEDOUT (10060): Connection timed out. To correct this problem, enable loopback on OS/2 by performing the following steps:

1. Open TCP/IP Configuration windows.
2. Select loopback interface from the Interface to Configure list box.
3. Select the Enable interface check box.
4. Close the TCP/IP Configuration window.

ping 127.0.0.1

After successfully configuring loopback, you should be able to use the sst-http interface from OS/2.

Packaging an image with Web Connection image components To package your Web Connection application so that it utilizes the Web Connection image components, you must implement a packager method to force inclusion of your web parts in the packaged image.

For example, implement the following method as a class method of the application containing your web connection parts.

packagerIncludeClassNames
 
   ^self defined collect: [:i | i name ]

<Error: No Form - Multiple Select>
<Error: No Form - Single Select>

For example, the sample application AbtWebSamplesApp is now headless by default because it does not include the prerequisite AbtRunHtmlPageApp. When the packaged image for this sample is started, no windows will open. The application AbtWebSamplesApp can be loaded into a passive XD image and packaged if desired.

The application AbtWebSamplesWithMonitorUIApp contains prerequisites to include the Web Server Interface Monitor as well as all the sample parts from AbtWebSamplesApp. This application cannot be loaded into an XD passive image.

In the example below, M.Pogue has subordinate A.Bagchi, but A.Bagchi is defined AFTER M.Pogue. This currently causes a validation error because subordinates is an IDREFS field.

<personnel>
  <person id="M.Pogue" >
    <name><family>Pogue</family> <given>Mike</given></name>
    <email>mpogue@us.ibm.com</email>
    <link subordinates=" A.Bagchi"/>
  </person>
 
  <person id="A.Bagchi">
    <name><family>Bagchi</family> <given>Anupam</given></name>
    <email>abagchi@us.ibm.com</email>
    <link manager=    "M.Pogue"/>
  </person>
</personnel></xmp>

abtValidateAttributeValue: aValue forHandler: anAbtSaxHandler
        " Make sure that passed id value exists in this document  "
 
        ( anAbtSaxHandler document idTable  includesKey: aValue )
                ifFalse: [ anAbtSaxHandler unresolvedIdRefs add: aValue ].
 
        " Always answer true.  Unresolved references will be reported after parsing completes "
        ^true

Change the following code:

self printAttribute: attrMap attribute 
        value:  (anObject abtAtAttribute: attrMap classAttribute asSymbol) 
        toStream: aStream ]]

self printAttribute: attrMap attribute 
        value:  (anObject abtAtAttribute: attrMap classAttribute asSymbol) 
        on: aStream ]]

Testing XML request handlers over HTTP

1. From the VisualAge Organizer, select the AbtXmlServerSamplesUIApp application.
2. Select the AbtXmlSampleHttpClientTesterView part.
3. Enter an XML string or a piece of code that evaluates to an XML string

AbtXmlSampleCustomerRequest xmlTestString1      
AbtXmlSampleCustomerRequest xmlTestString2

4. From the Actions menu, select the Open WSI monitor option to bring up the Web Server Interface monitor. Follow the instructions in the Web Connection User's Guide to start a WSI server with transport type wsi-tcp
5. Specifiy the URL that will handle the request:

 http://myserver/cgi-bin/abtwsac.exe/AbtXmlSampleCustomerRequestHandler

6. Enable the Options->Inspect result option so that you can view the returned XML response string
7. Select the code string in the text box, and select the Actions->Evaluate and send menu option (or use pop-up menu for text box).

After the command is processed, an inspector should open to display an XML string that contains the results.

Testing XML request handlers over sockets (very similar to the steps for testing over HTTP)

1. From the VisualAge Organizer, select the AbtXmlServerSamplesUIApp application.
2. Select the AbtXmlSampleSocketClientTesterView part.
3. Enter an XML string or a piece of code that evaluates to an XML string

AbtXmlSampleCustomerRequest xmlTestString1      
AbtXmlSampleCustomerRequest xmlTestString2

4. From the Actions menu, select the Open WSI monitor option to bring up the Web Server Interface monitor. Start a WSI server with transport type xml-tcp and select the request handler class that you wish to use for handling incoming requests on the socket. For example:

 AbtXmlSampleCustomerSaxRequestWsiHandler

5. From the XML socket client tester view, specify the server and port number for the request that is to be made (the same server and port from step #4 above).
6. Enable the Options->Inspect result option so that you can view the returned XML response string.
7. Select the code string in the text box, and select the Actions->Evaluate and send menu option (or use pop-up menu for text box).

After the command is processed, an inspector should open to display an XML string that contains the results.

1. Create a subdirectory named xml from your VisualAge base client directory. For example:

 mkdir xml

2. Copy the xml files from the directory /opt/IBMvast/5.5/xml to the newly created xml directory. For example:

cd <vast client directory> /xml
cp /opt/IBMvast/5.5/xml/*.* .   

packagerIncludeClassNames
| handlers |
  handlers := AbtXmlServerSamplesApp defined select: [:aClass | 
     aClass inheritsFrom: AbtXmlWsiHandler ].
  ^handlers collect: [:aClass | aClass name ]

1. Parse an XML file to construct a DOM (document object model).
2. Send the #mapUsing: method to the DOM and pass it a valid instance of the AbtXmlMappingSpec class.

For example, the #packagerIncludeClassNames packager method (a class method) can be implemented in the application class. For example, if MyModel1 and MyModel2' are classes in MyApplication, then the method below should be implemented as a class method in MyApplication.

packagerIncludeClassNames
   " Include class names that might be constructed via XML mapping "
 
   ^#(MyModel1 MyModel2)

The following code pages are not supported:

• EUC_JP conversion is not properly supported by native Windows code page routines. A Windows implementation of ICONV supports EUC_JP. To download ICONV, see http://www.ibm.com/software/ad/smalltalk/downloads/vacodepage.html Using the ICONV support, additional code pages, including EUC_JP, can be supported.
• The code page ISO-2022-JP is not supported by native routines or by ICONV.

AbtXmlStreamConverter mapEncoding: 'UTF-8' toCodePage:  65001.

Abt.Nls.160.e: Conversion from code page <sourceCodePage> to code page <targetCodePage> is not supported.