banner general release guidebanner7.utm.edu/manuals/banner_release_guides/general80800rg.pdf ·...

Banner GeneralRelease Guide

Release 8.8September 2015

Banner®, Colleague®, PowerCampus™, and Luminis® are trademarks of Ellucian Company L.P. or its affiliates and are registered in the U.S. and other countries. Ellucian®, Ellucian Advance™, Ellucian Degree Works™, Ellucian Course Signals™, Ellucian SmartCall™, and Ellucian Recruiter™ are trademarks of Ellucian Company L.P. or its affiliates. Other names may be trademarks of their respective owners.

©2015 Ellucian Company L.P. and its affiliates.

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.

Prepared by: Ellucian4375 Fair Lakes CourtFairfax, Virginia 22033United States of America

Revision History

Publication Date Summary

September 2015 New version that supports Banner General 8.8 software.

Ba

Contents

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Cumulative documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Change request enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

CR-000128147 - Oracle*Wallet Proxy for Job Submission . . . . . . . . . . . . . . . . . . . 6

Modified tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Site profile record (GUBIPRF). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Audit table for site profile record (GURAIPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

New scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

DDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8DML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Modified scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

DBPROCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9PLUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9MISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10COBOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Java. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

CR-000128604 - Internationalization support for Unilingual Job Submission . . . 11

New tables and views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Report/Process Internationalization Status Table (GJBJOBI) . . . . . . . . . . . . . . . . . 11Translated text for specific primary keys table (NLS_LANG_TEXT) . . . . . . . . . . . . 12NLS session parameters during execution table (GJBPNLS) . . . . . . . . . . . . . . . . . 13Metadata for Banner NLS table (NLSVIEW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Language View of TM_NLS - Language Definition View (TM_NLS) . . . . . . . . . . . . 15Jobs Parameter Definition View (NLS_GJBPDEF) . . . . . . . . . . . . . . . . . . . . . . . . . 15Default Parameter View (NLS_GJBPDFT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Process Run Parameter View (NLS_GJBPRUN) . . . . . . . . . . . . . . . . . . . . . . . . . . 18General Jobs Parameter Value View (NLS_GJBPVAL) . . . . . . . . . . . . . . . . . . . . . 20

New objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Modified objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

GOASDMD security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3nner General Release Guide | Contents

Ba

Appendix A - Oracle*Wallet Proxy for Job Submission Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Single instance setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Create wallet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Step 1. Create directory to store wallet files. . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Step 2. Create wallet in the new directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Step 3. Check wallet files were created correctly. . . . . . . . . . . . . . . . . . . . . . . . 25

tnsnames.ora and sqlnet.ora setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Step 1. Copy tnsnames.ora and sqlnet.ora to a new location . . . . . . . . . . . . . . 25Step 2. Modify tnsnames.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Step 3. Modify sqlnet.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Store credentials in wallet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Step 1. Create proxy user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Step 2. Store proxy user's credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Step 3. Test wallet credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

RAC setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Create wallet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Step 1. Create directory to store wallet files. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Step 2. Create wallet in the new directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Step 3. Check wallet files were created correctly. . . . . . . . . . . . . . . . . . . . . . . . 29

tnsnames.ora and sqlnet.ora setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Step 1. Copy tnsnames.ora and sqlnet.ora to a new location . . . . . . . . . . . . . . 30Step 2. Modify tnsnames.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Step 3. Modify sqlnet.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Store credentials in wallet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Step 1. Create proxy user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Step 2. Store proxy user's credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Step 3. Test wallet credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Enable Job Submission Proxy Wallet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Step 1. Edit GURJOBS driver shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Notes about Batch Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4nner General Release Guide | Contents

Ba

Introduction

This release guide documents release 8.8 of Banner® General. This release is a cumulative rollup of all releases and patches delivered since the Banner General 8.7 release.

Cumulative documentation

This document provides detailed information about the Banner General 8.8 release only. Banner General 8.8 is a cumulative release that also includes enhancements and change request resolutions delivered in the Banner General releases since 8.7. For complete documentation about these interim releases, please refer to the release guides identified in the table that follows.

Release Number Contents Release Date

8.7.1 VETS-100 Reporting Updates September 2014

8.7.2 Delivery of new tables and procedures to support Banner RESTful APIs for Elevate Integration and Migrate Banner Event Management 9.x related Database changes to Banner General DB

December 2014

8.7.3 Enhanced Job Submission January 2015

8.7.4 Delivery of new tables and procedures to support Banner Communication Management

February 2015

8.7.5 National Language Support (NLS) April 2015

5nner General Release Guide | Introduction

Ba

Change request enhancements

This document describes the following enhancements, which are new for release 8.8.

• CR-000128147 - Oracle*Wallet Proxy for Job Submission

• CR-000128604 - Internationalization support for Unilingual Job Submission

CR-000128147 - Oracle*Wallet Proxy for Job Submission

Banner General 8.8 delivers a modification to the Job Submission process. This modification supports communicating with Job Submission through a proxy user with an Oracle*Wallet supporting configuration (see Appendix A - Oracle*Wallet Proxy for Job Submission Configuration Information for more information) on the Job Submission server. Essentially, this modification supports running batch jobs without requiring to pass the user’s password value to the Job Submission server.

Note: When a user is connected to the Banner Transformed application, that user is commonly connected via a proxy connection. The user's password will not be known in order to pass it to the Job Submission server. For that reason, Banner Transformation requires General 8.8 Oracle*Wallet Proxy for Job Submission to be installed and configured.

In support of the Banner Oracle*Wallet Proxy for Job Submission enhancement, modifications were made in the section of COBOL programs that connect to the database. These COBOL modifications are required if you are implementing the Oracle*Wallet Proxy for Job Submission functionality.

These COBOL modifications can be found in the following releases/patches:

With the Banner Oracle*Wallet Proxy for Job Submission modification, the BANSECR.GUBIPRF.GUBIPRF_JS_PRXY_ENFORCED column is being provided. If a

Product Release/Patch

Accounts Receivable pcr-000125284_tas8050004

Financial Aid 8.23.1

General 8.8

Human Resources pcr-000129464_pay8110405

Student 8.8.4.1

6nner General Release Guide | Change request enhancements

Ba

Job Submission administrator sets this column to Y, then a userid must be granted connection through user BANJSPROXY in order to submit a job. Otherwise, the user receives the following error:

*ERROR* Job Submission Proxy enforced and User ID not granted proxy access. Job not submitted.

If a user has been granted connection through BANJSPROXY, his/her userid must be less than 29 characters. Otherwise, the user receives the following error:

*ERROR* Job Submission Proxy in use. Length of User ID must be less than 29 characters. Job not submitted.

Modified tables

The following tables were modified for this release.

Site profile record (GUBIPRF)

Two new columns have been added to the GUBIPRF table.

Audit table for site profile record (GURAIPF)

Two new columns have been added to the GURAIPF table.

Column Name Null? Type Description

GUBIPRF_JS_PRXY_SID

NULL VARCHAR2(30) User provisioning for user BANJSPROXY located in Oracle wallet.

GUBIPRF_JS_PRXY_ENFORCED

NULL VARCHAR2(01) Indicator that determines if the use of BANJSPROXY is being enforced by the system.


GURAIPF_JS_PRXY_SID NULL VARCHAR2 (30) JOBSUB PROXY SID: User provisioning for the user BANJSPROXY located in oracle wallet.


Ba

New scripts

The following scripts are new for this release.

DDL

DML

Modified scripts

The following scripts are modified for this release.

GURAIPF_JS_PRXY_ENFORCED

NULL VARCHAR2(1) JOBSUB PROXY ENFORCED: Indicator that determines if the use of BANJSPROXY is being enforced by the system.

Script Description

gubiprf_080800_01.sql

This script delivers both columns null.

gubiprf_080800_02.sql

This script comments on the new columns.

guraipf_080800_01.sql

This script creates the two new columns in the audit table.

guraipf_080800_02.sql

This script comments on the new columns.

Script Description

gurusrpi_080800.sql This script inserts a row into GURUSRP to restrict access to BANJSPROXY.


Ba

DBPROCS

PLUS

Forms

Package Description

gspsecr.sql This package has been modified to add new functions used by the Oracle*Wallet Proxy for Job Submission modification.

goknosl1.sql Nosleep modifications to recognize if Oracle* Wallet Proxy for Job Submission is being enforced.

gutiprf0.sql This trigger was modified to support the auditing of the two new columns added to the GUBIPRF table.

Script Description

gcreate_banjsproxy.sql

This script creates the BANJSPROXY user ID.

gchkjobsubproxy.sql Helper script to look at GJRINVC to make sure that characters [ and ] are not being suppressed.

gbanjsproxy_users.sql

This script is used to create another script that when run will give all the non-schema owners privileges to connect through BANJSPROXY.

Form Description

guainit.fmb New logic was added to this form. At the start of each new Banner session, the form's new triggers populate the three new global values representing the proxy SID, the user's proxy authorization, and whether the proxy is enforced or not.

guqintf.fmb This form has logic added to it to check the three new global values and manipulate the username and password based on those values. The form puts the username in brackets and uses the proxy SID instead of the password when the wallet is indicated, or runs the job normally if the wallet is not indicated. When the wallet is not indicated, the proxy is not enforced, or it throws an error if it is enforced according to the setting on GSASECR - Institutional Profile tab.


Ba

MISC

• gorsrin.shl

• jsm2gorblob.shl

• gorsrin.pll

• jsm2gorblob.pm

COBOL

• GLBDATA.pco

• GLBLSEL.pco

• GLBPARM.pco

• GLOLETT.pco

• GUAVRFY.pco

C

• guaorac2.pc

• gurinso.pc

Java

• gurjbif.jar

gsasecr.fmb This form has been updated to include the Authorize BANJSPROXY check box on the Alter or Create an ORACLE User ID block of the Users tab. Also, the Proxy Job submission SID text field and Enforce Job Submission Proxy check box have been added to the Institution Profile tab.

gsaaudt.fmb This form has been updated to include the changes that appear in GSASECR. The Enforce Job Submission Proxy check box and Proxy Job Submission SID field have been included in the audit entries under the Institution Profile tab.

Form Description


Ba

CR-000128604 - Internationalization support for Unilingual Job Submission

Banner General 8.8 release delivers some of the objects and database changes required for future language support as part of Banner baseline. Additional changes for full implementation of language support will be delivered in future releases.

Banner General 8.8 release delivers database objects to support Unilingual Job Submission in any of the currently supported languages, instead of only AMERICAN.AMERICA. This enables users to enter job submission input parameters in their native language (i.e. 1,23 instead of 1.23) and the subsequent usage by the batch processes. These objects were previously only delivered by the Solution Centers, but are now being baselined and will replace those objects being used by non-US clients.

At this point in time, the functionality for all clients remains the same. Future releases will continue to baseline additional components of language support until full language support is available for all clients.

Note: Several changes are being made associated with NLS (CR-000128604) and specifically the changes for access to GJBPDFT, GJBPDEF, GJBPVAL, and GJBPRUN are being changed from tables to views. If you have any local processes that are directly using any of those tables, you may need to grant access to the new views if they are in a different schema than BANINST1, FLEXREG, or TAISUSR. Without the proper grants, your packages will not compile. Please see the general/plus/gnlsviews_grants.sql script for the type of potential changes you may need.

New tables and views

The following tables are now being baselined for this release. For non-US clients, these tables already exist and will not be altered in any way. For US clients, these will be new tables.

Report/Process Internationalization Status Table (GJBJOBI)

The Report/Process Internationalization Status Table (GJBJOBI) contains the names of the reports or processes that will save the NLS session parameters for the process in the GJBPNLS table. This table is currently being used to hold the NLS session parameters and their values.


Ba

Translated text for specific primary keys table (NLS_LANG_TEXT)

The NLS_LANG_TEXT table is used to define translated verbiage for specific primary key values by table and column name. This table contains a listing of table names, column names and NLS language used to translate a text into language set in tm_nls view.


GJBJOBI_NAME NOT NULL

VARCHAR2(30) NAME: The name of an executable, procedure or report that will have the NLS_SESSION_PARAMETERS saved in GJBPNLS.

GJBJOBI_ACTIVITY_DATE

NOT NULL

DATE ACTIVITY DATE: This field identifies the most recent date a record was created or updated.

GJBJOBI_USER_ID NOT NULL

VARCHAR2(30) USER ID: The ID for the user that most recently updated the record.

GJBJOBI_SET_NLS NULL VARCHAR2(1) SET NLS: I(nherit settings) from submitter, else use server environment.

GJBJOBI_SURROGATE_ID

NULL NUMBER(19,0) SURROGATE_ID: Immutable unique key.

GJBJOBI_VERSION NULL NUMBER(19,0) VERSION: Optimistic lock token.

GJBJOBI_DATA_ORIGIN

NULL VARCHAR2(30) DATA ORIGIN: Source system that created or updated the data.

GJBJOBI_VPDI_CODE NULL VARCHAR2(6) VPDI CODE: Multi-entity processing code.


Ba

NLS session parameters during execution table (GJBPNLS)

This table is used to hold all NLS session parameters for processes defined in GJBJOBI. Typically, this data is used only for debugging purposes to verify and validate that NLS parameters at time of execution.


TABLE_NAME NOT NULL

VARCHAR2(32) TABLE NAME: The table name related to the translated text.

COLUMN_NAME NOT NULL

VARCHAR2(32) COLUMN NAME: The column name related to the translated text.

PKEY NOT NULL

VARCHAR2(512) PKEY: The key related to the translated text which is the cancatenation of all primary key columns, separated by chr(1).

NLS_LANG NOT NULL

VARCHAR2(64) NLS LANG: The language of the translated text.

NLS_TEXT NULL VARCHAR2(2048) NLS TEXT: The translated text associated with the key, column, and table.

ACTIVITY_DATE NULL DATE ACTIVITY DATE: This field identifies the most recent date a record was created or updated.


GJBPNLS_JOB NOT NULL

VARCHAR2(30) JOB: Job name used along with One Up Number to identify the parameters.

GJBPNLS_ONE_UP_NO NOT NULL

NUMBER ONE UP NO: Sequence number used along with Job and Number to identify the parameters.


Ba

GJBPNLS_PARAMETER NOT NULL

VARCHAR2(90) PARAMETER: The parameter from NLS_SESSION_PARAMETERS at the time this job was submitted.

GJBPNLS_VALUE NOT NULL

VARCHAR2(120) VALUE: The value associated with the parameter from NLS_SESSION_PARAMETERS at the time this job was submitted.

GJBPNLS_JAVA_LOCALE

NULL VARCHAR2(30) JAVA LOCALE: ISO locale at the time this job was submitted converted from the Oracle Language and Territory. For example, en_US instead of AMERICAN.AMERICA.

GJBPNLS_ACTIVITY_DATE

NOT NULL

DATE ACTIVITY DATE: This field identifies the most recent date a record was created or updated.

GJBPNLS_USER_ID NULL VARCHAR2(30) USER ID: The ID for the user that most recently updated the record.

GJBPNLS_SURROGATE_ID

NULL NUMBER(19,0) SURROGATE ID: Immutable unique key.

GJBPNLS_VERSION NULL NUMBER(19,0) VERSION: Optimistic lock token.

GJBPNLS_DATA_ORIGIN


GJBPNLS_VPDI_CODE NULL VARCHAR2(6) VPDI CODE: Multi-entity processing code.


Ba

Metadata for Banner NLS table (NLSVIEW)

This table is used to hold metadata about Banner tables for NLS functionality.

Language View of TM_NLS - Language Definition View (TM_NLS)

The TM_NLS view is used to describe the language currently being used. The language will be set as the value from nls_session_parameters for parameter NLS_LANGUAGE.

Jobs Parameter Definition View (NLS_GJBPDEF)

This view is used to hold the job parameter definitions from table GENERAL.GJBPDEF. The view contains data from GENERAL.GJBPDEF where GJBPDEF_DESC is a translated description in the language specified in TM_NLS and selected from NLS_LANG_TEXT.NLS_TEXT for the specified table, column and pkey (primary key).


NLSVIEW_TABLE_NAME NOT NULL

VARCHAR2(30) TABLE NAME: Table on which view is based.

NLSVIEW_TABLE_OWNER

NULL VARCHAR2(30) TABLE OWNER: Owner of the table.

NLSVIEW_DML_IND NOT NULL

VARCHAR2(1) DML IND: View supports DML (Y/N).

NLSVIEW_SYNCH_IND NOT NULL

VARCHAR2(1) SYNCH IND: Copy base table to nls_lang_text base.

NLSVIEW_SYNCH_DATE NULL DATE SYNCH DATE: Date of last synchronization.

NLSVIEW_SS_EDIT_IND

NOT NULL

VARCHAR2(1) SS EDIT IND: Show in Self Service interface.


LANG NULL VARCHAR2(160) LANG: NLS session parameter for NLS_LANGUAGE.


Ba


GJBPDEF_JOB NOT NULL

VARCHAR2(30) JOB: Name of executable, procedure or report.

GJBPDEF_NUMBER NOT NULL

VARCHAR2(2) NUMBER: Parameter number for this job.

GJBPDEF_DESC NULL VARCHAR2(4000) DESCRIPTION: Description of parameter based upon the current language setting.

GJBPDEF_LENGTH NOT NULL

NUMBER(2,0) LENGTH: Length of the defined parameter.

GJBPDEF_TYPE_IND NOT NULL

VARCHAR2(1) TYPE INDICATOR: Indicator to identify parameter type of (C)haracter, (D)ate, (I)nteger or (N)umber.

GJBPDEF_OPTIONAL_IND

NOT NULL

VARCHAR2(1) OPTIONAL INDICATOR: Indicator to identify whether this parameter is (O)ptional or (R)equired.

GJBPDEF_SINGLE_IND NOT NULL

VARCHAR2(1) SINGLE INDICATOR: Indicator to identify whether this parameter occurs (S)ingle or (M)ultiple times.

GJBPDEF_ACTIVITY_DATE

NOT NULL

DATE ACTIVITY DATE: Date this parameter was created or last modified.

GJBPDEF_LOW_RANGE NULL VARCHAR2(30) LOW RANGE: Specifies the low range boundary for this parameter.

GJBPDEF_HIGH_RANGE NULL VARCHAR2(30) HIGH RANGE: Specifies the high range boundary for this parameter.


Ba

Default Parameter View (NLS_GJBPDFT)

This view is used to hold the default parameter definitions from table GENERAL.GJBPDFT. This view contains data from GENERAL.GJBPDFT where column GJBPDFT_VALUE is derived based on the type indicator for the job on GJBPDEF.TYPE_IND, the job name and number from GJBPDFT. When type indicator is D, convert US formatted date to the current NLS date format, and when the type indicator is N, convert US formatted number (i.e. 1.23) to the current NLS numeric format (i.e. 1,23).

GJBPDEF_HELP_TEXT NULL VARCHAR2(4000) HELP TEXT: Long description of parameter based upon the current language setting.

GJBPDEF_VALIDATION NULL VARCHAR2(30) VALIDATION: Parameter level validation label to be performed when job is submitted through the Job Submission system.

GJBPDEF_LIST_VALUES

NULL VARCHAR2(30) LIST VALUES: Name of form to call for List of Values for this parameter.

GJBPDEF_SURROGATE_ID


GJBPDEF_VERSION NULL NUMBER(19,0) VERSION: Optimistic lock token.

GJBPDEF_USER_ID NULL VARCHAR2(30) USER ID: The ID for the user that most recently updated the record.

GJBPDEF_DATA_ORIGIN


GJBPDEF_VPDI_CODE NULL VARCHAR2(6) VPDI CODE: Multi-entity processing code.


Ba

Process Run Parameter View (NLS_GJBPRUN)

This view is used to hold the process parameter definitions from table GENERAL.GJBPRUN. The view contains data from GENERAL.GJBPRUN where column GJBPDEF_VALUE is derived based on type indicator for the job from GJBPDEF.TYPE_IND, the job name and number from GJBPDFT. When type indicator is


GJBPDFT_JOB NOT NULL

VARCHAR2(30) JOB: Name of executable, procedure or report associated with this parameter default.

GJBPDFT_NUMBER NOT NULL

VARCHAR2(2) NUMBER: Parameter number associated with this default.

GJBPDFT_ACTIVITY_DATE

NOT NULL

DATE ACTIVITY DATE: Date default value was created or last modified.

GJBPDFT_USER_ID NULL VARCHAR2(30) USER ID: User ID associated with this default. NULL values represent system level defaults.

GJBPDFT_VALUE NULL VARCHAR2(4000) VALUE: Default value for this parameter based upon the current language setting.

GJBPDFT_JPRM_CODE NULL VARCHAR2(15) Job Parameter Set Code.

REC_ROWID NULL ROWID ROWID: The ROWID from GJBPDFT.

GJBPDFT_SURROGATE_ID


GJBPDFT_VERSION_ID NULL NUMBER(19,0) VERSION: Optimistic lock token.

GJBPDFT_DATA_ORIGIN


GJBPDFT_VPDI_CODE NULL VARCHAR2(6) VPDI CODE: Multi-entity processing code.


Ba

D, convert US formatted date to the current NLS date format, and when the type indicator is N, convert US formatted number (i.e. 1.23) to the current NLS numeric format (i.e. 1,23).


GJBPRUN_JOB NOT NULL

VARCHAR2(30) JOB: Job name used along with One Up Number and Number to identify the parameters.

GJBPRUN_ONE_UP_NO NOT NULL

NUMBER ONE UP NO: Sequence number used along with Job and Number to identify the parameters.

GJBPRUN_NUMBER NOT NULL

VARCHAR2(2) NUMBER: Parameter Number used along with Job and One Up Number to identify the parameters.

GJBPRUN_ACTIVITY_DATE

NOT NULL

DATE ACTIVITY DATE: Date record was created or updated.

GJBPRUN_VALUE NULL VARCHAR2(4000) VALUE: Value of parameter based upon the current language setting.

GJBPRUN_LABEL NULL VARCHAR2(60) GJBPRUN_LABEL: The gjbprun_label column contains the name of a variable that will be prompted for when glblsel or glbdata is run. This value is only filled in from the gjapctl form.

REC_ROWID NULL ROWID ROWID: The ROWID from GJBPRUN.

GJBPRUN_USER_ID NULL VARCHAR2(30) USER ID: The ID for the user that most recently updated the record.

GJBPRUN_SURROGATE_ID



Ba

General Jobs Parameter Value View (NLS_GJBPVAL)

This view is used to hold the general jobs parameter values from GENERAL.GJBPVAL. The view contains data from GENERAL.GJBPVAL where column GJBPVAL_DESC is a translated description in another language selected from NLS_LANG_TEXT.NLS_TEXT for the specified table, column, pkey (primary key) and NLS_LANG equal to TM_NLS.LANG.

GJBPRUN_VERSION_ID NULL NUMBER(19,0) VERSION: Optimistic lock token.

GJBPRUN_DATA_ORIGIN


GJBPRUN_VPDI_CODE NULL VARCHAR2(6) VPDI CODE: Multi-entity processing code.


GJBPVAL_JOB NOT NULL

VARCHAR2(30) JOB: Job name of executable, procedure or report.

GJBPVAL_NUMBER NOT NULL

VARCHAR2(2) NUMBER: Parameter number associated with this job.

GJBPVAL_VALUE NOT NULL

VARCHAR2(30) VALUE: Validation value associated with this parameter.

GJBPVAL_DESC NULL VARCHAR2(4000) DESCRIPTION: Description of this validation value based upon current language setting.

GJBPVAL_ACTIVITY_DATE

NOT NULL

DATE ACTIVITY DATE: Date record was created or last modified.

GJBPDEF_SURROGATE_ID


GJBPDEF_VERSION NULL NUMBER(19,0) VERSION: Optimistic lock token.

GJBPDEF_USER_ID NULL VARCHAR2(30) USER ID: The ID for the user that most recently updated the record.


Ba

New objects

The following objects are new for this release. These objects were previously only delivered by the Solution Centers, but are now being baselined and will replace those objects being used by non-US clients.

At this point in time, the functionality for all clients remains the same. Future releases will continue to baseline additional components of language support until full language support is available for all clients.

GJBPDEF_DATA_ORIGIN


GJBPDEF_VPDI_CODE NULL VARCHAR2(6) VPDI CODE: Multi-entity processing code.

Object Description

mlutil This package supports routines for multilingual views.

nls_gjbpdef_iod This trigger deletes records from the GJBPDEF table for specified job name and number. This also deletes records from NLS_LANG_TEXT for the specified table name and pkey (primary key).

nls_gjbpdef_ioi This trigger inserts records into the GJBPDEF table for the specified job name and number. This also inserts rows into NLS_LANG_TEXT table name, column name, and description for the specified language in tm_nls.

nls_gjbpdef_iou This trigger updates the GJBPDEF table for the specified job name and number. When new description is not the old description, update NLS_LANG_TEXT table name, column name, and description for the specified language in tm_nls.

nls_gjbpdft_iod This trigger deletes records from the GJBPDFT table for specified row id.

nls_gjbpdft_ioi This trigger inserts into table GJBPDFT for the specified job name and number. The value in the table is derived based on the type indicator for the job from GJBPDEF.TYPE_IND and the job name and number from the GJBPDFT table.

When type indicator is D, convert the US formatted date to the current NLS date format and when the type indicator is N, convert the US formatted number (i.e. 1.23) to the current NLS numeric format (i.e. 1,23).


Ba

Modified objects

The following objects are modified for this release.

nls_gjbpdft_iou This trigger updates the GJBPDFT table for the specified row id. When the type indicator is D, convert the US formatted date to the current NLS date format and when the type indicator is N, convert the US formatted number (i.e. 1.23) to the current NLS numeric format (i.e. 1,23).

nls_gjbprun_iod This trigger deletes records from the GJBPRUN table for specified row id.

nls_gjbprun_ioi This trigger inserts a record into GJBPNLS when the job number is 99. Then, a record shall be inserted into GENERAL.GJBPRUN. When type indicator is D convert US formatted date to the current NLS date format and when type indicator is N convert US formatted number (i.e. 1.23) to the current NLS numeric format (i.e. 1,23).

nls_gjbprun_iou This trigger updates the GJBPDFT table for the specified row id. When the type indicator is D, convert the US formatted date to the current NLS date format and when the type indicator is N, convert the US formatted number (i.e. 1.23) to the current NLS numeric format (i.e. 1,23).

nls_gjbpval_iod This trigger deletes records from the GJBPVAL table for specified job name and number. This also deletes a record from NLS_LANG_TEXT for the specified table name and pkey.

nls_gjbpval_ioi This trigger inserts into table GJBPDEF for the specified job name and number. This also inserts a row into NLS_LANG_TEXT table name, column name, and description for the specified language in tm_nls.

nls_gjbpval_iou This trigger updates the GJBPVAL table for the specified job name and number. When new description is not the old description, update NLS_LANG_TEXT table name, column name, and description for the specified language in tm_nls.

gnlsviews_grants_local.sql

This trigger creates the grants that are given to the new NLSUSER.NLS_GJB% views similar to the grants that were present for the GENERAL.GJB% tables.

Object Description

gb_nlsjobs This package provides Job submission support, validation and formatting as it relates to the translation for international support.

Object Description


Ba

GOASDMD security

With Banner General 8.8 release, there is tighter security surrounding the generation and application of views related to the Supplemental Data Engine (SDE) on the Supplemental Data Attributes Definition Form (GOASDMD). Previously, users with access to the GOASDMD form could create SDE attributes as well as generate and apply new views. However, with this release, users can only generate and apply views if they are granted the new Banner security object BAN_GOASDMD_DDL and have a maintenance access (i.e. BAN_DEFAULT_M) to GOASDMD. A user with query only access (i.e. BAN_DEFAULT_Q) will not be able to generate or apply views even if they are granted BAN_GOASDMD_DDL.

Typically, the GOASDMD form should only be granted to a small set of power users with a technical background. You can use the following SQL to find out the users that currently have access to GOASDMD:

SELECT guvuacc_user,

g$_security.g$_get_username_name(guvuacc_user) "Name",

guvuacc_role, guvuacc_type, guvuacc_class,

guvuacc_group, guvuacc_rank

FROM bansecr.guvuacc

WHERE guvuacc_object = 'GOASDMD'

ORDER BY guvuacc_user, guvuacc_rank;

Once you have identified the users and verified that they should have the ability to generate and apply the new SDE view, you should grant BAN_GOASDMD_DDL to this group. Since it should be a small number of users, granting this to them directly is recommended instead of via a CLASS or SECURITY GROUP.

Note: The granting of access to this object is done by your local Banner Security Administration using the Security Maintenance Form (GSASECR).

gb_common This package provides standard functions and procedures among all Banner API packages.

gb_common_strings This package provides messages associated with the common business APIs to support globalization.

Object Description


BaInfo

Appendix A - Oracle*Wallet Proxy for Job Submission Configuration Information

This chapter describes the steps that must be taken in order to setup a Secure External Password Store using Oracle*Wallet with a proxy user's credentials so that a password is not needed to log in to the database when running batch jobs.

Note: These steps are a basic example of getting this solution running in a Linux environment. The solution does not rely on Linux specific utilities, so it can be used to implement this solution in other operating systems using the analogous command.

Single instance setup

Perform the following steps to set up Oracle*Wallet in a single instance environment.

Create wallet

These steps create an empty wallet with the necessary file permissions. Only the Operating System (OS) user that is used to run Job Submission process (gurjobs) has access to them.

Step 1. Create directory to store wallet files

For example, assume the Job Submission OS user is banjobs. As banjobs, in banjobs' home directory, the following command would be issued:

[ ~ ]$ mkdir proxy_wallet

Step 2. Create wallet in the new directory

The mkstore command is used to interact with the wallet. To create the wallet, the command is called with the -create option as mkstore -wrl <wallet directory> -create. The command will prompt for a password. This password will be used for all future interactions with the wallet. The commands would look like this if we continue on with the banjobs example:

[ ~ ]$ cd proxy_wallet

[ ~/proxy_wallet ]$ mkstore -wrl . -create

24nner General Release Guide | Appendix A - Oracle*Wallet Proxy for Job Submission Configuration rmation

BaInfo

<enter and confirm your new password>

Step 3. Check wallet files were created correctly

Use the ls command to check that the wallet files were created and that they have the correct file permissions. The wallet files should only be accessible to the Job Submission user, in this example, banjobs:

[ ~/proxy_wallet ]$ ls -l

Total 16

-rw------- 1 banjobs users 3000 Feb 27 07:46 cwallet.sso

-rw------- 1 banjobs users 3000 Feb 27 07:46 ewallet.p12

If the ls command indicated that other users had access to the wallet files, then use chmod to set them appropriately:

[ ~/proxy_wallet ]$ chmod 600 ./*

tnsnames.ora and sqlnet.ora setup

The tnsnames.ora and sqlnet.ora files need to be modified on the Job Submission server so the Oracle Net client knows where to look for the wallet. The default location for these files is $ORACLE_HOME/network/admin. The files need to be copied to a different location so that the Proxy Wallet will only be used with Job Submission and current functionality is preserved. Having WALLET_OVERRIDE in sqlnet.ora set to TRUE can interfere with other Oracle tools.

Step 1. Copy tnsnames.ora and sqlnet.ora to a new location

Create a new directory to store the tnsnames.ora and sqlnet.ora files that will be modified. Copy the tnsnames.ora and sqlnet.ora files that are currently being used to this new directory. The TNS_ADMIN environment variable will need to be set to this location for the shell that will execute GURJOBS.

[ ~ ]$ cd $ORACLE_HOME/network/admin

[ /u01/app/oracle/ORDBMS/11.2.0.2/network/admin ]$ mkdir proxy_setup

[ /u01/app/oracle/ORDBMS/11.2.0.2/network/admin ]$cp tnsnames.ora proxy_setup/tnsnames.ora

[ /u01/app/oracle/ORDBMS/11.2.0.2/network/admin ]$cp sqlnet.ora proxy_setup/sqlnet.ora

Step 2. Modify tnsnames.ora

Open the new tnsnames.ora file. This file contains entries that describe connections to your database. The original TNS entries should remain in both tnsnames.ora files. Add


BaInfo

a new entry as a copy of the one that is normally used to connect to the database and rename it. This alias will be used to create the wallet credentials and must be specified in the Proxy Job Submission SID on the GSASECR form. In the example tnsnames.ora below, SMPL is what is normally used to connect to the database, and JSUB was added as an exact copy:

SMPL =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = DBSMPL) (PORT = 1521))

)

(CONNECT_DATA =

(SID = SMPL)

(SERVICE_NAME = WWW.YOURINSTITUION.COM)

(SERVER = DEDICATED)

)

)

JSUB =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = DBSMPL) (PORT = 1521))

)

(CONNECT_DATA =

(SID = SMPL)

(SERVICE_NAME = WWW.YOURINSTITUION.COM)


)

)

Step 3. Modify sqlnet.ora

Open the new sqlnet.ora file. Entries need to be added to this file to specify the wallet location and force the wallet to be used to authenticate users to the database. The directory entry below should be the directory where the wallet was created. In this example, /u03/banjobs/proxy_wallet.

WALLET_LOCATION =


BaInfo

(SOURCE = (METHOD = FILE)

(METHOD_DATA =

(DIRECTORY=/u03/banjobs/proxy_wallet)))

SQLNET.WALLET_OVERRIDE = TRUE

SSL_CLIENT_AUTHENTICATION = FALSE

Store credentials in wallet

These steps will create a user that all Banner Job Submission users will use as a proxy to connect to the database. This user's credentials will be stored in the wallet. The banjsproxy user will already have been created during the Banner General 8.8 upgrade process. Remember, the wallet files will only be accessible to the Job Submission user.

Step 1. Create proxy user

Connect to the database using sqlplus and issue the following command to create the banjsproxy user:

SQL> create user banjsproxy identified by <password>

SQL> /

User created.

Step 2. Store proxy user's credentials

The mkstore command will be used to store the proxy user's credentials in the wallet. The mkstore command to store the user's credentials is of the form mkstore -wrl <wallet directory> -createCredential <alias from tnsnames.ora> <username> <password>, and will prompt you for the wallet password:

[ ~/proxy_wallet ]$ mkstore -wrl . -createCredential JSUB BANJSPROXY <password>

Enter password:

Create credential oracle.security.client.connect_string1

Step 3. Test wallet credentials

When testing, make sure the TNS_ADMIN variable is set to the location of the new tnsnames.ora and sqlnet.ora files. The tnsping command is used to test that the alias created in the tnsnames.ora file is able to connect to the database. Then, attempt to connect to sqlplus using the wallet syntax, sqlplus /@<alias from tnsnames.ora>. You will need to be logged in to the Job Submission OS user to make use of the wallet, and banjsproxy may need to be given create session privileges.


BaInfo

[ ~/proxy_wallet ]$ export TNS_ADMIN=/u01/app/oracle/ORDBMS/11.2.0.2/network/admin/proxy_setup/

[ ~/proxy_wallet ]$ tnsping jsub

TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 02-APR-2015 10:48:46

Copyright (c) 1997, 2010, Oracle. All rights reserved.

Used parameter files:

/u01/app/oracle/ORDBMS/11.2.0.2/network/admin/proxy_setup/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = DBSMPL) (PORT = 1521))) (CONNECT_DATA = (SID = SMPL) (SERVICE_NAME = WWW.YOURINSTITUTION.COM) (SERVER = DEDICATED)))

OK (10 msec)

[ ~/proxy_wallet ]$ sqlplus /@jsub

SQL*Plus: Release 11.2.0.2.0 Production on Thu Apr 2 10:56:03 2015

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> show user

USER is "BANJSPROXY"

RAC setup

There are a couple of different approaches for setting up the wallet in a RAC environment. The one best suited for your environment depends on how that RAC environment is used and implemented. This step will set the wallet up in a shared location that all nodes will use. An alternative is to install the wallet on each node. This can be done by repeating the Single Instance steps for each node and making sure to use TNS alias/service associated with the RAC, as opposed to the instance, for the wallet's connection string.

The wallet and SQL*Net files should be set up in a shared location so all the instances can see the wallet. This shared location could be a subdirectory of the Grid home or some other networked file system.


BaInfo

Create wallet

These steps will create an empty wallet with the necessary file permissions. Only the OS users that are used to run Job Submission process (gurjobs) should have access to them. These users should belong to their own group so that all other users are prohibited from reading or writing the wallet files.

Step 1. Create directory to store wallet files

For example, assume a Job Submission OS user is banjobs and the user group jobsub has been created for all the Job Submission OS users. As banjobs, navigate to the shared location. In this directory, the following command would be issued:

[ /s01/app/jsub ]$ mkdir proxy_wallet

Step 2. Create wallet in the new directory

The mkstore command is used to interact with the wallet. To create the wallet, the command is called with the -create option as mkstore -wrl <wallet directory> -create. The command will prompt for a password. This password will be used for all future interactions with the wallet.

[ /s01/app/jsub ]$ cd proxy_wallet

[ /s01/app/jsub/proxy_wallet ]$ mkstore -wrl . -create

<enter and confirm your new password>

Step 3. Check wallet files were created correctly

Use the ls command to check that the wallet files were created and that they have the correct file permissions. The wallet files should only be accessible to the Job Submission user group, in this example, jobsub:

[ /s01/app/jsub/proxy_wallet ]$ ls -l

Total 16

-rw-r----- 1 banjobs jobsub 3000 Feb 27 07:46 cwallet.sso

-rw-r----- 1 banjobs jobsub 3000 Feb 27 07:46 ewallet.p12

If the ls command indicated that other users had access to the wallet files, then use chmod to set them appropriately:

[ /s01/app/jsub/proxy_wallet ]$ chmod 640 ./*

tnsnames.ora and sqlnet.ora setup

The tnsnames.ora and sqlnet.ora files need to be placed on the shared location so the Oracle Net client knows where to look for the wallet. The files need to be copied to a different location so that the Proxy Wallet will only be used with Job Submission and


BaInfo

current functionality is preserved. Having WALLET_OVERRIDE in sqlnet.ora set to TRUE can interfere with other Oracle tools.

Step 1. Copy tnsnames.ora and sqlnet.ora to a new location

Create a new directory to store the tnsnames.ora and sqlnet.ora files that will be modified. Copy the tnsnames.ora and sqlnet.ora files that are currently being used to this new directory. The TNS_ADMIN environment variable will need to be set to this location for the shell that will execute GURJOBS.

[ ~ ]$ cd /s01/app/jsub

[ /s01/app/jsub ]$ mkdir proxy_setup

[ /s01/app/jsub ]$ cp $ORA_CRS_HOME/network/admin/tnsnames.ora proxy_setup/tnsnames.ora

[ /s01/app/jsub ]$ cp $ORA_CRS_HOME/network/admin/sqlnet.ora proxy_setup/sqlnet.ora

Step 2. Modify tnsnames.ora

Open the new tnsnames.ora file. This file contains entries that describe connections to your database. The original TNS entries should remain in both tnsnames.ora files. Add a new entry as a copy of the one that is normally used to connect to the database and rename it. This alias will be used to create the wallet credentials and must be specified in the Proxy Job Submission SID on the GSASECR form. In the example tnsnames.ora below, SMPLRAC is what is normally used to connect to the RAC, and SMPLRAC_JSUB was added as an exact copy:

LISTENERS_DBSMPL =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = DBSMPL1)(PORT = 1521))


)

LISTENER_DBSMPL1 =


LISTENER_DBSMPL2 =



BaInfo

SMPLRAC2 =

(DESCRIPTION =


(CONNECT_DATA =


(SERVICE_NAME = www.yourinstitution.com)

(INSTANCE_NAME = SMPLRAC2)

)

)

SMPLRAC1 =

(DESCRIPTION =


(CONNECT_DATA =



(INSTANCE_NAME = SMPLRAC1)

)

)

SMPLRAC =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = DBSMPL)(PORT = 1521))

(CONNECT_DATA =



)

)

SMPLRAC_JSUB =


BaInfo

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = DBSMPL)(PORT = 1521))

(CONNECT_DATA =



)

)

Step 3. Modify sqlnet.ora

Open the new sqlnet.ora file. Entries need to be added to this file to specify the wallet location and force the wallet to be used to authenticate users to the database. The directory entry below should be the directory where the wallet was created. In this example, /s01/app/jsub/proxy_wallet.

WALLET_LOCATION =

(SOURCE = (METHOD = FILE)

(METHOD_DATA =

(DIRECTORY=/s01/app/jsub/proxy_wallet)))

SQLNET.WALLET_OVERRIDE = TRUE

SSL_CLIENT_AUTHENTICATION = FALSE

Store credentials in wallet

These steps will create a user that all Banner Job Submission users will use as a proxy to connect to the database. This user's credentials will be stored in the wallet. The banjsproxy user will already have been created during the Banner General 8.8 upgrade process.

Note: The wallet files will only be accessible to the Job Submission user.

Step 1. Create proxy user

Connect to the database using sqlplus and issue the following command to create the banjsproxy user:

SQL> create user banjsproxy identified by <password>

SQL> /

User created.


BaInfo

Step 2. Store proxy user's credentials

The mkstore command will be used to store the proxy user's credentials in the wallet. The mkstore command to store the user's credentials is of the form mkstore -wrl <wallet directory> -createCredential <alias from tnsnames.ora> <username> <password>, and will prompt you for the wallet password:

[ /s01/app/jsub/proxy_wallet ]$ mkstore -wrl . -createCredential SMPLRAC_JSUB BANJSPROXY <password>

Enter password:

Create credential oracle.security.client.connect_string1

Step 3. Test wallet credentials

Wallet credentials can be tested in the same way as for the single instance demonstrated previously. When testing, make sure the TNS_ADMIN variable is set to the location of the new tnsnames.ora and sqlnet.ora files. The tnsping command is used to test that the alias created in the tnsnames.ora file is able to connect to the database. Then, attempt to connect to sqlplus using the wallet syntax, sqlplus /@<alias from tnsnames.ora>. You will need to be logged in as one of Job Submission OS users to make use of the wallet, and banjsproxy may need to be given create session privileges.

Enable Job Submission Proxy Wallet

To enable users to use the wallet the alias that was added to tnsnames.ora needs to be input in Internet Native Banner (INB). In INB, navigate to the GSASECR form. Under the Institution Profile tab, enter the alias in the Proxy Job Submission SID text field. Each user who wants to use Job Submission Proxy should have the Authorize BANJSPROXY check box checked.

Step 1. Edit GURJOBS driver shell

Article CMS-2317 in Ellucian Support Center contains information of how to implement GURJOBS as a background process. The driver shell needs to have the TNS_ADMIN variable set to the location of the new tnsnames.ora and sqlnet.ora. The example banjobs_driver.shl from CMS-2317 would be modified as follows:

:

# banjobs_driver.shl

# This script is run as banjobs from from the Unix prompt.

LOGFILE1=/u01/banner/banjobs/gurjobs.log;export LOGFILE1

LOGFILE2=/u01/banner/banjobs/sfrpipe.log;export LOGFILE2

export TNS_ADMIN=/u01/app/oracle/ORDBMS/11.2.0.2/network/admin/proxy_setup


BaInfo

/u01/banner/banjobs/gurjobs.shl >>${LOGFILE1} 2>&1 &

/u01/banner/banjobs/sfrpipe.shl >>${LOGFILE2} 2>&1 &

Notes about Batch Java

The Proxy Wallet can only be used with Oracle OCI JDBC driver. The classpath argument that is passed to the batch program must contain the jar file that is specific to the version of the Oracle Client that is installed. The classpath variable is set up in banjavaenv.shl for Unix/Linux systems and banjavaenv.pm for Windows systems.


banner general release guidebanner7.utm.edu/manuals/banner_release_guides/general80800rg.pdf ·...

Documents