Problem Note 40515: The SAS® Deployment Wizard erases entries in the SAS® Marketing Optimization EAR file after changing the host
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
| SAS System | SAS Marketing Optimization | Microsoft® Windows® for x64 | 5.3_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2003 Datacenter Edition | 5.3_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2003 Enterprise Edition | 5.3_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2003 Standard Edition | 5.3_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2003 for x64 | 5.3_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2008 | 5.3_M2 | | 9.2 TS2M3 | |
| Microsoft Windows Server 2008 for x64 | 5.3_M2 | | 9.2 TS2M3 | |
| Microsoft Windows XP Professional | 5.3_M2 | | 9.2 TS2M3 | |
| Windows 7 Enterprise 32 bit | 5.3_M2 | | 9.2 TS2M3 | |
| Windows 7 Enterprise x64 | 5.3_M2 | | 9.2 TS2M3 | |
| Windows 7 Home Premium 32 bit | 5.3_M2 | | 9.2 TS2M3 | |
| Windows 7 Home Premium x64 | 5.3_M2 | | 9.2 TS2M3 | |
| Windows 7 Professional 32 bit | 5.3_M2 | | 9.2 TS2M3 | |
| Windows 7 Professional x64 | 5.3_M2 | | 9.2 TS2M3 | |
| Windows 7 Ultimate 32 bit | 5.3_M2 | | 9.2 TS2M3 | |
| Windows 7 Ultimate x64 | 5.3_M2 | | 9.2 TS2M3 | |
| Windows Vista | 5.3_M2 | | 9.2 TS2M3 | |
| Windows Vista for x64 | 5.3_M2 | | 9.2 TS2M3 | |
| 64-bit Enabled AIX | 5.3_M2 | | 9.2 TS2M3 | |
| 64-bit Enabled HP-UX | 5.3_M2 | | 9.2 TS2M3 | |
| 64-bit Enabled Solaris | 5.3_M2 | | 9.2 TS2M3 | |
| HP-UX IPF | 5.3_M2 | | 9.2 TS2M3 | |
| Linux for x64 | 5.3_M2 | | 9.2 TS2M3 | |
| Solaris for x64 | 5.3_M2 | | 9.2 TS2M3 | |
*
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: | 2010-11-15 13:44:51 |
| Date Created: | 2010-08-04 12:33:43 |
