OutSystems Platform this.Version.ToString() βthis.BetaVersion

Checklist for OutSystems Platform Server Installation

This checklist describes the procedures you need to perform to install, upgrade, or update the OutSystems Platform Server. If you haven't already, read the System Requirements technical note to understand what it takes to install the OutSystems Platform.

In order to customize the checklist content for your particular installation requirements, you need to select below the kind of installation, the corresponding roles, operating system and other properties for the machine you'll be configuring. You should do this for each machine in order to have a checklist for each one of them.

It may prove useful to print each of the generated checklists. Once you have selected the necessary items for one machine, you'll be ready to print it out. Afterwards, you can move on to another checklist configuration.

Please select which kind of task you'll be doing:

This checklist should be used when you are installing a new standalone server, a new farm installation or adding new Front-end Servers to a previous installation. If you are simply trying to upgrade an existing installation, you should use one of the other installation types.

This checklist should be used when you want to upgrade your existing system to a new release. This happens when the Major, Minor or Build number changes (M.m.b.r). Besides fixes for reported problems, new releases usually provide new features.

This checklist should be used when you want to update your existing system to a new revision. This happens when the Major, Minor and Build numbers are the same, but the Revision number changes (M.m.b.r). Revisions usually only include fixes to reported problems.

Please select which role or combination of roles this machine will be responsible for:

Deployment Controller Servers are responsible for compiling eSpaces and publishing the compilation to all Front-end Servers. You can only have one Deployment Controller Server per farm. Select this role if the machine you're installing will be performing only this role.

Front-end Servers are responsible for running all deployed eSpaces. You can have as many Front-end Servers per farm as you want. Select this role if the machine you're installing will be performing only this role.

The Database is where the platform stores all its data. All other machines in your farm or standalone installation will need access to this machine in order to work. Select this role if the machine you're installing will be performing only this role.

Deployment Controller Servers are responsible for compiling eSpaces and publishing the compilation to all Front-end Servers. You can only have one Deployment Controller Server per farm.

Front-end Servers are responsible for running all deployed eSpaces. You can have as many Front-end Servers per farm as you want.

Select this combination if the machine will accumulate the roles of Deployment Controller Server and Front-end Server.

Deployment Controller Servers are responsible for compiling eSpaces and publishing the compilation to all Front-end Servers. You can only have one Deployment Controller Server per farm.

The Database is where the platform stores all its data. All other machines in your farm or standalone installation will need access to this machine in order to work.

Select this combination if the machine will accumulate the roles of Deployment Controller Server and Database.

Deployment Controller Servers are responsible for compiling eSpaces and publishing the compilation to all Front-end Servers. You can only have one Deployment Controller Server per farm.

Front-end Servers are responsible for running all deployed eSpaces. You can have as many Front-end Servers per farm as you want.

The Database is where the platform stores all its data. All other machines in your farm or standalone installation will need access to this machine in order to work.

Select this combination if the machine will accumulate the roles of Deployment Controller Server, Front-end Server and Database.

The Kannel is responsible for connecting the Platform Server with SMSC's and GSM Modems. Select this role if you'll be installing this more recent and powerful Kannel open source WAP and SMS gateway version.

Please select what type of installation you'll be doing:

A Standalone installation is one where the single Front-end Server in the installation is also the Deployment Controller Server. It may also be the Database.

A Farm installation is one where two or more machines will be Front-end Servers or the single Front-end Server is not the same machine as the Deployment Controller Server. One of the Front-end Servers in this installation may accumulate the role of Deployment Controller Server or you can have a separate machine dedicated to that role.

Please select which operating system you'll be using on this machine:

Microsoft Windows Server 2008 R2 (64 bit editions)

Microsoft Windows Server 2012 R2 (64 bit editions)

Other operating system. This option only applies to the SMS Gateway, Oracle Database machines, or databases using RDS.

Please select which database software you'll be using:

Microsoft SQL Server 2014

Microsoft SQL Server 2012

Microsoft SQL Server 2012 on Amazon RDS

Microsoft SQL Server 2008 or 2008 R2

Oracle Database

Oracle Database on Amazon RDS

Please select the database authentication mechanism OutSystems Services and Applications use to connect to the database server:

Use SQL Server Authentication with username and password in connection strings.

Use Windows Authentication to connect to the Outsystems database. No password is stored in configuration files or present in the connection strings. All the Servers and Database machines need to be on the same Domain.

Overview

The document is organized in the following sections:

In each section there is a list of topics that you have to test in order to successfully install OutSystems Platform Server. The mandatory topics are the ones that must be checked in order to have a certified installation, i.e. the requirements necessary to guarantee that OutSystems supports your installation. The mandatory topics are in red and the icon associated is *. On the other hand, the optional topics are only recommended and you are not forced to check them. The optional topics are in plain text and the icon associated is .

Pre-installation check list

In this section you have a list of all the issues that you must validate before installing the software.

OutSystems Platform Server

Topics that you must check before start installing OutSystems Platform Server.

Disable IPv4 checksum offload, large receive offload, large send offload and TCP checksum offload on the NIC driver settings:
  1. Access the Front-End server using Remote Desktop;
  2. Access Control Panel\Network and Internet\Network Connections;
  3. Right-click on the network adapter that reaches the SQL Server, and select Properties;
  4. Click Configure;
  5. In the Advanced tab, select the following settings* and disable them:
    • IPv4 Checksum Offload;
    • Large receive Offload (IPv4);
    • Large Send Offload (IPv4);
    • TCP Checksum Offload (IPv4).
    * The settings name may differ slightly depending on the installed driver and model.
  6. Close all dialog boxes with OK button (network connectivity will be momentarily lost).

For more details, check Timeout Connection to Amazon RDS.
* Amazon RDS dimension:
  • The minimum recommended size for a database instance is the medium size, that is, the Instance class must be at least "db.m1.medium". This is specified when you create the instance.
Amazon RDS time zones:
  • If you want your database to be in a different time zone, you will have to define the RDS time zone when creating the RDS.
    NOTE: When you change the database time zone, all your front-ends must be configured with the same time zone as the database.

    For more information about Amazon RDS time zones for Oracle check this page.
Amazon RDS time zones:
  • It is not possible to change the time zone for Microsoft SQL Server RDS. The default time zone is UTC.
    NOTE: All your front-ends must be configured with the UTC time zone.
Amazon RDS time zones:
  • You must configure your front-end using the same time zone as the RDS.
Amazon RDS High-availability:
  • If you want to have High-availability (Multi-AZ) in your RDS, it must be enabled when creating the RDS. When creating the RDS, in DB instance details, pick Yes for Multi-AZ deployment option. You can also change it for an existing Oracle RDS database in the AWS Management Console -> Instance actions -> Modify.
Amazon RDS High-availability:
  • If you want to have High-availability (Multi-AZ via Mirroring) in your RDS, it must be disabled during the execution of the Configuration Tool. When creating the RDS, in DB instance details, pick No for Multi-AZ deployment option. You can also change it for an existing SQL Server RDS database in the AWS Management Console -> Instance actions -> Modify.
* Windows Server 2008 R2:
  • You can use any 64-bit (x64) Windows Server 2008 R2 edition, except Server Core option.
