micro focus enterprise server on azure...micro focus enterprise server on azure january 2020 page 5...

Micro Focus Enterprise Server on Azure

An Azure Quickstart Template

January 2020

Contents Micro Focus Enterprise Server on Azure ....................................................................................................... 3

Costs and licenses ......................................................................................................................................... 3

Architecture of Enterprise Server on Azure .................................................................................................. 4

Quickstart ...................................................................................................................................................... 7

Prerequisites ............................................................................................................................................. 7

Review the Micro Focus End User License Agreement ............................................................................. 7

Deploy Enterprise Server from the solution template.............................................................................. 7

Tutorials ...................................................................................................................................................... 12

Prerequisites ........................................................................................................................................... 12

Introduction to the BankDemo demonstration application ................................................................... 13

Running the BankDemo demonstration application .............................................................................. 13

Connecting to the BankDemo enterprise server ................................................................................ 13

Running BankDemo in online mode ................................................................................................... 14

Running BankDemo in batch mode .................................................................................................... 19

Closing the BankDemo data files .................................................................................................... 19

Submitting the BankDemo JCL job .................................................................................................. 20

Viewing the output ......................................................................................................................... 21

Reopening the BankDemo data files ............................................................................................... 21

Investigating scale-out features in the BankDemo demonstration application ..................................... 21

Introduction to Enterprise Server scale-out features ......................................................................... 22

Micro Focus Enterprise Server on Azure January 2020

of 37

Multiple Enterprise Server virtual machines acting as a single logical entity..................................... 22

Updating modules in a live application ............................................................................................... 23

Housekeeping after running BankDemo ................................................................................................. 26

Stopping the BankDemo enterprise server ........................................................................................ 26

Starting the BankDemo enterprise server manually .......................................................................... 27

Commonly performed tasks for use in the tutorials ............................................................................... 29

Connecting to a Remote Desktop Gateway virtual machine .............................................................. 29

Connecting to an Enterprise Server virtual machine on Linux ........................................................... 30

Connecting to an Enterprise Server virtual machine on Windows ..................................................... 32

Additional resources ................................................................................................................................... 33

Azure ....................................................................................................................................................... 33

Best practices using Enterprise Server on Azure .................................................................................... 33

Micro Focus documentation ................................................................................................................... 33

Security ................................................................................................................................................... 35

Troubleshooting .......................................................................................................................................... 35

Notices ........................................................................................................................................................ 37


of 37

This quickstart deployment guide provides step-by-step instructions for you to quickly and confidently

deploy Micro Focus Enterprise Server 5.0 on Microsoft Azure.

This quickstart is for you if you are:

A system integrator (SI) who is used to installing and configuring Enterprise Server deployments on

premises, and want a template to use as a starting point for installing and configuring Enterprise

Server deployments on Azure.

An existing Micro Focus customer who has already deployed an IBM mainframe workload to

Enterprise Server on premises and want to see how easy it is to migrate these rehosted applications

to Azure.

Interested in exploring the feasibility of moving an IBM mainframe workload to Azure and want to

experience a fully functioning production server for running mainframe applications that can be

deployed with a single click.

The quickstart creates the required infrastructure for both Azure and Enterprise Server. This makes it easy

for you to see a fully-functioning demonstration application called BankDemo—using COBOL, CICS, Job

Control Language (JCL), and Virtual Storage Access Method (VSAM) files—running under Enterprise Server

on Azure.

Micro Focus Enterprise Server on Azure Micro Focus Enterprise Server is an application deployment environment for IBM mainframe applications

that have been running on the IBM z/OS operating system. Enterprise Server enables you to modernize and

integrate mainframe applications with technologies such as .NET and Java. It also gives you application

flexibility across Linux and Microsoft Windows, containerized or virtual, on Azure.

Using Enterprise Server, your organization can:

Support mainframe application deployment to Linux or Windows on Azure.

Rapidly replicate business-critical functionality to new platforms to support geographic, regulatory, line-

of-business, or other key requirements.

Reduce your ongoing IT application costs by as much as 90%.

Meet and exceed your application reliability, availability, and serviceability requirements.

Integrate with your security infrastructure, for appropriate application and system security.

Costs and licenses You are responsible for the cost of the Azure services used while running this quickstart reference

deployment. There is no additional cost for using the quickstart.


of 37

The Azure template for this quickstart includes configuration parameters that you can customize. Some of

these parameters, such as the specification of the virtual machines, will affect the cost of deployment. For

cost estimates, see the pricing pages for each resource you will be using. Prices are subject to change. See

the Azure Pricing Calculator.

This quickstart uses a Bring Your Own License (BYOL) model for Enterprise Server. How you license

Enterprise Server for use with this quickstart depends on what sort of license you have:

If you are an existing user of Enterprise Server you should contact your Micro Focus sales representative

to discuss how you can evaluate the quickstart using one of your existing licenses.

If you are not an existing user of Enterprise Server you can request a trial license from Micro Focus.

This trial license for Enterprise Server on Azure is only intended to be used for a maximum of 90 days,

and is not intended for production use. After the trial period, you are responsible for acquiring the

necessary licenses directly from Micro Focus to continue using Enterprise Server on Azure.

Architecture of Enterprise Server on Azure This section gives detailed information on the structure deployed by this quickstart on Azure.

When you deploy this quickstart, you must specify at least one version of the BankDemo demonstration

application, but otherwise, you can use the default parameters to build the following Enterprise Server

environment in Azure.

https://azure.microsoft.com/en-gb/pricing/calculator/

https://www.microfocus.com/products/enterprise-suite/enterprise-server/trial/


of 37

Figure 1: Quickstart architecture for Enterprise Server on Azure

Note: If you customize the supplied template to deploy your own Enterprise Server applications to

Azure, the resulting Azure architecture could be very different to the one described in this section.

The quickstart sets up the following:

A network load balancer to automatically distribute requests for the BankDemo demonstration

applications to the deployed Enterprise Server virtual machines and to handle 3270 traffic exposed via a

public IP address.

A subnet containing administration and management utilities:

A virtual machine to host Enterprise Server Common Web Administration (ESCWA). ESCWA is a

utility for viewing and managing enterprise servers running on different machines.

The default name of this virtual machine is mfes-esadmin.


of 37

Up to four Remote Desktop Gateway (RD Gateway or RDG) virtual machines for administrative

access. These instances also provide SSH access for when the enterprise server instances are

deployed on Linux.

The default names of these virtual machines are mfes-rdg01 through mfes-rdg04.

A subnet containing an availability set that contains primary and backup Active Directory domain

controllers.

The default names of the primary and backup domain controllers are mfes-adp and mfes-adb

respectively.

A subnet containing an availability set that contains up to nine virtual machines running Enterprise

