Set the Designer script parameters

You set the configuration parameters used in the scripts in the ant-task.properties file.

To set the script parameters, see:

About scripts common variables

The ant-task.properties file contains variables that are common to many scripts:

  • Database connection variables are parameters that make the database URL up.

Database connection variables:

Parameter Description
DBHost Database host
DBport Database port
DPInstance Name of the database instance
DBDriver Driver used to connect to the database
DBType Database type (oracle)
DBUser

User name for the connection to the database.

The same database user is used for all accesses to the database.

DBAdminUser

User and encrypted password for the database administrator user.

DBAdminPwd
DBPwd

Encrypted password.

The password can be changed via the encryptPassword script.

DBUrl The complete database URL. It will be used if it is specified, otherwise the database URL will be computed using the above arguments. It provides a way to specify complex database URLs.
  • InterPlay connection variables are parameters that specify the:
    • Web server URL
    • InterPlay Web application identifier

InterPlay connection variables:

Parameter Description
Host Host machine
Port Port of the Web server
Context Web application name (interplay-web or interplay-designer-web)

interplay-designer-web

CommunicationProtocol HTTP or HTTPS protocol
InterPlayUser User name for the connection to the product.
InterPlayPassword Password for the connection to the product.
InterplayUserDomain Domain for the connection to the product.

Add a parameter prefix

You can define several values for the same parameters by adding a prefix to the parameter name. This enables you to switch quickly from one configuration parameter set to another from the command line.

Most of the variables in the ant-task.properties file can have a prefix. The following variables are however exceptions:

  • ArchiveDestDirectory
  • ArchiveDestFileName
  • ArchiveBasedir
  • BASE_PATH
  • InstallerExecution
  • InterPlay connection variables
  • SetUpExecution
  • TrustStoreFile
  • TrustStorePass

InterPlay searches first for the variable with the given prefix, and if no variable is found, it searches for the variable without the prefix.

Example

If the ant-task.properties file contains the following parameters for the export document action:

ExportDocsByFilterDirectoryPath=D:\\Export\ACCOUNTING_DOCSET

ExportDocsByFilterConditionFilter = collection.bpi=99

Set1.ExportDocsByFilterConditionFilter = collection.bpi=100

Set2.ExportDocsByFilterConditionFilter = collection.bpi=101

In the command line, you specify the prefix to use:

ant -DPrefix=Set1 exportDocuments

This runs the exportDocuments script with the Set1.ExportDocsByFilterConditionFilter parameter.

The ExportDocsByFilterDirectoryPath parameter is used if the prefix is different from Set1 and Set2 or if no prefix is given.

Declare two database users

By default, InterPlay allows the connection to the database to a user that has the rights to alter the schema by adding tables. However, if your security policy requires that only an administrator on a special account modify the database schemas, then you can create two different database users:

During installation, give a different name to the 2 database users that are requested:

  • 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.

Restriction: Only the Owner user can run the scripts that modify the database schemas:

  • importServerConfiguration
  • cleanTables

Related Links