### ########################################################
### Release-Compellent
### ########################################################
### ##############################################################
### only log out of compellent iSCSI session
### ##############################################################
/sbin/iscsiadm -m session -R
iqn.2002-03.com.compellent:5000d31001266826, portal: 10.1.2.15,3260]
iqn.2002-03.com.compellent:5000d31001266824, portal: 10.1.2.15,3260]
iqn.2002-03.com.compellent:5000d31001266823, portal: 10.1.2.14,3260]
iqn.2002-03.com.compellent:5000d31001266825, portal: 10.1.2.14,3260]
/sbin/iscsiadm -m node -T iqn.2002-03.com.compellent:5000d31001266826 --logout
/sbin/iscsiadm -m node -T iqn.2002-03.com.compellent:5000d31001266824 --logout
/sbin/iscsiadm -m node -T iqn.2002-03.com.compellent:5000d31001266823 --logout
/sbin/iscsiadm -m node -T iqn.2002-03.com.compellent:5000d31001266825 --logout
/sbin/iscsiadm -m session -R
### ##############################################################
### delete only compellent configuration
### ##############################################################
cd /var/lib/iscsi/ifaces
rm -rf bnx2i.* old.p7p1 p7p1
cd /var/lib/iscsi/send_targets
rm -rf 10.1.1.1,3260 10.1.2.1,3260 10.1.2.14,3260 10.1.2.15,3260
cd /var/lib/iscsi/nodes
rm -rf iqn.2002-03.com.compellent:5000d31001266823 iqn.2002-03.com.compellent:5000d31001266825 iqn.2002-03.com.compellent:5000d31001266824 iqn.2002-03.com.compellent:5000d31001266826
# ###################################################################
# remove any Compellent specific entries from multipath.conf
# ###################################################################
cp -p no-compellent.multipath.conf multipath.conf
### ##############################################################
### remove only compellent mount points
### ##############################################################
rm -rf /old-BinghamtonUniversity /old-BKUP-CANNED /old-opt /old-sastmp /home/sas/prod/old-log/
### ##############################################################
### disable only the compellent NIC
### ##############################################################
cd /etc/sysconfig/network-scripts/
ifdown p7p1
ifconfig -a
mv ifcfg-p7p1 NIU-ifcfg-p7p1
### ##############################################################
### request networking to un-cable the p7p1 NIC.
### ##############################################################
### ########################################################
### Set Debugging
###
### the categories were not matching...
### sent what we had to SAS TechSup
###
### ########################################################
1. Turn on debugging for the transport services by editing the
gedit /opt/sasinside/config/midtier/Lev1/Web/Common/LogConfig/SASVisualAnalyticsTransport-log4j.xml
Chang each of the following categories from the default "INFO" to "DEBUG" ...
com.sas.onebi.transportservices
com.sas.rest.transportservices
com.sas.onebi.ws.transportservices
com.sas.bidata
### ######################################################
### DONE
### ######################################################
2. On the Plug-ins tab..
Select Application Management ►
Configuration Manager ►
SAS Application Infrastructure
Expand Visual Analytics 7.5 ►
Visual Analytics Services 7.5
Right-click Visual Analytics Transport Service 7.5
select Properties
Add or modify:
viewerservices.default.max.cells.produced value=5000000
va.detailTableSortResultLimit value=5000000
3. On the Plug-ins tab, select Application Management ► Configuration Manager ► SAS Application Infrastructure. Expand Visual Analytics 7.5 and select Properties. Add or modify:
va.CategoryCardinalityServerLimit value=500000
va.DistinctCountServerLimit value=500000
va.SummaryServerRowLimit value=500000
va.detailTableSortResultLimit value=500000
4. Restart SASServer12_1 for all of these changes to take effect.
cd /opt/sasinside/
./SAS.Services start
Sept 6
--------------------------------------------------
https://centostwo.binghamton.edu/SAS/Tuesday-09-06-2022.html
https://centostwo.binghamton.edu/SAS/SAS-Maint-HotFix-Steps.html
STEP 2 in the URL above
This hot fix requires scripting to automatically reconfigure SAS Middle
Tier 9.4_M7 after the hot fix has been applied.
The Apply Hot Fix and Configure SAS Hot Fix steps in the SAS Deployment Manager
must be run in separate steps when applying the hot fix.
You must first apply the hot fix without selecting the Configure SAS Hot Fix option.
After the hot fix has been successfully applied, you need to start all the SAS servers.
After the services have started, run the SAS Deployment Manager again and select "Configure SAS Hot Fix" only.
==============================================================================
https://centostwo.binghamton.edu/SAS/SAS-Maint-HotFix-Steps.html
STEP 6 in the URL above
### ###################################
### Rebuild and Redeploy Web Applications
### ###################################
Rebuild Web Applications
NOTE: In order for this step to execute correctly, the Metadata Server must be running.
Select the appropriate product as the Web Application to Rebuild; it is recommended that you rebuild and redeploy all of the web applications after applying this hot fix.
Re-start all SAS sessions, daemons, spawners and servers. For more information on the
proper order for starting servers, go to SAS® 9.4 Intelligence Platform: System Administration Guide,
Fourth Edition and review the section entitled "Starting, Stopping and Checking the Status of Servers".
Redeploy Web Applications
Redeploy the updated wars to the web application server.
JAVA
https://centostwo.binghamton.edu/SAS/SASJAVAInstallSteps.html
================================================================================
### ###################################
### Upgrade metadata
### ###################################
In SAS Management Console, select the Metadata Manager plug-in and navigate to
the Active Server.
Right click on the Active Server and chose Upgrade Metadata.
Click Yes in the pop-up window asking "Are you sure you want to continue?".
In SAS Management Console, select the Server Manager plug-in and navigate to
the SAS Job Flow Scheduling server definition.
On the Options tab, select the Enable HA check box and click OK to save the change.
================================================================================
### ###################################
### Update config.properties:
### ###################################
To determine the location of the config.properties file in your SAS Studio deployment,
consult the SAS Studio 3.8 Admin Guide for instructions on editing configuration settings:
https://go.documentation.sas.com/doc/en/webeditorcdc/3.8/webeditorag/n0ke09ir9n1sdfn19f9iwz8j8z60.htm
Before editing config.properties, create a backup copy.
/opt/sasinside/config/midtier/Lev1/Web/WebAppServer/SASServer2_1/sas_webapps/sas.sasstudio.war/config
Check for the existence of the following properties (default values are shown):
webdms.allowResultsActions=true (3.8 and 3.81 releases)
webdms.showGitSSLCertPath=false (3.81 release only)
webdms.showSSHGitPassword=true (3.8 and 3.81 releases)
In the file we find ...
egrep 'webdms.allowResultsAction|webdms.showGitSSLCertPath|webdms.showSSHGitPassword' config.properties
webdms.showGitSSLCertPath=false
webdms.showSSHGitPassword=false
webdms.allowResultsActions=true
Add the appropriate entries at the bottom of your config.properties file if
they are not already present.
Assign the true/false value of each based on the needs of your organization.
Save and close the config.properties file.
Restart the SAS Studio services: SASStudioSpawner, SASStudioWebAppServer.
Sign in to SAS Studio. If you changed the default values, confirm that the application behavior is as expected per documentation.