SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 40701: The SAS® Information Delivery Portal web application cannot communicate with other SAS® web applications

DetailsAboutRate It

The SAS Information Delivery Portal might have problems communicating with other SAS web applications (for example, the SAS Stored Process web application) when there are multiple servers defined in the IBM WebSphere application server and when the portal is moved to a different server.

You must manually change the IBM WebSphere session cookie name after you move the SAS Information Delivery Portal web application from one IBM WebSphere server to a different server. This change is necessary because the WebSphere cookie name is assigned based on the server name.

In order for the SAS® Information Delivery Portal to work properly after it is moved to a new WebSphere server, you must modify the web.xml file within the deployed instance of the portal and set the following parameter to reflect the correct server name:

<init-param> <param-name>SESSION_COOKIE_NAME</param-name> <param-value>JSESSIONIDSASServer1</param-value> </init-param>

The syntax for the WebSphere cookie name is JSESSIONIDserver-name. In the example above, the server name is SASServer1. So, for example, if the portal application is moved to a server called Baseball, then you must change JSESSIONIDSASServer1 to JSESSIONIDBaseball.

In addition to making this change in the location of the deployed portal web application, you must also change the server name in the <init-param> element of the web.xml.orig file, which resides in SAS-installation-directory\SASInformationDeliveryPortal\4.2\Configurable\wars\sas.portal\WEB-INF. You must make this change to ensure that the server name is retained in the event that the SASPortal4.3.ear file is ever rebuilt and redeployed.

The original element within the web.xml.orig file looks similar to the following example:

<init-param> <param-name>SESSION_COOKIE_NAME</param-name> <param-value>##SESSION_COOKIE_NAME##</param-value> </init-param>

You must change the parameter so that it reflects the new server name (Baseball). Change the value from ##SESSION_COOKIE_NAME## to JSESSIONIDBaseball, as shown here:

<init-param> <param-name>SESSION_COOKIE_NAME</param-name> <param-value>JSESSIONIDBaseball</param-value> </init-param>


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Information Delivery Portalz/OS4.34.39.2 TS2M39.2 TS2M3
Microsoft® Windows® for 64-Bit Itanium-based Systems4.34.39.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Datacenter 64-bit Edition4.34.39.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Enterprise 64-bit Edition4.34.39.2 TS2M39.2 TS2M3
Microsoft Windows XP 64-bit Edition4.34.39.2 TS2M39.2 TS2M3
Microsoft® Windows® for x644.34.39.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Datacenter Edition4.34.39.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Enterprise Edition4.34.39.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Standard Edition4.34.39.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 for x644.34.39.2 TS2M39.2 TS2M3
Microsoft Windows Server 20084.34.39.2 TS2M39.2 TS2M3
Microsoft Windows Server 2008 for x644.34.39.2 TS2M39.2 TS2M3
Microsoft Windows XP Professional4.34.39.2 TS2M39.2 TS2M3
Windows 7 Enterprise 32 bit4.34.39.2 TS2M39.2 TS2M3
Windows 7 Enterprise x644.34.39.2 TS2M39.2 TS2M3
Windows 7 Home Premium 32 bit4.34.39.2 TS2M39.2 TS2M3
Windows 7 Home Premium x644.34.39.2 TS2M39.2 TS2M3
Windows 7 Professional 32 bit4.34.39.2 TS2M39.2 TS2M3
Windows 7 Professional x644.34.39.2 TS2M39.2 TS2M3
Windows 7 Ultimate 32 bit4.34.39.2 TS2M39.2 TS2M3
Windows 7 Ultimate x644.34.39.2 TS2M39.2 TS2M3
Windows Vista4.34.39.2 TS2M39.2 TS2M3
Windows Vista for x644.34.39.2 TS2M39.2 TS2M3
64-bit Enabled AIX4.34.39.2 TS2M39.2 TS2M3
64-bit Enabled HP-UX4.34.39.2 TS2M39.2 TS2M3
64-bit Enabled Solaris4.34.39.2 TS2M39.2 TS2M3
HP-UX IPF4.34.39.2 TS2M39.2 TS2M3
Linux4.34.39.2 TS2M39.2 TS2M3
Linux for x644.34.39.2 TS2M39.2 TS2M3
Solaris for x644.34.39.2 TS2M39.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.