Problem Note 35885: Systems with multiple IP addresses might generate an incorrect WSDL when using the "Deploy as a Web Services" wizard
On systems that have multiple NIC cards or mutltiple IP addresses, you might notice a different IP address in the WSDL that is generated by the "Deploy as a Web Service" wizard in the SAS® Management Console.
For example, when viewing a WSDL from the SAS BI Web Services application at the following location, the WSDL will contain an incorrect hostname:
http://10.x.x.x:8080/SASBIWS/services/multiplynumbersBasic?wsdl
The incorrect hostname will be in the following line:
<soap:address location="http://192.x.x.x:8080/SASBIWS/services/multiplynumbersBasic" />
To work around this issue you should perform the following steps:
- Uncomment the line noted below which is in the <SAS_INSTALL_DIR>\SASWebInfrastructurePlatform\9.2\Configurable\wars\sas.biws\jboss\WEB-INF\conf\axis2.xml.orig file.
<!--<parameter name="hostname" locked="true">myhost.com</parameter>-->
- Change myhost.com to the correct hostname
- Rebuild the SASWebInfrastructurePlatform ear file using the SAS® Deployment Manager.
- Redeploy the new ear file.
To deploy the new ear file, perform the follwing steps:
- Launch the SAS® Deployment Manager
.
- Choose a Language and click OK
.
- Select Rebuild Web Apllications and click Next
.
- Select Configuration Directory and click Next
.
- Enter the password for the sasadm@saspw and click Next
.
- Select SAS Web Infrastructure Platform and click Next
.
- Click Start
.
When the application has finished, you should redeploy the following 4 ear files that are part of the SAS Web Infrastructure Platform.
- sas.storedprocess9.2.ear
- sas.wip.apps9.2.ear
- sas.wip.scs9.2.ear
- sas.wip.services9.2.ear
For instructions on deployment of these ear files, consult the SAS® 9.2
Intelligence Platform: Web Application Administration Guide.
Operating System and Release Information
SAS System | SAS Enterprise BI Server | z/OS | 4.2 | | 9.2 TS2M2 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 4.2 | | 9.2 TS2M2 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 4.2 | | 9.2 TS2M2 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 4.2 | | 9.2 TS2M2 | |
Microsoft Windows XP 64-bit Edition | 4.2 | | 9.2 TS2M2 | |
Microsoft® Windows® for x64 | 4.2 | | 9.2 TS2M2 | |
Microsoft Windows Server 2003 Datacenter Edition | 4.2 | | 9.2 TS2M2 | |
Microsoft Windows Server 2003 Enterprise Edition | 4.2 | | 9.2 TS2M2 | |
Microsoft Windows Server 2003 Standard Edition | 4.2 | | 9.2 TS2M2 | |
Microsoft Windows XP Professional | 4.2 | | 9.2 TS2M2 | |
Windows Vista | 4.2 | | 9.2 TS2M2 | |
64-bit Enabled AIX | 4.2 | | 9.2 TS2M2 | |
64-bit Enabled HP-UX | 4.2 | | 9.2 TS2M2 | |
64-bit Enabled Solaris | 4.2 | | 9.2 TS2M2 | |
HP-UX IPF | 4.2 | | 9.2 TS2M2 | |
Linux | 4.2 | | 9.2 TS2M2 | |
Linux for x64 | 4.2 | | 9.2 TS2M2 | |
Solaris for x64 | 4.2 | | 9.2 TS2M2 | |
*
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.
Systems with multiple ip addresses may generate an incorrect WSDL when using the "Deploy as Web Services Wizard..."
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2009-06-09 06:44:19 |
Date Created: | 2009-05-11 21:16:07 |