It is advised to also build the necessary checks into the live custom JDF’s so that the content does not get lost when the live database is copied into a test-database again. The additional check in the customs JDF’s will prevent that JDF’s are send from the test-database to Esko for jobs and products that do not start with a “T”-prefix. This means that a user cannot accidentally send JDF’s to Esko for jobs that have been created in the live database before it was copied into the test-database. So the live information (customers, jobs, products) are safe from being altered by data coming from the test database. In the live database the additional check in the custom JDF works the other way around (only for safety, in theory not required). Check if there are other Custom JDF’s besides the prepress and production Custom JDF’s. These will also need similar adjustments! The controllers in the Sqlb00Test need to be renamed in order to be able to recognize Esko subscriptions that are related to the test database. update jmfsrv__ set srv__ref = 'T'+substring(srv__ref,2,5) The devices that use the existing controllers need to be linked to the renamed controllers update jmfdev__ set srv__ref = 'T'+substring(srv__ref,2,5) The default JDF directories need to be corrected update jmfpar__ set jmf__dir='\\CERM-DATA\sqlb00test\jdf\' update jmfpar__ set jdf__dir='\\CERM-DATA\sqlb00test\jdf\' The existing subscriptions related to Esko need to be deleted delete from jmfpch__; Alternatively you can create a Telnet session to the Esko Server on port 4401 (cmd: telnet eskoserver 4401) and find all subscriptions using the command lsubscr. With the DAS command you can delete the Esko subscriptions Restart all JDF-related services on both Engines.
It is advised to also build the necessary checks into the live custom JDF’s so that the content does not get lost when the live database is copied into a test-database again. The additional check in the customs JDF’s will prevent that JDF’s are send from the test-database to Esko for jobs and products that do not start with a “T”-prefix. This means that a user cannot accidentally send JDF’s to Esko for jobs that have been created in the live database before it was copied into the test-database. So the live information (customers, jobs, products) are safe from being altered by data coming from the test database. In the live database the additional check in the custom JDF works the other way around (only for safety, in theory not required). Check if there are other Custom JDF’s besides the prepress and production Custom JDF’s. These will also need similar adjustments! The controllers in the Sqlb00Test need to be renamed in order to be able to recognize Esko subscriptions that are related to the test database. update jmfsrv__ set srv__ref = 'T'+substring(srv__ref,2,5) The devices that use the existing controllers need to be linked to the renamed controllers update jmfdev__ set srv__ref = 'T'+substring(srv__ref,2,5) The default JDF directories need to be corrected update jmfpar__ set jmf__dir='\\CERM-DATA\sqlb00test\jdf\' update jmfpar__ set jdf__dir='\\CERM-DATA\sqlb00test\jdf\' The existing subscriptions related to Esko need to be deleted delete from jmfpch__; Alternatively you can create a Telnet session to the Esko Server on port 4401 (cmd: telnet eskoserver 4401) and find all subscriptions using the command lsubscr. With the DAS command you can delete the Esko subscriptions Restart all JDF-related services on both Engines.