IBM Support

Disable DWC Plan Mirroring

Troubleshooting


Problem

Plan information displayed by the Dynamic Workload Console is slow updating or incorrect when connected to Tivoli Workload Scheduler 9.x.x.

Symptom

Plan (Symphony) mirroring is a new feature to TWS 9.x.x 

Cause

Unexpected Plan status information can be caused by incorrectly mirrored data between the Plan (Symphony) file and the database, or delays in mirroring the data.

Resolving The Problem

Starting from TWS 9.3 fp3 and TWS 9.4 fp3 and 9.5  multiple issues has been addressed in Mirroring feature.
The first action to recommend is to install the latest TWS 9.3,9.4  ,9.5/10.1 fixpack that contains multiple improvement/fixes on that feature.


When it is not possible to apply the required FixPack immediately ,
you can configure the DWC to access the Symphony file
directly for Plan status instead of using the data in the database.

Following these instructions will disable the mirroring feature "display" ; the TWS data will be loaded from the TWS Symphony as for previous releases.

However the TWS Engine will still syncronize Symphony data against the TWS DB.Read at the end of this technote for additional consideration.
Fixpack that addressed the mirroring issues must be applied as soon they are available and these
settings must be removed and the feature must be enabled again.


On TWS Engine:


Edit TWSConfig.properties and set the property:

 

For tws 9.1/92/93/94 Edit <TWA_home>/WAS/TWSProfile/properties/TWSConfig.properties

For tws 9.5 /10.1  Edit (example) /TWSDATA/usr/servers/engineServer/resources/properties/TWSConfig.properties

 

and set the property:

From

com.ibm.tws.planDaoFactory.impl = com.ibm.tws.dao.plan.rdbms.RDBMSPlanDAOFactory

To 

com.ibm.tws.planDaoFactory.impl = com.ibm.tws.dao.plan.SymphonyDAOFactory

Please take care to avoid spaces at the end of the line!

StopWAS and Stop TWS and restart all


On DWC:
For 9.x till 9.4.

To configure the DWC to use the Symphony file data directly:
  1. Stop the DWC WAS instance:

    # cd <TWAhome>/wastools
    # ./stopWas.sh -direct -user
    DWC_Admin_user -password password
     
  2. Created the following file if not already present::

    <JazzSM>/profile/registry/tdwc_options.properties
     
  3. Add the following line to the tdwc_options.properties file:

    com.ibm.tws.ui.disableMirroring=true
     
  4. Ensure that the file has ownership/permissions similar to:

    -rw-r--r--. 1 root root 37 Jan 27 15:13 tdwc_options.properties
     
  5. Restart WAS:

    # cd <TWAhome>/wastools
    # ./startWas.sh


To confirm that the DWC is obtaining status from the Symphony file, after restarting WAS, log in to the DWC then navigated to Monitor Jobs, and query all jobs in plan. Once the query completes check the SystemOut.log file for entries similar to::
 
  • [27/01/15 15:48:37:152 GMT] 00000074 SystemOut O [CommandExecutorFactory] mirroring has been disabled.
    [27/01/15 15:48:37:152 GMT] 00000074 SystemOut O [CommandExecutorFactory] Change registry/tdwc_options.properties,com.ibm.tws.ui.disableMirroring key to re-enable it, and restart WAS
Please notice that 
 the TWS Engine will still syncronize Symphony data against the TWS DB.
However this background mirroring mechanism could be stopped (usually NOT required)
starting from TWS 9.3 fp3 & TWS 9.4 fp4 ,9.5 /10.1 and higher fps level.
This could be useful if the Mirroring issue are related to Performance issue or Hang/deadlock  scenarios.
 
User should modify the TWSConfig.properties AND remove in the FinalPostreports  the planman checksync.

Edit TWSConfig.properties

   Add/change (if it already exist) the parameter to
com.ibm.tws.planner.monitor.subProcessors = 0
Add the line
   com.ibm.tws.planner.update.monitor.time = 0
(In case of Mirroring re-enabling the first keyword -com.ibm.tws.planner.monitor.subProcessors-
should be set to original value (recommended value is 10)
and the keyword com.ibm.tws.planner.update.monitor.time should be deleted)

and restart WAS/TWS.
Then on FinalPostreports:

- comment out the planman resync and its dependencies in the FINALPOSTREPORTS stream.

NOTE: comment out the line using hash space (# ) in the beginning of the line.

composer “modify sched=FINALPOSTREPORTS”

SCHEDULE MDM95JOY#FINALPOSTREPORTS

DESCRIPTION "Added by composer."

ON RUNCYCLE RC1 "FREQ=DAILY;"

SCHEDTIME <hhmm>

CARRYFORWARD

FOLLOWS MDM95JOY#FINAL.SWITCHPLAN PREVIOUS

:

# MDM95JOY#CHECKSYNC

MDM95JOY#CREATEPOSTREPORTS

For JnextPlan, backup and comment out the planman checksync as the the following section:

NOTE: comment out the line using hash space (# ) in the beginning of the line.

# log_line "Invoking planman checksync"

log_line "Disabled planman checksync"

# planman checksync | tee -a $JNEXTPLAN_OUTPUT
 
For TWS 9.5 and 10.1 only with mirroring disabled the
Dashboard with  folders different from root could produce not correct results versus the conman command line.
 

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"ARM Category":[],"Platform":[{"code":"PF016","label":"Linux"},{"code":"PF025","label":"Platform Independent"},{"code":"PF033","label":"Windows"}],"Version":"9.1;9.2;9.3;9.4;9.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 January 2023

UID

swg21697456