AB Suite 5.0 Is on its Way!Set to release in December of 2014, AB Suite 5.0 will deliver a wealth of new features, cutting-edge capabilities, valuable integrations, and more.

The EAE/AB Suite Symposium Is Almost Here! The second annual EAE/AB Suite Symposium includes a full agenda for EAE and AB Suite users, numerous technical sessions, and a wealth of networking opportunities.

Weaving EAE and AB Suite into the New Fabric-Based ClearPath SystemsEAE and AB Suite users have three distinct ways to benefit from the innovative capabilities built into our brand new fabric-based ClearPath Libra systems.

Engineering Corner: AB Suite Runtime for Windows – Runtime API The AB Suite Runtime API makes life easy for runtime admins by consolidating all administration functionality into a single, consistent, efficient interface.

Get to Know the Public Model FileThe Public Model file format in the AB Suite Model Export Utility offers a simple, programmatic means of applying bulk changes to multiple objects within your AB Suite applications.

Info Center and CalendarWe provide a wide array of materials to help you stay up to date on everything that’s happening in the world of EAE and AB Suite.

Not a subscriber of Developing Agility? Don’t miss the next issue – sign up today.

Contents

1

3

4

6

10

12

Developing Agility

Developing AgilityThe Quarterly Newsletter for Unisys EAE and

Agile Business Suite Customers

September 2014

AB Suite 5.0 Is on its Way!By Maarten Schneider, Worldwide Marketing Manager, Enterprise

Application Environment and Agile Business Suite, Unisys

We are thrilled to announce that the release of Agile Business Suite (AB Suite) 5.0 is right around the corner!

Planned for December 2014, AB Suite 5.0 will once again demonstrate our commitment to the AB Suite program by incorporating new integrations,

numerous enhancements, and more than 25 user-suggested features. Included in these new feature suggestions (NFS) is the dependencies and search feature, which performs an impact analysis to quickly find out where an element is used, and how. This capability will be exposed as a context menu option in various editors and the results will be displayed through the Find window in Microsoft® Visual Studio®.

We always welcome input from the global AB Suite user community. Not only does this make AB Suite “your” product, it leads to a much stronger overall offering. Many thanks to all of the AB Suite users who contributed an NFS.

A New Era of Application ModernizationAs organizations intensify their efforts to provide mobile access of their applications, while supporting rapidly growing “self-service” concepts, application modernization remains a hot topic. Enterprise Application Environment (EAE) and AB Suite users have long had the ability to use Client Tools, which makes it easy to generate contemporary user interfaces (UIs) and web services, to modernize their applications. >>

The EAE/AB Suite Symposium and European EAE/AB Suite Technical Seminar will be taking place in October. Mark your calendars!

September 2014 – Page 2

And now, both AB Suite 5.0 for ClearPath MCP and Microsoft Windows® are qualified for ClearPath ePortal 6.0, giving you new ways to generate mobile UIs and even native code for several mobile operating systems. Or, if you want the freedom to modernize with your favorite technology, you can use the new Client Framework available in AB Suite 5.0 for Windows. This capability is planned for AB Suite 6.0 for MCP.

Taken as a whole, this release will make it easier for you to build truly modern applications, standardize your development environment on Visual Studio, and help newer members of your development team quickly contribute to the business.

So what have we done to AB Suite 5.0 to make these goals a reality? Consider these noteworthy features:

• Integration with Visual Studio 2013 and Microsoft Team Foundation Server (TFS) 2013: Brings AB Suite in line with the latest enhancements to Visual Studio and TFS – and enables you to benefit from the considerable R&D investment Microsoft has made in these two products.

• TFS Build Manager and TFS Test Integration: Completes the TFS lifecycle integration in AB Suite by allowing you to create and manage build processes that automatically compile and test your applications, and automatically run test scripts in ATT.

• 64-Bit Microsoft Windows Runtime: Transfers the AB Suite on Windows runtime to a 64-bit production environment – and qualifies it for Microsoft SQL Server® 2014.

• Qualification for ClearPath ePortal 6.0: Supports the latest version of Visual Studio 2013 and provides access to the newest Microsoft modernization and integration features, which can help you optimize multi-tier, web, mobile, and web services integration projects without requiring complex programming.

