Installing or Migrating a Banner job from Test to Production
Use the following steps to migrate (i.e. copy or install) source files from a Banner job from TEST to PROD.
- Login to a Linux command prompt on the PROD job server as yourself.
Enter xsu banner to become the banner user.
A Banner job usually consists of a shell script (located in $BANNER_HOME/product_directory/oakland/misc) and a SQL script (located in $BANNER_HOME/product_directory/oakland/plus); other files may or may not be included in the request. Once a shell script has been installed, it usually does not get modified. If any of the files to be installed are not located under $BANNER_HOME, stop the installation.
- Position yourself in the appropriate directory (the ticket should indicate which directory is appropriate).
Enter testdiff filename to compare the new object to the one currently in PROD
- If the job is a new job, you should get an error message from the diff command saying that the file does not exist.
If the job is not a new job, read through the results of the testdiff command, and verify:
- that all new functionality is described in the ticket, and
- that all desired functionality from the ticket was actually added to the script.
Enter testcopy filename to copy the new object from TEST to PROD, and to create a link in the $BANNER_LINKS directory.
Repeat the above testdiff and testcopy steps for each file that needs to be migrated.
Use the following steps to define a new job in Banner (assuming the job already exists in TEST).
Login to both TEST and PROD Internet Native Banner as BANSECR.
In both instances, run the GSASECR form.
In both instances, click the Objects tab.
- In the TEST instance, press F7 to enter query mode. Enter the name of the job you are migrating, and then press F8.
In the PROD instance, click the Insert Record button. Type the entry for the new object in PROD so that it matches the TEST entry. Click the Save button.
In the TEST instance, click the Users and Classes assigned to this Object button. Keep the resulting window open for the next step.
In the PROD instance, click the Classes tab. Use the query box and Execute Query button to locate each class found in the previous step (you will ignore the "Direct" accesses). For each of these classes, click the Objects button. In the resulting form, click the Insert button; then, enter the new job in the Object Name column, and press the Tab key. If the role that this class has in TEST is different from the default role, change the value in the Role Name column to match the role for TEST. Then, click the Close button. When you are returned to the Classes tab, you will see that the Status of this class is now "Out of Sync". Repeat this procedure for all classes identified in the previous step.
When you are finished adding the new job to classes in PROD, if the query box does not contain "%", change it so that it does, and click the Execute Query button. Then, click the Synchronize All button.
To perform the remaining setup in Internet Native Banner, you must have access to the new job. In the PROD instance, if you personally do not have access to one of the classes that you added the object to, click the Users tab, type your userid in the query box, and click the Modify button. In the resulting form, type the new job into the Object Name column, and click the Close button.
- Logout from your BANSECR sessions in both TEST and PROD Internet Native Banner.
- Login to both TEST and PROD Internet Native Banner as yourself.
In both instances, run the GJAJOBS form.
In the TEST instance, type the name of the new job in the Process box, and press F8.
In the PROD instance, type Ctrl+Q to cancel Query mode; then, enter the data for the new job so that it matches what is in TEST (you do not need to enter the activity date), and click the Save button.
In both instances, exit the GJAJOBS form.
In the TEST instance, run the GJAPDEF form. Type the name of the new job in the Process box, and press Ctrl+PgDn. If no records are found, you may skip the next step.
If records were found in the above step, run the GJAPDEF form in the PROD instance. Type the name of the new job in the Process box, and press Ctrl+PgDn. Enter records in the PROD instance so that they match all of the records shown in the TEST instance.
In both instances, exit the GJAPDEF form.
If any GJAPDEF records were created above, run the GJAPVAL form in the TEST instance. The new job should already be in the Process box. Press Ctrl+PgDn. If no records are found, you may skip the next step.
If records were found in the above step, run the GJAPVAL form in the PROD instance. The new job should already be in the Process box. Press Ctrl+PgDn. Enter records in the PROD instance so that they match all of the records shown in the TEST instance.
In both instances, exit the GJAPVAL form.
- Logout from both of your Internet Native Banner sessions.
- If you did not have to grant yourself direct access to the new job in order to complete the GJAJOBS, GJAPDEF, and GJAPVAL steps, you may skip the next step.
If you had to grant yourself direct access to the new job, login to Internet Native Banner as BANSECR for each database where you granted yourself direct access. Run the GSASECR form. Type your username in the User ID box, and click modify. Place your cursor on the new job name in the Object Name column, and click the Delete button. Then click the Close button.
If you need to modify the parameters of an already existing job, adjust the above steps as needed to:
- Temporarily grant yourself access to the job if necessary.
- Insert, update, or delete records on the GJAPDEF and/or GJAPVAL forms.
- Revoke any temporary access you granted.
---
DataAdminHowTo
DB_Administration