On-premises installation

This chapter explains installation and the necessary settings for configuring the PANTHEON Web program when opting for an On-premises installation.

After choosing and activating Web license, users must follow the next steps.

1. Setting up the environment

Web Setup installs all necessary services in IIS and standalone (Workflow service) to enable full PAW functionality. During the installation, a new PAW_master database is created that contains links to associated PANTHEON databases.

IIS Prerequisites:

•            Microsoft Windows Server 2019 operating system or newer

•            Microsoft SQL Server 2019 or newer with PANTHEON database

•            Microsoft .NET 4.8 or newer

•            Microsoft IIS installation with ASP.NET 4.7

2. Installation verification

In PANTHEON, the Country field for Our company field must not be empty and Country must be the same as localization of licence.

Iso code must be field same as localization.

After installation check table tRA_MasterComSite

• Server_name
• Database_name
• Country

Also check all config files on C:\inetpub\wwwroot\PAW\WebApi

Checking config file for PAAS on C:\inetpub\wwwroot\PAW\PA

In ServerName we must insert IP address and PORT from SQL Server.

Check RegEdit for PAAS

• PAAS.exe can operate as a Service and can start Pantheon(s) as part of the Service.
  In this case an OS (Operational system) errors can occur with system VCL calls: AllocateHandle, CreateMenu, etc.
• Double click, scroll right to SharedSection -> THIRD number (Service heap size) change 700 to 40000

3.  Upgrade

If you have an old version of .NET Core, install new .NET Core. All Web files are automatically updated by runing new Web installer.

 4. Language configuration

WARNING PANTHEON Web language has to be the same as selected company's country.

In BackOffice/Web.config file search for SiteConfig. Uncomment the appropriate line to change PAW language.

For installations with cyrillic alphabets, enter databaseLocalization field below exactly as is entered in PANTHEON. Run the following SQL to retrieve the data from PANTHEON database:

select acISOCode from the_setCountry where acCountry = (select acCountry from the_setSubj where acSubject = (select acOurCompany from tpa_sysparam))

5.  PANTHEON configuration

WARNING After installation, Pantheon.exe for your localization needs to be manually downloaded and copied to PAW\PA folder. Pantheon.exe that is already present has EU localization (English) and may not be appropriate for your configuration. Simply replace the existing Pantheon.exe.

6. Additional configuration options

• Ports (for advanced users only)

By default, PAW needs Ports 9000, 9001, 9003, 9004 to be free, because installation uses those ports to install different PAW services to those ports. If you need to install PAW to different ports, please consult support.

7. Checking if services are operational

For PANTHEON Web to funcion normaly all three services needs to be opreational:

• WebApi: Open in browser localhost:9001/swagger. If anything opens, it works.
• BackOffice: Open in browser localhost:9000. If login screen opens, it works.
• PAAS: Open in browser localhost:9004. If a page opens, it works.

8. Invalid login error

This is very common error, which can be caused by a large range of configuration options or system errors. Here, you can find some of the most common issues with configuration options that should be checked:

• PAW does not support login without password, while PANTHEON does.
• Check the above prerequisites and check if all three services are operational (WebApi, BackOffice, PAAS).
• Check that the country is defined for Our company field in PANTHEON.
• Check if PAW language is the same as the company's country (see above on how to check/fix it).
• Check if the correct license for PAW is installed in the target database.
• Check user permissons for PAW in PANTHEON.

9. Other errors

Here are a few other possible errors and the tips for their troubleshooting:

• HTTP Error 500.19 – Internal Server Error and one of the first lines is Module IIS Web Core.
  • Re-run .NET Core Hosting bundle installer (select Repair), and after instalation restart IIS.
• In EventViewer, there is an error writing to WebApi/logs:
  • In folder WebApi, create subfolder logs and give everyone full permissions to it.
• Check WebApi/web.config if <aspNetCore processPath="dotnet.exe"...> is available on your system Path.