PerformanceTuning.log Lists all the steps done to perform tuning optimizations (if applicable). PerformanceTuningCheck.log Lists all the steps done to check which tuning optimizations can be performed. PrerequisitesInstall.log Lists all the steps done when installing missing prerequisites (if applicable). The available log files are the following: PrerequisitesCheck.log Lists all the steps done to check what prerequisites are installed and/or missing. Where is the user installing the platform. ![]() (the default path is C:\Users\\AppData\Local\OutSystems\PlatformInstaller) %LocalAppData%\OutSystems\PlatformInstaller.They are located in the following folder: You can check the logs generated by the installer package for detailed information. 1 = system reboot is required to finalize prerequisite installation (only detected when the Platform Server installation package is automatically installing the prerequisites)Ĭapturing these exit codes requires that the installer package is executed inside the context of its own command shell.The OutSystems Platform Server installation package will return different exit codes depending on the install status: If this switch is provided, it must be the last one in the command line and the provided path must not contain quotes ( "") even if the path contains spaces.įor more information check the Automatic Prerequisites Installation and Configuration Tuning. The optional /D switch specifies the path where the OutSystems Platform Server is installed. The optional /DoTuning= switch specifies if the tuning should be automatically performed. The optional /InstallPrerequisites=True switch specifies if the prerequisites will be automatically installed. Run the OutSystems Platform Server installation package as follows: PlatformServer-.exe /S The OutSystems Platform Server installation package can automatically install most of the prerequisites. server roles and features, services options). Implies execution of the steps described in the Pre-installation Checklist (e.g. Note: In both cases, you need to include the /SetPlatformServerAdminPassword argument if the Admin user of Platform Server is active and its password is still defined as 'admin'. In this scenario, you need to execute Step 7 to republish all applications right after the upgrade. The above command skips the modules preparation step. If you plan to republish all your applications right after the upgrade, use the following instead: \ /UpgradeInstall In this scenario, you won't execute Step 7 to republish all applications. The above command sets the Configuration Tool to start preparing your modules for the new Platform Server version, without deploying them. If you plan to publish your applications gradually, run the Configuration Tool as follows: \ /UpgradeInstall You can also opt to republish all your applications right after the upgrade, but it's not a mandatory step. If you are upgrading from Platform Server 11.x to Platform Server 11.12 or later, after the Platform Server is upgraded, you can publish your applications gradually, following your teams' pace. The same applies to other parameters that refer hostnames.Įnsure that usernames and passwords are stored with the correct casing. To easily add a front-end later, the CompilerServerHostname parameter must include the name or IP of the machine and not localhost. Keep in mind that configuration settings differ between OutSystems platform database. Templates can be automatically generated before proceeding with the configuration steps of the unattended installation process (or even before the installation of the platform in the new machine, if you already have another machine where the platform is already installed), by using the following command line which will save them to the directory \docs: \ /GenerateTemplates You can check the description of each parameter in the server.hsconf file. The templates refer to the operating system and application server where the Configuration Tool is running. To help create specific server configuration files, Configuration Tool can automatically generate different configuration file templates for each database engine on which OutSystems can run on. Replace the default \server.hsconf file with a customized template containing your specific configurations. Update the server.hsconf configuration file Copy the configuration files from the controller node to the front-endĥ. Only for upgrades: republish the entire factory ![]() Upload the license file (requires manual intervention) Upload license file (requires manual intervention) Only for Oracle: create the database users Install the Development Environment binaries Install the OutSystems platform prerequisites
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |