Copying Empirica Authenticator files to the Linux OBIEE server

Previous Topic

Next Topic

Book Contents

Copying Empirica Authenticator files to the Linux OBIEE server

In order to support different security environments, configuration variables may be initialized (hard-coded) into the initConfig.sh script file, or prompted for (interactively) in the configObiee.sh script file. Any combination of hard-coding and interactive prompting is supported. For example, leaving password values blank in initConfig.sh would result in interactive prompts for the passwords in configObiee.sh.

  1. Create temporary working folders <tempFolder> and <linuxObieeDir> on the Linux machine hosting OBIEE.
  2. Log in to the Linux server using privileged account and switch to non-privileged account using the following sudo command:

    sudo su - <non-privileged account>

  3. Unzip the Signal-8_1_0_0_<xxx>-OBIEE.zip into a temporary working folder <tempFolder>.

    The OBIEE directory is created in the <tempFolder> directory.

  4. Using your privileged account, issue the following command:

    sudo chmod -R 700 <tempFolder>

  5. From the Signal installation, copy the webvdme.properties file into the <tempFolder>/OBIEE/empiricaprovider directory.
  6. If necessary, explicitly provide the webvdme.properties file the permission to log in directly to the non-privileged account.

    Note: The SSO plugin settings in the webvdme.properties file must match the SSO settings used by OBIEE. For example, if SSO is not enabled on OBIEE, comment out the "sso" plugin lines in the webvdme.properties file.

  7. If the OBIEE Admin port is different than the default value of 9500, edit the <tempFolder>/OBIEE/empiricaprovider/obiee_auth.properties file, changing "port=9500" to "port=<AdminPort>", where "<AdminPort>" is the OBIEE Admin port.
  8. Edit the <tempFolder>/OBIEE/config/initConfig.sh file. Set each variable in the initialize configuration variables section and record the new value. For more information, see About configuring OBIEE authentication. If desired, leave sensitive configuration variables such as passwords blank. Blank values will be prompted for in the configObiee.sh script.
  9. Copy the <tempFolder>/OBIEE directory to the <linuxObieeDir> working directory on the Linux server. Record the full path to the <linuxObieeDir> directory.
  10. Using your privileged account, issue the following command:

    sudo chmod -R 700 <linuxObieeDir>

Send Feedback