degreeworks installation guide - my.bridgew.edu · degreeworks. installation guide. december 2010 ....

DegreeWorksInstallation Guide

December 2010 Software Patch DW4.0.8

What can we help you achieve? HIGHER EDUCATION

Baseline Release DW4.0.0September 30, 2008

______________________________________________________________________________ Trademark, Publishing Statement and Copyright Notice

SunGard or its subsidiaries in the U.S. and other countries is the owner of numerous marks, including “SunGard,” the SunGard logo, “Banner,” “PowerCAMPUS,” “Advance,” “Luminis,” “DegreeWorks,” “fsaATLAS,” “Course Signals,” and “Open Digital Campus.” Other names and marks used in this material are owned by third parties.

© 2010 SunGard. All rights reserved. Contains confidential and proprietary information of SunGard and its subsidiaries. Use of these materials is limited to SunGard Higher Education licensees, and is subject to the terms and conditions of one or more written license agreements between SunGard Higher Education and the licensee in question. This PDF is certified for use with Adobe Reader, version 6.x and higher. Some elements of this PDF may not render properly when viewed using earlier versions of the Acrobat Reader or with other PDF viewing applications.

In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional services. SunGard Higher Education makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization’s own choosing.

Prepared by: SunGard Higher Education

4 Country View Road Malvern, Pennsylvania 19355 United States of America

Customer Support Center Website

http://connect.sungardhe.com

Documentation Feedback

http://education.sungardhe.com/survey/documentation.html

Distribution Services E-mail Address

[email protected]

Revision History Log

Publication Date Summary

December 2010 New version that supports DegreeWorks 4.0.8.

http://connect.sungardhe.com/

http://education.sungardhe.com/survey/documentation.html

December 2010 DegreeWorks DW4.0.8 3 Installation Guide

Document Change Log Version Date Change Description DW4.0.8 December 17, 2010 Update version for DW4.0.8 changes DW4.0.7 August 27, 2010 Update version for DW4.0.7 changes DW4.0.6 April 15, 2010 Update version for DW4.0.6 changes DW4.0.5 January 22, 2010 Update version for DW4.0.5 changes DW4.0.4 October 16, 2009 Added DW4.0.1 release to Step 3 in the Application Server Patch Install instructions DW4.0.4 September 14, 2009 Update version for DW4.0.4 changes DW4.0.3 May 1, 2009 Update version for DW4.0.3 changes DW4.0.2 March 31, 2009 Update version for DW4.0.2 changes DW4.0.1 December 19, 2008 Update version for DW4.0.1 changes DW4.0.0 October 22, 2008 Application Server Installation - removed references to bt_file_setup, and made

other minor clarifications as a result of user feedback. Web Server Installation - made note of the fact that the zip file was created on a Windows platform, and made installation corrections for clients using UNIX.

DW4.0.0 September 30, 2008 Update version for DW4.0.0 changes Added Configuration Considerations section Added Oracle Discoverer Reports

7.7.2.D02.P02 March 2008 Added Instructions to install database link to Banner 7.7.2.D02 December 14, 2007 Update version for D02 changes 7.7.2.D01A August 17, 2007 Update version for Unix. 7.7.2.D01 July 27, 2007 Initial version for Red Hat Linux.


Table of Contents

Document Change Log ....................................................................................................... 3 Table of Contents ................................................................................................................ 4 Overview ............................................................................................................................... 5

DW4.0.8 Download - Customer Support Center ........................................................................................... 5

Application Server Patch Install ......................................................................................... 7 Instructions ...................................................................................................................................................... 7

Before Beginning ............................................................................................................................................................ 7 Installation Steps ............................................................................................................................................................ 8

Flex Tools Installation – Optional ..................................................................................... 14 Instructions .................................................................................................................................................... 14

1. Introduction ............................................................................................................................................................... 14 2. Choose War File Destination .................................................................................................................................... 15 3. Select Desired WAR Files ......................................................................................................................................... 16 4. JDBC Database Properties ....................................................................................................................................... 17 5. DegreeWorks URL .................................................................................................................................................... 18 6. DegreeWorks Application Home Directory................................................................................................................ 19 7. Flex Endpoint URL for WebTreQer ........................................................................................................................... 20 8. Configuration Summary ............................................................................................................................................ 21 9. Ready for configuration ............................................................................................................................................. 22

PC software ........................................................................................................................ 23 Upgrading the DegreeWorks PC software .................................................................................................. 23

1. Download the package ............................................................................................................................................. 23 2. Start the Installer ....................................................................................................................................................... 23 3. Program launch ........................................................................................................................................................ 24

Configuration Considerations .......................................................................................... 25 MEP Configuration Changes ........................................................................................................................ 26 UCX Review and Update ............................................................................................................................... 31 SHPCFG Review and Configuration ............................................................................................................ 34 Web Changes ................................................................................................................................................. 34 Bridge changes for RAD clients .................................................................................................................. 35 Native Integrated Interface for Banner ........................................................................................................ 36 Native Integrated Interface for Oracle PeopleSoft ..................................................................................... 44 Luminis ........................................................................................................................................................... 45 Workflow ........................................................................................................................................................ 45 3rd party reporting ......................................................................................................................................... 45 Other Server Changes .................................................................................................................................. 46

Sample Reports ................................................................................................................. 49 Sample Crystal Reports ................................................................................................................................ 49 Sample Oracle Discoverer Reports ............................................................................................................. 49


Overview The DegreeWorks DW4.0.8 patch software release supports an upgrade path for existing UNIX and Linux DW4.0.0, DW4.0.1, DW4.0.2, DW4.0.3, DW4.0.4, DW4.0.5, DW4.0.6, or DW4.0.7 DegreeWorks clients running Oracle. DW4.0.8 is cumulative, including changes delivered with DW4.0.1 through DW4.0.7. Each site must review the following document for critical information before processing the installation instructions: DegreeWorks 4.0.8 Release Guide (filename: dw40008rg.pdf). The DegreeWorks DW4.0.8 software is available through SunGard Higher Education’s Customer Support Center.

DW4.0.8 Download - Customer Support Center Log into the Customer Support Center. Navigate to Documentation and Download Center:

Software Downloads DegreeWorks - DegreeWorks

DW4.0.0 DW4.0.8

Software installation files for use with DW4.0.8:

dwupd-dw4.0.8.tar.gz Host installation update file DegreeWorks_406_Setup.exe PC installer update package DegreeWorks_408_AppCfg.exe Flex Application Configuration program - Optional SampleRpts_DW404.zip Sample Reports – Optional

Product Documentation files for use with DW4.0.8: Previous pdf filename New pdf filename Release version DGW_Technical_Guide dw40008tg.pdf DW4.0.8 DGW_Technical_Guide_Advanced_Reporting_CPA_SEP dw40007artg.pdf DW4.0.7 DGW_Technical_Guide_Banner_Considerations dw40008bnrtg.pdf DW4.0.8 DGW_Technical_Guide_BIF (Document renamed as the ‘DegreeWorks Bridge Interface Format Handbook’) dw40008biftechhb.pdf DW4.0.8 DGW_Technical_Guide_Banner_Data_Mapping_for_BIF dw40008biftg.pdf DW4.0.8 DGW_Technical_Guide_OPS_Considerations dw40008opstg.pdf DW4.0.8 DGW_Technical_Guide_OPS_Data_Mapping_for_BIF dw40008opsbiftg.pdf DW4.0.8 DGW_Technical_Guide_Transit (same) DW4.0.0 DGW_Technical_Guide_UCX dw40008ucxtg.pdf DW4.0.8 DGW_User_Guide_Scribe dw40008scrbu.pdf DW4.0.8 DGW_User_Guide_SHPEntry dw40008shpu.pdf DW4.0.8 DGW_User_Guide_SureCode_PC-based (same) DW4.0.0 DGW_User_Guide_SureCode_Web-based (same) DW4.0.4


DGW_User_Guide_Transit dw40008trnstu.pdf DW4.0.8 DGW_User_Guide_TreQ (same) DW4.0.4 DGW_User_Guide_TreQadmin dw40008tqu.pdf DW4.0.8 DGW_User_Guide_Web dw40008webu.pdf DW4.0.8


1 Application Server Patch Install

Application Server Patch Install

Instructions These instructions are provided to address the installation on all supported platforms. You must be on the DW4.0.0, DW4.0.1, DW4.0.2, DW4.0.3, DW4.0.4, DW4.0.5, DW4.0.6, or DW4.0.7 version of the software to install this update. Before Beginning Before beginning the update, be sure to check the following items:

• As of the DW4.0.6 update, DegreeWorks requires the Java 1.6 JDK, not the Java JRE required in previous releases. The most basic JDK is sufficient. There is no need for the additional features often provided with the JDK.

• Make sure you know the location of and have write access to the DegreeWorks web server files (where IRISLink.cgi resides)

• The DegreeWorks DW4.0.8 patch introduces running DegreeWorks in 64 bit mode. See special instructions in the Other Server Changes section in the Configuration Considerations section in this document. If you are interested in running DegreeWorks in 64 bit mode please review this topic before you begin this update as student audits generated in 32 bit mode will not be accessible when DegreeWorks is compiled in 64 bit mode.

• DegreeWorks MEP clients who extract data from a Banner MEP-VPDI database must configure the appropriate Banner VPDI code in each MEP dwenv.config file.

• It is strongly recommended that you create a full backup of both your DegreeWorks database and file system prior to beginning this update.

• If you are on a Banner release of 8.4.1 or later, you must grant your DegreeWorks user in your Banner database the USR_DEGREE_WORKS role, or your installation will fail.

grant USR_DEGREE_WORKS to degreeworks_user;

• The third party application OpenSSL must be installed on the server prior to installation. This is often bundled with the operating system. You can check to see if it is on your system by searching for the library and include file:

find / -name libcrypto.a –print find / -name evp.h –print

If these commands fail to report any files on your system, you must install them before proceeding. Contact your OS vendor for the appropriate package, or go to www.openssl.org to download the source code and build it on your machine.


The OpenSSL C include files must be in the openssl subdirectory under one of the standard system include directories (e.g. /usr/local/include). If it was not installed there, you should create a symbolic link to the installed directory from /usr/local/include. For example:

ln -s /opt/your/include/openssl /usr/local/include/openssl Replace "/opt/your/include" with the directory containing the openssl directory. Alternatively, you can specify the include directory in your dwenv.config file by modifying or adding the following lines:

# gsCfgAdditionalIncludes - additional includes needed for openssl gsCfgAdditionalIncludes='-I/opt/your/include' export gsCfgAdditionalIncludes

If the gsCfgAdditionalIncludes variable is already being set to a value, then simply append "-I/opt/your/include" to the end of the string separated from the existing string by a space. Similarly, the libcrypto.a file from the OpenSSL product should be placed in one of the standard library locations: /usr/lib or /usr/local/lib. If it was not installed there, you should create a symbolic link to the installed directory from /usr/local/lib. For example

ln -s /opt/your/lib/libcrypto.a /usr/local/lib/libcrypto.a Replace "/opt/your/lib/libcrypto.a" with the path to your libcrypto.a file. Alternatively, you can specify the location of the library in the dwenv.config file by modifying or adding the following lines:

# POST_OS_LIBS - to be appended to the LIBS variable # Default is null string export POST_OS_LIBS='-L/opt/your/lib -lcrypto'

If the POST_OS_LIBS variable is already being set to a value, then simply append "-L/opt/your/lib -lcrypto" to the end of the string separated from the existing string by a space.

• MEP sites only: Follow the MEP Configuration Changes instructions under the Configuration

Considerations section in this document before beginning the DegreeWorks update. Failure to configure share.xml will cause new database tables to be unique and NOT shared between your MEP environments. Do not proceed with the update until you have completed the steps outlined in MEP Configuration Changes!

Installation Steps 1. On your host machine, sign on as the DegreeWorks administrator for the account to be updated (for

example, dwadmin). 2. Check that the release variable is properly set:

echo $DWRELEASE

This should display your current release level – e.g.

DW4.0.0


or DW4.0.1 Etc.

If it is not correct, you must modify the dwrelease file in the DegreeWorks base directory.

3. Clients upgrading from DW4.0.0 or DW4.01 only: The JAVA_HOME variable must be modified. Edit the dwenv.config file and replace this:

JAVA_HOME=/usr/java/default export JAVA_HOME

with this:

#The location where Java JRE is installed export gsCfgJavaHome=/usr/java/default

replacing "/usr/java/default" with the directory where bin/java resides. In addition, the DWJAVA_LIB variable must be modified by clients who have NOT placed the java libraries (fop-1.0, DtlUtils-1.0 and JSAP-2.1) in the recommended directory /usr/local/dw/java. Edit the dwenv.config file and add the following immediately after the setting for gsCfgJavaHome:

#The location where fop-1.0, DdlUtils-1.0 and JSAP-2.1 are installed export gsCfgJavaLib=/usr/local/dw/java

replacing "/usr/local/dw/java" with the directory where your java libraries reside.

4. If your DegreeWorks database resides on your DegreeWorks server, and it is not using the default port of

1521, then add the following to dwenv.config after the ORACLE_SID setting in the variable gsCfgDBName. Substitute the actual port number for “9999”:

# DB_PORT_NBR - If your DW database resides on the DW server AND it does not # use default port 1521, set DB_PORT_NBR to identify the port you are using export DB_PORT_NBR=9999

5. Stop the DegreeWorks servers:

dapstop webstop

MEP sites only: Stop the DegreeWorks servers in each MEP environment.

6. Make sure that an empty updates directory exists under $DGWHOME:

cd $DGWHOME rm –rf updates mkdir updates chmod 700 updates

7. Download the dwupd-dw4.0.8.tar.gz file into the $DGWHOME/updates directory and decompress:

cd updates gzip -cd dwupd-dw4.0.8.tar.gz | tar xf -


8. Clients upgrading from DW4.0.0, DW4.0.1, DW4.0.2 or DW4.0.3: Check your database for potential database consistency problems prior to running the update. The DW4.0.4 update adds new constraints to the database, and this might cause problems during the update if your database contains records with no parent table entries. You should run the script check_orphaned_data to determine if you have any records with this problem. This script is located in the update directory. If it reports any issues, you must clean these up prior to running the update. The script produces one file for each database table that has problems. The files contain the ID numbers for problematic records. You can use the delete_orphaned_data script to delete all bad records.

cd updates ./check_orphaned_data ./delete_orphaned_data

9. All clients: Check your database for potential duplicate RAD_ETS_MST records by running the following

query in your DegreeWorks database. Use the “db” command to run sqlplus; MEP clients must use the schemaAll user or the global schema owner, because the RAD_ETS_MST is typically a shared table.

select rad_ets_code, count(*) from rad_ets_mst group by rad_ets_code having count(*) > 1;

If the results of the query is “no rows selected” then proceed with the update. If you receive one or more duplicates, you will have to remove the duplicates before proceeding. While still in sqlplus, you may wish to truncate the RAD_ETS_MST then rebridge this table after completing the installation. To truncate the table, issue this command from the sqlplus prompt:

truncate table RAD_ETS_MST; The truncate command will remove all rows from the RAD_ETS_MST but will leave the table and its associated objects intact. At the end of these installation instructions is a reminder to re-bridge this table.

10. Change the permissions on the dwdeploy script:

chmod +x dwdeploy 11. PeopleSoft clients only. Before beginning the update, make sure the following is in your dwenv.config file

in the DATABASE Variables section. New clients will have to add the following:

# DB_LOGIN_OPS - The PeopleSoft login id and password, in the form # "user/pass@service". # No default. Set only if accessing PeopleSoft DB_LOGIN_OPS=user/pass@service export DB_LOGIN_OPS

Change “user/pass@service” to a valid login to your PeopleSoft database. You must establish a user in your PeopleSoft database to be used with the DegreeWorks extract. This user must have select access to a list of student-oriented tables which are listed in the OPS Considerations documentation section entitled Required Access to PeopleSoft. While still in dwenv.config, locate the section entitled BUILD Environment Variables, and modify the line for POST_OS_LIBS:

export POST_OS_LIBS="-L$gsCfgJavaHome/jre/lib/<type>/server -ljvm"

under OTHER Custom Variables, locate and modify the line for gsCfgPostShlibPath:

export gsCfgPostShlibPath="$gsCfgJavaHome/jre/lib/<type>/client"


Note that the gsCfgJavaHome variable should be defined earlier in the dwenv.config file. The “<type>” part of these paths will vary depending due to the type of machine you have. Make sure that these directories exist and contain the libjvm.so file. These lines will already exist in the dwenv.config file, but may not have appropriate values or may be empty. Make sure that they are not commented out (preceded with a ‘#’ sign). You must login in again before starting the update in order for these changes to take effect.

12. If you are planning on running DegreeWorks in 64-bit mode, issue the following command to verify DW64BIT_ENABLED is set:

echo $DW64BIT_ENABLED

If the response is not 1, then see instructions in the Other Server Changes section in the Configuration Considerations section in this document before proceeding with the update.

13. Execute the dwdeploy script and go through the steps one-by-one:

./dwdeploy This should begin by displaying a message that indicates that a previous DW4.0 version of DegreeWorks has been detected, and that an update will be applied:

Version DW4.0.# of DegreeWorks has been detected in this account. It will be updated to version DW4.0.8 by installing patches: 8…

If you see a significantly different message than this, do not proceed. You should call the ActionLine for additional assistance. Banner clients: the dwdeploy script contains a new step “Verify Environment” which will verify that the DegreeWorks user established in your Banner database has been granted access to the required list of Banner tables, functions and packages. If you see warnings you may proceed with the update. If you see errors, you will need to grant select or execute access to the table or function listed. See the section Required Access to Banner Tables in the Banner Considerations Technical Guide for a complete list of access required by DegreeWorks. MEP sites only: STOP when the “Upgrade Specific Processing” step has been completed. The next two steps will have to be run manually for each of your different entities. You may exit the dwdeploy script. a) MEP sites only: DegreeWorks Batch Maintenance

Clients upgrading from DW4.0.0 or DW4.0.1 ONLY: Logon as each MEP entity and do the following:

cd $DGWHOME/updates/DW4.0.2/release/Upgrade/All/post/scripts degrees2goals (may take a while to run – creates all GOAL records)

Clients upgrading from DW4.0.0 or DW4.0.1 ONLY: Logon as each MEP entity and do the following:

cd $DGWHOME dapucx2shpgroup dapucx2shpservice ucx12job


b) MEP sites only: Launch Daemon Processes

All MEP upgrading clients: Logon as each MEP entity and do the following to copy the $DGWHOME/updates/dw.release file to each MEP entity filesystem. The following is an example for the NORTH entity, where the admnorth is the base directory:

cd admnorth cp $DGWHOME/updates/dw.release dw.release

Logon as each MEP entity and do the following:

echo $DWRELEASE DW4.0.8 If this is incorrect redo the copy of dw.release ucx12job dapstart webstart

14. Banner Clients: the bannerextract.config file on your DegreeWorks server MUST be updated to include

changes in queries run in the Banner database. Make the changes indicated in the section Native Integrated Interface for Banner under the Configuration Considerations section in this document. The bannerextract script will not execute without these changes! PeopleSoft Clients: various properties files on your DegreeWorks server MUST be updated to include new options or changes in queries run in the PeopleSoft database. Make the changes indicated in the section Native Integrated Interface for PeopleSoft under the Configuration Considerations section in this document. The opsextract script will not execute without these changes!

15. All clients: If you had truncated the RAD_ETS_MST table in step 9, you must re-bridge this table from your student system.

Banner clients: at the server prompt issue the command bannerextract ets PeopleSoft clients: at the server prompt issue the command opsextract ets RAD clients: stage the R701ETSM data files for import into DegreeWorks and run RAD11. See the Bridge Program section of the DegreeWorks BIF (Bridge Interface Format) technical documentation for details.

16. This patch delivered some files that MUST be moved to the DegreeWorks home of your web server. These files are located in the updates/webroot directory. Further, make sure you integrate any local changes that may have been made to these files. Make sure you have a copy of the original files from your web server before copying the files. NOTE: IRISLink.cgi has been replaced in the DW4.0.6 update. Site specific details were removed to separate files. If you are upgrading from DW4.0.6 then you should make a backup copy of your old IRISLink.cgi so that you may refer to it when configuring your new setup. See the related note below in the Other Server Changes section in the Configuration Considerations section in this document.

MEP SITES ONLY: The web server files delivered with this patch MUST be copied to the DegreeWorks webroot home of each of your different entities (e.g., “webnorth”, “websouth”, “webwest”, etc.). These files are located in the updates/webroot directory. Further, make sure you integrate any local changes that may have been made to these files. Make sure you have a copy of the original files from your web server before copying the files.


17. Review all of the sections in the Configuration Considerations section of this document. Some changes require you to review and configure UCX or other client-specific items. Please review the considerations and configure as appropriate for your site.

18. If you are a new PeopleSoft client that is installing Degreeworks for the first time, you should now

proceed with the OPS Considerations Technical Guide to configure DegreeWorks to successfully extract student and related data from your PeopleSoft database. In addition, you will need to copy the following files from the updates directory to the common directory. Note that existing PeopleSoft clients should NOT perform this step, as you should have already configured these files for your installation.

cp –p $DGWHOME/updates/release/install/admin/common/* $ADMIN_HOME/common/.

After copying the files, cd to the common directory and run shpparse on the new SHPCFG file, by issuing the shpparse command:

cd common shpparse

19. If any of the software delivered with this patch updates software that you have tailored, such as xsl, you

must re-integrate your changes. Look in the $LOCAL_HOME directory and check whether or not any of the files there were delivered on the patch. You can see a list of delivered files in the $DGWHOME/updates/dwdeploy.manifest file or in the Patch Contents section of the DW4.0.8 Release Guide. You must merge the local and new files and place the result in the local directory. Make sure to keep archive copies of your local files.

20. Download the updated documentation from the Customer Support Center. Navigate to the DegreeWorks

area of the Documentation download area. Review the Technical and User Guides for any patch documentation. Updated documentation will contain the patch level appended to the file name.

21. (Optional) Download the Flex configurator package for DW4.0.8. Follow instructions in the Flex Tools

Installation section of this document to configure and produce war files to be deployed to your application server.

22. Clients upgrading from DW4.0.0, DW4.0.1, DW4.0.2, DW4.0.3, DW4.0.4 or DW4.0.5: Download the

DW4.0.6 PC installer package. Follow instructions in the PC Software section of this document to upgrade each machine that has the DegreeWorks PC applications loaded.

2 Flex Tools Installation

Flex Tools Installation – Optional One new application is being delivered in this release that use technology new to DegreeWorks: TreQadmin. It, together with the SureCode and WebTreQer applications from previous releases, are Java based with an Adobe Flex interface. The installation of these applications is optional. These applications have their own configurator. The configurator is run on a Windows machine (Vista, XP or Windows 2000) and produces a Web Archive File (war file) for each of the applications. The applications are not installed when the configurator is run. The war files must be manually loaded into your application server. The configurator is named DegreeWorks_408_AppCfg.exe, and is found on the Customer Support Center.

Instructions 1. Introduction


Run the configurator on your Windows machine. After the initial loading screen, you will see the introductory screen. The left hand panel of this screen contains a table of contents for the configurator, and indicates your progress through the installation. Click Next to continue with the installation. 2. Choose War File Destination

This screen allows you to choose where the configurator will deposit the resulting war files. You can consider this a temporary location, since you must move these files to your application server. Enter the fully qualified directory path in the provided box, or click Choose to pick from a standard file open dialog. Once you have specified the directory, click Next.


3. Select Desired WAR Files

This screen allows you to choose which application you wish to install. You may ignore the Install Set box. It only serves to default the selections. Clicking on the name of one of the applications bring up a description of that item in the lower pane. Click on the box to the left of the application to select or deselect that item. The Administrative Shell is a container application that is used to access the SureCode, TreQadmin, and SHPEntry applications, which are no longer loaded as separate WAR files. SureCode maintains the UCX validation tables. SHPEntry maintains user authorizations. TreQadmin maintains articulation data for a separately licensed Transfer Articulation Module (TreQ). WebTreQer allows inquiring students to enter in classes they have taken at other institutions and receive an articulation of the classes to your equivalents as well as an academic audit. It requires a license to DegreeWorks TreQ product. Web Services provides interfaces for non-DegreeWorks software to access DegreeWorks functionality. Once you have made the selections, click Next to continue.


4. JDBC Database Properties

The new applications make use of JDBC to connect to the database. This screen configures these parameters. The JDBC URL is the standard format for a JDBC connection string, and an example is given in the help box in the upper portion. You may copy that line as a template. You must, at the very least, change “dbhost.mycollege.edu” to the name of the host that is serving the database, and “dgwdb” with the Oracle SID of that database. Change the listener port number (1521) to a different port, if required. Enter the database user name and password for the DegreeWorks user. This can be found in your host DegreeWorks environment by looking that DB_LOGIN variable. Click Next.


5. DegreeWorks URL

Some of the included software must be able to connect to the current DegreeWorks software. It does so by connecting the web services daemon running on the DegreeWorks host. The parameters on this page tell the application how to find those servers. The values for these parameters may be found in your CgiSettings.pm file on your web host. Click Next when you have completed this page.



6. DegreeWorks Application Home Directory (This screen is only displayed if you chose to install Web Services)

This screen records the location of the DegreeWorks software on your application server. This is where the host based software runs and where the web daemons are started (webstart). It should be an absolute UNIX path designation (e.g. /u01/degreeworks/prod/app). You can get this from your host while signed on to the DegreeWorks account by examining the DGWHOME environment variable.

echo $DGWHOME Click Next when you have completed this page.

7. Flex Endpoint URL for WebTreQer (This screen is only displayed if you chose to install WebTreQer)

WebTreQer make use of the Adobe Flex technology, which runs in the client browser. It must connect back to the application server to transfer data back and forth. This screen configures those parameters for WebTreQer. The Host Application Server is the machine name where the application server resides. It must be on the same machine as the regular DegreeWorks software. The Port is the port number on which that application server listens. This is configured in the application server. The Context Root is the location underneath the host server where the application is to reside. It will also be required when you install the war file into the tomcat server. Also, the first part must match the context of the DegreeWorks software. Do not put a slash “/” in front of the Context Root. For example, if your current DegreeWorks software is accessed with the URL http://www.mycollege.edu/DegreeWorks, then the Host Application Server would be www.mycollege.edu, and the Context Root might be DegreeWorks/WebTreQer. Click Next when you have completed this page.


8. Configuration Summary

This screen allows you to review your selections. If you would like to change one or more of them, click Previous to go back and edit the page. Otherwise, select Next to proceed.


9. Ready for configuration

To begin the configuration and creation of the WAR files, choose Install. The WAR files will be created in the location that you choose earlier. You should install these WAR files on your application server.



3 PC Software

PC software

Upgrading the DegreeWorks PC software No changes have been made to the PC application for this release. These installation instructions are for the DW4.0.6 release of the PC software, against Windows XP, Windows 2000 or Windows Vista operating systems. You must be logged into the PC with administrator rights to process the installation of the PC products, along with the Modify, Repair or Remove functions of the installer. Please note, the DegreeWorks_406_Setup.exe also contains new installation capabilities for the DW4.0.6 level PC applications. For new installation instructions please refer to the DW4.0.0 Installation Guide. 1. Download the package Download the DW4.0.6 PC Product package from the SunGard Higher Education support website. 2. Start the Installer Move the DegreeWorks_406_Setup.exe installation file to the workstation and double-click the executable to start the installer.

3. Program launch Since you are upgrading from a DW4.0.0, DW4.0.1, DW4.0.2 or DW4.0.4 PC installation to DW4.0.6, you will receive the upgrade screen followed by an Update Complete screen. No other installer steps are required.



4 Configuration Considerations

Configuration Considerations The Release Guide outlines the overall Configuration Considerations for DW4.0.8. This document is a supplement to the Release Guide, giving additional specific actions to take upon installation of the DW4.0.8 update. Customers moving from DW4.0.0 to DW4.0.8 must process the DW4.0.1, DW4.0.2, DW4.0.3, DW4.0.4, DW4.0.5, DW4.0.6, DW4.0.7 and DW4.0.8 configuration settings. Customers moving from DW4.0.1 to DW4.0.8 must process the DW4.0.2, DW4.0.3, DW4.0.4, DW4.0.5, DW4.0.6, DW4.0.7 and DW4.0.8 configuration settings. Customers moving from DW4.0.2 to DW4.0.8 must process the DW4.0.3, DW4.0.4, DW4.0.5, DW4.0.6, DW4.0.7 and DW4.0.8 configuration settings. Customers moving from DW4.0.3 to DW4.0.8 must process the DW4.0.4, DW4.0.5, DW4.0.6, DW4.0.7 and DW4.0.8 configuration settings. Customers moving from DW4.0.4 to DW4.0.8 must process the DW4.0.5, DW4.0.6, DW4.0.7 and DW4.0.8 configuration settings. Customers moving from DW4.0.5 to DW4.0.8 must process the DW4.0.6, DW4.0.7 and DW4.0.8 configuration settings. Customers moving from DW4.0.6 to DW4.0.8 must process the DW4.0.7 and DW4.0.8 configuration settings. Customers moving from DW4.0.7 to DW4.0.8 must only process the DW4.0.8 configuration settings. After any SHPCFG changes clients need to parse the file and bounce the servers for changes to take effect:

shpparse daprestart webrestart

After any UCX changes clients will need to bounce the servers for changes to take effect:

daprestart webrestart

MEP Configuration Changes All MEP sites must perform the following configuration steps prior to executing the dwdeploy script. Failure to configure share.xml will cause new database tables to be unique and NOT shared between your MEP environments. The share.xml file resides in the $DGWHOME/schema directory on your DegreeWorks server.

1. Check that the $DWRELEASE variable is set in each of your MEP environments – for MEP sites this

variable may not be set correctly for the DW4.0.4 installation.

The dw.release file is normally found in the DegreeWorks base directory (e.g., dw40, dwadmin, etc.). However, for MEP sites each unique College has its own admin or $ADMIN_HOME directory for that College (e.g., North College may have an ‘admnorth’ directory containing its North dwenv.config file with its particular configurations set; a South College may have an ‘admsouth’ directory containing its South dwenv.config file, etc.). The dw.release file from the DegreeWorks base directory must be copied to each of the individual MEP $ADMIN_HOME directories (e.g., ‘admnorth’, ‘admsouth’, etc.).

2. MEP SITES upgrading from DW4.0.0 or DW4.0.1 ONLY: Prior to executing the dwdeploy script MEP

sites must perform these additional steps.

a. Your sharing configuration file must be called share.xml in the $DGWHOME/schema directory. If you currently are using a different name, then rename or copy your file to share.xml. b. The DATA_BASES table MUST be added to your share.xml file. This table should be owned by the global schema, to be shared by all other users. If your default DefaultSharing value is “Share”, you do not need to add this table to the document.

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <EntityId>NorthCollege</EntityId> <EntityId>SouthCollege</EntityId> <EntityId>EastCollege</EntityId> <EntityId>WestCollege</EntityId> <DatabaseTable>DATA_BASES</DatabaseTable> <DatabaseTable>RAD_STUDENT_MST</DatabaseTable> <DatabaseTable>RAD_APPLICNT_DTL</DatabaseTable>

c. Four new database tables are being added with DW4.0.2:

rad_goal_dtl rad_goal_hsh rad_goaldata_dtl rad_goaldata_hsh

These tables are replacing the rad_degree_dtl and rad_school_dtl. These tables must be set up the same way as rad_degree_dtl in share.xml. If your rad_degree_dtl is Unique or Not Shared then it should not exist in share.xml and there is no need to add the GOAL tables to share.xml. However if your rad_degree_dtl data is shared among your MEP environments, it will exist in share.xml and you must then add the new GOAL tables as follows:

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>RAD_DEGREE_DTL</DatabaseTable> <DatabaseTable>RAD_GOAL_DTL</DatabaseTable> <DatabaseTable>RAD_GOAL_HSH</DatabaseTable>

<DatabaseTable>RAD_GOALDATA_DTL</DatabaseTable> <DatabaseTable>RAD_GOALDATA_HSH</DatabaseTable>

d. For MEP sites the dwenv.config file must be located in the $ADMIN_HOME directory for each College (e.g., ‘admnorth’, ‘admsouth’, ‘admwest’, etc.) so that the configurations can be unique for each College. However, a special “ALL” schema entity dwenv.config file must also exist for this installation. A dwenv.config file must be copied from one of the individual entities to the base directory for DegreeWorks (e.g., dw40, dwadmin, etc.). Then the DB_LOGIN must be set to the shared “ALL” schema user (e.g., schemaAll noted above in Step b.) and the dwenv.config file saved.

# DB_LOGIN - The login id and password, in the form "user/pass@machine" # Defaults to … DB_LOGIN=schemaAll/password export DB_LOGIN

e. Then this dwenv.config file must be invoked for the logon user that is running the DegreeWorks installation – note that there is a “DOT” followed by a blank, followed by “dwenv”, followed by a blank and then the base directory for your DegreeWorks environment (the example below is from a QA environment). Change the following “/dw/qa/dw40/dwenv.config” reference to be appropriate for your site:

. dwenv /dw/qa/dw40/dwenv.config Then type the following command to make sure your installation environment is referencing the appropriate database login.

$ echo $DB_LOGIN schemaAll/password

3. MEP SITES upgrading from DW4.0.0, DW.4.0.1 or DW4.0.2 ONLY: Prior to executing the dwdeploy

script MEP sites must perform these additional steps. a. UCX-STU100 is a table that is part of the custom search enhancement (see the Technical Guide -

Web Interface section for more information). If customers want this table to be shared among your MEP environments, add the line below in red to the following section of share.xml:

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>UCX_STU024</DatabaseTable>  <DatabaseTable>UCX_STU035</DatabaseTable>  <DatabaseTable>UCX_STU100</DatabaseTable>  <DatabaseTable>UCX_STU305</DatabaseTable> 

If customers do NOT want to share this table, and have it be unique for each MEP environment, then you do not need to modify share.xml.

b. Remove the UCX_SYS976 entry from the share.xml file, as it is now obsolete.

<DatabaseTable>UCX_SYS976</DatabaseTable>

c. Eight new UCX database tables have been added for CourseLink (see the Technical Guide – CourseLink section for more information.) Add them to your share.xml file if you want them to be shared and not unique among your MEP environments. The new tables are UCX_RPT050,

UCX_RPT051, UCX_RPT052, UCX_RPT053, UCX_RPT054, UCX_RPT055, UCX_RPT056, and UCX_RPT057. If you do NOT want to share these tables, and have them be unique in each MEP environment, then you do not need to modify share.xml.  <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>UCX_RPT050</DatabaseTable> <DatabaseTable>UCX_RPT051</DatabaseTable> <DatabaseTable>UCX_RPT052</DatabaseTable> <DatabaseTable>UCX_RPT053</DatabaseTable> <DatabaseTable>UCX_RPT054</DatabaseTable> <DatabaseTable>UCX_RPT055</DatabaseTable> <DatabaseTable>UCX_RPT056</DatabaseTable> <DatabaseTable>UCX_RPT057</DatabaseTable>

4. MEP SITES upgrading from DW4.0.0 through DW4.0.5 ONLY: Prior to executing the dwdeploy script

MEP sites must perform this additional step. A new table DAP_APPDATA_DTL was added with DW4.0.6. This new table should be shared in the same way as your DAP_APPLICNT_MST table. If the DAP_APPLICNT_MST table is not in share.xml, then you do not need to make any changes. Otherwise, put the DAP_APPDATA_DTL in the same section as your DAP_APPLICNT_MST table.

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>DAP_APPLICNT_MST</DatabaseTable> <DatabaseTable>DAP_APPDATA_DTL</DatabaseTable>

5. MEP SITES upgrading from DW4.0.0 through DW4.0.6 ONLY: Prior to executing the dwdeploy script

MEP sites must perform this additional step. Five new tables were added with DW4.0.7: RAD_SIGNAL_DTL, RAD_SIGNAL_HSH, UCX_AUD031, UCX_AUD032, and UCX_CFG068. These tables will have to be added to your share.xml file if you wish for them to be shared among your MEP environments. The two RAD tables should be shared if you are sharing the RAD_CLASS_DTL. These new tables should be shared in the same way as your RAD_CLASS_DTL table. If the RAD_CLASS_DTL table is not in share.xml, then you do not need to make any changes. Otherwise, put RAD_SIGNAL_DTL and RAD_SIGNAL_HSH in the same section as the RAD_CLASS_DTL table.

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>RAD_CLASS_DTL</DatabaseTable> <DatabaseTable>RAD_CLASS_HSH</DatabaseTable> <DatabaseTable>RAD_SIGNAL_DTL</DatabaseTable> <DatabaseTable>RAD_SIGNAL_HSH</DatabaseTable>

UCX_AUD031 and UCX_AUD032 should be shared if you are sharing UCX_AUD033, but you should review the UCX documentation and make the determination yourself. If the UCX_AUD033 table is not in share.xml, then you do not need to make any changes. Otherwise, put UCX_AUD031 and UCX_AUD032 in the same section as the UCX_AUD033 table.

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>UCX_AUD031</DatabaseTable> <DatabaseTable>UCX_AUD032</DatabaseTable>

<DatabaseTable>UCX_AUD033</DatabaseTable> UCX_CFG068 should be shared if you are sharing UCX_CFG070 but you should review the UCX documentation and make the determination yourself. If the UCX_CFG070 table is not in share.xml, then you do not need to make any changes. Otherwise, put UCX_CFG068 in the same section as the UCX_CFG070 table.

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>UCX_CFG068</DatabaseTable> <DatabaseTable>UCX_CFG070</DatabaseTable>

6. MEP SITES upgrading from DW4.0.0 through DW4.0.7: Prior to executing the dwdeploy script MEP

sites must perform this additional step. New tables were added with DW4.0.8: UCX_SHP078 and ten custom tables UCX_CST001 through UCX_CST010. These tables will have to be added to your share.xml file if you wish for them to be shared among your MEP environments. The UCX_SYS078 should be shared if you are sharing UCX_SHP076 and UCX_SHP077. If these SHP tables are not in share.xml, then you do not need to make any

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>UCX_SHP076</DatabaseTable>  <DatabaseTable>UCX_SHP077</DatabaseTable>  <DatabaseTable>UCX_SHP078</DatabaseTable> 

The ten UCX_CST tables are currently not in use by DegreeWorks software, but are added to the database for clients with custom needs. You may ignore these tables at this time and they will be unique for each of your MEP environments. If you wish to share one or more in the future, share.xml may be modified at that time and sharing can then be established. If you wish to share these tables now you may add them to share.xml as follows:

 <ShareGroup Id="sgAll" Schema="schemaAll" SchemaOutputFile="schemaall.sql"> <DatabaseTable>UCX_CST001</DatabaseTable> <DatabaseTable>UCX_CST002</DatabaseTable> <DatabaseTable>UCX_CST003</DatabaseTable> <DatabaseTable>UCX_CST004</DatabaseTable> <DatabaseTable>UCX_CST005</DatabaseTable> <DatabaseTable>UCX_CST006</DatabaseTable> <DatabaseTable>UCX_CST007</DatabaseTable> <DatabaseTable>UCX_CST008</DatabaseTable> <DatabaseTable>UCX_CST009</DatabaseTable> <DatabaseTable>UCX_CST010</DatabaseTable>

7. MEP SITES upgrading from DW4.0.0 through DW4.0.7: If you are connecting to a Banner database which has been configured as MEP, you will have to complete the following steps. For more details, see the Banner Database Issues section of the Banner Consideration Guide.

a. In Banner, enter the GSAVPDI form and click on the User Assignment tab. Bring up each of your DegreeWorks Oracle users and assign its associated Banner VPDI code.

b. On your DegreeWorks server, modify the dwenv.config file for each of your MEP environments and enter the following after the DB_LOGIN_BANNER variable:


export BANNER_VPDI=MYINST

where MYINST is the Banner Institution VPDI code being associated with this DegreeWorks Oracle user. Do not place spaces between the equal sign and the Institution Code value. The maximum size of the VPDI code is 6 bytes.


UCX Review and Update Review and update the following UCX tables based on your institution’s configuration needs. Refer to the DGW_Technical_Guide_UCX for specific information about each field on each record.

Changed with release

UCX Entry

DW

4.0.

1

DW

4.0.

2

DW

4.0.

3

DW

4.0.

4

DW

4.0.

5

DW

4.0.

6

DW

4.0.

7

DW

4.0.

8

Change

UCX-AUD012 APP X Add the new entry for DW4.0.2. This is a required User Class code for Applicant extract functionality. (1-4SR92L)

UCX-AUD027 X Review and configure the new UCX-AUD027 Degree Filter flags (1-3PD6GX)

UCX-AUD047 X Review and configure the new UCX-AUD047 “Additional Control Flag” (1-AUSWQ5)

UCX-AUD031 X Add the ATLETE-type blocks if using the Athletic Eligibility Audit functionality (1-BF3MTF)

UCX-AUD032 X Review and configure the new UCX-AUD032 Freeze Type table (1-ATO4I3)

UCX-BAN080 X Review and configure records for ACADSTANDING and SPORT if using the Athletic Eligibility Audit functionality (1-BF3MTF)

UCX-CFG020 BANNER X Review and update Transfer Repeat fields. (1-44BH3T)

UCX-CFG020 BANNER X

Review and configure the UCX-CFG020 BANNER "Program as Degree". For most sites this will be set to “N”. (1-4OALJO) Review and configure the UCX-CFG020 BANNER “"InactiveInSCBCRKY" flag. (1-4PLONJ) Review and configure the UCX-CFG020 BANNER “Process Applicants” flag. (1-4SR92L) Review and configure the UCX-CFG020 BANNER “Process Both Goals” flag. (1-4SR92L) Review and configure the UCX-CFG020 BANNER “Load SARADAP Goals” flag. (1-4SR92L) Review and configure the new UCX-CFG020 BANNER "Cross-listed" flag. (1-4U9S8R)

UCX-CFG020 BANNER X Review and configure the UCX-CFG020 BANNER “Transfer Program Attr” flag. (1-55HPE5)

UCX-CFG020 BANNER X

Review and configure the UCX-CFG020 BANNER “Truncate or Round SHRLGPA” flag. (1-5E9OPL) Review and configure the UCX-CFG020 BANNER “InProgressEquiv” flag. (1-6R5BWF) Review and configure the UCX-CFG020 BANNER “Write Transfers to Banner” flag. (1-5RHOYJ)

UCX-CFG020 BANNER X If the UCX-CFG020 BANNER Repeat Policy field is set to "B", customers should review the new “Excluded Repeats Count” and “Averaged Repeats Count” flag, along with the documentation. (1-B19ZWD)

UCX-CFG020 BANNER X Review and configure the UCX-CFG020 BANNER “CurrHistProgramAttr” flag. (1-C8C7MP)

UCX-CFG020 BANNER X

Review and configure the following new UCX-CFG020 BANNER flags: (1-DOP3AX) “InProgress Withdraws” (1-DPKPW0) “Apply Historic Repeat” (1-E9LSIF) “Load Current Grade”, “Grading Increment” and “Grading Period Length” (1-6SQ2T7) “Percentile Grading” (1-EL4DQP) “Load SHRTRCR Grade” and “Override SHRTRCR grade”

UCX-CFG020 COURSELINK X Add and configure the UCX-CFG020 COURSELINK entry (1-5O1CJ3, 1-6EKV77)

UCX-CFG020 DAP14 X Review the In-progress vs Completed Special Topic in the Techical Guide, and configure the UCX-CFG020 DAP14 “In-progress vs Completed” flag. (1-377PTP)

UCX-CFG020 DAP14 X Review and configure the UCX-CFG020 DAP14 "Insufficient OTHER GPA" flag. (1-5RSCHA)

UCX-CFG020 DAP14 X Review and configure the UCX-CFG020 DAP14 “Fallthru-Counts-in-Overall” flag. (1-8Y78ZO)

UCX-CFG020 EXCEPTIONS X Add and configure the new UCX-CFG020 EXCEPTIONS entry (1-3TSEQO)

UCX-CFG020 LDAP X Add and configure the new UCX-CFG020 LDAP entry (if UCX-CFG020 WEBPARAMS “Enable LDAP” is set to Y). (1-4L1AHN)



UCX Entry

DW

4.0.

1

DW

4.0.

2

DW

4.0.

3

DW

4.0.

4

DW

4.0.

5

DW

4.0.

6

DW

4.0.

7

DW

4.0.

8

Change

UCX-CFG020 LDAP X Review and configure the "User ID Attribute Suffix" flag if needed for Luminis integration (e.g. “::sct”). Otherwise, leave this blank. (1-7P99J6) Review and configure the "Use ADMIN Bind/Search" flag. (1-7X5J2P)

UCX-CFG020 LDAP_FILTER_START X

Add and configure new UCX-CFG020 LDAP_FILTER_START entry (if UCX-CFG020 LDAP "Use ADMIN Bind/Search" value is set to "Y") (1-7X5J2P)

UCX-CFG020 LDAP_FILTER_END X

Add and configure new UCX-CFG020 LDAP_FILTER_END entry (if UCX-CFG020 LDAP "Use ADMIN Bind/Search" value is set to "Y") (1-7X5J2P)

UCX-CFG020 LDAP_ADMIN_PWD X

Add and configure new UCX-CFG020 LDAP_ADMIN_PWD entry (if UCX-CFG020 LDAP "Use ADMIN Bind/Search" value is set to "Y") (1-7X5J2P)

UCX-CFG020 LDAP_ADMIN_DN X Add and configure new UCX-CFG020 LDAP_ADMIN_DN entry (if UCX-CFG020 LDAP "Use ADMIN Bind/Search" value is set to "Y") (1-7X5J2P)

UCX-CFG020 LDAPDN X Add and configure the new UCX-CFG020 LDAPDN entry (if UCX-CFG020 WEBPARAMS “Enable LDAP” is set to Y). (1-4L1AHN)

UCX-CFG020 LDAPSERVER X Add and configure the new UCX-CFG020 LDAPSERVER entry (if UCX-CFG020 WEBPARAMS “Enable LDAP” is set to Y). (1-4L1AHN)

UCX-CFG020 LEEPFROG X Add and configure the new UCX-CFG020 LEEPFROG entry (if using CourseLeaf and InstantRapport) (1-5DVQ7J)

UCX-CFG020 LF_COURSELEAFURL X Add and configure the new UCX-CFG020 LF_COURSELEAFURL entry (if

using CourseLeaf and InstantRapport) (1-5DVQ7J)

UCX-CFG020 LF_IRADVURL X Add and configure the new UCX-CFG020 LF_IRADVURL entry (if using CourseLeaf and InstantRapport) (1-5DVQ7J)

UCX-CFG020 LF_IRSTUURL X Add and configure the new UCX-CFG020 LF_IRSTUURL entry (if using CourseLeaf and InstantRapport) (1-5DVQ7J)

UCX-CFG020 LF_IRCHATICONURL X Add and configure the new UCX-CFG020 LF_IRCHATICONURL entry (if

using CourseLeaf and InstantRapport) (1-5DVQ7J)

UCX-CFG020 PLANNER X

Configure newly implemented fields (Show Minor, Show Concentration, Show College, Show Liberal Learning, Show Specialization, Show Program). (1-3RDNKD)

UCX-CFG020 PLANNER X Review and configure the “Plans Need Approval” flag (1-4POJ9Z)

UCX-CFG020 PLANNER X Review and configure the “Allow Changes to Approved Plans” flag (1-89HEP7)

UCX-CFG020 SEARCH X Review and configure the “Show Program” and “Show Catalog Year” flags (1-B4S5HB)

UCX-CFG020 TREQ X TreQ sites only: Review and configure UCX-CFG020 TREQ flags for WebTreQer (1-4JBZHP)

UCX-CFG020 WEB X Review the UCX-CFG020 WEB entry and set the “Date Format” field. (1-50LOHB)

UCX-CFG020 WEB X Review the UCX-CFG020 WEB entry and set the “Use CourseLeaf” and “Use InstantRapport” fields (if using CourseLeaf and InstantRapport) (1-5DVQ7J)

UCX-CFG020 WEB X Review and update the UCX-CFG020 WEB freeze and description Y/N flags (1-ATO4I3)

UCX-CFG020 WEBPARAMS X Review the UCX-CFG020 WEBPARAMS entry “Enable LDAP” and set accordingly for your site. (1-4L1AHN) Review and configure the “Enable Workflow” flag (1-4POJ9Z, 1-4SFMAH)

UCX-CFG020 WEBPARAMS X Set the new "Number of" settings for DAP09, UTL79 and WEB04 (1-58Y5XL)

UCX-CFG020 WHATIF X Review and configure the new UCX-CFG020 “Show College flag” (1-64HZKU)

UCX-CFG020 WORKFLOWCREDENTIALS X Add and configure the new UCX-CFG020 WORKFLOWCREDENTIALS

entry (1-4POJ9Z, 1-4SFMAH)

UCX-CFG020 WORKFLOWWSDL X Add and configure the new UCX-CFG020 WORKFLOWWSDL entry (1-4POJ9Z, 1-4SFMAH)

UCX-CFG020 WORKFLOWPETITION X Add and configure the new UCX-CFG020 WORKFLOWPETITION entry

(1-4POJ9Z, 1-4SFMAH)

UCX-CFG020 WORKFLOWPLANNER X Add and configure the new UCX-CFG020 WORKFLOWPLANNER entry

(1-4POJ9Z, 1-4SFMAH)

UCX-CFG068 X Add and configure the new UCX-CFG068 entries for the new Course Sequencing functionality (1-BESITN)

UCX-RPT036 X Review "Show Split Credits Section" settings for the appropriate Audit Report Formats (1-3UAXNR)



UCX Entry

DW

4.0.

1

DW

4.0.

2

DW

4.0.

3

DW

4.0.

4

DW

4.0.

5

DW

4.0.

6

DW

4.0.

7

DW

4.0.

8

Change

UCX-RPT036 X Review and update all WEB## and SEP30 entries for new CourseLink functionality (1-5O1CJ3, 1-6EKV77)

UCX-RPT050 – RPT057 X

Review and configure new UCX-RPT050, RPT051, RPT052, RPT053, RPT054, RPT055, RPT056 and RPT057 entries for new CourseLink functionality (1-5O1CJ3, 1-6EKV77)

UCX-STU016 X TreQ sites only using WebTreQer: Review and configure the “Show in WebTreQer” flag (1-5XF43R)

UCX-STU016 X Review and populate UCX-STU016 with the correct Financial Aid Year for running Financial Aid Audits (1-9DO2BH)

UCX-STU016 X Review and populate the Term Type field on all entries in UCX-STU016 if using the Athletic Eligibility Audit functionality (1-BF3MTF)



UCX-STU035 X TreQ sites only using WebTreQer: Review and configure the “WebTreQer” flag (1-4JBZHP)


UCX-STU346 X TreQ sites only using WebTreQer: Review and configure the “Show in WebTreQer Picklist” (1-4JBZHP)

UCX-STU350 X TreQ sites only: Review and configure the “Show in WebTreQer” flag (1-5XF43R)

UCX-STU350 X Review and populate the Full-time Credits field on all school entries in UCX-STU350 if using the Athletic Eligibility Audit functionality (1-BF3MTF)

UCX-STU352 X Discipline Codes with imbedded SPACES must be deleted and re-added using UNDERSCORES in place of the imbedded SPACES. (1-48KS2J)

UCX-STU385 X

If you have your failing grades in SHRGRDE with COMPLETED_IND set to N, then you must set the UCX-STU385 Override Incomplete value to N for these failing grades. Setting Override Incomplete = N causes these failed classes to be placed into the insufficient section. Review the Override Incomplete value in UCX-STU385 and update as needed. (1-3O8EQP)

UCX-STU385 X Review and populate the “Override Transfer Grade” column if UCX-CFG020 BANNER “Load SHRTRCR Grade” and “Override SHRTRCR Grade” are set to Y (1-EL4DQP)


UCX-TRQ060 X Review and update UCX-TRQ060 for the favorite/feeder schools; fill out the new School URL field for new CourseLink functionality (1-5O1CJ3, 1-6EKV77)


SHPCFG Review and Configuration

New with release…

Key D

W4.

0.1

DW

4.0.

2

DW

4.0.

3

DW

4.0.

4

DW

4.0.

5

DW

4.0.

6

DW

4.0.

7

DW

4.0.

8 Change

SDNTEMOD X Clients should review the notes-related access granted to Students as well as Advisors and REG. Advisors and REG need to be given SDNTEMOD only in order to update any student's notes (1-41674C)

PTSAUDIT X The PTSAUDIT key is required to run the Transit AUD01 report. It is delivered as a standard key in the SRNREG group. If additional access to this report is required beyond the SRNREG group, clients should review and update the SHPCFG accordingly (1-3VDPSE).

(APP User Class) X Update the SHPCFG to contain the “APP” User Class if using the new Applicant functionality. Review the Technical User Guide “Security” documentation for more details.

SDTREQER X Update the SHPCFG to contain the “SDTREQER” key if clients are using WebTreQer. (REG, ADV, ADVX User Classes)

X The REG and ADV/ADVX user classes now have the SDNTERUN key to run an audit after note changes occur. Use SHPCFG to remove/add this key to user-classes as needed. (1-5ZBV77)

(REG, AID and ATHL User Classes)

X The REG, AID and ATHL user classes now have the SDDELAUD, AUDFREEZ, AUDDESCR keys to freeze, describe or delete an audit. Use SHPCFG to remove/add these keys to user-classes as needed. (1-ATO4I3)

(REG User Class) X The REG user class now gets the SDAIDAUD and SDAIDHIS Financial Aid keys as the default. Use SHPCFG to remove/add these keys to user-classes as needed. (1-ATO4I3)

(ATHL User Class) X

Update the SHPCFG to contain the “ATHL” User Class if using the new Athletic Eligibility Audit functionality. Review the Technical User Guide “Security” documentation for more details.

SHPENTRY X Update SHPCFG to contain keys required to run the SHPEntry Flex application. Review the SHPEntry Technical user Guide for more details. Keys to SHPEntry are SHPENTRY, SHPUSER, SHPGROUP, SHPLOGS and SHPPASS. (1-ATDLQR)

Web Changes 1. Any worksheet xsl files that display a student header showing major/minor information will need to be

changed to use the new <Goal> xml nodes under the <Deginfo> nodes. Clients should review the new DGW_Reports.xsl delivered in this update to see how the student header makes use of the Goal data to display the student header information. (DW4.0.2 1-3TSEQO)

2. If your site is using the new CheckElectivesCreditsAllowed functionality, localizations need to be made to

the worksheet stylesheets in order to show the fall-through section with the new information. (DW4.0.2 1-4NRFQX)

3. Configuration options have been added to allow clients to search on a custom data value, and to show that

custom data value in the student context area of the main page. Any piece of data loaded into the rad-custom-dtl can be used on the Find Student page. See the Technical Guide - Web Interface section for specific details on how to set this up. (DW4.0.3 1-56UUOV)

4. Localizations need to be made to the worksheet stylesheets in order to define whether or not petitions are hidden in the worksheets. Set the vShowPetitions flag in the stylesheets to Y or N to show or hide the petitions in the worksheets. (DW4.0.4 1-5LYI9K)

5. Note that IRISLink.cgi has significantly changed with the DW4.0.6 update. You should keep a copy of

this file before overlaying it with the new version. The settings in this file have been moved to a separate file for future ease of updates. Refer to the Other Server Changes section in the Configuration Considerations section in this document for specific instructions.


(DW4.0.6 1-AK9L0V) 6. Copy the app/shpscripts/SEARCHCUSTOM page to your local/shpscripts directory and modify as needed

to add your own search fields searching on the data in the rad_custom_dtl. (DW4.0.7 1-B4S5HB)

Bridge changes for RAD clients 1. The SHPU shp_access_code field was changed from 20 to 64 bytes in the RAD BIF documentation. The

Banner BIF documentation was fixed in DW4.0.0. RAD clients should review the R171SHPU section of the DGW_Technical_Guide_BIF. (DW4.0.1 1-460KH5)

2. Clients should review the UCX section of the

DGW_Technical_Guide_Banner_Data_Mapping_for_BIF as well as the DGW_Technical_Guide_UCX documentation for more information about these changes and/or additions. Specifically the following changes should be made:

a. STU352 - Discipline codes with imbedded blanks must be changed to have underscores. The old Discipline codes with imbedded blanks should be deleted.

b. SCRIBE - rules that have discipline codes with imbedded blanks must be modified to use underscores instead.

c. Students who have courses with these modified Discipline codes MUST be re-bridged. d. Course master records with these modified Discipline codes must be modified and re-bridged.

Banner clients must run ban41. (DW4.0.1 1-48KS2J)

3. During the host installation clients are given the option to convert the current DegreeWorks degree and

school data to the new rad_goal_dtl and rad_goaldata_dtl data structures. This process uses a script named "degrees2goals". If clients choose to skip this step of the installation process, the bridge must be run for the "normal" student population to create the rad_goal_dtl and rad_goaldata_dtl records for the new data structure requirements. Historic data can be converted through the "degrees2goals" script. The script should be run prior to bridging in the "normal" student population since the script deletes existing goal records before converting the degree and school data to the rad_goal_dtl and rad_goaldata_dtl structure. (DW4.0.2 1-3TSEQO)

4. In order to take advantage of the new applicant indicators on the web, clients must modify the (R032GOAL) RAD_GOAL_DTL BIF layout to load student records with an “S” and applicant records with an “A” in the rad_degree_src. If the field is left blank, the record is treated as a student record. (DW4.0.4 1-5IVY93)


Native Integrated Interface for Banner 1. Banner Customers only (DW4.0.1 1-497YVI): Make sure to place these SSRMEET entries into your

bannerextract.config file in admin/common - you may put them anywhere, but the baseline software has them after the SSRATTR entries:

################### SSRMEET - COURSE SECTION MEETINGS (dap58) ############# # SSRMEET must be a; AND is required at the end of the WHERE # The SSRSECT_TERM_CODE and SSRSECT_CRN will be added to the WHERE # clause by dap58. You may add additional WHERE requirements here. SSRMEET-from: FROM SSRMEET a SSRMEET-where: WHERE # SSBSECT_TERM_CODE = <Hold Term> # AND SSBSECT_CRN = <Hold CRN>

2. Banner Customers only (DW4.0.2 1-4GOGG3): Make sure to place these SMRPRLE entries into your

bannerextract.config file in admin/common.

################### SMRPRLE - STU316 - PROGRAM CODES (ban44) ########### # SMRPRLE must be a; AND is NOT included at the end of the WHERE SMRPRLE-from: FROM SMRPRLE a SMRPRLE-where: # NO WHERE clause is included in ban44. # Add the entire WHERE clause if desired. #############################################################

To populate the UCX-STU316 entries:

a. Make sure the DegreeWorks Oracle user has read access to the SMRPRLE table in Banner. b. Insert "STU316" into a my.ucx file. c. Run the extract to populate your UCX-STU316 Program code table: $ bannerextract ucx my.ucx

3. Banner Customers only (DW4.0.2 1-3ROPTR): Modify the bannerextract.config in admin/common so

that it contains the following SGRADVR_PRIM_IND checks for SGRADVR2.

################### SGRADVR2 - ADVISOR secondary (ban40) ############### # SGRADVR must be a; AND is required at the end of the WHERE SGRADVR2-from: FROM SGRADVR a SGRADVR2-where: WHERE (a.SGRADVR_PRIM_IND IS NULL or SGRADVR2-where: a.SGRADVR_PRIM_IND = 'N' or SGRADVR2-where: a.SGRADVR_PRIM_IND = ' ') SGRADVR2-where: AND # a.SGADVR_PIDM = <students-pidm> # AND SGRADVR_TERM_CODE_EFF = <HoldTermCode>

4. Banner Customers only (DW4.0.2 1-4PLONJ): Modify the bannerextract.config in admin/common so that it contains the following SCBCRS4 entries or clone your SCBCRSE entries and change ‘SCBCRSE’ to ‘SCBCRS4’ in the keys in front of the ‘-from’ and ‘-where’. These entries will be used to read the SCBCRSE table by the EQUIV extract (ban43) in determining what ‘Inactive’ Courses to skip when processing the SCREQIV table. It may be desirable to make these entries different than those used by the Student Extract (ban40) which uses the ‘SCBCRSE’ entries.


################### SCBCRS4 – EQUIV (ban43) ############### # Special retrieval of the SCBCRSE records for equivalency processing # SCBCRSE must be a; AND is required at the end of the WHERE SCBCRS4-from: FROM SCBCRSE a, STVCSTA SCBCRS4-where: WHERE a.SCBCRSE_CSTA_CODE = STVCSTA_CODE AND SCBCRS4-where: STVCSTA_ACTIVE_IND = 'A' SCBCRS4-where: AND a.SCBCRSE_EFF_TERM = SCBCRS4-where: (SELECT MAX(b.SCBCRSE_EFF_TERM) SCBCRS4-where: FROM SCBCRSE b SCBCRS4-where: WHERE b.SCBCRSE_SUBJ_CODE = a.SCBCRSE_SUBJ_CODE SCBCRS4-where: AND b.SCBCRSE_CRSE_NUMB = a.SCBCRSE_CRSE_NUMB) SCBCRS4-where: AND # SCBCRSE_SUBJ_CODE = <Subj Code> AND # SCBCRSE_CRSE_NUMB = <Crse Numb> AND # SCBCRSE_EFF_TERM <= <Hold Term>

5. Banner Customers only (DW4.0.2 1-4SR92L): If Admissions Applicants are to be extracted from Banner and imported into DegreeWorks then the $LOCAL_HOME/sql/bannerapplicants.sql file must be created with the appropriate SQL to be used when Applicants are being processed either through RAD30 via Transit or the “bannerextract applicants” script. Copy the bannerstudents.sql file to bannerapplicants.sql and customize it to select the appropriate applicant pool. Review the “Applicant Processing” special topic in the Technical Banner Considerations Guide for more information.

Modify the bannerextract.config in admin/common so that it contains the following entries if Admissions Applicants are desired to be extracted from Banner and imported into DegreeWorks. Make sure to customize the entries for your site.

################### F_CLASS_CALC_FNC (ADMISSIONS) ##################### # F_CLASS_CALC_FNC: PIDM + LEVL_CODE + TERM_CODE # ******** ************ # NO WHERE on the first "CALCFN2-where:" line and NO Final AND # ******** ************ CALCFN2-from: FROM SARADAP a CALCFN2-where: a.SARADAP_TERM_CODE_ENTRY = CALCFN2-where: (SELECT MAX(b.SARADAP_TERM_CODE_ENTRY) CALCFN2-where: FROM SARADAP b WHERE b.SARADAP_PIDM = a.SARADAP_PIDM) # F_CLASS_CALC_FNC = PIDM + LEVL_CODE + TERM_CODE ################### SARADAP - APPLICANT (ban40) ####################### # SARADAP must be a; AND is required at the end of the WHERE # Used if no 'ADMISSIONS' SORLCUR/SORLFOS records are found and if # the UCX-CFG020 LoadSARADAPGoal = 'Y' SARADAP-from: FROM SARADAP a SARADAP-where: WHERE a.SARADAP_TERM_CODE_ENTRY = SARADAP-where: (SELECT MAX(b.SARADAP_TERM_CODE_ENTRY) SARADAP-where: FROM SARADAP b SARADAP-where: WHERE b.SARADAP_PIDM = a.SARADAP_PIDM) SARADAP-where: AND # a.SARADAP_PIDM = <applicant's-pidm> ################### SARADAPC - APPLICANT (ban40) ##################### # SARADAP must be a; AND is required at the end of the WHERE # This record is linked to the 'ADMISSIONS' SORLCUR record using the # SORLCUR_PIDM, SORLCUR_TERM_CODE and SORLCUR_KEY_SEQNO SARADAPC-from: FROM SARADAP a, SORLCUR c SARADAPC-where: WHERE # a.SARADAP_PIDM = <applicant's-pidm> AND


# a.SARADAP_TERM_CODE_ENTRY = <applicant's SORLCUR_TERM_CODE> AND # a.SARADAP_APPL_NO = <applicant's SORLCUR_KEY_SEQNO> ################### SORLCUR2 - ADMISSIONS CURRICULUM (ban40) ############ # SORLCUR must be a; AND is required at the end of the WHERE SORLCUR2-from: FROM SORLCUR a, STVTERM t, SARADAP c SORLCUR2-where: WHERE (SELECT COUNT(*) FROM SHRTRCR SORLCUR2-where: WHERE SHRTRCR_PIDM = c.SARADAP_PIDM) > 0 SORLCUR2-where: AND t.STVTERM_START_DATE > SYSDATE SORLCUR2-where: AND ((SELECT COUNT(*) FROM SGBSTDN SORLCUR2-where: WHERE SGBSTDN_PIDM = c.SARADAP_PIDM) < 1 SORLCUR2-where: OR (SELECT COUNT(*) FROM STVSTST, SGBSTDN p SORLCUR2-where: WHERE STVSTST_CODE = p.SGBSTDN_STST_CODE SORLCUR2-where: AND STVSTST_REG_IND = 'Y' SORLCUR2-where: AND p.SGBSTDN_TERM_CODE_EFF = (SELECT MAX SORLCUR2-where: (o.SGBSTDN_TERM_CODE_EFF) FROM SGBSTDN o SORLCUR2-where: WHERE o.SGBSTDN_PIDM = p.SGBSTDN_PIDM SORLCUR2-where: AND o.SGBSTDN_TERM_CODE_EFF < SORLCUR2-where: c.SARADAP_TERM_CODE_ENTRY)) < 1) SORLCUR2-where: AND a.SORLCUR_CACT_CODE = 'ACTIVE' SORLCUR2-where: AND a.SORLCUR_LMOD_CODE = 'ADMISSIONS' SORLCUR2-where: AND a.SORLCUR_SEQNO = (SELECT MAX(b.SORLCUR_SEQNO) SORLCUR2-where: FROM SORLCUR b SORLCUR2-where: WHERE b.SORLCUR_PIDM = a.SORLCUR_PIDM SORLCUR2-where: AND b.SORLCUR_PRIORITY_NO = a.SORLCUR_PRIORITY_NO SORLCUR2-where: AND b.SORLCUR_LMOD_CODE = 'ADMISSIONS') SORLCUR2-where: AND a.SORLCUR_PIDM = c.SARADAP_PIDM SORLCUR2-where: AND a.SORLCUR_TERM_CODE = c.SARADAP_TERM_CODE_ENTRY SORLCUR2-where: AND a.SORLCUR_KEY_SEQNO = c.SARADAP_APPL_NO SORLCUR2-where: AND t.STVTERM_CODE = c.SARADAP_TERM_CODE_ENTRY SORLCUR2-where: AND # a.SORLCUR_PIDM = <students-pidm> ################### SORLFOS2 - APPLICANT FIELD OF STUDY (ban40) ######## # SORLFOS must be a; AND is required at the end of the WHERE SORLFOS2-where: FROM SORLFOS a, SORLCUR b, STVTERM t, SARADAP d SORLFOS2-where: WHERE (SELECT COUNT(*) FROM SHRTRCR SORLFOS2-where: WHERE SHRTRCR_PIDM = d.SARADAP_PIDM) > 0 SORLFOS2-where: AND t.STVTERM_START_DATE > SYSDATE SORLFOS2-where: AND ((SELECT COUNT(*) FROM SGBSTDN SORLFOS2-where: WHERE SGBSTDN_PIDM = d.SARADAP_PIDM) < 1 SORLFOS2-where: OR (SELECT COUNT(*) FROM STVSTST, SGBSTDN p SORLFOS2-where: WHERE STVSTST_CODE = p.SGBSTDN_STST_CODE SORLFOS2-where: AND STVSTST_REG_IND = 'Y' SORLFOS2-where: AND p.SGBSTDN_TERM_CODE_EFF = (SELECT MAX SORLFOS2-where: (o.SGBSTDN_TERM_CODE_EFF) FROM SGBSTDN o SORLFOS2-where: WHERE o.SGBSTDN_PIDM = p.SGBSTDN_PIDM SORLFOS2-where: AND o.SGBSTDN_TERM_CODE_EFF < SORLFOS2-where: d.SARADAP_TERM_CODE_ENTRY)) < 1) SORLFOS2-where: AND b.SORLCUR_CACT_CODE = 'ACTIVE' SORLFOS2-where: AND b.SORLCUR_LMOD_CODE = 'ADMISSIONS' SORLFOS2-where: AND b.SORLCUR_SEQNO = (SELECT MAX(f.SORLCUR_SEQNO) SORLFOS2-where: FROM SORLCUR f SORLFOS2-where: WHERE f.SORLCUR_PIDM = b.SORLCUR_PIDM SORLFOS2-where: AND f.SORLCUR_PRIORITY_NO = b.SORLCUR_PRIORITY_NO SORLFOS2-where: AND f.SORLCUR_LMOD_CODE = 'ADMISSIONS') SORLFOS2-where: AND b.SORLCUR_PIDM = d.SARADAP_PIDM SORLFOS2-where: AND b.SORLCUR_TERM_CODE = d.SARADAP_TERM_CODE_ENTRY SORLFOS2-where: AND b.SORLCUR_KEY_SEQNO = d.SARADAP_APPL_NO SORLFOS2-where: AND t.STVTERM_CODE = d.SARADAP_TERM_CODE_ENTRY


SORLFOS2-where: AND a.SORLFOS_CSTS_CODE = 'INPROGRESS' SORLFOS2-where: AND a.SORLFOS_CACT_CODE = 'ACTIVE' SORLFOS2-where: AND a.SORLFOS_PIDM = b.SORLCUR_PIDM SORLFOS2-where: AND a.SORLFOS_LCUR_SEQNO = b.SORLCUR_SEQNO SORLFOS2-where: AND a.SORLFOS_SEQNO = SORLFOS2-where: (SELECT MAX(l.SORLFOS_SEQNO) FROM SORLFOS l SORLFOS2-where: WHERE l.SORLFOS_PIDM = b.SORLCUR_PIDM SORLFOS2-where: AND l.SORLFOS_PRIORITY_NO = a.SORLFOS_PRIORITY_NO SORLFOS2-where: AND l.sorlfos_csts_code = 'INPROGRESS' SORLFOS2-where: AND l.SORLFOS_LCUR_SEQNO = b.SORLCUR_SEQNO) SORLFOS2-where: AND # a.SORLFOS_PIDM = <students-pidm>

6. Banner Customers only (DW4.0.2 1-4SR92L): If the new Applicant extract is going to be used, then access must be granted in the following file: $ADMIN_HOME/common/SHPCFG - add the "APP" User Class with the SRNAPP capabilities. Copied below is the default. Please review the Technical User Guide "Security" documentation for more details.

############# Applicants ################################# if (DGWUSERCLASS = "APP") then TIMEINC = 9999 #Infinity TIMEMAX = 9999 addgroup = SRNAPP #See System Administrator's Guide for list of keys ########################################################

7. Banner Customers with TreQ licensed (DW4.0.2 1-4JBZHP): Give the DegreeWorks Oracle user access to the STVACCL Banner validation table. Modify the admin/common/bannerextract.config to contain the following extract of UCX-STU346.

################### STVACCL - STU346 - CALENDAR CODES (ban44) ############ # STVACCL must be a; AND is NOT included at the end of the WHERE STVACCL-from: FROM STVACCL a STVACCL-where: # NO WHERE clause is included in ban44. # Add the entire WHERE clause if desired.

Afterwards, populate the UCX-STU346 Calendar Code table:

a. Insert "STU346" into a my.ucx file (without the quotes). b. Run the extract to populate your UCX-STU346 Calendar Code table: $ bannerextract ucx my.ucx

Additionally, review and populate the Convert Number and Show in WebTreQer fields on each of the records using SureCode.

8. Banner Customers with TreQ licensed (DW4.0.2 1-4KSCEN): Modify the bannerextract.config in admin/common so that it contains the following entries in order to bring over the mappings from Banner to the articulation tables in TreQ (and WebTreQer). Customers must also run bannerextract ETS so that the rad_ets_mst has been populated.

################### SHBTATC - TRANSFER CATALOG DATA (ban46) ########### # SHBTATC must be a; AND is NOT included at the end of the WHERE SHBTATC-from: FROM SHBTATC a SHBTATC-where: WHERE a.SHBTATC_TRNS_REVIEW_IND = 'Y' SHBTATC-where: AND a.SHBTATC_TAST_CODE IN SHBTATC-where: (SELECT STVTAST_CODE FROM STVTAST SHBTATC-where: WHERE STVTAST_STATUS_IND = 'A')


################### SHBTATC - TRANSFER CATALOG DATA (ban46) ########### # SHBTATC must be a; AND is required at the end of the WHERE SHBTATC2-from: FROM SHBTATC a SHBTATC2-where: WHERE a.SHBTATC_TRNS_REVIEW_IND = 'Y' SHBTATC2-where: AND a.SHBTATC_TAST_CODE IN SHBTATC2-where: (SELECT STVTAST_CODE FROM STVTAST SHBTATC2-where: WHERE STVTAST_STATUS_IND = 'A') SHBTATC2-where: AND # a.SHBTATC_SBGI_CODE = <school-sbgi-code> ################### SHRTATC - TRANSFER ARTICULATION (ban46) ########### # SHRTATC must be a; AND is NOT included at the end of the WHERE SHRTATC-from: FROM SHRTATC a SHRTATC-where: WHERE ################### SHRICMT - TRANSFER COURSE COMMENT (ban46) ######### # SHRICMT must be a; AND is NOT included at the end of the WHERE SHRICMT-from: FROM SHRICMT a SHRICMT-where: WHERE a.SHRICMT_SEQNO IN (1,2) AND

9. Banner Customers only (DW4.0.2 1-4OALJO): Configure the UCX-CFG020 BANNER “Program as

Degree” flag to “Y” if you would like Programs loaded into the DEGREE goal-dtl records, if Programs exist. Otherwise, set the flag to “N”. Please note, this is very specific functionality that must be accounted for in your site’s scribed blocks and Banner data configuration. Existing clients may need to re-scribe blocks in this new "Program as Degree" scheme.

10. Banner Customers only (DW4.0.2 1-3TSEQO): During the host installation clients are given the option to

convert the current DegreeWorks degree and school data to the new rad_goal_dtl and rad_goaldata_dtl data structures. This process uses a script named "degrees2goals". If clients choose to skip this step of the installation process, the STUDENT mode of RAD30 must be run for the "normal" student population to create the rad_goal_dtl and rad_goaldata_dtl records for the new data structure requirements. Historic data can be converted through the "degrees2goals" script. The script should be run prior to RAD30 on the "normal" student population since the script deletes existing goal records before converting the degree and school data to the rad_goal_dtl and rad_goaldata_dtl structure.

11. Banner Customers only (DW4.0.3 1-55HPE5): Configure the UCX-CFG020 BANNER “Transfer

Program Attr” flag. Modify the bannerextract.config in admin/common so that it contains the following entries to create rad_attr_dtl for transfer classes that have been applied to a Program in Banner:

################### SHRDGMR - Degree Applied Table (ban40) ################ # Standard is to only select by student's pidm - but you may add to # the WHERE clause if needed - but don't forget the final AND SHRDGMR-from: FROM SHRDGMR a SHRDGMR-where: WHERE # a.SHRDGMR_PIDM = <students-pidm> ############# SHRTRCD - TRANSFER COURSE DEGREE APPLIED (ban40) ######### # Standard is to only select by student's pidm - but you may add to # the WHERE clause if needed - but don't forget the final AND SHRTRCD-from: FROM SHRTRCD a SHRTRCD-where: WHERE a.SHRTRCD_APPLIED_IND = 'Y' AND # a.SHRTRCD_PIDM = <students-pidm>


12. Banner Customers only (DW4.0.4 1-5IVY93): In order to take advantage of the new applicant indicators on the web the rad_degree_src field on the rad_goal_dtl must be loaded with an “A” or “S” (a “blank” value is treated as “S”). The extract will load these values. Records that are not extracted will need to have the rad_degree_src value manually updated.

13. Banner Customers only (DW4.0.4 1-5O1CJ3, 1-6EKV77): In order to use the new CourseLink functionality you must do the following:

a. Give your DegreeWorks Banner Oracle user read access to STVATTR b. Run the bannerextract in both "ets" and "mappings" mode c. Add this section to your admin/common/bannerextract.config file:

################### STVATTR - ATTRIBUTES (dap58) ############# # STVATTR must be a; AND is NOT included at the end of the WHERE STVATTR-from: FROM STVATTR a STVATTR-where:

d. Add this section to your admin/common/bannerextract.config file:

################### SCBCRSE/SCRATTR #################################### # Used for dap58 (Courselink) to get courses with specific attributes # You may add additional WHERE requirements here. COURSELINKATTR-from: FROM SCBCRSE a, SCRATTR b COURSELINKATTR-where: WHERE

14. Banner Customers only (DW4.0.4 1-76RL4U): Since the student extract (ban40) was modified to get the catalog year value from SORLCUR if it is blank in SORLFOS, if clients have blank SORLFOS_TERM_CODE_CTLG columns in Banner, they will need to rebridge these students and run new audits.

15. Banner Customers with TreQ licensed (DW4.0.4 1-5RHOYJ): In order to utilize the new functionality to roll articulated transfer records from TreQ to the Banner Student System, client must grant write access to Banner tables SHRTRIT, SHRTRAM and SHRTRTK.

16. Banner Customers only (DW4.0.7 1-92QZO2): In order to use the CourseLink cross-listed open seat availability fix, clients must do the following:

a. Give your DegreeWorks Banner Oracle user read-access to SSRXLST and SSBXLST. b. Add these two sections to your $ADMIN_HOME/common/bannerextract.config - after the

SSRMEET section.

################### SSRXLST - COURSE SECTION CROSS-LISTING (dap58) ########### # SSRXSLST must be a; AND is required at the end of the WHERE # The SSRXLST_TERM_CODE and SSRXLST_CRN will be added to the WHERE # clause by dap58. You may add additional WHERE requirements here. SSRXLST-from: FROM SSRXLST a SSRXLST-where: WHERE # SSRXLST_TERM_CODE = <ssbsect Term> # AND SSRXLST_CRN = <ssbsect CRN> ################### SSBXLST - COURSE SECTION CROSS-LISTING (dap58) ########### # SSBXSLST must be a; AND is required at the end of the WHERE # The SSBXLST_TERM_CODE and SSBXLST_XLST_GROUP will be added to the WHERE # clause by dap58. You may add additional WHERE requirements here. SSBXLST-from: FROM SSBXLST a SSBXLST-where: WHERE # SSBXLST_TERM_CODE = <ssbsect term> # AND SSBXLST_XLST_GROUP = <ssrxlst xlst-group>


17. Banner Customers only (DW4.0.7 1-BF3MTF): In order to use the new Athletic Eligibility Audit, clients

must do the following: a. Give your DegreeWorks Banner Oracle user read-access grant to the SGRATHE and

SGRSPRT tables. b. Add these two sections to your $ADMIN_HOME/common/bannerextract.config - after the

SGRSATT section.

################### SGRATHE - STUDENT ATHLETE (ban40) ############## # SGRATHE must be a; AND is required at the end of the WHERE more is added SGRATHE-from: FROM SGRATHE a SGRATHE-where: WHERE # a.SGRATHE_PIDM = <students-pidm>

18. Banner Customers only (DW4.0.7 1-C8C7MP): In order to use the new attribute functionality, clients

must do the following: a. Give your DegreeWorks Banner Oracle user read-access grant to the SHRTCKD table. b. Add this section to your $ADMIN_HOME/common/bannerextract.config.

################### SHRTCKD - Link to SHRDGMR (ban40) ################## # Standard is to only select by student's pidm - but you may add to # the WHERE clause if needed - but don't forget the final AND SHRTCKD-from: FROM SHRTCKD a SHRTCKD-where: WHERE a.SHRTCKD_APPLIED_IND is not null AND # a.SHRTCKD_PIDM = <students-pidm> 19. Banner Customers only (DW4.0.8 1-E9LSIF): This change is required for the new

LoadCurrentGradeIfExists flag in UCX_CFG020 BANNER. This change does NOT filter for a record where SFRSTCR_GRDE_DATE is NULL and thus reads ALL SFRSTCR records. BAN40 will filter them as appropriate. In order to use the new current grade functionality, clients must add the following to bannerextract.config:

################### SFRSTCR2 - CURRENT CLASS (ban40) #################### # Used during the grading period where a class could potentially be in # SHRTCKN as well as SFRSTCR - duplicates are eliminated by ban40.ec. # Only used when UCX_CFG020 BANNER LoadCurrentGradeIfExists = "Y". # Removed the "a.SFRSTCR_GRDE_DATE is NULL" edit. Cannot be used here. # However, does include a filter for Withdrawn classes - may remove the # "OR STVRSTS_WITHDAW_IND = 'Y')" if not checking for withdraws. # SFRSTCR must be a; AND is required at the end of the WHERE SFRSTCR2-from: FROM SFRSTCR a SFRSTCR2-where: WHERE a.SFRSTCR_RSTS_CODE IN SFRSTCR2-where: (SELECT STVRSTS_CODE SFRSTCR2-where: FROM STVRSTS WHERE STVRSTS_INCL_SECT_ENRL = 'Y' SFRSTCR2-where: OR STVRSTS_WITHDRAW_IND = 'Y') SFRSTCR2-where: AND # a.SFRSTCR_PIDM = <students-pidm>

20. Banner Customers only (DW4.0.8 1-DOP3AX) This change is required for clients who wish to use the

“In-Progress Withdraw” option which will import withdrawn classes from the in-progress class table SFRSTCR. Only make the following change in red to bannerextract.config if you wish to use this new functionality and have set the new UCX_CFG020 BANNER flag “InProgress Withdraws” to “Y”. If the “InProgress Withdraws” flag is blank or set to “N” then do not modify the SFRSTCR query in bannerextract.config:


################### SFRSTCR - CURRENT CLASS (ban40) #################### # SFRSTCR must be a; AND is required at the end of the WHERE SFRSTCR-from: FROM SFRSTCR a SFRSTCR-where: WHERE a.SFRSTCR_RSTS_CODE IN SFRSTCR-where: (SELECT STVRSTS_CODE SFRSTCR-where: FROM STVRSTS WHERE STVRSTS_INCL_SECT_ENRL = 'Y' SFRSTCR-where: OR STVRSTS_WITHDRAW_IND = 'Y') SFRSTCR-where: AND a.SFRSTCR_GRDE_DATE is NULL SFRSTCR-where: AND # a.SFRSTCR_PIDM = <students-pidm>


Native Integrated Interface for Oracle PeopleSoft 1. Oracle PeopleSoft Customers only (DW4.0.8 1-DF8AGJ): Modify your

$ADMIN_HOME/common/ValidationQuery.client.properties file to contain the following changes:

Add “ps_acad_car_tbl acadCarTbl” to the FROM clause for the UCX_STU356 and UCX_STU385 queries. The acad_career is required to be selected for each table because the composite ucx_keys contain the School code (acad_career). Here is the SGHE standard query to illustrate the required changes in red:

################################################### # Stu356 Grade Type Codes ValidationQuery.Stu356.client.from = \ FROM ps_grade_basis_tbl gradeBasisTbl, \ ps_acad_car_tbl acadCarTbl ValidationQuery.Stu356.client.where= \ WHERE gradeBasisTbl.setid = 'PSUNV' \ AND gradeBasisTbl.setid = acadCarTbl.institution \ AND gradeBasisTbl.grading_scheme = acadCarTbl.grading_scheme \ END-WHERE

################################################### # Stu385 - Grade Codes ValidationQuery.Stu385.client.from = \ FROM ps_grade_tbl gradeTbl, \ ps_acad_car_tbl acadCarTbl ValidationQuery.Stu385.client.where= \ WHERE gradeTbl.setid = 'PSUNV' \ AND gradeTbl.setid = acadCarTbl.institution \ AND gradeTbl.grading_scheme = acadCarTbl.grading_scheme \ END-WHERE

2. Oracle PeopleSoft Customers only (DW4.0.8 1-ETN64J): Modify your

$ADMIN_HOME/common/Capture.ops.properties file and add the following entry:

capture.ops.JointProgApprUsed=Y

If the Joint Program/Degree logic defined in the R032GOAL and R033GDTA records is desired set the flag to Y. Note that this line must be added to Capture.ops.properties even if the Joint Program/Degree logic is not needed; if that is the case then set the value to N.


Luminis DW4.0.2 Banner customers utilizing the new enhancement to display the student’s DegreeWorks audit through the portal should review the Luminis CPIP Inline Channel section of the DGW_Technical_Guide_Banner_Considerations. (DW4.0.2 1-515JU1)

Workflow For sites using Workflow with the DW4.0.2 release:

Copy all of these .jar files from the Banner Workflow server to the DegreeWorks server location: $DWJAVA_LIB/lib.

$WFHOME/axis/axis-ant.jar $WFHOME/axis/axis.jar $WFHOME/axis/commons-discovery-0.2.jar $WFHOME/axis/jaxrpc.jar $WFHOME/axis/saaj.jar $WFHOME/axis/wsdl4j-1.5.1.jar $WFHOME/jaf/activation.jar $WFHOME/javamail/mail.jar $WFHOME/workflow/workflow.jar

These two jar files are also required but should already be in place for FOP and DdlUtils: commons-logging.jar and xercesImpl.jar. Review the $DWJAVA_LIB/lib to ensure these files are in place. If not, review the Release Guide for information on where to acquire the jar files, along with the version requirements. Download the commons-cli-1.1.jar file from Apache. Place this jar file in the $DWJAVA_LIB/lib directory as well. The specific installation instructions for Workflow components can be found in the Banner Considerations documentation. Please review and follow the instructions if your site wishes to take advantage of this functionality. (DW4.0.2 1-4POJ9Z, 1-4SFMAH)

3rd party reporting Review the database changes for DW4.0.7, outlined in the Release Guide. Update 3rd party reports to use the new structure. (DW4.0.7)


Other Server Changes 1. MinClasses and MinCredits are now supported on a rule (course rule, subset and group). Customers

should review the Reserved Word section of DGW_User_Guide_Scribe documentation for more information about these changes and/or additions. (DW4.0.1 1-45HEUB)

2. The auditor now processes block header qualifiers in the order they appear in the requirement block,

instead of the undocumented order currently used by the auditor. Customers may reorder their block header qualifiers to accommodate the new ordering logic. In general, customers should list the most specific MAX qualifiers first, so those classes will be removed from consideration when the more general qualifiers are processed. For example, "MaxClasses 1 in @ (With Attribute=HEALTH)" should come before "MaxClasses 10 in PE @" - this way all but one of the HEALTH classes will be whittled down and not considered when it gets to the more general qualifier. (DW4.0.1 1-49FLS5)

3. A new Transit AUD001 report generates information about unenforced and unhooked exceptions. Run

audits on all students to generate the data used by the AUD001 report, then run the AUD001 report and review. (Optional) (DW4.0.2 1-3VDPSE)

4. A new variable in the dwenv.config file controls whether support for LDAP authentication is enabled at compile (build) time. The new variable is DWLDAP. Set DWLDAP=0 to disable LDAP authentication. To enable LDAP, verify that OpenLDAP is installed on the host system and set DWLDAP=1 in dwenv.config before running the build all. (DW4.0.2 1-4L1AHN)

5. The standard fopaudit.xsl and fopaudits-dw.xsl in the app/xsl directory have been updated with DW4.0.2.

Clients must copy the files in the app/xsl directory to the local/xsl directory. If your site has customized these files in the local/xsl directory, please make the following changes:

Change the seven “D20AuditTitleStyle” references to “CFG020AuditTitleStyle” Change the three “D20MaskStudent” references to “CFG020MaskStudent”

(DW4.0.2 1-4PMPNP) 6. Review and update any saved Transit files (.trn) that query off the “DEG:” or “SCH:” criteria. The saved

selection will need to query off the new goal_dtl and goaldata_dtl selection criteria options. (DW4.0.2 1-3TSEQO)

7. A new script has been created: $DGWHOME/scripts/dropdegrees. It may be used to delete the old

rad_degree_dtl and rad_school_dtl data after a thorough comparison of the new rad_goal_dtl and rad_goaldata_dtl with the old rad_degree_dtls and rad_school_dtls has been completed. However, do NOT drop these two tables. They must still remain in the RAD database because of backwards compatibility issues. (DW4.0.2 1-3TSEQO)

8. If multiple exceptions are applied to the same rule and are not showing correctly in the web worksheet,

customers will need to run a new audit in order for the worksheet to properly display the exception data. Running new audits on all students is recommended if customers want to be sure this problem is resolved for everyone. (DW4.0.4 1-5O7UYB)

9. A new flag has been added to UCX-CFG020 DAP14 to allow failed classes that could have applied to an

OTHER block to be included in the OTHER block's GPA. If customers set this flag to “Y”, running new audits on all students will enforce the new GPA setting. (DW4.0.4 1-5RSCHA)

10. MEP clients can use the “newenv” function to switch from one environment to another.

(DW4.0.4 1-76443R)


11. Running the bannerextract or the Bridge in delete-id mode now deletes the rad_student_mst records.

During the time the rad_student_mst records were not deleted, some students may have the same srn_id value. Run the “deleteproblem” script to clean up the data:

Run the sql file in sqlplus from the app/sql directory: $ db > @deleteproblem

Use the generated deletestudents.sql file to create a list of students who need to be deleted: $ db > @deletestudents

Use the generated deletestudents.ids file against the bridge to delete these students: $ bannerextract deleteid deletestudents.ids

Note: Clients may see errors in the rad30 log file created in the dgwspool directory - these will be constraint errors not being able to delete the rad_student_mst for some of the students in this file. Clients can run the same bannerextract against this same list of students to clean those up:

$ bannerextract deleteid deletestudents.ids

The duplicate data should now be deleted. Clients should rebridge those students that were deleted. $ bannerextract students deletestudents.ids

(DW4.0.4 1-5XLANJ)

12. TreQ clients implementing WebTreQer in Flex will need to localize the following files in addition to UCX

configuration: /webtreqer/WEB-INF/classes/classicConnector.properties /webtreqer/WEB-INF/classes/jdbc.properties /webtreqer/flex/ChannelsConfiguration.xml For more information, review the “Configuring WebTreQer” topic in the TreQ User Guide. (DW4.0.4 1-5XF43R)

13. The standard fopaudit*.xsl in the app/xsl directory have been updated with DW4.0.5. These changes

relate to the tStudentHeader template, when pulling data off of the Deginfo xml tree. Clients must copy the files in the app/xsl directory to the local/xsl directory. If your site has customized these files in the local/xsl directory, please make the following changes:

Change references: Major<xsl:if test="count(/Report/Audit/Deginfo/Goal[@Code='MAJOR'])>1">s</xsl:if> to Major<xsl:if test="count(Deginfo/Goal[@Code='MAJOR'])>1">s</xsl:if>

(DW4.0.5 1-8BSC37)

14. Customers using “CopyRulesFrom” in any block will need to run DAP16 from Transit to reparse all blocks, so Remarks are now associated with the correct rules. (DW4.0.5 1-8KKT1P )


15. The standard fopaudit.xsl in the app/xsl directory has been updated with DW4.0.6. Changes were made to

the section where the Rules are called from a call-template. Clients must copy the file in the app/xsl directory to the local/xsl directory. If your site has customized the file in the local/xsl directory, please integrate the changes in the standard version into your site’s custom version. (DW4.0.6 1-ACR893)

16. The IRISLink.cgi file was modified in the DW4.0.6 release and no longer contains site specific settings.

This will help ease the update burden in future releases by eliminating the most commonly changed items from this file. The site specific settings (web08 port number and server name) were moved to a perl module called CgiSettings.pm. The location of the CgiSettings.pm file can reside anywhere on your web server, and its location must be configured in the new CgiSettingsDir.pm file. Follow these steps to configure these new files appropriately: (DW4.0.6 1-AK9L0V)

a. Note the current $DEF_PORTNUMBER and $DEF_SERVER_NAME from your current

IRISLink.cgi. It will be overwritten with a new version. b. Copy CgiSettings.pm from updates/webserver to your web server and place it in a directory that is

not under the webserver root (i.e. in a directory other than where IRISLink.cgi resides). If your web server resides on your DegreeWorks application server, copy CgiSettings.pm to your $LOCAL_HOME/perl_libs directory. If perl_libs does not exist under your $LOCAL_HOME directory you must create it, and change its permissions: chmod o+rx perl_libs.

c. Configure CgiSettings.pm and set the $DEF_PORTNUMBER and $DEF_SERVER_NAME variables with the values from your old IRISLink.cgi.

d. Copy CgiSettingsDir.pm from updates/webserver to your web server directory where IRISLink.cgi resides. Configure CgiSettingsDir.pm to point to the location of the CgiSettings.pm file.

e. Change permissions of CgiSettings.pm and CgiSettingsDir.pm so they are executable. Be sure to place a copy of the CgiSettings.pm file in your $LOCAL_HOME/perl_libs directory on your DegreeWorks application server even if your web server is on a separate server. You may need to create the perl_libs directory under $LOCAL_HOME if one does not already exist.

17. The standard fopaudit*.xsl in the app/xsl directory has been updated with DW4.0.7. Clients must review

and integrate the app/xsl changes to the local/xsl file. Additionally, copy the new file $DGWHOME/xsl/fopaudits-athl.xsl to local/xsl. (DW4.0.7 1-7EPX6W, 1-BESITN, 1-BF3MTF)

18. If you are running DegreeWorks on a 64-bit machine you may now enable DegreeWorks to run in

64-bit mode. Edit your $DGWBASE/dwenv.config file and add this flag to enable 64-bit mode:

export DW64BIT_ENABLED=1

Log out and in again to source this change in your environment. You must make this change to dwenv.config before beginning the DW4.0.8 update. Note that when switching from 32-bit to 64-bit any pre-existing audits will be lost as they cannot be understood by the software compiled in 64-bit mode. If you wish to continue you should delete all old audits - see the dapdelaudits script in the Technical Guide to see how to delete by create date. DAP16 must be run from Transit to reparse all requirement blocks before attempting to generate new audits in 64-bit mode. Alternatively, you may run dap16all from the command line to reparse all requirement blocks in 64-bit mode. (DW4.0.8 RPE 1-ELE7JL)


5 Sample Reports

Sample Reports The processing of Sample Reports is optional for all customers. Sample Reports have been updated in DW4.0.2 for the new rad_goal_dtl and rad_goaldata_dtl structure, and a new sample financial aid eligibility report has been added in DW4.0.4. Step-by-step installation instructions for Crystal and Discoverer can be found in the DW4.0.0 Installation Guide. The sample DegreeWorks Crystal Reports query the RAD and DAP tables, and in addition, they query specific views SunGard Higher Education has defined. These updated sample reports can be found in the SampleRpts_DW404.zip on the Customer Support Center.

Sample Crystal Reports Step one for installing DegreeWorks Crystal Reports: you must define these views in the Oracle database. This step is done with the installation script. Step two is modifying the datasource location for each sample report. Step-by-step installation instructions for Sample Crystal Reports can be found in the DW4.0.0 Installation Guide.

Sample Oracle Discoverer Reports Before you can use the Oracle Discoverer Reports, your system administrator must first set up the End User Layer (EUL) in your Oracle database. The DegreeWorks database tables must be included in the EUL. This also includes the DegreeWorks Curriculum Planning Assistant Oracle Views. The next step is to create the necessary joins in your EUL. Your system administrator must use the Oracle Discoverer Administrator tool to set these up. After the joins are defined, you can run the report by opening it in Oracle Discoverer Desktop. Step-by-step installation instructions for Sample Oracle Discoverer Reports can be found in the DW4.0.0 Installation Guide.

degreeworks installation guide - my.bridgew.edu · degreeworks. installation guide. december 2010 ....

Documents