All - I am also involved with this disaster recovery site and here's the major issue. For purposes of discussion the we'll call the original enterprise/JAS server ES-01 and the original deployment server DS-01. They want the 2nd site to have its own DIFFERENTlY named Enterprise server, ES-02. I'm just bringing up a 2nd deployment server, DS-02. Here's the issues I see. While we can replicate various \folders and also the production biz and code tables (Oracle on Linux) the problem for me is simply this - if I bring up the differently named failover Enterprise server, ES-02, many of the key values in the replicated system tables will continue to point to ES-01 server. I didn't really want to have to go in and hack those tables. Here are 2 approaches.
Approach 1. My associated suggested a clean install on DS-01 pointing to a NEW JDE812 system database that we intentionally would NOT replicate. We would ONLY share the actual production biz data and central objects code databases.
Approach 2. In the planner session on DS-01, identify both the new deployment server, DS-02, as well as the new enterprise server ES-02. Install the JDE DS software on DS-02. The failover would consist in telling the system files, from DS-02 that ES-02 was now the system files security server and the main JDE system server. I don't think that this woule be enough and we'd STILL have to hack system tables on the replicated database to point the system from ES-01 over to ES-02.
Question. It looks like the client is NOT willling to change the machine name of ES-02 back to ES-01 in the event of a failover. Is there any less complicated way to approach this? Which Approach makes the most sense?