Home
November 26, 2013

Final Configuration Tasks for a PeopleSoft CS Install

Awhile back I posted information about how to manually create a PeopleSoft Campus Solutions database, with a note at the end indicating that information about how to setup the necessary web and app servers was forthcoming. This post contains the settings I used to get a web and app server running, in addition to setting up a Process Scheduler domain, compiling the required COBOL dependencies, and configuring Integration Broker. My focus was on getting the Student Records side of CS working, so the information here leans heavily in that direction.

Preliminary Information

If you are using this post as a reference for your own installation and configuration process, you should know that the following assumptions and prerequisites are assumed:

  • A PS CS demo database on Oracle 11g (running on Oracle Linux) already exists, with the database TOOLSREL value at 8.52. I used the steps in this post to manually create the database.
  • A Windows Server 2008 workstation has been configured with all PS installers run previously. See this post for information on how to setup a workstation that can be used in this post.
  • Ability to connect from workstation to database server (two-tier mode) using App Designer and Data Mover has been verified.
  • On Windows workstation, tnsnames.ora has been set up with an entry for the db server pointing to the Private IP (if running on EC2) of the database server.

The database and workstation instances I used on EC2 were both of type m1.medium in the us-east-1b region.

Configuring a New App Server Domain using PSADMIN.exe

  • Opened C:\PSCS_PT852\appserv\psadmin.exe
  • Entered 1 for Application Server
  • Entered 2 for Create a domain
  • Used ENTCSDEV for name of domain.
  • Entered 4 for small configuration template.
  • Entered y to configure domain.
  • Entered 1 to toggle Pub/Sub Servers to Yes.
  • Entered 6 to toggle WSL to Yes.
  • Ensured 16) DBNAME was set toENTCSDEV.
  • Entered 18 to change UserId to PS.
  • Entered 19 to change UserPswd to <password-for-user-PS>.
  • Entered 20 to change DomainID to ENTCSDEV.
  • Ensured 23) ConnectPswd was set to peop1e (note the use of the numeral 1).
  • Entered 13 to load the configuration.
  • Entered 1 to boot the domain.
  • Entered 1 to boot the domain serially.
  • Everything checked out OK; 18 processes started successfully.

Adding App Server Profile to Configuration Manager

  • Opened Configuration Manager.
  • Clicked the Profile tab.
  • Clicked Create.
  • Used ENTCSDEV as the profile name.
  • Used Application Server for Connection Type.
  • Used ENTCSDEV as Application Server Name.
  • Used ENTPS as machine name (ENTPS is the computer name of the Windows instance)
  • Used 7000 as the Port Number.
  • Used <domain-connection-password> as the Domain Connection Password.
  • Clicked Set.
  • Clicked Next, Next, Next, Next, and Finish.
  • Clicked the Startup tab.
  • Clicked Application Server for Database Type.
  • Selected ENTCSDEV as Application Server Name.
  • Used PS as the User ID.
  • Used people as the Connect ID.
  • Used peop1e as the Connect Password (note the numeral 1).
  • Clicked OK to exit Configuration Manager.
  • Opened Application Designer.
  • Signed in as user PS with password <password-for-user-PS> successfully.
  • At this point, App Server is configured, running, and operating normally.

Installing PIA

  • Started C:\PSCS_PT852\setup\PsMpPIAInstall\setup.bat
  • Clicked Next.
  • Used C:\PSCS_PT852 for installation path.
  • Ensured Oracle WebLogic Server was selected.
  • Used C:\WebLogic for web server root directory. Note that the installer should detect the existing installation of WebLogic in that directory, and display the version number next to it (in this case, WebLogic 10.3.4), since I had already installed WebLogic on the workstation.
  • For administrative login and password for WebLogic domain, I left the defaults. The default Login ID is system, the default password is Passw0rd.
  • Created new domain with name peoplesoft.
  • Selected Single Server Domain.
  • Used ENTCSDEV for the Website Name.
  • For port numbers, I left all values at their default; they were as follows:
    • Used ENTPS as the AppServer name.
    • Used 9000 as the JSL port.
    • Used 80 as the HTTP port.
    • Used 443 as the HTTPS port.
    • Set Authentication Token Domain to enterrupt.com; this should be used if you’re going to setup SSL. Leave blank if you’re not going to setup SSL for WebLogic later.
  • Left Web Profile Name defaulted at PROD.
  • Left User ID defaulted at PTWEBSERVER.
  • Left Password defaulted at PTWEBSERVER.
  • Left Report Repository location defaulted at C:\psreports
  • Clicked Install.
  • Installer completed successfully.
  • Rebooted app server as a precaution before continuing.
  • Launched web server via C:\PSCS_PT852\webserv\ENTCSDEV\bin\startPIA.bat
  • Web server entered RUNNING mode successfully.
  • Signed into self-service successfully.
  • At this point, Web Server is configured, running, and operating normally.

