Compare Reports

PeopleSoft Compare Reports:

• The compare reports are critical tools for the Fit/Gap analysis and determining the effort to re-apply/re-develop customizations.
• The PeopleSoft Compare Reports provide a comparison of PeopleSoft delivered functionality (vanilla) at the new release level to a client’s copy of production.
• The compare process is executed to identify the object and system data differences between current production and new release levels.
• The purpose of the compare report is to identify which customizations, objects and system data to upgrade to the new release level.
  
• The technical team will run the compare process and involve the client/functional team in the analysis to make the appropriate business decisions.
  
• When you review the compare reports always look at the following combinations and take the appropriate action.

Source	Target	Action
Unchanged	Changed*	Keep Target
Changed	Changed*	Copy and re-apply customization
Absent	Changed*	Keep Target
All other		Copy

Generating and reviewing the compare reports valuable insight to the level of customization.

Approach to Compare Report Analysis and Customization:

In a typical upgrade, the following approaches are taken to re-applying customizations:

• Customizations are carried forward where no PeopleSoft conflict exists. These customizations will require careful testing to ensure proper results.
• Customizations where PeopleSoft conflicts exist will be replaced by delivered PeopleSoft objects. If it is determined that these customizations are required in the new release they will need to be reapplied and tested to ensure proper results.
• Most client PeopleCode modifications are typically replaced where PeopleSoft conflicts exist. This is done to ensure the integrity of the new release and requires that any client modification will need to be reapplied manually.
• Currently there is no delivered PeopleSoft process for comparing Message Definitions, SQR, SQC, and Crystal Reports. Modifications to these delivered PeopleSoft components will need to be manually identified and included in the upgrade process.
• Customizations to components of Process Scheduler (Process Types, Process Definitions) will be identified through the compare process and included in the upgrade process.
• Custom indexes for performance reasons will be evaluated during the upgrade process to determine appropriateness of the index in light of key structure and data distribution changes. All effort will be focused on ensuring no performance degradation.
• Modifications required for external interfaces will be identified through the analysis and design process included in the upgrade project.

Compare Report Error

Error while running the compare report:
Records Application Upgrade Compare started: 2007-11-22-10.50.37 (62,6)
System Error : SQL error. Stmt #: 6962 Error Position: 0 Return: 1 - End of fetch (SQLSTATE PS001) (62,16)
System Error : RUN RECSTATS FOR TABLE (PSPROJECTWORK,LOW) (62,16)
Records Compare Report Created : c:\temp\HC9_MP1_ML\Upg00Records.prt (75,9)
Internal Error: invalid transaction handle instance passed from SamDestroy 0: 70 vs 0

Resolutions:
1. In compare report window UNCHECK the Update Project Item/Child Status option .
2. In configuration manager - CHECK the Disable DB Stats box

Tuxedo 8.1- Unable to connect 3-Tier Windows Client with 128 bit encryption

xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">






href="When%20the%20WSL%20encryption%20is%20set%20to%20128_files/filelist.xml">

When the WSL encryption is set to 128, though the domain boots,
user is unable to login. It gives an error,

 

Network API error – unable to connect to appserver because of
possible causes...

 

Tuxedo log shows a warning:

***************: WSNAT_CAT:1229: WARN: A client failed
encryption negotiation

***************: WSNAT_CAT:1229: WARN: A client failed
encryption negotiation

 

Check BEA On-line documentation for the description of
WSNAT_CAT:1229- style='color:#3333FF'>http://edocs.beasys.com/tuxedo/tux65/ style='font-size:11.0pt'>

 

Starting with the Tuxedo 7.1 release, there is no 128 encryption
add on package. The way it now works is that both the client and server need
128 bit license. Hence the solution here is to copy the style='font-size:11.0pt;font-family:"Trebuchet MS";color:#990000'>lic.txtstyle='font-size:11.0pt;font-family:"Trebuchet MS";color:black'> from the
Tuxedo install, $TUXDIR/udataobj to %PS_HOME%\tuxedo\udataobjstyle='font-size:11.0pt;font-family:"Trebuchet MS";color:black'> on your file
server (the location where you are launching the executable to logon 3-tier).style='font-size:11.0pt;font-family:"Trebuchet MS";color:#000033'> style='font-size:11.0pt'>

 

How to find the Jolt patch level in Tuxedo 8.1?

Where can you find the joltpatchlev file in Tuxedo 8.1?

• While Jolt 1.2 is a separate software package from Tuxedo 6.5, Jolt 8.1 is not.

• In Tuxedo 8.1, Jolt 8.1 is packaged together with Tuxedo 8.1. Jolt 8.1 also shares the same patch file. So, there is no longer a "joltpatchlev" file. There is only a Tuxedo patch level because Jolt is a part of Tuxedo 8.1. You can get the Tuxedo patch level from ${TUXDIR}/udataobj/patchlev.

• You can also run tmadmin -v to obtain the Tuxedo patch level. For example,

$ tmadmin -v
INFO: BEA Tuxedo, Version 8.1, 32-bit, Patch Level 091
INFO: Serial #: 616351266349-1322302213900, Expiration 2005-03-10, Maxusers 1000
INFO: Licensed to: BEA Internal Developer
INFO: 128-bit Encryption Package

• You can also look in the Tuxedo userlog. When the BBL boots, you'll see the Tuxedo patch level. Again, there is no Jolt patch level, anymore. Since Jolt is a part of Tuxedo, there is only a Tuxedo patch level.

114536.lcsol19!BBL.15032.1.0: 03-18-2004: Tuxedo Version 8.1, 32-bit, Patch Level 091
114536.lcsol19!BBL.15032.1.0: LIBTUX_CAT:262: INFO: Standard main starting

WebProfile - What is DEV profile and implications of using it?

There is a lot of confusion on what the DEV profile is and also how leaving certain options as delivered would cause larger problems with memory etc. The following resolution explains how certain options in the DEV profile need to be configured for better performance.

There are two options in the DEV profile that must be turned off . They are: "Show StyleSheet inline HTML" and "Show JavaScript inline HTML" both on the "Debugging" page. These options are only intended for use by Tools Support Analysts and Developers to analyze specific problems related to those areas of functionality.

Leaving these options as delivered can place a large drain on server resources.

This issue is resolved in 8.46. Customers on tools 8.44 should manually turn off this option.

PeopleSoft delivered 4 "representative" profiles beginning in 8.44. They are what we think to be good starting points for the 4 kinds of activities most frequently seen at customer sites. They are:
DEV - for application developer use only
TEST - pre-production testing
PROD - production use
KIOSK - production use in a shared workstation setting

PeopleSoft does not recommend using any of the above profiles for other than their intended purposes. Doing so can be the cause of poor performance or security issues.

Change Impact Analyzer - PsCIA

PeopleSoft Change Impact Analyzer (PsCIA) is a tool to evaluate the effect of changes you make on your installation. PsCIA can monitor the impact a Change Package has on your instance... Also, it can moniotr the impact from other changes such as customizations...

PsCIA helps you understand the impact of specific changes you plan to make during an application upgrade.

PsCIA displays several views of analyses in tabular and text views.

PsCIA is delivered with a set of RULES (Typically written in SQL… also includes some rules written in Java) that are used to determine the relationships between definitions.

You can add custom rules to the rules files to assess the impact of additional relationships.

• PsCIA runs on Windows
• PsCIA can be installed as a standalone application, or as a part of PeopleTools Installation, or as a part of Change Assistant (PsCA) installation
• JDBC Drivers must be installed for connectivity to your database platform
• PsCIA uses Type 4 JDBC drivers by default
• JDBC Drivers can be obtained from your RDBMS vendor's website.

Installing Change Impact Analyzer: Execute \setup\PsCIA\setup.exe

Configuring Database Connectivity:

Configuring Rules Files:

Running the PeopleCode and File Pre-Processors:

Setting Report Options:

Using Change Impact Analyzer:

Using the Rules Editor:

Detailed documentation is available in PeopleTools 8.48 PeopleBook. There is a complere 90 odd pages book available for PsCIA. www.peoplesoft.com

Environment Management Framework

Environment Management Framework (EMF) is a product that gathers and publishes PeopleSoft installation, configuration, and update information. It enables you to identify and view data about PeopleSoft environments. You can use EMF to obtain a snapshot of configuration and setup information about the file servers, the web servers, the application servers, the individual hosts, and the PeopleSoft Process Scheduler servers that comprise your PeopleSoft system. EMF also provides a vehicle to carry out commands remotely on different machines on the network, directed by Change Assistant, which uses EMF to apply updates to PeopleSoft installations and configurations. EMF consists of the following core elements:

• An Environment Management agent.

An Environment Management agent is a Java executable. One instance of the agent can run at a time per physical machine. The Environment Management agent initiates communication to the hub and is assigned a unique peer ID. This ID persists and is reused for later connections by the agent.

• The Environment Management hub.

The Environment Management hub is a web application that’s installed with the PeopleSoft Internet Architecture and portal. It’s started along with the rest of the web applications when the user boots the web server. The hub is the broker for all communication between peers.

• The Environment Management viewer.

The Environment Management viewer is a command-line tool that helps customers view data that is retrieved from the Environment Management hub. This data is saved in an XML file that contains data that is specific to individual customers—such as information about environments, software updates, hosts, file servers, application servers, PeopleSoft Process Schedulers, and web servers. Users can view this static data in HTML.

*** Please refer to PeopleBooks for complete coverage.