Using WebLogic Server Console to Monitor PeopleSoft Sessions

This is Taken from PeopleBooks – PeopleTools 8.49.

TheWebLogic Server console can display a list of established HTTP sessions for that instance of the WebLogic Server. Session Monitoring is automatically enabled for WebLogic. These instructions describe how monitor the single server configuration of PIA. When in production, note that a multi server configuration would be used to perform these steps to the server instance that you intend to monitor, such as PIA1 or PIA2, or both.

1. Start the PIA server.Start the PIA server either using startPIA.cmd(.sh) or, if installed as a Windows service, NET START peoplesoft-PIA.
2. Log on to PeopleSoftLog on to your PeopleSoft application. If possible, log on from a couple different workstations using different PeopleSoft IDs. For the purpose of this test, do not log off.
3. Log on to the WebLogic Server Administrative Console.In a new browser, access the WebLogic Server console at http://weblogichost:port/console and specify the WebLogic administrative ID you specified during the PIA installation. The default ID and password are system/password, respectively.
4. Monitor established HTTP sessions for the PORTAL web application.On the left, use the following navigation to view the list of established HTTP sessions for the PORTAL web application:
   1. Click Deployments, and view the deployment list in the right hand window.
   2. Click PeopleSoft.
   3. Select the Control tab.
   4. Select the PORTAL application module, where the context root of the module is ‘/’.
   5. Select the Monitoring tab.
   6. Select the Sessions tab.

Note. You can customize the list of fields that you want to monitor using the Customize this table link.

BEA Tuxedo Commands & Utilities

http://www.peoplesoftexpert.com/mediawiki/index.php/Bea_Tuxedo

The above link gives a list of BEA Tuxedo Commands and Utilities.

PeopleTools client installation Batch file

To install PeopleTools client on individual machine, you may create a batch file with the folloiwng lines in it and execute it to create Peopletools Client.

@echo off
[PS_HOME]\bin\client\winx86\pscfg -clean -quiet
echo Setting up PeopleTools Environment
[PS_HOME]\bin\client\winx86\pscfg -import:[PS_HOME]\peoplesoft.cfg -setup -quiet

[PS_HOME] could be like C:\PSFT\FN88PRD\

peoplesoft.cfg is the configuration file.

PeopleSoft Project Management

PeopleSoft Project: PeopleSoft Project is a temporary endeavour undertaken to create a unique peoplesoft software product. Installing PeopleSoft Payroll module is an example of peopleSoft project. This Payroll module will take care of the companies payroll related requirement.

Types of PeopleSoft Projects: Following are the types of Peoplesoft projects: 

1. New Implementation: In this category, one or more new modules of PeopleSoft are installed, configured. A company could implement Payroll and Benefits Administration module to replace its legacy payroll system. Another company could implement General Ledger, Accounts paybles and Purchasing module to start a new accounting, purchasing and payables system.
2. Upgrade & Patch application: PeopleSoft is improving its lines of software and keep releasing new versions. Along with the release of new versions, PeopleSoft may also stop supporting older versions. This makes all clients who have older versions need to upgrade the PeopleSoft system to newer versions. This also could involve just PeopleTools upgrade. The complexity of the project depends on two things, from which lower version to which higher version the upgrde is about and level of customization done to vanilla software.
3. Custom Development Projects: PeopleSoft venilla software may not be adaquate for many clients, and obviously they need to customize the PeopleSoft to their requirement. Normally more custom developments happen in the area of reports, interfaces and conversion.  

 Project Life cycle:

 Methodology: 8steps methodology could suit almost all kinds of PeopleSoft projects.

1. Initiation
2. Planning
3. Design & Development 
4. Monitor and Control
5. Testing and Training
6. Deployment
7. Post production support
8. Close

8steps Methodology details: A exhaustive list of components of each step is given below.

Initiation

• Project feasibility Study
• Develop Project Charter
• Develop Preliminary Project Scope statement

 Planning

• Develop Project management plan
• Scope Planning
• Scope Definition
• Create WBS
• Cost Management Plan
• Quality management plan
• Staffing management plan
• Communications plan
• Risk management Plan
• Procurement management plan
• Activity Defnition
• Activity Sequencing
• Actiivty Resource estimating
• Activity Duration estimating
• Schedule development
• Cost Estimation
• Cost Budgeting
• Quality Planning
• Human Resource Planning
• Communication Planning
• Risk Identification
• Qualitative Risk Analysis
• Quanititative Risk Analysis
• Risk Response Planning
• Plan purchase and Acquisitions
• Plan Contracting

 Design & Development

• Direct and Manage Project Execution
• Detailed design specification functional
• Detailed design specification technical
• Development of objects/code
• Perform Quality Assurance
• Acquire Project Team
• Develop Project Team
• Information Distribution
• Request Seller responses
• Select sellers (contract Management planning)
• Schedule control 

 Monitor and control

• Monitor and Control Project
• Integrated Change control
• Scope verification
• Scope Control
• Schedule control
• Cost control
• Perform Quality control
• Manage Project Team
• Performance reporting
• Manage Stake holders
• Risk Monitoring and control
• Contract Administration 

Testing and Training

Unit testing
System testing
User Acceptance Testing
User training 

Deployment

•  Deploy the product to production

Post production support

• Post production support

Close

• Close Project
• Close Contract
• Lessons learned documentation 

 

Related articles in other blogs:

• IT Toolbox – PeopleSoft Project Management
• PeopleSoft Wiki -starting-a-peoplesoft-project

Log file in Application Engine

A typical example of Log file creation in application engine using peoplecode is given below.

local File &Log_file;

&Log_file = GetFile(“c:\temp\logfilename.txt”, “W”, %FilePath_Absolute);

&Log_file.WriteLine(“Begin Process : ” | %Datetime);

&Log_file.close()

But if you have to use the same log file across the sections within an application engine, then
Declare the file as global in one of the initial step as given below.

Global File &Log_file;

&Log_file = GetFile(“c:\temp\logfilename.txt”, “W”, %FilePath_Absolute);
&Log_file.WriteLine(“Begin Process : ” | %Datetime);

Then in any following section’s peoplecode step, declare the global variable and start writing to the file.

Global File &Log_file;

&Log_file.WriteLine(“Write anything here”);

Don’t forget to close the log file at the end of application engine.

Global File &Log_file;

&Log_file.close()