ClearPath eportal Developer Help

Transcription

1 ClearPath eportal Developer Help Unisys Corporation. All rights reserved.

2 1 Table of Contents 1. Table of Contents 1-14 ClearPath eportal Developer Help 15 Getting Started 15 What's New? Documentation Updates 16 ClearPath eportal Overview Upgrading Projects 18 Importing ClearPath eportal 5.0 or Later Projects Upgrading a Web Site to a Web Application 19 Upgrading Themes for Web Forms Mobile Projects Updating NuGet Packages 20 Multi-Targeting Issues Preparing to Use ClearPath eportal Developer Modernizing Your Application 22 Modernizing a T27 Application Preparing to Capture the Screens of T27 Applications Creating a Web Presentation for a T27 Application with Minimal Work Creating a T27 Data Source Project Modernizing an MCP COBOL Application Preparing To Use the MCP COBOL Data Source Wizard Creating an MCP COBOL Data Source Project Modernizing an OS 2200 Open DTP Application Preparing to Use the OS 2200 Open DTP Data Source Wizards Translation Considerations Metadata Fields 42 Open DTP Configuration Considerations Creating an OS 2200 Open DTP Data Source Project Modernizing an OS 2200 TIP Application 45 Preparing to Create eportal Messages from Your TIP Application 46 1 ClearPath eportal Developer Help

3 Preparing to Use the DPS Import Form Library Dialog 46 Using the FLMU Utility DPS Form to Server Message Mapping Preparing to Use the OS 2200 COBOL Data Source Wizard Translation Considerations 52 Metadata Fields Creating an OS 2200 TIP Data Source Project Modernizing an OS 2200 UTS Application 54 Preparing to Capture the Screens of a UTS Application Creating a Web Presentation for a UTS Application with Minimal Work Creating an OS 2200 UTS Data Source Project Integrating an AB Suite/EAE Application with eportal Preparing to Use the AB Suite/EAE Ispec Import Dialog Support for Multiple AB Suite/EAE Applications 60 Support for AB Suite/EAE Features Creating an AB Suite/EAE Data Source Project Creating and Modifying Client Messages 62 Understanding Client Messages Creating Client Messages Modifying Client Messages Deleting a Client Message 66 Runtime Error Checking for Message Fields Controlling the Flow of Data Creating a Simple Orchestration Using Map and Forward to Simplify Orchestration 70 Using Orchestration to Identify an Output Server Message Creating Loops and Branches Creating Reusable Code with an Orchestration Process 73 Using External Code with an Orchestration Process Using External Code with an Orchestration Message Filter 74 Using the OrchExtensions Class ClearPath eportal Developer Help

4 Logging from your Orchestration 77 Consolidating Multiple Server Messages into One Client Message Orchestration Tasks for MCP COBOL Projects Orchestration Tasks for OS 2200 Open DTP Projects Orchestration Tasks for OS 2200 TIP Projects Orchestration Tasks for OS 2200 UTS Projects Orchestration Tasks for AB Suite/EAE Projects Determining the Type of a Received Message Handling Exceptional or Abnormal Conditions Debugging an Orchestration 89 Understanding Orchestration Preparing to Build Your Presentation Project 92 Getting Ready to Build a New Presentation Project Choosing Web Forms or MVC Creating an MVC Web Application Creating Web Forms Application Projects 95 Creating an ASP.Net Web Application Creating an ASP.Net Web Application (Terminal Screen Appearance) Creating an ASP.Net AB Suite/EAE Web Application Creating Web Forms Mobile Application Projects Creating an ASP.Net WebApp for use with Smartphone Devices Creating an ASP.Net AB Suite/EAE WebApp for use with Smartphone Devices Creating an ASP.Net WebApp for use with Tablet Devices Creating a Unisys Multi-Device App 102 Creating Web Service Application Projects 102 Choosing WCF or Web API Creating a Web API RESTful Service Application Creating a WCF Service Application using Scaffolding Creating a WCF Service Application Creating a WCF ASP.Net Compatibility Service Application Creating a WCF RESTful Service Application ClearPath eportal Developer Help

5 Modifying the Web.config File Controlling the Look and Feel of Your Presentation 112 Modifying the Styles for T27 and UTS Projects Modifying the Master Page Modifying the Layout Page Modifying the Web Form Template 117 Controlling the Look and Feel in a T27 Data Source Project Controlling the Look and Feel in a UTS Data Source Project Controlling the Look and Feel in All Data Source Projects Controlling the Look and Feel using Visual Studio Web Editors 125 Editing.cshtml Files Editing.aspx Files 126 Bootstrap Themes for MVC Projects 126 The Default Bootstrap Theme The Unisys Modern Bootstrap Theme 127 Other Bootstrap Themes 127 Changing the Selected Bootstrap Theme Controlling the Theme Selection for a Web Forms Mobile Project 128 About Themes 128 App_Themes Directory Structure 128 Included Themes Designer Theme Selection 129 Runtime Theme Selection Project Item Templates for Web Forms Mobile Presentation Projects 130 Creating a New Mobile Web Content Form Configuring an Icon and Startup Image for an ios Application 131 Using the Polymer Icons NuGet Package Controlling the Runtime Behavior of Your Presentation 132 Controlling the Runtime Behavior for MVC Web 132 Generated MVC Files ClearPath eportal Developer Help

6 Programming in the Controller for MVC Web Validating MVC Web Pages 134 Controlling the Runtime Behavior for Web API 134 Generated Web API Files 134 Programming in the Controller for Web API Controlling the Runtime Behavior for WCF Services Using Scaffolding 135 Generated WCF Service Files for WCF Services Using Scaffolding Programming in the Service Implementation for WCF Services Using Scaffolding Programming in the Custom Validators for WCF Services Using Scaffolding 137 Controlling the Runtime Behavior for WCF and WCF ASP.Net Services Generated WCF Service Files for WCF and WCF ASP.Net Services 138 Programming in the Service Implementation for WCF and WCF ASP.Net Services Programming in the Custom Validators for WCF Services (Without Scaffolding) 139 Controlling the Runtime Behavior for Web Forms Generated Web Forms Files 140 Opening the Generated Web Forms Files 140 Programming in the Code-Behind File Validating Web Forms Pages 143 Validation Performed by HTML5-Compatible Browsers Validation Performed by eportal 145 Adding Validation to Your Web Forms Page 145 Controlling the Runtime Behavior for AB Suite and EAE Logging Messages from your Code Configuring Redundant Application Connections 148 Preparing Your Project for Use 148 Testing a Presentation Project Testing an MVC Web Application Testing a Web Forms Application 150 Testing a Web Forms Mobile Application Testing a Web API RESTful Web Service Application Using the Web API RESTful Test Client ClearPath eportal Developer Help

7 Testing a WCF RESTful Web Service Application Using the WCF RESTful Test Client Testing Other Web Service Applications Publishing to IIS Defining Additional Performance Counters 158 Staging a Presentation Project Restaging a Presentation Project 160 Modifying Your Project 160 Modifying T27 Projects 160 Modifying the Connection Properties Connecting to and Disconnecting from the T27 Application 161 Restarting a Screen Capture 161 Modifying Existing Server Messages 161 Recapturing a Screen Deleting Server Messages 163 Modifying UTS Projects 163 Modifying the Connection Properties 163 Connecting to and Disconnecting from the UTS Application 163 Restarting a Screen Capture Modifying Existing Server Messages 164 Recapturing a Screen Deleting Server Messages 165 Modifying MCP COBOL Projects 165 Handling Updates to the MCP Application Code Changing the COBOL Data Identifier 166 Deleting Server Messages 166 Modifying OS 2200 Open DTP Projects Handling Updates to the OS 2200 Open DTP Application Data Definitions 167 Handling Updates to the OS 2200 Open DTP Service Name Changing String to Binary or Binary to String 168 Changing String Field Properties ClearPath eportal Developer Help

8 Changing the COBOL Data Identifier Deleting Server Messages 169 Modifying OS 2200 TIP Projects 169 Handling Updates to DPS Forms 169 Handling Updates to the OS 2200 TIP Application Data Definitions Handling Updates to the OS 2200 TIP Transaction Code Changing the COBOL Data Identifier for OS 2200 TIP Projects 171 Deleting Server Messages for OS 2200 TIP Projects 171 Modifying AB Suite/EAE Projects 171 Handling Updates to the AB Suite/EAE Ispecs Changing Table Generation for Copy Ispecs 172 Changing Automatic Control Label Generation 172 Modifying Presentation Projects Changing to a Master Page 173 Changing Presentation Generation Options Removing a Dynamic Region from an.aspx File 174 Viewing or Changing eportal Application Configuration Properties. 174 Controlling Source Files 174 Using Source Control Working with Controlled Files 175 Building Your eportal Solution 175 Build Configurations 175 Building the Solution Cleaning the Solution 177 Rebuilding the Solution 177 Using an SDF Formlibrary Using an SDF Formlibrary with eportal 178 Using the SDFXMLEXTRACTOR Utility Modernizing an SDF COBOL Application using a T27 Data Source Project Migrating an SDF COBOL Application into an MCP COBOL Data Source Project ClearPath eportal Developer Help

9 MCP COBOL Data Source Project Considerations Consuming the Web Service Methods by a Web Service Client 186 Consuming RESTful Web Services 186 Consuming Other Web Services eportal Command-line Tools Building the Solution from the Command Line 188 Updating the Configuration Files (Optional) Staging the Presentation Project from the Command Line Configuring File Transforms Deploying an Application from the Command Line UnDeploying an Application from the Command Line Troubleshooting 194 Logging Errors and Tracing Gathering Diagnostic Information 195 Blank Lines are Missing in the Presentation Project Cannot Connect to Host 196 eportal Developer Controls Are Missing 196 eportal Toolbox Item Is Missing 196 Deleted Dynamic Regions Reappear after a Build 196 No Generators Found for Target Project No matching record identifier found 197 No Valid Connection found for this Session 197 Presentation Pages Do Not Reflect Master Page Content 197 Presentation Pages Do Not Reflect Web Form Template Contents Screen Columns Do Not Line Up 198 Search for ClearPath eportal Help Does Not Work 198 Presentation Application Did Not Launch 198 Connection Errors and Timeouts When Using Web Services Unexpected Errors When Submitting Large Web Pages 199 Unable to Load Unisys.MCPT27.WebEnablerRuntime 199 Unrecognized Attribute targetframework Occurs When Running a Published Web ClearPath eportal Developer Help

