May 2018 | Issue 1 www.lansa.com

LANSA V14 SP2 We are very proud to announce LANSA Version 14 SP2. It

contains lots of new features that are detailed it in this

Newsletter.

The next issues will be discussed in this Newsletter:

• LANSA Developer Center Website.

• New in LANSA for Web.

• New in Visual LANSA Framework.

• Visual LANSA IDE Enhancements.

• CSP (Content Security Policy) for Web Applications.

• New Loading of Windows Tables.

• Enhanced Version Control with Git Integration.

• LANSA DevOps and Deployment.

• RESTful Web Services.

• …….. and many more …………

LANSA V14 SP2 ....................................... 1

New Developer Center Website ............. 2

New in LANSA for Web ........................... 3

New in Visual LANSA Framework ......... 14

Visual LANSA IDE Enhancements ......... 16

CSP (Content Security Policy) for Web Applications .......................................... 26

New Loading of Windows Tables ......... 28

Enhanced Version Control with Git Integration ............................................ 32

LANSA DevOps and Deployment .......... 35

RESTful Web Services ........................... 40

Nomenclature Changes ........................ 44

External Program Integration on IBM i Servers .................................................. 45

Wrapped Integrator Services for Easier RDMLX Use ........................................... 47

New LANSA Evaluation Installation ...... 49

RDMLX Extended Library ...................... 51

Installation of V14 SP2 ......................... 52

IBM i Software Will Be Issued as a Save-File ........................................................ 54

INSIDE THIS ISSUE

Page 2

New Developer Center Website

You can now access all developer resources on the new LANSA Developer Center website.

On the website you can find:

• The LANSA developer community

• All shipped sample applications and demos

• Videos

• Tutorials

• Blogs

• The LANSA forum

• Documentation

• Support

The New LANSA Evaluation Installation can also be downloaded from the website.

Page 3

New in LANSA for Web

1. Your First Mobile Application

2. Use Web and Mobile Templates and Sample Applications

3. Responsive Web Applications for Mobile, Tablet and Desktops

4. Google Material Design Controls and Themes

Page 4

1. Your First Mobile Application

When you first start Visual LANSA, the Welcome Screen shows a wizard you can use to quickly build

and execute a mobile web application.

Page 5

2. Use Web and Mobile Templates and Sample Applications

The easiest way to start creating mobile applications is to use a template or a sample application.

You can find the latest sample applications in the LANSA Developer Center.

In the IDE, choose the Build a Mobile Web Application on the Home page of the Visual LANSA IDE to

use templates or sample applications:

Page 6

Mobile Application Templates

You can choose from templates with different layouts:

Page 7

Sample Applications

You can start creating your application by choosing a sample application which most closely

resembles the one you want to create.

Samples are available in the IDE and in the LANSA Developer Center.

Page 8

3. Responsive Web Applications for Mobile, Tablet and Desktop

Mobile-device-friendly, responsive applications optimize the user experience by automatically

adapting to the screen of the device on which they are used.

Page 9

Views and Dialogs are new component types used for creating applications for mobile devices.

In addition to adapting to different screen sizes (by resizing, hiding, shrinking, enlarging, or moving

content to make it look good on any screen) they make it easy to structure the functionality in your

mobile application.

Views are used to present application functionality in quickly navigable groups. The user switches

between views using the buttons in the application drawer.

Page 10

Application dialogs are modal windows typically used as editors or detailers.

Views and dialogs are used together with view containers and application title bars.

Page 11

4. Google Material Design Controls and Themes Google material design components provide a consistent user interface for apps and websites across

Android, iOS, and the web. If you want to know more about them, see https://material.io/components/.

Explore the Material Design Controls in LANSA

Use the Explore the Material Design Controls link in the Home page of the Visual LANSA IDE to see

samples of material design components:

Page 12

The material design sample web page is named xMdMain. To see the shipped source code behind

the page, choose it in the IDE:

