Release Notes Synapta Presentation Builder
Attachmate Synapta Presentation Builder Version 4.0 October 2004


This file contains late-breaking information about this release of Attachmate Presentation Builder.

In addition to this product-level readme file, there is a Management & Control Services readme file, readme_mcs.htm, included in this product that addresses specific MCS issues.

New since the Release of Presentation Builder 3.0

For more information about these features refer to the topic, What's New in Presentation Builder, in the Getting Started Guide.

Installation Notes

Installing MCS and Management Components with Windows XP SP2

During the installation of MCS or an MCS management component, you may see a Windows security alert one or more times. This message is displayed only if you use Windows XP with the Windows XP firewall enabled (as it is by default). The message asks you if you want to keep blocking the program java or javaw. To continue with the installation, when you see this message, click Unblock.

After you click Unblock, these programs are logged in the Windows Firewall Exceptions page. Although not evident on this page, the entire path to the program has been saved. Running either program from the logged location does not display the security alert; however, running them from a different location will cause the alert to display.

Installing Over Presentation Builder v. 3.0

For important details about installing over Presentation Builder v. 3.0, refer to the Presentation Builder Getting Started Guide, available by opening the file start_here_presentationbuilder.htm from the root folder of your Presentation Builder CD-ROM.

Republish Presentations to MCS After Upgrade from Presentation Builder v. 3.x

If you are upgrading from Presentation Builder version 3.x, your existing projects will be automatically updated when you open and save them in Presentation Designer. To retain a copy of your projects from the earlier version, you should back up your \Program Files\Attachmate\EAI\PresentationDesigner\Projects directory before opening a project in Presentation Designer. Before your applications and presentations can be used in the current version of the Runtime Service, you'll need to republish them to MCS.

Projects Not Migrated with Upgrade from Presentation Builder v. 2.0

When you install a new version of Presentation Builder to upgrade from Presentation Builder v. 2.0, existing projects won't be migrated. For more information, contact the Customer Support department at Attachmate Corporation.

Upgrading Presentation Manager and Application Manager

When upgrading the Presentation Manager and Application Manager components of Presentation Builder, you need to reboot your server machine after the upgrade is complete.

Uninstaller Lists Components Multiple Times

When different components have been installed from different CDs that have common components, such as MCS, the uninstaller dialog will list these common components, such as MCS, more than once. The common component will be listed under each main header section. Make sure that all references to a given component are treated the same, either checked or unchecked.

Officially Supported JRE

The officially supported JRE for Presentation Builder 4.0 is J2RE SE, version 1.4.2_02.

Netscape 7.1 Overwrites the Default Java Plug-in

If you install Netscape 7.1 on a client machine that already has J2RE SE, version 1.4.2_02, Netscape overwrites J2RE, SE. When you access the Management & Control Services (MCS) server, you will see a warning message about a mismatch in the Java Plug-in and a request to install the plug-in.

To restore the Java Plug-in
  • Uninstall J2RE, SE v. 1.4.2_02 and reinstall it.

    When you access MCS, you will be given an option to reinstall the J2RE, SE v. 1.4.2_02 from either the Java Sun Web site at or from MCS.

    If you try to launch a presentation from the myAccess Links page on a client machine with no JRE, you will be prompted to install J2RE, SE.

    Note From the Java Plug-in Control Panel, on the Browser tab, be sure the Netscape option is selected during the installation of J2RE.

Installing on Solaris 7, 8, and 9

Prior to installing on the Solaris 7, 8, and 9 operating environments, you should be sure that you have installed the full set of recommended Sun patches needed for support of Java 2 SDK 1.4.2_02. Recommended and required patches are available for download on the SunSolve Web site at

Known Issues

Using 3270 Model Sizes Other Than Model 2 for 3270 Connection Settings

The default model for the custom device type for a 3270 connection in Presentation Builder is Model 2. Models 3, 4, and 5 are supported, but must be configured manually to specify model size, and/or to specify a resource when connecting without TN3270 Enhancements enabled.

In the Terminal/Device Type field, selecting either IBM-3278 or IBM-DYNAMIC will connect Model 2, EAB's supported.

To manually configure the custom device type
  1. From the Host menu, choose New Connection or, to change an existing configuration, choose Host Settings.

  2. In the Host Settings dialog box, under Connection Settings, on the General page, modify the Custom Device Type using a valid entry listed in the table below.

    Custom evice type Definition
    IBM-3278-2 IBM-3278 Model 2 *
    IBM-3278-3 IBM-3278 Model 3 *
    IBM-3278-4 IBM-3278 Model 4 *
    IBM-3278-5 IBM-3278 Model 5 *
    IBM-3278-2-E IBM-3278 Model 2
     EAB's supported
    IBM-3278-3-E IBM-3278 Model 3
     EAB's supported
    IBM-3278-4-E IBM-3278 Model 4
     EAB's supported
    IBM-3278-5-E IBM-3278 Model 5
     EAB's supported
    IBM-3279-2 IBM-3279 Model 2 *, #
    IBM-3279-3 IBM-3279 Model 3 *, #
    IBM-3279-4 IBM-3279 Model 4 *, #
    IBM-3279-5 IBM-3279 Model 5 *, #
    IBM-3279-2-E IBM-3279 Model 2 #
     EAB's supported
    IBM-3279-3-E IBM-3279 Model 3 #
     EAB's supported
    IBM-3279-4-E IBM-3279 Model 4 #
     EAB's supported
    IBM-3279-5-E IBM-3279 Model 5 #
     EAB's supported

Note *  In the Attachmate implementation, EAB's are always supported, even if the Custom device type does not specify this.

#  IBM-3279 is a graphics terminal. However, Attachmate implementation does not support APL, graphics, and so on.

To select a specific resource when connecting without 3270 Enhancements enabled
  • Add the following to the end of any of the custom device types specified in the preceding table:


  • Note The resource name is provided by the userís system administrator. For example, IBM-3278-2-E@theresource.

Default Security Option in Windows XP SP2 Restricts JavaScript in Help

The Presentation Builder help uses JavaScript. Windows XP SP2 includes the security option Local Machine Zone Lockdown, which by default restricts JavaScript from running in Internet Explorer. If you use Internet Explorer, by default, when you attempt to display the help, a message is displayed in the Information bar stating that Internet Explorer has restricted the help from showing active content.

To display the help
  • Click the Information bar, and then click Yes to allow active content.
  • Note You must do this each time you view the help.

Alternatively, you can lower your security settings to avoid seeing this message. However, this change will apply to all files that include active content, and Microsoft does not recommend this approach. For more information about Local Machine Zone Lockdown, see the Microsoft Web site.

Modify Screen Recognition Rule for Table Control Navigation to Multiple Screens to Avoid Lockup of the Designer

When defining a table control for navigation to multiple screens, you must modify the screen recognition rule so that those screens can be recognized as the same form.

If you switch from Customize to Interactive while viewing the form that contains the table control and table navigation goes to a different screen than where it started, the screens are not recognized as the same and the designer may lock up.

Using Tasks from Services Builders for IMS or CICS

When using tasks exposed by the Services Builders for IMS or CICS within the AXIS Web Service environment, a known error condition may occur. If the defined IMS/CICS task is defined with a task input area of smaller size than the task output area, execution errors will result. The workaround to this error is as follows:

To successfully use tasks from Services Builders for IMS or CICS
  1. Locate the taskfile containing the task that was produced by the Designer Studio for IMS or CICS. This taskfile should be located (for IMS) in the install directory, \EAI\IMSTaskDesigner\Metadata, or (for CICS), in the install directory, \EAI\CICSTaskDesigner\Metadata.

  2. Manually edit this taskfile. Find the transaction ID=yourTaskName tag in the taskfile, where "yourTaskName" is the task that had the error condition. Within that tag, find the appinfo tag, and locate the InputLength= and OutputLength= attributes within the appinfo tag. Edit the value of the InputLength attribute to increase it to the same value as the value set to the OutputLength attribute.

  3. Save the taskfile, and open the Services Builder for IMS (or CICS).

  4. Select the Generate function of the Services Builder, by selecting the appropriate toolbar button, the Generate button in the Services Builder Guide, or the Generate option from the Tools menu.

  5. Select the taskfile manually edited in step 2 from the list of taskfiles provided, and choose the Next button.

  6. From the Web Services menu, select the Apache Axis option. Generate the AXIS Web Service, then use the standard procedure to rebuild and deploy the result to the AXIS environment again.

  7. Refresh the Tomcat service to pick up the revised Web Service objects.

Host Screen Forms Have Issues When Published as HTML

Host screen based forms that are set as static forms and published as HTML have issues if the host field is padded with spaces and the input/output binding is defined on the UI control.

Memory Management for Increased Performance

The Java VM allows for specific memory tuning for increasing performance. The default settings of the installed environments are just a baseline in most cases. To increase performance, depending on the memory installed on your computer, it may be to your advantage to increase the amount of memory allocated to the Java VM.

To modify the memory used in the Presentation Designer
  • Open the PresentationDesigner.lp file and change the javaoptions setting.

To modify the memory used in the Presentation Builder Runtime Service
  1. Open the Registry Editor, and locate the following folder:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ATTM HTTP Engine\Parameters

  2. Modify the default values for the following keys:
    Key Default Value
    JVM Option Number 2 -Xms256m
    JVM Option Number 3 -Xmx256m

  3. Note Sun recommends that you set these values to the same size.

    For additional information on setting the values for -Xms and -Xmx, see the Java Technology page.

  4. Restart HTTP Engine.

Terminal Viewers with Windows 98 Second Edition

If problems arise when using Terminal Viewers and Windows 98 Second Edition, please install JDK or JRE v. 1.3.0x prior to downloading. When a Terminal Viewer is downloaded that requires Java, JRE v. 1.4.2_02 will be installed automatically. This overlay of JREs allows Terminal Viewers to function correctly in the Windows 98 environment.

Using HTTP Engine on UNIX Systems

If you are using the HTTP Engine on a UNIX system that will receive a high volume of traffic for MCS, you should increase your system's default setting for the number of "files" that can be concurrently opened by a particular process to 1024. This is advisable because UNIX considers a network connection to be a kind of file. Many systems have a default value of 64 or 256 for this setting, which may limit concurrent connections available to your MCS Server.

To increase the number of files allowed by the Java process in which MCS is running
  1. After the UNIX installation is complete, edit, located in the Attachmate/HTTPEngine/bin directory, by adding the following line near the top of the file:

    ulimit -n 1024

  2. Restart HTTP Engine.

Errors in the HTTP Engine Logs

You may see several bad read errors in your HTTP Engine log files. This is a known bug which is documented on the Apache Web site at The errors are harmless and can be safely ignored.

Modifying Connection Information for a Configuration Server in a Clustered Environment

If, after installation, the IP address, host name, or port number of your MCS server or another configuration server changes, you will need to manually reconfigure values for all the servers in the server cluster so that they point to the new location. If the change is in your MCS cluster, you may also need to reconfigure values in other server clusters.

Note This procedure is necessary only if you work in a clustered environment. If you work in a single MCS server environment, a change in its IP address can be automatically detected.

The following procedure assumes that your Web server has also been updated with the new values.

To manually update connection information for a configuration server
  • Search the MCS install directory and subdirectories of your MCS servers and replace the values on all MCS servers on which they occur.

    Values that may need to be updated:
    In this file
    Note The location of the file varies, depending on your application server environment. In most cases, it is located in the WEB-INF directory, but it could also be in the mcs directory.

    MCS.dataservices.primary (This value should be blank for primary servers, including the MCS server.)


    mcs/resources/ServerMgt_Content.xml References to the name, address, or port number under the <MCS Cluster> node.


      where n is the server number of the affected server. For example, 10001.xml is the XML file for the MCS server.

    The following attributes to the <server> element:

    name, and/or

Presentation Designer Issues

Global Variables with Same Name as Host Name have Errors at Runtime

If a global variable is created with the same name as one of the host names in the project, the generated application will have errors at runtime and may not run.

Unable to Obtain an IP Address from ID Manager at Run Time if Connecting to HTTPS

If an application is set to get a resource from ID Manager at run time via the IP address of the client machine (Dynamic IP), and the Presentation server is connecting via HTTPS, ID Manager receives local host instead of the IP of the requesting machine.