Server.

The default names of these virtual machines are mfes-es01 through mfes-es09.

A subnet that contains an Azure Cache for Redis instance.

This subnet is only deployed if you choose to install the Performance and Availability Cluster (PAC)

version of the BankDemo demonstration application.

A subnet containing data-related resources:

A virtual machine running Fileshare and with a shared network drive that is used when running the

BankDemo demonstration application in batch mode.

This is only deployed if you choose to install the Fileshare version of the BankDemo demonstration

application.

An availability set that contains the following SQL Server resources:

Two SQL Server nodes.

The default names of these nodes are mfes-sqls0 and mfes-sqls1.

A SQL Server witness to monitor the performance of the SQL Server nodes.

The default name of the SQL Server witness is mfes-sqlw.

This availability set is only deployed if you choose to install the SQL Server or PAC version of the

BankDemo demonstration application.

A SQL Server load balancer to automatically distribute the load between the two SQL Server nodes

used by the BankDemo demonstration application.

The default name of the SQL load balancer is mfes-sqlLb.

This subnet is installed if you choose to install any version of the BankDemo demonstration application.


of 37

Quickstart This quickstart shows how to deploy Enterprise Server (including one or more versions of a demonstration application) into Azure. When you have deployed Enterprise Server, we recommend that you read the section Running the BankDemo demonstration application in order to validate that Enterprise Server was successfully deployed and also to familiarize yourself with it.

Prerequisites Before deploying the Enterprise Server template ensure that you have the following:

An Azure subscription.

If you don't already have one you can create one for free.

A valid license for Enterprise Server.

This quickstart uses a Bring Your Own License (BYOL) model for Enterprise Server. If you are an

existing user of Enterprise Server, you should contact your Micro Focus sales representative to

discuss using one of your existing licenses. If you are not an existing user of Enterprise Server, you

need to request a trial license from Micro Focus. For more information, see the section Costs and

licenses.

Review the Micro Focus End User License Agreement

Before launching this quickstart for Enterprise Server, you must review the terms of the Micro Focus End

User License Agreement. You will be asked to accept the terms of the End User License Agreement during

deployment.

Deploy Enterprise Server from the solution template This section describes how to use the Azure portal to deploy Enterprise Server using the supplied template.

The parameters described in this section are not the only parameters that you can specify when deploying

Enterprise Server. Additional parameters are specified in the JSON files that comprise the solution template.

If you have experience working with Azure template files and are familiar with Enterprise Server

deployments, you could edit the JSON files to customize the Enterprise Server deployment. You should be

aware that doing so is at your own risk and could result in behavior that is significantly different from the

behavior of the unmodified solution template.

Note: You are responsible for the cost of the Azure services used while running this quickstart

reference deployment. There is no additional cost for using this quickstart. For full details, see the

pricing pages for each Azure service you will be using in this quickstart. Prices are subject to change.

1. Sign in to the Azure portal at https://portal.azure.com.

2. On the top left-hand side of the screen, click Create a resource.

The New page is displayed.

https://azure.microsoft.com/en-gb/free/


https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/GUID-0562B3C9-2271-4CE8-AF64-93DE4940077F.html


https://portal.azure.com/


of 37

3. Enter Micro Focus Enterprise Server in the Search the marketplace field.

The Marketplace lists all options containing "Micro Focus Enterprise Server".

4. Select Enterprise Server.

5. Click Create.

6. On the Basics tab, specify values for the following parameters (accepting default settings where they are

appropriate) then click Next: Virtual Network Configuration:

Project details:

Subscription The Azure subscription to be billed for any charges

incurred for this deployment.

Resource group The name of the resource group to use for this

deployment. You can select an existing resource group

from the drop-down menu or use the Create new link.

Instance details:

Region The Azure region to use.

Cluster prefix The string to use as the prefix for the names of the

various resources that will be created for this

deployment.

Operating system The operating system to use for the virtual machines

hosting Enterprise Server.

License file A valid license file for Enterprise Server.

See Costs and licenses for more information on Enterprise

Server license files.

7. On the Virtual Network Configuration tab, specify values for the following parameters (accepting

default settings where they are appropriate) then click Next: Virtual Machine Settings:


of 37

Domain settings:

Domain DNS name The fully qualified domain name to use for the

deployment.

Administrator user name The user name to use for the administrator of the domain

and virtual machines created for this deployment.

Administrator user password and

Confirm password

The password for user name Administrator user name.

The password must contain:

at least 12 characters in total

at least one numeric character

at least one uppercase character

at least one lowercase character

8. On the Virtual Machine Settings tab, specify values for the following parameters (accepting default

settings where they are appropriate) then click Next: Demo Settings:


of 37

General machine settings:

SSH public key for VM admin user The SSH public key for Administrator user name

(specified on the previous tab). For information on

creating SSH key pairs see Create and use an SSH public-

private key pair for Linux VMs in Azure.

Remote desktop gateway host count The number of Remote Desktop Gateway hosts to use.

Remote desktop gateway VM size The size of the virtual machines to be used for the

Remote Desktop Gateway hosts.

Active Directory VM size The size of the virtual machine to be used for the primary

and backup domain controllers.

Enterprise Server machines:

Enterprise Server host count The number of Enterprise Server virtual machines to be

deployed. This can be from 1 - 9.

Enterprise Server hosting VM size The size of the virtual machines to be used for running

Enterprise Server.

Data disk size for VMs The amount of data to use for the virtual machines to be

used for running Enterprise Server.

Application user name The user name to use when running applications using

Enterprise Server.

Application user password and

Confirm password

The password for user name Application user name. The

password must contain:

at least 12 characters in total




9. On the Demo Settings tab, specify values for the following parameters (accepting default settings where

they are appropriate) then click Next: Review + create:

https://docs.microsoft.com/en-gb/azure/virtual-machines/linux/mac-create-ssh-keys



of 37

Deploy Fileshare demo Whether the Fileshare version of the BankDemo

demonstration application is to be installed.

Deploy PAC demo Whether the PAC version of the BankDemo


Deploy database demo Whether the SQL Server version of the BankDemo


Fileshare settings:

Fileshare VM size The size of the virtual machine to be used for running

Fileshare.

Data disk size for VM The amount of data to use for the virtual machine to be

used for running Fileshare.

Fileshare port The port that Fileshare will use to listen for requests.

Fileshare administrator password and

Confirm password

The password for the Fileshare administrator. The

password must contain:

between 8 and 32 characters in total




Database settings:

SQL witness VM size The size of the virtual machine to be used for running the

SQL Server AlwaysOn witness.

SQL node VM size The size of the virtual machine to be used for running SQL

Server.

Note: This quickstart is configured to install all three (Fileshare, SQL Server, and PAC) versions of the

BankDemo demonstration application by default. In order to avoid deploying (and possibly paying

for) resources that you do not need, you should ensure that you only install the versions of the

demonstration application that you are interested in.

If you deselect all three of Deploy Fileshare demo, Deploy database demo, and Deploy PAC demo,

the demonstration application is not installed at all, and you will not be able to test the deployment

as described in the section Running the BankDemo demonstration application.


of 37

The information you specified so far is validated. Assuming there were no validation issues, the Review

+ create tab shows a "Validation Passed" message and a summary of the parameters that are to be

used.

10. Click Create to deploy Enterprise Server.

A screen is displayed informing you that the deployment is underway.

How long the deployment takes depends on the parameters you specify, and in particular which of the

BankDemo demonstration applications you install. If you install the Fileshare version of BankDemo or do

not install BankDemo at all, the deployment should take approximately 35 minutes. If you install the SQL

Server or PAC version of BankDemo, the deployment should take approximately 1 hour and 5 minutes.

A message is displayed when the deployment of Enterprise Server is complete.

Tutorials This section contains a number of tutorials, all based around the BankDemo demonstration application. An

overview of BankDemo is provided in the section Introduction to the BankDemo demonstration application.

The first tutorial, covered in the section Running the BankDemo demonstration application, walks you

through BankDemo's basic operation.

Two additional tutorials, described in the section Investigating scale-out features in the BankDemo

demonstration application, take a closer look at Enterprise Server's scale-out features which you can

investigate if you have installed the PAC version of BankDemo.

This section also contains information on housekeeping tasks that you might need to perform after running

the tutorials.

Prerequisites

Before you run the BankDemo demonstration application that is used in these tutorials, you need to ensure

that you have:

Successfully deployed the Enterprise Server on Azure template, including at least one version of the

BankDemo demonstration application. To have installed a version of BankDemo you must have

selected at least one of Deploy Fileshare demo, Deploy database demo, or Deploy PAC demo on

the Demo Settings tab when deploying the Enterprise Server on Azure template.

Installed a TN3270 terminal emulator. You can use any TN3270 terminal emulator, but this guide

shows the use of Micro Focus Rumba, which is supplied with Micro Focus Enterprise Developer.

Note: The instructions in these tutorials assume that when deploying the Enterprise Server on Azure

template you used the default value specified for Cluster prefix on the Basics tab. The default value

for this parameter is mfes, so a number of the resources referenced in the tutorials start with this

prefix (such as mfes-eslb and mfes-rdg01).


of 37

If you specified a value other than mfes for the Cluster prefix parameter, whenever a tutorial refers

to a resource prefixed with mfes- you must instead use the name of the corresponding resource on

your system.

Introduction to the BankDemo demonstration application

BankDemo is a demonstration application for an imaginary banking company and provides simple banking

functionality such as displaying accounts and transactions, transferring funds between accounts, and

changing users' contact details. The source code for BankDemo is supplied with Enterprise Developer, which

is a Micro Focus product that enables you to develop and maintain mainframe COBOL and PL/I applications.

This quickstart for Enterprise Server includes deployable files that have been built using Enterprise

Developer. Running BankDemo after you have launched this quickstart enables you to verify that the

quickstart has deployed as expected and that Enterprise Server is running successfully on Azure.

This quickstart includes three versions of BankDemo that differ in the types of data that they use (and

therefore the types of Azure resources that they require). The three versions of BankDemo use the following

types of data:

VSAM data files that are processed by Fileshare. This version requires a virtual machine running

Fileshare.

A SQL Server database. This version requires SQL Server with Always On across multiple Azure virtual

machines.

A Performance and Availability Cluster (PAC) using Azure Cache for Redis as a Scale-Out Repository

(SOR). The VSAM data files are hosted in SQL Server with Always On across multiple Azure virtual

machines.

Most of the information in the tutorials applies to all versions of BankDemo. Information that does not apply

to all versions is marked accordingly.

All three versions of the BankDemo application can run in online mode. The Fileshare and PAC versions can

additionally run in batch mode.

Running the BankDemo demonstration application

This section contains the steps you need to follow in order to run the first of the tutorials. The tutorial shows

how to run the BankDemo demonstration application in online and batch modes (where appropriate).

Connecting to the BankDemo enterprise server

The BankDemo application runs in an enterprise server that’s started automatically when you launch this

quickstart. This section describes how to connect to this enterprise server. Use your TN3270 terminal

emulator to connect to the mfes-eslb load balancer using the following details:

mfes-eslb-IP-address:port


of 37

where:

mfes-eslb-IP-address is the IP address of the load balancer. To obtain this value:

1. Use the Search box on the Azure portal to locate the mfes-eslb load balancer.

2. On the Load balancers page, select the mfes-eslb load balancer.

The load balancer details blade is displayed. The Public IP address field shows the IP address and

DNS name of the mfes-eslb load balancer.

port is the port number to use and varies depending on which version of BankDemo you are running.

The possible values for port are as follows:

5555 - Fileshare version

5556 - SQL Server version

5557 - PAC version

Once connected to the Fileshare or PAC version of the BankDemo application you will see a screen

similar to the one in Figure 2. When you connect to the SQL Server version of BankDemo, you will see a

blank screen instead.

Figure 2: The Enterprise Server region for the Fileshare or PAC version of BankDemo

Now that you're connected, you're ready to run the BankDemo application in online mode.

Running BankDemo in online mode

You can now perform the following steps to run the BankDemo application in online mode:

1. Press Ctrl+Shift+Z to clear the screen.


of 37

2. Enter the name of the transaction to run:

BANK

The BankDemo sign-on screen is displayed, as shown in Figure 3.

Figure 3: The BankDemo sign-on screen

This screen being displayed is confirmation that the BankDemo application is running under Enterprise

Server on Azure.

The rest of this section describes how you can try out some of BankDemo's features in online mode, to

verify that it is able to read and write data as expected.

If you don't want to try out these BankDemo features in online mode, your next step depends on which

version of BankDemo you're running:

If you are running the Fileshare or PAC version of BankDemo, you can jump to the section Running

BankDemo in batch mode.

If you are running the SQL Server version of BankDemo, you can jump to the section Housekeeping

after running BankDemo.


of 37

The remaining steps in this section enable you to verify that BankDemo can read and write data by

logging in as a user, viewing the user's balance, transferring an amount between two of the user's

accounts, and viewing the user's balance again to confirm that the transfer has happened.

Tip: Each screen of the BankDemo application has its own help page, which you can access by

pressing F1.

3. From the BankDemo sign-on screen, specify a valid user ID, press Tab, and then enter a password. Valid

user IDs are B0001 - B0036. This demonstration uses B0004.