Page 13

Material Design in the IDE

You can find Google material design components in the Controls tab in the Visual LANSA IDE:

Material design themes are available in the Theme tab in the Visual LANSA IDE ribbon:

Page 14

New in Visual LANSA Framework

VLF-ONE Deployment Template A new deployment template for VLF-ONE is available in the Deployment Tool.

Build a Mobile App in Under 10 Minutes See a web and mobile app being built with the Framework in under 10 minutes:

https://youtu.be/hh9fGPZ-ECs

If you want to watch the video in full screen, click on the YouTube link.

Page 15

Launch the Framework from the IDE Home Page The Framework Developer Workbench and demonstration application can now be launched from the

Home page of the Visual LANSA IDE:

Page 16

Visual LANSA IDE Enhancements

LANSA Desktop Icons

When you install a LANSA Version 14 SP2 system, two icons are created on the desktop.

The new Visual LANSA icon starts the development environment:

The LANSA system icon displays the folder for your Visual LANSA system:

Page 17

New IDE Home Page

The redesigned IDE home page provides access to the things you commonly need when creating

web applications.

The home page also contains links to desktop application wizards and samples.

Page 18

Diagrams and Links to Guides in Source Code

Selected examples and generated RDMLX source code now include explanatory diagrams in the

source code, and hyperlinks to relevant sections in LANSA guides.

The diagrams are intended to make it easier to understand how things work together. They are

displayed by the new annotations feature which allows images and URLs to be imbedded into source

code.

You can turn annotations on or off with this option:

This is a shipped example reusable part with annotations turned on:

Page 19

Examples are found in the DF_T52, DF_T523 and DF_T53 name range (Visual LANSA Framework

components).

The source code can also contain links to relevant sections in the guides, as in here in component

DF_OEXEC:

Which displays the page describing optional things that can be done with the component:

Page 20

Quick Rules for Tables A new set of predefined Quick Rules are available to minimize the effort in adding common rules to table columns.

The rules available are based on the type of data. You can see quick rules available for string columns above. These are the quick number rules:

Quick date rules are:

Page 21

New Intrinsic Methods

Regular Expressions for Numeric and Character Masking The new string intrinsic method IsMatch, with parameters pattern and result, can be used to deal

with regular expressions for email address formatting.

For example, to Validate an IP Address: #STD_TEXT.IsMatch Pattern("^(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$") Result(#Label1)

#STD_TEXT = 12.13.14.15 will return TRUE

#STD_TEXT = a.b.c.d will return FALSE.

What are Regular Expressions?

The phrase regular expressions, and consequently, regexes, is often used to mean the specific,

standard textual syntax for representing patterns for matching text. A regex pattern matches a

target string.

Can use https://regexr.com/ website or any other similar website to build, test, validate and copy

common regular expressions.

Email and Password Validation Intrinsics New string intrinsic methods .IsValidEmail and .IsValidPassword(Medium/Strong) can be used to

validate a field or a string used as an email address or a password.

.IsValidEmail Rules

• The address cannot be more than 254 characters long.

• The address must not contain more than one “@”, double dots (”..”) or begin with a "@" or

"."

• The address cannot have any spaces or end with a "."

• There must be at least 1 character between "@" and “.” as domain

• There must be at least one dot in an email address after @

• The part preceding @ cannot be more than 64 characters long, contain any of “( ) , : ; < > [

\”] ” characters or end with a “.”

.IsValidPassword( password Strength: Medium/ Strong ) Rules

This method has two parameters Medium and Strong which are mandatory and must be set.

Medium password rules:

• Password length must be at least 6 characters long.

• Password should contain at least one lowercase and one uppercase alphabetical character, or

at least one lowercase and one numeric character, or at least one uppercase and one numeric

character.

Strong password rules:

• Password length must be at least 8 characters long.

• Password must contain one uppercase, one lowercase, one numeric and one special

character.

• Special characters are “ @$!%*?& ”

Page 22

URLEncode and URLDecode Intrinsics URLEncode converts special characters to escape characters representing the UTF-8 encoding. All

characters are converted except for A-Z a-z 0-9 ; , / ? : @ & = + $ - _ . ! ~ * ‘ ( ) #

URLDecode converts UTF-8 escaped characters back to their native equivalent.

View Table Data You can now see the data in a table using the Data Preview tab in table definitions.

To view the local data, click the Refresh button.

Page 23

Non-IBM i Developer View When a partition does not support IBM DB2 for iSeries databases, the attributes of a table are simplified:

The support for IBM DB2 for iSeries is specified in the partition settings:

Page 24

New Source Code Formatting Options

Adjust Identifier Case This option, selected by default, formats any identifier (variable,

method, property or event name) according to its definition.

If you define a method:

MthRoutine Name(MyMethod)

And you use it like this:

#COM_OWNER.mymethod

The formatter will replace it with:

#COM_OWNER.MyMethod

Auto Convert Unquoted

Literals

This option, selected by default, highlights the fact that RDML treats

identifiers without quotes as upper-case strings. Therefore:

#STD_TEXT := hello

Is equivalent to:

#STD_TEXT := “HELLO”

Many users do not know this, and enter, for example:

#COM_OWNER.Caption := STD_TEXT

Without realizing that STD_TEXT without the hash sign to indicate it

is a field (#STD_TEXT) will be treated as a quoted string.

To help avoid this error, the editor will now change the string to:

#COM_OWNER.Caption := “STD_TEXT”

As soon as you leave the line.

Page 25

Other Changes

Design Theme Tab Removed The Design Theme tab has been removed from LANSA Settings. All changes to themes are made in the Theme ribbon.

Groups and Frameworks Removed Groups and Frameworks are no longer specified when creating objects in the Visual LANSA IDE. Prior to SP2:

In SP2:

Page 26

CSP (Content Security Policy) for Web Applications

To help you secure your web pages, Visual LANSA supports the Content Security Policy (CSP)

standard.

CSP prevents cross-site scripting (XSS), clickjacking and other code injection attacks resulting from

execution of malicious content in the trusted web page context using a whitelist of sources of trusted

content in web page HTTP headers.

The Content Security Policy external resources are created in the Partition CSP folder. LANSA ships

three sample Content Security Policy samples (xStrict, xMedium and xLow) with descending level of

restrictions. Use these samples as a starting point for creating your own Content Security Policy

files.

CSP resources can be associated with either Visual LANSA Web pages or WAMs.

Page 27

Editing CSP Files You can edit the contents of your CSP text files. A CSP external resource is a text file with lines for

each directive (name-values). The text file must be encoded in UTF-8.

If your style-src and script-src keywords do not include the 'unsafe-inline' value, you must add

a nonce attribute (represented by the replacement variable %{nonce_hdr}%

To edit a CSP text file, open the settings of your Web Page:

And select your Content Security Policy:

For example, this CSP only allows my app domain, Google Analytics and APIs:

After you have applied the CSP, you need to save and recompile your web page. When you run your

web page, the contents of your CSP external resource file are sent as HTTP headers.

Page 28

New Loading of Windows Tables

Import Table Definitions is used to populate the LANSA repository with the details of tables created

and maintained outside of LANSA in products such as SQL Server or MySQL.

Nearly all native data types are now supported. During the import the native data types are

converted to LANSA field types.

The import makes the tables accessible to LANSA applications, and it also creates fields,

representing the table columns, which can be used as visual controls and variables in code.

Page 29

Data Sources Loading tables begins with the Data Sources page that shows the known database sources as seen in the Windows ODBC Administrator.

Select a Data Source and click the Next button. If no suitable data source exists, you can create one by selecting New Data Source.

Creating a Data Source On the New Data Source page, you can create a data source and use it immediately. Alternatively, you can use the Windows ODBC Administrator to create the DSN and then relaunch the wizard.

Select the appropriate Driver for your database from the dropdown, and then choose the Server. You can then choose whether to use Trusted Connections, or you can supply the User ID and Password. Test the connection. If successful, click Next.

Page 30

Data Source Tables The Data Source Tables page lists all the database tables grouped by schema. Expanding an individual table item will show any views defined for the table. Note that loading a table makes every view known to LANSA.

Selecting a schema item selects all child items. If a table is already known to LANSA, it is flagged as an Update. Note that it is not necessary to load all tables at the same time.

Table Options As part of the load, there are three options that can be applied to tables:

Page 31

Allow Read Access

Only

The table will not allow data to be updated or deleted

Commitment

Control

The table will be configured to support transaction boundaries with commit

and rollback operations.

Submit Compiles Generate the tables’ Object Access Modules (OAMs) as part for the load.

The transformation process converts the table and column definitions to memory-resident LANSA

tables and fields. These can be reviewed on the subsequent Preview page

Click Next to run the transformation.

Preview The Preview page is shown after the definitions of the source tables have been transformed into memory-resident LANSA tables and fields. Use it to review the results before committing them to the LANSA repository.

Finishing the Import When the Finish button is clicked, the fields and tables are created.

This may take a few minutes, depending on the volume of tables and columns being loaded.

Page 32

Enhanced Version Control with Git Integration

Version control system integration between Visual LANSA IDE and Git is now available.

Version Control Settings Version control settings are specified in LANSA Settings in the Visual LANSA IDE.

You can specify that when objects are created and deleted in the Repository, these actions are

synchronized with version control.

Page 33

Version Control Status and History Version control status and history can be viewed in the Visual LANSA IDE.

Folder Management in Version Control In Version Control you can create, rename and move folders, and move repository objects between

folders.

Page 34

Version Control Objects and Actions Visual LANSA provides access to a set of Git actions on objects: Commit, Show History, Show in

Folder View and Show Repository.

Changes can be pulled and pushed in the Version Control View.

Page 35

LANSA DevOps and Deployment

DevOps is a combination of software development and operations which emphasizes communication,

collaboration, and cohesion between developer and IT operations teams. By integrating these two

interdependent functions, DevOps helps an organization deploy software more frequently, while

maintaining service stability and gaining the speed necessary for more innovation.

Visual LANSA supports deploying your applications into the cloud without any manual configuration.

Currently cloud environments are provided for evaluating the feature. Assistance is provided to

deploy your application into test and production environments in your own cloud account. In the

near future there will also be an option to deploy your applications into a cloud environment which is

procured and managed by LANSA on your behalf.

Page 36

Deploy Your Application In order to deploy your application to the cloud, you need to create a repository list of the objects to

be deployed. Only those objects in the list will be deployed no matter what other changes have been

made to your application.

The cloud environment must be set up before deployment. If you have installed a Visual LANSA

Evaluation system or if you have paid for Premium tier features, the environment is automatically

set up for you. It is also possible to set up a cloud environment yourself. For details of how to do

this, refer to the Deploying LANSA Applications on Windows using the Deployment Tool guide.

To deploy an application:

1. Create a repository list for your application. Note that the list needs to be a Favorite.

2. Add all your objects to the list. Make sure you include all the tables and server modules

which your application uses.

3. Then select your list in the Favourites tab and choose Deploy from the dropdown on the top

left:

Page 37

4. The Deploy menu option deploys the current repository list. It creates a package

called version 1.0.65535 which you can see in the Deployment Tool for the application named

the same as the IDENTIFIER of your list, for example OL13 for the list created in Step 1

above. Note that the Deploy menu option does not construct an MSI, it only assembles all the

objects from the repository list.

When the deployment has completed, use the application URL to check the changes you have

deployed.

Note that you can deploy multiple lists into the cloud environment. Each application will continue to

work provided that the lists are mutually exclusive. However, when the cloud scales out, it only

installs the last list deployed so you should limit your deployment and testing to a single deployed

list.

Deployment Tool Changes The deployment tool now uses the WiX 3.10 toolkit to generate the MSI and MSP installs.

The Patching Mechanism Has Been Changed

All files are now individually patched, except the JavaScript runtime which is only ever patched as a

complete set of files.

The LANSA runtime may be included in a patch.

Fewer warnings are produced to ensure significant warnings are not hidden amongst the clutter.

These warnings are no longer produced:

• Files are no longer deleted from the patch base files so there are no warnings that a file has

been deleted when constructing the patch.

• Identifier names are truncated to the maximum allowed by WiX. Thus there are no warnings

about a name being too long when building the Web Images.

Page 38

Only objects which have a DLL with a later File Version will be changed. No other executable objects

will even be considered for patching.

Patches are no longer cumulative, which means that significant patches can be distributed and then

later patches be based on that patch which may only include a single DLL.

A patch is dependent on a Version or another Patch. The target system must have the parent patch

or a later patch installed.

To speed up the patch installation, the repository definitions are only imported if the Install Import

option is selected when creating the Patch.

MSIs

A Version Install Package now has a parent Version. This enforces MSIs being installed in the correct

order, which may be important for database upgrade scripts to be run correctly.

An MSI may optionally include the LANSA runtime, and it may be installed into an existing LANSA

installation. This may be an installation by another MSI which includes the LANSA runtime or a

development environment.

A set of MSIs may be packaged together into a single executable and provide optional installs. See

Feature Set Deployment for more information.

New Table Data Processing Options You may request the Package Install to use ALTER TABLE to change the table, which does not

require data to be loaded and unloaded. If the type of change is not supported, it will automatically

fall back to the existing mechanism which is now called Universal Data Processing.

You may completely replace the table upgrade process with your own SQL. You could, for example,

use “SELECT INTO” style logic to more quickly update very large tables that cannot be updated

using ALTER TABLE.

Page 39

Set as Home Page When selecting repository objects, you can nominate a web page as the default page to be directed

to when a web browser is started or the home button is pressed. You do this by selecting the

option Set as home page for the web page. When this option is selected, an index.html page is

generated which redirects to the selected application web page.

Installation Over-The-Shoulder installs are supported, provided access to IIS is not required. Microsoft requires

administration rights to be able to read configuration information in IIS.

An administrator may choose to install into a shared or user-specific location. A non-administrator is

automatically only given the option to install into a user-specific location.

An MSI may be executed directly from Windows Explorer, unless access to IIS is required.

Other Just In Time deployment supports Feature Sets.

Page 40

RESTful Web Services

Representational state transfer (REST) or RESTful web services are a way of providing

interoperability between computer systems on the Internet. REST-compliant Web services allow

requesting systems to access and manipulate textual representations of Web resources using a

uniform and predefined set of stateless operations.

Consume RESTful Web Services Consuming web services allows you to extend your applications and business processes with capabilities that are provided by various third parties. For example, if your application needs to convert an address to geographic coordinates (latitude and longitude), you would most likely use the Google Maps Geocoding API to do that. Being able to consume web services can add enormous value to your applications by providing very useful extra functionality to your customers which you could not otherwise offer.

Page 41

What is a RESTful Web Service?

Most modern web services are RESTful web services.

REST (stands for Representational State Transfer) is an architectural style for building web services.

The transport for REST is always done over HTTP (unlike SOAP). HTTP verbs (GET, POST, etc.) are

used to indicate the kind of operation being requested. The input and output of REST request is

typically JSON texts.

REST web services are generally simple and easy to construct. It is often said that REST popularity

came from developers having had enough of the complexity (and bloated nature) of SOAP.

Refer to the Consuming Web Services guide for more information.

JSON Parsing

JSON (JavaScript Object Notation) is a simple, text-based data exchange format. JSON is human

readable and contains just the minimum amount of text to describe the data.

RESTful web services are generally JSON-based which is why we need to be able to construct and

parse JSON-formatted data.

There are a couple of classes that you can choose from to work with JSON data. They are:

• XPRIM_JsonObject and XPRIM_JsonArray

• XPRIM_JsonWriter

• XPRIM_RandomAccessJsonReader and XPRIM_JsonReader

Page 42

Publish RESTful Web Services

LANSA developers can now develop RESTful web services using RDML.

Server module API definition consists of:

Definition Publish as Swagger V2

Info Title, Description, Terms of Service

Security

Requirements

HttpBasic, API Key, OAuth2, OpenIDConnect

Paths URLs that map to operations with parameters.

Each operation is mapped to HTTP VERB and to server routine.

Components Schema Types. Each schema type can be mapped to Field, Integer, String,

Array, Object, Boolean or Number.

Security Schemes

REST API definition can be set up within the server module. The API Configuration is automatically

published and updated when the Server Module is compiled.

Page 43

Swagger documentation can be generated for REST API.

Page 44

Nomenclature Changes

To make some LANSA specific terms conform to general usage, these terms have changed:

• Files are now tables

• Logical views are now indexes

• Fields are now columns when used in a table.

Page 45

External Program Integration on IBM i Servers

RDMLX programs can now call external programs and

procedures on IBM i, including RPG programs and procedures

in service programs.

The integration is implemented by two new commands:

Def_Mth_Ex Defines the program, or procedure and service program to call.

Def_Map_Ex Defines the mapping in terms of data type, length, decimals, formatting, separators,

usage as input, update, or both and a return value.

These commands can only be used in RDMLX code based components but not web pages.

There is no inherent limitation within LANSA on the number of parameters to be passed. It is only

limited by either the C compiler or what happens at run time.

All RDMLX data types are supported except for LOBs. In other words, fixed length character, signed,

decimal (packed), binary, date, time, datetime, integer, float, null terminated string, varchar

(integer length followed by the value), boolean & nvarchar (integer length in characters followed by

the value) are supported.

Return values from procedures are supported.

This example defines an external method, in this case a call to a program to test that dates are

mapped to all the IBM i RPG supported date formats and separators:

/* Call program with miscellaneous Date parameters (Run OK) */ Def_Mth_Ex Name(CallPgmMiscDate) Module(P157373J) Def_Map_Ex Name(DateISO) For(*INPUT) Type(*DATE) Format(*ISO) Def_Map_Ex Name(DateJIS) For(*INPUT) Type(*DATE) Format(*JIS) Def_Map_Ex Name(DateEUR) For(*INPUT) Type(*DATE) Format(*EUR) Def_Map_Ex Name(DateUSA) For(*INPUT) Type(*DATE) Format(*USA) Def_Map_Ex Name(DateDMYc) For(*INPUT) Type(*DATE) Format(*DMY) Date_Separator(*COMMA) Def_Map_Ex Name(DateMDYd) For(*INPUT) Type(*DATE) Format(*MDY) Date_Separator(*DOT) Def_Map_Ex Name(DateYMDh) For(*INPUT) Type(*DATE) Format(*YMD) Date_Separator(*HYPHEN) Def_Map_Ex Name(DateJULs) For(*INPUT) Type(*DATE) Format(*JUL) Date_Separator(*SLASH) Def_Map_Ex Name(DateDMYb) For(*INPUT) Type(*DATE) Format(*DMY) Date_Separator(*BLANK)

Page 46

This method routine executes the call:

/* Call program with miscellaneous Date parameters (Run OK) */ Mthroutine Name(MthCallPgmMiscDate) Define Field(#DatISO) Type(*DATE) Default(*YYYYMMDD) Define Field(#DatJIS) Type(*DATE) Default(*YYYYMMDD) Define Field(#DatEUR) Type(*DATE) Default(*YYYYMMDD) Define Field(#DatUSA) Type(*DATE) Default(*YYYYMMDD) Define Field(#DatDMYc) Type(*DATE) Default(*YYYYMMDD) Define Field(#DatMDYd) Type(*DATE) Default(*YYYYMMDD) Define Field(#DatYMDh) Type(*DATE) Default(*YYYYMMDD) Define Field(#DatJULs) Type(*DATE) Default(*YYYYMMDD) Define Field(#DatDMYb) Type(*DATE) Default(*YYYYMMDD) #COM_OWNER.CallPgmMiscDate( #DatISO #DatJIS #DatEUR #DatUSA #DatDMYc #DatMDYd #DatYMDh #DatJULs #DatDMYb ) Endroutine

Page 47

Wrapped Integrator Services for Easier RDMLX Use

For some JSM Services, commands can now be invoked by a simple method call. In addition, more

common workflows are provided to invoke a single routine to perform a complete JSM Service

transaction.

These new objects are shipped in Samples and Examples.

Commands

Page 48

JSM Service Command reusable parts provide a method routine for each command in the

Service. You can use them to construct your own workflow by invoking a succession of Method

Routines associated with a service.

For example, using the ZipService you could invoke the methods JSMOpenandLoad, ZipOpen,

ZipAddFile and JSMCloseandUnload to open a zip file and a file to it.

Workflows

JSM Service Workflow reusable parts provide commonly used workflows, like the above example, as

a single call to a method routine. Each workflow is a sequence of calls to JSM Service Command

routines.

In some cases, the user will need to copy the sample material and modify to their own

requirements. For example, in the case of ExcelService the specific format of the Excel data

(number of columns, type of data etc.…) will need to be customised in the RDMLX code.

Page 49

New LANSA Evaluation Installation

The LANSA V14 SP2 Evaluation install is downloadable from developer.lansa.com after registering on

the LANSA web site:

The V14 SP2 Evaluation includes Freemium Cloud support.

The V14 SP2 Evaluation is a cut down version of the normal Installation. It installs an Independent

Visual LANSA system with Version Control and the common default features (Visual LANSA, Web

Administration, LANSA Web Server Extension, Web Images, Integrator JSM, Integrator Studio,

LANSA Open and LANSA Connect).

Page 50

There are two main differences to the normal installation:

One Dialog

There is only one dialog presented. This dialog is equivalent to the main installation’s “Options and

Summary” dialog but it only has three options that need to be reviewed:

• An option to ask for the root directory

• A database dialog which is a combination of the Main Install’s DSN and Database options

• The User Id for VL Web Configuration option which is identical to the option in the main

installation.

License

The first thing the evaluation installation does is request an evaluation license. If it cannot obtain an

evaluation license, the installation will not continue.

Page 51

RDMLX Extended Library

LANSA Version 14 SP2 includes an RDMLX Extended Library with many useful features.

For example, the Cryptographic hashing functions support these algorithms:

• MD5

• SHA-256

• PBKDF2

• SCrypt

• HMAC-SHA-256

See LANSA RDMLX Extended Library in the Technical Reference Guide.

Page 52

Installation of V14 SP2

The new Installation of V14 SP2:

• Ships SQL Server 2017 Express for Development Usage

• SQL Server only Supports 64-bit OS

• Can use earlier SQL Server version if needed

Default installation type is Independent VCS. Git and Git Extensions are installed if you do not have

them.

Page 53

IBM i 5250 Development Support will be Turned off by default. It can be enabled in the editor

Settings:

Page 54

IBM i Software Will Be Issued as a Save-File The IBM i software will no longer be installable directly from the DVD.

The IBM I software is now provided as a zipped save file, not as an ISO image. You need to copy the

LANSA for i save file provided on the V14 SP2 DVD and use LODRUN with the save file to install

LANSA for i.