CSULB Campus Solutions 9.

0 Upgrade
Project Orientation

Goals....................................................................................................................................2
Scope....................................................................................................................................2
Schedule...............................................................................................................................2
Major Simultaneous Projects...........................................................................................2
Roles....................................................................................................................................3
Documents...........................................................................................................................3
Status Meetings....................................................................................................................4
Meeting Rooms....................................................................................................................4
Project Databases.................................................................................................................5
Testing.................................................................................................................................5
Preserving Your Functional Work.......................................................................................6
Security Track......................................................................................................................6
General Approach............................................................................................................6
Detailed Guides...............................................................................................................6
Appendix – CS-Link, Reports, and FTP Gateway..............................................................7
CS-Link Application for 9.0 Project................................................................................7
FTP GateWay for 9.0 Project..........................................................................................8
Source Databases for Reports..........................................................................................9
PeopleSoft Database....................................................................................................9
RDS Database............................................................................................................10
Astra Database...........................................................................................................10
StarRez Database.......................................................................................................10
Outgoing Email..............................................................................................................10
Scope..........................................................................................................................11
Programmer Notes.........................................................................................................11
SQR & Crystal Executables.......................................................................................11
Approach for Re-Working Reports...........................................................................11

L:\U\ 9.0 \ A \01 \01 \Project [Link] 1/12 Last Revised: 7/26/2010
Goals
 Upgrade the CMS CS (“Campus Solutions”) system to Version 9.0 by May 5,
2011.
 Maintain or improve all current data and functional processes.
 Implement selected new 9.0 features.
 Continue uninterrupted support of the production business systems and required
upgrades to the 8.9 system.

Scope
 All current delivered PeopleSoft and CSU Baseline functions as listed in the
Business Process Guides and Standard Test Plans.
 All custom-built programs and reports listed in the SA TechTrak Database.
 All SA security.
 Updates to Documentation, Training and Communications. Make all web docs
ATI-compliant.
 Re-test interfaces to all Third Party tools and vendors.
 Discontinue EPOS. Implement Applicant Self-Service.
 Implement new delivered functionality related to Self-Service, Facilitating
Graduation, Enrollment Backpack & Permits, and Scholarships.

Schedule
Phase When Comment
Prep May ‘10 – Aug ‘10
Pass 1 Aug ‘10 Initial upgrade and database setup.
Phase 1 Sep ’10 – Nov ‘10 Test and re-work existing functions.
Pass 2 Nov ‘10 Refresh upgrade of all databases.
Phase 2 Dec ‘10 – Feb ‘11 Re-test existing. Start all new work.
Final dress-rehearsal practice upgrade to all
Pass 3 Mar ‘11
databases.
Phase 3 Mar – Apr ‘11 Re-test. Finalize docs and go-live plan.
MTP May 5 - 8 ‘11 Move to Production.

Major Simultaneous Projects

 The Ad Astra Version 7 upgrade is still in progress. Until a firm Astra cutover
date is decided, assume that Astra 5.2 is the target production system.
 The Scholarship administration project is proceeding in parallel with the upgrade.

L:\U\ 9.0 \ A \01 \01 \Project [Link] 2/12 Last Revised: 7/26/2010
Roles
Module Leads
 Module coordination, prioritization, deliverables.
 Module-specific project lead.
 Progress and status reporting.
Assistant Module Leads
 Testing.
 Issues and follow-up.
Doc/Trainers
 Security.
 Documentation.
 Training.
 Communications.
Programmers
 Rework and confirm all custom development.
 Module technical support.
Systems Leadership/Business Analyst Team
 Project management.
 Tracking.
 Reporting.

Documents
The project folder is located at “L:\U Upgrade\ 9.0” which may be called the “U” drive
or “U” folder. Do not modify the high-level structure of this folder.

This folder is to be used only for certain types of files that are needed to coordinate the
overall 9.0 upgrade. These are:
 Project Management files.
o Project plans, statuses, issues, etc.
o Consolidated summary lists from Modules
o Task lists for Pass preparation
 Cross-module projects:
o Self-Service, etc.
o Security
o Standard Test Plans
o Documentation & Training
o Technical

L:\U\ 9.0 \ A \01 \01 \Project [Link] 3/12 Last Revised: 7/26/2010
  Technical rework projects for Gold package

Module-specific docs should stay in the folders that were established for the initial
implementation. Do not place module-specific docs in the “U” folder except in the cases
listed above.

Status Meetings
Each project track must meet regularly to ensure priorities, communication, and
deliverables. “Tracks” include, but are not limited to the following:

 Modules
 New major functional tracks
 Self-service
o Student
o Applicant
o Faculty/Advisor
 Security
 Technical - programming
 Reports
 Change Mgmt/Doc Training
 Special projects

Weekly
Each activity track should meet weekly during its period of peak activity.

Monthly
Once per month, the weekly meetings will be attended by Project Leadership
representatives who will review the important issues and provide assistance.

Meeting Rooms
The ES - Ed Center (BH 124) and ES – Conference Room (BH 276) can be booked via
Lotus Notes. ES Admin Support administers those rooms. They can also assist in
finding and booking other rooms.

Many other DAF meeting rooms can be booked directly via Notes. A list of these can be
found via the Notes Calendar, by selecting ‘Rooms’, while scheduling the meeting.

L:\U\ 9.0 \ A \01 \01 \Project [Link] 4/12 Last Revised: 7/26/2010
Project Databases
The 9.0 databases are accessible via the same links page that is used for 8.9:

[Link]

The databases for the 9.0 project are at the bottom of the list. They are identifiable by the
prefix “HA…” and by the version of PeopleTools: 8.50.

Customizations move from HALBDVL to HALBTST before being officially frozen in

HALBSTG.

DataBase Usage Security

Technical development and re-working of
HALBDVL Programmers have Admin role.
customizations.
Similar to production.
In Phase 1, Module Leads will
HALBTST Functional testing. Third-party interfaces.
have Admin role.
Programmers have Admin role.
HALBPRE Production-like hardware for Pass 3 testing. Same as PRD.
The “Gold” database. Where all finalized custom
HALBSTG DBA’s only.
work is kept in preparation for the next Pass.

Testing
See “L:\U \9.0 \B Standard Test Plans\”

The module standard test plans accomplish many things:

1. A comprehensive list of all functionality to be tested.

2. An indication of priority or “weight”.
3. Pass/Fail status and follow-up for Fails.
4. Details regarding the testing data and execution steps.

We will continue to use the same standard test plan templates that we use for
Maintenance Pack testing. Each module will review their spreadsheets and update it with
any additional functionality introduced by HCM 9.0.

Just testing the base case will easily lead to success. Testing every possible variation will
take too much time. Modules can use their own expertise and judgment to determine a
reasonable level of variation.

L:\U\ 9.0 \ A \01 \01 \Project [Link] 5/12 Last Revised: 7/26/2010
Preserving Your Functional Work
Each “Pass” is a complete over-write of the project databases. This allows increasingly
accurate practice upgrades. But it also wipes out the campus work. During each phase of
work we will collect our programs and setup data into a “Gold” package for carrying
forward to the next phase. The Gold package will be strictly controlled by the DBA’s.

Many custom objects must be reworked to make them 9.0 compatible. The developers
have strict methods for packaging mods to ensure carry-forward.

There are four areas of “functional” work that have to be tracked for carry-forward to the
next phase.
1. Manual Setup data entry in HALBTST.
2. New or modified PS Queries in HALBTST.
3. Translate Values (programmers will have to be involved in any changes).
4. Security Changes.

The folder, “L:\U\ 9.0 \A \03 \D Tracking Functional Rework” contains the tracking sheet and
README file with additional details.

Security Track
During the multiple phases of this project, there will be a number of component security
changes to support user access to existing and new functionality. These must be tracked
and implemented consistently to ensure that all application security is ready for Go Live
in May, 2011. Some changes will require dual updates to databases (DB’s) in both 8.9
and 9.0 environments.

General Approach
1. User profiles will be owned by the current version 8.9 database and will be
maintained throughout the upgrade passes. This includes UserID’s, passwords,
primary permission lists, role memberships, ID linkage, etc.

2. Role and permission list definitions will come from the 9.0 Gold database, to be
applied after the pass is complete. Similar to other LB Custom development, a Gold
security project will be maintained and applied after the database has been
upgraded and Baseline objects applied.

