Hi all
What's the best method of installing, setting up Ebase for 2 councils. Forms are to be the same, but templating and data sources are different.
Anyone who'd had experience with that? Any suggestions welcome.
Kind regards
Josh
Setting single Ebase up for 2 different councils
Moderators: Jon, Steve, Ian, Dave
-
- Ebase User
- Posts: 19
- Joined: Fri Oct 24, 2008 1:55 pm
- Location: WFH, Oxfordshire, UK
- Contact:
- Joost
- Ebase User
- Posts: 49
- Joined: Fri Sep 14, 2007 6:14 pm
- Location: The Netherlands
Re: Setting single Ebase up for 2 different councils
By naming the template and datasource the same you may use the deployment manager to put the form on two Ebase enironments at once.JoshuaW wrote:setting up Ebase for 2 councils. Forms are to be the same, but templating and data sources are different.
http://portal.ebasetech.com/cp/doc/Depl ... anager.htm
If only different tables are used in the same database you may consider using parameters in the database resource to distinguish which table you want. Eg. TABLENAME_&&PARAMETER
In both cases you may use a single Tomcat with two Ebase environments. Or two Tomcat's each with one Ebase environment. The first is a little easier to setup but will share at least Tomcat thus if it goes down for maintenance all environments are down.
0 x
- Wai
- Moderator
- Posts: 165
- Joined: Wed Sep 12, 2007 9:04 am
- Location: Sandy, UK
- Contact:
If you have one Ebase instance with one web application and one Ebase repository:
It's possible to change the template at runtime based on the Council the forms are running for, so you can design different templates for each council.
Councils will share the repository but you will have to have its own datasources defined for application data.
It's possible to change the template at runtime based on the Council the forms are running for, so you can design different templates for each council.
Councils will share the repository but you will have to have its own datasources defined for application data.
0 x
-
- Moderator
- Posts: 184
- Joined: Tue Sep 11, 2007 8:58 am
Also consider dynamic databases, suitable only when same database resources / dynamic lists/ stored procedures are required to run, but the physical database is different - normally determined by some logic.
Just as you can dynamically set the template - using fpl: you can also set the database to be used - using fpl:
Example fpl, probably in a before form event:
or, even better:
Full details available in the online documentation (search for $DATABASE)
Just as you can dynamically set the template - using fpl:
Code: Select all
set template my_template;
Code: Select all
set $DATABASE = 'A_DATABASE_ELEMENT_DEFINED_IN_DESIGNER';
Code: Select all
if [CUST_ID = 1]
set template CUST_TEMPLATE_1;
set $DATABASE = 'CUST_DB_1';
endif
if [CUST_ID = 2]
set template CUST_TEMPLATE_2;
set $DATABASE = 'CUST_DB_2';
endif
Code: Select all
set cust_command = 'set template CUST_TEMPLATE_' + tostring(CUST_ID);
interpret cust_command;
set cust_command = 'set $DATABASE = ' + QUOT + 'CUST_DB_'+ tostring(CUST_ID) + QUOT; // QUOT is a form field containing a single quote character as its default value
interpret cust_command;
0 x
Who is online
Users browsing this forum: No registered users and 59 guests