10 Application Unable to Access MVC Web Application from a Unisys Multi-Device AppHybrid Mobile Application Examples 200 Sample Applications 200 T27 Project SDFXMLEXTRACTOR Utility Example COBOL Project SDFXMLEXTRACTOR Utility Example Using a CustomValidator with Message Field Runtime Error Checking MVC Scaffolding and Templating Examples Reference Information Alternate Methods of Initiating Tasks Data Source Project Property Pages Dialog MCP COBOL Data Source Project Property Pages Dialog OS 2200 Open DTP Data Source Project Property Pages Dialog OS 2200 TIP Data Source Project Property Pages Dialog 215 AB Suite/EAE Data Source Project Property Pages Dialog Reference Information for MCP T27 Projects 217 T27 Editor and Dialog Boxes 217 Dynamic Region Array Dialog 217 T27 Emulator T27 Screen Editor T27 Connection Properties Dialog 219 T27 Property Descriptions 219 T27 Dynamic Field Property Descriptions T27 Emulator Property Descriptions T27 Field Property Descriptions T27 Page Identification Region Property Descriptions T27 Page Property Descriptions 224 Reference Information for MCP COBOL Projects MCP COBOL Data Source Wizard Pages 225 Welcome ClearPath eportal Developer Help

11 Select the COBOL Source File 225 COBOL Data Description Selection Specific Definition 226 Select the COBOL Data Identifier Update Existing MCP COBOL Data Description Wizard Pages Welcome 228 Select The COBOL Source File 228 Found Data Descriptions 228 Select the COBOL Data Identifier Warning Screen 229 Finish Page 229 MCP COBOL Configuration Dialog Box COBOL Record Editor 230 Reference Information for OS 2200 Open DTP Projects Add Open DTP Server Message Dialog 231 OS 2200 Open DTP View Data Source Wizard OS 2200 Open DTP X OCTET Data Source Wizard OS 2200 Open DTP COBOL Data Source Wizard Update Existing OS 2200 Open DTP COBOL Data Description Wizard OS 2200 Open DTP Record Editor 236 OS 2200 Open DTP Configuration Dialog 236 Reference Information for OS 2200 TIP Projects DPS Import Form Library Dialog Configure Discriminator Field Dialog 238 OS 2200 COBOL Data Source Wizard Update Existing OS 2200 COBOL Data Description Wizard OS 2200 TIP Configuration Dialog 242 Reference Information for OS 2200 UTS Projects 242 UTS Editor and Dialog Boxes 242 Dynamic Region Array Dialog 242 UTS Emulator ClearPath eportal Developer Help

12 UTS Screen Editor UTS Connection Properties Dialog 244 UTS Property Descriptions 244 UTS Dynamic Field Property Descriptions UTS Emulator Property Descriptions UTS Field Property Descriptions UTS Page Identification Region Property Descriptions 247 UTS Page Property Descriptions UTS Emulator Keyboard Map Reference Information for AB Suite/EAE Projects 252 AB Suite/EAE Ispec Import Dialog Reference Information for Scaffolded Projects 255 Using Multiple Data Source Projects Choosing a Traditional or Single Page Application Add Unisys eportal Data Source Reference Dialog 257 Scaffolding 257 Overview of Scaffolding Scaffold Templates Creating Custom Scaffold Templates Editor Templates Invoking Scaffolders Scaffold Unisys WCF Service for eportal Data Source Dialog Scaffold Unisys Web API Controller for eportal Data Source Dialog Scaffold Unisys Controller for eportal Data Source with Views Dialog Scaffold Unisys Controller for eportal Data Source Dialog Scaffold Unisys View Dialog Terminal Options Dialog 273 AB Suite/EAE Options Dialog 273 Best Practices for Scaffolded Presentation Projects Reconciling Client Message Changes to Scaffolded Presentation Projects Localization Support for MVC ClearPath eportal Developer Help

13 Configuring a Data Source Project for Localization 276 Manage Languages Dialog 277 Reference Information for Orchestration 277 Orchestration Property Descriptions 277 Orchestration Properties Throw Activity Property Descriptions 279 Orchestration Editor and Dialog Boxes 279 Orchestration Editor Assign Data for Message Dialog Box Edit Condition Dialog Box Orchestration Exceptions Orchestration Exception Properties Orchestration Toolbox Selections Programming Keystrokes for T27 and UTS Applications Key Sequence Editor Dialog Theme Management Dialog 297 eportal Developer Controls 297 eportal Developer Controls for Web Forms Mobile Projects eportal Developer Controls for Web Forms Projects 298 eportal Associated Controls 298 eportal Labeled Controls ARIA Labeled Controls Other eportal Controls eportal Developer Controls for MVC Web Projects 304 eportal Message View Open Presentation Files Reconcile Presentation Files 306 Delete Presentation Files 306 Generate Presentation Files 307 Message Editor ClearPath eportal Developer Help

14 Message Editor Root Node Properties Message Editor Field Properties 309 Message Editor Toolbox Selections Save Message Dialog 310 ListItem Collection Editor Dialog Property Descriptions 311 eportal Application Configuration Property Values 311 MCP T27 Application Configuration Properties MCP COBOL Application Configuration Properties OS 2200 Open DTP Application Configuration Properties OS 2200 TIP Application Configuration Properties OS 2200 UTS Application Configuration Properties AB Suite/EAE Application Configuration Properties WebServer Properties 323 Web Properties for a Web Forms Application Project Web Properties for a Web Forms Mobile Project 324 Web Properties for a Web Service 324 Presentation Generation Properties Presentation Generation Properties for a WCF Service Application 325 Presentation Generation Properties for a WCF ASP.Net Compatibility Service Application Presentation Generation Properties for a WCF RESTful Service Application Presentation Generation Properties for an ASP.Net Web Service Application 327 Presentation Generation Properties for a Web Browser Project Presentation Generation Properties for a Web Forms Mobile Project Markup Template Editor Dynamic Character Mapping Web Content Accessibility Guidelines 333 General Guidelines 333 Specify the Human Language for Each Web Page Specify a Title and Description for Each Web Page ClearPath eportal Developer Help

15 Specify Alternate Text for Images 335 Provide Explicit Labels for Inputs Use Tables with Correct Headers 337 Allow Keyboard Access for All Controls Provide Enough Contrast 338 Legal and Copyright Notices Index ClearPath eportal Developer Help

16 ClearPath eportal Developer Help ClearPath eportal Developer Help Unisys Corporation. All rights reserved. Getting Started Review the following topics before getting started with eportal Developer. What'sNew? lists updates and new features added for this release of ClearPath eportal Developer. DocumentationUpdates provides a link to the Problem List Entry (PLE), where future updates to this help file are documented. ClearPathePortalOverview provides an overview of the eportal product and its capabilities. UpgradingProjects provides information for upgrading existing eportal solutions for compatibility with the latest version of eportal Developer. Multi-TargetingIssues provides important information about selecting the correct version of.net for the projects you use with ClearPath eportal Developer. PreparingtoUseClearPathePortalDeveloper provides information to get you started. What's New? The following topics have been added or updated in this release: NeworUpdatedInformation Additional Performance Counters information Updated --drainwaittime option description Host Application Redundancy information AffectedTopics DefiningAdditionalPerformanceCounters DeployinganApplicationfromtheCommandLine UnDeployinganApplicationfromtheCommandLine ConfiguringRedundantApplicationConnections MCPT27ApplicationConfigurationProperties MCPCOBOLApplicationConfigurationProperties OS2200TIPApplicationConfigurationProperties OS2200UTSApplicationConfigurationProperties ABSuite/EAEApplicationConfigurationProperties 15 ClearPath eportal Developer Help

17 Scripted Build Stage Deployment information Message Filter information Logging information from your Orchestration Removed references of Unisys Multi- Device Simulator eportalcommand-linetools BuildingtheSolutionfromtheCommandLine UpdatingtheConfigurationFiles StagingthePresentationProjectfromtheCommandLine ConfiguringFileTransforms DeployinganApplicationfromtheCommandLine UnDeployinganApplicationfromtheCommandLine UnderstandingOrchestration UsingExternalCodewithanOrchestrationProcess UsingExternalCodewithanOrchestrationMessageFilter UsingtheOrchExtensionsClass OrchestrationToolboxSelections LoggingfromyourOrchestration CreatingaUnisysMulti-DeviceApp ChoosingaTraditionalorSinglePageApplication ControllingtheRuntimeBehaviorforMVCWeb Documentation Updates This document contains all the information that was available at the time of publication. Changes identified after release of this document are included in problem list entry (PLE) To obtain a copy of the PLE, contact your Unisys representative or access the current PLE from the Unisys Product Support website: Note: If you are not logged into the Product Support site, you will be asked to do so. ClearPath eportal Overview With ClearPath eportal, you can quickly modernize the look and feel of many ClearPath server applications. Once a presentation project is created in ClearPath eportal Developer, it can be deployed on a ClearPath eportal Web Cluster. Refer to the ClearPath eportal Implementation and Operations Guide for a complete description of the total product. The following elements make up the product. Element ClearPath eportal Developer ClearPath eportal Management Website Description A Visual Studio plug-in that enables you to capture the interfaces of existing ClearPath server applications into a data source project and orchestrate the flow of data between the newly designed Web interfaces or Web services and the existing mainframe application. The ClearPath eportal data source project is then used to create the contents of the presentation projects. The plug-in uses Visual Studio conventions. A browser-based point-and-click management environment that automates the processes required to deploy, configure, and manage applications on eportal Web Partitions. 16 ClearPath eportal Developer Help

