SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 40515: The SAS® Deployment Wizard erases entries in the SAS® Marketing Optimization EAR file after you change the host

DetailsHotfixAboutRate It

If you rebuild the SAS Marketing Optimization EAR file, the config.properties file will have an incorrect connection string for the JNDI settings. Therefore, it is necessary to modify the config.properties file and add the correct value.

This is an example of the incorrect config.properties file that occurs after you change the host:

# JNDI properties jndi.properties.java.naming.factory.initial= jndi.properties.java.naming.provider.url=://:

In this example, the file is missing the string for the host connection.

Depending on your web application server, add the correct java.naming.factory and the java.naming.provider. Specify the host name and bootstrap based on your environment.

Here are examples:

For WebSphere:

# JNDI properties jndi.properties.java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory jndi.properties.java.naming.provider.url=iiop://host-name:bootstrap_address-port

For JBoss:

# JNDI properties jndi.properties.java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory jndi.properties.java.naming.provider.url=jnp://host-name:bootstrap_Address-port

For WebLogic:

# JNDI properties jndi.properties.java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory jndi.properties.java.naming.provider.url=t3://host-name:bootstrap_Address-port

After you make the necessary change, redeploy the application within the web application server.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Marketing OptimizationMicrosoft® Windows® for x645.3_M25.49.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Datacenter Edition5.3_M25.49.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Enterprise Edition5.3_M25.49.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Standard Edition5.3_M25.49.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 for x645.3_M25.49.2 TS2M39.2 TS2M3
Microsoft Windows Server 20085.3_M25.49.2 TS2M39.2 TS2M3
Microsoft Windows Server 2008 for x645.3_M25.49.2 TS2M39.2 TS2M3
Microsoft Windows XP Professional5.3_M25.49.2 TS2M39.2 TS2M3
Windows 7 Enterprise 32 bit5.3_M25.49.2 TS2M39.2 TS2M3
Windows 7 Enterprise x645.3_M25.49.2 TS2M39.2 TS2M3
Windows 7 Home Premium 32 bit5.3_M25.49.2 TS2M39.2 TS2M3
Windows 7 Home Premium x645.3_M25.49.2 TS2M39.2 TS2M3
Windows 7 Professional 32 bit5.3_M25.49.2 TS2M39.2 TS2M3
Windows 7 Professional x645.3_M25.49.2 TS2M39.2 TS2M3
Windows 7 Ultimate 32 bit5.3_M25.49.2 TS2M39.2 TS2M3
Windows 7 Ultimate x645.3_M25.49.2 TS2M39.2 TS2M3
Windows Vista5.3_M25.49.2 TS2M39.2 TS2M3
Windows Vista for x645.3_M25.49.2 TS2M39.2 TS2M3
64-bit Enabled AIX5.3_M25.49.2 TS2M39.2 TS2M3
64-bit Enabled HP-UX5.3_M25.49.2 TS2M39.2 TS2M3
64-bit Enabled Solaris5.3_M25.49.2 TS2M39.2 TS2M3
HP-UX IPF5.3_M25.49.2 TS2M39.2 TS2M3
Linux for x645.3_M25.49.2 TS2M39.2 TS2M3
Solaris for x645.3_M25.49.2 TS2M39.2 TS2M3
Microsoft Windows 8 Enterprise 32-bit6.1_M19.3 TS1M2
Microsoft Windows 8 Enterprise x646.1_M19.3 TS1M2
Microsoft Windows 8 Pro 32-bit6.1_M19.3 TS1M2
Microsoft Windows 8 Pro x646.1_M19.3 TS1M2
Microsoft Windows 8.1 Enterprise 32-bit6.1_M19.3 TS1M2
Microsoft Windows 8.1 Enterprise x646.1_M19.3 TS1M2
Microsoft Windows 8.1 Pro6.1_M19.3 TS1M2
Microsoft Windows 8.1 Pro 32-bit6.1_M19.3 TS1M2
Microsoft Windows Server 2008 R26.1_M19.3 TS1M2
Microsoft Windows Server 2012 Datacenter6.1_M19.3 TS1M2
Microsoft Windows Server 2012 R2 Datacenter6.1_M19.3 TS1M2
Microsoft Windows Server 2012 R2 Std6.1_M19.3 TS1M2
Microsoft Windows Server 2012 Std6.1_M19.3 TS1M2
* 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.