Agile Business Suite - Unisysassets.unisys.com/Documents/Global/SoftwareRelease... · Visual Studio 2015 and Team ... Agile Business Suite Developer or AB Suite Developer is an Integrated

Unisys

Agile Business Suite

Developer

December 2016

Software Release Announcement

Release 6.1

3826 5930–007

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages.

You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used.

The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions.

Notice to U.S. Government End Users: This software and any accompanying documentation are commercial items which have been developed entirely at private expense. They are delivered and licensed as commercial computer software and commercial computer software documentation within the meaning of the applicable acquisition regulations. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys' standard commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data rights clauses.

Unisys and other Unisys product and service names mentioned herein, as well as their respective logos, are trademarks or registered trademarks of Unisys Corporation.

Contents

Section 1 Product Overview...................................................................... 1

What does Agile Business Suite Include? ..........................................................1Building an Application .......................................................................................2Agile Business Suite Runtime ............................................................................3

Section 2 Hardware and Software Requirements ................................... 5

Hardware Requirements ....................................................................................5Software Requirements .....................................................................................6

Section 3 Migration Requirements ...........................................................9

Preparing for Migration .......................................................................................9Migration ..........................................................................................................10Migration Guide ................................................................................................10

Section 4 Release Functionality ...............................................................11

Visual Studio 2015 and Team Foundation Server 2015 ....................................11XML Processing ...............................................................................................11New Wizards ....................................................................................................12List Attribute .....................................................................................................12Visual Studio Logic Editor .................................................................................12Multiple Team Foundation Server (TFS) Support ..............................................13Installation Improvements ................................................................................13SQL Server 2016 ..............................................................................................13

Section 5 Restrictions and Known Limitations ..................................... 15

Restrictions ......................................................................................................15

Section 6 Support..................................................................................... 19

Unisys Support Online ......................................................................................19Unisys Client Support Center ...........................................................................19Direct Telephone Support .................................................................................20Software Support Services ...............................................................................20

3826 5930–006 iii


Section 7 Product Information ............................................................... 23

Documentation CD-ROM ................................................................................. 23Downloading Documentation .......................................................................... 23Ordering Documentation ................................................................................. 23Self-paced Training ........................................................................................... 23Instructor-led Training ....................................................................................... 25

Section 8 Ordering Procedure................................................................. 27

Agile Business Suite Developer Product Packaging ........................................ 27Ordering Agile Business Suite ......................................................................... 28Licensing Options ............................................................................................ 28Style IDs ........................................................................................................... 30

iv 3826 5930–006

Section 1 Product Overview

Delivering features and functionality that increase the productivity and efficiency of the developers, Agile Business Suite (AB Suite) enables high level service to the user community, supports agile development strategies, and extracts more value out of IT investments. AB Suite exploits the “upside potential” of mission critical business applications.

AB Suite software enables enterprises to deliver superior solutions in today’s demanding timeframes. Such systems require scalability, reliability, and manageability unseen in less capable systems.

Over the course of more than twenty years, Unisys has demonstrated its superiority in building complete large-scale, reliable systems, using the powerful Enterprise Application Environment (EAE) product suite. Agile Business Suite is the next generation of development tools from Unisys; it builds on the strengths of EAE and incorporates new component-based concepts that make it an ideal tool for building composite applications.

What does Agile Business Suite Include?Agile Business Suite Developer or AB Suite Developer is an Integrated Development Environment (IDE) for rapid application development. It operates as a plug-in to Visual Studio®, running on a Windows workstation.

Targeted for both new and existing AB Suite users, AB Suite Developer requires minimal orientation for people familiar with Visual Studio. AB Suite Developer also has familiar aspects for experienced EAE developers. Existing EAE 3.3 model files can be migrated into AB Suite Developer.

After the model is migrated, you can take advantage of significant opportunities to further enhance your application, including UML application modeling and Object Oriented (OO) concepts, or new features that can improve the maintainability of your application. Visual Studio IDE, the OO concepts and its high level developer’s productivity language makes AB Suite Developer an ideal tool for C# developers to take the next step towards developing large enterprise mission critical applications for ClearPath MCP and Windows Runtime environment.

3826 5930–007 1


The AB Suite development environment includes:

System Modeler – A model-based tool for designing and developing information systems. It allows you to focus on the logical requirements of a system, without worrying about platform-specific implementation details. Individual elements you define in System Modeler translate into multiple physical elements in your Runtime system.

Debugger – Emulates the host runtime environment on your development workstation. Using Debugger you can test the application you are modeling and trace any problems. Debugger runs within the Visual Studio IDE.

Builder – Generates a complete application tailored for the specific architecture you are deploying to. The generated application comprises the graphical user interfaces, database tables and access mechanisms, and application code. The application components generated by Builder can be deployed automatically to an AB Suite Runtime host, where they are run and managed.

Source Control – Provided in AB Suite using third-party tools and is used for version management of models and model elements.

Automated Test Tool (ATT) – Verifies the changes in an AB Suite generated application using a series of test steps. It is integrated with the AB Suite Development Environment. It provides functions to record, play back, and edit test sequences for the AB Suite applications deployed on all the supported Runtime environments.

