AppDev Studio 1.2 Patch 2

Please read this file carefully as it contains the necessary information to install AppDev Studio 1.2 Patch 2 on your existing AppDev Studio installation. This patch is designed to update version 1.2 of AppDev Studio. It contains all of the fixes that were in AppDev Studio 1.2 Patch 1 as well as some additional fixes. It will not work with any other version of AppDev Studio. To upgrade a previous version of AppDev Studio, contact your SAS representative and ask for the latest version of AppDev Studio.

For detailed information about the fixes the are part of this patch, please read the list of updates.

When you unzip the patch file, the files will be put in a folder named ADS12Patch2. In the instructions below all references to files and folders are assuming that ADS12Patch2 is your current folder.

This patch contains updates for your AppDev Studio 1.2 installation as well as your production web server and SAS server. Please follow the steps listed below to update all of the machines at your site. It is important that you update all of the machines with this patch.

Some fixes in this patch will provide additional performance improvements or functionality when this patch is installed in combination with the EIS hotfix for SAS 8.1. Please see the updates file for a list of affected fixes.

For SAS 8.1 users, installation of the EIS hotfix is recommended for optimal performance.

To update the AppDev Studio Installation:

1. Invoke the program ADS12_patch2.exe, which is the patch installation program.
2. Follow the instructions in the install program.

To update your production web server:

1. In the sasweb folder there are two archive files, sasweb.zip and sasweb.tar.
2. Copy the appropriate archive file to your web server machine.
3. Be sure that the tools you use to update the web server preserves the case of the files in the archive.
4. Extract the contents of the archive file into the web server home folder.
5. Copy the webAF.jar, webEIS.jar, webAFNC.jar and webEISNC.jar files to the web server. These files are located in the  ADS12Patch2 folder.
6. Move webAF.jar to the sasweb\webAF folder under the web server home folder.
7. Move webEIS.jar to the sasweb\webEIS folder under the web server home folder.
8. Move webAFNC.jar and webEISNC.jar to the sasweb\tools\SASNetCopy folder under the web server home folder.

To update your SAS server:

1. In the sasupdates folder, there is a subfolder for V6, V8.0, and V8.1.
2. Copy the appropriate appdev.cpo file from one of these folders to your SAS server machine.
3. Start SAS on the server.
4. Enter and submit the following code:

filename updates 'path-to-appdev.cpo-file';
proc cimport c=sashelp.rsclmod infile=updates force;run;

To update your JSP engine:

1. Copy the webAFServerPages.jar to the machine where your JSP engine is running.
2. If you haven't already done so, add this jar file to the classpath of the JSP engine.

NLS Issues with this patch

If you want to run ADS 1.2 in French, German, Hungarian, Italian, Polish, or Spanish, you need to follow these instructions. This patch contains two fixes for NLS issues.

The first fix updates translated version of the afmsg and eismsg message data sets on the SAS server. In the sasupdates folder there are a set of cport files. For version 6 of SAS (v6ln.cpo), for version 8.0 of SAS (v80ln.cpo), and for version 8.1 of SAS (v81ln.cpo), where ln stands for language code (see the language code table listed below for the ln values).  The cpo files contain the server side datasets as well as the Statdesc.scl entry in case of version 6. Without applying this fix, user will not be able to utilize the functionality of the Computed Values and Show Detail Data menu options within ADS 1.2 applets.

Language	Language Code (ln)
French	fr
German	de
Hungarian	hu
Italian	it
Polish	pl
Spanish	es

To apply the French, German, Hungarian, Italian, Polish, or Spanish updates:

1. In the sasupdates folder there is a subfolder for V6, V8.0, & V8.1.
2. Copy the appropriate v*ln.cpo file from one of these folders to the machine which is your SAS server. Be sure to carefully choose the correct version of the SAS cpo files that corresponds with the version of your SAS server. The cpo files are stored in subfolders by SAS version in the sasupdates folder. If you attempt to apply the wrong SAS version of the cpo file, the results will be unpredictable.
3. Start SAS on the server.
4. Enter and submit the following code:

      For V81 SAS Servers:

libname appdev 'path-to-the: : \sasupdates\v81';
proc cimport lib=appdev infile='path-to-the: : \sasupdates\v81ln.cpo'; run;
/* Where ln stands for language code. See the table above for ln values. For example, v81de.cpo is the Version 8.1 German cpo file.*/

proc datasets library=appdev;
   copy out=sashelp;
   select eismsg afmsg;
   run;

       For V80 SAS Servers:

libname appdev 'path-to-the: : \sasupdates\v80';
proc cimport lib=appdev infile='path-to-the: : \sasupdates\v80ln.cpo'; run;
/* Where ln stands for language code. See the table above for ln values. For example, v80de.cpo is the Version 8.0 German cpo file.*/

proc datasets library=appdev;
   copy out=sashelp;
   select eismsg afmsg;
   run;