Updating Template Content in SAS Web Application Projects That Use the SAS Web Infrastructure Platform :: SAS(R) AppDev Studio(TM) 3.41 Eclipse Plug-ins: Migration Guide

Update Content for a SAS Web Infrastructure Platform Application Metadata Creation Template

The following two processes update the content from a SAS Web Infrastructure Platform Application Metadata Creation template to work with a new SAS 9.3 EBI server by re-applying the template to the project and selecting the SAS 9.3 BI Server Profile that you want to use with the project.

The AppDev Studio Template Wizard stores the multicast address and port of the last SAS BI Server Profile that a project used in the project's .SASTemplateResources file. To remove the relevant lines from that file and force the project to reacquire the multicast properties for use in the launchparameters.txt file, follow these steps:

In the Navigator view, expand the root folder of the project to update.
Right-click the .SASTemplateResources file and select Open WithText Editor.

Delete these two lines and all intervening lines:

<managed-parameter name="multicast.launch.system.properties">
[...]
</managed-parameter>

Save and close the file.

To reapply the metadata creation template, follow these steps:

Expand the project's metadata folder.
If manual changes have been made to the Application.xml file in that folder, or if you are unsure if manual modifications have been made, rename the Application.xml file to Application92.xml.
From the main menu, select FileNewOther.
Expand SAS AppDev Studio, select Add Template Content to Project, and click Next.
In the Project field, select the project to update.
In the Templates tree, expand the SAS Java Web Application and SAS Web Infrastructure Platform Support categories, and then select SAS Web Infrastructure Application Metadata Creation. Click Next.
When the Template Wizard fails to display the SAS BI Server Profile for the old, invalid multicast address and port, a new profile called Auto-created Profile is generated. This generated SAS BI Server Profile contains the stored multicast address and port and the defaults for all remaining settings.

When AppDev Studio attempts to acquire the BI Server information for an Auto-created Profile, click Cancel, or allow the acquisition to fail. Failure takes approximately 20 seconds.
Select a valid BI Server Profile.
Update the Application Name and Description.
Delete the contents of the Application ID field.
Update the Protocol, and Web Server Host and port to match the ADS Apache Tomcat server (or server of your choice).
Click Finish to apply the template.
If you saved a copy of the original Application.xml in step 2, select both Application.xml and Application92.xml and select Compare WithEach Other. Port any other changes to the new Application.xml file.
Remove the automatically generated profile.
1. Select WindowPreferences.
2. Expand SAS AppDev Studio and select SAS BI Profiles.
3. From the BI Server Profile list, select the Auto-created Profile, and click Remove.
4. Confirm the deletion, and then click OK.

Be sure to run the script to actually create the server metadata.

Remove Content for an Information Map Viewer Servlet (uses SAS Visual Data Explorer and SAS WIP) Template

Because the SAS Visual Data Explorer is no longer available in SAS 9.3, content from the Information Map Viewer Servlet (uses SAS Visual Data Explorer and SAS WIP) template must be removed from your project. To prevent these templates from being displayed by the Examples Welcome File page, follow these steps:

In the Project Explorer, expand the Java Resources folder, the src folder, and then the folder or folders that represent the packages where the servlets for the Information Map Viewer Servlet template were placed. The default folder is servlets.
In the WEB-INF folder, right-click the sas-examples.xml file and open it with a Text Editor or XML Editor.
In the editor, delete the <type> element (and its children) whose name attribute is Information Map Viewer Servlet (uses SAS Visual Data Explorer and SAS WIP). Save and close the file.

To find the servlets to delete, continue with these steps:

In the WEB-INF folder, right-click the web.xml file, and open it with a Text Editor or XML Editor.
In the spring-config folder, right-click the webapp-config.xml file, and open it with a Text Editor or XML Editor.
From the main menu, select SearchFile.
In the Search dialog box, enter VisualDataExplorerServlet in the Contains text field.
Enter *.java in the File name patterns field.
Select Enclosing projects for the Scope, and click OK to perform the search.

All occurrences of the VisualDataExplorerServlet string are displayed. The string will appear twice in any servlet produced by the Information Map Viewer Servlet (uses SAS Visual Data Explorer and SAS WIP) template.

For each servlet Java file that appears in the Search view, perform the following steps:
1. In the web.xml file, delete the <servlet> element whose <servlet-name> element contains the servlet base name. Also delete all of its children.
2. Also in the web.xml file, delete the <servlet-mapping> element whose <servlet-name> element contains the servlet base name. Also delete all of its children.
3. In the webapp-config.xml file, delete the <bean> element whose id attribute contains the name of the Java file without the .java extension.
4. In the WebContent folder, right-click the JSP file that corresponds to the servlet Java file and select Delete. The JSP filename follows the pattern <servletBaseName>Viewer.jsp.
5. Right-click the servlet Java file and select Delete.

Remove any other servlets not identified in the search. Save and close both the web.xml file and the webapp-config.xml file.

Update Content for a Report Viewer Servlet (uses SAS Web Report Viewer and SAS WIP) Template

Because the SAS Visual Data Explorer and the Information Map Viewer Servlet template are no longer available, the ability to display a SAS Information Map is now provided by the Report Viewer Servlet (uses SAS Web Report Viewer and SAS WIP) template.

Both SAS Web Report Viewer and SAS Web Report Studio can display reports that are generated from an Information Map. However, these generated reports do not support all the features of the now-deprecated SAS Visual Data Explorer, nor do SAS Web Report Viewer and SAS Web Report Studio always deal with Information Map features in the same way. For example, if you generate a report from an Information Map with a filter that uses a prompt, SAS Web Report Viewer and Web Report Studio handle the prompt differently. To achieve equivalent functionality, a new report must be created based on the Information Map. Similarly, because Data Explorations cannot be displayed by SAS Web Report Viewer or SAS Web Report Viewer Studio, a new report is required.

To manually update all the Report Viewer Servlet templates in your project to display Information Maps without reapplying the template, follow these steps:

Select the project to update.
From the main menu, select SearchFile.
In the Contains text field, enter:

filterList.add("Report");
In the File name patterns field, enter *.java.
For the Scope select Enclosing projects, and click OK to perform the search.
For each occurrence of filterList.add("Report"); in the Search view, perform the following:
1. From the main menu, select NavigateNext Match. This will open the Java file in an editor and take you to the line where the text was found.
2. Above the filterList.add("Report"); line add a new line:
  
  filterList.add("InformationMap");
3. Save and close the file.

Rebuild the project if it is not building automatically.

Update the Java Files for a SAS Stored Process Servlet (uses SAS WIP) Template

This process updates the StoredProcessConnection.java and StoredProcessFacade.java files for the SAS Stored Process Servlet template that uses the Web Infrastructure Platform. If you are using Foundation Services, see Update the Java Files for a SAS Stored Process Servlet (uses SAS FS) Template.

There are two ways to update these Java files, which are produced by the SAS Stored Process Servlet (uses SAS WIP) template. The first way is to add a new stored process template to the project. The addition of the template updates the Java files automatically.

The second way, documented here, is to copy the Java files from a new, temporary project that uses the AppDev Studio 3.41 SAS Web Infrastructure Platform and then insert them into the migrated project. Follow these steps to create the temporary project and add the stored process template:

Select FileNewOther, expand SAS AppDev Studio and select SAS Web Application Project. Then click Next.
Enter a name for this temporary project and click Next.
Enable Add Template Content, and select the SAS Stored Process Servlet (uses SAS WIP) template under the SAS Web Application Examples category. Click Next.
Click Next and then select a BI Server Profile. Click Next again.

The BI Server Remote Services for this profile must be running.
If not already connected to a BI Server, click the Change button and log on.
Click the Change button in the Stored Process section, and select a stored process. Click OK, and then Finish.

To copy the StoredProcessConnection.java and StoredProcessFacade.java files, follow these steps:

In the Project Explorer view for the new temporary project, expand Java Resources, src, and support.storedprocess.
Expand the same items in the project being migrated.
Select both the StoredProcessConnection.java and StoredProcessFacade.java files in the source project, and then right-click and select Copy.
In the migrated project, right-click on the support.storedprocess package, and select Paste.
When prompted to confirm overwriting, click Yes to All.

If either of the files in the migrated project are open in editors, switch to those editors and select FileSave.

The Java files are now updated.
Delete the temporary project.

Stored process servlets in the project being migrated will contain new generics warnings. These warnings can be suppressed by changing each of the @SuppressWarnings found in the Java file to @SuppressWarnings({“unchecked”, "rawtypes"}). You can also review how the warnings were addressed in the stored process servlet in a new project and make the same change in the migrated project.