10.0

Edit

Prepare servers

Prepare MS SQL server

For Workfusion Intelligent Automation Cloud installation you need to have an existing activated instance of the MS SQL server. The server must be up and running during the Workfusion Intelligent Automation Cloud installation.

To prepare a MS SQL server:

  1. Create the <mssql_db_name> database, and specify the database name. For other options you may use the default values.

    Create DB

  2. Create the <mssql_dba_user> owner with the full-access permissions for the <mssql_db_name> database. This user must be later specified in config.yml.

    Note: for all logins, the following password policies are applied:

    • Allowed special symbols for db password for monitoring tools: @#^*():,.}<>/
    • Allowed special symbols for db password for the Analytics component: @#^*():,.;}[]/

    To create the owner:

    1. On a MS SQL server, create the mssql login, specify the login name, and then make sure that the Enforce password policy check box is not selected.

    2. In the Default database box, specify the database, and then choose English as Default language.

    3. In the Select a page group, click User mapping, and then select the <mssql_dba_user> check box to map the user to the <mssql_db_name> database. Leave all other options unchanged.

      Create DB User

    4. In the database Users, select the db_owner check box to assign <mssql_dba_user> to the db_owner role.

      Assign to group

  3. Create the following MS SQL login names and passwords for the Workfusion components:

    • mssql_dba_user
    • mssql_ct_user
    • mssql_ws_user
    • mssql_sqc_user
    • mssql_ds_user
    • mssql_rpa_user
    • mssql_pm_user
    • mssql_dm_user
    • mssql_rapi_user
    • mssql_ocr_user

    See the password policy earlier.

  4. For each login, specify the following parameters:

    • If you use the SQL Server authentication,

      1. Specify the login name.
      2. Make sure that the Enforce password policy check box is not selected.
      3. In the Default database box, specify the database.
      4. Choose English as Default language.

      SQL auth

    • If you use Windows authentication,

      1. Select a corresponding login name.
      2. In the Default database box, specify the database.
      3. Choose English as Default language.
      4. For other options leave the default values.

      Win auth

  5. When configuring the Integration server, on the INT server, in the config.yml file, in the #MSSQL section, remember to specify the corresponding login names and passwords, that you have created on the previous step.

Prepare Integration server

Extract installation packages

To extract installation packages:

  1. Log in to the Integration server as a Linux installation user, by using Linux Terminal, Windows PuTTY, or any other SSH client:

    $ ssh -i <path-to-private-key.pem> <username>@<hostname.example.com>

  2. In INSTALL_DIR, create a directory for the WorkFusion installation package, for example, /opt/workfusion/wf_installer. Grant the read access for this directory to all users:

    $ sudo mkdir -p /opt/workfusion/wf_installer
$ sudo chmod 0755 /opt/workfusion/wf_installer

  3. Make sure that the Linux installation user is an owner of the installation directory:

    $ sudo chown -R <username>:<username> /opt/workfusion/

  4. Download the provided installation package with any file retrieving tool, for example, wget or curl:

    • If the Internet access is available on the server:

      $ curl 'https://link_to_installer' --output /opt/workfusion/workfusion-full-package-<version>.tar.gz

    • If the Internet access is not available on the Integration server, download the Intelligent Automation Cloud installer and copy it as /opt/workfusion/workfusion-full-package-<version>.tar.gz on the Integration server.

  5. Extract the downloaded package to the directory:

    $ tar -xzvf /opt/workfusion/workfusion-full-package-<version>.tar.gz --strip 1 -C /opt/workfusion/wf_installer

Configure installation

To configure installation:

  1. In your PACKAGE_DIR directory, edit the hosts.yml configuration file. The vi text editor is used in the example below:

    $ vi hosts.yml

    Refer to the hosts.yml options section for more details on each option.

  2. In the same directory, change the permissions for the config.yml file:

    $ sudo chmod 644 config.yml

  3. Open the PACKAGE_DIR/config.yml file, and in the parameter ansible_vault_password, change the ansible vault password:

    $ vi config.yml

    The password is used for encrypting the config.yml at the following step and will be asked several times during the installation of the components. We strongly recommend to secure and memorize it. When creating passwords, make sure they are strong enough and meet the following requirements:

    Ansible pass

    Optionally, on the INT server, run the following command to automatically generate passwords for the WorkFusion internal services according to product policies. We strongly recommend to change them manually for security reasons. Note that the command doesn't generate end-user password.

    $ ./install.sh passwords generate

    As a result, in config.yml, the passwords for most services, except for the following end-user ones, are created:

    "wf_password"
"ldap_bind_password"
"mail_pass"
"tableau_dashboard_pass"
"tableau_automation_pass"
"windows_installation_pass"
"elk_admin_pass"
"ansible_vault_password”
"bot_relay_user_pass"
"bot_user_pass"

    If you prefer to set the passwords manually, remember to use only Latin letters and allowed symbols. If needed, change other secrets and parameters, as well. After that, save and close the file.

    Remember, in the #MSSQL section, specify the corresponding MS SQL login names and passwords, that you have created earlier.

  4. In your PACKAGE_DIR, encrypt the config.yml file:

    $ ./install.sh encrypt config

    Note that WorkFusion Intelligent Automation Cloud 10 installer will not let you start the installation until config.yml is encrypted.

    If needed, you can later edit the encrypted file with the following commands:

    $ cd /opt/workfusion/wf_installer
$ ./install.sh edit_config int

  5. Prepare the TLS certificates, as described in Prepare TLS certificates for installation.

  6. Copy the provided license.properties file to the installation directory to install the WorkFusion license, for example, /opt/workfusion/wf_installer/license.properties.

    If you perform installation on your own, request the license file from your WorkFusion Account Manager in the same way, as you receive the Tableau license.

Prepare Windows servers

The following operations must be performed on all Windows servers.

To configure access for Intelligent Automation Cloud installation:

  1. Connect to the remote Windows server via Remote Desktop or any other client as a Windows installation user. See Create installation users.

  2. Run PowerShell as Administrator.

  3. In PowerShell, run the following commands:

    $url = "https://s3.amazonaws.com/workfusion-installer/blobs/artifacts/winrm-config/ConfigureRemotingForAnsible.ps1"
$file = "$env:c\ConfigureRemotingForAnsible.ps1"
(New-Object -TypeName System.Net.WebClient).DownloadFile($url, $file)
powershell.exe -ExecutionPolicy ByPass -File $file -Verbose

    The script checks the current WinRM (PS Remoting), enables CredSSP authentication, creates SSL listener and configures firewall for WinRM HTTPS connections to allow Ansible to connect, authenticate, and execute PowerShell commands.

If the Internet access is not available on the target server:

  1. Download the script from https://s3.amazonaws.com/workfusion-installer/blobs/artifacts/winrm-config/ConfigureRemotingForAnsible.ps1 and save it to the target windows server manually, for example, to C:\tmp\ConfigureRemotingForAnsible.ps1.

  2. Run PowerShell as Administrator.

  3. In PowerShell, run the following command:

    powershell.exe -ExecutionPolicy ByPass C:\tmp\ConfigureRemotingForAnsible.ps1
← PreviousNext →