Track #1 - Plex r7.2.1 Features - CM First Groupcmfirstgroup.com/wp-content/uploads/2017/10/Plex2e2017_Day01_Plex_r7_2... · These Materials are confidential and proprietary information

9th CA 2E/CA Plex Worldwide Developer Conference

Features

1


Legal Statement

These educational materials (hereinafter referred to as the “Materials”) are for the end user’s educational purposes only and are subject to change or withdrawal by CA, Inc. (“CA”) at any time.

These Materials may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. These Materials are confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THESE MATERIALS “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THESE MATERIALS, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The use of any software or product referenced in the Materials is governed by the end user’s applicable license agreement.

The manufacturer of these Materials is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

© 2017 CA. All rights reserved. CA confidential & proprietary information. For internal use only. No unauthorized use, copying or distribution. All names of individuals or of companies referenced herein are fictitious names used for instructional purposes only. Any similarity to any real persons or businesses are purely coincidental.

2


Speakers

3

Painuly, ArunPrincipal Software Engineer, CA Technologies

Gayosso, LucioSr Consultant/Nearshore Team Lead/ Support Manager, CM First Group


Agenda

4

o CA Plex r7.2.1

• Overview • Upgrade considerations• Upgrade Possibilities

o CA Plex r7.2.1 features

o Certifications & PTFs

o Upgrade – problems addressed

o Q/A


CA Plex r7.2.1

5


Overview

6

This release has targeted to address long pendingcompiler upgrade (IDE, runtimes) along with latestthird party certifications.

The decision was primarily based on Plex usercommunity’s input. This ensures the long termbenefit of protecting investment and extends theproduct stability.


Upgrade considerations

7

o WinC/WinNTC variant requires• Visual Studio Professional 2013 (Update 5)• Visual C++ MFC MBCS Library for Visual Studio 2013

o Regeneration/rebuild required for WinC/WinNTC function

o .NET variant• .NET Framework 4.6

o Java Variant• Java 1.8



8

o Create an Upgrade Plan.

o Review Release Notes.

o Main stages:1. Back up Group and Local Models. Follow best practices.2. Ensure the latest work from all Local Model has been updated3. Update the Group Model to the latest PLEX 7.2.14. Update the Local Models to the Latest PLEX 7.2.15. Regen WinC (C++) clients. Details on what is needed for this can be found at https://docops.ca.com/ca-

plex/7-2-1/en/release-information/new-and-updated-features6. When upgrading to CA Plex r7.2.1, it's not mandatory to regenerate or rebuild existing Java,

C# or RPG functions. The advantages of regenerating C# to take advantage of .Net Framework 4.6 can be found at –https://docops.ca.com/ca-plex/7-2-1/en/release-information/new-and-updated-features

Some additional details on what is included with .NET 4.6 –https://msdn.microsoft.com/en-us/library/ms171868(v=vs.110).aspx#v46

7. For C#, to use .Net Framework 4.6 across Plex built application and Plex runtime - require regen/rebuild but at this point there is no need for this.



9

o Packaging

• Stable packaging of your functions is critical.• Once objects are packaged and generated, do not change

their packaging.• No automated cleanup in case of packaging changes.

o PLEX Packaging Tool

• Allows automated package regeneration.• The default packaging groups (UI, SERVER, and MISC) have been

proven to work for most organizations.



10

o PLEX Packaging Tool (cont.)

• Package after having created the objects.• Do not change Package Names.



11

o Source Code Objects

• Need to add for .Net variant.

• Establish proper naming conventions for the different variants.


Upgrade Possibilities

12

o WinC to .NET

• Real examples



13

o WinC to .NET (cont.)

• Real examples



14

o WinC to .NET (cont.)

• Real examples



15

o Enhanced Layout via XAML

• Additional layout control.• External to PLEX.• Requires practice.• Example, change alternating row color.


Runtime Considerations

16

