Configuring the Micro Focus Enterprise Server for .NET Environment

Note: This topic explains the configuration required to use Micro Focus Enterprise Server for .NET on a single machine (local environment). Once you have established this environment, see System Architecture Options for information about optionally expanding your configuration to include multiple machines or to reconfigure Micro Focus Enterprise Server for .NET to use a scaled-out architecture.

Following a successful installation of Enterprise Developer and before using Micro Focus Enterprise Server for .NET, you must further configure your environment as follows:

Install third-party software

Microsoft .NET Framework 4.0 or later

If your Windows operating system does not automatically install the .NET Framework, download and install it separately. See the Microsoft Web site for details.

Microsoft SQL Server

Enterprise Server for .NET requires that you have Microsoft SQL Server installed. The following versions are supported:

Microsoft SQL Server 2012 or later - for production or development environments
Microsoft SQL Server Express 2012 or later - for development environments only

TN3270 Terminal Emulator

We recommend that you use Micro Focus HACloud, which is automatically installed by Enterprise Developer. However, you may choose to install any other Micro Focus or a third-party TN3270 terminal emulator.

Configure Windows

Irrespective of your Windows version, you must perform some additional configuration tasks before using Micro Focus Enterprise Server for .NET.

Note: See your Windows operating system Help for information on accessing and using the Windows Control Panel. The information in this topic is based on Windows 10, but might be different depending on your Windows version.

Ensure Administrator privileges

Set the Windows account type for the local user to Administrator.

Activate additional features

Check the following additional features on the Turn Windows features on or off window in the Windows Control Panel:

.NET Framework version Advanced Services

ASP.NET version
WCF Services
- HTTP Activation
- TCP Port Sharing
- TCP Activation (Windows 10) or Non-HTTP Activation (Windows versions earlier than 10)

Internet Information Services

Web Management Tools
- IIS 6 Management Compatibility
  - IIS Metabase and IIS 6 configuration compatibility
- IIS Management Console
World Wide Web Services
- Application Development Features
  - .NET Extensibility version
  - ASP.NET version
  - Common Http Features
    - Default Document
    - Directory Browsing
    - Static Content
  - Health and Diagnostics
    - HTTP Logging
    - Tracing
  - Security
    - Basic Authentication
    - Windows Authentication

Note: If you are prompted to reboot your machine following these changes, do so at this time.

Start the Net.Tcp Port Sharing Service

If it is not already running, start the Net.Tcp Port Sharing Service from the Services window in the Windows Control Panel.

Configure SQL Server

You need to ensure that the local SQL Server user has sufficient privileges to access the database. Do this from Microsoft SQL Server Management Studio as follows:

Start SQL Server Management Studio, specifying the connection as follows:

Server type	`Database Engine`
Server name	`localhost`
Authentication	`Windows Authentication`

If it doesn't already exist, create a new Security Login - NT Authority\SYSTEM.
Add the following Server Roles to the NT Authority\SYSTEM login:
- sysadmin
- dbcreate

Note: For specific instructions on using the Microsoft SQL Server Management Studio, see your Microsoft documentation.

Run the wassetup command

The wassetup command configures the Windows Internet Information Services (IIS) and Windows Authentication Service (WAS) if required, and ensures that all required services are running.

Start an Enterprise Developer command prompt as an administrator. If you need instructions, see To start an Enterprise Developer command prompt as an administrator.
At the command prompt, enter wassetup.
When the command has completed its run, you should see the message Operation successfully completed.