the POS transaction is a session.delegator. so what ever is set in the entityengine.xml is what POS is connected to. this is usually a local DB on which the POS is running.
Skip sent the following on 9/18/2007 5:20 PM: > Hmmm, I wonder if I am missing something here that I assumed was correct. > Lets say you have 5 stores, each with 5 POS stations. > > Once of the 5 stores is the "Home Office" with a central data store. > > I am assuming that the 5 POS stations are configured to talk to the same > local database connection, and a 6th instance (the back office) is doing the > synchronization with the "Home Office". Is this not correct? > > I am heading now to dig into this code to see just how it works. > > Skip > > -----Original Message----- > From: David E Jones [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 18, 2007 4:45 PM > To: [email protected] > Subject: Re: POS Setup > > > > Check out EntityScheduledServices.xml, noting the targetServiceName in the > EntitySync record. That is the service called to send stuff remotely, and if > you look at it you'll see it uses the remote Service Engine to Service > Engine calling mechanisms. > > -David > > > Vince Clark wrote: >> Skip and David. Thanks for responding quickly to my post. I definitely >> need to use entity synchronization, not database replication. >> >> We're under the gun to deliver a proof of concept this week. I know the >> entity sync works, or at least I trust that it does. I am going thru the >> exercise of reverse engineering how it works based on a demo install. >> The demo data sets up all necessary entities like stores and terminals. >> But there is no default configuration for synchronization. I would >> expect this, as host names would change on a case by case basis. So I >> would not expect a default config. Unfortunately that makes it difficult >> to understand how to set up entity sync by example. >> >> Any hints, links, etc. that could speed up the learning curve would be >> greatly appreciated. >> >> David E Jones wrote: >>> Just a quick note on this: the entity sync stuff is different from >>> database replication as it has different configs for different servers >>> so only the relevant data is needed. A good db level replication tool >>> could probably do something similar, but you would miss some EECA >>> rules that OFBiz runs based on data moving around and stuff like that. >>> >>> -David >>> >>> >>> Skip wrote: >>>> Vince >>>> >>>> I have been looking at this myself and was turned onto EnterpriseDB >>>> which >>>> has a nice replication server. I want all my stores using the same >>>> central >>>> database and the local database only when the internet breaks. >>>> EnterpriseDB's replication server works for that. Somewhat costly, >>>> but not >>>> nearly as bad as Oracle. >>>> >>>> Just gotta add (maybe it's already there?) some failover logic. >>>> >>>> Skip >>>> >>>> -----Original Message----- >>>> From: Vince Clark [mailto:[EMAIL PROTECTED] >>>> Sent: Tuesday, September 18, 2007 2:49 PM >>>> To: [email protected] >>>> Subject: POS Setup >>>> >>>> >>>> I am having trouble figuring out the "step by step" process to deploy >>>> POS with synchronization. >>>> >>>> First area of clarification - How do I get the various pieces deployed >>>> and talking to each other? I have reviewed all the documentation I can >>>> find, and also the related config files. Here is what I understand so >>>> far: >>>> 1) Setup all the necessary entities (stores, facilities, products, >>>> pricing, etc.) >>>> 2) Create POS sync settings to define what entities will be synced >>>> (example PosSyncSetting.xml) >>>> 3) Define terminals per example DemoRetail.xml >>>> 4) Set entity-sync-rmi in serviceengine.xml file >>>> 5) Schedule the sync service >>>> >>>> So where do I do each of these? Master server, per store server, pos, >>>> all of the above? For example, if I have a configuration of one store, >>>> one pos terminal in the store, and one central server I want the flow >>>> to be: >>>> Push product, pricing, etc from central server down to POS terminal: >>>> MCS -> PSS -> POS >>>> >>>> Pull transactions from POS terminal to MCS: >>>> POS -> PSS -> MCS >>>> >>>> So let's start with the central server as the majority of setup will >>>> occur here. The main question I have about the central server is, how >>>> does it know where to "Push"? There is only one setting in >>>> serviceengine.xml for entity-sync-rmi. So how do I configure multiple >>>> per store servers? Or do I misunderstand the use of "PUSH" in the config >>>> file? Is everything really "Pull?" So we just point each deployment to >>>> the server where it should communicate? For example the POS terminal >>>> would always be configured to talk to the PSS, PSS to MCS? >>>> >>>> Is it necessary to use a PSS, or can we go straight from POS->MCS? >>>> >>>> And for those of you also trying to come up to speed on POS, here is the >>>> glossary: >>>> MCS = Main Central Server >>>> PSS = Per Store Server >>>> POS = Point of Sale >>>> -- >>>> Vince Clark >>>> Global Era >>>> The freedom of open source. >>>> (303) 493-6723 >>>> (303) 455-2409 fax >>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >>>> www.globalera.com >>>> > > > >