You can use any valid user ID, but if you choose a user other than B0004, the data presented on the

screens that you see will be different from the data shown in the figures from this point on.

The password can be any non-blank character string. Once successfully logged on, you see the

BankDemo main options screen:

Figure 4: The BankDemo main options screen

4. The cursor is positioned on the first option, Display your account balances. Press X, and then press

Enter. The BankDemo account balances screen is displayed, showing the balances of the different

accounts held by this user:


of 37

Figure 5: The BankDemo account balances screen

5. Press F4 to return to the BankDemo main options screen.

6. Now we want to transfer some funds from one account to another. You can see from Figure 5 that this

user's checking account is overdrawn, so we will transfer $80 from the savings account to the checking

account.

Press Tab so that the cursor is positioned next to the Transfer funds between accounts option, press X,

and then press Enter.

The BankDemo balance transfer screen is displayed, showing the user's accounts, their balances, and

options to move an amount from one account to another.


of 37

Figure 6: The BankDemo balance transfer screen

7. The cursor is positioned next to the Enter amount to be transferred prompt. Specify 80.00 and then

press Tab.

8. The cursor is now positioned in the From column of the savings account. This is the account that we

want to transfer money from. Press X, and then press Tab twice.

9. The cursor is now positioned in the To column of the checking account. This is the account that we want

to transfer money into. Press X, and then press Enter.

The account balances are updated, and a message appears toward the bottom of the screen

summarizing the transfer.

10. Press F4 to return to the BankDemo main options screen.

11. Although the balance transfer screen showed us the changed account balances after we had carried out

the transfer, we will now display the account balances screen again. This is to confirm that the data has

been updated and that we can read it.

The cursor is positioned on the first option, Display your account balances. Press X, and then press

Enter.


of 37

The account balances screen is displayed, showing the balances that reflect the changes that were

made.

12. Press F3 to exit BankDemo.

Running BankDemo in batch mode

If you’re running the Fileshare or PAC version of BankDemo, you can now run it in batch mode. The steps

required to do this can be summarized as follows:

1. Close the BankDemo data files.

2. Submit the BankDemo JCL job.

3. View the output.

4. Reopen the BankDemo data files.

Closing the BankDemo data files

Running BankDemo in batch mode requires access to BankDemo's data files but if you have run the Fileshare

version of BankDemo interactively those data files will still be locked by Fileshare.

To close the data files so that you can run BankDemo in batch mode you need to do the following:

1. Still in your TN3270 terminal emulator, press Ctrl+Shift+Z to clear the screen.

2. Enter the following, which is the name of a supplied transaction to close BankDemo's data files:

CFIL

A message is displayed confirming that the data files have been closed.

3. This step applies only if you have deployed more than one Enterprise Server instance.

If you are using the Fileshare version of BankDemo, running the CFIL transaction closes the BankDemo

data files on the current Enterprise Server instance only. When there is more than one Enterprise Server

instance, the BankDemo data files on the other Enterprise Server instances will still be open (and

locked), so you must also close those.

To close the data files on the Enterprise Server instances other than the one on which you just ran the

CFIL transaction, you must connect to each of the other Enterprise Server instances, and on each one

stop the BNKDMFS region that is running.

Note: If you are using the PAC version of BankDemo, running the CFIL transaction on any one

Enterprise Server instance closes the BankDemo data files on all Enterprise Server instances, so you

do not need to perform this step.

See the section Connecting to an Enterprise Server virtual machine on Linux or Connecting to an

Enterprise Server virtual machine on Windows for information on connecting to these virtual machines.


of 37

Submitting the BankDemo JCL job

To submit the JCL job you must connect to the mfes-rdg01 virtual machine, from where you can use

Enterprise Server Common Web Administration (ESCWA) to submit the JCL job.

1. Connect to the mfes-rdg01 Remote Desktop Gateway virtual machine if you are not already connected

to it. See the section Connecting to a Remote Desktop Gateway virtual machine for information on how

to do this.

2. Double-click the ES Common Web Administration shortcut on the mfes-rdg01 desktop. This is the third

Google Chrome shortcut from the top.

Google Chrome opens showing the dashboard for Enterprise Server Common Web Administration

(ESCWA). The dashboard shows two warning messages (which are expected) and a Welcome message.

3. Click NATIVE.

The navigation pane on the left shows the directory servers that are running. These will vary depending

on whether you are running the Fileshare version of BankDemo or the PAC version and whether you

changed from the default of deploying two Enterprise Server virtual machines. If you deployed the

default two Enterprise Server virtual machines:

For the Fileshare version you will see three directory servers listed: mfes-es01 and mfes-es02

correspond to the Enterprise Server virtual machines where BankDemo is running, and mfes-fs

corresponds to the Fileshare virtual machine.

Click mfes-es01 and mfes-es02 in turn and you can see that they each contain a BNKDMFS region

which is running the BankDemo application.

Both mfes-es01 and mfes-es02 also contain a region called ESDEMO. The ESDEMO region is a

demonstration region installed by default by Enterprise Server. It is not used by BankDemo so you

can ignore it.

For the PAC version you will see two directory servers listed: mfes-es01 and mfes-es02.

Click mfes-es01 and mfes-es02 in turn and you can see that they each contain a BNKDM region

which is running the BankDemo application.

The two BNKDM regions have been configured to be part of the same Performance and Availability

Cluster (PAC) and use Azure Cache for Redis as the Scale-Out Repository (SOR). BankDemo's VSAM

data files are hosted in SQL Server with Always On across multiple Azure virtual machines.

The rest of the instructions for working with the PAC version of BankDemo show different

operations being carried out on the BNKDM region running on the mfes-es01 directory server.

However, because mfes-es01 and mfes-es02 are configured as part of the same PAC, you could

substitute mfes-es02 for mfes-es01 if you so chose.

4. In the navigation pane, expand Directory Servers > mfes-es01 and click BNKDMFS if you are running the

Fileshare version of BankDemo. If you are running the PAC version of BankDemo the region name is

BNKDM rather than BNKDMFS.


of 37

The GENERAL PROPERTIES page shows the basic attributes of the region.

5. Click JES > Control.

The JCL CONTROL page is displayed.

6. Using Windows Explorer on the mfes-rdg01 virtual machine, navigate to the folder c:\BankDemo_FS\jcl

or c:\BankDemo_PAC\jcl depending on which version of the demonstration application you are using.

7. Drag the file ZBNKSTMT.jcl into the dotted area of the JCL CONTROL page, and then click SUBMIT.

A popup window and messages above the VIEW JOB button confirm that the JCL job has been

submitted. The JCL job that you submitted reads one of the BankDemo data files, sorts the data in it, and

then prints the results.

Viewing the output

1. Click VIEW JOB.

The JOB page displays informational messages that were generated while the job was running.

2. Scroll to the bottom of the screen where you can see a number of entries in the DD ENTRIES group,

hover over the row that contains PRINTOUT in the DD NAME column, and click View ( )to the right

of the RECORDS column.

The output from the JCL job is displayed, showing that you have successfully run BankDemo in batch

mode.

Reopening the BankDemo data files

After you have run BankDemo in batch mode, if you want to run it again in online mode, you must first

reopen the data files.

1. Switch back to your TN3270 terminal emulator, and then press Ctrl+Shift+Z to clear the screen.

2. Enter the following, which is the name of a supplied transaction to open BankDemo's data files:

OFIL

A message is displayed confirming that the data files have been opened. You are now free to run

BankDemo in online mode again.

Investigating scale-out features in the BankDemo

demonstration application This section contains two tutorials that enable you to take a closer look at Enterprise Server's scale-out

features in action while running the PAC version of the BankDemo demonstration application. To be able to

run these tutorials you must have installed the PAC version of BankDemo by selecting Deploy PAC demo on

the Demo Settings tab when deploying the Enterprise Server on Azure template.


of 37

The first tutorial looks at the basic set-up that enables multiple Enterprise Server virtual machines to appear

to function as a single entity, while the second shows how you can change a module of an application

without having to stop and restart the application.

Introduction to Enterprise Server scale-out features

Enterprise server instances are typically deployed as a scale-up server. This means that performance is

improved by adding or replacing the existing hardware components. Ultimately, the server's performance is

limited by the machine's existing resources.

A Performance and Availability Cluster (PAC) enables you to configure enterprise server instances in a scale-

out architecture. In a PAC, multiple enterprise server instances work together, as a single logical entity.

A PAC can provide the following advantages over a single enterprise server instance:

Availability - A PAC that utilizes distributed enterprise server instances improves robustness to

hardware or network issues.

Performance - Multiple enterprise server instances work together to maximize the overall

performance and throughput, potentially performing better than a single enterprise server instance.

The enterprise server instances in a PAC need to be able to share synchronized user and system data. To

facilitate the sharing and synchronicity requirement a PAC uses a data store referred to as a Scale-Out

Repository (SOR).

Note: Enterprise Server Scale-Out Performance and Availability Clusters is in Early Adopter Product

(EAP) release status. We will continue the development of additional features and provide

additional interfaces via patch updates and future releases.

Multiple Enterprise Server virtual machines acting as a single logical entity

After you have successfully deployed Enterprise Server into Azure you can perform the steps in this tutorial

to use the PAC version of BankDemo to illustrate that multiple regions are working together.

1. Connect a TN3270 terminal emulator to the load balancer using the following details:

mfes-eslb-IP-address:5557

where:

mfes-eslb-IP-address is the DNS name of the load balancer. To obtain this value:

a. Use the Search box on the Azure portal to locate the mfes-eslb load balancer.

b. On the Load balancers page, select the mfes-eslb load balancer.

The load balancer details blade is displayed. The Public IP address field shows the IP address

and DNS name of the mfes-eslb load balancer.

5557 is the port number for the PAC version of BankDemo.


of 37


3. Enter the following command to close the BNKHELP file across the PAC:

CFMT CL BNKHELP



to do this.

5. If ESCWA is not already displayed, double-click the ES Common Web Administration shortcut on the

mfes-rdg01 desktop. This is the third Google Chrome shortcut from the top.



6. Click NATIVE from the menu.

7. In the navigation pane, click Directory Servers > mfes-es01 > BNKDM.

8. Click CICS > Resources from the menu at the top.

9. Click Active in the drop-down list next to RESOURCES.

10. Expand the FCT item and select BNKHELP.

The State field shows that the BNKHELP file is closed. You could do the same check for BNKDM2 under

ESSERVER2.

11. Return to your TN3270 terminal emulator. If necessary, reconnect using the same credentials that you

used at step 1.


13. Enter the following command to open the BNKHELP file across the PAC:

CFMT OP BNKHELP

14. Return to ESCWA in Google Chrome in the mfes-rdg01 virtual machine.

15. Repeat steps 7 through 10.

Notice that the BNKHELP file is now marked as open for reading and writing.

Updating modules in a live application

This tutorial illustrates a scenario in which some mistakes have been spotted in one of the BankDemo

screens. The issues have been fixed, and using the PAC you introduce the fixed module into the PAC without

having to take down the application. Without the use of a PAC, you would not be able to introduce the fixed

module without having to stop and restart the BankDemo application.

1. If your TN3270 terminal emulator is not connected to the load balancer, connect it as described in

step 1 of the section Multiple Enterprise Server virtual machines acting as a single logical entity.



of 37

3. Enter the following command to run the BankDemo application:

BANK

The BankDemo sign-on screen is displayed.

4. Specify B0004 as the user ID, press Tab, then enter any non-blank character string as the password.

The BankDemo main options screen is displayed. The cursor is positioned on the first option, Display

your account balances.

5. Press X to select Display your account balances, and then press Enter.

Figure 7: Typos on the Account Balance display screen

The BankDemo account balances screen is displayed, showing the balances of the different accounts

held by this user. Notice that there are two typos at the bottom of the screen: it says "bdased on

you" instead of "based on your".


of 37

6. If you are not still connected to the mfes-es01 virtual machine, connect to it as described in the

section Connecting to an Enterprise Server virtual machine on Linux or Connecting to an Enterprise

Server virtual machine on Windows.

7. On the mfes-es01 virtual machine, switch to using the updated file.

On Windows the fixed file is C:\BankDemo_PAC\BBANK30P_Fixed.dll.

1. Rename this file to BBANK30P.dll.

2. Run the following command from an Enterprise Server command prompt:

caspac -aLoadCics=c:\BankDemo_PAC\BBANK30P.dll -sredis,mfes-redis:6379 –nDEMOPSOR

On Linux the fixed file is /home/demouser/BankDemo_PAC/BBANK30P_Fixed.so.

1. Rename this file to BBANK30P.so.

2. Run the following command:

caspac -aLoadCics=/home/demouser/BankDemo_PAC/BBANK30P.so -sredis,mfes-redis:6379 –nDEMOPSOR

Note: Making this change on the mfes-es01 virtual machine results in the change

also being made in the Scale-Out Repository, which means that the change is in

effect for all of the Enterprise Server virtual machines using the Scale-Out

Repository.

8. Return to your TN3270 terminal emulator. If necessary, reconnect using the same credentials that

you used at step 1.


10. Enter the following command to load the new copy of the BBANK30P module:

CPMT NE BBANK30P

11. View the console log to verify that the updated version of the BBANK30P module has been picked

up.

a. On the mfes-rdg01 virtual machine, if the BNKDM region isn't already selected in the

navigation pane, click Directory Servers > mfes-es01 > BNKDM.

b. Click MONITOR > Logs > Console Log from the menu at the top.

An informational message in the console log indicates that a new version of the BBANK30P

module was loaded. Other regions will load and use the new version of the BBANK30P

module when it is next called in that region.


of 37

12. Run the BankDemo application so that the BBANK30P module is called, resulting in the fixed module

being used.

a. Return to your TN3270 terminal emulator. If necessary, reconnect using the same

credentials that you used at step 1.

b. Press Ctrl+Shift+Z to clear the screen.

c. Enter the following command to run the BankDemo application:

BANK

The BankDemo sign-on screen is displayed.

d. Specify B0004 as the user ID, press Tab, then enter any non-blank character string as the

password.

The BankDemo main options screen is displayed. The cursor is positioned on the first option,

Display your account balances.

e. Press X to select Display your account balances, and then press Enter.

The BankDemo account balances screen is displayed, showing the balances of the different

accounts held by this user. The two typos at the bottom of the screen are no longer there

because the fixed module is now being used.

Housekeeping after running BankDemo

This section describes tasks you might want to perform after you have run the BankDemo demonstration

application.

Stopping the BankDemo enterprise server

After you have finished with BankDemo, disconnect from the running enterprise server, and then stop the

enterprise server:

1. Click the Disconnect button ( ) on the Rumba toolbar to disconnect from the running enterprise

server.

2. Stop whichever of the enterprise servers are running the BankDemo application:

a. Connect to the mfes-rdg01 Remote Desktop Gateway virtual machine if you are not already

connected to it. See the section Connecting to a Remote Desktop Gateway virtual machine for

information on how to do this.

b. Double-click the ES Common Web Administration shortcut on the mfes-rdg01 desktop. This is

the third Google Chrome shortcut from the top.

Google Chrome opens showing the dashboard for Enterprise Server Common Web

Administration (ESCWA). The dashboard shows two warning messages (which are expected) and

a Welcome message.


of 37

c. In the left-hand pane, expand Directory Servers > mfes-es01 and click the region specified

beneath it. This will be one of BNKDMFS, BNKDMSQL, or BNKDM depending on the version of

BankDemo that is running.

d. Click GENERAL > Control.

The CONTROL page is displayed for the region that you selected.

e. Click STOP.

The Region Stop Options dialog box is displayed showing the region details and security

configuration information. This dialog box also gives you the option of specifying operating

system and security credentials to be used.

f. Click STOP.

After a few seconds the status of the region is shown as Stopped.

Note: The instructions above show how to stop an enterprise server using ESCWA.

If you have started an enterprise server from an Enterprise Server command prompt,

however, you must also stop it from an Enterprise Server command prompt. Similarly, if you

started an enterprise server from ESCWA, you must stop it from ESCWA.

To stop an enterprise server from an Enterprise Server command prompt, connect to the

mfes-es01 virtual machine, and run the relevant command. See the section Connecting to

an Enterprise Server virtual machine on Linux or Connecting to an Enterprise Server virtual

machine on Windows for information on how to connect to the mfes-es01 virtual machine.

The commands to stop an enterprise server for the different versions of BankDemo are

below.

For the Fileshare version:

casstop -rBNKDMFS

For the SQL Server version:

casstop -rBNKDMSQL

For the PAC version:

casstop -rBNKDM

Starting the BankDemo enterprise server manually

The enterprise servers used by BankDemo are started automatically when you launch this quickstart. As a

result, if you stop these enterprise servers and then want to re-run the BankDemo application, you must

manually start the enterprise server that is appropriate for the version of BankDemo that you want to run.


of 37



to do this.

2. If ESCWA is not already displayed, double-click the ES Common Web Administration shortcut on the

mfes-rdg01 desktop. This is the third Google Chrome shortcut from the top.



3. In the left-hand pane, expand Directory Servers > mfes-es01 and click the region specified beneath it.

This will be one of BNKDMFS, BNKDMSQL or BNKDM depending on the version of BankDemo that is

running.

4. Click GENERAL > Control.

The CONTROL page is displayed for the region that you selected.

5. Click START.

The Region Start Options dialog box is displayed showing the region details and security configuration

information. This dialog box also gives you the option of specifying operating system and security

credentials to be used.

If you are using the PAC version of BankDemo you can check Cold Start to specify that a cold start will be

performed. For more information on cold starts see the Cold Start option's popup help or the

description of the casstart command in your Enterprise Server documentation.

6. Click START.

After a few seconds the status of the region is shown as Started.

Note: The instructions above show how to start enterprise servers using ESCWA. If you would rather

use the command line to start your enterprise server, connect to the mfes-es01 virtual machine, and

run the relevant command. See the section Connecting to an Enterprise Server virtual machine on

Linux or Connecting to an Enterprise Server virtual machine on Windows for information on how to

connect to the mfes-es01 virtual machine.

The commands to start an enterprise server for the different versions of BankDemo are below.

For the Fileshare version:

casstart -rBNKDMFS

For the SQL Server version:

casstart –rBNKDMSQL

For the PAC version:


of 37

casstart –rBNKDM

When starting the enterprise server for the PAC version of BankDemo you might want to use the

/s:c option to specify that the enterprise server is to be cold started. For more information, see the

description of the casstart command in your Enterprise Server documentation.

Whichever method you use to start an enterprise server (command line or ESCWA), you must use

the same method to stop it.

Commonly performed tasks for use in the tutorials

This section contains descriptions of a number of tasks that you will need to perform at different stages as

you follow the Enterprise Server tutorials. The steps described in this section are not part of the tutorials,

but are listed here so that you can easily refer to them from the relevant points when you are running

BankDemo.

Connecting to a Remote Desktop Gateway virtual machine

This section describes how to connect to the Remote Desktop Gateway virtual machine from which you can

run Enterprise Server Common Web Administration (ESCWA) and access the Enterprise Server virtual

machines.

Note: The following steps assume that when deploying the Enterprise Server on Azure template you

used the default value for the Cluster prefix parameter on the Basics tab. The default value for this

parameter is mfes, which results in the creation of a Remote Desktop Gateway virtual machine

called mfes-rdg01.

If you specified a value other than mfes for the Cluster prefix parameter, whenever the following

steps refer to mfes-rdg01 you must instead use the name of the corresponding virtual machine on

your system.

1. Use the Search box on the Azure portal to locate the mfes-rdg01 virtual machine.

2. On the Virtual machines page, click the ellipses (…) in the row for mfes-rdg01 and click Connect.

The Connect to virtual machine blade is displayed.

3. On the RDP tab, click Download RDP File.

4. Save the .rdp file to your machine.

5. Using Windows Explorer, navigate to the .rdp file you just saved, then double-click it.

A Remote Desktop Connection dialog box is displayed asking you to confirm that you want to connect

to the mfes-rdg01 virtual machine.

6. Click Connect.

A prompt is displaying requesting a user ID and password.


of 37

7. For the ID, specify \ID (or localhost\ID), where ID is the value that you specified for the

Administrator user name parameter on the Virtual Network Configuration tab when you deployed

Enterprise Server.

For the password, specify the password that you specified for the Administrator user password

parameter on the Virtual Network Configuration tab, then click OK.

A message box is displayed to say that the identity of the remote computer cannot be confirmed.

8. Click Yes to confirm that you want to connect to the remote computer.

A Networks message asks if you want to make the computer visible on the network.

9. Select either Yes or No. Whichever option you choose has no effect on the behavior of the

demonstration program.

The mfes-rdg01 virtual machine is displayed, with Server Manager maximized.

10. Dismiss the Windows Admin Center message box and minimize Server Manager.

The desktop for the mfes-rdg01 virtual machine is displayed. It includes a number of shortcuts to Google

Chrome that have been preconfigured to open various web pages that are relevant to Enterprise Server.

Connecting to an Enterprise Server virtual machine on Linux

This section describes how to connect to a Linux-based Enterprise Server virtual machine. Once you are

connected to such a virtual machine you can use Enterprise Server as you would in a non-cloud

environment.




called mfes-rdg01 and Enterprise Server virtual machines called mfes-esxx.

These instructions use virtual machines called mfes-rdg01 and mfes-es01. If you specified a value

other than mfes for the Cluster prefix parameter, whenever the following steps refer to mfes-rdg01

or mfes-es01 you must instead use the name of the corresponding virtual machine on your system.

For security reasons, it is only possible to access an Enterprise Server virtual machine via a Remote Desktop

Gateway virtual machine, so you must connect to a Remote Desktop Gateway virtual machine before you

can connect to an Enterprise Server virtual machine:

1. Connect to the mfes-rdg01 Remote Desktop Gateway virtual machine if you are not already



2. Before you deployed the Enterprise Server on Azure you needed to have generated a private key file

and stored it on your local machine. Copy this private key file from your local machine to the

Documents folder on the mfes-rdg01 Remote Desktop Gateway virtual machine.


of 37

The Documents folder is C:\Users\admin-user\Documents, where admin-user is the value that you

specified for the Administrator user name parameter on the Virtual Network Configuration tab

when you deployed Enterprise Server.

3. Double-click the PuTTY shortcut on the mfes-rdg01 desktop.

The PuTTY Configuration dialog box is displayed.

4. In the Category field, expand Connection > SSH and click Auth.

5. On the Auth panel, click Browse next to the Private key file for authentication field.

6. Navigate to the Documents folder containing the private key file that you copied at step 2, select it,

then click Open.

The Private key file for authentication field shows the file you selected.

7. In the Category field, click Session.

8. On the Session panel, specify mfes-es01 in the Host Name (or IP address) field and click Open.

9. Click Yes on the PuTTY Security Alert dialog box to complete the connection to mfes-es01.

A terminal window opens prompting for a login id.

10. Enter the value that you specified for the Administrator user name parameter on the Virtual

Machine Settings tab when you deployed Enterprise Server.

You are connected to the Enterprise Server virtual machine. You did not need to specify a password

because authentication was performed using the SSH key pair.

11. To be able to run Enterprise Server commands you need to be running as the application user rather

than the administrator user, so you need to switch user ids.

Enter the following command:

su user@domain

where:

user is the id you specified for Application user name on the Demo Settings tab when

deploying the Enterprise Server on Azure template.

domain is domain name you specified for Domain DNS name on the Virtual Network

Configuration tab.

12. Enter the password that you specified for Application user password on the Demo Settings tab.

You are now logged into the Enterprise Server virtual machine as the application user.


of 37

Connecting to an Enterprise Server virtual machine on Windows

This section describes how to connect to a Windows-based Enterprise Server virtual machine. Once you are

connected to such a virtual machine you can use Enterprise Server as you would in a non-cloud

environment.




called mfes-rdg01 and Enterprise Server virtual machines called mfes-esxx.

These instructions use virtual machines called mfes-rdg01 and mfes-es01. If you specified a value

other than mfes for the Cluster prefix parameter, whenever the following steps refer to mfes-rdg01

or mfes-es01 you must instead use the name of the corresponding virtual machine on your system.

For security reasons, it is only possible to access an Enterprise Server virtual machine via a Remote Desktop

Gateway virtual machine, so you must connect to a Remote Desktop Gateway virtual machine before you

can connect to an Enterprise Server virtual machine:

1. Connect to the mfes-rdg01 Remote Desktop Gateway virtual machine if you are not already



2. From the mfes-rdg01 virtual machine, use Remote Desktop Connection to connect to the mfes-es01

virtual machine specifying the following credentials:

Computer - mfes-es01.

User name - The value that you specified for the Administrator user name parameter on the

Virtual Machine Settings tab when you deployed Enterprise Server.

Password - The value that you specified for the Application user password parameter on the

Virtual Machine Settings tab.

A message box is displayed to say that the identity of the remote computer cannot be confirmed.

3. Click Yes to confirm that you want to connect to the remote computer.

4. Select either Yes or No when asked if you want to make the computer visible on the network.

Whichever option you choose has no effect on the behavior of the demonstration program.

The mfes-es01 virtual machine is displayed, with Server Manager maximized.

5. Dismiss the Windows Admin Center message box and minimize Server Manager.

The desktop for the mfes-es01 virtual machine is displayed. Its desktop is clear, but Enterprise

Server is installed and ready for use.

6. To be able to run Enterprise Server commands you open an Enterprise Server command prompt but

you need to ensure that you open the Enterprise Server command prompt as the application user

rather than the administrator user.


of 37

To do this, right-click on the Enterprise Server command prompt shortcut and click Run as different

user, then when prompted for login details, specify the following:

User name - The value that you specified for the Application user name parameter on the

Demo Settings tab when you deployed Enterprise Server.

Password - The value that you specified for the Application user password parameter on the

Demo Settings tab.

The Enterprise Server command prompt opens using the required credentials for the application

user. You are now logged into the Enterprise Server virtual machine running Enterprise Server as the

application user.

Additional resources This section provides links to information that is of particular use if you are not already familiar with Azure

or Enterprise Server.

Azure

Azure Cache for Redis

https://docs.microsoft.com/en-us/azure/azure-cache-for-redis/cache-overview

Azure portal

https://portal.azure.com

Azure Pricing Calculator


Create an Azure subscription


Create and use an SSH public-private key pair for Linux VMs in Azure


SQL Server availability groups

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-

portal-sql-availability-group-overview

Best practices using Enterprise Server on Azure

The best practices that apply to using Enterprise Sever in a non-Azure environment also apply to using

Enterprise Sever on Azure. See Diagnostic Best Practice in Micro Focus Enterprise Server for more

information.

Micro Focus documentation The Micro Focus website includes a wide variety of resources related to Enterprise Server. Many of these

resources are freely available, while other resources require you to have a SupportLine login. To obtain a

https://docs.microsoft.com/en-us/azure/azure-cache-for-redis/cache-overview

https://portal.azure.com/




https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-availability-group-overview

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-availability-group-overview

https://supportline.microfocus.com/examplesandutilities/TroubleShootingpack/Best%20Practice%20implementation%20of%20MF%20Enterprise%20Server.pdf


of 37

login, you need a valid license for Enterprise Server (or other relevant Micro Focus product). For licensing

information, see Costs and licenses, earlier in this guide.

The following resources are freely available:

Configuring the Fileshare server

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-

WIN/BKFSFSSTDOS011.html

Diagnostic best practice in Micro Focus Enterprise Server

https://supportline.microfocus.com/examplesandutilities/TroubleShootingpack/Best%20Practice%20im

plementation%20of%20MF%20Enterprise%20Server.pdf

Enterprise Server architecture

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/GUID-B2ED168C-

812D-4660-9A2C-F5A106E90FDD.html

Enterprise Server instance architecture

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-

WIN/BKCACAINTRU005.html

Enterprise Server on-demand training

https://www.microfocus.com/ondemand/courses/enterprise-server-basic-diagnostics-training-free/

Enterprise Server on UNIX product documentation

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-UNIX/index.html

Enterprise Server on Windows product documentation

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/index.html

Guide to securing Enterprise Server

https://supportline.microfocus.com/supportresources/documentation/A%20Guide%20to%20Securing%

20Enterprise%20Server.pdf

Guidelines for reporting incidents

https://supportline.microfocus.com/000/MicroFocus_EnterpriseandCOBOL_initial_incidentreporting_G

uidelinesforcustomers.pdf

Micro Focus End User License Agreement

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/GUID-0562B3C9-

2271-4CE8-AF64-93DE4940077F.html

Requesting a trial license for Enterprise Server


To set environment variables from the user interface

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/GUID-B31297A6-

577B-4118-961B-FBD8DB4C2892.html

The following resource requires you to have a SupportLine login:

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/BKFSFSSTDOS011.html

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/BKFSFSSTDOS011.html



https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/GUID-B2ED168C-812D-4660-9A2C-F5A106E90FDD.html



https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/BKCACAINTRU005.html



https://www.microfocus.com/ondemand/courses/enterprise-server-basic-diagnostics-training-free/

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-UNIX/index.html

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/index.html

https://supportline.microfocus.com/supportresources/documentation/A%20Guide%20to%20Securing%20Enterprise%20Server.pdf


https://supportline.microfocus.com/000/MicroFocus_EnterpriseandCOBOL_initial_incidentreporting_Guidelinesforcustomers.pdf

https://supportline.microfocus.com/000/MicroFocus_EnterpriseandCOBOL_initial_incidentreporting_Guidelinesforcustomers.pdf




https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/GUID-B31297A6-577B-4118-961B-FBD8DB4C2892.html

https://www.microfocus.com/documentation/enterprise-developer/ed-latest/ES-WIN/GUID-B31297A6-577B-4118-961B-FBD8DB4C2892.html


of 37

Enterprise Server Troubleshooting Enablement Pack and Support Videos

https://supportline.microfocus.com/examplesandutilities/TroubleShootingpack/index.aspx

Security

Information on security-related aspects of using Enterprise Server is available in Guide to Securing

Enterprise Server.

Troubleshooting Q. My application encountered an error when running under Enterprise Server. What information do I need

to include when informing Micro Focus of the issue, and what is the best way of obtaining that information?

A. For all troubleshooting exercises, gather as much information as possible about the state of the

enterprise server region when the problem occurred and about the events leading up to the problem. This

should include the date/time that the problem occurred, observations on what was happening in the

system, how long it had been running, what the symptoms were, and how/where these were observed.

When a problem occurs, capture and provide specific logs, traces and dumps, and ideally the contents of

various configuration files, directories, and the output from a number of operating system tools. Do this as

soon as possible after the failure occurs.

You can use the MFESdiags diagnostic collection script— mfesdiags.sh on Linux or MFESdiags.cmd on

Windows —to collect the required Enterprise Server diagnostic information automatically.

This script is included in each Enterprise Server virtual machine in /utils on Linux or c:\utils on Windows. It

can be run from any command prompt or from Windows Explorer as appropriate. You will be prompted for

the region name. You should create a .zip file of the resultant data collection directory, and attach it to the

Support Incident (SI) that you submit.

The script invokes the relevant "mfsupport" utility, which collects information about the operating system

and machine hardware along with details about Micro Focus products installed.

As a minimum, if MFESdiags isn’t used to collect the data, you should collect and provide the following items

as soon as possible after a failure (by zipping or ‘tar’ing the contents of the system/region directory):

console.log

log.html or log-*.html (for communications problems)

Journal log (for MFDS/security problems)

Any casdump or aux traces

mfSupportInfo

However, the MFESdiags data collection script collects the preceding items, and other useful information

details, as follows:

All files from the Enterprise Server's System/Region Directory, including:

https://supportline.microfocus.com/examplesandutilities/TroubleShootingpack/index.aspx




of 37

– console.log and console.bak. The communications process log log.html or log-*.html.

– Any trace diagnostic datasets, casauxta.rec and casauxtb.rec.

– Any system abend dumps (casdumpa.rec, casdumpb.rec or casdumpx.rec).

– Any HSF output files (*.csv).

The output from mfSupportInfo – this contains product and system information.

The Resource Definition File (RDO/RDT), dfhdrdat.

The Directory Server (MFDS) log file.

The Directory Server configuration directory.


of 37

Notices © Copyright 2020 Micro Focus or one of its affiliates.

The only warranties for this product and any associated updates or services are those that may be described

in express warranty statements accompanying the product or in an applicable license agreement you have

entered into. Nothing in this document should be construed as creating any warranty for a product, updates,

or services. The information contained in this document is subject to change without notice and is provided

"AS IS" without any express or implied warranties or conditions. Micro Focus shall not be liable for any

technical or other errors or omissions in this document. Please see the product's applicable end user license

agreement for details regarding the license terms and conditions, warranties, and limitations of liability.

This product includes software developed by Computing Services at Carnegie Mellon University (http://

www.cmu.edu/computing/)".