29
28
you'll have to find somebody who does have it to create this seed database.
31
30
.. i18n: .. index::
32
.. i18n: single: password; super-administrator
33
.. i18n: single: password; superadmin
31
.. i18n: single: password; super-administrator
32
.. i18n: single: password; superadmin
36
35
single: password; super-administrator
37
36
single: password; superadmin
39
38
.. i18n: .. note:: The super-administrator password
40
.. i18n: Anyone who knows the super-administrator password has complete access to the data on the server
41
.. i18n: – able to read, change and delete any of the data in any of the databases there.
43
.. i18n: After first installation, the password is ``admin``. This is the hard-coded default, and
44
.. i18n: is used if there is no accessible server configuration file. If your system has been
45
.. i18n: set up so that the server configuration file can be written to by the server then
46
.. i18n: you can change the password through the client. Or you could deliberately make the
47
.. i18n: configuration file read-only so that there is no prospect of changing it from the client.
48
.. i18n: Either way, a server systems administrator can change it if you forget it.
50
.. i18n: So if your system is set u to allow it, you can change the superadmin password through the GTK client
51
.. i18n: from the menu :menuselection:`File --> Databases --> Administrator Password`, or through the
52
.. i18n: web client by logging out (click the :guilabel:`Logout` link), clicking :guilabel:`Databases` on the
53
.. i18n: login screen, and then clicking the :guilabel:`Password` button on the Management screen.
55
.. i18n: The location of the server configuration file is typically defined by starting the server with
56
.. i18n: the ``--config`` command line option.
58
.. note:: The super-administrator password
41
60
Anyone who knows the super-administrator password has complete access to the data on the server
42
61
– able to read, change and delete any of the data in any of the databases there.
44
.. i18n: Anyone who knows the super-administrator password has complete access to the data on the server
45
.. i18n: – able to read, change and delete any of the data in any of the databases there.
47
After first installation, the password is ``admin``. This is the hard-coded default, and
48
is used if there is no accessible server configuration file. If your system has been
49
set up so that the server configuration file can be written to by the server then
50
you can change the password through the client. Or you could deliberately make the
51
configuration file read-only so that there is no prospect of changing it from the client.
52
Either way, a server systems administrator can change it if you forget it.
54
So if your system is set u to allow it, you can change the superadmin password through the GTK client
55
from the menu :menuselection:`File --> Databases --> Administrator Password`, or through the
56
web client by logging out (click the :guilabel:`Logout` link), clicking :guilabel:`Databases` on the
57
login screen, and then clicking the :guilabel:`Password` button on the Management screen.
59
The location of the server configuration file is typically defined by starting the server with
60
the ``--config`` command line option.
62
.. i18n: After first installation, the password is ``admin``. This is the hard-coded default, and
63
.. i18n: is used if there is no accessible server configuration file. If your system has been
64
.. i18n: set up so that the server configuration file can be written to by the server then
65
.. i18n: you can change the password through the client. Or you could deliberately make the
66
.. i18n: configuration file read-only so that there is no prospect of changing it from the client.
67
.. i18n: Either way, a server systems administrator can change it if you forget it.
69
.. i18n: So if your system is set u to allow it, you can change the superadmin password through the GTK client
70
.. i18n: from the menu :menuselection:`File --> Databases --> Administrator Password`, or through the
71
.. i18n: web client by logging out (click the :guilabel:`Logout` link), clicking :guilabel:`Databases` on the
72
.. i18n: login screen, and then clicking the :guilabel:`Password` button on the Management screen.
74
.. i18n: The location of the server configuration file is typically defined by starting the server with
75
.. i18n: the ``--config`` command line option.
77
63
After first installation, the password is ``admin``. This is the hard-coded default, and
78
64
is used if there is no accessible server configuration file. If your system has been
79
65
set up so that the server configuration file can be written to by the server then
121
108
.. i18n: .. figure:: images/create_new_db_GTK.png
123
.. i18n: :align: center
125
*Creating a new database through the GTK client*.. i18n:
127
.. i18n: *Creating a new database through the GTK client*
110
.. i18n: :align: center
112
.. i18n: *Creating a new database through the GTK client*
114
.. figure:: images/create_new_db_GTK.png
129
118
*Creating a new database through the GTK client*
131
120
.. i18n: If you're using the web client, click :guilabel:`Databases` on the login screen, then
132
121
.. i18n: :guilabel:`Create` on the database management page. Enter the super-administrator password, and the
133
122
.. i18n: name of the new database you're creating.
135
124
.. i18n: In both cases you'll see a checkbox that determines whether you load demonstration data or not.
136
125
.. i18n: The consequences of checking this box or not affect the **whole use** of this database.
183
172
single: access; user
185
174
.. i18n: .. tip:: User Access
176
.. i18n: The combination of username/password is specific to a single database. If you have administrative
177
.. i18n: rights to a database you can modify all users.
180
.. i18n: single: module; users_ldap
182
.. i18n: Alternatively you can install the :mod:`users_ldap` module, which manages the authentication of users
183
.. i18n: in LDAP (the Lightweight Directory Access Protocol, a standard system), and connect it to several
184
.. i18n: Open ERP databases. Using this, many databases can share the same user account details.
187
188
The combination of username/password is specific to a single database. If you have administrative
188
189
rights to a database you can modify all users.
190
.. i18n: The combination of username/password is specific to a single database. If you have administrative
191
.. i18n: rights to a database you can modify all users.
194
192
single: module; users_ldap
197
.. i18n: single: module; users_ldap
199
Alternatively you can install the :mod:`users_ldap` module, which manages the authentication of users
200
in LDAP (the Lightweight Directory Access Protocol, a standard system), and connect it to several
201
Open ERP databases. Using this, many databases can share the same user account details.
203
.. i18n: Alternatively you can install the :mod:`users_ldap` module, which manages the authentication of users
204
.. i18n: in LDAP (the Lightweight Directory Access Protocol, a standard system), and connect it to several
205
.. i18n: Open ERP databases. Using this, many databases can share the same user account details.
207
194
Alternatively you can install the :mod:`users_ldap` module, which manages the authentication of users
208
195
in LDAP (the Lightweight Directory Access Protocol, a standard system), and connect it to several
209
196
Open ERP databases. Using this, many databases can share the same user account details.
211
198
.. i18n: .. note:: Failure to create a database
213
How do you know if you've successfully created your new database?
214
You're told if the database creation has been unsuccessful.
215
If you have entered a database name using prohibited characters (or no name, or too short a name)
216
you will be alerted by the dialog box :guilabel:`Bad database name!` explaining how to correct the error.
217
If you've entered the wrong super-administrator password or a name already in use
218
(some names can be reserved without your knowledge), you'll be alerted by the dialog box
219
:guilabel:`Error during database creation!`.
221
.. i18n: How do you know if you've successfully created your new database?
222
.. i18n: You're told if the database creation has been unsuccessful.
223
.. i18n: If you have entered a database name using prohibited characters (or no name, or too short a name)
224
.. i18n: you will be alerted by the dialog box :guilabel:`Bad database name!` explaining how to correct the error.
225
.. i18n: If you've entered the wrong super-administrator password or a name already in use
226
.. i18n: (some names can be reserved without your knowledge), you'll be alerted by the dialog box
227
.. i18n: :guilabel:`Error during database creation!`.
200
.. i18n: How do you know if you've successfully created your new database?
201
.. i18n: You're told if the database creation has been unsuccessful.
202
.. i18n: If you have entered a database name using prohibited characters (or no name, or too short a name)
203
.. i18n: you will be alerted by the dialog box :guilabel:`Bad database name!` explaining how to correct the error.
204
.. i18n: If you've entered the wrong super-administrator password or a name already in use
205
.. i18n: (some names can be reserved without your knowledge), you'll be alerted by the dialog box
206
.. i18n: :guilabel:`Error during database creation!`.
208
.. note:: Failure to create a database
229
210
How do you know if you've successfully created your new database?
230
211
You're told if the database creation has been unsuccessful.
246
227
If this is the first time you've connected to this database you'll be asked a series of questions to
247
228
define the database parameters:
249
.. i18n: #. :guilabel:`Select a profile` : select \ ``Minimal Profile``\ and click :guilabel:`Next`.
230
.. i18n: #. :guilabel:`Select a profile` : select \ ``Minimal Profile``\ and click :guilabel:`Next`.
232
.. i18n: #. :guilabel:`Company Details` : replace the proposed default of \ ``Tiny sprl``\ by your own
233
.. i18n: company name, complete as much of your address as you like, and add some lines about your company,
234
.. i18n: such as a slogan and any statutory requirements, to the header and footer fields. Click
235
.. i18n: :guilabel:`Next`.
237
.. i18n: #. :guilabel:`Summary` : check the information and go back to make any modifications you need
238
.. i18n: before installation. Then click :guilabel:`Install`.
240
.. i18n: #. :guilabel:`Installation Completed` : click :guilabel:`Ok`.
242
#. :guilabel:`Select a profile` : select \ ``Minimal Profile``\ and click :guilabel:`Next`.
251
244
#. :guilabel:`Company Details` : replace the proposed default of \ ``Tiny sprl``\ by your own
252
245
company name, complete as much of your address as you like, and add some lines about your company,
253
246
such as a slogan and any statutory requirements, to the header and footer fields. Click
254
247
:guilabel:`Next`.
256
.. i18n: #. :guilabel:`Company Details` : replace the proposed default of \ ``Tiny sprl``\ by your own
257
.. i18n: company name, complete as much of your address as you like, and add some lines about your company,
258
.. i18n: such as a slogan and any statutory requirements, to the header and footer fields. Click
259
.. i18n: :guilabel:`Next`.
261
249
#. :guilabel:`Summary` : check the information and go back to make any modifications you need
262
250
before installation. Then click :guilabel:`Install`.
264
.. i18n: #. :guilabel:`Summary` : check the information and go back to make any modifications you need
265
.. i18n: before installation. Then click :guilabel:`Install`.
267
#. :guilabel:`Installation Completed` : click :guilabel:`Ok`.
269
.. i18n: #. :guilabel:`Installation Completed` : click :guilabel:`Ok`.
271
252
#. :guilabel:`Installation Completed` : click :guilabel:`Ok`.
273
254
.. i18n: Once configuration is complete you're connected to your Open ERP system. Its functionality is very
325
308
:guilabel:`Login` screen.
327
310
.. i18n: .. index::
328
.. i18n: single: database; duplicate
311
.. i18n: single: database; duplicate
331
314
single: database; duplicate
333
316
.. i18n: .. tip:: Duplicating a database
318
.. i18n: To duplicate a database you can:
320
.. i18n: #. make a backup file on your PC from this database.
322
.. i18n: #. restore this database from the backup file on your PC, giving it a new name as you do so.
324
.. i18n: This can be a useful way of making a test database from a production database. You can try out the
325
.. i18n: operation of a new configuration, new modules, or just the import of new data.
327
.. tip:: Duplicating a database
335
329
To duplicate a database you can:
337
.. i18n: To duplicate a database you can:
339
331
#. make a backup file on your PC from this database.
341
.. i18n: #. make a backup file on your PC from this database.
343
333
#. restore this database from the backup file on your PC, giving it a new name as you do so.
345
.. i18n: #. restore this database from the backup file on your PC, giving it a new name as you do so.
347
This can be a useful way of making a test database from a production database. You can try out the
348
operation of a new configuration, new modules, or just the import of new data.
350
.. i18n: This can be a useful way of making a test database from a production database. You can try out the
351
.. i18n: operation of a new configuration, new modules, or just the import of new data.
353
335
This can be a useful way of making a test database from a production database. You can try out the
354
336
operation of a new configuration, new modules, or just the import of new data.
356
338
.. i18n: .. index::
357
.. i18n: single: access
339
.. i18n: single: access
390
372
What if want to update what's there, or extend what's there with additional modules?
392
374
.. i18n: * To update what you have, you'd install a new instance of Open ERP using the same techniques as
393
.. i18n: described earlier in this section, :ref:`sect-dbcreate`.
395
* To extend what you have, you'd install new modules in the ``addons`` directory of your current
396
Open ERP installation. There are several ways of doing that.
375
.. i18n: described earlier in this section, :ref:`sect-dbcreate`.
398
377
.. i18n: * To extend what you have, you'd install new modules in the ``addons`` directory of your current
399
.. i18n: Open ERP installation. There are several ways of doing that.
378
.. i18n: Open ERP installation. There are several ways of doing that.
380
* To update what you have, you'd install a new instance of Open ERP using the same techniques as
381
described earlier in this section, :ref:`sect-dbcreate`.
401
383
* To extend what you have, you'd install new modules in the ``addons`` directory of your current
402
384
Open ERP installation. There are several ways of doing that.
404
386
.. i18n: .. index::
405
.. i18n: pair: system; administrator
387
.. i18n: pair: system; administrator
408
390
pair: system; administrator
472
454
server by the server software).
474
456
.. i18n: .. index::
475
.. i18n: pair: filesystem; permissions
457
.. i18n: pair: filesystem; permissions
478
460
pair: filesystem; permissions
480
462
.. i18n: .. tip:: Changing permissions
482
A very simple way of changing permissions on the Linux system you're using to develop an Open ERP
483
application is to execute the command sudo chmod 777 <path_to_addons> (where <path_to_addons> is
484
the full path to the addons directory, a location like /usr/lib/python2.5/site-packages/openerp-
487
.. i18n: A very simple way of changing permissions on the Linux system you're using to develop an Open ERP
488
.. i18n: application is to execute the command sudo chmod 777 <path_to_addons> (where <path_to_addons> is
489
.. i18n: the full path to the addons directory, a location like /usr/lib/python2.5/site-packages/openerp-
490
.. i18n: server/addons).
464
.. i18n: A very simple way of changing permissions on the Linux system you're using to develop an Open ERP
465
.. i18n: application is to execute the command sudo chmod 777 <path_to_addons> (where <path_to_addons> is
466
.. i18n: the full path to the addons directory, a location like /usr/lib/python2.5/site-packages/openerp-
467
.. i18n: server/addons).
469
.. tip:: Changing permissions
492
471
A very simple way of changing permissions on the Linux system you're using to develop an Open ERP
493
472
application is to execute the command sudo chmod 777 <path_to_addons> (where <path_to_addons> is
added
removed
i18n/vi/source/book/1/1_1_Inst_Config/1_1_Inst_Config_db_create.rst