To use this environment, you must use the Tomcat SSL connector (you have to provide a certificate for Tomcat).

To use the Tomcat SSL connector
  • Follow the instructions in the server.xml file, by executing:

    %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)


    $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)

    where the password is equal to "changeit" for both the certificate and the keystore itself.

For more information, refer to

Manual Deletion of Events for Deleted Hosts

When a Host is deleted, the user must manually delete all events that referenced the deleted host, or change them to reference another valid Host.

APL/Graphics Not Supported

APL/Graphics are not supported in this release. You can press the RESET (ESCAPE) key to clear the error and continue.

Add Disconnect Action before Adding Configure Plus Display Form Actions

On a host-based screen form, if you execute an Event that includes Configure plus Display Form, you must add a Disconnect action before the Configure action. Failure to disconnect the host before the event is executed will result in a blank form being displayed.

Package Name Must Be Included When Generating a Task

If you want to use a task with Presentation Builder, you must include a package name when generating a Services Builder task, including IMS and CICS tasks. If a package name is not included, the project will not compile and the application will not be generated.

See the Java Technology Home Page for additional information — under Source Compatibility, refer to item number 8.

Setting Runtime Server for Task Execution

Presentation Designer can execute a Task object created from the Attachmate line of Services Builders. During the design phase of the project, a Services Builder task can be included into the project and tested with Presentation Designer.

To change the runtime server settings to successfully execute a task
  1. Before testing the task, modify the PresentationDesigner.sp file to point the appropriate property to the correct Runtime server.

  2. Change the properties listed as indicated:

    • attachmate.screenconnectors.serveraddress=localhost
    • attachmate.ims.serveraddress=localhost
    • attachmate.cics.serveraddress=localhost
    • attachmate.cics.protocol=tcpip

  3. Modify the appropriate connector property with the address of the Runtime server.

  4. (Optional) Modify the protocol property for the CICS connector (refer to the CICS connector documentation for supported protocols).

    These properties are read the first time that the task is executed in the design environment. After that, a file is written and the property is cached.

    If the server address is not changed before executing Services Builder tasks, or the server is renamed, you may need to modify the configuration setting.

The configuration settings are located in C:\Documents and Settings\username\cfg.

Task Bean Name Collisions

When task beans are created in different task builders (for example, Services Builder for IMS and Services Builder for CICS), or in different copies of the same task builder, then given the same name as another task, they are then downloaded by Presentation Designer, and copied into different product-related directories. Depending on the order of the directory in the classpath specification, Presentation Designer will load the first-found task based on name. In Presentation Runtime Service, the task bean that is copied last will overwrite existing task beans with the same name. In both cases, the affected applications will malfunction, and both the application and the task that was overwritten will need to be rebuilt.

Disk Space Requirements

A user installing Presentation Designer on a drive with low disk space may encounter problems if the drive has insufficient space to download resources from MCS or create projects.

Presentation Server not Using Latest Application from MCS — Changing the Application Cache Setting

To increase performance and reliability, the Presentation Builder Runtime Service caches applications that have been downloaded from MCS. When the applications are changed, you must restart the HTTP engine to force the new version to be downloaded. This operation should typically be done after business hours, since clients that are currently connected will be disconnected when you restart the HTTP engine.

HTML Issues

Defaults for and common.js Must Be Changed for Application Persistence

Application Persistence defaults are False. If you want to use Application Persistence for HTML presentations, you must change the isApplicationPersistence=true variable in the common.js, and the variable applicationPersistence=true. Both values must be true to enable Application Persistence.

The and common.js files can be found in the following locations.

Limitations in HTML Versions of Presentations

Compared to the Presentation Renderer version, the HTML version will have some limitations including the following:

Solaris and HTML Applications

If you want to run HTML applications on Solaris, you may need to run CDE or another X Window-based window manager. It is not necessary to run an X Window server to run Presentation Builder Runtime Service.

Previously Published HTML Applications Not Updated at Runtime

An HTML application that has been previously published is not updated at runtime — when the application is downloaded as a Presentation, you will not see the latest modifications.