|Newbie questions about Pliant
Appending user pdb files
|Message posted by marcus on 2004/11/14 21:05:38
|I have two applications hosted on different servers, say, server1 and server2.
I want to host both on server1.
Would the procedure below do the trick?
- halt both servers
- append the user.pdb and user2.pdb files of both servers and create new user.pdb
and user2.pdb files for server1
- copy the tree containing the application on to server1
- restart server1
|Message posted by hubert.tonneau on 2004/11/14 21:32:51
|Appending files while the servers are not running should be ok,
provided you do not have '<precovery ...>' lines in the database files.
To remove these, use 'Store databases' in the status page while the server is
Moving datas while the servers are running is also possible through the
data browser (download from one, upload to the other), also it only works
for datas that are mapped to Pliant datatabase datas tree (not mapping all
datas is a stupid idea I had in Pliant early days to try to improve
(*) Stupid means that there are nowdays plenty of mapped datas that beeing
abble to modify is enough to corrupt the all server security, so have
some not mapped is not much security improvement.
|Message posted by marcus on 2004/11/22 21:24:10
|I have uploaded the contents of pliant/browse/data/pliant/user/ from server1
to server2. But it seems this not enough to be able to login to server2 as a
user of server1.
What else do I need to upload from server1?
Another question: do I need to also upload /pliant/browse/data/pliant2 from
server1 to server2?
|Message posted by hubert.tonneau on 2004/12/04 10:53:23
|I've been late to answer. Please apology.
A user account is shared on three database:
user.pdb contains roughly the user name, and rights.
user2.pdb contains roughly some of his private datas.
user_secret.pdb roughly contains his password.
So, if you want to copy tables, you have to copy all of them.
Now, there is a way to do that live:
1) check that the remote execution is on ('configure' 'remote execution'
'Remote execution global settings for this computer' and 'Test remote access')
2) configure shared user accounts ('configure' 'users'
'Users database client and server global settings for this computer')
When an account is modified on a server computer, it will be automatically
forwarded to the client computers.
3) use the new 'Broadcast all users account' on one of the servers containing
the accounts to send all of them to the client computers at once if you
don't start with user databases up to date on all computers.