Best Practice for Designing a Rifidi APP - Revision history

Bppause: /* Design */

2014-09-05T18:45:49Z

‎Design

Bppause: /* Design */

2014-09-05T18:08:52Z

‎Design

Bppause: /* Design */

2014-09-05T18:08:21Z

‎Design

Bppause: /* Design */

2014-09-05T18:07:26Z

‎Design

Bppause: /* Design */

2014-09-05T17:52:50Z

‎Design

Bppause at 11:05, 29 August 2014

2014-08-29T11:05:06Z

Bppause: /* Other Topics (Monitoring/Logging/Management/Deployment) */

2014-08-29T06:59:35Z

‎Other Topics (Monitoring/Logging/Management/Deployment)

Bppause at 06:58, 29 August 2014

2014-08-29T06:58:39Z

Bppause at 06:58, 29 August 2014

2014-08-29T06:58:25Z

Bppause at 21:00, 26 August 2014

2014-08-26T21:00:38Z

@@ Line 16: / Line 16: @@
-Overview
+*Design Framework Overview
-*Application properties are used to set Global (for a application group) and Application specific prioperties such as timeouts, database connection strings etc..
+**Application properties are used to set Global (for a application group) and Application specific prioperties such as timeouts, database connection strings etc..
-*Applications use reader zones - Defined in readzone - proeprties file
+**Applications use reader zones - Defined in readzone - proeprties file
-*Read zone properties map to one to many readers in rifidi.xml
+**Read zone properties map to one to many readers in rifidi.xml
-*Readers in defined rifidi.xml (or using workbench UI) map to the physical reader/sensor(s)
+**Readers in defined rifidi.xml (or using workbench UI) map to the physical reader/sensor(s)
 *What Hardware (readers and sensors) are you looking to use?

@@ Line 17: / Line 17: @@
 Overview
-**Application properties are used to set Global (for a application group) and Application specific prioperties such as timeouts, database connection strings etc..
-**Applications use reader zones - Defined in readzone - proeprties file
+*Application properties are used to set Global (for a application group) and Application specific prioperties such as timeouts, database connection strings etc..
-**Read zone properties map to one to many readers in rifidi.xml
+*Applications use reader zones - Defined in readzone - proeprties file
-**Readers in defined rifidi.xml (or using workbench UI) map to the physical reader/sensor(s)
+*Read zone properties map to one to many readers in rifidi.xml
 *What Hardware (readers and sensors) are you looking to use?

@@ Line 17: / Line 17: @@
 Overview
-Application properties are used to set Global (for a application group) and Application specific prioperties such as timeouts, database connection strings etc..
+**Application properties are used to set Global (for a application group) and Application specific prioperties such as timeouts, database connection strings etc..
-Applications use reader zones - Defined in readzone - proeprties file
+**Applications use reader zones - Defined in readzone - proeprties file
-Read zones properties map to one to many readersin rifidi.xml
+**Read zone properties map to one to many readers in rifidi.xml
-Readers in defined rifidi.xml (or using workbench UI) map to the physical reader/sensor(s)
+**Readers in defined rifidi.xml (or using workbench UI) map to the physical reader/sensor(s)
 *What Hardware (readers and sensors) are you looking to use?

← Older revision		Revision as of 18:07, 5 September 2014
Line 14:		Line 14:

	==Design==		==Design==
		+
		+
		+	Overview
		+	Application properties are used to set Global (for a application group) and Application specific prioperties such as timeouts, database connection strings etc..
		+	Applications use reader zones - Defined in readzone - proeprties file
		+	Read zones properties map to one to many readersin rifidi.xml
		+	Readers in defined rifidi.xml (or using workbench UI) map to the physical reader/sensor(s)

	*What Hardware (readers and sensors) are you looking to use?		*What Hardware (readers and sensors) are you looking to use?

@@ Line 27: / Line 27: @@
 ***Yes - A list of out of the box Rifidi Services addressing these design challenges can be found in the [[Developer%27s_Guide | Developer's guide] or [[Rifidi_Services_Jumpstart]]
 ***No - A custom business rule can be developed using Esper (Esper is a trademark of EsperTech Inc) An example of custom Esper to create a work in progress business rule can be found in the [[Northwind_Example_Application_-_Advanced_Development_Topic | Northwind Example Application]] - Note: A more advanced topic once familiar with developing a basic application such as [[HelloWorld_App_Jumpstart | HelloWorld Application]].
-**4 Define the read zones required  - This defines the relations the readers/sensors have to each other within the application such as 1 to 1 relationship, 1 to many, many to 1 (Note The readzone configurations also support regular expressions in the event you use a naming convention when defining read adapters to potentially represent relationships - How to define readzones can be found in the [[Developer%27s_Guide | Developer's guide]]
+**4 Define the read zones required   - This defines the relations the readers/sensors have to each other within the application such as 1 to 1 relationship, 1 to many, many to 1 (Note The readzone configurations also support regular expressions in the event you use a naming convention when defining read adapters to potentially represent relationships - How to define readzones can be found in the [[Developer%27s_Guide | Developer's guide]] Note: The serviceid for a given reader factory adapter instance in the rifidi.xml is used to map to a readerID in teh readzone property files
 **5 Are there any application properties required? Such as database parameters, Queue Names, Webservice Endpoints/URL, Rifidi services parameters (timeouts, thresholds) -Note: All teh Rifidi Jumpstart Applications provide examples on how these are defined and used within an application
 ==Other Topics (Monitoring/Logging/Management/Deployment)==
 * Is there a need to Dynamically/Remotely manage the Edge Server such as stopping/starting sessions, configuring sensors, managing applications etc.. A list of how to use these Edge management services can be found [[Edge_Management | Edge Management]]

@@ Line 35: / Line 35: @@
 * Any changes to Edger Server configuration such as changing default port, RMI, production mode [[Edge_Server_Configuration | Edge_Server_Configuration]]
 * Are there any OSGI Bundles you need to add to Edge Server required by your application?  such as the Oracle database driver [[How_to_add_OSGI_Bundles| How_to_add_OSGI_Bundles]]
 * Complete steps to export and deploy a app you designed/developed [[How_to_export_your_custom_Rifidi_application| How_to_export_your_custom_Rifidi_application]]

@@ Line 11: / Line 11: @@
 ==Setup==
-* Ensure you have setup your Rifidi development environment  - [[Edge_Server_Development_Environment | dge_Server_Development_Environment]]
+* Ensure you have setup your Rifidi development environment  - [[Edge_Server_Development_Environment | Edge_Server_Development_Environment]]
 ==Design==

← Older revision		Revision as of 21:00, 26 August 2014
Line 35:		Line 35:
	* Any changes to Edger Server configuration such as changing default port, RMI, production mode [[Edge_Server_Configuration \| Edge_Server_Configuration]]		* Any changes to Edger Server configuration such as changing default port, RMI, production mode [[Edge_Server_Configuration \| Edge_Server_Configuration]]
	* Are there any OSGI Bundles you need to add to Edge Server required by your application? such as the Oracle database driver [[How_to_add_OSGI_Bundles\| How_to_add_OSGI_Bundles]]		* Are there any OSGI Bundles you need to add to Edge Server required by your application? such as the Oracle database driver [[How_to_add_OSGI_Bundles\| How_to_add_OSGI_Bundles]]
		+	* Complete steps to export and deploy a app you designed/developed [[How_to_export_your_custom_Rifidi_application\| How_to_export_your_custom_Rifidi_application]]