Detailed Guides
L:\U Upgrade\9.0\O Security\01 Planning\ HCM 9 Upgrade Security [Link]

L:\U Upgrade\9.0\O Security\03 Change Tracking\ HCM 9.0 Security Tracking [Link]

L:\U\ 9.0 \ A \01 \01 \Project [Link] 6/12 Last Revised: 7/26/2010
Appendix – CS-Link, Reports, and FTP Gateway
Both programmers and testers should understand this appendix. There is a risk that
letters, emails, or data files will be distributed accidentally because someone did not
understand the difference between the production and test environments.

There is a separate Reports testing environment. Like the production CS-Link

environment, it is comprised of the following major components:

 A CS-Link web application for running reports.

 An FTP GateWay for moving files via background scripts.
 SQR & Crystal executables that are called by CS-Link.

CS-Link Application for 9.0 Project

URL: [Link]
ID: Your CS-Link production ID. Same as Campus ID.
Password: Should be same as CS-Link production.
If that does not work, then it will be the same as your ID.

When bookmarking this site in your browser, give it a name like “CS-Link
9.0 Testing”.

1. CS-Link programs will produce real files that go to JetForms. Mostly these are
the CMSmail programs. They will always send the tester a sample and a log. If
they are run in “Real” mode as opposed to “Test” mode, then they will also send
out real communications.

2. If a report’s Upgrade Status is “Testing” or “Completed”, then it should work

properly. Notify the programmer if it does not. Change the TechTrak Item from
“Completed” back to “In Progress.”

L:\U\ 9.0 \ A \01 \01 \Project [Link] 7/12 Last Revised: 7/26/2010
FTP GateWay for 9.0 Project

The FTP Gateway resides on the CS-Link reports machine. We use it for many things,
including CS-Link input and output files, files going to and from Unisys, and files going
to and from external parties. It also has a forwarding folder to JetForms. The GateWay
allows end-users to perform file transfers without using an FTP tool.

For the 9.0 project, there is a parallel GateWay running on the test reports server. Instead
of Q: the path is mapped as R: on the core team PC’s.

Key points when using the 9.0 GateWay:

 The CS-Link\In & \Out folders are used by the 9.0 CS-Link test application
(described above.)
 FTP Sites refers to external parties.
o The Outbound forwarding scripts have been disabled so that files do not
FTP automatically to external sites.
o The Inbound forwarding scripts, which move files to other GateWay
folders, are still operational. You can drop files in an Inbound folder to
simulate receipt from an outside party.
 The PeopleSoft_Test folder is a little complicated because there is actually only
one Unisys environment for all non-prod instances, including both 8.9 and 9.0
instances.
o PeopleSoft_Test\From_PeopleSoft would normally contain files that were
forwarded from the non-prod LB_GateWay folder at Unisys. But that
folder is configured for 8.9 activity, so it forwards files to the Q: drive. If
you run a 9.0 process at Unisys and send the output to:

L:\U\ 9.0 \ A \01 \01 \Project [Link] 8/12 Last Revised: 7/26/2010
 /hr/hrpsoft/xfer/in/hlbftp/LB_GateWay/some_folder, then the file will appear
at Q:\PeopleSoft_Test\From_PeopleSoft\some_folder. From there you can
manually drag it to another destination if necessary.
o PeopleSoft_Test\To_PeopleSoft works as you would expect. Place a file
into R:\PeopleSoft_Test\To_PeopleSoft\some_folder and it will appear at
Unisys in /hr/hrpsoft/xfer/in/hlbftp/some_folder. This is the same Unisys
directory that is used by all non-prod 8.9 and 9.0 instances.
 The JetForms folders are for auto-forwarding files to JetForms.
o Mostly these folders are used by programs, not by individual users.
o On the R: drive, the various JetForms subfolders interact with the
JetForms server just as they do on the Q: drive.
o There is no test version of JetForms. Every file that JetForms receives
will be processed the same as a production file. It is up to the tester to
prevent Emails and letters from being distributed accidentally.

Technical (programming) points regarding the GateWay:

 The GateWay is on the same machine that runs the 9.0 CS-Link reports. The
