The Repositories area in Evoke is where you define the actual, physical, back end databases that will be accessed and used by the App. These may be via direct access, via stored procedures or through an intermediate API, it is entirely up to you.
Data Repositories Definition
For each Repository (database) that you want your App to have access to you simply set up a Repository definition. Use the + symbol in the header or the eplipsys to add a new repository definition or remove an existing one.
Extensive video guidence for repository definition setup is available in the Important setup information for Evoke. If you have previously configured a datbase and wish to add, change or swap one, please review the description of Swapping or changing Databases for details of the steps required.
The following information is required for each repository definition:
  • ID - The name you wish to associate with this repository

  • Repository Technology - identify the type of database as either a) SQL b) MultiValue or c) a Custom Data Environment

  • Platform - the 'flavour' of the database e.g. SQLServer, MySQL, Oracle, etc for SQL or jBASE, Universe, D3, mvBASE, etc for MultiValue

  • Connection Type - select the 'Connection Type" you want to use to connect to the database, this will also identify the actual physical location of the database and address the security requirements to access. The connection type is dependent on the flavour of the database. Examples of the connectivity products are Dynamic DML using ADO.Net or ODP.Net client libraries/Stored Procedures for SQL or mv.Net Core Objects/U2 data client library for MultiValue. other connectivity products are available.

  • Connection String (SQL) - your DBA will need to provide the 'Connection String', although the "Build" button will help identify the string components

  • Login Profile Name (MultiValue) - the connection product profile name (usually the name of your database in the connectivity product)

  • Connection Password (SQL) - the password for SQL databases that you have set for your database

  • Repository Object Prefix - if your database, uses a prefix for repositiory objects, this is entered here

  • Options - additional, database specific options are entered here

Connecting and Scanning your database
Once you have set up your repository, use the elipsys menu to select from the following:
  • Test Connection - check that the connection to your database repository is set up correctly and that the connection works

  • DownLoad Evoke Utilities (MultiValue Database Only) - downloads utilities required for implementing Evoke specific CRUD.

  • Scan For Repository Objects - Scans the repository and populates the repository objects list with the names of any tables/files that are found in the repository.

Repository Objects
Once you have scanned your repository and populated the list of repository objects, you will see a full list of the visible objects (files) accessable from Evoke in your physical database (see example image).
Although you will probably not want to use all of your respository objects in your app design you will certainly want to use a few of them and for each of the ones you want to use you will need an Entity definition.
You can manually create you Entity definitions or alternatively you can import the Entity Definitions from the physical object/file structure.

You can set up as many repository definitions, with connectivity to different databases, as you wish within each Evoke App.