Setting Up AE and Running SQRs

  • I am now on Task 7-4 of the PeopleBook, and at the start of part 3 of 3 of Nic Gasparatto’s blog post on database setup.
  • On the Windows instance, via a terminal, run: C:\PSCS_PT852\bin\client\winx86\psae -CD ENTCSDEV -CT ORACLE -CO PS -CP PS -R INSTALL -AI VERSION. Replace C:\PSCS_PT852 with your $PS_HOME and ENTCSDEV with the name of your database.
  • After ~1 minute, the Application Engine program ended normally.
  • Created a shortcut on the desktop to C:\<$PS_HOME>\bin\sqr\ora\BINW\sqrw.exe.
  • Opened sqrw.exe and filled out the following fields:
    • Report name: C:\PSCS_PT852\sqr\dddaudit.sqr
    • Username: SYSADM
    • Password: <password-for-user-SYSADM>
    • Database: ENTCSDEV
    • Report arguments: -ZIFC:\PSCS_PT852\sqr\pssqr.ini -iC:\PSCS_PT852\sqr\ -fC:\temp\dddaudit.htm -keep -printer:ht
  • Clicked OK to run the SQR. Entered ENTCSDEV for database name and left the process name (optional) blank. Report completed after ~8 mins.
  • Viewed the log file at C:\temp\dddaudit.htm; extraneous records were indicated in the TABLE-3 section (PS_PTCHPLC_PROJ_RN) and VIEWS-2 section (PS_PTCHPLC_COMP_VW and PS_PTCHPLC_MKT_VW). Using SQL Developer, I dropped these three objects from the database in accordance with the note in Task 7-6 (page 214) of the PeopleBook.
  • Re-ran dddaudit.sqr; report indicated that no records were found in all sections (a good thing).
  • I opted not to modify database initialization parameters in the ENTCSDEV pfile on the Oracle 11g instance; these modifications are suggested on page 214 (Task 7-6) of the PeopleTools 8.52 Installation for Oracle PeopleBook. In a previous install log, I made these modifications and no performance gains were noticeable.
  • Ran sysaudit.sqr; report indicated OK status for all lines.
  • Ran sysaud01.sqr; report indicated OK status for all lines.
  • Ran setspace.sqr; report indicated that 90 PSTBLSPCCAT records were inserted, report completed successfully.
  • Skipping Task 7-8 (“Running Alter Audit”), as this section was completed in a previous log when upgrading TOOLSREL from 8.50 to 8.52.

Configuring a New Process Scheduler Domain using PSADMIN.exe

  • These steps roughly align with Chapter 10 of the PeopleTools 8.52 for Oracle Installation PeopleBook.
  • Started app and web servers.
  • Logged into portal.
  • Went to PeopleTools > Security > User Profiles
  • Pulled up record for operator PS.
  • Verified that the ProcessSchedulerAdmin role existed for user PS.
  • Added the ReportDistAdmin role to user PS.
  • Pressed Save.
  • Noted that the permission list name assigned to the Process Profile field under the General tab for the user PS is HCSPPRFL.
  • Went to PeopleTools > Security > Permissions & Roles > Permission Lists
  • Pulled up record for permission list HCSPPRFL.
  • Checked the box next to Can Start Application Server?
  • Pressed Save.
  • Moved to Task 10-3-4.
  • Went to PeopleTools > Process Scheduler > Report Nodes
  • Clicked Add a New Value
  • Used ENTCSDEV as Distribution Node Name
  • Verified that Http Information radio button was selected.
  • Used http://ENTPS/psreports/ENTCSDEV as the URL.
  • Web server OS is Windows.
  • Used ENTPS for URI Host.
  • Used SchedulerTransfer/ENTCSDEV for URI Resource.
  • Clicked Save.
  • Moved to Task 10-3-5.
  • Went to PeopleTools > Process Scheduler > Servers
  • Pulled up the record for the PSNT server.
  • Clicked the Distribution tab.
  • Using ENTCSDEV as the Distribution Node Name (the distribution node created a few steps ago).
  • Used 5 for Maximum Transfer Retries.
  • Used 2 for Interval for Transfer Attempt.
  • Checked the box next to Transfer System Files to Report Repository.
  • Clicked Save.
  • Logged out of portal.
  • Opened psadmin.exe.
  • Entered 2 for Process Scheduler.
  • Entered 2 to Create a domain.
  • Entered ENTCSDEV for name of domain.
  • Entered 9 to change UserId to PS.
  • Entered 10 to change UserPswd to <password-for-user-PS>.
  • Verified that 100) ConnectPswd was set to peop1e (note the use of the numeral 1).
  • Entered 14 to change Output Dir to C:\PSCS_ProcessSchedulerOutput
  • Entered 3 to load config.
  • Booted Process Scheduler successfully.
  • Verified that Process Scheduler was operating normally:
    • Signed into portal as user PS.
    • Went to PeopleTools > Process Scheduler > Process Monitor > Server List
    • Verified that recent processes had run successfully, and on the Server List tab, verified that PSNT had status of “Running.”
  • All tasks related to Process Scheduler are now complete.

Switching WebLogic to Use DEV Web Profile Instead of PROD

  • Initially I had set up WebLogic to use the PROD Web Profile, but I learned that if you use DEV, you can set trace flags from the PS portal sign-on page, and when you press Ctrl+J twice in portal, you can get information about the page, component, etc. I haven’t fully explored the trace options, but those will come in useful during testing.
  • Opened C:\PSCS_PT852\webserv\peoplesoft\applications\peoplesoft\PORTAL.war\WEB-INF\psftdocs\ENTCSDEV\configuration.properties.
  • Changed WebProfile=DEV to WebProfile=PROD
  • Rebooted web server.
  • Opened sign on portal page; noticed new “Set Trace Flags” link below user ID and password boxes.
  • Upon signing in, was able to press Ctrl+J twice in Student Center to see various component, page, etc. data.

Compiling COBOL

  • Referencing this post.
  • Opened command window.
  • Ran set PS_HOME=C:\PSCS_PT852
  • Ran set PATH=%PS_HOME%\src\cbl\win32;%path%
  • Ran set COBROOT="C:\Program Files (x86)\Micro Focus\Net Express 5.1\Base"
  • Ran cd %PS_HOME%\setup
  • Ran cblbld C: \temp\compile (ensure there is a space between the “C:” and “\temp\compile”)
  • Compilation process completed after ~8 mins. It gave an error about being unable to compile about 15 .obj files. I do not have a note of this error from my previous COBOL compilations for previous PSCS installations. This may be related to the fact that this is the first Unicode installation I’ve done. The error said “Aborting this process !!! EXEs/GNTs/INTs are not going to be copied/replaced…”, and sure enough in $PS_HOME\CBLBINU, only a few files existed. So I went to C:\temp\compile and copied all of the contents to $PS_HOME\CBLBINU, since it appears as if most of the CBL compiled successfully (and I really only care about SR-related COBOL at the moment).
  • Note that the COBOL directory for this PSCS installation is $PS_HOME\CBLBINU, with “U” for Unicode, whereas past installations used $PS_HOME\CBLBINA for non-Unicode.
  • Verified RemoteCall functionality via portal:
    • Signed into portal as user PS.
    • Went to PeopleTools > Utilities > Debug > PeopleTools Test Utilities
    • Clicked Test under Remote Call Test; dialog box indicated that Remote Call worked as expected.
  • COBOL should now be ready for use. In the event of any problems, I’ll need to explore the above error further regarding inability to compile those .obj files.

Setting up Integration Broker

  • Signed into portal as user PS with password <password-for-user-PS>.
  • Went to PeopleTools > Integration Broker > Integration Network WorkCenter
  • Clicked on the Gateway link in the left sidebar.
  • Replaced the value You must replace this URL.com with http://ENTPS/PSIGW/PeopleSoftListeningConnector
    • Note: Clicking Ping Gateway with the new URL will be successful if you’re on the workstation; it will fail otherwise (as is to be expected).
  • Clicked Load Gateway Connectors; all 10 gateway connectors loaded successfully.
  • Clicked Save.
  • Clicked Gateway Setup Properties.
  • Logged in as administrator with default password password.
  • Clicked Advanced Properties Page.
  • Changed the value for secureFileKeystorePasswd from password to {V1.1}7m4OtVwXFNyLc1j6pZG69Q== (this is the encrypted value of ‘password’ using PSCIPHER)
  • Pressed OK.
  • For Gateway Default App Server:
    • Using //ENTPS:9000 for App Server URL.
    • Using PS for User ID.
    • Using <password-for-user-PS> for Password.
    • Using 8.52 for Tools Release.
    • Using <domain-password> for Domain Password.
    • Leaving Virtual Server Node blank.
  • For default PeopleSoft Node:
    • Using PSFT_HR for Node Name.
    • Using //ENTPS:9000 for App Server URL.
    • Using PS for User ID.
    • Using <password-for-user-PS> for Password.
    • Using 8.52 for Tools Release.
    • Using <domain-password> for Domain Password.
    • Clicked Ping Node; received error message: “Integration Broker Authentication: No node Authentication Option set for node PSFT_HR on Target syst”. This will be resolved when the PSFT_HR node is configured in succeeding step.
    • Pressed Return.
  • Pressed Save, then OK.
  • Clicked Node Network link in left sidebar.
  • Clicked PSFT_HR link.
  • Set Authentication Option to Password.
  • Setting Node Password to .
  • Leaving Default User ID at PS.
  • Pressed Save.
  • Returned to Gateway link, then Gateway Setup Properties, then clicked Ping Node next to PSFT_HR; message indicated successful ping this time.
  • Pressed Save, then OK.
  • Clicked the Node Network link in left sidebar, then scrolled down and clicked Save.
  • Clicked the Configuration Status link in left sidebar; all three components now show that they are configured correctly (green check marks next to each).
  • Clicked the Network Status link in left sidebar.
  • Clicked Ping Status; status check was successful.
  • Clicked Network Integration Status; status check failed due to error: “User PS not authorized to invoke Service Operation GETNETWORKSTATUS”
    • To remedy this, I added the following roles to the PS user via PeopleTools > Security > User Profiles:
      • Integration Administrator
      • Integrations Administrator
    • After adding the roles, I retried clicking Network Status; the status check was successful.
  • Integration Broker is now configured and ready for use.

Configuring Term / Student for Testing

  • As mentioned at the start of this post, I will be using this PS CS instance to work with SR functionality. This final section shows how to roll term data forward from a full term to Fall 2013 (which requires Process Scheduler to be running), allow open enrollment in Fall 2013 at the moment, and term activate a student. I should then be able to sign in as that student and enroll / drop a course, both of which require COBOL to complete successfully.
  • Signed in as user PS.
  • Went to Records and Enrollment > Student Term Information > Term Activate a Student
  • Searching on last name begins with ADAMS
  • Selected record for AA0001 (Kimberly Adams)
  • Added a new activation record via the + sign button.
  • Using PSUNV for Academic Institution
  • Using 0710 for term (Fall 2013)
  • Using 0 for Student Career Nbr.
  • Clicked Save.
  • Went to PeopleTools > Security > User Profiles
  • Clicked Add a new value.
  • Using KADAMS as User ID.
  • Using SYSADM1 as Symbolic ID.
  • Using <password-for-user-KADAMS> as Password.
  • Using HCCPCSSA1010 (CS Self Service - Student) Permission List for the following: Navigator Homepage, Process Profile, Primary, and Row Security (in the bottom section labeled Permission Lists).
  • Clicked ID tab.
  • Using Employee as ID Type.
  • Using AA0001 (Kimberly Adams) as Empl ID.
  • Clicked Roles tab.
  • Added CS - Student role.
  • Added PeopleSoft User role.
  • Clicked Save.
  • Opened a new window and signed in as user KADAMS; successfully verified her access to self-service.
  • As user KADAMS, I tried searching subjects in various terms to find one that had a large number of courses in it. I found that the 2012 Fall term has a significant number of courses loaded in it, so this is the source term I’ll use in rolling term data forward.
  • Returned to my portal session as user PS.
  • Went to Curriculum Management > Roll Curriculum Data Forward > Copy Prior Term’s Schedule.
  • Added a new value; Run Control ID is MQ-2012Fall-to-2013Fall
  • Using 0690 (2012 Fall) for value of Roll From Term.
  • Using 0710 (2013 Fall) for value of Roll To Term.
  • Clicked Save, then Run, then OK.
  • Process was assigned an instance number of 696 by PeopleSoft.
  • Clicked the Process Monitor link; verified that process name SRROLL was running.
  • SRROLL completed successfully and posted successfully; I verified the generated PDF file for the SQR in the appropriate subdirectory of C:\psreports; only text in the report mentioned lack of session definitions for BUSN, CNED, MEDS, and TECH academic careers (not an issue since I only care about LAU).
  • Returned to my session as user KADMS; successfully searched for courses in 2013 Fall.
  • Attempted to enroll in ENGLLIT 100 (Surv Brit Lit); attempt was successful.
    • Due to success of attempt, I will not modify any term or session definitions / time windows.
  • At this point, COBOL and the Process Scheduler have been verified as functioning properly; KADAMS is a term-activated student for Fall 2013 enrolled in one course (ENGLLIT 100).
← return home