Automated PeopleTools Installation – And More!

Ever got the go-ahead for an upgrade or installation of PeopleTools, looked at all your application and web servers, and thought “Man, if only there was some way to automate all these installs”?  Me too.

Sadly, Oracle does not make this easy to do.  The “” files written by the install processes are usually incomplete and can’t actually be used to reproduce an installation.  Fortunately, through the magic of Java decompilers, InstallShield 2013, and hard work, I’m here to share working files for not only things that come with Oracle-generated examples, but PeopleTools itself.

I think the most obscure automated installation is PeopleTools, so I’ll start there.  You can find the PeopleTools file you can use to structure your own installation on my GitHub. Just look at some of those names – USER_INPUT_RESULT_14?  Way to make it easy.  Edit that file to reflect your environment and database type, then just use “setup.exe -f” to silently and automatically install PeopleTools.  Of course, why stop there?  I’ve also written PowerShell wrappers for both installing a new Tools environment and upgrading an existing install to a point release.  These scripts handle your error checking during the process and the upgrade script will automatically update your PIA installer files on a file share while preserving your custom for your PIA automatic installs.

Speaking of PIA automatic installs, some people know that Oracle provides a skeleton for PIA in the \scripts directory of PsMpInstall.  For those that didn’t, you can find a usable for PIA here.  I have a PowerShell wrapper for the PIA install, but it’s a fairly simple process to call the PIA executable with the file.  Nicholas Gasparotto did a nice write-up  – although he is on Linux the basic steps are the same.

We’ve now got our PeopleTools and PIA silent installs covered, but how can we do the prerequisites too?  We need to install Tuxedo on the application servers and WebLogic on the PIA servers.  Never fear though…

Oracle has a write-up on unattended Tuxedo installs on their site.  Maybe I’m slow but I didn’t find it too easy to follow right off the bat.  So, grab your Tuxedo file here and make it easy on yourself by just having to customize for your environment.  Then, just follow Oracle’s instructions to call the installer with your file.

But what about Tuxedo Rolling Patches?  We don’t want to move on without those, right? I have a nice PowerShell wrapper for the process of installing an RP that takes care of all the steps in that procedure, including uninstall, cleanup, error handling, etc.  Easy, and better, automated.

WebLogic is another product Oracle wrote a guide for silent installation for.  But if you don’t want to read all that and write your silent.xml, get yours here! Oh, and there’s also another PowerShell wrapper for the install process.  It’s not as involved as the others though.

Again, what about WebLogic Patch Set Updates? Grab your PSU PowerShell wrapper and automate those installs away.

I left out JDK automated installs because that process is fairly well documented in my opinion.  I do have a PowerShell wrapper for that as well that takes care of uninstalls, error handling, and other minor stuff – if anyone wants it leave a comment and it can be another post.

Want to take all that to the next level?  Set up a file share, get all your properties and XML files in line, then convert those scripts to SCCM packages.  Now, you can deploy installs or upgrades to site collections and never even have to log in to a machine.

If something gets confusing let me know and I’ll try to help if I can.  Converting all these steps to SCCM packages has really changed the way I handle upgrades and installs for our PeopleTools environments.

6 thoughts on “Automated PeopleTools Installation – And More!”

  1. Do you have experience automating the PeopleTools 8.54 installation? I am trying to use SCCM’s task sequence functionality to automate the installation of a PeopleSoft Web Tier, but I am getting stuck at the PeopleTools install as I am not finding a method of automating it. Any help would be greatly appreciated.

    1. Hello, thanks for stopping by!

      From testing that I’ve done, the file on my GitHub page is working with Tools 8.54. The arguments to the installer are the same as they were for 8.53.

      What I’ve tested in our environment is making a package in SCCM that calls the Install-PeopleTools.ps1 PowerShell wrapper on GitHub. Then, I deploy this package to a collection of application servers and the script runs, calling the installer with the unattended installer file. We keep the PowerShell scripts on a network location and pass that location to the package – if you go this route you’ll need a code signing certificate and the scripts have to be signed. It might be possible to do this as an application instead of a package, but I haven’t given that a shot yet. You should just be able to use setup.exe for the executable and -f for the command line arguments.

      We haven’t worked much with task sequences for SCCM, but if you were to create the Tools installer package as above and add it to the task sequence, this should get the unattended installation to work. You’d probably need to add more logic in the PowerShell script to determine whether or not the installation was done, so it didn’t try to move on before the Tools install completed.

      If you have any more questions or input please let me know – the SCCM automation is near to my heart as it’s something I am working towards as well.


    1. Hi!

      Sorry for the delay in responding, I haven’t been keeping up with the blog as much as I should. I haven’t personally tried the unattended installation in *nix but from what I can tell the I have up should work the same way – you’d just provide the same arguments to that I specify for setup.exe as far as I know. If you try it and it works let me know.

      Thanks for stopping by!

    1. The license key only tells the PeopleTools installer what database type you have, so for an unattended installation you don’t need it. That part is handled by a section in the installer file:

      #Choose database type
      #Valid Values:
      #ORA = Oracle
      #INF = Informix
      #DBX = DB2 for Unix/NT
      #SYB = Sybase
      #MSS = Microsoft SQL Server
      #DB2= DB2 for OS/390

      You still need to pay Oracle for support though in order to be license-compliant.

      Thanks for the feedback!

Leave a Reply

Your email address will not be published. Required fields are marked *