Client Framework – Uses the AB Suite Access Layer based on .NET to provide a new approach to design AB Suite applications. You can use Client FRamework for designing a user interface by using standard technologies, such as Windows Presentation Foundation (WPF), ASP.NET Model View Controller (MVC), or Windows Communication Foundation (WCF).

XML Processing – Sends XML messages to a runtime system, processes the message, and obtains a response from the runtime system.

AB Suite also includes:

• AB Suite Client Tools

• AB Suite Runtime for the ClearPath MCP Operating System

• AB Suite Runtime for the Windows® Operating System

Building an ApplicationOnce your application model has been developed using AB Suite Developer, you can build and deploy it to a runtime server using the Builder capability.

Builder produces a fully running system on a server running the Agile Business Suite Runtime from the Developer model database repository, including client, application and database layers. For this release, systems are generated for the .NET framework on ClearPath MCP and Windows Operating System.

2 3826 5930–007


Microsoft Build Engine

The Microsoft Build Engine (MSBuild) provides you the option to build AB Suite applications without using the Visual Studio environment. It also provides you the flexibility to use the powerful functionality of TFS Build, which enables you to build AB Suite applications on the TFS server while running a build definition on a TFS client. See the Developer User Guide for more information.

Agile Business Suite RuntimeAgile Business Suite Runtime software is used to deploy and support Agile Business Suite applications on a runtime server. AB Suite supports two runtime environment; ClearPath MCP Environment and Windows Environment.

For more information, see the Software Release Announcements for Agile Business Suite Runtime for ClearPath MCP Operating System and Agile Business Suite Runtime for the Windows® Operating System.

3826 5930–007 3


4 3826 5930–007

Section 2 Hardware and Software Requirements

Hardware RequirementsThe development environment can be installed on stand-alone workstations or on Terminal Services. The minimum requirements for these configurations are described below.

Development Environment

The following table shows the minimum hardware requirements for a workstation when the AB Suite development environment is installed, either on its own, or together with Builder or Version Control.:

Note: Additional disk space is required if the Microsoft SQL Server database is stored on this machine. The required space varies depending on the size and complexity of the system.

It is recommended to provide each developer one or two large screens, so that they can open multiple panes for maximum productivity.

You should have minimum a Dual Core processor, for Microsoft Visual Studio and AB Suite in one machine.

HardwareDevelopment Environment

Development Environment and Builder or Version

Control

Processor Dual Core or Quad Core configuration Intel Core i5, 3.0 GHz

Dual Core or Quad Core configuration Intel Core i7, 3.0 GHz

RAM 8 GB or higher 16 GB or higher

Disk space 100 GB 100 GB

Operating System 32 or 64 bit Client Operating system

32 or 64 bit Client Operating system

3826 5930–007 5


The system configuration for a server environment is highly dependent on a number of factors including the number of users, size of the Model and required response time. A more powerful machine than these minimum specifications will likely be required for a larger development group or a larger model specification.

AB Suite Developer is an I/O intensive application because all objects are stored in the model and updated constantly as each object changes.

For the Model Database

The disk space required for the model database depends on the size of the Specification being developed. This includes the number of <<Ispec>> classes, <<Reports>> classes, and lines of logic.

Due to the extensive re-engineering that has been carried out in Agile Business Suite Developer, and the efficiencies of the Microsoft SQL Server databases, the disk space required for a Model database (repository) is significantly less than was required for previous releases of Enterprise Application Developer.

Refer to the AB Suite 6.1 Software Qualification and Support Matrix for the recommended hardware configuration.

Software RequirementsThe system software configuration required to support Agile Business Suite Developer client workstations is detailed in the following table:

Requirement Comment

One of the following:

• Windows 10 Anniversry Update Professional, Enterprise (x86, x64) or later

• Windows Server 2012 R2 Datacenter

Windows 7 Professional, Ultimate (x86, x64) SP1, Windows 8.1 Professional, Enterprise (x86, x64), or Windows Server 2012 R2 Standard supports AB Suite development environment.

Agile Business Suite 6.1 Developer for Windows is not supported in a Native 64-bit environment. It runs in a 32-bit WOW64 environment, wherever available.

• Visual Studio 2015 Professional Update 3 or later

and

• Team Foundation Server 2015

or

• Team Foundation Server 2013 or Team Foundation Server 2012

Team Foundation Server 2015 requires SQL Server 2016 and Team Foundation Server 2013 or 2012 requires SQL Server 2012.

6 3826 5930–007



• SQL Server 2016 Enterprise Edition (x64)

• SQL Server 2016 Express (x86, x64), Standard (x86, x64), Enterprise Edition (x86)

• SQL Server 2014 Express (x86, x64), Standard (x86, x64), Business Intelligence Editions (x86, x64), Enterprise Edition (x86) SP2

• SQL Server 2012 Express (x86, x64), Standard (x86, x64), Business Intelligence Editions (x86, x64), Enterprise Edition (x86, x64) SP3

The installation proceeds successfully if SQL Server is not installed. However, before you start using Developer, you must either install a database server or have access to another machine with a database server installed.

Notes:

