This communities post addresses some questions that customers might have after reading the SAS Customer Intelligence Customer alert – “SAS® Customer Intelligence 360 requires Java 11 for general agents, diagnostic agents, and SDK-based custom agents for 23.08 and later.” The note says that this alert does not apply to the direct agent (SAS® 360 Engage: Direct) or the Optimize agent (SAS® 360 Engage: Optimize). Can customers also expect a requirement to update to Java 11 for these agents later on in the year?  The SAS 360 Engage: Direct and SAS 360 Engage: Optimize agents are bound to SAS®9, and they mimic what is supported by the relevant maintenance version.  The SAS® 9.4M5 (TS1M5)–SAS® 9.4M7 (TS1M7) versions of these agents are bound to SAS 9 and must remain on Java 8 since these SAS versions do not support Java 11.  The agents for SAS® 9.4M8 (TS1M8) are already on Java 11 since SAS 9.4M8 supports this Java version.   Why is this alert relevant only to general agents, diagnostic agents, and SDK-based custom agents?  The general, diagnostic, and custom agents are not bound to SAS 9. Therefore, these are being updated now because support for Java 8 is running out. SAS wants to take advantage of the more secure and newer Java version.   The alert says that customers “will need to update their environment so that the agent is run using Java 11.” Is this a straightforward process, and is involvement from SAS needed?  SAS 9.4M8 is shipped with Java 11, and the customer might decide to use the JRE that SAS provided or a third-party JRE.   If the customer upgrades the general, diagnostics, or custom agents to version 23.08, they need to make sure that these agents point to and use JRE version 11 (JAVA_HOME and PATH environment variables) in the environments that the agents reside in.  SAS 9.4M5-SAS 9.4M7 is shipped with Java 8. If the customer is using SAS 9.4M5–SAS 9.4M7, SAS 9 will still use Java 8 and will not support Java 11.   Therefore, if the customer upgrades the general, diagnostics, or custom agents to version 23.08, the customer should install a separate Java version 11 JRE (Oracle or OpenJDK). Then, the customer should make sure that these agents point to and use JRE version 11 (JAVA_HOME and PATH environment variables) in the environments that the agents reside in.  For example, by altering the file for the mkt-agent-sdk general agent, which is located in the [Your agent folder]/systemd/ folder, you will find something similar to the following:  #set JAVA_HOME to root of the Java 1.11 installation on this machine  JAVA_HOME=/opt/sas/onprem/jdk1.11.0_201  More information can be found in the SAS Customer Intelligence 360: Administration Guide. Search for the topic, “Running the General Agent as a Service in UNIX (systemD)”  Note: Customers should make sure that they are pointing to the correct version for the different agents when they upgrade to 23.08.  If customers are not able to update their environments by August 8, 2023 (for example, a freeze occurs in their IT team sprints), will they still be allowed to update the agents beyond version 23.08 even if they do not have Java 11?  The general, diagnostics, and custom agents—from version 23.08 and later—will require Java 11 to function. Once version 23.08 of these agents is available, it is fine if the customer decides not to upgrade immediately to version 23.08 of these agents. For example, if the customer has a 23.07 version of these agents, that version will be supported for at least three versions after the 23.08 release.  Is Java 17 supported as well as Java 11 with 23.08 Agent SDK?  SAS is not aware of any incompatibilities with using Java 17 to run the agent, but Java 17 has not been tested. Currently, Java 17 is not officially supported, but it should work without any issues.  Do we need to wait until 23.08 to switch to Java 11 or Java 17, or is Java 11 or Java 17 already supported with the current version (23.06)?  Any agent versions prior to 23.08 are not supported with either Java 11 or Java 17. The customer needs to wait until version 23.08 is released. Note: Upgrading the agent to version 23.08 and Java 11 needs to occur at the same time.  Can we upgrade the Java version to version 11 before CI360 version 23.08 is released in August? Are all current Agents compatible with Java 11?  Customers can first update once the agents are available in version 23.08.  Note that customers are not required to do anything on the day on which version 23.08 is released. The old agents running Java 8 will continue to work.     Only the 23.08 agents require Java 11. SAS will continue to support agents that are at least three revisions old.     The first time that the customer needs to take action will be in late 2023 when the 23.07 agents start aging out. However, if the customer needs a newer feature that is available in 23.08, they will need to upgrade sooner.  Please note that the Customer Alert included this link under section “Additional Information”:   This link can also be found in the following location: SAS Help Center: Configuring Agents for an Access Point         ... View more

When you download subject lists from SAS Customer Intelligence 360, they are converted to MATables SAS data sets when necessary. Those data sets are used for in-database processing (that is a customer’s data mart and/or CDM tables) or other SAS specific functionalities such as stored processes. MATables Overview Joining SAS data sets and database tables in SAS is usually a slow process because all of the data from the database table needs to be downloaded onto the to enable the join. So, SAS uses the database bulk load or fast load utility to load the MATables to the database to allow the joins to take place there. This process is typically much faster.   Any MATables that are automatically uploaded to the data mart during the execution are removed after use whenever possible. Freeing Up Disk Space With SAS Customer Intelligence 360, users can delete MATables that are older than x days (for example, MATables that are older than 7 days).   There is logic in the on-premises agent that reuses existing MATables for ad hoc counts requests. However, if those MATables are missing, they are simply regenerated as necessary. Note that to regenerate the missing MATables, the logic requires that the segment be re-executed.   SAS Customer Intelligence 360 does not rely on pre-existing MATables for segments or link nodes, which are stored in SAS Customer Intelligence 360. This behavior means that if those tables are removed, their dependencies are not broken.  ... View more

An issue has been found with the latest MA 6.5 hotfix – Z77021 released on December 17st.   If you are using custom details, please don’t apply the hotfix. If you have applied the hot fix already and encounter issues with custom details, please follow the instructions documented in the SAS Note, see details below.   Problem Note 65312: A pop-up error occurs when you create a custom detail using the selection group and set up a required field in SAS® Customer Intelligence   When you create a custom detail in SAS Customer Intelligence 6.5, you might encounter the following pop-up window:     To correct this error: 1. Open the services-config.xml file that is located in the following directory: SAS-configuration-directory/Lev1\Web\SASServer6_1/sas_webapps/sas.customerintelligencestudio.war/WEB-INF/flex 2. Locate the allow-classes block in the services-config.xml file and include the following line: <class name="flex.messaging.io.ObjectProxy" /> 3. Save the file and restart the SASServer6_1 web application server.   The issue will be corrected asap with hot fix Z77022.  ... View more