Web OAM&P - Revision history

Ktrueman at 15:08, 8 May 2009

2009-05-08T15:08:11Z

Ktrueman at 15:07, 8 May 2009

2009-05-08T15:07:13Z

Ktrueman: /* Caveats */

2009-05-07T19:49:23Z

Caveats

Ktrueman: /* Caveats */

2009-05-07T19:48:53Z

Caveats

Ktrueman: /* Caveats */

2009-05-07T19:48:26Z

Caveats

Ktrueman at 19:47, 7 May 2009

2009-05-07T19:47:44Z

Ktrueman at 19:47, 7 May 2009

2009-05-07T19:47:14Z

Ktrueman at 19:45, 7 May 2009

2009-05-07T19:45:22Z

Ktrueman at 19:44, 7 May 2009

2009-05-07T19:44:39Z

Ktrueman at 19:44, 7 May 2009

2009-05-07T19:44:05Z

@@ Line 20: / Line 20: @@
 '''Database'''
-The web application queries and updates the framework database that acts as an interface to configure the underlying framework. The database is the only required part of the configuring tool. This means clients can build their own configuration GUI as long as it uses the database correctly. For more information see the framework database. Note that the naming convention is one that is used widely and easy to understand. This is also the naming convention used by the Ruby on rails framework.
+The web application queries and updates the framework database that acts as an interface to configure the underlying framework. The database is the only required part of the configuring tool. This means clients can build their own configuration GUI as long as it uses the database correctly. For more information see the [[Framework database]]. Note that the naming convention is one that is used widely and easy to understand. This is also the naming convention used by the Ruby on rails framework.
 '''Web application'''

@@ Line 1: / Line 1: @@
 A tool is provided to configure/monitor the framework. Using this tool it is possible to:
-*Manage users.
+*Manage users
-*Manage configurations.
+*Manage configurations
-*Configure/monitor Hardware.
+*Configure/monitor Hardware
-:*IP Interfaces.
+:*IP Interfaces
-:*TDM Interfaces.
+:*TDM Interfaces
-:*ISDN stacks.
+:*ISDN stacks
-:*SIP service access points.
+:*SIP service access points
-*Configure network access points.
+*Configure network access points
 When used with the gateway application it is also possible to:
-*Monitor call activity.
+*Monitor call activity
-*Configure dial plans.
+*Configure dial plans
 There are three terms that are often used in the framework when referring to this tool:
-*Configuration : An element’s configuration can always be viewed but can only be changed on non active configurations.
+*'''Configuration ''': An element’s configuration can always be viewed but can only be changed on non active configurations
-*States : An element’s state can only be viewed/changed on active configurations.
+*'''States ''': An element’s state can only be viewed/changed on active configurations
-*Status : An element’s state can only be viewed on active configurations. It may never be changed.
+*'''Status ''': An element’s state can only be viewed on active configurations. It may never be changed
@@ Line 25: / Line 25: @@
 The web application is a full working example (also optional) of how to integrate with the framework’s database:
 *Written in Ruby using the Ruby on Rails framework. The framework is easy to learn and use; it simplifies traditional web design by a great factor. Since the framework is based on the MVC pattern, it is very easy to add new pages without risking to break the rest of the application.
-*Implements all of the database tables.
+*Implements all of the database tables
-*Uses cascading stylesheets extensively to allow for "look and feel" customization.
+*Uses cascading stylesheets extensively to allow for "look and feel" customization
-*When it makes sense, Ajax is used to provide better responsiveness.
+*When it makes sense, Ajax is used to provide better responsiveness
-*Supports at least the following browsers: IE, Mozilla, Opera and Safari.
+*Supports at least the following browsers: IE, Mozilla, Opera and Safari
 *Can run on the following web servers: Apache, lighttpd, or nginx proxying to Mongrel (or using FastCGI)

← Older revision		Revision as of 19:49, 7 May 2009
Line 42:		Line 42:


−	The framework database must be one supported by Ruby On Rails to use the supplied web application~~. Such a list is maintained at Ruby on Rails ([http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers])~~.	+	The framework database must be one supported by Ruby On Rails to use the supplied web application.

← Older revision		Revision as of 19:48, 7 May 2009
Line 42:		Line 42:


−	The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at [http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers~~\|RubyonRails~~].	+	The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at Ruby on Rails ([http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers]).

← Older revision		Revision as of 19:48, 7 May 2009
Line 42:		Line 42:


−	The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at [~~RubyonRails\|~~http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers].	+	The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at [http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers\|RubyonRails].

← Older revision		Revision as of 19:47, 7 May 2009
Line 42:		Line 42:


−	The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at [http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers].	+	The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at [RubyonRails\|http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers].

@@ Line 10: / Line 10: @@
 When used with the gateway application it is also possible to:
-*Monitor call ativity.
+*Monitor call activity.
 *Configure dial plans.
@@ Line 23: / Line 23: @@
 '''Web application'''
-The web application is a full working example (also optionnal) of how to integrate with the framework’s database:
+The web application is a full working example (also optional) of how to integrate with the framework’s database:
-*Written in Ruby using the Ruby on Rails framework. The framework is easy to learn and use; it simplifies traditionnal web design by a great factor. Since the framework is based on the MVC pattern, it is very easy to add new pages without risking to break the rest of the application.
+*Written in Ruby using the Ruby on Rails framework. The framework is easy to learn and use; it simplifies traditional web design by a great factor. Since the framework is based on the MVC pattern, it is very easy to add new pages without risking to break the rest of the application.
 *Implements all of the database tables.
 *Uses cascading stylesheets extensively to allow for "look and feel" customization.
@@ Line 33: / Line 33: @@
 == Usage ==
-Usage depends on the server used to run the web application and the database. In any case there is some configuration
+Usage depends on the server used to run the web application and the database. In any case there is some configuration that must be modified in the web application. The "database.yml" file must be changed to point to the client’s framework database. Starting the web server (using Webrick or Mongrel) can then be done as follows from the web application’s directory:
 that must be modified in the web application. The "database.yml" file must be changed to point to the client’s
-framework database. Starting the web sever (using Webrick or Mongrel) can then be done as follows from the web
 application’s directory:
    ruby script/server
@@ Line 45: / Line 42: @@
-The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is
+The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at [http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers].
 maintained at http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers.

← Older revision	Revision as of 19:45, 7 May 2009
Line 41:	Line 41:


	+
	+	== Caveats ==
	+
	+
	+	The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is
	+	maintained at http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers.

← Older revision		Revision as of 19:44, 7 May 2009
Line 19:		Line 19:


−	== Database ==	+	'''Database'''
	The web application queries and updates the framework database that acts as an interface to configure the underlying framework. The database is the only required part of the configuring tool. This means clients can build their own configuration GUI as long as it uses the database correctly. For more information see the framework database. Note that the naming convention is one that is used widely and easy to understand. This is also the naming convention used by the Ruby on rails framework.		The web application queries and updates the framework database that acts as an interface to configure the underlying framework. The database is the only required part of the configuring tool. This means clients can build their own configuration GUI as long as it uses the database correctly. For more information see the framework database. Note that the naming convention is one that is used widely and easy to understand. This is also the naming convention used by the Ruby on rails framework.

		+	'''Web application'''
		+	The web application is a full working example (also optionnal) of how to integrate with the framework’s database:
		+	*Written in Ruby using the Ruby on Rails framework. The framework is easy to learn and use; it simplifies
		+	traditionnal web design by a great factor. Since the framework is based on the MVC pattern, it is very easy to
		+	add new pages without risking to break the rest of the application.
		+	*Implements all of the database tables.
		+	*Uses cascading stylesheets extensively to allow for "look and feel" customization.
		+	*When it makes sense, Ajax is used to provide better responsiveness.
		+	*Supports at least the following browsers: IE, Mozilla, Opera and Safari.
		+	*Can run on the following web servers: Apache, lighttpd, or nginx proxying to Mongrel (or using FastCGI)


		+	== Usage ==
		+	Usage depends on the server used to run the web application and the database. In any case there is some configuration
		+	that must be modified in the web application. The "database.yml" file must be changed to point to the client’s
		+	framework database. Starting the web sever (using Webrick or Mongrel) can then be done as follows from the web
		+	application’s directory:
		+	~>ruby script/server