• Client Framework: Provides an industry-standard interface, based on the DataModel, that enables organizations running AB Suite on Windows to create modern UIs with any tool they prefer.

• Enterprise Database Server for ClearPath MCP (DMSII): Allows you to benefit from the effort and expertise of the ClearPath engineering team by bringing the latest enhancements in DMSII – including dump encryption, physical set/subset sections, pre-verify reorganizations, no fine table lock, and data masking – to the AB Suite on ClearPath MCP environment.

• Qualification with DMSII XL: Helps you avoid crippling downtime by significantly increasing the limits of structures in the DMSII database.

Get a Head Start – Sign Up for the AB Suite 5.0 Field TestIf you’d like to see what these features can do in the real world, then we encourage you to sign up for the AB Suite 5.0 field test. Slated to run from September 15 to October 17, 2014, the field test is a great way to get an early look at all the amazing things we’ve added into AB Suite 5.0. And even more importantly, your participation in the field test will go a long way toward making this release of AB Suite the best it can be – for both your organization and the entire AB Suite user community.

If you sign up for the field test, you will have the opportunity to communicate directly with Unisys engineers. And, your CSC analyst will provide the same high level of support you receive for released products during the testing activities. Interested? Please email us for details.

We encourage all current AB Suite users to begin planning their upgrades to AB Suite 5.0 now. And if you’re an EAE shop that’s interested in AB Suite, there’s never been a better time to start the migration process. Please contact ABSuite@unisys.com to get started.

Developing Agility

September 2014 – Page 3

The EAE/AB Suite Symposium Is Almost Here!

Developing Agility

Just like last year’s inaugural event, the 2014 Symposium boasts an entire agenda dedicated to EAE and AB Suite topics. It includes:

• Updates, overviews, and demos of EAE and AB Suite, the new AB Suite Client Framework, ClearPath ePortal Release 6.0, and more

• A review and demonstration of the key features in AB Suite 5.0

• A discussion of EAE to AB Suite migration approaches and best practices

• A look at how AB Suite fits in with the Forward! by Unisys™ enterprise computing platform and all-new ClearPath fabric-based infrastructure

• A sneak peek at the upcoming AB Suite 6.0 release

The EAE/AB Suite Symposium will take place alongside the 2014 Universe Conference. So, in addition to a wealth of EAE and AB Suite specific content, attending the Symposium will let you take advantage of other technical sessions, great networking opportunities, and exciting keynote speeches – featuring Dr. Steven Squyres, lead scientist on NASA’s Mars Rover mission, and IDG CEO Matthew Yorke, among others.

The Symposium is open to EAE and AB Suite users from around the world. The registration fee includes all meals, drinks, entertainment, and transportation to and from the airport. All you’ll have to cover, in addition to the discounted registration fee, are your travel and hotel accommodations. Invitations with the registration link have been sent via email. If you didn’t receive yours, please contact Diane McGonigle.

We look forward to seeing you in October!

You are cordially invited to join us October 13-15, 2014, for the second annual EAE/Agile Business Suite Symposium!

What: EAE/AB Suite Symposium

When: October 13-15, 2014

Where: Gaylord Texan Resort & Convention Center, Dallas/Fort Worth, TX

Who: Developers, Application Development Managers, Architects

Can’t Make it to the Symposium?

Don’t worry, we’ll cover many of the event’s topics at the European EAE/AB Suite Technical Seminar in Amsterdam on October 21-22.

These systems answer the growing need for greater simplicity, cost control, and alignment between IT and the business by providing a common infrastructure for ClearPath MCP and previously distributed Microsoft Windows and Linux® workloads.

And in addition to the fabric-based architecture, these systems showcase an all-new high-speed interconnect and improved processor and I/O performance.

These capabilities are available in the premium high-end Libra 8380 and 8390 systems, high-end Libra 6380 and 6390 systems, and mid-range Libra 4380 and 4390 systems.

Assessing Your OptionsAs an EAE or Agile Business Suite user, you have several ways to move to these cutting-edge new systems. Each alternative leverages the new fabric-based infrastructure in varying degrees.

Currently, there are two options available for organizations that plan to move to a new fabric-based Libra system now. A third option will be available with AB Suite 5.0. The following summarizes each option at a high level.

