SAS 9.1.3 Integration Technologies » Developer's Guide


SAS BI Web Services
Using Web Services
Deciding Between .NET and Java
Writing SAS Programs for Web Services
Discover Method
Execute Method
Securing Web Services
Security for .NET Using WSE 2.0
Security for Java
Samples
Sample PROC MEANS
SAS Integration Technologies Samples
Reference Materials
How to Implement a Web Service with SAS
Java Technology and Web Services
Microsoft XML Web Services
SAS BI Web Services

Deciding Between .NET and Java

There are some differences between SAS BI Web Services for .NET and SAS BI Web Services for Java. Following are some frequently asked questions that you can use to help you decide which version is the right one for you to install, and some differences that exist for the Web service client.

Installation and Administration Differences

  • What operating environment are you using?
    • SAS BI Web Services for .NET can only be installed in the Windows XP, Windows 2000, and Windows 2003 operating environments.
    • SAS BI Web Services for Java can be installed in any operating environment that can understand Java.

  • How do you want to administer the Web services?
    • SAS BI Web Services for .NET are administered using IIS.
    • SAS BI Web Services for Java are administered using Apache Tomcat or BEA Weblogic. If you install SAS BI Web Services for Java, you will also need to have a Java Virtual Machine for an application server.

SAS BI Web Services for .NET and SAS BI Web Services for Java also differ in the way they handle logging and configuration. SAS BI Web Services for .NET use .NET logging, and SAS BI Web Services for Java use SAS Foundation Services for logging.

Client Differences

Web service clients cannot generally identify differences between SAS BI Web Services for .NET and SAS BI Web Services for Java. As long as the client adheres to the usage rules for Web services, the client should be able to use either platform.

One difference for the Web service client is how you get the WSDL. If you use SAS BI Web Services for .NET, you get the WSDL by using a URL that ends with sasxmla.asmx?WSDL. If you use SAS BI Web Services for Java, you get the WSDL by using a URL that ends with xmla.wsdl. In both cases, the actual endpoint is specified in the WSDL file.

Another difference for the Web service client is how the path is returned for the name of the stored process (DataSourceName). SAS BI Web Services for Java return a BIP URL. SAS BI Web Services for .NET return a simple path. In both cases, you get the name of the stored process to invoke by using the Discover method of the same Web service.