Safely changing a store to inactive or active - Revision history

Msartor at 10:37, 30 December 2010

2010-12-30T10:37:32Z

← Older revision		Revision as of 10:37, 30 December 2010
Line 6:		Line 6:
	You need to do two changes per store:		You need to do two changes per store:
	* Change the type of the store in the database		* Change the type of the store in the database
-	* Change the LDAP attribute of the store (e.g. in OpenLDAP with the zarafa-schema the attribute: zarafaSharedStoreOnly)	+	* Change the LDAP attribute of the store (e.g. in OpenLDAP with the zarafa-schema the attribute: zarafaSharedStoreOnly) - Check in you ldap config which attribute is used.

Msartor at 09:48, 30 December 2010

2010-12-30T09:48:37Z

← Older revision		Revision as of 09:48, 30 December 2010
Line 6:		Line 6:
	You need to do two changes per store:		You need to do two changes per store:
	* Change the type of the store in the database		* Change the type of the store in the database
-	* Change the LDAP attribute of the store	+	* Change the LDAP attribute of the store (e.g. in OpenLDAP with the zarafa-schema the attribute: zarafaSharedStoreOnly)

Msartor at 09:44, 30 December 2010

2010-12-30T09:44:22Z

← Older revision		Revision as of 09:44, 30 December 2010
Line 7:		Line 7:
	* Change the type of the store in the database		* Change the type of the store in the database
	* Change the LDAP attribute of the store		* Change the LDAP attribute of the store
		+

	The MySQL changes you need to do are in the users table. The users table has the following fields:		The MySQL changes you need to do are in the users table. The users table has the following fields:

Msartor at 09:44, 30 December 2010

2010-12-30T09:44:12Z

← Older revision		Revision as of 09:44, 30 December 2010
Line 5:		Line 5:
	==Explanation of fields==		==Explanation of fields==
	You need to do two changes per store:		You need to do two changes per store:
-	- Change the type of the store in the database	+	* Change the type of the store in the database
-	- Change the LDAP attribute of the store	+	* Change the LDAP attribute of the store

	The MySQL changes you need to do are in the users table. The users table has the following fields:		The MySQL changes you need to do are in the users table. The users table has the following fields:

Gertvdijk: removed incorrect comment in php script

2010-11-12T08:43:00Z

removed incorrect comment in php script

← Older revision		Revision as of 08:43, 12 November 2010
Line 59:		Line 59:
	$zarafa_pass="";		$zarafa_pass="";
	$zarafa_sock="file:///var/run/zarafa";		$zarafa_sock="file:///var/run/zarafa";
-
-
-	/*
-	* Updates all users' free/busy information
-	*/

	include('/usr/share/php/mapi/mapi.util.php');		include('/usr/share/php/mapi/mapi.util.php');

Ddebyttere at 08:55, 12 July 2010

2010-07-12T08:55:53Z

← Older revision		Revision as of 08:55, 12 July 2010
Line 1:		Line 1:
	This page will describe how to change a store to active or inactive preserving the data that is in the store.		This page will describe how to change a store to active or inactive preserving the data that is in the store.

-	This page only applies to Zarafa versions < 6.40 (in Zarafa 6.40 or higher, you are able to change active <-> inactive on the fly, without Zarafa orphaning the store).	+	'''This page only applies to Zarafa versions < 6.40''' (in Zarafa 6.40 or higher, you are able to change active <-> inactive on the fly, without Zarafa orphaning the store).

	==Explanation of fields==		==Explanation of fields==

Msartor at 14:36, 30 March 2010

2010-03-30T14:36:02Z

← Older revision		Revision as of 14:36, 30 March 2010
Line 143:		Line 143:

	?>		?>
-		+	</BODY>
		+	</HTML>
	</pre>		</pre>

Gertvdijk: some markup enhancements

2010-03-30T14:19:55Z

some markup enhancements

← Older revision		Revision as of 14:19, 30 March 2010
Line 1:		Line 1:
-	This page will describe ~~howto~~ change a store to active or inactive ~~without losing~~ the data that is in the store.	+	This page will describe how to change a store to active or inactive preserving the data that is in the store.

-	This page only applies to ~~zarafa~~ versions < 6.40 (in ~~zarafa~~ 6.40 or higher, you are able to change active <-> inactive on the fly, without ~~zarafa~~ orphaning the store).	+	This page only applies to Zarafa versions < 6.40 (in Zarafa 6.40 or higher, you are able to change active <-> inactive on the fly, without Zarafa orphaning the store).

-	====Explanation of fields====	+	==Explanation of fields==
-	You need to do 2 changes per store:	+	You need to do two changes per store:
	- Change the type of the store in the database		- Change the type of the store in the database
-	- Change the ~~ldap~~ attribute of the store	+	- Change the LDAP attribute of the store

-	The ~~mysql~~ changes you need to do are in the users table. The users table has the	+	The MySQL changes you need to do are in the users table. The users table has the following fields:
-	following fields:	+
	<pre>		<pre>
	1. id \| int(11) -> Internal ID of user		1. id \| int(11) -> Internal ID of user
	2. externid \| blob -> External ID of user		2. externid \| blob -> External ID of user
-	3. object_type \| int(11) -> 1=active, 5=inactive(~~sharedstore~~)	+	3. object_type \| int(11) -> 1=active, 5=inactive(shared store)
	4. signature \| varchar(255)		4. signature \| varchar(255)
	5. company \| int(11)		5. company \| int(11)
	</pre>		</pre>
	For field nr. 2 the following goes:		For field nr. 2 the following goes:
-	The value depends on the ~~backend~~ you are using. If you are using ~~openldap~~ the	+	The value depends on the back-end you are using. If you are using OpenLDAP the <tt>externid</tt> will probably be an integer (mostly used is <tt>uidNumber</tt>)... If you use ADS as back-end then the <tt>externid</tt> is a binary value which is really hard to relate to any user.
-	externid will probably be an integer (mostly used is uidNumber)... If you use ADS	+
-	as ~~backend~~ then the externid is a binary value which is really hard to relate to	+
-	any user.	+

-	Below you will find a ~~php~~ script which you can place on the ~~zarafa~~ server	+	Below you will find a PHP script which you can place on the Zarafa server somewhere so that you can access it from a web browser.
-	somewhere so that you can access it from a ~~webbrowser~~.	+

-	You need to modify the credentials on top of the script (any ~~zarafa~~ user will do).	+	You need to modify the credentials on top of the script (any Zarafa user will do). This script will get all the users from Zarafa and will show an HTML table. The last field is the internal id (field nr. 1) of the user. So this can make it easier for you finding the id's of the stores you want to make inactive or active.
-	This script will get all the users from ~~zarafa~~ and will show ~~a html~~ table. The	+
-	last field is the internal id (field nr. 1) of the user. So this can make it	+
-	easier for you finding the id's of the stores you want to make inactive or active.	+

-		+	==The steps==
-	====The ~~Steps==~~==	+
	So the steps to change a store would be:		So the steps to change a store would be:
-	* Find all the id's of the stores you want to make inactive with the ~~php~~ script.	+	* Find all the id's of the stores you want to make inactive with the PHP script.
-	* Write a script that will do the following ~~sql~~ statement for each user you want to change (object_type=1 for active, object_type=5 for inactive):	+	* Write a script that will do the following SQL statement for each user you want to change (<tt>object_type=1</tt> for active, <tt>object_type=5</tt> for inactive):
	<pre>		<pre>
	update users set object_type=[new_object_type] where id=[internal ID]		update users set object_type=[new_object_type] where id=[internal ID]
	</pre>		</pre>
-	Or if you want to use external ID (with ~~openldap~~ -> Of course internal id will also work):	+	Or if you want to use external ID (with OpenLDAP -> Of course internal id will also work):
	<pre>		<pre>
	update users set object_type=[new_object_type] where externid=[external ID]		update users set object_type=[new_object_type] where externid=[external ID]
	</pre>		</pre>
	* Stop Zarafa-server		* Stop Zarafa-server
-	* Run the ~~mysql~~ script	+	* Run the MySQL script
-	* Change the stores to inactive (~~sharedstore~~) in ~~ldap~~ (DO NOT FORGET)	+	* Change the stores to inactive (shared store) in LDAP ('''DO NOT FORGET''')
	* check check, double check		* check check, double check
-	* Start ~~zarafa~~	+	* Start Zarafa-server


-	====The ~~Script==~~==	+	==The script==
-	Here you find the ~~php~~ script (change credentials to a valid ~~zarafa~~ user). This script shows ~~a html~~ table which will show all the ~~zarafa~~ stores, the last field in each row contains the internal id of the store (field nr.1 in users table).	+	Here you find the PHP script (change credentials to a valid Zarafa user). This script shows an HTML table which will show all the Zarafa stores, the last field in each row contains the internal id of the store (field nr.1 in users table).
	<pre>		<pre>
	<HTML>		<HTML>

Msartor at 13:59, 30 March 2010

2010-03-30T13:59:37Z

← Older revision		Revision as of 13:59, 30 March 2010
Line 29:		Line 29:
	This script will get all the users from zarafa and will show a html table. The		This script will get all the users from zarafa and will show a html table. The
	last field is the internal id (field nr. 1) of the user. So this can make it		last field is the internal id (field nr. 1) of the user. So this can make it
-	easier for you finding the id's of the stores you want to make inactive.	+	easier for you finding the id's of the stores you want to make inactive or active.

Msartor at 13:52, 30 March 2010

2010-03-30T13:52:44Z

← Older revision		Revision as of 13:52, 30 March 2010
Line 35:		Line 35:
	So the steps to change a store would be:		So the steps to change a store would be:
	* Find all the id's of the stores you want to make inactive with the php script.		* Find all the id's of the stores you want to make inactive with the php script.
-	* Write a script that will do the following sql statement for each user you want	+	* Write a script that will do the following sql statement for each user you want to change (object_type=1 for active, object_type=5 for inactive):
-	to change (object_type=1 for active, object_type=5 for inactive):	+
	<pre>		<pre>
	update users set object_type=[new_object_type] where id=[internal ID]		update users set object_type=[new_object_type] where id=[internal ID]