data_insight-win-4.5RP3HF1

 Basic information
Release type: Hot Fix
Release date: 2015-06-16
OS update support: None
Technote: None
Documentation: None
Popularity: 475 viewed    downloaded
Download size: 48.06 KB
Checksum: 3250775614

 Applies to one or more of the following products:
Data Insight 4.5 On Windows 32-bit
Data Insight 4.5 On Windows 64-bit

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
3791005, 3798450

 Patch ID:
None.

Readme file
Date: 2015-06-17

OS: Windows

Etrack Incidents: 3798450, 3791005

Errors/Problems Fixed:

3798450 - Extended workflow date is not getting used. Workflow moves to 
completed date after the end_date specified while workflow creation.

3791005 - If Permission Remediation (Email for raising ticket) is configured
and in ER workflow, you submit a path without making any changes to the 
permissions, mail is not sent and the status for that path is always 
"Executing Action".
 
 
Applies to: Data Insight Management Server node and all Data Insight nodes 
that have Self-Service Portal role configured.

Install/Uninstall Instructions:

Apply this hotfix to Data Insight Management Server node and all Data Insight
nodes that have Self-Service Portal role configured. 

This hotfix can be applied to Data Insight version 4.5.3(4.5RP3) only.

FILE AFFECTED BY THIS PATCH:

Windows:
INSTALL_ROOT\DataInsight\tomcat\webapps\ROOT\WEB-INF\classes\com\symc\matrix\workflow\operations\entitlement\EntitlementReviewStep.class
INSTALL_ROOT\DataInsight\tomcat\webapps\ROOT\WEB-INF\classes\com\symc\matrix\workflow\operations\incidentmanagement\StepUtils*.class

By default, value of INSTALL_ROOT on Windows is "C:\Program Files\Symantec".

NOTE: Please keep a backup of the files you are about to patch. This will be 
required in case you want to rollback the patch.

Steps:

Log into Data Insight Management Server and all Data Insight nodes which have 
the Self-Service Portal role configured and perform the following steps:
	
	1. Stop Data Insight services:
    	From the command prompt, issue the following command:
		
        net stop DataInsightWatchdog
        net stop DataInsightWeb
	net stop DataInsightComm
        net stop DataInsightConfig
	net stop DataInsightWorkflow
	net stop DataInsightPortal

        2.  Take a backup of entire tomcat and portal_tomcat (portal_tomcat folder
	is present only on those nodes which have Portal role configured) folders 
	under the install location.

	3. Unzip the patch files to a temporary folder. In this folder, locate the
	"patches" folder. This folder contains binaries for 32bit and 64bit Windows
	operating Systems. Files provided in the patch are in the same directory 
	hierarchy as those present on your system at "INSTALL_ROOT\DataInsight".
	
	Example: If you unzip hotfix to C:\temp, it will create the following folders
	under C:\temp:
	C:\TEMP\
	+---README
	+---patches
		+---windows
			+---32bit
				+-------tomcat
			+---64bit
				+-------tomcat

	4. Copy the patch files to the install directory. For example, if you are
	patching a 64 bit Windows server installed at 
	"C:\Program Files\Symantec\DataInsight", copy "tomcat" folder under 
	"C:\temp\patches\windows\64bit" to "C:\Program Files\Symantec\DataInsight",
	replacing the original files with those from the patch, for Management Server
	node as well as all Data Insight nodes which have Portal role configured.
	
	5. Start Data Insight services:
	From the command prompt, issue the following command:
	
        net start DataInsightConfig
        net start DataInsightComm
	net start DataInsightWeb
        net start DataInsightWatchdog
	net start DataInsightWorkflow
	net start DataInsightPortal

Additional Notes:
1. Apply this hotfix to Data Insight 4.5.3 (4.5RP3) only.
2. DataInsightPortal service is applicable only for those Data Insight nodes that 
   have the Self-Service Portal role configured.
   In case of Management Server node acting as Portal nodes, it has 
   DataInsightPortal service running on it.
3. DataInsightWeb service is applicable only for the Management Server node.