Configuring an Application

Topics

● Configure Application Settings

○ Site Properties
○ Timers
○ Web References
○ Database Connections
Application Settings

When an application is deployed from one environment to another, the application

source code is compiled, generated and deployed in the destination environment

However, it is often that these applications have settings that are not part of the code
or are environment-specific, thus they are not deployed!

When deploying an application to another environment, it may be necessary to change

those application settings, according to the destination environment requirements

After the deployment to the destination environment, OutSystems allows to configure:

● Values of module parameters (site properties)
● Timer configuration parameters
● URL of consumed REST APIs and SOAP Web Services
● Connections for external databases and SAP systems
Configure Application Settings

These configurations are created and edited per environment, in Service Center

Changing the configurations of an application does not require republishing the

application, nor any downtime for the end-users
Site Properties

A site property is a persistent variable,

defined in the scope of a module, and
used for parameterization purposes

Site properties can be changed in logic, or

in Service Center. This may have
performance impacts!
● Invalidates the cache
● High impact on loads

A site property has:

● A default value used for initialization
purposes
● An effective value to override the default
○ Not propagated in the deployment!
Timers

A Timer is a schedulable asynchronous job, and are defined in the application modules

Timers execute application logic following a schedule, and are commonly used to
perform long-running tasks or heavy batch jobs that avoid peak hours

Each Front-end server, by default, can run 3 timers in parallel

Scheduler Front-end
Service
App 1
un
xtR Timer Email Process
Ne thread
App 2 thread thread

Timer Email Process

Timers
thread thread thread

App n Timer
queue
thread

Process
thread
Configuring Timers

Timers are configured per environment, in

Service Center

Effective Schedule defines when the

Timer is scheduled to run, and periodicity:
● Daily
● Weekly
● In a given day or weekday of a month
● When published

Priority value is used to prioritize timers

with same schedule, in the queue

Timeout value defines when the timer

execution times out
Web References

A Web Service that is invoked inside a module is called a Web Reference

The Web Reference endpoint may need to be different across environments, thus
requiring configuration after deployment

After deploying to another environment, the Effective URL may require revision by the
operations team

Development Web Reference

External System
OSModule Development

After the deployment, the Web Reference endpoint may need to change

Quality Web Reference

External System
OSModule Quality
Configuring Web References

Web References can be configured per

environment, in Service Center.

The Default URL is set up when the REST /

SOAP API method(s) call is defined in
Service Studio

The Effective URL can be changed in any

environment, regardless the default URL

Logging Levels defines information

logged in every API call: Default,
Troubleshoot or Full
Database Connections

OutSystems can easily integrate with external Oracle, SQL Server, MySQL and DB2
databases. To connect to those databases, a database connection must be configured
in each environment

Database connections may be different between environments, thus the connection may
require configuration after the deployment

Development
Database Connection
External DB
OSModule Development

After the deployment, the DB connection may need to change

Quality
Database Connection
External DB
OSModule Quality
Configuring Database Connections

With the database connection defined,

applications in the environment can read
and write data from the external database

This is done in Extension modules

created in Integration Studio

Logical databases defined in Extensions,

must be mapped to the respective
database connection in all environments

While deploying an application that

requires this configuration, LifeTime asks Logical name given
by the developer
the user to perform it, before continuing
Mapping to the DB
Connection
Configuring an Application
Thank You!
Demo!