Protege Client-Server Tutorial - Revision history

TaniaTudorache at 21:05, January 24, 2012

2012-01-24T21:05:00Z

JenniferVendetti at 18:18, September 24, 2009

2009-09-24T18:18:50Z

JenniferVendetti at 18:03, September 24, 2009

2009-09-24T18:03:35Z

Tredmond at 18:12, August 4, 2009

2009-08-04T18:12:01Z

Tredmond: /* Resources */

2009-08-04T16:15:55Z

‎Resources

TaniaTudorache at 02:30, February 14, 2009

2009-02-14T02:30:15Z

TaniaTudorache at 02:28, February 14, 2009

2009-02-14T02:28:29Z

TaniaTudorache at 01:47, February 13, 2009

2009-02-13T01:47:40Z

TaniaTudorache at 01:45, February 13, 2009

2009-02-13T01:45:11Z

Show changes

TaniaTudorache at 00:59, February 13, 2009

2009-02-13T00:59:29Z

← Older revision		Revision as of 21:05, January 24, 2012
Line 14:		Line 14:

	The tutorial is structured in the following way: first, it describes how to configure and start the Protege server and some trouble shooting tips, then it will describe how to connect a Protege client to a server, and then it will describe some advance topics, such as working with firewalls, compression, debugging, etc.		The tutorial is structured in the following way: first, it describes how to configure and start the Protege server and some trouble shooting tips, then it will describe how to connect a Protege client to a server, and then it will describe some advance topics, such as working with firewalls, compression, debugging, etc.
		+
		+	'''Note. There is a known Java bug in Java 1.6.0_29 and Java 1.7 that affects the starting of the Protege server. If you use this version, please read [[Troubleshooting_Client_Server_Connections#Java_1.6.0_29_and_1.7_rmiregistry_issue\|this information]] first.'''
		+

	== Setting up the server ==		== Setting up the server ==

@@ Line 1: / Line 1: @@
 <div class="orangeBox">
 <span class="orangeBoxTitle">Protege Client-Server Tutorial</span><br /><br />
-'''This tutorial explains how to configure and run Protege in client-server mode. The client-server mode allows multiple Protege clients to edit simultaneously a shared ontology stored on a Protege server. The client-server mode is also referred to as the multi-user mode of Protege and is suitable for projects in which multiple users need to access and edit the same ontology.'''
+'''This tutorial explains how to configure and run Protege in client-server mode. Client-server mode allows multiple Protege clients to simultaneously edit a shared ontology stored on a Protege server. Client-server mode is also referred to as the multi-user mode of Protege and is suitable for projects in which multiple users need to access and edit the same ontology.'''
 </div><br /><br />

@@ Line 7: / Line 7: @@
 __TOC__
-== The Protege client-server mode==
+== Protege's client-server mode==
-The '''client-server mode''' allows multiple Protege clients to edit simultaneously a shared ontology stored on a Protege server. The client-server mode is also referred to as the '''multi-user mode''' of Protege and is suitable for projects in which multiple users need to access and edit the same ontology.
+The '''client-server mode''' allows multiple Protege clients to simultaneously edit a shared ontology stored on a Protege server. The client-server mode is also referred to as the '''multi-user mode''' of Protege and is suitable for projects in which multiple users need to access and edit the same ontology.
 The communication between the client and server is realized using the Java [http://java.sun.com/javase/technologies/core/basic/rmi/index.jsp Remote Method Invocation (RMI)], which works also if the clients and server are behind firewalls. See the ''Advanced Topic'' section for information on how to setup the server to run with a firewall.
@@ Line 15: / Line 15: @@
 The tutorial is structured in the following way: first, it describes how to configure and start the Protege server and some trouble shooting tips, then it will describe how to connect a Protege client to a server, and then it will describe some advance topics, such as working with firewalls, compression, debugging, etc.
+== Setting up the server ==
 The setup of the Protege server is described in details on the [[Protege_Client_Server_Tutorial_Setup|Server setup wiki page]]. The covered topics include:
@@ Line 25: / Line 24: @@
 * Troubleshooting
+== Configuring the server: users and policies  ==
 The configuration of the Protege server is described in details on the [[Protege_Client_Server_Tutorial_Configuration|Protege server configuration wiki page]]. The covered topics include:
@@ Line 34: / Line 32: @@
 * Setting the policies
+== Administering the server: starting and shutting down server projects ==
 The administration of the Protege server is described in details on the [[Protege_Client_Server_Tutorial_Administration|Protege server administration wiki page]]. The covered topics include:
@@ Line 44: / Line 41: @@
 * Shutting down the Protege server
+== Advanced topics ==
 The advanced topics related to the Protege server are described in details on the [[Protege_Client_Server_Tutorial_Advanced|Advanced wiki page]]. The covered topics include:
@@ Line 58: / Line 54: @@
 Occasionally things to wrong.  It is especially hard sometimes to debug problems with the first connection from the client to the server and we have started a [[Troubleshooting Client Server Connections|troubleshooting]] page to give some of ideas on how to troubleshoot a problem.
 == Limitations ==

@@ Line 54: / Line 54: @@
 * Debug and Performance Monitoring
 * Accessing the Server Programmatically
@@ Line 61: / Line 65: @@
 *'''Policy mechanism'''. Currently we only enforce some of the operations in the ''GroupOperations'' that define the policies for accessing the server. The list of enforced policies is available on the [[Protege_Client_Server_Tutorial_Configuration#Predefined_and_enforced_policies|server configuration wiki page]]. We also provide a policy mechanism that is accessible via an API. If a project defines its own custom operations and policies for its own UI, then the application can use the policy manager API and enforce their own policies in their custom application (it can also be a tab widget, or a separate application).
 == Resources ==
 You may take a look at [[Collaborative_Protege|Collaborative Protege]] that provides support for collaboration (e.g., change tracking, annotations, discussion threads on ontology entities, chat, etc.). Collaborative Protege works in client-server mode with different ontology languages (OWL, RDF, Frames) and for different Protege backends (files or databases).

@@ Line 62: / Line 62: @@
 *'''Policy mechanism'''. Currently we only enforce some of the operations in the ''GroupOperations'' that define the policies for accessing the server. The list of enforced policies is available on the [[Protege_Client_Server_Tutorial_Configuration#Predefined_and_enforced_policies|server configuration wiki page]]. We also provide a policy mechanism that is accessible via an API. If a project defines its own custom operations and policies for its own UI, then the application can use the policy manager API and enforce their own policies in their custom application (it can also be a tab widget, or a separate application).
 == Resources ==
 You may take a look at [[Collaborative_Protege|Collaborative Protege]] that provides support for collaboration (e.g., change tracking, annotations, discussion threads on ontology entities, chat, etc.). Collaborative Protege works in client-server mode with different ontology languages (OWL, RDF, Frames) and for different Protege backends (files or databases).

← Older revision		Revision as of 02:30, February 14, 2009
Line 60:		Line 60:
	*'''Forms configuration''' made on the client are not propagated to the server. All clients will see the same forms configuration of the project stored on the server side. We do not currently support different forms for different users. So, if you want to change the forms configuration of a project, you will need to edit the server project in the standalone version of Protege on the server side, and then restart the Protege server for the changes to take effect.		*'''Forms configuration''' made on the client are not propagated to the server. All clients will see the same forms configuration of the project stored on the server side. We do not currently support different forms for different users. So, if you want to change the forms configuration of a project, you will need to edit the server project in the standalone version of Protege on the server side, and then restart the Protege server for the changes to take effect.

−	*'''Policy mechanism'''. Currently we only enforce some of the operations in the ''GroupOperations'' that define the policies for accessing the server. ~~We enforce~~ the ~~''Read'' and the ''DisplayInProjectList'' policies~~. We also provide a policy mechanism that is accessible via an API. If a project defines its own custom operations and policies for its own UI, then the application can use the policy manager API and enforce their own policies in their custom application (it can also be a tab widget, or a separate application).	+	*'''Policy mechanism'''. Currently we only enforce some of the operations in the ''GroupOperations'' that define the policies for accessing the server. The list of enforced policies is available on the [[Protege_Client_Server_Tutorial_Configuration#Predefined_and_enforced_policies\|server configuration wiki page]]. We also provide a policy mechanism that is accessible via an API. If a project defines its own custom operations and policies for its own UI, then the application can use the policy manager API and enforce their own policies in their custom application (it can also be a tab widget, or a separate application).

← Older revision		Revision as of 02:28, February 14, 2009
Line 42:		Line 42:
	* Starting and shutting down server projects		* Starting and shutting down server projects
	* Killing other users' sessions		* Killing other users' sessions
		+	* Shutting down the Protege server

← Older revision		Revision as of 00:59, February 13, 2009
Line 16:		Line 16:


−	== ~~Starting and Testing~~ the Server ==	+	== Setting up the Server ==
		+
		+	The setup of the Protege server is described in details on the [[Protege_Client_Server_Tutorial_Setup\|Server setup wiki page]]. The covered topics include:
		+
		+	* Starting the server
		+	* Testing the server
		+	* Shutting down the server
		+	* Troubleshooting
		+

	=== Start the Server ===		=== Start the Server ===