Not covered here.
However once you have installed the on-premise Rollbase you may want to set up multiple tenants in order to separate the various demos and to establish different user accounts that can access different segments of your Rollbase instance
You can download this from the DDC website http://www.datadirectcloud.com/
Make sure to install as administrator.
Once installed you can use the configuration tool to generate your unique id that enables DDC to access your machine:
You should use your progress id and password (the same one you use to access DDC)
Login to DDC
Choose DDC then data sources then Rollbase On-Premise
Enter datasource details
Turn off encryption – doesn’t seem to work if its on.
Choose SQL Testing
Choose your datasource from the drop down
If you get this message
Make sure your Rollbase instance is started.
Run this query
In the results you should see all of the users that are defined for that tenant in Rollbase based on the user id and password you entered in the datasource screen.
Set your database connection parameters for the vocabulary like this
Test the connection
Create an Entity
Set its persistence property to yes:
If you do not know the name of the table then select from the drop down:
If you do know the name then just type that for the entity name and Corticon will match the correct table.
For example User and Patient:
Now add attributes in the same way.
Make sure to choose the correct data type:
Create a rule sheet
To run a quick test, create a rule sheet like this:
Make sure to select “Extend to Database” on the entities:
Make sure to set it to Read/Update
Now run the test (you don’t need any input)
If you delete any instance of your objects (using the .remove operator) or if you create any new objects (using the .new operator) these changes will be reflected in your Rollbase database – so exercise care.
Particularly so with the remove operator. Make sure you use it with a carefully scoped alias.
If you inadvertently use X.remove (where X is an entity name) then ALL objects of type X will be deleted from your database.
You might be able to configure the data source to prevent updates using the advanced tab: