Technical instruction - Administration

Owned by Mattias Löfstrand
Last updated: 27 Nov 2017
3 min read

This document is intended for technical staff administrating Signifikant Platform (focus operations setup/monitoring).

System down

Check list if system is down

Check list if system is down is available here: Technical instruction - Down time check list

Test and production

It is strongly advisable to keep both a test and a production environment.

Ensure test environment reflects the setup of the production environment and always follow the procedure to verify updates and changes in configuration in the test environment prior to updating or changing the production environment. Also ensure to be prepared to rollback any changes to production environment in case of any disturbances.

Log files

Location of log files

Web Viewer and Server will write log entries to a log file named AssertWeb.log and AssertServer.log. The default location of these log files is

C:\ProgramData\Signifikant\Assert\

Log file location can be configured, refer to reference [1] for how to change log file locations.

Log files on separate share

It is recommended to keep log files on a share separate from the application and OS.

Log level

Log level can be configured to several different levels, refer to Configuration of Web Viewer version 4.x for available log levels.

The log level for Assert Web Viewer is controlled by server.config located in

C:\inetpub\wwwroot\AssertWeb\App_Data\

The log level for Assert Server is controlled by server.config located in

C:\ProgramData\Signifikant\Assert\

Log level

During implementation, it is recommended to keep the log level at verbose. During production, it is recommended to keep the log level at error.

Backup and monitoring

Excluded files

If mdb and log files files are located in the site folder, these files will have to be excluded in the file area backup.

Manager and Server

Manager tool holds the parts and document data in a “site”. A site is a database and a file area. Configurations are located in ProgramData/Signifikant/Assert. Backup is recommended for

  • Site (SQL database and site file area) Default location: <data disk>:/Assert/Data/ Default database name: Assert4#<site>
  • Configurations ProgramData/Signifikant/Assert

Monitoring is recommended for

  • SQL instance
  • Available disk space
  • IIS worker process

IIS recycling

Check recycling of Default Application Pool in IIS and ensure recycling will not occur during scheduled imports or publications, or at high usage periods.

Web Viewer

Web Viewer does not hold any parts catalogue data. In some installations, Web Viewer holds users and users order history. In such case backup is recommended for

  • SQL database for users and order history Default database name: Assert4#Server

Monitoring is recommended for

Install files

An install area where application install files and configurations may be stored is recommended. Location of this install area as per client’s policies. Standard location is:

D:/Signifikant/Install/

The area shall contain the latest install versions with configurations to ensure recovery as well as downgrading is possible.

Error email reset

Web Viewer may produce an email when an error occurs. Only one email is sent and then a flag is raised. Until the flag has been lowered, no more emails will be sent. The flag may be reset in the admin section of the web viewer.

When the error flag is raised, the web viewer will write to a file:

C:\ProgramData\Signifikant\Assert\AssertErrorFlag.txt

Other

Normal security monitoring of servers and SQL instance per client’s policies. Possible integrations with ERP or web shop may require separate security monitoring depending on design and client’s policies.