Use InterPlay with two users

Overview

If your company policy requires limiting the rights of the Database users, InterPlay can be installed with two database users.

The two users are:

  • Owner: the administrator is allowed to modify the database schema.
  • Functional: the end-user is allowed to insert and update data in the InterPlay database.

The Owner user name and password are not saved in the InterPlay configuration files but must be provided for each modification of the Database schema.

For example, when installed with one database user that has rights to modify the database schema, InterPlay dynamically adds new database tables each time new formats are deployed from the repository. In the “two users” mode, this operation is not authorized anymore.

The following operations that imply modifications on the database structure are modified in the “two users” mode.

  • Deployment button in the Designer: to deploy your configuration.
  • The button only publishes the configuration on the disk and in the Repository but does not publish it anymore on the connected InterPlay instance.
  • cleanTables ant command that cleans the database takes now the user name and password as input parameters.
  • updateServerConfiguration ant command that deploys the configuration into InterPlay and creates new tables takes now the username and password as input parameters.

For more information on database "two user" mode, refer to the InterPlay Installation Guide.

Database cleaning

To clean the database, use the cleanTables ant command with associated parameters

Example:

ant cleanTables -DInstallerDBUser=<adminUser> -DInstallerDBPwd=<encryptedAdminPassword>

Where

<adminUser> represents the ID of a user with administrative rights on the database that the Runtime component uses.

<encryptedAdminPassword> represents the admin user password in encrypted form.

Deployment and server configuration update

Same instance of Repository for Interplay and InterPlay Designer

If InterPlay and InterPlay Designer use the same instance of Repository:

  1. In the InterPlay Designer, deploy the configuration using the Deploy button.
  2. Run the updateServerConfiguration command.
    The command must be run in offline mode. Make sure that in the ant-task.properties filethat the UpdateServerConfigurationMode property is set to offline.
  3. Run the runGeneratedSqlScripts ant command using the InstallerDBUser and InstallerDBPwd parameters.

Example:

ant runGeneratedSqlScripts -DInstallerDBUser=<adminUser> -DInstallerDBPwd=<encryptedAdminPassword>

Where

  • <adminUser> represents the ID of a user with administrative rights of the Database the Runtime component uses
  • <encryptedAdminPassword> represents the admin user password in encrypted form.

Different instances of Repository for Interplay and InterPlay Designer

If InterPlay and InterPlay Designer use different instances of Repository:

  1. From the InterPlay Designer Tools, run the createDeploymentPackage ant command.
  2. Copy the deployment directory created in the previous step to the machine where the Repository for InterPlay is running.
  3. Import the configuration previously created from InterPlay Designer to Repository of InterPlay Runtime using the commands from the Repository.
  4. From the InterPlay Designer Tools, run the updateServerConfiguration command.
    The command must be run in offline mode. Make sure that in the ant-task.properties file that the UpdateServerConfigurationMode property is set to offline.
  5. Run the runGeneratedSqlScripts ant command using the InstallerDBUser and InstallerDBPwd parameters.
  6. Example:

    ant runGeneratedSqlScripts -DInstallerDBUser=<adminUser> -DInstallerDBPwd=<encryptedAdminPassword>

    Where

    • <adminUser> represents the ID of a user with administrative rights of the Database the Runtime component uses
    • <encryptedAdminPassword> represents the admin user password in encrypted form.
  7. Use the “encryptPassword” ant command to generate an encrypted password. This command is available among the InterPlay and Designer batch commands.

Example:

ant encryptPassword <passwordToEncrypt>

Where

<passwordToEncrypt> is the password to encrypt

Related Links