Sie sind auf Seite 1von 18

Banner Human Resources

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

Step Description and Dependencies Table ............................................................................................ 3


Step 1 Distribute Release Documents ..................................................................................... 4

Step 2 Verify Environment Prerequisites ................................................................................. 4

Step 3 Installation/Upgrade Prerequisites and Preparation ..................................................... 6


Part A Prerequisites;.................................................................................................. 6
Part B Additional Prerequisites for Multilingual Systems .......................................... 6
Part C Installation sequence .................................................................................... 6
Part D Create required directory structure ................................................................ 7

Step 4 Modify Database Objects ............................................................................................. 9


Part A ............................................................................................................................ 9

Step 5 Migrate from Stage to Permanent Directories ............................................................ 10


Part A .......................................................................................................................... 10

Step 6 Compile Cobol Programs ........................................................................................... 12


UNIX ........................................................................................................................... 13
MICROSOFT WINDOWS ........................................................................................... 13

Step 7 Compile C Resources................................................................................................. 13

Step 8 Generate Oracle Forms .............................................................................................. 16

Step 9 Update INB Menus ..................................................................................................... 16

Step 10 Update Online Help .................................................................................................... 16

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 2
RELEASE 8.15.1

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.

Step Description and Dependencies Table


The following list of steps is consistent from release to release. Any steps that are not required are marked N/A in the
"Applies to this Stage" column in this table.

Step Applies Description Dependent


to this on Step
upgrade
1 Distribute Release Documents —
2 Verify Environment Prerequisites Previous
3 Installation/Upgrade Prerequisites and Previous
Preparation
4 Modify Database Objects Previous
5 Migrate from stage to permanent directories Previous
6 Compile Cobol Programs 5
7 Compile C Resources 5
8 NA Generate Oracle Forms 5
9 Update INB Menus Previous
10 Update Online Help Previous

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 3
RELEASE 8.15.1

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

(SQL, SHL, PL and, BAT files)

Step 1 Distribute Release Documents


Distribute the enclosed Readme found in the doc subdirectory, to the appropriate departments. This
document explains the modifications that have been made to the system in functional terms and explains
actions that must be taken by the users in preparation for or as part of the release upgrade.

Do not proceed until the responsible users indicate that any current processes or cycles have completed and
will not be affected by the upgrade.

Step 2 Verify Environment Prerequisites

Part A This upgrade requires a minimum of Oracle Database Release 11.1.0.7.0.

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).

COMPLETE BACKUPS OF YOUR EXISTING SYSTEM BEFORE CONTINUING!


Make sure Oracle is down when the backup is taken. This ensures a consistent backup. Verify that all
database files, redo logs, and control files have been successfully backed up.

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.

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 4
RELEASE 8.15.1

For all platforms set SQLPATH equal to ORACLE_PATH.

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.

ATTENTION: In order to comply with USA Federal Audit Standard GAO-09-


232G, ALL Ellucian releases, effective September, 2011,
A NOTE will no longer deliver code with clear text passwords.
REGARDING
DELIVERED This affects the delivered file login.sql as well as C and
ELLUCIAN COBOL compile scripts and form generate scripts for the
CODE AND UNIX and Windows environments.
CLEAR TEXT
PASSWORDS You will now be responsible for editing the delivered
login.sql script for every upgrade and replacing the
string “#UPDATEME#” with whatever value the particular
schema owner’s password is in your environment. You will
be required to do this for all Banner schema owners that
exist in your particular environment.

The compile scripts (C/ COBOL/ form generate scripts/


report generate scripts) in the upgrade, for all supported
platforms, have been modified to include environment
variables that need to be defined at your site in order to
successfully compile/generate the Ellucian delivered
objects.

For the UNIX/LINUX environment, issue the following


command:

export DFLT_BANINST1_PASS=the_value_of_baninst1_password;

For the Windows environment issue the following command:

SET DFLT_BANINST1_PASS=the_value_of_baninst1_password

The delivered generate and compile scripts will expect


these environment variables to be present in your
environment, defined and available to be used at the
appropriate times.

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 5
RELEASE 8.15.1

Step 3 Installation/Upgrade Prerequisites and Preparation


Banner Human Resources 8.15.1 ESMX is an upgrade release of the ESMX code including forms, TMMs,
forms, resources, cobol files and/or table data translations. Follow the steps described below to upgrade an
existing Banner Human Resources 8.15 ESMX or later installation to Banner Human Resources 8.15.1
ESMX.

Part A Prerequisites;

For more information, refer to the ‘Banner_IntPatch_Releases_Interdependencies’ and


‘Banner_Spanish_Releases_Interdependencies’ documents.

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”.

Part B Additional Prerequisites for Multilingual Systems

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.

CAUTION: Beware that customized code might be overwritten by this installation.

Part C Installation sequence


The upgrade of a UNILINGUAL Banner INB system as of ESMX 8.2 consists of four main steps.

1. Apply Banner upgrades

2. Apply SCB upgrade (not required for all upgrades)

3. Apply Banner International Patches (if your ESMX release contains c resources)

4. Apply ESMX upgrades.

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 6
RELEASE 8.15.1

When upgrading several products, the usual order applies:

Seq. No. Banner Product


1. General
2. Student
3. Accounts Receivable
4. Advancement
5. Finance
6. Human Resources
7. Position Control
8. Web Tailor
9. Web for General
10. Student Self-Service
11. Faculty and Advisor Self-Service
12. Advancement Self-Service
13. Employee Self-Service
14. Finance Self-Service
15. Luminis Channels for Banner

Part D Create required directory structure

In this step you will create the required directory structure for all Banner ESMX products.

The ESMX scripts migrate into separate install sub-directories of $BANNER_HOME/esmx.

Example for ESMX General INB:

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 7
RELEASE 8.15.1

$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

Other INB products require a similar structure.

Example for ESMX General Self-Service:

$BANNER_HOME/esmx/genweb/

$BANNER_HOME/esmx/genweb/data

Other Self-Service products use the same structure.

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.

In addition, the following directory is required:

$BANNER_HOME/esmx/nls/data

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 8
RELEASE 8.15.1

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:

FOR UNIX: mkdir $BANNER_HOME/esmx/«prodname»/forms E nter

FOR MICROSOFT WINDOWS:


mkdir drive_letter\banner_home_directory\esmx\«prodname»\forms E nter

Step 4 Modify Database Objects

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.

FOR MICROSOFT WINDOWS:


If performing the install from a MS windows environment, ensure that the sqlplus 'Start In' directory is set
to the location on your server of the new sql sub-directory.

The installation will be executed against your default database as set with LOCAL (Windows) or
TWO_TASK (Unix).

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 9
RELEASE 8.15.1

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.

Do not proceed until the necessary edits have been finished.

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:

sqlplus /nolog @pay81501u_esmx.sql E nter

The installation will be spooled to the file pay81501u_esmx.lst.


Review this file for any errors to determine the install has been
successful before moving on to the next product.

Step 5 Migrate from Stage to Permanent Directories

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.

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 10
RELEASE 8.15.1

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

2. Position to the staging directory for this product.

3. Run the migration script by typing:

sh pay81501u_esmxmigr.shl >pay81501u_esmxmigr.log 2>&1 & 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

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 11
RELEASE 8.15.1

If BANENV has a value of ENV, the value for BANNER_HOME will be taken from the environment
variable BANNER_HOME.

Review the script for correct directory path names.

To run the migration script and produce an error log for the migration, do the following:

1. Position to the staging directory for this product.

2. Run the migration script by typing:

perl pay81501u_esmxmigr.pl >pay81501u_esmxmigr.log 2>&1 E nter

Review: pay81501u_esmxmigr.log
This file contains the results of the migration.

Step 6 Compile Cobol Programs

In this step you will compile any affected COBOL programs.

For ESMX cobol compilation use the following settings:

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.

Do not proceed until the necessary edits have been finished.

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 12
RELEASE 8.15.1

UNIX

1. Position yourself in the stage directory.

2. If your operating system prompt is a percent sign, you are a cshell user. Enter the Bourne shell by
typing:
sh Enter

3. Start the compiles by typing:


sh paycmpl.shl > paycmpl.log 2>&1 & 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

1. Position yourself in the stage directory.

2. Start the compiles by typing:


perl paycmpl.pl > paycmpl.log 2>&1 Enter

Review: paycmpl.log
This file contains the results of the compilation.

Step 7 Compile C Resources


The Root resources for C and Pro*C objects are delivered as part of the Banner International Patches.
Translated versions of Banner C and Pro*C use the ICU resource bundle mechanism to look up translations
for messages.

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

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 13
RELEASE 8.15.1

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

The directory and file structure will be setup as follows:

$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

Script to generate Resource bundle files for a file or directory

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 14
RELEASE 8.15.1

Usage genres version 1.1:

genres BuildTarget [sourcedir [targetdir]]

where BuildTarget is ALL, UPDATE, CLEAN or the C file name like gjrrpts.pc

sourcedir and targetdir default to current directory

Locales that will be generated: root en es fr ar .

Set extra locales using e.g. export locales="nl nl_NL"

before executing this script.

Optional Environment Variables to change behavior

TM_BUNDLE_DEBUG=Y to show which bundle is generated

GENRBOPT=... options to pass to genrb like -v for verbose

To compile and deploy a directory with resource files:

1. Ftp, copy or link all resource .txt files to $BANNER_RES

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

3. cd to the folder where your text resources are located

$ cd $BANNER_RES

4. generate all resource files

$ genres ALL

5. (alternatively you can use $ genres UPDATE to only compile .txt files that are newer than the
corresponding .res file)

Check for errors and warnings.

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:

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 15
RELEASE 8.15.1

$ cd $BANNER_HOME/esmx
$ genres_all ALL

It is also possible to compile per product and language (locale):

$ genres ALL $BANNER_HOME/general/resources $BANNER_RES

$ genres ALL $BANNER_HOME/esmx/general/resources $BANNER_RES

You can use UPDATE instead of ALL if you do not want to touch unchanged resource files.

Step 8 Generate Oracle Forms


This step does not apply to this upgrade.

Step 9 Update INB Menus


In this part you will update the INB menus after installing or updating translations.

To update menus, invoke SQL*Plus and run the procedure:

sql_cmd baninst1/baninst1_password E nter

start gurrhmu E nter

Step 10 Update Online Help


If updated online help files for your language are included in this release, refer to the installation
instructions provided in the “howtoinstallinterimOH_esmx.txt” file contained in the
Banner_Payroll_Online_Help_8.15_esmx.zip file, which you will find in pay81501u_esmx directory
(where applicable).

This Banner Human Resources 8.15.1 ESMX Upgrade is now complete

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 16
RELEASE 8.15.1

Ellucian
2003 Edmund Halley Drive
Reston, VA 20191
United States of America
www.ellucian.com

JANUARY 2019 BANNER HUMAN RESOURCES 8.15.1 ESMX


UPGRADE GUIDE 17

Das könnte Ihnen auch gefallen