Changes in AppDev Studio 3.41

General Differences

Requires SAS 9.3

Projects created in AppDev Studio 3.41 use the SAS 9.3 jars. Projects imported from AppDev Studio 3.4 must be upgraded to use the SAS 9.3 jars before development of those projects can continue.

Requires Eclipse 3.6.x and the Eclipse Web Tools Platform 3.2.x

AppDev Studio 3.41 runs on Eclipse 3.6.x and the Eclipse Web Tools Platform 3.2.x. The minimum version of the Eclipse Web Tools Platform is 3.2.1.

New Compiler Warning Type

The Eclipse 3.6.x Java compiler has been changed to warn you about the use of raw types even if the code is marked with the @SuppressWarnings("unchecked") statement.

To prevent these warnings, Java files imported from AppDev Studio 3.4 need @SuppressWarnings("unchecked") statements changed to the following:

@SuppressWarnings("rawtypes")

If this code causes the unchecked warnings to reappear, suppress both types of warnings by changing the code to the following:

@SuppressWarnings({"unchecked", "rawtypes"})

Templates in AppDev Studio 3.41 already include these changes where needed.

BI Server Profiles Now Include Local System Settings

The BI Server Profile Properties now includes three settings that help AppDev Studio acquire the BI Server information.

New Local System Settings

Setting	System Property	Default value
Prefer IPv4 Stack	java.net.preferIPv4Stack	true Must be set to true on Windows Vista and Windows 7 to work with an EBI configured to use IPv4. Because the default for EBI installations is IPv4, the setting defaults to true.
JGroups Bind Address	jgroups.bind_addr	[not set] When the address is not set, JGroups selects a network interface. On a system with several network interfaces, JGroups might pick a network interface that is unable to connect to the BI Server middle tier. In this situation, the IP address of a network interface that can connect to the BI Server middle tier should be specified in the JGroups Bind Address.
Multicast TTL	multicast_udp_ip_ttl	32 To limit the multicast broadcasts, reduce this value to reach only the BI Server middle tier. If the BI Server middle-tier is on the same system as AppDev Studio, set the value to 0.

These new parameters are output to the launchParameters.txt file that is generated by most of the SAS Web Application templates. However, AppDev Studio cannot use that file to acquire BI Server information directly. Instead, it relies on the Eclipse system property settings in eclipse.ini. Because a BI Server acquisition can succeed only when these new properties match between the BI Server Profile and the running Eclipse, be sure to add these settings to eclipse.ini.

Acquisition Timeout Increased

The Acquisition Timeout for BI Server acquisitions within AppDev Studio has been increased from 10 seconds to 20 seconds to avoid failures caused by the slow loading of plug-ins when they were first used in Eclipse. The timeout used by the BI Server middle tier and test servers in Eclipse remains 10 seconds.

Metadata Server Connections No Longer Expire

When logging in to a Metadata server using a Connection Profile, the timeout for the associated SAS SessionContext is now disabled.

SAS Project Differences

New 9.3.0.0000 Versions of the SAS Facets

Building on the facet support in the Eclipse Web Tools Platform to control the configuration of SAS Web application projects, AppDev Studio 3.41 provides new versions of the SAS Java Components and SAS Web Infrastructure Platform facets.

New SAS Tooling Library

All SAS projects now include the SAS Tooling library and the SAS Repository library. The Tooling library contains Java classpath entries needed at build time. These entries are not needed at runtime, which is why they are in a separate library. Currently there is only one entry in the SAS Tooling library. Upgrading the facet of an AppDev Studio 3.4 SAS Web application project automatically adds the SAS Tooling library to the project. To upgrade SAS Java projects, the library must be added manually.

Template Differences

Credential Changes for SAS Stored Process Templates

The Java client for executing a SAS Stored Process template now uses trusted (privileged server account) credentials to deploy SAS Foundation Services. Access to the SAS stored process is controlled with user credentials. Projects must be updated manually to account for these changes.

New Log4j Logging Configuration Template

A new Log4j Logging Configuration template is now available to SAS Web application projects. Because this template requires only the SAS Java Components facet, it can be added to Web application projects that are based on the Foundation Services, and also to SAS Web application projects that use the Web Infrastructure Platform. This logging template replaces the AppDev Studio 3.4 Logging Configuration template, which depended on the now-deprecated Foundation Services Logging Service.

Updated Editable Portlet Template to Use Portal Logger

The SAS Information Delivery Editable Portlet template now uses com.sas.portal.Logger in place of the deprecated com.sas.services.logging.LoggerInterface. The other portlet templates already use the com.sas.portal.Logger to perform logging. Imported AppDev Studio 3.4 editable portlets must be manually updated.

Application ID Field Now Defaults to Blank in the Create Application Metadata Template

The Create Application Metadata template now leaves the Application ID field blank. Imported SAS Web application projects must change the value to a blank string. New validation in SAS 9.3 requires that this value be blank for Web applications developed by customers. This field might be removed in a future version of AppDev Studio.

Deprecated Tools

Table Server Removed

The Table Server is no longer available. Projects imported from AppDev Studio 3.4 that use the Table Server must be updated to use the SAS IOM or SAS ShareNet JDBC driver to continue working in SAS 9.3.

SAS Visual Data Explorer Removed

The SAS Visual Data Explorer is no longer available. SAS Web Application projects can no longer display Information Map Viewer Servlet content.

In SAS 9.3, Information Maps are displayed by SAS Web Report Viewer or SAS Web Report Studio. To support this shift, the Report Viewer Servlet template can now select Information Maps and Reports. Data Explorations and Information Maps that use advanced features, such as filters that use prompting, must be converted to reports to achieve the same or similar functionality. Portlets based on Information Maps must be altered to remove their dependency on the SAS Visual Data Explorer. The AppDev Studio 3.41 templates that are based on Information Map portlets already incorporate the needed changes.