machine is “its-cslnkd”.
 The environment was set up in parallel with the production Reports Server so that
9.0 reports can be tested without modifying any path and file names.
o Within that machine, the path down to the gateway folders is the same as
on the production reports server. The GateWay top folder is known to that
machine as its “E” drive, just as in production.
o If we add FTP subfolders for auto-forwarding, the matching FTP
subfolders must be added at Unisys non-prod. Notify Don and set the
Unix folder security to 775.

Source Databases for Reports

PeopleSoft Database
When you run reports in the 9.0 CS-Link, the default database is HALBTST (9.0).
1. Reports that point to HLBPRD or HLBRPT are automatically re-directed to pull
data from HALBTST.
2. Some reports might allow you to select a database. Always select HALBTST or
else you will not get 9.0 data.

L:\U\ 9.0 \ A \01 \01 \Project [Link] 9/12 Last Revised: 7/26/2010
RDS Database
There will be a parallel RDS test environment for the 9.0 project. All CS-Link reports
that point to RDS will be automatically re-pointed to the 9.0 RDS database for the
duration of the project.

The DBA’s will re-work the Cognos RDS loader throughout September. We can start
testing and re-working RDS reports in October.

Astra Database
Some reports point to Ad Astra and some of those have DB-Links to PeopleSoft. For the
CMS project, the connections will be as follows:
CS-Link – AstraT – DB-Link - HALBTST

StarRez Database
For technical reasons, we use Astra to connect to the Housing system (StarRez) while
also connecting to PeopleSoft.
CS-Link – AstraP – DB-Link – StarRez
– DB-Link – HLBPRD

For the CMS project, the connections will be as follows:

CS-Link – AstraT – DB-Link – StarRez
DB-Link – HALBTST

Outgoing Email

We now have several tools and methods for sending emails to students. To reduce the
chance that real emails will be sent out during testing, all email addresses will be replaced
by a dummy address in the 9.0 test databases.

The dummy email address is: hrsa-null@[Link] This address is maintained by ITS.
All incoming emails are sent to a dump area where they are saved temporarily.

L:\U\ 9.0 \ A \01 \01 \Project [Link] 10/12 Last Revised: 7/26/2010
Scope
The address replacement will apply to all ID’s where the user’s account is not locked. In
other words, the core project team and testing team will still have their proper email
addresses in the 9.0 test databases. This allows us to receive test emails and logs as
usual.

Caution
There is a risk created by any process such as Mentor that imports new email addresses
into the system. Unless we re-run the replacement script, those new addresses are a
potential hazard.

Programmer Notes

SQR & Crystal Executables

The 9.0 test instance of CS-Link points to executables that reside and run on its-cslnkd.
In the 8.9 world you would access those executables via the “M” drive.

Each Reports Developer will manually map a “T” drive to its-cslnkd in order to rework
and test the reports. The exact path is: \\Its-cslnkd\reports

You can enter that in Windows Explorer and then map a drive or save the shortcut. If
you don’t have access, then send Peter a request. (Programmers only!)

Approach for Re-Working Reports

The approach for the 9.0 upgrade is to maintain complete separation between the 8.9 and
9.0 reports. That is the reason for the separate CS-Link instance and separate machine
for a parallel GateWay and a parallel folder for reports executables.

We start by moving all existing reports into the new folders. Some of them will not
function with 9.0. As reports are re-worked for 9.0, the contents of the SQR and Crystal
folders will become increasingly “cleaner” until all reports are functioning correctly.

L:\U\ 9.0 \ A \01 \01 \Project [Link] 11/12 Last Revised: 7/26/2010
It is essential that the TechTrak Database accurately reflects the state of the reports. The
TechTrak Upgrade section is the main source for the Project Management Tracking
reports which are run in CS-Link Prod.

During the project, any Reports work done in 8.9 has to be replicated in 9.0, tested and
tracked in TechTrak. Be sure to fill in the “Upgrade” section in TechTrak.

At the 9.0 Go-Live, executable reports and CS-Link setups will be migrated back to the
production reports environment. Then the 9.0 project environment will be deleted.

L:\U\ 9.0 \ A \01 \01 \Project [Link] 12/12 Last Revised: 7/26/2010