18 ClearPath eportal Web Partition ClearPath eportal Web Cluster An environment used to export ClearPath applications and data in an industry-standard technology, for example, HTML/Web Service. A web partition or clustered set of web partitions that functions and is managed as a single "virtual" server. All web partitions in a set share the same applications and configuration information. TheGeneralModernizationProcess Follow this general process to modernize an existing ClearPath server application: 1. Plan the new interface by deciding the presentation method and the functions that the new interface needs to perform. The new interface does not have to include all the functionality of the existing ClearPath server application. For example, you might want to create a Web service for inventory inquiry. The new interface and current interface to the ClearPath server application can work concurrently. Refer to the ClearPath eportal Implementation and Operations Guide for information on planning the new interface. 2. Use ClearPath eportal Developer to do the following. Refer to PreparingtoUseClearPathePortalDeveloper for more detailed information about the steps. a. Create an eportal data source project. b. If necessary, create the data flow logic using the orchestration functionality. c. Create the appropriate eportal presentation project or projects. d. Test the eportal presentation project or projects locally. e. Stage the presentation or presentations to the ClearPath server. 3. Use ClearPath eportal Manager to deploy the staged new presentation on the appropriate ClearPath eportal Web Cluster. BasicFacts An eportal data source project contains server messages, client messages, and logic for each client message received from a client. All of the logic is referred to as an orchestration. The client messages of a data source project can be used to populate one or more eportal presentation projects. Refer to GettingReadytoBuildaNewPresentationProject. If an orchestration cannot be designed to facilitate multiple eportal presentation types, another data source project must be created, and an appropriate eportal presentation or presentations created, and populated with the data of the client messages of the new data source project. IdentifyinganOutputServerMessage Whenever eportal receives output data from the ClearPath server, eportal must map this data to a particular eportal server message. For some output server message types, the output data stream contains a separate protocol item that identifies the particular data received, in addition to the message data itself. In this case, eportal can automatically find the correct eportal server message to use. The following are the server message types in which the output data stream contains a separate protocol item that identifies the data: Server messages created with the OS2200OpenDTPViewDataSourceWizard Server messages created with the OS2200OpenDTPX_OCTETDataSourceWizard Server messages created with the ABSuite/EAEIspecImportDialog For all other cases, the output data stream does not contain a separate protocol item to identify the correct eportal server message to use. Instead, the application developer must provide additional information so eportal can find the correct eportal server message. Consult one of the following topics for more information regarding your topic type: PlanningtheDataIdentificationStrategy in PreparingtoCapturetheScreensofT27Applications 17 ClearPath eportal Developer Help

19 PlanningtheDataIdentificationStrategy in PreparingtoUsetheMCPCOBOLDataSourceWizard PlanningtheDataIdentificationStrategy in PreparingtoUsetheOS2200OpenDTPCOBOLDataSource Wizard PlanningtheDataIdentificationStrategy in PreparingtoUsetheOS2200COBOLDataSourceWizard PlanningtheDataIdentificationStrategy in PreparingtoCapturetheScreensofaUTSApplication Upgrading Projects If you already have an eportal solution developed with a previous version of eportal developer, follow these steps to upgrade the solution for use with this version of ClearPath eportal Developer: Upgrade your solution using the Visual Studio Upgrade Wizard. See the topic ImportingClearPathePortal5.0or LaterProjects for more information. If your solution contains one or more web forms mobile presentation projects, upgrade the themes for each project. See the topic UpgradingThemesforWebFormsMobileProjects for more information. The legacy web site presentation type is no longer supported in this version of eportal developer. If your solution contains one or more legacy web sites, upgrade these to the appropriate web application project type. See the topic UpgradingaWebSitetoaWebApplication for more information. If you want your projects to target a different.net version, see the topic Multi-TargetingIssues for guidelines and instructions. Starting with eportal Developer 6.0, eportal uses NuGet packages to deliver important functionality. One advantage of a NuGet package is that it is easy to update a NuGet package installed in an existing project. For more information on NuGet, see Any time you install a new major version of eportal or a new Interim Correction (IC), you should check to see if there are updates to the NuGet packages that are installed in your existing presentation projects. See Updating NuGetPackages for more information. Importing ClearPath eportal 5.0 or Later Projects Any ClearPath eportal 5.0 or later projects can be opened directly in Visual Studio The Visual Studio 2015 upgrade wizard handles the upgrade. Notes: ClearPath eportal Developer Help If your solution is under source control using a system which requires explicit file check out, you must check out the data source project file and each presentation project file before starting the upgrade process. The data source project file has an extension of McpT27Proj, McpCobolProj, OpenDtpProj, TipProj, UTSProj or ABSEAEProj. A presentation project file has an extension of csproj. Sometimes a solution that requires an upgrade might load without launching the upgrade wizard; however, the data source project is not loaded. In this case, Solution Explorer displays the note "(Needs Migration)" next to the data source project. In this case, right-click the data source project and select ReloadProject to launch the upgrade wizard. The build process has been optimized to improve build performance. See BuildingYourePortalSolution for more information. As part of this optimization, generated C# files in the Generated Component Code folder (for a data source project) and in the App_Code folder (for a WCF Web Service presentation project) are no longer members of the Visual Studio project. The upgrade wizard excludes these files from the project. If your solution is in source control, you may be prompted whether or not to delete these files from source control. You should delete these files from source control, as the files are not user-editable and are regenerated as needed by the build process. The upgrade process ensures that the data source project is targeting at least.net 4.0. If the data source targets less than.net version 4.0, then the versi on is set to 4.0; otherwise it is left unchanged. The.NET version for presentation projects is also not changed. If you wish to upgrade your projects to a newer version of.net, see the topic Multi-TargetingIssues for more information. If you are upgrading from eportal developer 6.0 or later, be sure to update NuGet packages before attempting to 18 ClearPath eportal Developer Help

20 build. See UpdatingNuGetPackages for more information. After the upgrade completes, and you update the NuGet packages (if applicable), you must perform a full rebuild of your solution by selecting RebuildSolution from the Build menu for the first build on a particular development system. See RebuildingtheSolution for more information. Performing a Build Solution is not sufficient. Upgrading a Web Site to a Web Application DifferencesBetweenWebSitePresentationsandWebApplicationPresentations To create a Web Site presentation type, click File, then click Add, then click NewWebSite. In Solution Explorer, a Web Site presentation displays as a directory path (containing backslash characters), rather than as a project name. A web site does not contain a Visual Studio project file. To create a Web Application presentation, click File, then click Add, then click NewProject. In Solution Explorer, a Web Application displays as a simple identifier (without backslash characters). A Web Application contains DLL references and other settings in a Visual Studio project file. Note: eportal does not support website presentation types. UpgradingtoaWebApplication The legacy Web Site presentation type is not supported in this version of ClearPath eportal Developer. Therefore, you must upgrade any existing Web Site presentations to a corresponding Web Application presentation. Note: Before performing this procedure, you should make a backup copy of your entire solution. For each existing web site, do the following: 1. Add a new Web Forms Application. See the topic CreatingWebFormsApplicationProjects for instructions. 2. In Solution Explorer, right-click the Pages directory in the new Web Application project and select Delete. 3. In Solution Explorer, right-click the Pages directory from the Web Site, and select Copy. Right-click the new Web Application project and select Paste. 4. Repeat step 3 to copy the App_Data directory from the Web Site to the new Web Application. If necessary, confirm overwriting the destination directory. Also, copy any other directories you may have added (for example, App_Code, App_Resources, and Scripts) from the Web Site to the new Web Application. 5. If you have any external web service references in your web site, add each reference as a ServiceReference in the web application. 6. In Solution Explorer, for each code-behind file (.aspx.cs) in the Pages/DataSourceProjectName directory of the new Web Application project, right-click the file and select Properties, then change BuildAction to Content. 7. In Solution Explorer, right-click the Web Site and select Remove. After converting each Web Site, you must rebuild your solution with the Rebuild Solution function; performing a Build Solution is not sufficient. Click RebuildSolution from the Build menu. See the topic RebuildingtheSolution for more information. Upgrading Themes for Web Forms Mobile Projects Unisys may update the contents of themes in future updates to the ClearPath eportal Developer product. For example, if you install a new IC for eportal Developer, Unisys may have made updates to the theme files. Themes in your existing projects are not automatically updated when you install a new IC of eportal Developer. Because of this, there is a separate process you need to complete to bring your projects' mobile themes up to the latest version. Note: The themes are now installed and updated using a NuGet package. Using a NuGet package is a more standard way of updating an existing project. For more information on NuGet, see InstallingtheUnisysClearPathePortalMobileControlsThemes If you are upgrading your solution from ClearPath eportal Developer 5.1 or earlier, then you have never installed the NuGet 19 ClearPath eportal Developer Help

21 package. Perform the following procedure for each mobile presentation project: 1. Open the existing solution in Visual Studio If you have updated any of the theme files under the App_Themes folder, or if you have updated the themeselection.xml file, make a backup copy of these updated files. 3. Right-click the mobile project in Solution Explorer and select ManageNuGetPackages. 4. From the Packagesource list, select UnisysClearPathePortalPackage and click Browse. 5. In the left pane, select Unisys.eportal.mobile.themes, and then click Install in the right pane. The Preview dialog box appears. 6. Click OK to start the installation. 7. Click YestoAll on the File Conflict dialog. 8. If you backed up updated files, you will need to manually reconcile your updates. UpdatingtheUnisysClearPathePortalMobileControlsThemes If you have already previously installed the Unisys ClearPath eportal Mobile Controls Themes NuGet package, perform the procedure documented in the topic UpdatingNuGetPackages. Updating NuGet Packages Starting with eportal Developer 6.0, eportal uses NuGet packages to deliver important functionality. One advantage of a NuGet package is that it is easy to update a NuGet package installed in an existing project. For more information on NuGet, see Any time you install a new major version of eportal or a new Interim Correction (IC), you should check to see if there are updates to the NuGet packages that are installed in your existing presentation projects. Perform the following procedure for each eportal solution to install updated versions of the NuGet packages: 1. Create a backup of the entire solution folder. 2. Open the existing solution in Visual Studio On the Tools menu, click NuGetPackageManager, and then click PackageManagerConsole. The Package Manager Console window appears. 4. Enter the UpdateUnisysNuGetPackages command. Wait for the process to complete. This may take several minutes, depending on the number of packages to be updated. This launches a PowerShell script that updates all Unisys NuGet packages in all projects present in the solution to the most recent versions. Any dependent packages are also upgraded, if required. Multi-Targeting Issues GuidelinesforChoosingtheTargetFrameworkVersion ClearPath eportal Developer Help You may configure and mix various Target Framework Versions (for example,.net versions) for your data source and presentation projects; however, to ensure compatibility, you must follow these guidelines. Visual Studio 2015 automatically installs support for.net 4.5.2, 4.6, and Older versions of the eportal platform may not support all versions of.net. Check with the administrator for the eportal platform to confirm which versions of.net the platform supports. All ClearPath eportal data source project types must target.net 4.0 or later. All presentation projects that reference a ClearPath eportal data source must target a.net version that is greater than or equal to the data source.net version. If you are using eportal with an AB Suite or EAE application, you use the eportal Generator in AB Suite Client Tools to generate Ispec model files that you import to your eportal data source. Your presentation projects must target a.net version that is greater than or equal to the version of.net used to generate these Ispec model files. See PreparingtoUsetheABSuite/EAEIspecImportDialog for more information. 20 ClearPath eportal Developer Help

22 In order to use a ClearPath eportal data source project with an MVC Web presentation or a Web API presentation, the data source must target.net 4.5 or later. Microsoft has ended support for.net 4.0, 4.5, and You can continue to target these.net versions, and your application will run without recompilation on a platform with.net installed. However, you should target.net or later for new projects. See the following blog for more information: SettingtheTargetFrameworkVersionforNewProjects You set the Target Framework Version when you create a new project by selecting the correct.net version on the Visual Studio 2015 New Project dialog. ChangingtheTargetFrameworkVersionforExistingProjects You can change the Target Framework Version for an existing project as follows: 1. In Solution Explorer, right-click the project and select Properties. 2. In the properties dialog, change the TargetFramework property. For a data source project, the Target Framework property is found under the Project category. See DataSource ProjectPropertyPagesDialog. For a presentation project, the Target Framework property is found on the Application tab. 3. Answer Yes to the confirmation message. Preparing to Use ClearPath eportal Developer The ClearPath eportal Developer plug-in uses Visual Studio conventions throughout the interface. This help includes steps for using the plug-in and does not give instructions for using Visual Studio in general. Use the Visual Studio help to learn about Visual Studio functionality. InstitutingSourceControlinVisualStudio If source control is not already instituted in Visual Studio and source control is required, refer to Visual Studio help for information about instituting source control. When source control is instituted in Visual Studio, a ClearPath eportal Developer project can be placed under source control as the project is created. Refer to UsingSourceControl. InstallingandConfiguringClearPathePortalDeveloper Note: Installing ClearPath eportal Developer 7.0 does not automatically uninstall previous versions that use Visual Studio 2010 or 2013; you must remove it manually. In order to use ClearPath eportal Developer, perform the following steps: 1. Install the software. Refer to the release notes (readme file) for ClearPath eportal Developer for instructions. 2. Open Visual Studio 2015, select C# as the language of choice, and ensure that the following windows are present in the interface by selecting them on the View menu of Visual Studio: Solution Explorer Properties Window Other Windows/ePortal Message Window Error List Output Toolbox 3. On the Help menu, select SetHelpPreference LaunchinHelpViewer. 4. Try using eportal Developer with some samples. Refer to SampleApplications. 5. While planning the new presentation interface, identify the application and the features within the application that will be used as the basis for the interfaces. 21 ClearPath eportal Developer Help

23 ClearPathePortalDeveloperProcess The following steps are done in Visual Studio using the ClearPath eportal Developer plug-in. 1. Create an eportal data source project, which creates a Visual Studio solution. 2. Define the connection properties, if necessary, to connect to the ClearPath server application. 3. Create server messages. You create eportal server messages using artifacts from your ClearPath server application. For example, capturing screens from a terminal application or importing records or forms from your application. 4. If needed, create client messages. Refer to UnderstandingClientMessages. 5. If needed, control the flow of data between the end user and the ClearPath server backend software by using the orchestration functionality. Refer to UnderstandingOrchestration. 6. Create one or more eportal presentation projects. Refer to GettingReadytoBuildaNewPresentationProject. 7. Populate each eportal presentation project with information from the eportal data source project by building the solution. Refer to BuildingYourePortalSolution. 8. If an eportal presentation project is not a Web Service application project, make additional look and feel changes to the interface as needed. Refer to ControllingtheLookandFeelofYourPresentation 9. If custom coding is needed, refer to ControllingtheRuntimeBehaviorofYourPresentation. 10. If needed, update configuration properties for each presentation project. Refer to ViewingorChangingePortal ApplicationConfigurationProperties. 11. Test each eportal presentation project locally. Refer to TestingaPresentationProject. 12. Make changes as needed, and retest. 13. Stage the presentation project on the ClearPath server on which the ClearPath portion of the ClearPath eportal software is installed. Refer to StagingaPresentationProject Proceed to the topic ModernizingYourApplication. Modernizing Your Application The following topics describe the steps that you perform to modernize an existing application. Consult the following table to determine which topic to read next. For some applications, more than one topic may apply. In this case, consult each topic that applies to determine the best fit for your application. ApplicationType MCP terminal applications designed for T27 terminals MCP Transaction Server (formerly known as COMS) applications written in COBOL OS 2200 Open DTP applications OS 2200 TIP applications (including applications using DPS) OS 2200 terminal applications designed for UTS terminals AB Suite or EAE applications for either MCP or OS 2200 RelatedInformation ModernizingaT27Application ModernizinganMCPCOBOLApplication ModernizinganOS2200OpenDTP Application ModernizinganOS2200TIPApplication ModernizinganOS2200UTSApplication IntegratinganABSuite/EAEApplicationwith eportal Modernizing a T27 Application The following topics describe the steps necessary to modernize a T27 application. PreparingtoCapturetheScreensofT27Applications 22 ClearPath eportal Developer Help

24 CreatingaWebPresentationforaT27ApplicationwithMinimalWork CreatingaT27DataSourceProject Preparing to Capture the Screens of T27 Applications MCP ClearPath Data Source T27 applications can be modernized with ClearPath eportal Developer only if the application has the following characteristics: Uses forms mode. Works with an input function that uses the transmit option "Transmit page in forms." Note: Some T27 applications require special keys, such as the Specify key, to operate properly. To handle this situation, the client message and server message contain the special field _KeySequence. You use _KeySequence to send keystrokes, such as terminal control sequences or the Specify key, to the application. See the topic ProgrammingKeystrokesforT27 andutsapplications for more information. If you want to quickly provide a Web presentation for a T27 application without implementing any significant changes to the interface appearance, you do not need to capture the screens of your application. Instead, eportal can dynamically generate Web pages that look like your existing T27 application. See CreatingaWebPresentationforaT27Application withminimalwork for more information. However, if you want the flexibility to modify the interface, provide a Web service presentation, and provide a mobile presentation, then you must capture the screens of your T27 application as follows: 1. Plantheidentificationstrategy. 2. Determine if the screens of the MCP application have areas that are changed automatically by the MCP application and cannot be controlled by the user and determine if this information should appear in the new presentation. Such areas might be an area where the date and time are displayed or areas where responses to a request are displayed, such as inventory information. Such areas are marked as dynamic regions in ClearPath eportal Developer. 3. Determine if the MCP application uses the status line of the terminal for display of application data and if this information should be preserved in the new presentation. 4. Determine if T27 highlighting capabilities are used on the screens that are going to be captured, and determine which highlights are used. 5. Determine if the MCP application uses more than one page of the T27 terminal. If other pages are used, each page must be captured. 6. Ensure that the Custom Connect Facility is running on the MCP server. 7. Gather the connection information described in T27ConnectionPropertiesDialog. 8. Proceed to one of the following topics: If you have an SDF Formlibrary, go to UsinganSDFFormlibrary. Otherwise, go to CreatingaT27DataSourceProject. PlanningtheDataIdentificationStrategy At run time, the eportal software must identify the output data that it receives from the MCP application. There are two data identification strategies: Definingauniqueidentifierfortheservermessages Usingorchestrationtoidentifytheservermessagethatyouexpecttoreceive DefiningaUniqueIdentifier To define a unique identifier for a server message, select a region of the screen that contains text that is unique to this server message. If necessary, you can select multiple regions that create a unique identifier for the server message, when combined. These are known as the page identification regions. Normally, the first few lines of a screen contain the screen title and some unique information about the screen. This is 23 ClearPath eportal Developer Help

25 generally a good area to select and establish a page identification region. See Procedure3-AddingRuntimeInformationtotheServerMessage in CreatingaT27DataSourceProject. UsingOrchestration If a screen does not include a unique page identification region, then you can elect not to provide one when you capture the screen. If you do not provide a page identification region, you must use orchestration to identify which server message you expect eportal to receive. See UsingOrchestrationtoIdentifyanOutputServerMessage for more information. Creating a Web Presentation for a T27 Application with Minimal Work If you want to quickly provide a Web presentation for a T27 application without implementing any significant changes to the interface appearance, you do not need to capture the screens of your application. A T27 application can be run from a Web forms application or an MVC Web application by using eportal's dynamic page creation feature. Each screen that is presented to eportal at runtime is rendered as a Web page automatically. In addition, the T27 application can be presented within a master page or layout page. Refer to ModifyingtheMasterPage or ModifyingtheLayoutPage for details. 1. On the File menu, point to New and click Project. 2. In the NewProject dialog box, do the following: a. Select the desired.net Framework version from the dropdown list at the top of the dialog. For guidelines on selecting the.net version, see Multi-TargetingIssues. b. Under Installed, Templates, UnisysePortalProjects, expand ClearPathDataSource, and click MCPData Source. c. In the Templates pane, select MCPT27DataSource. d. In the Name box, type a name for the eportal data source project. The name must be a valid C# name. e. In the Location box, identify the path to the location where you want to save the project. f. If the AddtoSourceControl checkbox is present and the project should be put under source control, ensure that the checkbox is selected. g. Accept all other default settings. h. Click OK. 3. Select Build, then BuildSolution to build the project. 4. Create a new Web presentation as follows: To use a Web Forms application, follow the instructions for Procedure 1 in the topic CreatinganASP.Net WebApplication(TerminalScreenAppearance). To use an MVC Web application, follow the instructions for Procedure 1 in the topic CreatinganMVCWeb Application, and then scaffold the data source using the ScaffoldUnisysControllerforePortalData SourcewithViewsDialog; ensure that you select the PreserveScreenLayoutsandStyles option. 5. The presentation project appears in Solution Explorer. 6. In Solution Explorer, right-click the presentation project, and click SetasStartUpProject. 7. To review the ClearPath eportal application configuration property values, right-click the presentation project, and click ClearPathePortalApplicationConfiguration. The eportalapplicationconfiguration dialog box appears. The <project name> tab contains the properties of the data source project, and the Web tab contains the properties of the presentation project. Refer to eportalapplicationconfigurationpropertyvalues for information about the property values. 8. Make any required changes and click Apply. ClearPath eportal Developer Help 9. If detailed tracing is needed, refer to LoggingErrorsandTracing for information about selecting logging levels. 24 ClearPath eportal Developer Help