* Windows Server 2012 R2:
  • You can use any 64-bit (x64) Windows Server 2012 R2 edition, except Server Core option.
* Install the latest Windows Server 2008 R2 Service Pack
* Install the latest Windows Server 2012 R2 Service Pack
* Install Microsoft .NET Framework 4.5.1
Install the latest Security Microsoft Updates
*

Add Application Server Role and Internet Information Services 7:

Open Server Manager

In the left tree, select Roles

  1. Make sure that you have installed the role Application Server. If you don't, install it by doing the following:
    1. In the right pane, click Add Roles
    2. Choose Application Server (and accept all dependencies);
    3. In Role Services, make sure to select:
      • .NET Framework 3.5.1

  2. Make sure that you have installed the role Web Server (IIS). If you don't, install it by doing the following:
    1. In the right pane, click Add Roles
    2. Choose Web Server (IIS)
    3. In Role Services, make sure to select:
      • Under Web Server:
        • Under Application Development:
          • Choose ASP.NET
        • Under Security:
          • Choose Windows Authentication
        • Under Performance:
          • Choose Static Content Compression
          • Choose Dynamic Content Compression
        • Under Management Tools:
          • Choose IIS Management Console
          • Under IIS 6 Management Compatibility:
            • Choose IIS 6 Metabase Compatibility
      • Make sure to accept all dependencies of the items mentioned above. For all the items not mentioned above, leave the default value.

If the role is already installed, confirm that the above items are already installed. If they are selected, then their dependencies are also correctly chosen.

*

Add Application Server Role and Internet Information Services 8.5:

Open Server Manager and, in the left tree, select Local Server

On the right window, scroll down to the Roles and Features list and make sure that you have installed the Application Server and Web Server(IIS) roles. If you don't, make sure to follow these instructions:

  • Installing the Application Server and Web Server (IIS) roles:
    1. Click the Manage menu and then click Add Roles and Features
    2. On the Installation Type page, select Role-based or feature based installation and click Next
    3. On the Server Selection page, select your Local Server from the server pool and click Next
    4. On the Server Roles page, select Application Server (accepting all dependencies) and click Next
    5. On the Features page, select the .NET Framework 3.5 Features from the list and click Next
    6. On the Application Server Role Services page, select Web Server (IIS) Support from the list
    7. On the Add Roles and Features wizard, click Add Features
    8. On the Application Server Role Services page, click Next
    9. On the Web Server Role (IIS) Role Services page, ensure the following role services are selected in this list:
      • Common HTTP Features
        • Default Document
        • Directory Browsing
        • HTTP Errors
        • Static Content
      • Health and Diagnostics
        • HTTP Logging
        • Request Monitor
      • Performance
        • Static Content Compression
        • Dynamic Content Compression
      • Security
        • Request Filtering
        • Windows Authentication
      • Application Development
        • .NET Extensibility 3.5
        • .NET Extensibility 4.5
        • ASP.NET 3.5
        • ASP.NET 4.5
        • ISAPI Extensions
        • ISAPI Filters
      • Management Tools
        • IIS Management Console
        • IIS 6 Management Compatibility
          • IIS 6 Metabase Compatibility
    10. On the Confirmation page, click Install

If the roles are already installed, confirm that the above items are installed as well. If they are selected, then check that their dependencies are also correctly chosen.

For more information on Installing IIS 8.5 visit http://www.iis.net/learn/install/installing-iis-85/installing-iis-85-on-windows-server-2012-r2.

*

Install Message Queuing:

Open Server Manager and, in the left tree, select Local Server

On the right window, scroll down to the Roles and Features list and make sure that you have installed the Message Queueing feature. If you don't, make sure to follow these instructions:

  • Installing the Message Queueing feature:
    1. Click the Manage menu and then click Add Roles and Features
    2. On the Installation Type page, select Role-based or feature based installation and click Next
    3. On the Server Selection page, select your Local Server from the server pool and click Next
    4. On the Server Roles page, click Next
    5. On the Features page, select the Message Queuing Server feature from the list (located under Message Queuing > Message Queuing Services) and click Next
    6. On the Confirmation page, click Install
*

Install Message Queuing:

Open Server Manager

In the left tree, select Features

Make sure to have installed the feature Message Queuing. If you don't, install it by doing the following:

  1. In the right pane, click Add Features
  2. Select:
    • Under Message Queuing:
      • Under Message Queuing Services:
        • Choose Message Queuing Server
In registry, add the AlwaysWithoutDS DWORD (32-bit) registry value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\Setup, with a value of 1:
  • The message queues will always try to contact a message queue server when running on a server registered in a domain, even if installed as local.
* Check that you have the minimum Role Services and Features needed instaled on the machine
  • To do that, open Server Manager
    • In the left tree, select Roles
      • Make sure that you have in the Application Server Role the following services installed:
        • .NET Framework 3.5.1
      • Make sure that you have in the Web Server (IIS) Role the following services installed:
        • Web Server
          • Common HTTP Features
            • Static Content
            • Default Document
            • Directory Browsing
            • HTTP Errors
          • Application Development
            • .NET Extensibility 3.5
            • .NET Extensibility 4.5
            • ASP.NET 3.5
            • ASP.NET 4.5
            • ISAPI Extensions
            • ISAPI Filters
          • Health and Diagnostics
            • HTTP Logging
            • Request Monitor
          • Security
            • Windows Authentication
            • Request Filtering
          • Performance
            • Static Content Compression
            • Dynamic Content Compression
          • Management Tools
            • IIS Management Console
            • IIS 6 Management Compatibility
              • IIS 6 Metabase Compatibility
    • In the left tree, select Features
      • Make sure that you have the following Features installed:
        • Message Queuing
          • Message Queuing Services
            • Message Queuing Server
        • Remote Server Administration Tools
          • Role Administration Tools
            • Web Server (IIS) Tools
        • Windows Process Activation Service
          • Process Model
          • .NET Environment
          • Configuration APIs
        • .Net Framework 3.5.1 Features
          • .NET Framework 3.5.1
* Check that you have the minimum Role Services and Features needed instaled on the machine
  • To do that, open Server Manager and, in the left tree, select Local Server
  • Make sure that you have in the .NET Framework 3.5 Features path the following feature installed:
    • .NET Framework 3.5 Features
  • Make sure that you have in the Web Server (IIS) path the following services installed:
    • Web Server
      • Application Development
        • .NET Extensibility 3.5
        • ASP .NET
        • ISAPI Extensions
        • ISAPI Filters
      • Common HTTP Features
        • Default Document
        • Directory Browsing
        • HTTP Errors
        • Static Content
      • Health and Diagnostics
        • HTTP Logging
        • Request Monitor
      • Performance
        • Dynamic Content Compression
        • Static Content Compression
      • Security
        • Request Filtering
        • Windows Authentication
    • Management Tools
      • IIS 6 Management Compatibility
        • IIS 6 Metabase Compatibility
      • IIS Management Console
  • Make sure that you have in the Message Queueing path the following services installed:
    • Message Queuing
      • Message Queuing Services
        • Message Queuing Server
  • Make sure that you have in the Windows Process Activation Service path the following services installed:
    • Windows Process Activation Service
      • .NET Environment 3.5
      • Configuration APIs
      • Process Model
*

Confirm that Windows Search is off:

This service is not installed by default. To determine if it is installed:

  • Open Server Manager
  • In the left tree, select Configuration - Services
  • See if a service named Windows Search exists. If so, set its properties to Startup Type: Disabled, and stop it.
*

Confirm that Windows Search is off:

This service is not installed by default. To determine if it is installed:

  • Open Server Manager and, in the left tree, select Local Server
  • Scroll down to the Services list
  • See if a service named Windows Search exists. If so, set its properties to Startup Type: Disabled, and stop it.
* Confirm that Windows Management Instrumentation Service is on and set to Automatic start:
  • Open Server Manager
  • In the left tree, select Configuration - Services
  • Locate service Windows Management Instrumentation. Confirm its properties to Startup Type: Automatic, and confirm that it is started.
* Confirm that Windows Management Instrumentation Service is on and set to Automatic start:
  • Open Server Manager and, in the left tree, select Local Server
  • Scroll down to the Services list
  • Locate service Windows Management Instrumentation. Confirm its properties to Startup Type: Automatic, and confirm that it is started.
* Set appropriate size for Event Logs:
  • Make sure that Event logs Application, Security and System have the default options:
    • Overwrite events as needed
    • Maximum log size: 20480KB
  • To confirm this:
    • Open Server Manager
    • In the left tree, select Diagnostics - Event Viewer - Windows Logs
    • Right-click each of the mentioned logs and choose Properties
    • Confirm the above mentioned options
* Set appropriate size for Event Logs:
  • Make sure that Event logs Application, Security and System have the default options:
    • Overwrite events as needed
    • Maximum log size: 20480KB
  • To confirm this:
    • Open Server Manager and, in the top menu, under Tools, select Event Viewer
    • In the left tree select Windows Logs
    • Right-click each of the mentioned logs and choose Properties
    • Confirm the above mentioned options
* Microsoft SQL Server:

You need to confirm the collations on both the database instance and the database catalog that will be used by the OutSystems Platform:

  • The database instance must be Case Insensitive;
  • The database instance must be installed with Mixed mode authentication;
  • The database catalog must be Case Insensitive and should also be Accent Insensitive.


When installing SQL Server:

  • When asked, choose authentication option Mixed mode - SQL Server and Windows Authentication;
  • Uncheck the Case-sensitive option (and, if possible, the accent-sensitive option as well. Database catalogs created afterwards just have to inherit the server settings and will also be case insensitive.
    • Database catalogs should also be Accent Insensitive
    • Actual collation to be used must comply with specific demands of the application to be deployed.


When SQL Server is already installed:

To confirm that the database instance complies with the specified requirements do the following:

  • Connect to the database server using SQL Server Management Studio;
  • In Object Explorer, right-click the top level of the object tree, and select Properties;
  • In the General page, confirm that Server Collation is case-insensitive
    : check the collation name. If it ends with CI_AI or CI_AS, the collation is case-insensitive;
  • In the Security page, confirm that Server authentication is configured with option SQL Server and Windows Authentication mode (mixed mode).

To confirm that the database catalog also complies with the specified requirements by doing the following:

  • Still using SQL Server Management Studio, in Object Explorer expand the Databases folder under the top level of the object tree;
  • Locate the database catalog that you will be using;
  • Right-click it and select Properties;
  • In the General page, confirm that Collation is case-insensitive.
    : check the collation name. If it ends with CI_AI or CI_AS, the collation is case-insensitive.
To improve performance, when creating the databases in Microsoft SQL Server, configure the default data and log files location to a partition with a 64KBcluster size.
* Due to a severe bug in SQL Server 2008 (KB958611) make sure that at least one of the following updates is installed:
  • Cumulative update package 2 for SQL Server 2008. You can download it here.
  • SQL Server 2008 Service Pack 1. You can download it here.
Install the latest Microsoft SQL Server Service Packs
* In SQL Server Configuration Manager, the SQL Server Service must be running and with Start Mode - Automatic
* Confirm that the TCP/IP protocol is enabled in SQL Server:
  • In SQL Server Configuration Manager, expand SQL Server Network Configuration and choose Protocols for <Instance_name>
  • Right-click TCP/IP and choose Properties
  • In the IP Addresses tab, configure the IP to be used. If in doubt, leave all defaults;
  • In the Protocol tab, change Enabled to Yes. Click OK.
  • Restart the SQL Server service.
* Oracle 10g R2, 11g R2 or 12c R1 Database:
  • Ensure you install Oracle 10g R2, 11g R2 or 12c R1
  • When creating the database, make sure the block size is set to at least 8KB
  • When creating the database, set the following NLS parameters:
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CHARACTERSET AL32UTF8 (Unicode support)
    or
    WE8MSWIN1252 (no Unicode support)
    NLS_DATE_FORMAT DD-MON-RR
    NLS_SORT BINARY
  • Choosing AL32UTF8 for Unicode support allows applications to handle non-western characters.
    For more information on this subject please refer to Recommended Database Character Sets.
  • The minimum recommended limit of Oracle system processes and sessions is 250. Higher values might be required for highly loaded environments, so adjust accordingly.
    • To display the current limit of system processes and sessions in your database, execute the following statement as sysdba: SELECT Value FROM v$parameter WHERE Name='processes' or Name='sessions';
    • To change the number of system processes of your database, execute a statement like:
      ALTER SYSTEM SET processes=250 SCOPE=spfile;
      ALTER SYSTEM SET sessions=250 SCOPE=spfile;
      followed by a database restart
* Oracle 12c R1 Adaptive Optimizer:
  • Running Oracle 12c database with the adaptive optimizer feature results in serious performance degradation. As such, the adaptive optimizer feature must be disabled.
    • To disable the adaptive optimizer feature follow these steps:
      • Execute the following statement as sysdba:
        ALTER SYSTEM SET optimizer_adaptive_features=false SCOPE=spfile;
      • Restart the database
For better stability and performance create a separate Oracle database instance for the session database model using the same configuration as the main database, but with the noarchivelog option set.
* Oracle 10g R2, 11g R2 or 12c R1 Services:
  • Make sure the following services/processes are running in the Oracle:
    • OracleOradb10g_home1TNSListener
    • OracleService<SID>
    • <SID> - the Service Id that identifies the instance you are going to use
* Oracle 11g R2 Patch (Linux):
  • If you are using a Linux operating system, make sure the following patch is applied:
    • Oracle patch number 8799099.
* MySQL Database:
  • Ensure you use MySQL 5.6.5+
  • Make sure sql mode is set to "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
  • Make sure innodb_file_per_table is set to 1
  • Make sure default-storage-engine is set to INNODB
  • Make sure lower_case_table_names is set to 1
  • Make sure max_allowed_packet is set to at least 128M
  • Make sure log_bin_trust_function_creators is set to 1
  • Make sure innodb_log_file_size is set to at least 1280M
This can be done by editing the MySQL configuration file:
  • C:\ProgramData\MySQL\MySQL Server 5.6\my.ini

The file should look like this:
		[mysqld]
		sql_mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
		lower_case_table_names=1
		max_allowed_packet=128M
		default-storage-engine=INNODB
		log_bin_trust_function_creators=1
		innodb_log_file_size=1280M
		innodb_file_per_table=1
		
If you have extra configuration make sure there are no duplicate settings.

Legend: * Mandatory; Optional.

* Download the Kannel 1.4.3 pre-compiled binary packages from http://www.kannel.com/download.shtml
Check Kannel documentation at http://www.kannel.com/doc.shtml
Check Kannel User Guide at http://www.kannel.org/download/1.4.3/userguide-1.4.3/userguide.html
Download, from OutSystems Network, Technical Note Third-party SMS gateway integration

Legend: * Mandatory; Optional.

Installation check list

In this section you have a list of all the steps that you must follow to guarantee that the software was successfully installed.

OutSystems Platform Server

This section provides the steps that you must follow to successfully install your Deployment Controller Server or Front-end Server.

* In Microsoft SQL Server, create a new database catalog to be used by OutSystems Platform Server.
This catalog will be used to configure runtime settings in the Configuration Tool.
* Install the Platform Server:
  • Run the installation file PlatformServer-M.m.b.r.exe and follow the on screen installation instructions
*

If until now you have not installed Platform Server in your Deployment Controller Server you should follow the Deployment Controller Server checklist up until that point.

Once that step has been completed you will be instructed to resume this checklist.

*

At this point you need to have the data and session model created. If you do not have it created yet, please refer to the Database profile in this checklist.

* Execute the Platform Server database creation script.
  • You can find it in the Deployment Controller Server under the Outsystems Platform Server Installation directory, in db\runtime_oracle_creation.sql. This file allows you to create users, tablespaces and grants the necessary permissions. By default, when executing this file, the following objects will be created:
    • Users: OSADMIN, OSRUNTIME, OSLOG
    • Tablespaces: OSSYS, OSIDX, OSUSR, OSLOG
    • Grants:
      • OSADMIN: Create Session, Create View, Create Table, Alter Session, Create Sequence, Create Procedure, Create Trigger
      • OSRUNTIME: Create Session
      • OSLOG: Create Session
  • Please check with your Database Administrator how to do this according to your database environment. At the very least, you should make sure the file paths, tablespaces and users don't clash with existing objects in the database.
  • If you change any of these settings, remember to do so throughout the file.
  • You'll need the usernames, passwords and tablespaces used in this script to configure Platform Server later on.
* Execute the Platform Server database creation script.
  • You can find it in the Deployment Controller Server under the Outsystems Platform Server Installation directory, in db\RDS_runtime_oracle_creation.sql. This file allows you to create users, tablespaces and grants the necessary permissions. By default, when executing this file, the following objects will be created:
    • Users: OSADMIN, OSRUNTIME, OSLOG
    • Tablespaces: OSSYS, OSIDX, OSUSR, OSLOG
    • Grants:
      • OSADMIN: Create Session, Create View, Create Table, Alter Session, Create Sequence, Create Procedure, Create Trigger
      • OSRUNTIME: Create Session
      • OSLOG: Create Session
  • Please check with your Database Administrator how to do this according to your database environment. At the very least, you should make sure the file paths, tablespaces and users don't clash with existing objects in the database.
  • If you change any of these settings, remember to do so throughout the file.
  • You'll need the usernames, passwords and tablespaces used in this script to configure Platform Server later on.
* Execute the Platform Server database creation script.
  • You can find it in the Deployment Controller Server under the Outsystems Platform Server Installation directory, in db\runtime_mysql_creation.sql. This file allows you to create users schemas and the necessary permissions. Please make sure you change the default passwords! By default, when executing this file, the following objects will be created:
    • Schema: outsystems
    • Users: OSADMIN, OSRUNTIME, OSLOG
    • Grants:
      • OSADMIN: SELECT on information_Schema , All privileges outsystems schema
      • OSRUNTIME: SELECT, INSERT, UPDATE, DELETE, EXECUTE, CREATE ROUTINE, ALTER ROUTINE, CREATE TEMPORARY TABLES, LOCK TABLES
      • OSLOG: SELECT, INSERT, UPDATE, DELETE, EXECUTE, CREATE TEMPORARY TABLES, LOCK TABLES
  • Please check with your Database Administrator how to do this according to your database environment. At the very least, you should make sure the schemas and users don't clash with existing objects in the database.
  • If you change any of these settings, remember to do so throughout the file.
  • You'll need the usernames and passwords used in this script to configure Platform Server later on.
* Execute the Platform Server session creation script.
  • You can find it in the Deployment Controller Server under the Outsystems Platform Server Installation directory, in db\session_mysql_creation.sql.
  • This allows you to configure the schema the user and password. Please make sure you change the default passwords By default, the objects are set to:
    • Schema: outsystems_session
    • User: OSSTATE
  • If you change any of these settings, remember to do so throughout the file.
  • Run this script like you did with the script to create the data model of the OutSystems Platform.
* Configure Platform Server settings with the Configuration Tool
- Platform Database


Start the Configuration Tool (Start -> Programs -> OutSystems -> Administration Tools).

Configure the Platform Database Schema (Database tab):
  • Set "Oracle" in the drop-down list Database Provider
  • Set the Oracle database to be used by configuring the Database section.
    If you have any doubt on how to configure this section, please use the More info link, near the Naming method drop-down.
  • Fill in User in the Admin section using the database login previously created for the Admin role
  • Fill in Tablespace and Index Tablespace fields in the Admin section with the System Tablespace and the Index Tablespace previously created
  • Fill in User in the Runtime section using the database login previously created for the Runtime role
  • Fill in Tablespace field in the Runtime section with the Runtime Tablespace previously created
  • Fill in User in the Log section using the database login previously created for the Log role
  • Fill in Tablespace field in the Log section with the Log Tablespace previously created
  • Test all users to confirm correct connectivity. For this, click Test Connection for each of the users configured.
  • Create the Platform Database schema by clicking the Create/Upgrade Database button.

Do not close the Configuration Tool at this point - further tasks are to be performed.
* Configure Platform Server settings with the Configuration Tool
- Platform Database


Start the Configuration Tool (Start -> Programs -> OutSystems -> Administration Tools).

Configure the Platform Database Schema (Database tab)::
  • Set "MySQL Database" in the drop-down list DBMS
  • Set the MySQL database to be used by configuring the Server field:
    • You can use either the DNS name or the IP of the database although DNS name is recommended
    • Examples: mysqlserver
  • Set the MySQL schema to be used by configuring the Schema field:
  • Fill in Admin user in the Admin section using the database login previously created for the Admin role
  • Fill in Runtime user in the Runtime section using the database login previously created for the Runtime role
  • Fill in Log user in the Log section using the database login previously created for the Log role
  • Test all users to confirm correct connectivity. For this, click Test Connection for each of the users configured.
  • Create the Platform Database schema by clicking the Create/Upgrade Database button.

Do not close the Configuration Tool at this point - further tasks are to be performed.
* Execute the Platform Server session creation script.
  • You can find it in the Deployment Controller Server under the Outsystems Platform Server Installation directory, in db\session_oracle_creation.sql.
  • This allows you to configure the tablespace, the tablespace's datafile location, the user and password. By default, the objects are set to:
    • Tablespace: OSSTATE
    • User: OSSTATE
  • If you change any of these settings, remember to do so throughout the file.
  • Run this script like you did with the script to create the data model of the OutSystems Platform.
* Execute the Platform Server session creation script.
  • You can find it in the Deployment Controller Server under the Outsystems Platform Server Installation directory, in db\RDS_session_oracle_creation.sql.
  • This allows you to configure the tablespace, the tablespace's datafile location, the user and password. By default, the objects are set to:
    • Tablespace: OSSTATE
    • User: OSSTATE
  • If you change any of these settings, remember to do so throughout the file.
  • Run this script like you did with the script to create the data model of the OutSystems Platform.
* Configure Platform Server settings with the Configuration Tool
- Session State Database


Configure the Platform Session Database (Session tab):
  • Set the Oracle database to be used by configuring the Database Section.
    The configuration process for this Database is the same used in the Platform Database
  • Configure the User, Password and Tablespace with the session database login and the session tablespace previously created
  • Press the Test Login button to confirm that the settings are correct
  • Create the Session Database schema by clicking the Configure Session Database button.

Do not close the Configuration Tool at this point - further tasks are to be performed.
* Configure Platform Server settings with the Configuration Tool
- Session State Database


Configure the Platform Session Database (Session tab):
  • Set the MySQL database to be used by configuring the Server field:
    • Set the MySQL server to be used by configuring the Server field:
      • You can use either the DNS name or the IP of the database although DNS name is recommended for the server
      • Examples: mysqlserver
    • Set the MySQL schema to be used by configuring the Schema field:
    • Configure the User, Password with the session database login previously created
    • Press the Test Login button to confirm that the settings are correct
    • Create the Session Database schema by clicking the Configure Session Database button.

    Do not close the Configuration Tool at this point - further tasks are to be performed.
* Make sure the database catalog recovery model is set to Simple. Check How to Set the Catalog Recovery Model.
* Configure Platform Server settings with the Configuration Tool
- Platform Database


Start the Configuration Tool (Start -> Programs -> OutSystems -> Administration Tools).

Configure the Platform Database (Database tab):
  1. In the Database Provider drop-down list, choose SQL Server
  2. Configure Server and Database fields:
    • Server is the name or IP of the database server, and instance or TCP port indication if it is the case.
      Examples: localhost, 192.168.1.2, srvdatabase\CORP, 10.10.10.01,1433
    • Database is the name of the database catalog created to be used by the Platform Server.
      Example: outsystems
      Note: if a catalog with the same name exists in the database, it will be re-used. If it does not exist, it will be created with the Latin1_General_CI_AI collation.
  3. Select Database Authentication as the Database Authentication
    Note: if you prefer using Windows users and passwords, please select Windows Authentication as the database authentication mechanism on the top of this document to update the checklist content.
  4. Select Windows Authentication as the Database Authentication
    Note: if you prefer using SQL Server users and passwords, please review this checklist's selections in the top of this document to update the checklist content.
  5. Select the Admin user:
    • Fill in the User and Password fields in the Admin section.
      -> the Admin user must be an existing and valid domain user. The password is needed to configure the identity for the OutSystems Deployment services. This user will be granted local administrator permission (to deploy new applications and manage the IIS) and Database owner privileges (to create and upgrade the applications database models).
  6. Select the Runtime user:
    • Fill in the User and Password fields in the Runtime section.
      -> the Runtime user must be an existing and valid domain user. The password is needed to configure the identity for the OutSystems application pool and some OutSystems services. This user will have restricted local permissions (to execute applications) and Database read & update privileges.
  7. Select the Log user:
    • Fill in the User and Password fields in the Log section.
      -> the Log user must be an existing and valid domain user. The password is needed to configure the identity for the OutSystems Log service. This user will have limited database read & update privileges.
  8. Click the Grant Permissions button. This will create the database catalog (if it does not exist) , create the users you indicated (if they do not exist), and grant the needed permissions for the Platform Admin, Platform Runtime and Platform Log roles.
    -> To do this, the Configuration Tool may prompt you to provide a database login with permissions to create a new database.
    For example, you can use the credentials of the sa user.
  9. Create the Platform Database schema by clicking the Create/Upgrade Database button.

Do not close the Configuration Tool at this point - further tasks are to be performed.
* Configure Platform Server settings with the Configuration Tool
- Session State Database


Configure the Platform Session Database (Session tab):
  1. Configure Server and Database fields:
    • Server is the name or IP of the database server, and instance or TCP port indication if it is the case.
      Examples: localhost, 192.168.1.2, srvdatabase\CORP, 10.10.10.01,1433
      You can use the same database server you used in the Database tab, or you can use another server.
    • Database is the name of the database catalog to store the Session Database model.
      This catalog cannot be the same as the one configured in the Database tab.
      Example: ASPStateOS
      Note: if a catalog with the same name exists in the database, it will be re-used. If it does not exist, it will be created.
  2. Choose the credentials for the Session user:
    • Fill in the User and Password fields in the Session section.
      A user will be created, with these credentials, in the next step.
  3. Click Configure Session Database. This will create the database catalog (if it does not exist) , create the login you indicated (if it does not exist), and grant the needed permissions to the user. If the catalog already exists, it will be updated.
    -> To do this, the Configuration Tool may prompt you to provide a database login with permissions to create a new database.
    For example, you can use the credentials of the sa user.

Do not close the Configuration Tool at this point - further tasks are to be performed.
If there is a SMS Gateway, access Gateways tab in the Platform Server Configuration Tool, and configure its parameters. For more details, refer to the SMS Gateway role of this checklist.
If the front-end being configured has more than one network card, and if the Controller server can only communicate with this front-end on one of the network cards, you need to change a setting in the Configuration Tool to specify which IP will be used by the Controller to communicate with the front-end. To do this:
  • Access the Network tab in the Configuration Tool;
  • Under Front-End Registration, choose the IP which the Controller will use to communicate from the Local IP Address drop-down. If you don't see the IP there, you can type it manually.
* In the Platform Server Configuration Tool, Controller tab, set the Deployment Controller Server IP address or host name.
* Click the Apply and Exit button on the Configuration Tool.
  • Answer Yes if a popup shows up asking to start the Outsystems Scheduler Service and the Outsystems SMS Connector Service.
  • Answer No if a popup shows up asking to start the Outsystems Scheduler Service and the Outsystems SMS Connector Service.
  • A popup will be shown asking you to run the Service Center installation. Accept by clicking Yes.
* Stop and disable the OutSystems Deployment Service.
Disable the OutSystems SMS Connector Service and the OutSystems Scheduler Service.
* Export the configuration file, for use in the front-ends

In the Platform Server Configuration Tool, export the configuration file by using File -> Export configuration...
Save the file in a convenient location.
Exit the Configuration Tool by clicking File -> Exit.
* Import the configuration file

In the Platform Server Configuration Tool, import the configuration file by using File -> Import configuration... and choosing the appropriate file, exported from the Deployment Controller server.

Confirm the IP which will be used to register the front-end with the controller:
  • Access the Network tab in the Configuration Tool;
  • Under Front-End Registration, if the Local IP Address option is not set as (automatic), confirm that the IP address belongs to the machine where the Configuration Tool is being run. If needed, fix this by choosing an IP address from the drop-down, choosing (automatic) or typing it manually.
  • If the front-end being configured has more than one network card, and if the Controller server can only communicate with this front-end on one of the network cards, choose the IP which the Controller will use to communicate from the Local IP Address drop-down. If you don't see the IP there, you can type it manually.

* Apply the Configurations
  • Fill in the Password field in the Admin section.
  • Click the Apply and Exit button on the Configuration Tool.
    • Answer Yes if a popup shows up asking to start the Outsystems Scheduler Service and the Outsystems SMS Connector Service.
    • Answer No when a popup asks you to run the Service Center installation.
* Disable the OutSystems Deployment Controller Service
* Install Development Environment:
  • Run the installation file DevelopmentEnvironment-M.m.b.r.exe and follow the on screen installation instructions

Legend: * Mandatory; Optional.

* Follow the Kannel's official installation instructions to install and configure Kannel 1.4.3. It is recomended to use pre-compiled binary packages.
Configure Kannel to forward incoming SMSs (Mobile originated SMSs) to the Platform Server:
  • In the Kannel machine, go to the Kannel's installation directory;
  • Locate the 'kannel.conf' file and edit it;
  • Under the sms-service group (line started with group = sms-service) create or Update 'get-url' property to: "http://<Platform Server Front-End IP>/dispatcher/dispatch.aspx?message=%a&from=%p&to=%P&bin=%b&coding=%C&udh=%u&sent=%t";
  • Save the file and exit;
  • If the Kannel is running, restart it to reload the new configuration.

Legend: * Mandatory; Optional.

Post-installation check list

In this section you have a list of all the steps that you check after installing OutSystems software.

OutSystems Platform Server

After installing OutSystems Platform Server, check the following topics.

Amazon RDS High-availability:
  • If you want to have High-availability (Multi-AZ via Mirroring) in your RDS, you must enable it after the execution of the Configuration Tool. This is done via AWS Management Console -> Instance actions -> Modify.
* Check if the following services are started and their startup type is set to Automatic:
  • OutSystems Deployment Controller Service
  • OutSystems Deployment Service
  • OutSystems Log Service
  • OutSystems Scheduler Service
  • OutSystems SMS Connector Service
* Check if only the following OutSystems services are enabled:
  • OutSystems Deployment Controller Service
  • OutSystems Log Service
* Check if only the following OutSystems services are enabled:
  • OutSystems Deployment Service
  • OutSystems Scheduler Service
  • OutSystems Log Service
  • OutSystems SMS Connector Service
* Upload your license:
  • Log in to Service Center using your administrator credentials (http://<yourserver>/ServiceCenter)
    • NOTE: By default, the administrator credentials are admin/admin. It is advisable to change it once logged in to Service Center.
  • Go to the licensing screen (Administration -> Licensing)
  • Click Upload New License and select the .lic file you got from the OutSystems Network
  • If you don't have a license file, click the Request New License and follow the instructions
* Configure Service Center:
  • Launch Service Center, log on as user admin, password admin and go to Administration -> Environment Configuration
  • Set the environment's Hostname
  • Set the environment's Running mode to Development or Production
  • Press the Apply button
* Install System Components:
  • Log in to Service Center using your administrator credentials (http://<yourserver>/ServiceCenter)
  • Go to the solutions screen (Factory -> Solutions)
  • Click Upload and Publish a Solution and select the System_Components.osp file in the installation directory (e.g.: C:\Program Files\OutSystems\Platform Server\)
  • Click 1-Click Publish, or Prepare Publish if you have 2-Stage deployment active.
NOTE: After the solution is published, it is advisable to run the Users application (http://<yourserver>/Users), log in as administrator (username and password are admin), and change the default password.
* LifeTime - only available for the Enterprise Edition:

LifeTime should only be installed in a dedicated environment. Installing it in more than one environment may lead to erroneous behaviors.

If you are applying this checklist to LifeTime environment, continue with the following procedures. Otherwise skip this step.

Read the LifeTime Installation and Configuration Tech Note to learn more.

Execute this step to install LifeTime in this environment:
  • Log in to ServiceCenter using your administrator credentials (http://<yourserver>/ServiceCenter)
  • Go to the solutions screen (Factory -> Solutions)
  • Click Upload and Publish a Solution and select the LifeTime.osp file in the Platform Server installation directory (e.g.: C:\Program Files\OutSystems\Platform Server\).
  • Click 1-Click Publish, or Prepare Publish if you have 2-Stage deployment active.
  • Log in to LifeTime to set up your infrastructure (http://<yourserver>/lifetime)
SEO Friendly URLs:

If you will be using the SEO Friendly URLs feature, you need to install it at this point.
Detailed instructions can be found in www.outsystems.com/goto/install-seo

Registration in SAP System Landscape Directory:
  • Install SAP SLD Registration. You can download it here.
  • Log in to http://<yourserver>/SAP_SLD_Registration using your administration credentials.
  • Fill in your own SAP SLD Details and press the Register button.
NOTE: This step is only required if you are going to integrate the OutSystems Platform with your SAP.
Integration with iDB2 databases:
  • Install IBM iAccess. You can download it here.
NOTE: This step is only required if you are going to integrate the OutSystems Platform with your IBM iDB2 database.
Business Activity Monitoring:
  • Install Business Activity Monitoring this.Version.ToString(). You can download it here.
NOTE: If you are using Business Process Technology, the installation of Business Activity Monitoring this.Version.ToString() is highly recommended.

Legend: * Mandatory; Optional.

For External Delivery Report (DLR) Storage follow Kannel Documentation.

If your are using the DLR Storage over databases, it is recommended that you create an index on the 'dlr' table with the columns corresponding to the fields 'smsc' and 'timestamp'.

* Make sure Kannel is running as a service and is set to start automatically. Check your Operationg System manual how to configure a service.
To customize the integration with Kannel, follow the OutSystems Technical note Third-party SMS gateway integration.

Legend: * Mandatory; Optional.

Platform Server Release Upgrade Steps

This section provides the steps that you must follow in order to successfully upgrade the OutSystems Platform Server with a new software release. This happens when the Major, Minor or Build number changes (M.m.b.r).

The mandatory topics are the ones that must be checked in order to have a certified installation, i.e. consist in the requirements necessary to guarantee that OutSystems supports your installation. The mandatory topics are in red and the icon associated is *. On the other hand, the optional topics are only recommended and you are not forced to check them. The optional topics are in plain text and the icon associated is .

Platform Server Revision Update Steps

This section provides the steps that you must follow in order to successfully update the OutSystems Platform Server with a new software revision. This happens when the Major, Minor and Build numbers are the same, but the Revision number changes (M.m.b.r). Whenever a new revision is issued, the previous one must be considered deprecated and unsupported.

The steps sequence for the Front-end Server profile should be applied in each one of the Front-end Servers.

When upgrading your OutSystems Platform from 6.0 or earlier, you must upgrade to the latest revision of OutSystems Platform 8.0, and only then upgrade to P9.

Description Server
* Microsoft .NET Framework 4.5.1

Deployment Controller Server

Front-end Server

* Backup configuration files:
  • Copy all the OutSystems services configuration files (files with extension .exe.config) located in the OutSystems Platform Server installation folder to a backup directory
  • Copy the OutSystems Configuration File (server.hsconf) to a backup directory
  • Copy the .NET Framework 4 configuration files machine.config and web.config from folder %WINDIR%\Microsoft.NET\Framework\v4.0.30319\CONFIG %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\CONFIG to a backup directory

Deployment Controller Server

Front-end Server

* Install the new Development Environment release:
  • Run the installation file DevelopmentEnvironment-M.m.b.r.exe and follow the on screen installation instructions

Deployment Controller Server

* Install the new OutSystems Platform Server release:
  • Run the installation file PlatformServer-M.m.b.r.exe and follow the on screen installation instructions

Make sure you select the folder where the previous version was installed

Deployment Controller Server

Front-end Server

* Upgrade the Platform Server settings with the Configuration Tool

Upgrade the Platform Database (Database tab):
  • Fill in the Password field in the Admin section.
  • Press the Create/Upgrade Database button.

Do not close the Configuration Tool at this point - further tasks are to be performed.

Deployment Controller Server

Upgrade the Platform Server settings with the Configuration Tool

Upgrade the Platform Session Database (Session tab):
  • Press the Configure Session Database button.
    -> To do this, the Configuration Tool may prompt you to provide a database login with permissions to create a new database.
    For example, you can use the credentials of the sa user.

    Note: during this process, all current sessions will be terminated.

Do not close the Configuration Tool at this point - further tasks are to be performed.

Deployment Controller Server

* Upgrade the Platform Server settings with the Configuration Tool

Save the configuration by pressing the Apply and Exit button.
  • Answer No if a popup shows up asking to start the Outsystems Scheduler Service and the Outsystems SMS Connector Service.
  • Answer No when a popup asks you to run the Service Center installation.

Deployment Controller Server

* Update the configuration settings with the Configuration Tool

  • Open the Platform Server Configuration Tool and press the Apply and Exit button.
  • Open the Platform Server Configuration Tool and fill in the Password field in the Admin section.
  • Leave by pressing the Apply and Exit button.
  • Answer No if a popup shows up asking to start the Outsystems Scheduler Service and the Outsystems SMS Connector Service.

Front-end Server

* Install Service Center:

  • Open the Platform Server Configuration Tool
    and fill in the Password field in the Admin section
    .
  • Leave the Configuration Tool by pressing the Apply and Exit button.
  • Answer Yes if a popup shows up asking to start the Outsystems Scheduler Service and the Outsystems SMS Connector Service.
  • Answer Yes when a popup asks you to run the Service Center installation.
  • Check Service Center availability by launching [Start] > Programs > OutSystems > Service Center

Deployment Controller Server

* Configure OutSystems Platform:
  • Start the Outsystems Scheduler Service and the Outsystems SMS Connector Service.

Front-end Server

* Upload your license:
  • Log in to Service Center using your administrator credentials (http://<yourserver>/ServiceCenter)
  • Go to the licensing screen (Administration -> Licensing)
  • Click Upload New License and select the .lic file you got from the OutSystems Network
    • NOTE: You tipically will need a new license file. If you don't have a license file or need a new one, click the Request New License and follow the instructions

Front-end Server

* Install System Components:

The upgrade of System Components should be done in the development environment with developer's supervision. If you already have the System_Components deployed and customized, you will need to merge your customized version with the System_Components.osp file in the Platform Server installation directory (e.g.: C:\Program Files\OutSystems\Platform Server\).

Update System Components:

  • Log in to Service Center using your administrator credentials (http://<yourserver>/ServiceCenter)
  • Go to the solutions screen (Factory -> Solutions)
  • Click Upload and Publish a Solution and select the System_Components.osp file in the Platform Server installation directory (e.g.: C:\Program Files\OutSystems\Platform Server\)
  • Click 1-Click Publish, or Prepare Publish if you have 2-Stage deployment active.
NOTE: After the solution is published, it is advisible to run the Users application (http://<yourserver>/Users), log in as administrator (username and password are admin), and change his password.

Front-end Server

* LifeTime - only available for the Enterprise Edition:

LifeTime should only be installed in a dedicated environment. Update it before the others.

Installing LifeTime in more than one environment may lead to erroneous behaviors.

If you are applying this checklist to LifeTime environment, continue with the following procedures. Otherwise skip this step.

Read the LifeTime Installation and Configuration Tech Note to learn more.

Execute this step to install LifeTime in this environment:
  • Log in to ServiceCenter using your administrator credentials (http://<yourserver>/ServiceCenter)
  • Go to the solutions screen (Factory -> Solutions)
  • Click Upload and Publish a Solution and select the LifeTime.osp file in the Platform Server installation directory (e.g.: C:\Program Files\OutSystems\Platform Server\).
  • Click 1-Click Publish, or Prepare Publish if you have 2-Stage deployment active.
  • Log in to LifeTime to set up your infrastructure (http://<yourserver>/lifetime)

Front-end Server

SEO Friendly URLs:

If you will be using the SEO Friendly URLs feature, confirm that SEO Friendly URLs have been installed.
Detailed instructions can be found in www.outsystems.com/goto/install-seo

Front-end Server

Business Activity Monitoring:
  • Install Business Activity Monitoring this.Version.ToString(). You can download it here.
NOTE: If you are using Business Process Technology, the installation of Business Activity Monitoring this.Version.ToString() is highly recommended.

Deployment Controller Server

* Republish all the eSpaces.

This is needed to update the eSpaces so they use the corrections and improvements from the new version.
In a production environment, this should be done with developer supervision. Typically, a solution with all the eSpaces should be used.

NOTE: Be aware to not overwrite the System Components extensions and eSpaces if your factory already includes some of these components.

Deployment Controller Server

Legend: * Mandatory; Optional.

Tuning and Security Check list

In this section you have a list of issues that you should check in a production environment. These issues are useful to improve the performance and security of your system.

Tuning your systems

Check the following issues to improve the performance of your system.

* Configure Process Scheduling and Virtual Memory:
  1. In the Start menu, right-click My Computer and choose Properties.
  2. In the left pane, click Advanced system settings and confirm that the Advanced tab is selected.
  3. On the Performance group, click on Settings button.
  4. Click on the Advanced tab and:
    1. On Processor scheduling group, check Background services option. With this setting, all the programs receive the same amount processor resources.
    2. On Virtual Memory group, click on Change button:
      • Uncheck Automatically manage paging file size for all drives.
      • Select the Custom size option.
      • Confirm the value recommended by Windows (Recommended:, in the Total paging file size for all drives group).
      • Set both the Initial size (MB) and Maximum Size (MB) parameters with the same value as the one collected in the above bullet.
      • In the Drives list, choose one that has enough free disk space. If in doubt, use C:. After that, click Set, and exit this dialog.
      • This setting will avoid page size fragmentation and I/O bottleneck.
    3. Click on Data Execution Prevention tab:
      • If a warning is presented stating that Your computer's processor does not support hardware-based DEP, you may consider selecting Turn on DEP for essential Windows programs and services only.
    4. Click the OK button.

You might need to restart the server after these changes.

* Tuning Internet Information Services
- Configure unlimited connections


Open Server Manager. In the left tree, select Roles, choose Web Server (IIS) and then Internet Information Services (IIS) Manager. If you don't see an entry here, access this utility under Start > Run, and type inetmgr.msc.

  1. Expand <servername> > Sites > Default Web Site, and then click Default Web Site.
  2. In the right pane, under Manage Web Site > Configure, click Limits...
  3. Make sure that the Limit number of connections checkbox is unchecked.
  4. Click the OK button.

Do not close the IIS Manager at this point - further tasks are to be performed.
* Tuning Internet Information Services
- Configure unlimited connections


Open Server Manager and, in the top menu, under Tools, select Internet Information Services (IIS) Manager.

  1. Expand <servername> > Sites > Default Web Site, and then click Default Web Site.
  2. In the right pane, under Manage Web Site > Configure, click Limits...
  3. Make sure that the Limit number of connections checkbox is unchecked.
  4. Click the OK button.

Do not close the IIS Manager at this point - further tasks are to be performed.
* Tuning Internet Information Services
- Configure upload size limits


These steps might require elevated privileges. We recommend saving a backup of them on a different location before any edits.
  • Edit with Notepad your %WINDIR%\Microsoft.NET\Framework\v4.0.30319\CONFIG\machine.config %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\CONFIG\machine.config file:
    1. Locate the <system.web> section
    2. In the <httpRuntime> element, set the maxRequestLength attribute to:
          - 32768 (for small factory environments),
          - 65536 (medium sized factory environments)
          - 131072 (large factory environments).
      These values are in KBytes. If sould leave all other parameters untouched and end up with something similar to:
          <httpRuntime executionTimeout="110" maxRequestLength="131072" />
  • Edit with Notepad your %WINDIR%\system32\inetsrv\config\applicationHost.config file:
    1. Locate the <system.webServer> tag. Make sure it is not one that is preceeded by a <location> tag in the previous line. Its full path should be <configuration>\<system.webServer>
    2. Within the <system.webServer> section, locate the <security> sub-section
    3. Find the <requestFiltering> sub-section
    4. Find the <requestLimits> element inside <requestFiltering>.
    5. In the <requestLimits> element, set the maxAllowedContentLength attribute to 33554432 (for small factory environments), 67108864 (medium sized factory environments) or 134217728 (large factory environments). This value is in Bytes. You should end up with something similar to <requestLimits maxAllowedContentLength="134217728" />
* Tuning Internet Information Services
- Configure worker process optimizations


Configure the worker process optimizations:
  1. Expand <servername> and click Application Pools
  2. In the middle pane, click OutSystemsApplications.
  3. In the right pane, under Edit Application Pool, click Recycling...
  4. Uncheck all checkboxes under Fixed Intervals group.
  5. Under Memory Based Maximums, uncheck Virtual memory usage (KB) and configure Private memory usage to be at most 60% of the total physical memory of the machine. Then click Next.
  6. Activate all the Runtime recycling events. These will provide additional information whenever worker process recycle - this information will be logged in Event Log.
  7. In the main window, in the right pane, under Edit Application Pool, click Advanced Settings.
  8. Under Process Model, set Idle Time-out (minutes) to 0 (zero). Exit by clicking OK.

Do not close the IIS Manager at this point - further tasks are to be performed.
* Tuning Internet Information Services
- Create Service Center Application Pool


Create and configure the Service Center Application Pool:
  1. Expand <servername> and click Application Pools
  2. In the right page, under Actions, click Add Application Pool...
  3. Give it a name of your choice (e.g. ServiceCenterAppPool), choose .NET version v4.0.30319 and Managed pipeline mode: Classic. Leave Start application pool immediately checked. Click the OK button.
  4. In the main window, expand <servername> > Sites > Default Web Site.
  5. Right-click ServiceCenter and then choose Manage Application > Advanced Settings.
  6. Under General, click Application Pool and then the button with ... on the right. Choose the application pool you just created, click OK, and then click OK again to close the dialog.
  7. Repeat steps 2-8 of the previous group (Configure worker process optimizations) for the Service Center Application Pool you have just created.
* Tuning Internet Information Services
- Create LifeTime Application Pool


Create and configure the LifeTime Application Pool:
  1. Expand <servername> and click Application Pools
  2. In the right page, under Actions, click Add Application Pool...
  3. Give it a name of your choice (e.g. LifeTimeAppPool), choose .NET version v4.0.30319 and Managed pipeline mode: Classic. Leave Start application pool immediately checked. Click the OK button.
  4. In the main window, expand <servername> > Sites > Default Web Site.
  5. Right-click lifetime and then choose Manage Application > Advanced Settings.
  6. Under General, click Application Pool and then the button with ... on the right. Choose the application pool you just created, click OK, and then click OK again to close the dialog.
  7. Right-click LifeTimeEngine and then choose Manage Application > Advanced Settings.
  8. Under General, click Application Pool and then the button with ... on the right. Choose the application pool you just created, click OK, and then click OK again to close the dialog.
  9. Right-click LifeTimeCore and then choose Manage Application > Advanced Settings.
  10. Under General, click Application Pool and then the button with ... on the right. Choose the application pool you just created, click OK, and then click OK again to close the dialog.
  11. Right-click LifeTimeMonitoring and then choose Manage Application > Advanced Settings.
  12. Under General, click Application Pool and then the button with ... on the right. Choose the application pool you just created, click OK, and then click OK again to close the dialog.
  13. Right-click LifeTimeSDK and then choose Manage Application > Advanced Settings.
  14. Under General, click Application Pool and then the button with ... on the right. Choose the application pool you just created, click OK, and then click OK again to close the dialog.
  15. Right-click PerformanceMonitor and then choose Manage Application > Advanced Settings.
  16. Under General, click Application Pool and then the button with ... on the right. Choose the application pool you just created, click OK, and then click OK again to close the dialog.
  17. Repeat steps 2-8 of the previous group (Configure worker process optimizations) for the LifeTime Application Pool you have just created.
SQL Server Tuning

Review your database settings according to the SQL Server Best Practices for Platform Server document.

Making your system more secure

Check the following issues to improve the security of your system.

Disabling SSLv3 to prevent POODLE Vulnerability.
  • Open regedit.exe

  • Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols\

  • Add a key named SSL 3.0
  • Under the SSL 3.0 key, add two keys named Client and Server
  • Under the Client key, add a DWORD Value named DisabledByDefault and set its value to 1
  • Under the Server key, add a DWORD Value named Enabled and set its value to 0

  • Under the SSL 2.0 key, add a key named Server
  • Under the Server key, add a DWORD Value named Enabled and set its value to 0

  • Restart the server

Legend: * Mandatory; Optional.

See Also

As mentioned in the above sections, you might need to: