Beruflich Dokumente
Kultur Dokumente
Spanish (ESMX)
Upgrade Guide
Release 8.15.1
January 2019
© 2019 Ellucian.
Contains confidential and proprietary information of Ellucian and its subsidiaries. Use of these materials is
limited to Ellucian licensees and is subject to the terms and conditions of one or more written license
agreements between Ellucian and the licensee in question.
In preparing and providing this publication, Ellucian is not rendering legal, accounting, or other similar
professional services. Ellucian makes no claims that an institution's use of this publication or the software for
which it is provided will guarantee 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.
Ellucian
2003 Edmund Halley Drive
Reston, VA 20191
United States of America
Publication Summary
Date
January 2019 New version that supports Banner Human Resources 8.15.1 ESMX software.
RELEASE 8.15.1
Table of Contents
Overview ................................................................................................................................................. 3
Overview
The Banner Human Resources 8.15.1 Spanish (ESMX) release delivers the Spanish translation of the Banner Human
Resources 8.15.1 upgrade as well as a full install of the Spanish translations of dbprocs, c reports and table data for
Banner Human Resources 8.x to support Banner Human Resources 9.x.
This document describes the steps required to perform an upgrade of Banner Human Resources 8.15 ESMX or later to
version 8.15.1. It is designed to be used in conjunction with the ‘Banner_IntPatch_Releases_Interdependencies’ and
‘Banner_Spanish_Releases_Interdependencies’ documents which are available for download from the Ellucian
Customer Support Center at http://www.ellucian.com/Solutions/Ellucian-Client-Support/
The ‘Banner_IntPatch_Releases_Interdependencies’ document outlines the release interdependencies for all Banner,
SCB, International Patch releases within the Digital Campus (DC). The ‘Banner_Spanish_Releases_Interdependencies’
document outlines the release interdependencies for Spanish language releases within the Digital Campus (DC). Before
you install or upgrade a product within the DC, use this document to determine which other DC products you must
install first.
NOTE:
The "Some translation releases are not supported via ESM for Windows clients" Article 000042576
is available via the Ellucian Support Center (http://www.ellucian.com/Solutions/Ellucian-Client-
Support/). It is necessary that you check this document prior to applying the release by querying
for Article 000042576.
If any errors or problems occur during the upgrade process, login to the Ellucian Customer Support Center at
http://www.ellucian.com/Solutions/Ellucian-Client-Support/ to search for solutions or to submit a case for assistance
with the issue.
Read All Instructions Before Beginning; Review the Contents of All Scripts
Do not proceed until the responsible users indicate that any current processes or cycles have completed and
will not be affected by the upgrade.
In order to maintain technical currency, for Banner Human Resources 8.15.1 Oracle 10g is no longer
supported. It is required that you upgrade to Oracle 11gR1 in order to use this release of Banner Human
Resources and take advantage of the functionality and the continuity it provides across Banner Digital
Campus.
“Article 1-AUTYZE - Oracle 11G Database and Application Server” can be referenced for additional
details.
For more information on 11G database requirements, refer to the Banner General release documentation.
Be sure all Oracle users are logged off and cannot or will not log on. SCB installation scripts only
require DBA for BANINST1. BANINST1 will grant DBA to &UPGRADE_OWNER who is used to
do the installation. The DBA role is revoked from &UPGRADE_OWNER if installation finishes OK
(granted/revoked for each product upgrade).
Part B Apply this upgrade to your SEED instance first. Never apply it to production without familiarizing yourself
with the process by executing it against a non-critical database. This stage must be applied to all of your
Banner «product» ESMX environments.
If you are running under UNIX, be sure that the current directory (represented by a ".") is at the front of
your ORACLE_PATH, SQLPATH and UNIX path to avoid any problems when starting some of the
upgrade SQL scripts and shells.
If you are running under MICROSOFT WINDOWS, be sure that the plus subdirectory of every Banner
product you license has been added to the
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\SQLPATH registry entry and/or the SQLPATH
environment variable to avoid any problems when starting the upgrade SQL scripts. Please also note that
the commands you use to import files and to start SQL*Plus will depend on the version of Oracle Server
you are using. To perform an upgrade on the MICROSOFT WINDOWS platform, you must open up an
MS-DOS window and execute all commands from the MS-DOS command prompt.
export DFLT_BANINST1_PASS=the_value_of_baninst1_password;
SET DFLT_BANINST1_PASS=the_value_of_baninst1_password
Part A Prerequisites;
NOTE: All Banner language systems require Banner General 8.7.5 and in addition
multilingual Banner language systems require SCB 8.4.
Any modifications you have made to the base product will remain your responsibility. Each object that
has been modified contains descriptive text about the purpose of the modification. This text can be
found at the beginning of each object, except for forms, for which the comments are found in Form
level procedures named AUDIT_TRAIL_”release_number”.
Any new installation or upgrade of a multilingual system to Banner Human Resources 8.15.1 ESMX
requires SCB 8.4 to be installed and the installation path as explained in the SCB 8.2/8.4 documentation as
well as article 1-EULYEX to be followed.
Any modifications you have made to the base product will remain your responsibility.
3. Apply Banner International Patches (if your ESMX release contains c resources)
In this step you will create the required directory structure for all Banner ESMX products.
$BANNER_HOME/esmx/general
$BANNER_HOME/esmx/general/data
$BANNER_HOME/esmx/general/forms
$BANNER_HOME/esmx/general/resources
$BANNER_HOME/esmx/general/fmbdata
$BANNER_HOME/esmx/common
$BANNER_HOME/esmx/common/data
$BANNER_HOME/esmx/common/forms
$BANNER_HOME/esmx/common/resources
$BANNER_HOME/esmx/genweb/
$BANNER_HOME/esmx/genweb/data
Note that with support of the Cascade user interface as of version 8.3, a new subfolder “misc” under the
Web Tailor directory needs to present or else created as follows:
$BANNER_HOME/esmx/wtlweb/misc
The ESMX migration scripts will migrate translations for Cascade specific XML files into this
subdirectory.
$BANNER_HOME/esmx/nls/data
Finally, one links directory shared by all products needs to be in place (for UNIX):
$BANNER_HOME/esmx/links
Please verify that those sub-directories are present for all ESMX products that you want to install.
If you have questions on required folders and folder names, please consult the migration scripts for each
product for reference.
If this directory structure is not created in your environment yet, please create as follows:
Part A
CAUTION: The following installation steps will affect your existing installation. Please
make sure your system is backed up accordingly including all your
customizations. Customizations will need to be re-applied after the ESMX
installation is completed.
In this step you will install TMM files and run table scripts for Banner Human Resources 8.15.1 ESMX.
Changes that you have made to your existing installation may be affected by this process.
CAUTION: Make sure ALL prerequisites specified in the Overview and Installation
Requirements sections have been met before proceeding.
The installation will be executed against your default database as set with LOCAL (Windows) or
TWO_TASK (Unix).
CAUTION: Please make sure your SQL session is set to AL32UTF8 while installing the
message files, since the files were generated using AL32UTF8.
CAUTION: Before beginning this upgrade, please review Step 2 Part B for additional
instructions regarding establishment of environment variables and edits to
the file login.sql.
From the new install sub-directory, invoke SQL*Plus and connect as any user or use the nolog flag to
invoke SQL*Plus without connecting.
When you get an SQL*PLUS prompt, type in the name of the .sql file (incl. the @ sign) as follows:
Before executing any of the migration scripts make sure you are signed on to an
operating system account that has write permission into the target Banner ESMX
directories.
The migration scripts provided for the UNIX and MICROSOFT WINDOWS
platforms expect your directory structure to match the one created by the Banner
install process. You will have to modify the scripts if you chose a different directory
structure. Migration scripts for other platforms are not provided due to their highly
customized structures but you may use the pay81501u_esmxmigr.txt file as
a starting point for writing your own migration script.
Part A
In this step you will migrate the staged files to your permanent directories.
The file pay81501u_esmxmigr.txt lists all files that need to be deleted from your permanent
directories, and all files which should be copied from the staging directory to your permanent directories.
The destination is indicated in UNIX format, and will be different on other platforms.
UNIX
The file pay81501u_esmxmigr.shl will do the appropriate removes, copies, and links. Review for
correct directory path names and make sure that the environment variable $BANNER_HOME is set to the
appropriate directory before executing.
NOTE: The pay81501u_esmxmigr.shl file defines a local variable, LN, at the top of
the file which determines the type of links which should be used in the
migration. This change enables clients who wish to use symbolic links, for
example, to set LN=‘ln -s’ instead of the default value of ‘ln’ so that the
command ${LN} file $BANNER_HOME/links is translated to ln -s file
$BANNER_HOME/links. Similarly, clients who wish to force the removal of
any existing targets before linking files can set LN=‘ln -f’.
Note that even if your directory structure matches the baseline perfectly, some of the link commands will
fail (that is, where the link currently exists). Other link errors may indicate that you had two copies of an
object when the migration script was executed. This condition must be corrected. The duplication is
probably between links and the product subdirectory.
You may wish to run the migration shell in background so that you may review any errors when it is
complete. To submit into background and produce an error log, do the following:
1. If your operating system prompt is a percent sign, you are a cshell user. Enter the Bourne shell by
typing:
sh E nter
4. If you were a cshell user and want to return to that mode, press CTRL-D or type:
exit E nter
Review: pay81501u_esmxmigr.log
This file contains the results of the migration.
MICROSOFT WINDOWS
The file pay81501u_esmxmigr.pl will do the appropriate deletes and copies. Before running the migration
script, you must check the BANENV environment variable. This value may be determined by executing the
SET command from the DOS prompt.
If BANENV has a value of REG, the value used for BANNER_HOME will be taken from the registry
entry:
HKEY_LOCAL_MACHINE\SOFTWARE\BANNER\BANNER_HOME
If BANENV has a value of ENV, the value for BANNER_HOME will be taken from the environment
variable BANNER_HOME.
To run the migration script and produce an error log for the migration, do the following:
Review: pay81501u_esmxmigr.log
This file contains the results of the migration.
export BANNER_LINKS=$BANNER_HOME/esmx/links
Please verify that sctprocb.mk exists at $BANNER_HOME/esmx/links/ directory. If it does not exist,
please copy it from $BANNER_HOME/links/ to $BANNER_HOME/esmx/links/
The output from the baseline compile routine is placed into the defined environment variables like
$EXE_HOME directory on UNIX and the BANNER_EXE directory on WINDOWS. If your compile
routine has been modified to write into the current directory, the output will have to be migrated to
$EXE_HOME directory on UNIX and the BANNER_EXE directory WINDOWS on before it can be
accessed by the users.
This procedure must be run from an operating system account that has write
permission into the target directory.
CAUTION: Before beginning this upgrade, please review Step 2 Part B for additional
instructions regarding establishment of environment variables and edits to
the file login.sql.
UNIX
2. If your operating system prompt is a percent sign, you are a cshell user. Enter the Bourne shell by
typing:
sh Enter
4. If you were a cshell user and want to return to that mode, press CTRL-D or type:
exit Enter
Review: paycmpl.log
This file contains the results of the compilation.
MICROSOFT WINDOWS
Review: paycmpl.log
This file contains the results of the compilation.
For more information, refer to the International Patch C and Pro*C Resources Installation Information
document.
For source code files there can be a number of associated resource bundle files with message ID’s and
message strings. The resource bundle files come in two flavors, plain text files (*.txt) and binary files
(*.res). The binary .res files are created by compiling the .txt files with ICU tool genrb. It is assumed that
ICU is installed and that genrb can be located when executed in the shell. The default deploy method for
language systems will be to install .res files in a specific directory tree structure as described below. The
organization of the binary .res files has to be according to ICU rules.
The General Translation releases include script genres to simplify the set up of resource bundle files in
Unix or Linux like environments. No Microsoft Windows scripts are provided - Windows users can use
Cygwin or similar.
The genres script is located in directory ../general/misc. Please copy the script to your favorite scripts
directory and include this directory in your $PATH. The following instructions use Unix conventions for
environment variables and paths. Note that for other OSs it works the same, but conventions differ slightly.
The shell commands are written in courier and start with $ when directly entered in the shell.
The compiled resources for all IntPatch products will be installed in $BANNER_HOME/resources and an
environment variable is created to point to this location.
$ export BANNER_RES=$BANNER_HOME/resources
$ mkdir $BANNER_RES
At runtime this directory has to be included in $ICU_DATA. This has the same format as $PATH (multiple
directories separated by colon (:), the separator is OS dependent).
To set this up permanently you can include the following in the .profile for the OS user that execute the
jobs:
export BANNER_RES=$BANNER_HOME/resources
export ICU_DATA=$BANNER_RES:$ICU_DATA
$BANNER_RES/
Prog1.pc/
root.res
es.res
Prog2.pc/
root.res
es.res
This example tree contains only the root and Spanish resource files. Directory names end with a slash (/).
$BANNER_RES will contain a directory per C source file (.c, .cpp, .pc, .h). In this directory there will be
files <locale>.res. Because the names of the directories are the same as existing Banner files it is not
possible to link into the $BANNER_LINKS directory.
If genres is ‘installed’ as described you can enter genres without parameters to display a little help text:
$ genres
where BuildTarget is ALL, UPDATE, CLEAN or the C file name like gjrrpts.pc
2. Make sure all locales you wish to compile are listed when you execute genres without parameters,
follow instructions to add missing locales when needed
$ cd $BANNER_RES
$ genres ALL
5. (alternatively you can use $ genres UPDATE to only compile .txt files that are newer than the
corresponding .res file)
The steps describe the case that you have all resource .txt files in $BANNER_RES and also have this as the
root for the binary .res files.
Script genres_all has been included in scb/general/misc to traverse through all product directories in the
current directory and call genres if a directory resources exists in this product directory. The following is an
example of usage:
$ cd $BANNER_HOME/esmx
$ genres_all ALL
You can use UPDATE instead of ALL if you do not want to touch unchanged resource files.
Ellucian
2003 Edmund Halley Drive
Reston, VA 20191
United States of America
www.ellucian.com