• SQL Server 2012 Express (x86, x64), Standard (x86, x64), Business Intelligence Editions (x86, x64), Enterprise Edition (x86, x64) with Service Pack 3; or SQL Server 2014 Express (x86, x64), Standard (x86,x64), Business Intelligence Editions (x86, x64), Enterprise Edition (x86, x64) with Service Pack 2 or SQL Server 2016 Express (x86, x64), Standard (x86, x64), Enterprise Edition (x86) are supported but not recommended as the express version has restrictions for the number of CPUs, memory and database size, thereby limiting the size of systems supported by Agile Business Suite 6.1.

• If you are using an SQL database, ensure that the SQL Server is configured to allow both SQL Server and Windows authentication. Refer to the Agile Business Suite Installation and Configuration Guide for more information.

• SQL Server 2016 need not be installed on a Developer workstation when the Model database is on another machine. However, it is required only when you need a local Model database. If the model database is on another machine, then SQL Server Native Client is a requirement for the Developer workstation.

• SQL Server 2012, or SQL Server 2014, or SQL Server 2016 Native Client is required for Developer installations that do not already have SQL Server installed.

Microsoft Visual C++ Redistributable for Visual Studio 2015 latest update

Visual C++ runtime redistributables are required for unmanaged parts of Developer and can be download from Microsoft.

Requirement Comment

3826 5930–007 7



• Microsoft SQL Server 2016 Native Client



This is a mandatory pre-requisite for AB Suite Developer installations that do not already have SQL Server installed.

.NET Framework 4.6.1 .NET Framework 4.6.1 or later is required.

Note: .NET 4.6.2 is supported and required on Windows 10 Anniversary Update Professional or later.

Oracle Java Software Development Kit (JDK) v1.6 or later

For generating Java based applications.

Note: Java 64-bit is supported.

Enterprise Output Manager 12.0 or 13.0 (32-bit)

This is an optional supported application.

ePortal 7.0 Supports capabilities of many client technologies, including HTML5, mobile web forms (iOS, Android, Blackberry, Windows Phone), ASP.NET Web Forms, ASP.NET Web Services, WCF Services and REST services.

Requirement Comment

8 3826 5930–007

Section 3 Migration Requirements

Applications created in AB Suite 2.0, 3.0, 4.0, or 5.0 Enterprise Application Environment (EAE) Release 3.3 can be directly migrated to AB Suite Release 6.1. It is advised that systems created in earlier EAE releases are upgraded to release EAE 3.3 before migrating to AB Suite 6.1. The migration utilities for AB Suite do not support versions of EAE earlier than Release 3.3.

To migrate AB Suite 2.0, 3.0, 4.0, and 5.0 applications to 6.1, you should export the model databases into a .model file with AB Suite Developer 2.0, 3.0, 4.0, and 5.0 and then import the exported file with AB Suite 6.1 Developer.

Migration of EAE 3.3 applications can be done using an Exported LCIF file. Use of a migration Model database is recommended when migrating from EAE 3.3. Because of the development environment interface changes, your model will look substantially different when migrated to AB Suite. When a model is loaded from an existing LCIF file, its elements are automatically mapped to the new constructs. However, the basic structure of your model remains the same.

It is important that you read the Agile Business Suite Migration Guide thoroughly before undertaking any migration activities.

Preparing for MigrationBefore migrating to Developer from any previous release, you need to:

• Inform Unisys about your plans. For this either contact your local representative or reach us at via [email protected]

• Complete the migration qualification checklist and share it with Unisys

• Read the Agile Business Suite Migration Guide.

• Back up your system and data.

• Ensure your environment meets the hardware and software requirements for this release.

• Install AB Suite Developer.

• Install AB Suite Runtime.

3826 5930–007 9


MigrationThe Agile Business Suite Migration Guide contains all the steps that are required to migrate your system. The EAE to AB Suite Migration Reference Guide contains detail on post migration functionality and references.

The following are some of the issues and differences you might encounter during or after migration:

Name Substitution

During the model migration some user-defined element names may be altered due to new conventions. Changes may occur to the following:

• Any name containing hyphens. Hyphens are replaced by underscores.

• The name of any print frame will be prefixed.

• Any name which conflicts with an internal or framework name.

• Array names, due to the syntax changes for referencing array elements.

Language Migration

All LDL commands are converted to the new LDL+ syntax during the migration process. The logic of every method, and the conditions attached to profiles and data types are converted to LDL+.

Security

It is not possible to migrate existing security settings. EAE security is based on privilege levels, which are combined in Agile Business Suite Developer with security utilizing the Windows security system. Roles must be manually configured for any migrated systems. More information is available in the Installation Guide.

Version Control Migration

To migrate version control history, you need to export your EAE 3.3 version control data to an XML file. This file can then be migrated using the History Migration Viewer application supplied with AB Suite Developer.

Migration GuideThe AB Suite Migration Guide describes all the steps that are required to migrate your EAE 3.3 system. The EAE to AB Suite Migration Reference Guide contains detail on post migration functionality and references.

The AB Suite Migration Guide includes comprehensive details regarding pre-migration activities, the migration process, and the results that can be expected once a system is migrated into the new development environment.

10 3826 5930–007

Section 4 Release Functionality

Visual Studio 2015 and Team Foundation Server 2015

The development environment for AB Suite 6.1 is now hosted with Visual Studio 2015. A new set of AB Suite Developer icons are available with this release of AB Suite 6.1. Refer to Agile Business Suite Developer User Guide for more information.

For AB Suite 6.1, the System Modeler now supports new Source Control Provider, Microsoft Team Foundation Server (TFS) 2015.

XML ProcessingIn AB Suite 6.1, the XML Processing feature allows an AB Suite Runtime for Windows to act as a message broker for XML messages. A client can submit XML messages to a runtime system where they are parsed, interpreted, processed, and a response returned to the client.

The modelling enhancements to support XML processing are now implemented within a new type of model referred to as XML Framework. To use these features you must either create a new application by selecting the Include XML Framework check box in the New Application Wizard or convert your model using the Convert an Existing Model wizard. Converting your model clones it to a new model database and enables all the new XML processing features. You can also create a Client Framework model with the new XML Processing feature enabled.

The new XML Framework model also supports new concepts, such as a Serialization and Messenger stereotype. Serialization is used to represent XML messages and Messenger stereotypes are used to represent and handle input XML messages, Types; that is, simple data type definitions that have no instances or any other class-like behaviour, and Templates that represents true inheritance without assuming instantiation. These concepts are added mainly to support XML Processing in AB Suite Runtime for Windows applications.

Refer to the Agile Business Suite Developer User Guide for more information on XML Processing in AB Suite.

3826 5930–007 11


New WizardsIn AB Suite 6.1, two new wizards have been introduced; Xsd Import Wizard and Xsd Export Wizard.

The Xsd Import Wizard allows you to create a class in your model that defines an XML document. The input file for this process must be an XSD file that defines the schema for an XML document. After completion of this process your model will contain a class or classes that define the structure of the XML document.

The Xsd Export Wizard allows you to generate an XSD file from any Messenger or Serializable class definition.

It will be possible to export any class that implements Serialization to an XSD file to share the definition of the XML document with other systems. This exported XSD will contain a fully self-contained and complete definition of the XML class being exported in a single XSD file.

Refer to the Agile Business Suite Developer User Guide for more information on the wizards.

List AttributeIn AB Suite 6.1, defining List attributes has been made simpler. A new kind of attribute, List Attribute, has been included. When you add an attribute you can indicate that you want it to be a ‘List’, and you can specify a Template to define the list item type. It is no longer necessary to create a separate ‘List Type’ to define a list, although this is still available.

Importing an XSD which includes list elements will represent these lists by using ‘List Attributes’ and will no longer define them through separate ‘List Types’.

A new pop-up dialog box is used as the default way to add new attributes, variables, and parameters. The first field on this dialog box is the Template field, which encourages all attributes to derive from a type or class. You can specify that the attribute should be a ‘List’ on this dialog box.

Refer to the Agile Business Suite Developer User Guide for more information.

Visual Studio Logic EditorIn AB Suite 6.1, the custom editor has been replaced with the Visual Studio Code Editor to provide a richer more natural editing experience. Visual Studio provides language-specific support for editing source code in the Integrated Development Environment (IDE) by implementing a language service as part of a VS package.

12 3826 5930–007


The new logic editor is enabled by default and provides the following features:

• Quick Actions – resolve logic errors quickly and simply from a list of suggested fixes

• Debugger – conditional breakpoints

• Peek Definition – view and edit method and insertable logic inline of the current logic window

• Code Definition window – quickly view Method or profile logic without navigating away from the current logic window

• Improved auto – list to write more logic in fewer key strokes

• Dynamic Validation – logic is validated as it is entered to give early notification

Refer to the Agile Business Suite Developer User Guide for more information.

Multiple Team Foundation Server (TFS) Support

In AB Suite 6.1, Microsoft Build Engine (MSBuild) allows you to build AB Suite applications on TFS 2013 (Team Foundation Build) or separately through a command line without using the Visual Studio environment. The TFS Build is part of Visual Studio TFS and is implemented as an extension of MSBuild. Refer to the Agile Business Suite Developer User Guide for more information.

AB Suite 6.1 is integrated with TFS 2015. You can use Visual Studio TFS to manage the lifecycle of your AB Suite Applications, reduce risks, and improve efficiencies. AB Suite 6.1 also works with TFS 2013 and TFS 2012.

If you already have an older TFS environment, you can integrate AB Suite 6.1 with TFS so that we can get more feedback on any issues with TFS 2013 or 2012.

Installation ImprovementsThe AB Suite 6.1 Development Environment installation has an option to create the Application User and Administrative User so that these users do not have to be manually setup prior to installation.

The AB Ready tool is also available to create these users separately from outside of the product installation, and to also check for software prerequisites.

SQL Server 2016SQL Server 2016 is used for the AB Suite 6.1 Model and Debugger databases. AB Suite 6.1 also supports SQL Server 2014 and SQL Server 2012.

3826 5930–007 13


14 3826 5930–007

Section 5 Restrictions and Known Limitations

RestrictionsThis section describes the restrictions and limitations that apply to AB Suite Release 6.1 Developer and Builder.

For the latest restrictions information, refer to the README.HTM file available on the Unisys Support Online Web site at http://www.service.unisys.com.

Automated Test Tool (ATT)• For recording the test cases, you should configure ATT and create a unit test project

before recording transactions. ATT cannot record multiple sessions for a client application.

Model• Multiplicity greater than 1 for Attributes inheriting from Glb.File, SQLScript, or Frame

is allowed but not supported.

• Multiplicity greater than 1 for Parameters and Return Variable is allowed but not supported.

• GLB.OutputStream can be specialized but is not supported.

Version Control

Before updating the workspace with a GetLatest operation, the AB Suite solution must be closed in Visual Studio. There have been reported occurrences of Visual Studio crashing and inconsistent synchronization when the project is open. After the GetLatest and before opening the project, the database needs to be synchronized with the command import –vf <project file> -m <model>.

Builder• The Clean option removes all temporary files from the Builder cache and Builder

output and resets all change analysis information and applies to all built packages of the Model for the selected configuration. The Clean option applies to all segments under the Model regardless of the current folder deployment options.

3826 5930–007 15


Clean option can be used only on Model Nodes.

Note: The Clean operation does not affect the deployed application.

• Threshold Control for Builder is still being implemented. Although the control appears, the underlying behavior is still being implemented. Please ignore this option for now.

Debugger• The new Alternate Name property in debugger configuration does not support the

SwitchTo command.

• If an unattached report is stopped during the debug session, Debugger stops the report and will not perform the retry operation.

• Debugger with MCP configuration does not support the COBOL COMP format to store a number array due to Unisys OLEDB limitation. Therefore, the way of storing and retrying these data in DMSII is different from MCP Runtime.

• A batch file (DBGRPaths.bat) is provided under the “Development Environment” folder of the Developer CD package. This batch file needs to be run if there is compilation error during wrapper build while using external classes in debugger.

Note: This batch file update is required only if Visual Studio is installed on a drive other than C drive.

Visual Studio Logic Editor

Some logic references continue to show a Guid instead of a qualified element name. This is an issue with the Visual Studio logic editor itself which is under investigation at this moment.

XML Processing in AB Suite

Some Messenger transactions fail on the second transmit in the Debugger.

Client Framework

Unisys.ABSuite.AccessLayer.Connector project references are not updated when importing from an AB Suite 5.0 BCK file. References need to be updated manually for now.

MCP Runtime Specific

The following restrictions in Developer are specifically due to runtime limitations for the ClearPath MCP operating system.

• Restrictions on IsInner Classes

Owner Data is not passed nor returned from user defined methods (non internally overridden methods Construct, Prepare, Main, Edit for Stereotyped classes such as Ispec, CopyIspec, Event, CopyEvent) of the IsInner Class(es) in this release.

16 3826 5930–007


• Restrictions on Method parameters / return types

Polymorphism for class parameters / return types is not supported in this release. When generating a method with a potential polymorphic parameter to the MCP platform, a warning will be sent into the output log.

Extract file parameters are not supported in this release. When generating a method with an extract file parameter on the MCP platform, an error is sent to the output window and the generate is cancelled.

• Restrictions on inherited Methods

Internally overridden methods Construct, Prepare, Main, Edit (for Stereotype classes such as Ispec, CopyIspec, Event, CopyEvent) are not inherited in this release.

Similarly, in this release you cannot call an inherited Framework method of an Ispec.

If during generation to MCP in the 4.0 release, logic attempting to call an inherited framework method of an Ispec is encountered a warning message will be sent to the output window to state that the logic in question has been ignored.

• Restrictions on Report/Frame User Defined Methods

Report and Frame user defined methods are not available in this release. If a report or frame user defined method is found during a build to the MCP platform an error will be sent to the output window and the generate cancelled.

• Restrictions on Polymorphic assignment

Only persistent polymorphism is supported in this release. Any non-persistent data is indeterminate after a polymorphic assignment.

• Restrictions on Aggregated Class Instances

Persistent Aggregated Instances:

Aggregated persistent instances are not supported in this release. If an aggregated persistent instance is found defined under a class during a build to the MCP platform, an error will be sent to the output window and the generate cancelled.

Aggregated Instances:

Aggregated class instances are not supported within user defined Methods (non internally overridden methods Construct, Prepare, Main, Edit for Stereotyped classes such as Ispec, CopyIspec, Event, CopyEvent). The value of any aggregated instance used in a user defined method is indeterminate.

Extracting a class that contains an aggregated class instance is also not supported in this release.

• Restrictions on First() and Last():

First() (other than a First on a simple String object) and Last() LDL+ methods are not supported in this release. Any logic trying to use these methods in the unsupported context will see a warning displayed in the output window (during a build of the system to an MCP host) and the logic will be ignored.

• Object Arrays of inherited classes:

Object arrays of a class in an inheritance structure will not be supported in this release.

3826 5930–007 17


• Restrictions on Extract Files / Extracting:

Extracting from the online (non report/frame):

Extracting data to an extract file from non report/frame classes and user defined methods is not supported in this release. Extract files defined at the Segment level cannot be referenced directly. You must create an instance of the extract file under an Ispec/vanilla class/report and refer to the instance defined under the Ispec/vanilla class/report. Extract files defined directly under methods are not supported in this release. If an extract file has been defined under a method, during a build to the MCP platform an error will be sent to the output window and the generate cancelled.

Aggregated Instances:

Extracting a class that contains an aggregated class instance is also not supported in this release.

• ROC and ADHOC models do not migrate into AB Suite correctly (underscores in Ispec names are migrated out), which means they will not work at runtime.

• OLTP systems must have a default segment service name defined.

Number of Keys on Ispecs

Ispecs with greater than 16 keys cannot be used with a Microsoft SQL Server database. Microsoft SQL Server has a maximum capability of 16 keys for an index. If the user tries to use greater than 16 keys they will see the following DBReorg error.

"2006-06-15 10:47:03.250 DBReorgEXE(1564:5360) [ABC-1\adminuser];

L11::Fatal::Action failed::Cannot specify more than 16 column names for

statistics or index key list. 20 specified."

It is recommended that you specify less than 16 keys which will also improve your database performance.

This error can also occur when debugging an MCP system using a Microsoft SQL Server database.

18 3826 5930–007

Section 6 Support

Unisys Support OnlineUnisys Support Online is a web-based online technical resource that is available to all Unisys clients with a service agreement.

Unisys Support Online puts a wealth of technical information regarding hardware and software product support services at your fingertips. Unisys technical specialists provide updated symptom and solution information, including frequently asked questions.

Unisys Support Online is available 24 hours a day, 7 days a week.

To initiate a support request, do either of the following:

• Submit a request online at http://www.service.unisys.com. After you log on or register, click Create Service Incident, and then follow the on-screen instructions. Enter the required information in the Support Request entry form.

• Contact the Unisys Call Reception Center (CRC). Access the Unisys Support website at http://www.unisys.com/about-us/support. The site provides links to various types of support. It also includes a link to a Video Demonstration of the Unisys e-Service Portal, where you will see how to effectively use this easy web-based tool to access product documentation and submit support requests for Unisys-supported products.

Unisys Support Online allows you to:

• Search technical databases for information on a problem.

• Download Interim Correction (IC) files containing fixes.

• Track the progress of software updates and fixes.

• Participate in support forums.

• Access instructional information in Customer Technical Bulletins.

• Log and track support requests.

Unisys Client Support CenterThe Unisys Client Support Center (CSC) is your information resource for problems that cannot be resolved through Unisys Support Online or your site administrator. Your site administrator can place a support request electronically.

3826 5930–007 19


The Electronic Support Request interface allows you to pose technical questions, discuss technical issues, and escalate design concerns with the experts at the Unisys Client Support Center.

When logging an Electronic Support Request you will be asked to specify the:

• Hardware model number

• Operating environment

• Software product and level code

The software product and level code for Agile Business Suite Developer Release 6.1 is AGILE-BUS-SUITE-DEV-6.1.

Direct Telephone SupportUnisys also offers direct telephone support. If you are located within the continental United States or Canada, you can call one of the following toll-free numbers during the times indicated in your service agreement:

• United States 800-328-0440 (prompt 4)

• Canada (English) 800-387-6181

• Canada (French) 800-361-8097

Customers outside the continental United States or Canada should refer to their local Unisys representative for support contact information.

Software Support ServicesUnisys Client Support Centers offer Software Support Services, a full complement of technical services to help clients with cost effective, fast-cycle support.

Software Support Services include:

• Software support ambassador – personalized attention from a dedicated Unisys Client Support Center specialist.

• System generation – assistance in installing or generating system software upgrades and enhancements.

• System migration – planning and optimization of system migration and upgrades.

• Performance Reviews – evaluation of existing systems and networks, and tuning recommendations.

• Communications systems enhancements – assistance in the configuration, generation, and installation of communications systems.

20 3826 5930–007


• Database management consulting – evaluation of systems and database backup procedures to ensure they promote data recovery.

• Administration seminars, and recovery tape and audit trail configuration.

For more information on Software Support Services, see Unisys Support Online at: http://www.service.unisys.com, in the United States call Unisys directly on 800-328-0440 (prompt 4), or contact your local Unisys representative.

3826 5930–007 21


22 3826 5930–007

Section 7 Product Information

Documentation CD-ROMThe Agile Business Suite Documentation CD-ROM contains full product documentation and is included when you purchase an Agile Business Suite Runtime Release 6.1 license.

It provides product information on all software, including:

• Agile Business Suite Developer

• Agile Business Suite Runtime for the MCP Operating System

• Agile Business Suite Runtime for the Windows Operating System

• Agile Business Suite Client Tools

Downloading DocumentationDocuments included on the Documentation CD-ROM are also available from the Product Support page at Unisys Support Online (http://www.support.unisys.com), as are updates to these documents as they become available.

Ordering DocumentationCopies of the Documentation CD-ROM (Part Number 8897 9273-000) can be ordered separately by calling 1-800-448-1424 in the United States or by contacting your local sales office for assistance in all other countries.

Self-paced TrainingSelf-paced training is available for AB Suite Developer.

The training is a self-study guide to developing applications using AB Suite. Interactive lessons help students understand concepts, and practical hands-on activities apply these concepts to build and test a simple application.

3826 5930–007 23


Training is designed for developers with little or no experience in developing AB Suite applications, although there is also a path for experienced EAE developers to familiarize them with the new AB Suite Developer environment.

Getting Started with Developer

Getting Started with Developer explains AB Suite basics, including components, the runtime cycle, logic, and debugger.

The course contains:

• A student guide with lesson summaries and activities.

• Computer-based training lessons.

• Screen demonstrations on how to complete tasks in the Developer environment.

The topics covered in the course include:

• Installing AB Suite

• What is Developer

• Using the Model

• Using Folders and Dictionaries

• Introducing Classes

• Testing your Forms

• Defining Events

• Introducing the Runtime Cycle

• Defining Logic

• Controlling the Runtime Cycle

• Designing User Interfaces

• Debugging your Application

• Errors and Feedback

• Simple Data Manipulation

• Using Methods

• Using Vanilla Classes

• Defining Profiles

• Advanced Data Manipulation

• Developing Reports

• Using Session-persistent Attributes

• Deploying your Application

• Introduction to Automated Test Tool

24 3826 5930–007


Getting Started with Developer for AB Suite Release 6.1 (Part Numbers 47259189-010 (CD-ROM) and 47259197-010 for the student work book) can be ordered from the Unisys Customer Education Web page at: http://www.app3.unisys.com/customer-education.

XML Processing in AB Suite

This tutorial explains how a client application can submit XML messages to the AB Suite runtime system where they are parsed, interpreted, corresponding processing is performed, and a response is returned to the client application.

The topics covered in this tutorial are:

• Defining XML Message Format and Processing Logic

• Submitting XML Message to the Runtime System

XML Processing in AB Suite for AB Suite 6.1 can be ordered from the Unisys Customer Education Web page at:

http://www.app3.unisys.com/customer-education.

Instructor-led TrainingInstructor-led training is available for AB Suite Developer.

The training is an Instructor-led training to develop applications using AB Suite. The classroom sessions help students to interact with the instructor and understand concepts. The practical hands-on activities help students to apply these concepts to build and test a simple application.

The instructor-led trainings contain student notes for each module, instructor slides corresponding to the modules in the student notes, sample files used in the practical exercises, and instructor guide containing detailed instructions for the instructor.

Using Source Control with AB Suite

The Using Source Control with AB Suite course is designed to assist customers in the implementation of AB Suite Source Control. This version of the course focuses on the implementation of Team Foundation Server (TFS) 2015 for AB Suite 6.1. The AB Suite Development Environment provides facilities to assist in the implementation of TFS for an effective change management system.

The course contains:

• Slides

• Instructor Guide

• Student Guide

• Demonstrations

3826 5930–007 25


The topics covered in this course include:

• AB Suite with TFS

• Installing TFS 2015

• Using AB Suite and TFS Source Control

• Application Life Cycle Management

• Using Compare Tools

• Source Control Operations

Using Source Control with AB Suite for AB Suite 6.1 (Part Number 68735828-002) can be ordered from the Unisys Customer Education web page at:

http://www.app3.unisys.com/customer-education.

26 3826 5930–007

Section 8 Ordering Procedure

Agile Business Suite Developer Product Packaging

When you purchase an Agile Business Suite Developer Release 6.1 license, you will receive:

• Agile Business Suite Developer Release 6.1 CD-ROM containing:

– Agile Business Suite System Modeler software and documentation

– Automated Test Tool

– Agile Business Suite Client Tools software and documentation

o Agile Business Suite Component Enabler

- Java and .NET Framework versions

o Agile Business Suite Presentation Client

o Agile Business Suite Client Generators

- Presentation Client Generator

o C# implementations

- ASP .NET Web Forms Generators


- ASP .NET Web Services Generator


- VB .NET Forms Client Generator


- JSP Generator


- ePortal Generator


o Agile Business Suite Business Integrator

o Agile Business Suite Client Framework

• A printed copy of this Software Release Announcement

3826 5930–007 27


When you purchase a license for the optional, separately ordered Agile Business Suite Generator Customization Kit, you will receive:

• The Agile Business Suite Generator Customization Kit Key Letter that will enable you to install the customization kit software from the Developer CD-ROM

• Agile Business Suite Generator Customization Kit document

Ordering Agile Business SuiteTo order the products described in this Software Release Announcement please follow the instructions below.

• Customers in the United States have the following options:

– Call Software Order Express at 800-829-1313

– Fax an order to Unisys at 215-986-9281

– Send an e-mail to [email protected]

• Customers outside the United States have the following options:

– Contact the Unisys Customer Support Center for your area or region

– Contact your local Unisys sales representative or organization, or an authorized Unisys Value Added Reseller

Licensing OptionsAgile Business Suite Developer and the Generator Customization Kits are licensed on a concurrent user basis. Developer can be licensed in single license increments, in Multiple License Packs, or in a combination of the two.

Notes:

• In all cases you are required to buy a license of Microsoft Visual Studio 2015 and one of the qualified SQL Server versions, and optionally Microsoft Team Foundation Server 2015 (TFS) directly from Microsoft; the same is the case for support and updates.

• As Unisys and Microsoft provide regular new releases, we strongly advise you to go for a MSDN contract with Microsoft that covers support and regular upgrades.

• The required number of Runtime licenses is equal to the maximum number of concurrent users that could be actively using it at any one time. You are required to notify Unisys when additional users are added to order additional user licenses.

28 3826 5930–007


Usage Level

Agile Business Suite Developer Multiple License Packs are an economical and convenient way for you to order the number of Developer licenses you need. In addition to providing a quantity discount, they also simplify the ordering and maintenance agreement tasks by reducing the number of individual styles involved in each process.

Note: The required number of Developer or Generator Customization Kit licenses is equal to the maximum number of concurrent users that could be actively using each product at any one time.

Types of Licenses

Depending on your current licensing situation, different types of licenses are available:

• New licenses

• Update licenses

• Upgrade licenses

• Select Software Update (SSU) Subscription licenses

New Licenses

New licenses are for new users who need initial licenses for Agile Business Suite Developer and/or Generator Customization Kit, or for current users who require additional licenses.

Update Licenses

Update licenses are for current EAE users who have a license, EAE Developer or ASP Customization Kit, and who want to migrate to AB Suite. Customers must have both SSU Subscription and valid maintenance agreement for Enterprise Application Developer to order an AB Suite Developer or Generator Customization Kit update style.

Update styles are also available for customers who are licensed for Agile Business Suite Developer 2.x, 3.x, 4.x,or 5.x and have both, a current SSU Subscription and a valid maintenance agreement for it. Please note that any maintenance vendor agreement and SSU Subscription for AB Suite Developer does not include Visual Studio or any other software like SQL Server.

Upgrade Licenses

Upgrade licenses are for current users who have a license and a maintenance agreement for Enterprise Application Developer or ASP Customization Kit and who want to migrate to Agile Business Suite but do not have a Software Update Subscription for Enterprise Application Developer.

Upgrade styles are also available for customers who have a license for Agile Business Suite Developer 2.x, 3.x, 4.x,or 5.x and a maintenance agreement but do not have a SSU Subscription for it.

3826 5930–007 29


SSU Subscription Licenses

SSU Subscriptions provide ‘no additional charge’ updates to future releases for an annual or fixed period subscription fee.

Customers with a SSU Subscription and valid maintenance agreement do not pay an upgrade fee when migrating to a new chargeable release level. SSU Subscription coverage must be continuous from the original software shipment date.

SSU Subscriptions are available for new licenses as well as for update and upgrade licenses, and are ordered using the relevant SSU Subscription style ID.

Note: SSU Subscriptions can be purchased only when ordering a new, update or upgrade license, or at the renewal for an existing subscription license.

Style IDs

Style IDs for Agile Business Suite Developer

New License Styles

The following table lists the Style IDs used to order new licenses for Agile Business Suite Developer.

SSU Subscription Style

The following table lists the Style ID used to order SSU Subscriptions for Agile Business Suite Developer.

Usage Level Style ID

One Concurrent user License ABD699-CD

10 Concurrent user Multiple License Pack ABD69910-CD







One Concurrent License* ABD100-CD

30 3826 5930–007


* For Multiple License Packs, for example ABD69910-CD, order the same number of subscriptions as the total quantity of Developer licenses (not the number of styles) ordered.

Update License Style

The following table lists the Style ID used to order update licenses for Agile Business Suite Developer when moving from Enterprise Application Environment 3.3 or from Agile Business Suite 2.x, 3.x, 4.x, or 5.x.

Upgrade License Styles

The following table lists the Style IDs used to order upgrade licenses for Agile Business Suite Developer when moving from Enterprise Application Environment 3.3 or Agile Business Suite 2.x, 3.x, 4.x, or 5.x.


One Concurrent user License ABD60-CD








One Concurrent user License ABU60-CD

10 Concurrent user Multiple License Pack ABU6010-CD






3826 5930–007 31


Style IDs for Agile Business Suite Generator Customization Kit

New License Style

The following table lists the Style ID used to order new licenses for Agile Business Suite Generator Customization Kit.

SSU Subscription Style

The following table lists the Style ID used to order SSU Subscriptions for Agile Business Suite Generator Customization Kit.

Update License Style

The following table lists the Style ID used to order update licenses for Agile Business Suite Generator Customization Kit when moving from Enterprise Application Environment 3.3 or Agile Business Suite 2.x, 3.x, 4.x, or 5.x.

You can use these style codes only if you have a valid License, Maintenance and SSU contract for the current versions used in Developer software.

Upgrade License Style

The following table lists the Style ID used to order upgrade licenses for Agile Business Suite Generator Customization Kit when moving from Enterprise Application Environment 3.3 or Agile Business Suite 2.x, 3.x, 4.x, or 5.x.

You can use these style codes only if you have a valid License, Maintenance and SSU contract for the current versions used in Developer software.


One Concurrent user license ABD999-CCG






One Concurrent user license ABU122-CCG

32 3826 5930–007


Customers who have AB Suite Developer release level 2.0, 3.0, 4.0, or 5.0 licenses, an associated maintenance agreement for them, and corresponding SSU Subscriptions are entitled to receive release level 6.1 at no additional charge. This update does not include additional or upgrade copies of Visual Studio.

3826 5930–007 33


34 3826 5930–007

© 2016 Unisys Corporation.All rights reserved.

*38265930-007*3826 5930–007