Problem Note 47113: Campaigns are not locked in SAS® Customer Intelligence Studio when you execute the optimization process in SAS® Marketing Optimization
When you are running the optimization process in SAS Marketing Optimization, the
campaigns that belong to an optimization group in SAS Customer Intelligence Studio do not lock. As a result, users can modify campaigns in SAS Customer Intelligence Studio while the optimization in SAS Marketing Optimization is executed. When that happens, the optimization process fails.
Click the Hot Fix tab in this note to access the hot fix for this issue.
After you apply the hot fix, you need to set the following option as a Java Virtual Machine (JVM) option for your web application server:
-Dsas.ci.mo.createInputData.lockCampaignGroupAndMembers
The method for setting this option is different for each vendor of web application servers. Check your Instructions.html file to locate the JVM options for you web application server.
Setting this option directs SAS Marketing Automation to lock the campaign group and its members during the optimization process.
The following example shows you how to set the option for the JBoss web application server. The SAS® Deployment Wizard sets default values for JBoss in the JAVA_OPTS environment variable that resides in C:\JBoss-installation-directory\bin\SASServer6.bat. Open the BAT file and add the option discussed previously to the end of the JAVA_OPTS environment variable, as follows:
:start_as_script
set JAVA_HOME=C:\jdk1.6.0_16
set JAVA_OPTS=-Xms1024m -Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=512m -Xss256k -XX:NewSize=128m
-XX:MaxNewSize=256m -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:+DisableExplicitGC
-XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled -Dcom.sun.management.jmxremote
-Djava.awt.headless=true -Djboss.platform.mbeanserver
-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Dsas.container.identifier=jboss -Dcom.sas.services.logging.disableRemoteList=true
-Dcom.sas.services.logging.disableRemoteLogging=true -Dsas.jms.authentication.decorator=false
-Dsas.svcs.http.max.connections=20 -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false
-Dmulticast_udp_ip_ttl=1 -Dmulticast.address=239.21.16.70 -Dmulticast.port=8561
-Djava.security.policy="C:\jboss-4.2.0.GA\server\SASServer6\conf\sas.all.permissions.policy"
-Djboss.home.dir="C:\jboss-4.2.0.GA" -Djboss.server.home.dir="C:\jboss-4.2.0.GA\server\SASServer6"
-Dsas.deploy.dir="C:\jboss-4.2.0.GA\server\SASServer6\deploy_sas"
-Dcom.sas.log.config.url=file:///C:/SAS/Config/Lev1/Web/Common/LogConfig/ -Dsas.auto.publish.port=8580
-Dsas.ci.mo.createInputData.lockCampaignGroupAndMembers
Operating System and Release Information
SAS System | SAS Marketing Automation | Microsoft Windows Server 2008 | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Microsoft Windows Server 2008 for x64 | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Windows 7 Enterprise 32 bit | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Windows 7 Enterprise x64 | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Windows 7 Home Premium 32 bit | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Windows 7 Home Premium x64 | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Windows 7 Professional 32 bit | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Windows 7 Professional x64 | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Windows 7 Ultimate 32 bit | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Windows 7 Ultimate x64 | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
64-bit Enabled AIX | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
64-bit Enabled HP-UX | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
64-bit Enabled Solaris | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
HP-UX IPF | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Linux | 5.4 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
*
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: | high |
Date Modified: | 2012-08-15 10:39:52 |
Date Created: | 2012-08-01 11:56:22 |