AppSuite:Context management

From Open-Xchange
Revision as of 17:15, 16 December 2012 by Tierlieb (talk | contribs) (Admin handbook, sadly html-formatted.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
<a class="indexterm" name="id2590615"></a>

createcontext is the tool to create new contexts. A context is an independent instance within the createcontext Open-Xchange system and holds users, groups and resources and all their objects. Data from one context is not visible to other contexts. Module access (calendar, tasks, email) can be set via predefined "access combination names". These names can be configured on the server side. All users which are created during later use of the "createuser" tool will inherit the module access rights from the context. If you do not specify any access rights on createcontext minimal access rights will be granted. Currently, these are Webmail and Contacts access rights.

Parameters

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-h,--helpPrints a help text
--environmentShow info about commandline environment
--nonlRemove all newlines (\n) from output
-c,--contextid <integer>The id of the context, when starting with 0, 0 is deleted
-q,--quota <integer>Context wide filestore quota in MB
-u,--username <string>Username for the new context admin user
-d,--displayname <string>Displayname for the new context admin user
-g,--givenname <string>Given name for the new context admin user
-s,--surname <string>Surname/last name for the new context Admin user
-p,--password <string>Password for the new context Admin user
-e,--email <string>Primary E-Mail address for the new context Admin user
-l,--lang <lang>Language for the new context Admin user
-t,--timezone <timezone>Timezone for the new context Amin user
-N,--contextname <string>Context name
-L,--addmapping <string>Add login mappings separated by ","
--access-combination-name <access-combination-name>Access combination name
--access-denied-portal <on/off>Denies portal access (Default is off)
--csv-import <CSV file> Full path to CSV file with user data to import. This option makes mandatory options obsolete, except credential options (if needed).

--csv-import <CSV file>

Full path to CSV file with user data to import. This option makes mandatory command line options obsolete, except credential options (if needed). But they have to be set in the CSV file.

With this option you can specify a csv file (a full pathname must be given) with the data which should be imported. The columnnames in the CSV file must be the same as the long-options of the command line tools, without the prefix "--".

This option will normally be used to fill new large installations with the new data. So instead of calling the command line tools in a shell script every time, just a csv file needs to be created, containing the whole data.

Note that the credentials of the masteradmin in the createcontext call must be given on the command line with the -A and -P options nevertheless - if authentication is enabled. If the createuser command line tool is used, the credentials are part of the csv file, and cannot be set as options on the command line itself. The reason for this different behavior is that different contexts have different credentials for the admin user, so they must be set in every line of the csv file. Opposed to this the credentials of the masteradmin are always the same.

Extra parameters when authentication is enabled

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-A,--adminuser <string>Master Admin user name
-P,--adminpass <string>Master Admin password

Return value

0 on success

>0 on failure

Mandatory parameters

contextid {adminuser adminpass} quota username displayname givenname surname password email

Command output

On success:

context <contextid> created

On failure:

context <contextid> could not be created: <reason from server>

Example

root@oxhe~# /opt/open-xchange/sbin/createcontext -c 123 -q 1000 -N CompanyA -u "admin" -d "Admin of CompanyA" -g John -s Example -p newpw -e john@example.com

context 123 created

deletecontext

<a class="indexterm" name="id2577690"></a>

deletecontext is the tool to delete contexts and all data stored that belong to it. This includes all database entries and files in the infostore but no E-Mail components.

Parameters

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-h,--helpPrints a help text
--environmentShow info about commandline environment
--nonlRemove all newlines (\n) from output
-c,--contextid <contextid>The id of the context
-N,--contextname <contextname>Context name

Extra parameters when authentication is enabled

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-A,--adminuser <string>Master Admin user name
-P,--adminpass <string>Master Admin password

Return value

0 on success

>0 on failure

Mandatory parameters

(contextid or contexname) {adminuser adminpass}

Command output

On success:

context <contextid> deleted

On failure:

context <contextid> could not be deleted: <reason from server>

Example

root@oxhe~# /opt/open-xchange/sbin/deletecontext -c 123

context 123 deleted

listcontext

<a class="indexterm" name="id2523861"></a>

listcontext is the tool to list and search for contexts.

Parameters

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-h,--helpPrints a help text
--environmentShow info about commandline environment
--nonlRemove all newlines (\n) from output
-s,--searchpattern <string>Search/List pattern, default “*
--csvCommand output as csv

Extra parameters when authentication is enabled

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-A,--adminuser <adminuser>Master Admin user name
-P,--adminpass <string>Master Admin password

Return value

0 on success

>0 on failure

Mandatory parameters

{adminuser adminpass}

Command output

Standard output:

cid fid fname       enabled qmax qused name        lmappings
  .   . ...         ...     ...    ... ...         ...

csv output:

id,filestore_id,filestore_name,enabled,max_quota,used_quota,name,lmappings

Example

root@oxhe:/opt/open-xchange/sbin# ./listcontexts

cid fid fname enabled qmax qused name lmappings

6 3 6_ctx_store true 1000 0 customerA 6,customerA,secondlogin


disablecontext

<a class="indexterm" name="id2591992"></a>

disablecontext is the tool to disable contexts. Whenever a customer tries to log in to a disabled context, the login is denied.

Parameters

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-h,--helpPrints a help text
--environmentShow info about commandline environment
--nonlRemove all newlines (\n) from output
-c,--contextid <integer>The id of the context
-N,--contextname <string>Context name

Extra parameters when authentication is enabled

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-A,--adminuser <string>Master Admin user name
-P,--adminpass <string>Master Admin password

Return value

0 on success

>0 on failure

Mandatory parameters

(contextid or contextname) {adminuser adminpass}

Command output

On success:

context <contextid> disabled

On failure:

context <contextid> could not be disabled: <reason from server>

Example

root@oxhe~# /opt/open-xchange/sbin/disablecontext -c 123

context 123 disabled


disableallcontexts

<a class="indexterm" name="id2592248"></a>

disableallcontexts is the tool to disable all contexts. Whenever a customer tries to log in to a disabled context, the login is denied.

Parameters

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-h,--helpPrints a help text
--environmentShow info about commandline environment
--nonlRemove all newlines (\n) from output

Extra parameters when authentication is enabled

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-A,--adminuser <string>Master Admin user name
-P,--adminpass <string>Master Admin password

Return value

0 on success

>0 on failure

Mandatory parameters

{adminuser adminpass}

Command output

On success:

all contexts disabled

On failure:

all contexts could not be disabled: <reason from server>

Example

root@oxhe~# /opt/open-xchange/sbin/disableallcontexts

all contexts disabled


enablecontext

<a class="indexterm" name="id2592489"></a>

enablecontext is the tool to enable a disabled context.

Parameters

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-h,--helpPrints a help text
--environmentShow info about commandline environment
--nonlRemove all newlines (\n) from output
-c,--contextid <integer>The id of the context
-N,--contextname <string>Context name

Extra parameters when authentication is enabled

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-A,--adminuser <adminuser>Master Admin user name
-P,--adminpass <string>Master Admin password

Return value

0 on success

>0 on failure

Mandatory parameters

(contextid or contextname) {adminuser adminpass}

Command output

On success:

context <contextid> enabled

On failure:

context <contextid> could not be enabled: <reason from server>

Example

root@oxhe~# /opt/open-xchange/sbin/enablecontext -c 123

context <contextid> enabled


enableallcontexts

<a class="indexterm" name="id2592740"></a>

enableallcontexts is the tool to enable all disabled contexts.

Parameters

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-h,--helpPrints a help text
--environmentShow info about commandline environment
--nonlRemove all newlines (\n) from output

Extra parameters when authentication is enabled

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-A,--adminuser <string>Master Admin user name
-P,--adminpass <string>Master Admin password

Return value

0 on success

>0 on failure

Mandatory parameters

{adminuser adminpass}

Command output

On success:

all contexts enabled

On failure:

all contexts could not be enabled: <reason from server>

Example

root@oxhe~# /opt/open-xchange/sbin/enableallcontexts

all contexts enabled


changecontext

<a class="indexterm" name="id2592976"></a>

changecontext is the tool to change the current quota for a given context. When the context has more changecontext space in use than the new quota allows, the customer is only able to delete files until the usage is below quota. Module access (calendar,tasks,email)can be set via predefined "access combination names". These names can be configured on the server side. All users which are created during later use of the "createuser" tool will inherit the module access rights from the context. If you do not specify any access rights on createcontext minimal access rights will be granted. Currently, these are Webmail and Contacts access rights.

There are some default combinations in the ModuleAccessDefinitions.properties file on the admin server, like:

<tbody></tbody>
webmail=webmail, contacts, globaladdressbookdisabled, collectemailaddresses,editpassword
pim=webmail, calendar, contacts, tasks, globaladdressbookdisabled, collectemailaddresses, multiplemailaccounts, subscription, publication,editpassword
pim_infostore=webmail, calendar, contacts, tasks, infostore, webdav, globaladdressbookdisabled, collectemailaddresses, multiplemailaccounts, subscription, publication
pim_mobility=webmail,calendar,contacts,tasks,syncml,usm, activesync,globaladdressbookdisabled,collectemailaddresses,multiplemailaccounts,subscription,publication, editpassword
groupware_standard=webmail,calendar,contacts,infostore,tasks,webdav,ical,vcard,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,collectemailaddresses,multiplemailaccounts,subscription,publication (Groupware Standard always gets new features except mobility and OXtender. )
groupware_premium=webmail,calendar,contacts,infostore,tasks,webdav,webdavxml,ical,vcard,syncml,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,collectemailaddresses,multiplemailaccounts,subscription,publication
all=webmail,calendar,contacts,infostore,tasks,webdav,webdavxml,ical,vcard,syncml,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,publicfoldereditable,collectemailaddresses,multiplemailaccounts,subscription,publication

When having changed the access rights of the context and its users with "changecontext" the "downgrade" command should be called on the admin server. All unnecessary data are removed from the data base via "groupware api". If e. g. the context 1 is changed from "pim_infostore" to "webmail", the "downgrade" command has to be called for this context then. Then, all unnecessary folders for this context are removed from the data base.

Parameters

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-h,- -helpPrints a help text
--environmentShow info about commandline environment
--nonlRemove all newlines (\n) from output
-c,- -contextid <integer>The id of the context
-N,- -contextname <string>The name of the context
-L,- -addmapping <string(s)>Add login mappings. Separated by ","
-R,- -removemapping <stirng(s)>Remove login mappings. Separated by ","
-q,- -quota <integer>Quota for the context filestore in MB
--access-combination-name <access-combination-name>Access combination name

Extra parameters when authentication is enabled

<colgroup><col align="left"><col align="left"></colgroup><tbody></tbody>
-A,- -adminuser <string>Master Admin user name
-P,- -adminpass <string>Master Admin password

Return value

0 on success

>0 on failure

Mandatory parameters

(contextid or contextname) {adminuser adminpass} and at minimum one attribute to change

Command output

On success:

context <contextid> changed

On failure:

context <contextid> could not be changed: <reason from server>

Example

root@oxhe~# /opt/open-xchange/sbin/changecontext -c 123 -q 500

context 123 changed


getAdminId

<a class="indexterm" name="id2593384"></a>

Returns the ID of the context administrator.