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 upgrade your existing 4.2 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.

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 Application Server you'll be using on this machine:

JBoss Enterprise Application Platform 6.3

JBoss Community Application Server 7.1.1 Final

Oracle WebLogic 11g

Oracle WebLogic 12c

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

Linux Red Hat Server 6.X - 64 bit

Linux Red Hat Server 5.X - 64 bit

Linux CentOS 5.X - 64 bit

Linux CentOS 6.X - 64 bit

Oracle Linux 6.X - 64 bit

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

Please select which database software you'll be using:

Oracle Database

Oracle Database on Amazon RDS

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.

When installing without an Internet connection there may be dependency errors in packages required by the OutSystems Platform.
In this case, please download the dependencies from a machine with Internet connection, and then use the downloaded packages to install them in the target machine.
See the documentation for yumdownloader, which is a tool provided by the package yum-utils.


In order to follow this checklist, you will need credentials for the Red Hat Network. If you do not have them, please contact your IT before proceeding.

In order to follow this checklist, you will need credentials for the Oracle Network with a valid support identifier. If you do not have them, please contact your IT before proceeding.
* Amazon RDS dimension:
  • The minimum recommended size for a database instance is the medium size, that is, the Instance class should be at least "db.m1.medium". This is specified when you create the instance.
Amazon RDS time zones:
  • In order to have your infrastructure working with the OutSystems Platform, you need to have all front-ends using the same time zone than the database.
    You can set the RDS database time zone when you are creating the instance. For instance, you must have your front-ends using the same time zone you defined for the database.

    For more information about Amazon RDS time zones for Oracle check this page.
Amazon RDS time zones:
  • You must configure your front-end using the same time zone as the RDS.
Amazon RDS High-availability:
  • To choose the Multi-AZ option, you have to enable it while creating the database, in DB instance details, pick Yes for Multi-AZ deployment option. You can also change it in an existing Oracle RDS database in the AWS Management Console -> Instance actions -> Modify.
File System Partitions:
  • If you want to increase performance and stability of the OutSystems Platform, plan ahead the installation of the Operating System so that you will have two extra partitions available:
    • One partition for the OutSystems Platform installation
    • One partition for the JBoss Application Server
    • One partition for the WebLogic Application Server
* Register in Red Hat Network:
  • Go to Red Hat Network and login into your account.
  • If your System is not registered in Red Hat Network, register it by executing (as the root user) rhn_register.
  • Fill-in your server details, and go to Software / Software Channels and add these Entitlements (Repositories):
    • RHEL Server Supplementary (v. this.OperatingSystem.GetRepositoryVersion() 64-bit x86_64)
    • Red Hat JBoss EAP (v. this.ApplicationServer.GetRepositoryVersion()) for this.OperatingSystem.GetRepositoryVersion()Server x86_64
    • RHEL Third Party Oracle Java (v. this.OperatingSystem.GetRepositoryVersion() 64-bit x86_64)
* Red Hat Enterprise Linux 6.X x64: Red Hat Enterprise Linux 5.X x64: CentOS Linux 5.X x64: CentOS Linux 6.X x64: Oracle Linux 6.X x64:
  • As the root user, make sure the following packages are installed:
    • Shell
      • yum install bash
    • Communication (ssh shells)
      • yum install openssh-clients
    • Firewall (iptables)
      • yum install iptables
    • Utilities
      • yum install zip unzip ant
    • X server - only necessary to install Oracle Database Server tools.
  • Iptables configuration:
    • As the root user, set iptables service to auto-start:
      • chkconfig iptables on
    • As the root user, open the following ports:
      • 2033, 12000, 12001, 12002, 12003 - OutSystems Services default communication ports
      • 7001, 7002 - AdminServer default communication ports
      • 5556 - NodeManager default communication port
        • You can open a port in iptables by running the following command (as the root user):
        • iptables -I INPUT -p tcp --dport [PORT] -j ACCEPT
        • You can store the iptables settings permanently by running the following command (as the root user):
        • service iptables save
  • If you decide to install a different firewall follow these additional steps:
    • As the root user, set iptables service to not auto-start:
      • chkconfig iptables off
    • Set port redirection:
      • 8080 redirect to 80;
      • 8443 redirect to 443;
    • Open the following ports:
      • 8080, 8443 - JBoss default communication ports;
      • 8080, 8443 - WebLogic default communication ports;
      • All ports that must be open in iptables
Register in Red Hat Network:
  • Go to Red Hat Network at Red Hat Network and log in to your account.
  • If your System is not registered in Red Hat Network, register it by executing (as the root user) rhn_register.
  • Enter in your machine details, and go to Software / Software Channels and add these Entitlements (Repositories):
    • RHEL Supplementary (v. this.OperatingSystem.GetRepositoryVersion() 64-bit x86_64)
* 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
* Oracle 10g R2, 11g R2 or 12c R1 Services:
  • Make sure that Oracle services are running.
Install latest Oracle Database updates
* 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:
  • Linux: /usr/my.cnf

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.
* Install Sun's Java SDK (1.6 x64):
  • Please download from the official site:
    http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html.
  • As the root user, execute the installer: sh jdk-*-linux-x64-rpm.bin
    • Install Java into a location that is accessible by all users.
    • For the purpose of this document, we assume Java will be installed to /usr/java/jdk1.6.0_* folder.
  • Set Java version system wide. As the root user, execute:
    JAVA_HOME="/usr/java/`ls /usr/java/ | grep jdk1.6.0 | sort -t_ -n -k2 | tail -1`"
    mkdir -p /usr/lib/jvm
    alternatives --install /usr/bin/java java $JAVA_HOME/bin/java 16999
    alternatives --install /usr/lib/jvm/java-1.6.0 java_sdk_1.6.0 $JAVA_HOME/ 16999
  • Override the system wide java version. As the root user, execute:
    alternatives --set java $JAVA_HOME/bin/java
    alternatives --set java_sdk_1.6.0 $JAVA_HOME/
  • Confirm that the system wide java version is correct. As the root user, execute: alternatives --config java
    • You should see an output containing the path /usr/java/jdk1.6.0_*/bin/java selected.