Alternative 1: Move your EAE or AB Suite applications, without regenerating or rebuilding, from your existing Libra system – running either MCP Release 14.0, 15.0, or 16.0 – to a new Libra 4300, 6300, or 8300 system. For this alternative, you will need either:

• EAE hot patch 3.3.3302

• AB Suite 3.0.1304 or higher

• AB Suite 4.0.1004 or higher

Of course, for ongoing application development, you can then generate or build your EAE and AB Suite applications as needed on your new Libra system.

Alternative 2: Migrate to your new Libra system using a hot patch or IC release that takes advantage of some of the changes in the fabric-based infrastructure. For this alternative, you will need either:

• EAE IC 3.3.3310

• AB Suite hot patch 3.0.1305

• AB Suite 4.0.1009 or higher

These versions of EAE and AB Suite have been formally tested with MCP Release 16.0 on a fabric-based Libra system and incorporate the database library and other independent code files that are optimized for these new systems. >>

September 2014 – Page 4

Weaving EAE and AB Suite into the New Fabric-Based ClearPath Systems

The newest ClearPath Libra systems are part of a groundbreaking architectural transformation that uses an innovative, fabric-based infrastructure to extend the inherent strengths of the Intel® based ClearPath environment to new ends.

Developing Agility

September 2014 – Page 5

Alternative 3: Fully leverage the fabric-based infrastructure with AB Suite release 5.0. In either the initial release of AB Suite 5.0, or a future IC, we will implement changes that leverage the full capabilities of the fabric-based infrastructure.

From this point onward, Unisys will build, test, and support two packages of the AB Suite Runtime for ClearPath MCP: one for non-fabric systems and one for the new fabric-based Libra systems.

Getting StartedWe recommend that you work with your Unisys sales rep and support contact to determine how best to transition your EAE and/or AB Suite applications to the new fabric-based Libra architecture. They can explain scenarios in more detail and help you make a decision. Or, you can send your questions to ABSuite@Unisys.com.

One final note: There are no plans to fully leverage the fabric-based infrastructure for EAE.

Developing Agility

AB Suite Runtime Administration TodayThe Agile Business Suite Runtime for Windows is administered primarily through the AdminTool MMC interface. While most of the commonly used administration tasks are available from this

interface, there are several capabilities that are not part of the console.

These remaining capabilities tend to be spread out among a number of standalone utilities (such as DPM.exe and Admin.exe), Registry Keys, configuration files (such as DBConfig.XML), and other consoles, including Component Services. The result is an inconsistent mix of interfaces that behaves differently and requires an AB Suite runtime administrator to have privileged access to many different parts of an application server’s environment. The Runtime API PhilosophyThe idea behind a runtime API is to consolidate all administration functionality into a single, consistent, efficient interface. And, the AB Suite team has come up with a new interface that sits on top of, or in some cases, replaces, the old interfaces: the AB Suite Runtime API.

It’s much more “script friendly,” so runtime administrators can avoid the need to sit at an AdminClient console late at night waiting for a task to complete. It can be managed within a wider application ecosystem through system dashboards and other tools, helping to promote third-party integration. It presents everything in a neatly laid out GUI that makes it easy to visualize the available options – especially for anyone who isn’t familiar with runtime administration. It can, in some cases,

support zero-touch operations. And finally, a modular design allows its capabilities to easily to extend to match the growing needs of the AB Suite Runtime.

The .NET API The Runtime API is, first and foremost, an API. So at its core it is a programmable interface that can be readily referenced by .NET programs. A single assembly (Unisys.AgileBusiness.RuntimeAPI.dll) containing all of the API’s interfaces and methods is shipped with the AB Suite Runtime for Windows 4.0 and above. This is great for developing customized administration programs, and is recommended for administrators who need to integrate the AB Suite Runtime for Windows with third-party programs.

namespace MyCustomAdmin

{

using System;

using Unisys.AgileBusiness.RuntimeAPI;

using System.Security;

class Program

{

…

Figure 1. The AB Suite Runtime API assembly.

Once you have the assembly referenced in Figure 1, a number of specific AB Suite Runtime administration interfaces and methods become available for your custom program to call.

AB Suite 4.0 provides three interfaces aimed at automating some of the tasks done today via a GUI:• IConfigureRuntime: Log and Protocol Adapter

configuration capabilities. >>

September 2014 – Page 6

Engineering Corner: AB Suite Runtime for Windows – Runtime API By Andrew Lee, Software Architect, AB Suite Runtime for Windows,

Technology Products, Unisys

Developing Agility

September 2014 – Page 7

• IDeployPackage: Runtime Transfer, Deployment, and Deployment Package Manager capabilities.

• IAdministerSystem: System Administration Commands, which roughly overlap in functionality with the old Admin.exe utility.

In AB Suite 5.0, these are extended and joined by one new interface:

• IConfigureSystem (new for 5.0): Adds the ability to configure deployed runtime systems, including database commands and COM+ properties.

• IConfigureRuntime: Now allows Views to be programmatically added and deleted and gives them access to a number of runtime-specific registry and environment settings.

• IAdministerSystem: Extended to support Printing properties, audit log configuration, and miscellaneous system-specific functionality.

• IDeployPackage: DPM for reports now also added.

So, if you use the custom program from Figure 1 to perform a deployment, you could use the IDeployPackage interface as shown in Figure 2.

You will notice that the API supports Factory patterns in order to gain an instance of the AB Suite Deployment Manager. Most Runtime API method calls requiring complex input parameters will use the parameter structures highlighted in the middle, which are mostly unique to each interface, so that the right parameters are always passed to each method. Finally, some methods return output via a Callback, which is created in a single call, allowing progress and output messages to be handled by the custom administration program. The StatusInfo return object is a class that contains an error number, plus a string description of the return status. >>

Developing Agility

class Program { static void Main(string[] args) { //Get the deployer

IDeployPackage deployer = RuntimeFactory.GetDeployer();

//GetDeployer sets up security behind the scenes // Set up the password to pass to deployer SecureString securePwd = new SecureString(); string pass = //some string from a file – do not hard code passwords in your script! foreach (char c in pass) securePwd.AppendChar(c);

//Construct the PackageInstallParameter PackageInstallParameter param = new PackageInstallParameter() { DeployPackagePath = @”C:\TEMP\stagingarea\NGENSampleDeploy.msi”, UserName = @”ApplicationUser”, Password = securePwd };

//Get the callback object for progress message CallBackHandler callBack = new CallBackHandler();

StatusInfo statusInfo = deployer.PackageInstall(param, callBack); }}

Figure 2. An example of the IDeployPackage interface.

September 2014 – Page 8

You will also find that a Runtime API log – in the standard AB Suite Runtime’s Data\Log location – is provided in case you need to diagnose specific issues with the API calls.

There are some variations to how each interface is used, driven primarily by the underlying, and often pre-existing, implementation. But generally, programmatic access to runtime administration functionality is fairly similar to the example in Figure 2. The product documentation provides detailed descriptions of every interface, method, and parameter, as well as use cases to get you started.

Command-Line UtilitiesThe Runtime API also includes command-line utilities. These allow easy access to runtime administrative functionality from command shells, scripts, and batch files. Operations that were once GUI only, such as Runtime Transfer, or required access to specialized consoles, such as registry and XML editors, can now be easily accomplished via a scripting operation. These command-line utilities effectively wrap the APIs shown in Figure 2 in a utility that is installed with the AB Suite Runtime for Windows.

Note that the utilities follow a “verb-name” naming convention – ConfigureLog, for example – to improve readability. And in some cases, the underlying interface’s functionality is divided among multiple command-line utilities to reduce the number of parameters in some commands.

The AB Suite 4.0 Runtime API includes the following command line utilities:

• DeployPackage.exe: Runtime Transfer and Deployment functionality.

• ManagePackage.exe: Deployment Package Manager functionality.

• ConfigureLog.exe: Runtime Log settings configuration.

• ConfigureAdapter.exe: Protocol Adapters configuration.

• AdminSystem.exe: Runtime administration colon commands and report administration operations.

The AB Suite 5.0 Runtime API enhances these utilities and adds two new commands for configuring deployed systems and the runtime environment:

• ConfigureSystem.exe (new for 5.0): Adds command-line access to system database configuration settings and many COM+ settings.

• AdminSystem.exe: Adds Audit Log and Multilanguage settings, UMT checking, and system printing property configuration.

• ConfigureRuntime.exe (new for 5.0): Allows access to view creation and deletion, runtime registry, and environment configuration.

An example of the DeployPackage.exe, which provides access to all the runtime transfer and deployment functionality, is shown in Figure 3.

DeployPackage.exe /L <DeployPackagePath> /U <UserName>

/P <Password> [/DN <DeploymentName>] [/PC <true|false>]

[/RDB <true|false>] [/BDB <true|false>] [/TSN <TargetServerName>] [/TDBR < TargetDatabaseRegistration>] [/TDBN <TargetDatabaseName>] [/TP <TargetPath>] [/TS <TargetSystemName>] [/TW

<TargetWinformPath>] [/?]

Figure 3. An example of the DeployPackage.exe.

Again, please refer to our product documentation for detailed descriptions and examples.

SecurityThe Runtime API and the command-line utilities are built on top of the existing AB Suite Runtime infrastructure, and also require users to have the same privilege levels before they can access administrative functionality. At the center of runtime administration authorization lays the COM+ role-based authentication mechanism, which defines the users that have privileges to perform various tasks. >>

Developing Agility

September 2014 – Page 9

Therefore, Runtime API access can be controlled via the same mechanism. And in most cases, users can be granted access to runtime administration simply by adding their accounts to the necessary roles detailed in the product documentation. In some cases, the operating system will require users to be members of the local administrators group, particularly in Deployment.

To make configuration a little easier, the AB Suite 4.0 Runtime added a new local users group “AB Suite Runtime Administrators” to a runtime server.

Figure 4. The AB Suite Runtime Administrators Properties window.

By default, no one outside of users who were given permission in previous releases, such as a local administrator, is allowed additional access to runtime administration. All you need to do to grant non-administrators access to Runtime administration functionality is add users to this group. Alternatively, if you wish to limit usage of this functionality, you can delete this group and tailor the individual role membership settings in COM+ to your specific requirements.

A Word on Remote Administration…As of now, the Runtime API is accessed locally on an application server – there is currently no official means of accessing these commands remotely. The AB Suite team is in the process of looking into providing remote administration capabilities that align with our Client Framework strategy. In the meantime, aside from exposing custom-written services, we recommend using remote-desktop-based alternatives, such as RemoteApp, to remotely access Runtime API commands.

The AB Suite team plans to extend the Runtime API in future releases and make it the main platform from which we build new AB Suite Runtime administration capabilities. We are eager to see how the AB Suite community extends the Runtime API and welcome any suggestions on where you would like us to take this feature.

Developing Agility

Using the standard AB Suite Model Export Utility and a separately licensed dll, you can export a model file from your database that is written in a clear, easy-to-read XML format, giving you the access you need to make bulk updates with the help of a custom-written script or basic editor.

Once you’re ready to load the model back into the database, the PModel Validator, a standalone tool, can be used to double check your changes, flag any issues, and notify you if any unauthorized/inconsistent updates have been made prior to it being imported back into the AB Suite model database. The modified model will also be validated during the import process.

So how can you use the PModel file in your environment? Consider these real-world situations where the feature was put to good use.

EAE to AB Suite Migration – Model Bulk ChangeRob Henrichs tells of an organization that routinely used a Global Setup Data construct (GSD) in the CriticalPoint SD Report option in EAE. As a part of its AB Suite migration planning, the company determined that this approach would not work in a more Object-Oriented environment without some modification. Since the GSD was referenced in a Performable Global Logic and could be inserted hundreds of times in the report, it was necessary to add a parameter to provide more specific information.

The Public Model File along with the AB Suite Model Export Utility delivered an easy fix in just a few steps:

• First, using AB Suite Developer, a parameter was added to the methods involved, which inherit from the GSD in the application

• Next, all reports were exported using the PModel file format

• Then, a VBScript was run against the exported reports to update all instances where the methods are called, changing the LDL+ construct from Method() to Method(parameter) in the PModel file

• Finally, the changed PModel file with the updated reports was imported back into the AB Suite model database

This migration had to be done for multiple versions of the same application, so using the PModel capability helped to make sure that no instance of the GLG was missed. Plus, it was quick and helped to mitigate the risk associated with making manual updates.

Simplifying Bulk UpdatesGary Taylor has used the PModel file format for similar bulk updates. For example, it’s helped him fix up Graphical Attributes, such as button size, which are expanded by the migration process. In this case, he developed a Microsoft Visual Basic® .Net program that reads a parameter file to determine what to fix up in the previously >>

September 2014 – Page 10

Get to Know the Public Model File

There may be times when you have to make the same or similar changes to many objects within your Agile Business Suite application. You could use AB Suite Developer, but there’s another approach that’s much simpler and more programmatic: consider using the Public Model (PModel) file format in the AB Suite Model Export Utility.

Developing Agility

September 2014 – Page 11

extracted PModel file and makes the changes. The file was then imported back into the AB Suite model database.

Replacing EAE UtilitiesBut the PModel file can be used in other ways, as well. Over the years, there were a number of utilities and third-party products that “grew” around the LINC/EAE product. Nigel Tunnicliffe has used the PModel file format as a means of providing similar capabilities for AB Suite. Here are two examples.

One customer had an Automatic History Generator (AHG) for EAE that captured Ispec data along with the current Ispec definition as part of an audit trail. As many of our readers know, EAE applications are used for years and years but are frequently modified as needed. The AHG generates logic to read and write to an audit trail based on the current definition of the Ispec. Nigel used the PModel file to replicate this capability once the customer moved its application to AB Suite.

The AB Suite Model Export Utility and PModel file format made these updates to the AHG simple:

• First, it extracted the PModel definition of the Ispecs that have been updated

• Then, the AHG read the PModel definition and updated templates for the logic that reads and writes to the audit trail using these new Ispec definitions

• Finally, the updated templates were exported into a PModel file, which was then manually re-imported into the AB Suite model database.

Nigel has also used the PModel file format to replace a development tool that enables developers to determine the impact of a potential application change. With Nigel’s new utility, a developer can find the answer to questions such as:

• “Where is this class stored in the database?”

• “Which other methods invoke this method?”

• “Where is this attribute used in an arithmetic statement?

• “Which comment lines contain a reference to Fix number 1234?”

Ready to Give It a Try?The PModel file format is available to AB Suite customers through a separate licensing mechanism. There is no charge for the feature but you must sign an addendum to your existing software agreement. If you are interested in obtaining a copy, please contact Maarten Schneider to start the process.

And for even more information, please read our whitepaper.

Developing Agility

Developing Agility September 2014 – Page 12

Info Center and Calendar

Specifications are subject to change without notice.

© 2014 Unisys Corporation.

All rights reserved.

Unisys, the Unisys logo, ClearPath, and Forward! by Unisys are registered trademarks or trademarks of Unisys Corporation. Intel is a registered trademark of Intel Corporation in the U.S. and/or other countries. Linux is a registered trademark of Linus Torvalds. Microsoft, SQL Server, Windows, Visual Basic, and Visual Studio are registered trademarks of Microsoft Corporation. All other brands and products referenced herein are acknowledged to be trademarks or registered trademarks of their respective holders.

WHAT

Universe Conference

EAE/AB Suite Symposium

European EAE/AB Suite Technical Seminar

WHERE

Dallas, Texas

Dallas, Texas

Amsterdam, Netherlands

WHEN

October 13-15, 2014

October 13-15, 2014

October 21-22, 2014

New additions to our libraries of How To documents, white papers, and other useful information include:

• How To: Extract Version Attributes from Windows Runtime System DLLs (NEW)

• How To: Configuring Firewalls for Networked AB Suite Windows Runtime (Updated)

• How To: Use Registry Keys with Windows Runtime (Updated)

To view these and other resources, simply go to public.support.unisys.com, choose “Documentation” in the “Public Information” box located on the left-hand side of the screen. No special login is needed.

We also encourage you to view the list of available AB Suite training courses. These courses are a great educational resource and include a lot of graphics, interactivities, simulations, and demonstrations with voice-over narration.

And for even more training and educational resources, please visit the Unisys Education & Training web site and check out the AB Suite Course Catalog.

Mark your calendar for these upcoming events: