Remastered 9.2 Application media

Some of you may have noticed this already but I recently saw that some of the PeopleSoft 9.2 Application media had been remastered.

  • HCM 9.2 was updated on E-delivery at the end of October.  It includes patches from Update Image 9.  Image 9 was also released as a certified Upgrade Demo Image.
  • FSCM 9.2 was updated at the end of September.  It includes patches from Update Image 5 which also released as a certified Upgrade Demo Image.
  • ELM 9.2 was updated in early October and contains patches from Update Image 6.  As with the others it also is a certified upgrade image.
  • CRM 9.2 looks updated at the end of September as well, but it does not indicate if any patches from an Update Image are included.  Since there is not currently a supported Upgrade Image other than CRM 9.2.000 it would not make sense that this media include the patches.  This may indicate it was updated because PeopleTools 8.53 was pulled and 8.54 added to the collection.  I have not downloaded it to look.

In addition the other change I noticed was that all PeopleTools 8.53 media has been pulled.  If you need something from the 8.53 media set you will need to open a non-tech SR.  This seems to be a change from the previous strategy of keeping the current plus one previous Tools set available for download.  I’m not on E-delivery all that often so who knows, maybe they changed that a while ago.

Either way, those looking to start upgrades or may have recently started the process using media they downloaded prior to end of September should evaluate where they are and possibly grab this new media.  Jumping straight to a Update Image would be beneficial.  Those looking to avoid PeopleTools 8.54 for some reason may want to avoid these though because at least HCM, FSCM, and ELM will already be 8.54 PeopleTools in the database.

New DataViewer Tool released

I’ve finally WeblogicRealTimemade a new version of the DataViewer tool available for download.  This new version includes new stand alone features as well.  I’ve added Real Time Weblogic monitoring and an Access Log Parser.  It also includes all the old charts for the Weblogic and Tuxedo monitor data files and some new ones.  This version requires Java 8.  I won’t be making new updates to the old version, but it will still be available for download if for some reason you can’t use Java 8.  I’ve posted new screenshots on the Monitoring Tools Screenshot page.  Another little improvement is the application should remember your last viewed data file and attempt to use it again the next time it is started.  Same goes for the data entered on the Real Time Weblogic Monitor configuration.  Download it here.  And read how to use the new viewer on the DataViewer page.


Monitoring Tool updates

I have finally uploaded some updated versions of my monitoring tools. I’ve made only minor updates to the Weblogic monitoring tool. I created versions that work with Weblogic 9.2 and Weblogic 8.1, but they will be available by request only.  The viewer has had a few items added and can now be used to open the files generated from the newly released (but not really new) app monitoring tool.  Continue reading

New PeopleSoft Monitoring Tools Coming Soon

As a PeopleSoft Admin, I’m interested in numbers.  Numbers from everything; sessions, queues, processes, load, errors, memory, CPU, IO latency… the list goes on.  These numbers tell us what is occurring in our environments.  Even better we can use them to build patterns and trends.  If you don’t know your numbers how do you know what is occurring in your environment?

I’ve found over the years most PeopleSoft Admins don’t have all the numbers they need to do their job well.  There are several reasons for this that I’ve seen, the most common being:

  • A nice 3rd party solution is just too expensive
  • Other solutions require too many resources or are unwielding to manage or learn

psr outputThere are lots of numbers out there for the taking and they want to be seen.  Some of the obvious favorites are session counts, jvm stats, and thread / servlet info from Weblogic.  There are also the old trusty values kicked out from Tuxedo with psr, pq, pclt, and the less commonly used psc.  I’m not even going to bring up Database numbers today (that’s a whole different party).  These numbers are usually easy enough to get to but are provided in one time snapshots.  Like what you get from psr or the Weblogic  Admin Console.  In order to learn more we need collect these somehow to review historically.

Is a Picture Worth a Thousand Words?

Weblogic Open Session Count I wanted something simple to use, fast to deploy, grabbed at least the basics, and was platform independent.  There are lots of options out there but nothing seemed to fit the qualities I was looking for.

Last year I started working on my own set of tools that meet my criteria.  What I have now is still in the very early stages.  I’m writing several small utilities, that when put together, can give you a nice picture of what your PeopleSoft system has been doing.  The concept is to keep things simple.  I want to keep installation and configuration, start to finish, under 10 minutes.

Currently, I have a working Weblogic component and have started working on the Tuxedo Weblogic Heap Free Percentagemonitoring component.  The graphs here are samples of an environment I’m currently monitoring.  These apps are currently in private beta testing phase.  However I am considering opening them up to members, if I can get them cleaned up a bit more (maybe in April, free time permitting). If you’re interested please register (it’s free) and watch for updates.

Determining psjoa.jar Version

I recently answered a question on the OTN forums that I thought was interesting and figured I’d detail it a little further here.  Someone was using psjoa.jar to interface with a remote PeopleSoft system and wanted to verify what PeopleTools version a specific psjoa.jar file was from.  First a little background on psjoa.jar.  This file is a package of java classes that can be used to interface with PeopleSoft.  It’s required by a multitude of 3rd party applications and adapters which wish to interface with PeopleSoft.  It can also be used to expose Component Interfaces to your own Java applications, which I may detail in a future post shortly.

Here’s how I found the version and created the solution:

First it helps to know that psjoa.jar can be found in $PS_HOME/appserv/classes.  So I ran unzip -c psjoa.jar | strings |grep 8.52.  8.52 being my current major tools release version for this file.  unzip -c extracts to stdout and then I piped that to strings and from there to grep.  If your wondering why I ran unzip it’s because the jar contents are compressed which garbles everything useful that strings might give me from each individual file in the jar.

$ unzip -c psjoa.jar | strings | grep 8.52

Okay, so I knew the version was in there a few times and since strings was able to see it, it’s in a readable format.  Now lets find out where exactly, so I unzipped psjoa.jar to a temp directory and I ran find on the directory using the -exec option to run grep -l on every file so I would just get the file name of every file that matches.

$ mkdir /tmp/psjoa
$ unzip psjoa.jar -d /tmp/psjoa/
$ find /tmp/psjoa -exec grep -l 8.52 {} \;

Okay, so I got a few options and these sound promising… promising in that they hopefully won’t disappear in the next version.  So I had half a solution, by grepping for a regex pattern that matches a tools release. So something like

unzip -c psjoa.jar |strings |grep 8″\.”[4-5]

would work, but I was looking for something more (as was the poster since they were on Windows and was trying to build this into something web based on their end I think).  So I imported psjoa.jar into a project in Netbeans to take a look.  After looking at the above classes in Netbeans I found ND would be the best class.  ND is an interface that contained public static final variables only, that’s perfect.  I showed the OP he could just import and then print out the variable TOOLS_REL and build that into a jsp page or however he would like to deploy it.  One thing to remember about this is that final static primitive or String constants will be replaced to their value at compile time, the bytecode will not contain a variable anymore but the value directly.  So just compiling the program with ND implemented will cause every version we check to always be that of the file used to compile and that won’t do us any good.

same version

Notice in the above screenshot both psjoa.jar and psjoa2.jar indicate the same PeopleTools release.  But psjoa.jar is from 8.51 and psjoa2.jar is from 8.52.  So since this a really simple single purpose utility with only one line I created a new ND.class to use at compile time that forced the variable to no longer be constant.  The cloned ND.class is only for compile time, during runtime we find the real file and the compiled code  needs to look up the value from the file every time.  Exactly what I wanted.  Now I have a simple cross platform utility to check the version.

different version

I’ve posted this program in my new Downloads section.  Because PeopleTools 8.53 is now built using Java 7, this utility is best run with the Java 7 JRE.  I compiled it with support back to Java 5, however if your using Java 6 to look at a psjoa.jar file from 8.53 which was built with Java 7 then you’ll get the error “Unsupported major.minor version 51.0” because psjoa.jar itself is not compiled with the backwards compatibility.  51 in the error indicates the ND.class being imported requires Java 7.  PeopleTools 8.49 was the first version to use Java 5, so this version of the utility will be limited to testing 8.49+ psjoa.jar files.  I’ve run it on 8.49, 8.51, 8.52, and 8.53 and it worked on all 4 of those.

New Downloads section

I’ve created a new Downloads section where I will start placing items for download.  Access to the Downloads section will be restricted to those who have registered with the site.  These will be programs and utilities created by me, and as such, are all considered beta unless otherwise specified.  Registration with a working email address is required so I may contact those that downloaded the programs if the need arises.