* As the root user, install JRockit Java SDK (1.6 x64):
  • Please download from the official site:
    http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-jrockit-2192437.html.
  • As the root user, execute the installer: chmod a+x jrockit-jdk1.6.0_*-linux-x64.bin && ./jrockit-jdk1.6.0_*-linux-x64.bin
    • Install JRockit into a location that is accessible by all users.
    • For the purpose of this document, we assume JRockit will be installed to /usr/java/jrockit-jdk1.6.0_* folder.
  • Set Java version system wide. As the root user, execute:
    JAVA_HOME="/usr/java/`ls /usr/java/ | grep jrockit-jdk1.6.0 | sort -t_ -n -k2 | tail -1`"
    mkdir -p -m755 /usr/lib/jvm
    alternatives --install /usr/bin/java java $JAVA_HOME/bin/java 16999
    alternatives --install /usr/lib/jvm/java-1.6.0 java_sdk_1.6.0 $JAVA_HOME/ 16999
  • As the root user, override the system wide java version.:
    alternatives --set java $JAVA_HOME/bin/java
    alternatives --set java_sdk_1.6.0 $JAVA_HOME/
  • Confirm that the system wide java version is correct. As the root user, execute: alternatives --config java
    alternatives --config java_sdk_1.6.0
    • You should see an output containing the path /usr/java/jrockit-jdk1.6.0_*/bin/java selected.
  • Ensure that /usr/java has appropriate permissions. As the root user, execute: chmod 755 /usr/java
Workaround for WebLogic performance problems on low entropy systems
  • At this point, WebLogic has documented performance problems on low entropy systems performance problems on low entropy systems such as virtual machines.
    You can workaround this problem by changing the securerandom.source property on the file /etc/alternatives/java_sdk_1.6.0/jre/lib/security/java.security:
    securerandom.source=file:/dev/./urandom
    Make sure to include the path as it is written above, including the dot, as described in JDK bug 6521844.
    Note that this procedure reduces the security levels of your java applications.
* Install JBoss Application Server (7.1.1 Final):
  • Download the file jboss-as-7.1.1.Final.zip from the official site:
    http://www.jboss.org/jbossas/downloads/.
    • For the purpose of this document, we assume JBoss will be installed to /opt/jboss-as-7.1.1.Final folder.
  • As the root user, uncompress the JBoss installation file to /opt: unzip jboss-as-7.1.1.Final.zip -d /opt/
Mount JBoss in a separate partition:
  • If you have a partition reserved for the JBoss Application Server, move the directory /opt/jboss-as-7.1.1.Final/standalone to the alternate partition, and create a mount point to it at /opt/jboss-as-7.1.1.Final/standalone.
* Install WebLogic Application Server:
  • Please download the Oracle WebLogic Server 12.1.1 10.3.6 Generic Installer from the official site: http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html.
    • To find the correct Generic Installer, click the 'see all files' link next to the Oracle WebLogic Server version in the 'Oracle WebLogic Server Previous Releases' table.
  • As the root user, create a user for WebLogic and disable password ageing:
    useradd -s /bin/nologin -U wls_outsystems
    chage -m 0 -M 99999 -I -1 -E -1 wls_outsystems
  • As the root user, install WebLogic:
    mkdir -p /opt/Oracle/Middleware
    chown wls_outsystems:wls_outsystems /opt/Oracle/Middleware
    mv wls1211_generic.jar wls1036_generic.jar /home/wls_outsystems/
    su - wls_outsystems -s /bin/bash -c "umask 0027; $JAVA_HOME/bin/java -jar /home/wls_outsystems/wls1211_generic.jar" su - wls_outsystems -s /bin/bash -c "umask 0027; $JAVA_HOME/bin/java -jar /home/wls_outsystems/wls1036_generic.jar"
    • Enter the Middleware Home /opt/Oracle/Middleware
      • For the purpose of this document we'll use the Middleware Home suggested above.
      • WebLogic in every front-end must be installed in the same path as WebLogic in the Controller.
    • Register for Security Updates, depending on your needs.
    • Choose a Typical Installation.
    • Choose the JRockit you've previously installed, as JDK
    • Confirm the Product Installation Directories, and Confirm that you want to install them.
* Install required WebLogic patches:
  • As the root user, check if you have patches 14617042(65WQ), 15921652(2QP1) and 18123824(M61X) applied to your WebLogic, by running the following code and looking for the Patch ID of the installed patches: su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -status=applied -verbose -view; popd"
  • If you do not have all mentioned patches, please download patch 14617042(65WQ), patch 15921652(2QP1) and patch 18123824(M61X) for Oracle WebLogic 10.3.6 from the official Oracle Support site.
  • As the root user, install the patch by following the instructions in the README.txt file that comes with the patch: mv p14617042_1036_Generic.zip p15921652_1036_Generic.zip p18123824_1036_Generic.zip /home/wls_outsystems/
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p14617042_1036_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p15921652_1036_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p18123824_1036_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -patchlist=65WQ,2QP1,M61X -install; popd"
* Install required WebLogic patches:
  • As the root user, check which patches are applied to your WebLogic, by running the following code and looking for the Patch ID of the installed patches: su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -status=applied -verbose -view; popd"
  • If you have the patch 17170980(6LUU), as the root user, uninstall the patch by running the following code: su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -patchlist=6LUU -remove; popd"
  • If you do not have the patches 15857413(F3LX), 16196081(33VQ), 16578101(JXFY), 16196750(R79R), 18679737(ZNIQ), 15921652(KS83) and 18123824(SCT9) applied to your WebLogic, please download patch 15857413(F3LX), patch 16196081(33VQ), patch 16578101(JXFY), patch 16196750(R79R), patch 18679737(ZNIQ), patch 15921652(KS83) and patch 18123824(SCT9) for Oracle WebLogic 12.1.1 from the official Oracle Support site.
  • As the root user, install the patch by following the instructions in the README.txt file that comes with the patch: mv p15857413_12110_Generic.zip p16196081_12110_Generic.zip p16578101_12110_Generic.zip p16196750_12110_Generic.zip p18679737_12110_Generic.zip p15921652_12110_Generic.zip p18123824_12110_Generic.zip /home/wls_outsystems/
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p15857413_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p16196081_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p16578101_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p16196750_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p18679737_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p15921652_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p18123824_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -patchlist=F3LX,33VQ,JXFY,R79R,ZNIQ,KS83,SCT9 -install; popd"
* Creating a WebLogic domain for OutSystems:
  • As the root user, execute the following instructions:
    su - wls_outsystems -s /bin/bash -c "/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/common/bin/config.sh"
    • Welcome: choose the "Create a new WebLogic domain" option.
    • Select Domain Source: choose the "Choose WebLogic Platform components" option.
    • Application Template Selection: choose the "Basic WebLogic Server Domain" option.
    • Edit Domain Information: enter outsystems_domain as the domain name.
    • Select the target domain directory for this domain: Use the default /opt/Oracle/Middleware/user_projects/domains as the domain directory.
      • For the purpose of this document we'll use the domain name and default domain directory as suggested above.
    • Configure Administrator User Name and Password: enter the name and credentials for the WebLogic Administrator account. OutSystems Platform will require these credentials later on:
      • Choose an appropriate Name for the Administrator account. For more info about this, please check the WebLogic best practices document, at the bottom of this page.
      • Choose a password
      • Confirm the user password
    • Domain Mode Configuration: select Production Mode as the domain mode configuration, both for Production and Non-Production environments.
    • Java SDK Selection: choose the JRockit you've previously installed
    • Select Optional Configuration: uncheck "Administration Server", check "Managed Servers, Clusters and Machines", uncheck "RDBMS Security Store"
    • Configure Managed Servers:
      • Enter an appropriate Name for the Managed Server
        • Suggestion: Use the server hostname as the Managed Server name.
      • Leave All Local Addresses as the Listen Address
      • Enter 8080 as the Listen Port
      • If you enable SSL, enter 8443 as the SSL listen port
    • Configure Clusters: don't do anything and proceed to the next step.
    • Configure Machines:
      • Enter an appropriate Name for the Machine
        • Suggestion: Use the server hostname appended with _machine as the Machine name.
      • Enter the Machine IP as the Node Manager listen address
      • Leave 5556 as the Node Manager listen port
    • Configure Unix Machine: don't do anything and proceed to the next step.
    • Assign the previously created Managed Server to the Machine you've created previously
      • Enter the number that identifies the Machine (typically 1.1)
      • Choose the Select option
      • Choose the Managed Server created earlier and accept it
Workaround for NodeManager SSL configuration:
  • By default, WebLogic configures the Node Manager to operate over SSL, which means that the Node Manager host must have a valid certificate and that the Administration Server needs to trust that certificate before being able to communicate with that Node Manager.

    OutSystems strongly recommends that you properly configure your SSL certificates. For more information on how to configure certificates between the Node Managers and the Administration Server, please see http://docs.oracle.com/cd/E23943_01/doc.1111/e15483/node_manager.htm http://docs.oracle.com/cd/E24329_01/web.1211/e24422/ssl.htm#SECMG384 .

    If you are sure that you do not want to configure SSL certificates between the Node Managers and the Administration Server you can manually disable it.

    Note that this procedure reduces the security level of the communication between Node Managers and Administration Server

    As the root user, execute:
    • Start NodeManager:
      su - wls_outsystems -s /bin/bash -c "/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/server/bin/startNodeManager.sh"
    • Wait until the output says "listener started on port 5556" and press Ctrl+C.
    • Disable NodeManager secure listener:
      su - wls_outsystems -s /bin/bash -c "sed -i.bak s/SecureListener=true/SecureListener=false/g /opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/common/nodemanager/nodemanager.properties 2>&1 > /dev/null"
    • Start WebLogic:
      su - wls_outsystems -s /bin/bash -c "/opt/Oracle/Middleware/user_projects/domains/outsystems_domain/bin/startWebLogic.sh"
    • Open the WebLogic console at http://<AdministrationServer>:7001/console
      • Click the Lock & Edit button
      • Go to the outsystems_domain and expand Environment
      • Click on Machines
      • Select the machine associated with the node you are configuring
      • Click on the Node Manager tab
      • Change Type to Plain
      • Save and Activate Changes
    • Stop WebLogic:
      su - wls_outsystems -s /bin/bash -c "/opt/Oracle/Middleware/user_projects/domains/outsystems_domain/bin/stopWebLogic.sh"
* Preparing to extend the outsystems_domain - Making an outsystems_domain template file
  • As the root user, execute the following line to pack your domain's template using the wls_outsystems user su - wls_outsystems -s /bin/bash -c "/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/common/bin/pack.sh -domain=/opt/Oracle/Middleware/user_projects/domains/outsystems_domain -managed=true -template=/home/wls_outsystems/outsystems_domain.jar -template_name=outsystems_domain"
  • This template will be used later by each Front-End.
* Extending the existing outsystems_domain - Unpacking the Domain's template
  • As the root user, copy the outsystems_domain.jar template file available from the Administration Server host to the Front-End server.
    • Check The Controller's checklist Instructions, on how to generate this file, if you haven't done it yet.
  • As the root user, execute the following line to unpack your domain's template using the wls_outsystems user: mv outsystems_domain.jar /home/wls_outsystems/
    chown wls_outsystems:wls_outsystems /home/wls_outsystems/outsystems_domain.jar
    su - wls_outsystems -s /bin/bash -c "/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/common/bin/unpack.sh -domain=/opt/Oracle/Middleware/user_projects/domains/outsystems_domain -template=/home/wls_outsystems/outsystems_domain.jar"
* Extending the existing outsystems_domain - Registering a new Front-End:
  • At this stage you'll need an Admininstration Server running and reachable from the Front-End. Please complete the Controller's checklist prior to this step, if you have not done it yet.
  • Creating a Machine and Managed Server in the AdminServer's console:
    • Open the WebLogic console at http://<AdministrationServer>:7001/console
      • Click the Lock & Edit button
      • Go to the outsystems_domain and expand Environment
      • Click on Machines
      • Create a new Machine:
        • Enter an appropriate Name for the Machine
          • Suggestion: Use the server hostname appended with _machine as the Machine name.
        • Select the appropriate Node Manager Type (SSL or Plain, consistent with the rest of your environment)
        • Enter the Machine IP as the Node Manager listen address
        • Leave 5556 as the Node Manager listen port
        • Press the Finish button
      • Create a new Server:
        • Enter an appropriate Name for the Server
          • Suggestion: Use the server hostname as the Managed Server name.
        • Leave the Listen Address empty
        • Enter 8080 as the Server Listen Port
        • Press the Finish button
        • Click on the newly created Server
        • Click on the newly created Server
        • Associate the server with the machine created just before
        • Enable SSL Listen Port and enter 8443 as the SSL Listen Port
        • Save and Activate Changes
Workaround for NodeManager SSL configuration:
  • By default, WebLogic configures the Node Manager to operate over SSL, which means that the Node Manager host must have a valid certificate and that the Administration Server needs to trust that certificate before being able to communicate with that Node Manager.

    OutSystems strongly recommends that you properly configure your SSL certificates. For more information on how to configure certificates between the Node Managers and the Administration Server, please see http://docs.oracle.com/cd/E23943_01/doc.1111/e15483/node_manager.htm http://docs.oracle.com/cd/E24329_01/web.1211/e24422/ssl.htm#SECMG384 .

    If you are sure that you do not want to configure SSL certificates between the Node Managers and the Administration Server you can manually disable it.

    Note that this procedure reduces the security level of the communication between Node Managers and Administration Server

    As the root user, execute:
    • Start NodeManager:
      su - wls_outsystems -s /bin/bash -c "/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/server/bin/startNodeManager.sh"
    • Wait until the output says "listener started on port 5556" and press Ctrl+C.
    • Disable NodeManager secure listener:
      su - wls_outsystems -s /bin/bash -c "sed -i.bak s/SecureListener=true/SecureListener=false/g /opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/common/nodemanager/nodemanager.properties 2>&1 > /dev/null"
Mount WebLogic in a separate partition:
  • If you have a partition reserved for the WebLogic Application Server, move the directory /opt/Oracle/Middleware to the alternate partition, and create a mount point to it at /opt/Oracle/Middleware.

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.

* If until now you have not installed OutSystems Platform in your Deployment Controller Server you should follow the Deployment Controller Server checklist up until the point where you are instructed to resume the current checklist. You can access the Deployment Controller Server checklist in this document by selecting the Deployment Controller Server role at the top of this page.
* Install the OutSystems yum repository:
  • As the root user, execute: rpm -i http://yum.outsystems.net/this.Version.ToString()/noarch/outsystems-repo.rpm
    • To install a package without internet connection, download the rpm from the above location, and then execute (as root user): rpm -i outsystems-repo.rpm
* Install Deployment Controller Server and/or Front-end Server:
  • As the root user, execute: yum install outsystems-agileplatform-jboss6-eap yum install outsystems-agileplatform-jboss7-community yum install outsystems-agileplatform-weblogic
    • To install a package without internet connection, download the latest rpms outsystems-agileplatform-*.noarch.rpm outsystems-agileplatform-libs-*.noarch.rpm outsystems-agileplatform-jboss6-eap-*.noarch.rpm outsystems-agileplatform-jboss7-community-*.noarch.rpm outsystems-agileplatform-weblogic-*.noarch.rpm from the "OutSystems yum repository", and then execute (as root user): yum --disablerepo=* install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* install outsystems-agileplatform-*.noarch.rpm
    yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm
  • The OutSystems Platform Server files will be installed to /opt/outsystems/platform.
  • Copy the Controller's /etc/outsystems/server.hsconf to the same location on each Front-End Server.
* Enable weblogic-outsystems-adminserver service:
  • As the root user, execute: chkconfig --levels 345 weblogic-outsystems-adminserver on
    • OutSystems Platform requires the AdminServer to be available.
      OutSystems recommends to enable the weblogic-outsystems-adminserver service in the deployment controller node, as it will automatically start and stop the AdminServer whenever required.
Mount JBoss in a separate partition:
  • If you have a partition reserved for the JBoss Application Server, move the directory /var/lib/jbossas/standalone to the alternate partition, and create a mount point to it at /var/lib/jbossas/standalone.
Mount OutSystems Platform Server in a separate partition:
  • If you have a partition reserved for the OutSystems Platform Server, move the directory /opt/outsystems/platform to the alternate partition, and create a mount point to it at /opt/outsystems/platform.
* Execute the Platform Database creation script:
  • You can find in the Deployment Controller Server at /opt/outsystems/platform/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 the OutSystems Platform Server later on.
* Execute the Platform Database creation script:
  • You can find in the Deployment Controller Server at /opt/outsystems/platform/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 the OutSystems Platform Server later on.
* Create the Platform Database:
  • Connect to your Oracle instance with a user that can create databases and use the customized script to create the database.
* Execute the OutSystems Platform Server session creation script:
  • You can find it at /opt/outsystems/platform/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 OutSystems Platform Server session creation script:
  • You can find it at /opt/outsystems/platform/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.
* Execute the Platform Database creation script:
  • You can find it in the Deployment Controller Server at /opt/outsystems/platform/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 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 the OutSystems Platform Server later on.
* Create the Platform Database:
  • Connect to your MySQL instance with a user that can create databases and use the customized script to create the database.
* Execute the OutSystems Platform Server session creation script:
  • You can find it at /opt/outsystems/platform/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
    • Run this script like you did with the script to create the data model of the OutSystems Platform.
* At this point you need the database users and schemas for use by the OutSystems Platform. For instructions on creating them, access the Database checklist in this document.
To do this, select the Database role at the top of this page.
* Download strong Cryptographic Support extension:
* Configure Deployment Controller Server services:
  • As the root user, execute: /opt/outsystems/platform/serviceconfigurator.sh -controller
* Configure Front-end Server services:
  • As the root user, execute: /opt/outsystems/platform/serviceconfigurator.sh -frontend
* Configure OutSystems Platform:
  • Start the OutSystems Configuration Tool. As the root user, execute: /opt/outsystems/platform/configurationtool.sh
    • Configure the OutSystems Platform Database
    • Do not skip the Farm Settings.
    • In the Farm configurations, set the Deployment Controller Server hostname. This network address will be used by this node to reach the deployment controller node.
    • In the Farm configurations, set the Local IP Address for Front-End Registration. This network address will be used by the Deployment Controller server to reach this Front-End node.
    • For the OutSystems Platform configurations use the default values.
    • Do not skip the WebLogic Settings: Choose the appropriate Managed Server.
    • Enter the address of the machine where WebLogic Administration Console is installed, the port, username and password.
    • Upon completion, the OutSystems Platform Database and the Session Database schema will be created.
    • When asked, please execute the following actions:
      • Restart the Application Server
      • Restart the OutSystems Services
      • Run the Service Center installation
      These are mandatory steps, otherwise the OutSystems Platform won't install properly
* Use the Glassfish RI JAXB Provider for web services in WebLogic:
  • The default JAXB Provider has issues that cause, in some cases, the incorrect execution of the platform's web service feature while having no advantages for the current implementation.
  • Make sure WebLogic is set to use the Glassfish RI JAXB Provider:
    • Open the WebLogic console at http://<AdministrationServer>:7001/console
      • You may need to allow incoming traffic through port 7001, you can add a temporary rule to iptables by running the following command (as the root user):
      • iptables -I INPUT -p tcp --dport 7001 -j ACCEPT
      • To restore iptables rules you can restart the service by running the following command (as the root user):
      • service iptables restart
    • Expand "Environment" under the "outsystems_domain" in the Domain Structure.
    • Select "Servers".
    • Select your Managed Server.
    • Select "Server Start" Tab
    • Ensure the "Arguments" text box contains the following: -Dcom.sun.xml.ws.spi.db.BindingContextFactory=com.sun.xml.ws.db.glassfish.JAXBRIContextFactory -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory
    • Restart your Managed Server by running the following command: service weblogic-outsystems restart

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.

* 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 (http://<yourserver>/ServiceCenter)
  • Set the environment's Hostname
  • Set the environment's Running mode to Development or Production
  • Press the Apply button
* Install System Components:
  • NOTE: In case you don't have a Web browser in the Production environment, copy the OSP file to a machine with a Web browser and execute the above steps there.
  • 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.: /opt/outsystems/platform/)
  • 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 his 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:
  • NOTE: In case you don't have a Web browser in the Production environment, copy the OSP file to a machine with a Web browser and execute the above steps there.
  • 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.: /opt/outsystems/platform/).
  • 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)
Business Activity Monitoring:
  • Install graphviz in the front-end servers: wget -O /etc/yum.repos.d/graphviz-rhel.repo http://www.graphviz.org/graphviz-rhel.repo
    yum install graphviz graphviz-gd
    yum install graphviz graphviz-gd
  • 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.

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 .

Be advised that, if you are upgrading OutSystems Platform from version 5.0.2 or earlier, you will have to upgrade your Red Hat installation to Red Hat Server 6.X.
OutSystems endorses Red Hat Inc's recommendation of performing a fresh installation (and manually migration of your personal data) rather than attempting an in-place Operating System upgrade from versions prior to 6.x.
To speed up the reactivation of the OutSystems Platform after install we advise that you should backup the current configuration file /etc/outsystems/server.hsconf. After the installation of the new version of the Red Hat Enterprise 6.x Operating System you should follow this Installation Checklist for the task First Install, restoring the backed up configuration file to /etc/outsystems prior to executing the OutSystems Configuration Tool.

Be advised that, if you are not already using it, you will have to upgrade your installation to Oracle Linux 6.X 64-bit.
OutSystems endorses Oracle's recommendation of performing a fresh installation (and manually migration of your personal data) rather than attempting an in-place Operating System upgrade from versions prior to 6.x.
To speed up the reactivation of the OutSystems Platform after install we advise that you should backup the current configuration file /etc/outsystems/server.hsconf. After the installation of the new version of the Oracle Linux 6.x Operating System you should follow this Installation Checklist for the task First Install, restoring the backed up configuration file to /etc/outsystems prior to executing the OutSystems Configuration Tool.

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.

When installing without internet connection there may be dependency errors, please download the necessary dependencies from the Red Hat Network.

Description Server
* Save configuration files:
  • You may want to backup the OutSystems services configuration files (files with extensions .properties and .policy) located in the OutSystems Platform Server installation folder to a backup directory. After the upgrade is complete, you may be able to re-apply any customizations they might have.
  • Copy the Configuration Tool file (/opt/outsystems/platform/server.hsconf) to a backup directory;

Deployment Controller Server

Front-end Server

* Register in Red Hat Network:
  • Go to Red Hat Network at Red Hat Network and log in to your account.
  • If your System is not registered in Red Hat Network, register it by executing rhn_register.
  • Enter in your machine details, and go to Software / Software Channels and add these Entitlements (Repositories):
    • RHEL Supplementary (v. this.OperatingSystem.GetRepositoryVersion() 64-bit x86_64)
    • JBoss Application Platform (v this.ApplicationServer.GetRepositoryVersion()) for this.OperatingSystem.GetRepositoryVersion()Server x86_64

Deployment Controller Server

Front-end Server

Register in Red Hat Network:
  • Go to Red Hat Network at Red Hat Network and log in to your account.
  • If your System is not registered in Red Hat Network, register it by executing rhn_register.
  • Enter in your machine details, and go to Software / Software Channels and add these Entitlements (Repositories):
    • RHEL Supplementary (v. this.OperatingSystem.GetRepositoryVersion() 64-bit x86_64)

Deployment Controller Server

Front-end Server

* Stop the JBoss Application/Web Server:
  • As the root user, execute: service jboss stop

Deployment Controller Server

Front-end Server

* Uninstall OutSystems Platform Server:
  • As the root user, execute: rpm -e OutSystemsPlatform
  • If you get a pre-uninstallation error, try it again but executing (as the root user): rpm --nopreun -e OutSystemsPlatform
  • Clean the OutSystems Platform directory when prompted.

Deployment Controller Server

Front-end Server

* Uninstall OutSystems JBoss Configurator:
  • As the root user, uninstall the previous version of OutSystems JBoss Configurator: rpm -e $(rpm -qa | grep OutSystemsJBoss)

Deployment Controller Server

Front-end Server

* Remove JBoss service:
  • As the root user, remove the service: chkconfig --del jboss
  • As the root user, remove the init script: rm /etc/init.d/jboss

Deployment Controller Server

Front-end Server

* Uninstall JBoss 5.0.1.GA:
  • If you made any customizations to JBoss, create a backup so that you can apply them to the new JBoss version.
  • As the root user, remove the JBoss 5.0.1.GA installation folder: rm -Rf /opt/jboss-5.0.1.GA
    • The JBoss configuration files have changed from version 5.0.1 GA. You should check the JBoss documentation to learn how to apply your customizations to the new JBoss version.

Deployment Controller Server

Front-end Server

* Clean environment variables:
  • Edit the /etc/profile file and remove any hardcoded definition of the following environment variables:
    • JBOSS_HOME
    • JAVA_HOME
    • ANT_HOME
  • As the root user, execute: unset JBOSS_HOME JAVA_HOME ANT_HOME
  • As the root user, execute: unset JAVA_HOME ANT_HOME

Deployment Controller Server

Front-end Server

* Install JBoss Application Server (7.1.1 Final):
  • Download the file jboss-as-7.1.1.Final.zip from the official site:
    http://www.jboss.org/jbossas/downloads/.
    • For the purpose of this document, we assume JBoss will be installed in the /opt/jboss-as-7.1.1.Final folder.
  • As the root user, uncompress the JBoss installation file to /opt: unzip jboss-as-7.1.1.Final.zip -d /opt/

Deployment Controller Server

Front-end Server

* Install the OutSystems yum repository:
  • As the root user, execute: rpm -i http://yum.outsystems.net/this.Version.ToString()/noarch/outsystems-repo.rpm
    • To install a package without internet connection, download the rpm from the above location, and then execute (as root user): rpm -i outsystems-repo.rpm

Deployment Controller Server

Front-end Server

* Install required WebLogic patches:
  • As the root user, check if you have patches 14617042(65WQ), 15921652(2QP1) and 18123824(M61X) applied to your WebLogic, by running the following code and looking for the Patch ID of the installed patches: su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -status=applied -verbose -view; popd"
  • If you do not have all mentioned patches, please download patch 14617042(65WQ), patch 15921652(2QP1) and patch 18123824(M61X) for Oracle WebLogic 10.3.6 from the official Oracle Support site.
  • As the root user, install the patch by following the instructions in the README.txt file that comes with the patch: mv p14617042_1036_Generic.zip p15921652_1036_Generic.zip p18123824_1036_Generic.zip /home/wls_outsystems/
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p14617042_1036_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p15921652_1036_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p18123824_1036_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -patchlist=65WQ,2QP1,M61X -install; popd"

Deployment Controller Server

Front-end Server

* Install required WebLogic patches:
  • As the root user, check which patches are applied to your WebLogic, by running the following code and looking for the Patch ID of the installed patches: su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -status=applied -verbose -view; popd"
  • If you have the patch 17170980(6LUU), as the root user, uninstall the patch by running the following code: su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -patchlist=6LUU -remove; popd"
  • If you do not have the patches 15857413(F3LX), 16196081(33VQ), 16578101(JXFY), 16196750(R79R), 18679737(ZNIQ), 15921652(KS83) and 18123824(SCT9) applied to your WebLogic, please download patch 15857413(F3LX), patch 16196081(33VQ), patch 16578101(JXFY), patch 16196750(R79R), patch 18679737(ZNIQ), patch 15921652(KS83) and patch 18123824(SCT9) for Oracle WebLogic 12.1.1 from the official Oracle Support site.
  • As the root user, install the patch by following the instructions in the README.txt file that comes with the patch: mv p15857413_12110_Generic.zip p16196081_12110_Generic.zip p16578101_12110_Generic.zip p16196750_12110_Generic.zip p18679737_12110_Generic.zip p15921652_12110_Generic.zip p18123824_12110_Generic.zip /home/wls_outsystems/
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p15857413_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p16196081_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p16578101_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p16196750_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p18679737_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p15921652_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "unzip -o -d /opt/Oracle/Middleware/utils/bsu/cache_dir/ /home/wls_outsystems/p18123824_12110_Generic.zip"
    su - wls_outsystems -s /bin/bash -c "pushd /opt/Oracle/Middleware/utils/bsu/; ./bsu.sh -prod_dir=/opt/Oracle/Middleware/wlserver_this.ApplicationServer.Version()/ -patchlist=F3LX,33VQ,JXFY,R79R,ZNIQ,KS83,SCT9 -install; popd"

Deployment Controller Server

Front-end Server

* Use the Glassfish RI JAXB Provider for web services in WebLogic:
  • The default JAXB Provider has issues that cause, in some cases, the incorrect execution of the platform's web service feature while having no advantages for the current implementation.
  • Make sure WebLogic is set to use the Glassfish RI JAXB Provider:
    • Open the WebLogic console at http://<AdministrationServer>:7001/console
      • You may need to allow incoming traffic through port 7001, you can add a temporary rule to iptables by running the following command (as the root user):
      • iptables -I INPUT -p tcp --dport 7001 -j ACCEPT
      • To restore iptables rules you can restart the service by running the following command (as the root user):
      • service iptables restart
    • Expand "Environment" under the "outsystems_domain" in the Domain Structure.
    • Select "Servers".
    • Select your Managed Server.
    • Select "Server Start" Tab
    • Ensure the "Arguments" text box contains the following: -Dcom.sun.xml.ws.spi.db.BindingContextFactory=com.sun.xml.ws.db.glassfish.JAXBRIContextFactory -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory
* Install the new OutSystems Platform Server revision:
  • As the root user, execute: yum update outsystems-agileplatform-jboss6-eap outsystems-agileplatform outsystems-agileplatform-libs yum update outsystems-agileplatform-jboss7-community outsystems-agileplatform outsystems-agileplatform-libs yum update outsystems-agileplatform-weblogic outsystems-agileplatform outsystems-agileplatform-libs
    • To install a package without internet connection, download the latest rpms outsystems-agileplatform-*.noarch.rpm outsystems-agileplatform-libs-*.noarch.rpm outsystems-agileplatform-jboss6-eap-*.noarch.rpm outsystems-agileplatform-jboss7-community-*.noarch.rpm outsystems-agileplatform-weblogic-*.noarch.rpm from the "OutSystems yum repository", and then execute (as root user): yum --disablerepo=* --nogpgcheck update outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck update outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck update outsystems-agileplatform-*.noarch.rpm
    yum --nogpgcheck update outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck update outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck update outsystems-agileplatform-*.noarch.rpm

Deployment Controller Server

Front-end Server

* Install the new OutSystems yum repository:
  • As the root user, execute: rpm -U http://yum.outsystems.net/this.Version.ToString()/noarch/outsystems-repo.rpm
    • To install a package without internet connection, download the rpm from the above location, and then execute (as root user): rpm -U outsystems-repo.rpm

Deployment Controller Server

Front-end Server

* Install the new OutSystems Platform Server release:
  • As the root user, execute: yum install outsystems-agileplatform-jboss6-eap yum install outsystems-agileplatform-jboss7-community yum install outsystems-agileplatform-weblogic
    • To install a package without internet connection, download the latest rpms outsystems-agileplatform-*.noarch.rpm outsystems-agileplatform-libs-*.noarch.rpm outsystems-agileplatform-jboss6-eap-*.noarch.rpm outsystems-agileplatform-jboss7-community-*.noarch.rpm outsystems-agileplatform-weblogic-*.noarch.rpm from the "OutSystems yum repository", and then execute (as root user): yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm
    yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm

Deployment Controller Server

Front-end Server

* Install the new OutSystems Platform Server release:
  • As the root user, execute: yum install outsystems-agileplatform-jboss6-eap yum install outsystems-agileplatform-jboss7-community yum install outsystems-agileplatform-weblogic
    • To install a package without internet connection, download the latest rpms outsystems-agileplatform-*.noarch.rpm outsystems-agileplatform-libs-*.noarch.rpm outsystems-agileplatform-jboss6-eap-*.noarch.rpm outsystems-agileplatform-jboss7-community-*.noarch.rpm outsystems-agileplatform-weblogic-*.noarch.rpm from the "OutSystems yum repository", and then execute (as root user): yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm
    yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm
  • Customize the OutSystems services configuration files (files with extensions .properties and .policy), based on the backup you have created before the upgrade. The OutSystems services configuration files are now located in /etc/outsystems.

    Don't reuse the old configuration files from 4.2 version. Instead, merge any customizations you have into the new configuration files.

  • Restore the file server.hsconf from the backup directory to /etc/outsystems.

Deployment Controller Server

Front-end Server

* Download strong Cryptographic Support extension:

Deployment Controller Server

Front-end Server

* Configure Deployment Controller Server services:
  • If the node is not a Front-end node, as the root user, execute: /opt/outsystems/platform/serviceconfigurator.sh -controller

Deployment Controller Server

* Upgrade the Platform Database schema:
  • Start the OutSystems Configuration Tool. As the root user, execute: /opt/outsystems/platform/configurationtool.sh
    Use the default values.
  • Answer Yes if a message shows up asking to restart the Application Server.
  • Answer Yes if a message shows up asking to start the Outsystems Scheduler Service.
  • Answer Yes when a message shows up asking you to run the Service Center installation.
  • Answer No if a message shows up asking to start the Outsystems Scheduler Service.
  • Answer No when a message shows up asking you to run the Service Center installation.

Deployment Controller Server

Front-end Server

* Configure OutSystems Platform:
  • Start the OutSystems Configuration Tool. As the root user, execute: /opt/outsystems/platform/configurationtool.sh
    Use the default values.
  • Answer Yes if a message shows up asking to start the Outsystems Scheduler Service.
  • Answer Yes when a message shows up asking you to run the Service Center installation.
  • Answer No if a message shows up asking to start the Outsystems Scheduler Service.
  • Answer No when a message shows up asking you to run the Service Center installation.

Deployment Controller Server

Front-end Server

* Save configuration files:
  • You may want to backup the OutSystems services configuration files (files with extensions .properties and .policy) located in the OutSystems Platform Server installation folder to a backup directory. After the upgrade is complete, you may be able to re-apply any customizations they might have.
  • Copy the Configuration Tool file (/opt/outsystems/platform/server.hsconf) to a backup directory;

Front-end Server

* Register in Red Hat Network:
  • Go to Red Hat Network at Red Hat Network and log in to your account.
  • If your System is not registered in Red Hat Network, register it by executing (as the root user) rhn_register.
  • Enter in your machine details, and go to Software / Software Channels and add these Entitlements (Repositories):
    • RHEL Supplementary (v. this.OperatingSystem.GetRepositoryVersion() 64-bit x86_64)
    • JBoss Application Platform (v this.ApplicationServer.GetRepositoryVersion()) for this.OperatingSystem.GetRepositoryVersion()Server x86_64

Front-end Server

Register in Red Hat Network:
  • Go to Red Hat Network at Red Hat Network and log in to your account.
  • If your System is not registered in Red Hat Network, register it by executing (as the root user) rhn_register.
  • Enter in your machine details, and go to Software / Software Channels and add these Entitlements (Repositories):
    • RHEL Supplementary (v. this.OperatingSystem.GetRepositoryVersion() 64-bit x86_64)

Front-end Server

* Stop the JBoss Application/Web Server:
  • As the root user, execute: service jboss stop

Front-end Server

* Uninstall OutSystems Platform Server:
  • As the root user, execute: rpm -e OutSystemsPlatform
  • If you get a pre-uninstallation error, try it again but executing (as the root user): rpm --nopreun -e OutSystemsPlatform
  • Clean the OutSystems Platform directory when prompted.

Front-end Server

* Uninstall OutSystems JBoss Configurator:
  • As the root user, uninstall the previous version of OutSystems JBoss Configurator: rpm -e $(rpm -qa | grep OutSystemsJBoss)

Front-end Server

* Remove JBoss service:
  • As the root user, remove the service: chkconfig --del jboss
  • As the root user, remove the init script: rm /etc/init.d/jboss

Front-end Server

* Uninstall JBoss 5.0.1.GA:
  • You may want to make a backup of any customizations you have made to your JBoss installation, in order to re-apply them in the new JBoss version.
  • As the root user, remove the JBoss 5.0.1.GA installation folder: rm -Rf /opt/jboss-5.0.1.GA
    • The configurations files changed from JBoss 5.0.1 GA. You should refer to JBoss documentation in order to migrate your settings.

Front-end Server

* Clean environment variables:
  • Edit the /etc/profile file and remove any hardcoded definition of the following environment variables:
    • JBOSS_HOME
    • JAVA_HOME
    • ANT_HOME
  • As the root user, execute: unset JBOSS_HOME JAVA_HOME ANT_HOME
  • As the root user, execute: unset JAVA_HOME ANT_HOME

Front-end Server

* Install the new OutSystems Platform Server revision:
  • As the root user, execute: yum update outsystems-agileplatform-jboss-eap outsystems-agileplatform outsystems-agileplatform-libs yum update outsystems-agileplatform-jboss-community outsystems-agileplatform outsystems-agileplatform-libs yum update outsystems-agileplatform-jboss6-eap outsystems-agileplatform outsystems-agileplatform-libs yum update outsystems-agileplatform-jboss7-community outsystems-agileplatform outsystems-agileplatform-libs yum update outsystems-agileplatform-weblogic outsystems-agileplatform outsystems-agileplatform-libs
    • To install a package without internet connection, download the latest rpms outsystems-agileplatform-*.noarch.rpm outsystems-agileplatform-libs-*.noarch.rpm jboss-outsystems-configuration-eap-*.noarch.rpm jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-jboss-eap-*.noarch.rpm outsystems-agileplatform-jboss-community-*.noarch.rpm outsystems-agileplatform-jboss6-eap-*.noarch.rpm outsystems-agileplatform-jboss7-community-*.noarch.rpm outsystems-agileplatform-weblogic-*.noarch.rpm from the "OutSystems yum repository", and then execute (as root user): yum --disablerepo=* --nogpgcheck update jboss-outsystems-configuration-eap-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck update jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck update outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck update outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck update outsystems-agileplatform-*.noarch.rpm
    yum --nogpgcheck update jboss-outsystems-configuration-eap-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck update jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck update outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck update outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck update outsystems-agileplatform-*.noarch.rpm

Front-end Server

* Install JBoss Application Server (7.1.1 Final):
  • Please download the file jboss-as-7.1.1.Final.zip from the official site:
    http://www.jboss.org/jbossas/downloads/.
    • For the purpose of this document, we assume JBoss will be installed to /opt/jboss-as-7.1.1.Final folder.
  • As the root user, uncompress the JBoss installation file to file to /opt: unzip jboss-as-7.1.1.Final.zip -d /opt/

Front-end Server

* Install the OutSystems yum repository:
  • As the root user, execute: rpm -i http://yum.outsystems.net/this.Version.ToString()/noarch/outsystems-repo.rpm
    • To install a package without internet connection, download the rpm from the above location, and then execute (as root user): rpm -i outsystems-repo.rpm

Front-end Server

* Install the new OutSystems Platform Server release:
  • As the root user, execute: yum install outsystems-agileplatform-jboss-eap yum install outsystems-agileplatform-jboss-community yum install outsystems-agileplatform-jboss6-eap yum install outsystems-agileplatform-jboss7-community yum install outsystems-agileplatform-weblogic
    • To install a package without internet connection, download the latest rpms outsystems-agileplatform-*.noarch.rpm outsystems-agileplatform-libs-*.noarch.rpm jboss-outsystems-configuration-eap-*.noarch.rpm jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-jboss-eap-*.noarch.rpm outsystems-agileplatform-jboss-community-*.noarch.rpm outsystems-agileplatform-jboss6-eap-*.noarch.rpm outsystems-agileplatform-jboss7-community-*.noarch.rpm outsystems-agileplatform-weblogic-*.noarch.rpm from the "OutSystems yum repository", and then execute (as root user): yum --disablerepo=* --nogpgcheck install jboss-outsystems-configuration-eap-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm
    yum --nogpgcheck install jboss-outsystems-configuration-eap-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm

Front-end Server

* Install the new OutSystems Platform Server release:
  • As the root user, execute: yum install outsystems-agileplatform-jboss-eap yum install outsystems-agileplatform-jboss-community yum install outsystems-agileplatform-jboss6-eap yum install outsystems-agileplatform-jboss7-community yum install outsystems-agileplatform-weblogic
    • To install a package without internet connection, download the latest rpms outsystems-agileplatform-*.noarch.rpm outsystems-agileplatform-libs-*.noarch.rpm jboss-outsystems-configuration-eap-*.noarch.rpm jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-jboss-eap-*.noarch.rpm outsystems-agileplatform-jboss-community-*.noarch.rpm outsystems-agileplatform-jboss6-eap-*.noarch.rpm outsystems-agileplatform-jboss7-community-*.noarch.rpm outsystems-agileplatform-weblogic-*.noarch.rpm from the "OutSystems yum repository", and then execute (as root user): yum --disablerepo=* --nogpgcheck install jboss-outsystems-configuration-eap-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --disablerepo=* --nogpgcheck install outsystems-agileplatform-*.noarch.rpm
    yum --nogpgcheck install jboss-outsystems-configuration-eap-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install jboss-outsystems-configuration-community-*.noarch.rpm outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm yum --nogpgcheck install outsystems-agileplatform-*.noarch.rpm
  • Customize the OutSystems services configuration files (files with extensions .properties and .policy), based on the backup you have created before the upgrade. The OutSystems services configuration files are now located in /etc/outsystems.

    Don't reuse the old configuration files from 4.2 version. Instead, merge any customizations you have into the new configuration files.

  • Restore the file server.hsconf from the backup directory to /etc/outsystems.

Front-end Server

* Download strong Cryptographic Support extension:

Front-end Server

* Configure Front-end Server services:
  • If the node is not a Controller node, as the root user, execute: /opt/outsystems/platform/serviceconfigurator.sh -frontend

Front-end Server

* Configure OutSystems Platform:
  • Start the OutSystems Configuration Tool. As the root user, execute: /opt/outsystems/platform/configurationtool.sh
    Use the default values.
  • Answer No if a message shows up asking to start the Outsystems Scheduler Service.
  • Answer No when a message shows up asking you to run the Service Center installation.

Front-end Server

* Configure OutSystems Platform:
  • Start the OutSystems Configuration Tool. As the root user, execute: /opt/outsystems/platform/configurationtool.sh
    Use the default values.
  • Answer Yes if a message shows up asking to restart the Application Server.
  • Answer No if a message shows up asking to start the Outsystems Scheduler Service.
  • Answer No when a message shows up asking you to run the Service Center installation.

Front-end Server

* Platform upgrade:
  • As the root user, execute: /opt/outsystems/platform/scinstall.sh

Deployment Controller Server

* 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
    • NOTE: You typically 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

* System Components:

NOTE: 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 /opt/outsystems/platform/System_Components.osp.

Update System Components:

  • NOTE: In case you don't have a Web browser in the Production environment, copy the OSP file to a machine with a Web browser and execute the above steps there.
  • 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 /opt/outsystems/platform/System_Components.osp file
  • Click 1-Click Publish
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 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:
  • NOTE: In case you don't have a Web browser in the Production environment, copy the OSP file to a machine with a Web browser and execute the above steps there.
  • 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.: /opt/outsystems/platform/).
  • 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

Business Activity Monitoring:
  • Install graphviz in the front-end servers: wget -O /etc/yum.repos.d/graphviz-rhel.repo http://www.graphviz.org/graphviz-rhel.repo
    yum install graphviz graphviz-gd
    yum install graphviz graphviz-gd
  • 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

Front-end Server

* Upgrade your factory:

Upgrade your factory manually.

  • You will need a Microsoft Windows environment with Service Studio this.Version.ToString() and Integration Studio this.Version.ToString() installed.

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

Windows Environment

* Configure OutSystems Platform:
  • Start the Outsystems Scheduler Service. As the root user, execute: service outsystems start scheduler

Deployment Controller Server

Front-end 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.

*
Edit /usr/share/jbossas/bin/standalone-outsystems.conf /opt/jboss-as-7.1.1.Final/bin/standalone-outsystems.conf and adjust the memory options of the JAVA_OPTS.
In the Administration Server Console (http://<AdministrationServer>:7001/console), find the Managed Server's Start tab, and adjust the memory options.
  • OutSystems recommends that the maximum java heap size to be the server's total RAM, minus 1.5GB for other services (e.g.: If the server has 8GB of RAM, configure 6.5GB for the application server with -Xmx=6656m).
For a Java JVM options reference, see Java HotSpot VM Options.
For JRockit JVM options reference, see JRockit JVM Command-Line Reference.

Legend: * Mandatory; Optional.

Making your system more secure

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

Red Hat Linux Manuals: See Firewalls reference in Red Hat Linux Manuals.
Disabling SSLv3 to prevent POODLE Vulnerability.
  • Execute source ./etc/sysconfig/outsystems

  • Edit the $JBOSS_HOME/standalone/configuration/standalone-outsystems.xml file.
  • Find all HTTPS connectors ( attribute secure="true" and sub element <ssl> present )
  • Add a protocol="TLSv1" attribute at the end of the ssl element.

  • Edit the $JBOSS_HOME/bin/standalone-outsystems.conf file.
  • Add the line JAVA_OPTS="$JAVA_OPTS -Dhttps.protocols=TLSv1" at the end of the file.

  • Restart jboss by executing service jboss-outsystems restart
Disabling SSLv3 to prevent POODLE Vulnerability.
  • Open the WebLogic console at http://<AdministrationServer>:7001/console
    • You may need to allow incoming traffic through port 7001, you can add a temporary rule to iptables by running the following command (as the root user):
    • iptables -I INPUT -p tcp --dport 7001 -j ACCEPT
    • To restore iptables rules you can restart the service by running the following command (as the root user):
    • service iptables restart
  • Press the "Lock and Edit" button.
  • Expand "Environment" under the "outsystems_domain" in the Domain Structure.
  • Select "Servers".
  • Select your Managed Server.
  • Select "Server Start" Tab
  • Ensure the "Arguments" text box contains the following: -Dweblogic.security.SSL.protocolVersion=TLS1 -Dhttps.protocols=TLSv1
  • Press the "Save" and "Activate Changes" buttons.
  • Restart your Managed Server by running the following command: service weblogic-outsystems restart
By default, WebLogic user accounts get locked for a period of time when a number of invalid login attempts exceed the specified Lockout Threshold.
  • To be able to unlock your Administrator Account, in case it happens, go to the Administration Server Console (http://<AdministrationServer>:7001/console), and create a secondary Administrator Account considering:
    • Give the user a unique name that cannot be easily guessed.
    • Do not use system, admin or administrator for your system administrator user accounts.
    • Do not deploy a domain that can be accessed with the username weblogic and the password welcome1
    • The passwords for user accounts on production machines should be difficult to guess and should be guarded carefully.
Get more info about WebLogic Best Practices Best Practices .
To enable SSL communication in your WebLogic server see the SSL configuration reference in Oracle Manuals.
To enable SSL communication in your WebLogic server see the SSL configuration reference in Oracle Manuals.
Oracle Linux: See Firewalls reference in the Security Guide in Oracle Manuals.

Legend: * Mandatory; Optional.

See Also

As mentioned above sections, you might need to consult the following: