Create Repository

A Repository contains workflow definitions, Queues, Calendars, Workflow execution data, and Business Activity Monitoring (BAM) data. The Resource Provider for the repository is also defined while creating a repository.

To create a Repository

1. On the Windows Start menu, point to Programs, point to AVEVA, and then click Central Configuration.

   The Central Configuration page appears.

2. Click Repository Settings.

   The Repository List page appears.

3. Click Add.

   Note: If the number of repositories exceeds the permitted limit for the license, then the message You have exceeded the maximum number of repositories appears, and the repository creation is stopped. Click Close.

   The Manage Repository page appears.

4. Enter the required details.

5. Click OK.

   The Config Administrator page appears.

6. Click to configure an administrator.

   The User Lookup dialog box appears.

7. Select the provider from the provider drop-down list.

8. Enter the details to search the administrator for the repository that is created.

   Note: You can also search a user based on ObjectSID and objectGUID (applicable only for Active Directory provider).

9. Click Search.

   The user is listed under Available Resources.

10. Select and click the arrow to list the user under Selected Resource.

11. Click Update.

    The selected user is displayed in User Lookup.

12. Click OK.

    A message confirming the successful creation of an administrator appears.

13. Click OK.

    The Repository List page appears.

    For more information about configuring the system user, see Configure System User.

Manage Repository Window Fields

The following table explains the fields of the Manage Repository window:

Repository Providers

AVEVA Work Tasks supports the following Repository Providers by default:

Note: The Repository Providers are not the recommended authentication methods for production environments. For enhanced security, AVEVA recommends using industry-standard solutions such as Active Directory or Microsoft Entra ID.

• Active Directory

  When you select Active Directory as the Resource Provider, details such as Active Directory datasource and the Active Directory search base are populated by default.

  Authentication User, Authentication Password, User Log-on ID, and User Log-on Display Name are optional fields. Access to the active directory might not be available for all users. In such cases, provide the active directory authentication user name and the active directory authentication password with which you can connect to the Active Directory.

  AVEVA Work Tasks considers SAM-Account-Name as User Log-on ID by default. If you want to use active directory attributes other than the SAM-Account-Name user, then enter the desired active directory attribute details in the User Log-on ID field and User Log-on Display Name field. User Log-on Display Name is the user friendly display name of the active directory attribute. This User Log-on Display Name is referred in the User Lookup dialog box against the User Log-on ID.

  Steps

  1. When you select Active Directory as the Resource Provider, then the Use Token Service field appears. In this field, select one of the following:

     • If you do not want to use AIM authentication, select Without Token Service.

     • If you want to use AIM authentication, then select a server from the list of alias server names.

  2. Enter Active Directory datasource.

  3. Enter Active Directory search base.

  4. Enter Domain Name.

     The domain name is case-sensitive.

  5. Enter Authentication User.

  6. Enter Authentication Password.

  7. Check Is Cross Domain Role Provider checkbox, if cross domain users and roles mapping is required.

     Example: Users John and Jim of domain TelematicsU and users Mike and Bob from domain TelematicsAU are added to role Team HR of domain TelematicsMain.

  8. Enter User Log-on ID if you want to use another Active Directory attributes instead of SAM-Account-Name.

     We recommend to use attributes of type string as input for User Log-on ID. However, ObjectSID and objectGUID are also supported.

     After you set the User Log-on ID, you cannot change it later.

  9. Enter the User Log-on Display Name.

     After you set the User Log-on Display Name, you cannot change it later.

     This is the default display name of the user account of the active directory user used. User Log-on Display Name is used in user lookups.

  10. Click Test LDAP.

      A message about successful LDAP test appears.

  Note:
  - Some of the active directory attributes or properties are not indexed. If you use an active directory attribute that is not indexed, it might impact the log-on validation performance based on the active directory entries. We recommend to use indexed attributes as User Log-on ID or index the attributes.
  - For an upgraded repository, you cannot change both User Log-on ID and User Log-on Display Name.
  - You cannot localize User Log-on ID and User log-on Display Name fields.
  - Disabled users will not be shown in user lookup search.
  - While configuring Active Directory with token service, ensure that the primary System Management Server (SMS) is online.

• Forms

  If the selected repository data source is of type SQL Server, then Forms provider is of type SQL Server database.

  1. In the Resource Provider drop-down list, select Forms.

  2. In the User Entity properties field, enter XML data.

     Click Sample Code to get the XML Schema Template.

     Example

     <properties>

     <property name="userid" type="string" purpose="identifier" />

     <property name="username" type="string" purpose="name" />

     <property name="pwd" type="string" purpose="password" />

     </properties>

  3. In the User Provider Properties field, enter the same XML Schema.

     There must be at least one identifier in the XML Schema. For example, UserID

  4. In the Datasource field, enter a valid data source or specify a dll.

     The value for the data source can be specified as Physical path of the dll or Physical path of the dll::param. Param is not mandatory.

     See topic Implementation of IDBConnectionString Interface under Data source Related Code Samples sub-chapter in the Build Business Process section for creating the assembly.

     Ensure that there is only one class implementing IDBConnectionString interface within this assembly, whereas one class can return multiple connection strings.

     Examples of data source parameter:

     • c:\DLLStore\GetConnectionString.dll

     • c:\GetConnectionString.dll::Leave

     If there are two data sources, Leave and Licensing, and only one DLL is used to return a connection string based on the data source selected. The parameter can be specified as c:\GetConnectionString.dll::Leave or c:\ GetConnectionString.dll::Licensing. The connection string can be returned from the connection dll based on this parameter.

  5. Enter a proper table name or view name which holds the User Name and Password for the Authentication purpose.

     Example: Passmast (the table which is available in IMS_NEW Database)

  6. Click Test SQL Connection.

     A message about successful test connection appears.

• ASP.NET Membership

  This resource provider lists users defined in the asp.net membership database.

• Repository Provider

  This resource provider allows you to set the password for the system administrator (username: admin), and confirm the password. This password will then be used to access Enterprise Console configured with the Repository Provider.

  The password should have at least one uppercase letter, one lowercase letter, one special character, one number, a minimum length of 8 characters, and no blank spaces.

  For upgrade scenario, refer to Configure Password for Admin User in Silent Mode using XML.

  Note: All characters from A-Z, a-z, and 0-9 are allowed, along with all special characters except space. Foreign special characters are not permitted.

• Lists

  This resource provider lists users created using AVEVA Work Tasks Users Creation. If you are unable to determine a User Provider to create a repository, use AVEVA Work Tasks Lists.

To verify successful creation of the Repository

17. Click Enterprise Console URL from the site path column.

    The repository created is listed.

    Add the created Enterprise Console link into "Add to Favorites" to easily navigate in future.

18. Click Repository User Provider link to logon to the repository.

    The Enterprise Console log-on page appears.

19. Enter the logon details, and then click Login.

    The Enterprise Console home page appears. This indicates successful creation of a Repository.

    All features can only be available for a user with administrative privileges.

Note:
Consider you created the Repository and then deleted it. If you create the same Repository again immediately and try to log into it through Enterprise Console, the Provider does not list the Repository. You need to access IIS and recycle AVEVA Work Tasks from the Application Pool to get the Repository listed in the Provider list.