We have a production and a development server. The database is a replic and has to be replicated only by manual command from a developer, if the code is tested. There is no automated replication between the systems. We also use design locking which is done on the production server.
In the past we could develop/change the code on the development server, test it and it was never changed on the production server until we started a replication.
With the latest version of the the developer client (FP4) a change on the development server is also saved on the production server and this is not really wanted… Any ideas, if there is a setting?
Subject: Connection Document?
Do you have a connection document for the two servers that enables replication?
On the Replication tab, there are two fields, ‘Files/Directory paths to replicate:’ and ‘Files/Directory paths to NOT replicate:’
I use the ‘Files/Directory paths to NOT replicate:’ to exclude my ‘test’ and ‘work’ directories…
Subject: Replication Disabled
Replication is disabled in the connection document - only Mail Routing is allowed and scheduled.
Subject: replication
In the Replication settings tab of the domino proeprties unser the “Others” tab, there is an option to ‘Temporarily disable replication for this replica’… I would enable that prior to performing any work. This will stop that application from replicating until you change the property back.
Subject: Design Locking is the problem
Design Locking is done on the PROD server, but development is mostly done on the DEV server. So, if we open something on the DEV server, the design is locked on the PROD server. After saving changes on the DEV server, the changes are immediatly published to the PROD server. After changing the ACL server (also locking) to the DEV server, the changes are not published to the PROD server anymore. This behaviour is new, as our settings haven’t changed for years.
btw: this “replication” was also done if “replication is temp disabled” on the DEV server
Subject: We know
we know about that setting and use it now. But if someone forgets to set it, we have the problem. As mentioned - this replication was not done automatically in the past and this is easier to handle 