Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Go to the installer path C:\Program Files\WhereScape\RED, run RedSchedulerInstaller.exe.

  2. The Scheduler Installation screen opens. Select all the installation options: Install Scheduler, Install Executor, and Add Scheduler Configuration to RED, and click Next.

    1. Only one Scheduler can be installed per RED metadata repository
    2.  If you installed a scheduler already and only want to install another Executor then deselect the other options
  3. In the Install Location screen, select the Installation Location. It is recommended to create a folder under the C: disk to install Azkaban. Click Next. 

    Tip
    titleAzkaban Install Location

    The install location must be writeable for the Service User which the service will run under so should not be installed in a directory under Windows Users. Typically you would create a folder called Azkaban in your 'C:\Program Files\WhereScape' directory, but it can be installed anywhere on the machine that the service you has write access to.


  4. The Scheduler Metadata screen shows the information of the database that contains the scheduler metadata. Fill out the Database Name, the User Name, and the Password of the database you created for Azkaban (Follow the same steps you follow to create the PostgreSQL Database). 

    Click Validate to confirm that all the entered information is correct. Click Next.

    Note: PostgreSQL Database Server Port is 5432 in default installations, but your database port may be different.

  5. Enter the RED Metadata database information. Enter the Database Name, the User Name, and the Password. Click Validate to confirm all the information is correct , and click Next.

  6. Enter the Scheduler Metadata information to upgrade or install itinstallation/upgrade or leave blank to use the previously entered user for Azkaban and click Next. These credentials are for an administrative database user with permission to perform DDL operations (If required) and click Next.

  7. The new Scheduler runs as a web server. The Web Server Configuration screen is populated automatically, make allows specifying the settings for the Web Server, make any changes necessary, populate all "required" fields and be sure that the option Install as Windows Service is selected before you move on.  Note: You can uncheck Install as a Windows Service when upgrading or when you want to manage startup of the Web Server manually.

    Tip
    titleProfile Pwd and Windows User

    The 'Profile Encryption Secret' will be used by RED Scheduler Jobs to decrypt the connection credentials at run-time, therefore you must remember and use this same password when generating the encrypted Scheduler Profile records for your connections. See Scheduler Profile Maintenance for more information.

    The 'Service User' is a windows user with the 'Log On As A Service' right, which the Azkaban service will run under. During installation the azkaban.local.properties file will be created for each Azkaban server with Windows user-based DPAPI encrypted password values and therefore only this same Service User will be able to decrypt those passwords at run-time.

    The 'Job Work Directory' is a location for any RED job related temporary files to be created. When left empty it will default to the Service User's temp directory at run-time. If you specify a value here it is important to make sure it will be writeable for the Server User, so typically you would not use a folder under the Windows Users directory.


  8. In the Executor Configuration, click Add an Executor Tag…, enter the host name or IP address, and click OK. Click Next to continue with the installation.

  9. Under the Email Configuration, enter the values you need to configure the email notifications. Click Next.

  10. A window pops up to select the Data Source Name from the drop-down menu which is the RED Metadata database that you created previously, its credentials, Validate the data, and click Login.

    Tip
    titleRED Scheduler Configuration

    This step applies the configuration to RED, which can be viewed in RED Scheduler Tab. It is important to note that the credentials for the Azkaban Dashboard User and API User are not applied to RED since these now reside only in the RED Profile file. After installing the Azkaban Web Server you will need to log in to RED and set these values in you Scheduler Configuration and then right click on 'Connections' node in the object tree to 'Save Profile' and 'include passwords'

  11. The Add Scheduler Configuration to WhereScape RED window shows the information on how the new Scheduler will be accessed. Click Next.

    Tip
    titleRED Scheduler Configuration

    It is important to note that the credentials for the Azkaban Dashboard User and API User are not applied to RED since these now reside only in the RED Profile file. Therefore after installing the Azkaban Web Server you will need to log in to RED and set these values in you Scheduler Configuration and then right click on 'Connections' node in the object tree to 'Save Profile' and 'include passwords'.
    The default credentials used in this screen are: wsdashboarduser, wsdashboardpass and wsapiuser, wsapipass




  12. In the Summary window, review all the information about your installation and click Install.

  13. When the installation is complete, click Finish to close the confirmation window.

...

In most cases you can simply go to Services.msc in Windows to find your Azkaban services and go to Properties of that service and renter the password for the service user, which will prompt Windows to detect the lack of rights issue and set the required rights for the user. In some systems only an Administrator user will be able to assign these rights so it is best to either have an admin do this or have the user created with the required rights by and admin prior to installation.

Another reason this could happen is if the services already exist, such as in an upgrade scenario. For upgrades it is best to either remove the service manually prior to upgrading or uncheck the 'Install as a Service' option during the install. In many cases the application upgrade will have been successful so you would just need to start up the service again.