Problem Note 69674: Scrolling in the Select Node of SAS® Marketing Automation is slow when there are many data items in the information map
When you scroll in the Select node of SAS Marketing Automation, the scroll is slow when there are many data items in the information map. The general rule is to limit the number of data items in the information map to 2,000 or fewer. There are cases when having 2,000 data items can cause scrolling to be slower, making it appear as if the scroll bar moves suddenly.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Post-Hot-Fix Instructions
Note: After you apply the fix for this issue, you need to disable the look-ahead functionality. To do that, add the Java option -Dsas.ci.disableSelectNodeLookAhead as explained below.
Linux or Other UNIX Operating Environments
Add the option to the setenv.sh file, as shown below:
JAVA_OPTS="$JVM_OPTS $AGENT_PATHS $JAVA_AGENTS $JAVA_LIBRARY_PATH" JAVA_OPTS="$JAVA_OPTS -Dsas.ci.disableSelectNodeLookAhead"
The setenv.sh file is typically located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory. You need to restart the middle tier so that the settings can take effect.
Microsoft Windows Operating Environments
These are environments where the servers are started as Windows Services. Add the option to the wrapper.conf file, as shown below:
wrapper.java.additional.XX=-Dsas.ci.disableSelectNodeLookAhead
Note: In this option, XX specifies the next number in the sequence for your machine.
The wrapper.conf file is typically located in the SAS-configuration-directoryLev1\Web\WebAppServer\SASServer6_1\conf directory.
You need to restart the middle tier so that the settings can take effect.
Operating System and Release Information
SAS System | SAS Marketing Automation | Microsoft® Windows® for x64 | 6.6 | | | |
64-bit Enabled AIX | 6.6 | | | |
64-bit Enabled Solaris | 6.6 | | | |
Linux for x64 | 6.6 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-01-24 15:05:45 |
Date Created: | 2022-11-11 03:36:10 |