Forums » Interstage BPM Server

• admin admin

  
   

  June 5, 2011 6:36:57 AM PDT

  I would like to set up a contingency server.  What this means is, that I want to set up a complete copy of our production server, in a different facility.  I don't want to use it at the same time, I just want redundancy in case something disastrous happens to the production server.  The idea is that if the production server becomes completely unavailable for some reason (say fire in facility, tsunami, terrorist act, major telecom interruption) we will be able to turn on contingency server, and have it pick up pretty much where the other left off.
  
  Our production server already is clustered and makes use of fail-over.  So if there is a small equipment failure (disk drive, etc) we are completely covered without any interruption.  This is only for major problems *just in case*.  For this contingency server, it is not necessary to have seamless failover, we simply need to have all the equipment and everything ready so that a new server can be started in a matter of minutes (5 or 10 minutes to start a server would be acceptable -- 24 hours to install software would not be acceptable.)
  
  We can set up the DB server to have a copy of the data, and set it to stay up to date due to sending the transaction log every few minutes.  Oracle (and probably other DB) support.  That is how the contingency server will have reasonably up to date data.
  
  My question is: how does one set up Interstage BPM to support this kind of configuration?
  
  

  Author: null
  Attachment:

• admin admin

  
   

  June 5, 2011 3:17:07 PM PDT

  Hi,
  
  Please follow the below steps to configure Interstage BPM Contingency setup
  

  Steps:

  1.Install  IBPM Contingency cluster setup. Make sure the folder/directory is same as Production cluster setup
          a.Make sure that the servers name on Contingency environment should be same as of the Production Environment (InterstageBPMCS1, InterstageBPMCS2)
          b.While installing standalone IBPM (before configuring cluster), specify the Standby database in silent installer script as IBPM database i.e. it should point to Standby database.

  2.Incase of disaster; synchronize the Production DB with Standby DB. Export all rows of ibpmproperties table from Standby database using external tools like TOAD or ORACLE SQL DEVELOPER into a cvs/xml file. For example  as ibpm_all_properties.(cvs/xml)

  3.Replace the Production machine host names with the Contingency machine host names based on configuration in exported file (step #2) in the following server properties.

   a.JMSNamingProviderURL . host name . node name
   b.JSExtCmdsFile . host name . node name
   c.KPIListenerConfigFile . host name . node name
   d.ServerBaseURL . host name . node name
   e.ServerEmailBaseURL . host name . node name
   f.ServerHost . host name . node name
   g.ServerRoot . host name . node name
   h.ServerSharedRoot . host name . node name

        For example
            Production Clustered Environment
               MachineA
               MachineB

            Standby Clustered Environment
               MachineC
               MachineD

  
  Replace the word MachineA with MachineC and MachineB with MachineD in all the propertykey and propertyvalue columns in the ibpmproperties file (exported in step #2)

             For example
                 JMSNamingProviderURL.MachineA.InterstageBPMCS1= jnp://MachineA:1100 
                 JMSNamingProviderURL.MachineB. InterstageBPMCS2= jnp://MachineB:1100 

            Changed to

                  JMSNamingProviderURL.MachineC. InterstageBPMCS1= jnp://MachineC:1100
                  JMSNamingProviderURL.MachineD. InterstageBPMCS2= jnp://MachineD:1100

  4.Truncate the ibpmproperties table in Standby database

  5.Import the modified ibpmproperties table ( step #3)

  6.Replicate the Production environment DMS structure on the Contingency environment i.e. copy all the folders/files from Production shared location to Contingency shared location.

  
  7.Copy the “DmsCollections.xml” from location “ProductionMachine/IBPM_HOME/ /server/instance/default/tenants/Tenant_Name/resources to “ContigencyMachine/IBPM_HOME/ /server/instance/default/tenants/Tenant_Name /resources. Do step # 7 for all the Tenants.

  8.Start the IBPM Contingency clustered server 
  
  Hope this will help.
  
  If you have any other queries, please let us know.
  
  Regards,
  Rajeev
  
  

  Author: Rajeev Kumar Singh
  Attachment: