Docs‎ > ‎Live Logic Tutorial‎ > ‎

Sample Project


You would use a similar procedure for your own projects.


Sample Databases

Espresso provides 3 sample databases:
  • Northwind - located on an cloud-based Espresso server, this is installed as part of your Tour when you first start the Designer

  • Logic Demo - a simple database of 6 tables, used to illustrated basic concepts

  • Logic Sample - a database of few dozen tables, used in the Logic Tutorial to illustrate advanced rules and database concepts

Account Types

There are a number of different Account Types, summarized in the table below.  Your account type determines whether the Demo and Sample Databases are available, or require installation

 Account Type  How can I tell
 Logic Demo DB, Project
 Logic Sample
DB
 Logic Sample Project
 Eval
  • You clicked the red Try It Now button on the website
  • Your URL looks like https://eval.espressologic.com/LogicDesigner/...
 Automatically installed  Automatically created  Not created - Import project as described on this page
  Cloud Account
  • You signed up for a Cloud-based Developer/Production account
  • Your Url looks like: https://<yourAccount>.my.espressologic.com/LogicDesigner
 Automatically installed  Automatically installed  
  On-premise war   Not created - use the procedures on this page   Not created - use the procedures on this page  Not created - use the procedures on this page
  Appliance
  • You installed the Appliance
  • Your URL looks like 10.0.1.15/LogicDesigner/#/
 Automatically installed  Automatically installed  Automatically installed


Create or Verify Demo and Sample Databases

The first step is to create the 2 sample databases for war file installations, or otherwise verify them.

War File accounts - Create databases

If you are using the war file, you must create the Logic Demo and Logic Sample databases.

We recommend naming these as shown below:
  1. Download and unpack the project export file.  These contain, for both Logic Demo and Logic Sample:
    1. json Project export files, created using the project export procedure.
    2. sql files, to initialize the schema and data

  2. Create the espresso_demo and espresso_sample schemas, as shown here.

    Use the  same procedures you used to create the espresso_adm_db Database

  3. Load the schema and sample data from the supplied .sql file

Other Accounts - verify

In other cases, the Sample Database was already created while building your server. 

You can verify it in your favorite database tools, or by using phpMyAdmin:

The credentials were supplied in your registration email, shown below.  So for user val, login to phpMyAdmin as val_sam (val_demo would be used to access the smaller demo database):



Load JavaScript Libraries (FIXME - remove)

If you are using the war file, you will need to 

Create Sample Projects

Projects are the definitions you create for your Data Sources, your API (Custom Resources, etc), your logic and your security.  Just like projects you create, the sample projects have been exported into a json export file.  Import them as shown below.
  1. Perform the procedures below once for Logic Sample, and once (as required) for Logic Demo.

Create Project from Import

Download the export, and import it to create a new project, as follows:
  1. If your have not already done so, download and unpack the project export file.  These contain, for both Logic Demo and Logic Sample:
    1. Json Project export files, created using the project export procedure.
    2. sql files, to initialize the schema and data

  2. Click Import

  3. Select Choose File, and select the unpacked file json from above


Project Fixup

The json export file does not include passwords and other key security information.  You will therefore need to make a few small updates to your project, as described below.

  1. You will need to uncheck Short Menus


Database Definition

You must first update the Database URL and Catalog as shown below.  The proper credentials depend on your Account Type:
  1. War Install - use the defaults, and specify the Password as password!
  2. Otherwise - obtain the values from your registration email (see screen shot above)

Project URL and Authorization Provider

The import defaults several project properties as shown below - fix them as shown below:
      1. Access Project Properties on the left navigation var
      2. You will have to correct the Authorization Provider.  
      3. For your own projects, you will also need to fix:
        1. Project Name
      4. Project Name
        1. URL Fragment
      5. URL Fragment



User Passwords

If you are using the Default Authentication Manager, you will need to update your Passwords.  
    1. For the sample databases, specify Password1



Verify Operation


ċ
Sample Databases.zip
(350k)
Val Huber,
Apr 30, 2015, 6:36 PM