o Upgrade Runtime DLLs

• Determine CA PLEX runtimes for your app.§ I.e. OBPTCSHARP.dll contains the Date library functions

• DLLs are prebuilt and shipped with PLEX and found under version-dependent folders (i.e. C:\Users\Public\Documents\CA\Plex\7.1\class710\PatternLibs\OBPTCSHARP.dll)

• Determine what other runtimes to support your app are required for your deployment

• Assemblies can be relocated using your app’s EXE.CONFIG file.


CA Plex r7.2.1 features

17

Plex IDE and runtimes (WinC, WinNTC) upgraded to Visual Studio 2013.

Prerequisites:o Visual Studio Professional 2013 (Update 5)o Visual C++ MFC MBCS Library for Visual Studio 2013

Note: We have done sanity testing with Plex & Visual Studio 2013 Community edition and all looks good. But we don’t have Plex officially certified with Visual Studio 2013 community edition yet.

CA Plex product upgrade with Visual Studio 2013


CA Plex r7.2.1 features…

18

# Runtime binary version string change

Version string changes from 600 to 721.e.g. Ob600lc.dll is now Ob721lc.dll

# Registry changes (WinNTC)HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CA\Plex\7.2

Key changes within Plex IDE, WinC & WinNTC runtime



19

Support enabled for EJB 3.2 specifications.

o Gen/Build window option modified to EJB version 3.2“EJB Connector Options” -> “EJB Version”

o Reference implementation changed from j2sdkee1.3 to glassfish

o EAR file creation is being done with ANT script instead of Java old packager tool which is part of part of J2ee 1.3.

Plex generated EAR file should be compatible with any APP Server which compliance with EJB 3.2 implementation.

EJB 3.2 support



20

The Control IDs allocated for GUI panel elements that are generated onto a panel will be stored in the panel design for each panel. This way external testing tools can rely on the fact that the control IDs allocated against Java resource files always remain the same for each control. This feature makes creating test scripts against Java applications much more robust against changes to label text or panel element reordering.

This feature is available for Java variant with this release.

Java Control ID support

ToenablefixedcontrolIDs,updateBLDfile.

[Options]AllocateFixedControlIDs=0|1



21

CA Plex .NET variant is using .NET framework 4.6 compared to 4.0 earlier.

Note: Windows 10 comes with .Net Framework 4.6.1 as a default install. This will prevent .Net Framework 4.6 installation as higher versionis already installed. In this environment, we may get compilation warnings related to the processor architecture as Plex .Net runtime is basedon .Net 4.6 and the machine has 4.6.1. This warning can be ignored.

Plex .NET variant upgraded to .NET Framework 4.6


Certifications & PTFs

22

o Windows 10

o SQL Server 2014

o Post GA certifications:• Oracle 12c R2• IBM-I 7.3

o PTFs• Plex r7.2.1 PTF build 001 (25+ fixes) has been published – support.ca.com.

Problems addressed…

23

Identified problems with ActiveX integration, especially with Codejock

o Problem has been resolved with few code changes in ActionDiagram to invoke component methods differently.

o Few changes in Plex WinC runtime to avoid ActiveX problem.

COM Connectors problemo The problem has been addressed.

Changes will be rolled out in next PTF build.



24

Post build event & Trigraph

o Problem has been addressed as part of PTF build 001.

Group model extract/update – long duration o This improvement has been addressed as part of Plex r7.2.1

PTF build 001. Performance has improved by 35%.



25

Plex version/level - block modification level

o Changes has been made to not mark AD block as modified to current level, if there is one of the parameter mapped with default mapping.

Function meta variable - inconsistence replacemento Problem has been addressed and fix will be rolled out in next

PTF build.


Note: Aforementioned solutions arereadyandwillberolledoutinupcomingPTFbuild.


Contact

26

Email: [email protected]: www.cmfirstgroup.com

Email: [email protected]: www.ca.com


Q / A

27