During a DR test, can I dynamically change the mainframe IP from the prod to DR?

Document ID:  TEC1830493
Last Modified Date:  06/08/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Output Management Web Viewer

Releases

  • CA Output Management Web Viewer:Release:12.1

Components

  • OUTPUT MGMT WEB VIEWER - HP/UX:WBVHP9
  • OUTPUT MGMT WEB VIEWER - HP/UX IA64:WBVHPI
  • CA OUTPUT MANAGEMENT WEB VIEWER FOR ALL PLATFORMS:WBVLUW
  • OUTPUT MGMT WEB VIEWER - LINUX ZSERIES:WBVLXZ
  • OUTPUT MGMT WEB VIEWER - MAC:WBVMAC
  • OUTPUT MGMT WEB VIEWER - AIX:WBVRS6
  • OUTPUT MGMT WEB VIEWER - SUN SOLARIS:WBVSOL
  • OUTPUT MGMT WEB VIEWER - UNIX SYSTEM SERVICES:WBVUSS
  • OUTPUT MGMT WEB VIEWER - WINDOWS:WBVWIN
  • OUTPUT MGMT WEB VIEWER - LINUX PC:WBVX86
Introduction:

12.1 Web Viewer is configured to point to a single CCITCP and DRAS License server, with no provision to revert to an alternate in a mainframe DR or outage situation.

Question:

During a DR test, can I dynamically / automatically change the mainframe IP from the prod to DR?

Answer:

There is no automatic 12.1 Web Viewer DR cut-over to an alternate CCI/DRAS from the primary DRAS/Web Viewer License server process. At best, the process is at least partially manual.

Here's a write-up of the manual procedures needed for Web Viewer to handle a mainframe disaster recovery event. 

=== Assumptions === 

o TWO instances of Web Viewer, each deployed to a different WebSphere or Tomcat Application Server (WAS). 
~ Web Viewer share a DB2 or SQL database. 
~ Web Viewers are both configured identically in regards to CCI and primary DRAS (the "single-point of failure"). 
~ WAS is NOT on the mainframe, or at least not the mainframes where CCI/DRAS/View reside. 

o F5 or other Load Balance to the two WAS servers each with one with Web Viewer instance. 

o TWO mainframe systems, primary and alternate (DR system). Currently CCI and DRAS on one (primary). 


=== Setup === 

o CCI and DRAS in both LPAR. DRAS tasks on each LPAR referencing the same CA View repositories. 

o Configure Web Viewer twice. 

1) Configure CCI to primary LPAR and DRAS license server on primary LPAR. Note: This is probably the current setting. 
2) Save copy of files CCIClient.properties and WVProfile.properties from folder ${CAOMWV12_HOME}/config - this is your "primary" configuration. 
3) Configure CCI to alternate LPAR and DRAS license server on alternate LPAR. 
4) Save copy of files CCIClient.properties and WVProfile.properties from folder ${CAOMWV12_HOME}/config - this is your "alternate" configuration. 
5) Revert to primary configuration by copy/replace of the file in ${CAOMWV12_HOME}/config using the "primary" configuration back-up. 

o Optional: Setup scripting (BAT/SH files) to automate Web Viewer switch to/from the "primary" and "alternate" configurations (files CCIClient.properties and WVProfile.properties). 

o Setup alternate repositories in Web Viewer. 

1) Assumes DRAS tasks active on both systems and the CCI cross-system communication is enabled. Else, repository discovery will not list those on the "other" LPAR. 
2) Log into Web Viewer as a system administrator. 
3) Under Administration > Repository, select a repository. 
4) On the Definition sub-tab, item "Alternate Location(s)". Select a location on the alternate LPAR. Note: If you DRAS task user the same serverID and repository names, the locations will look the same except for the first part of the name - this is the ENFID for the LPAR. Ensure the the "Repository Location" and selected Alternate Location are for DRAS on the two different LPARs. 
5) Save the change. 
6) Repeat for all defined repositories. 


=== DR Actions === 

1) In the event of disaster recovery event... 
2) Primary mainframe system is down. 
3) Switch Web Viewer system's configuration files (CCIClient.properties and WVProfile.properties) to the "alternate" configuration. 
4) Re-cycle the web servers so that Web Viewer picks up the configuration change. 

=== Post-DR actions === 

1) Ensure "primary" LPAR and needed tasks (CCI, DRAS, etc.) are operational. 
2) Switch Web Viewer system's configuration files (CCIClient.properties and WVProfile.properties) to the "primary" configuration. 
3) Re-cycle the web servers so that Web Viewer picks up the configuration change.

Additional Information:

If you want to pursue a more automatic solution, please visit the OM Web Viewer page of the CA Communities site and create an "Idea" to have the capability added to the product and/or vote up any other, like ideas. 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >