This message gets annoying working with PUM images. The browser complains about the SSL certificate even though it’s just a temporary one and you’re not working on production or sensitive data.
So, I worked through telling my browser to trust the certificate. Here are my notes…
I ran into an issue where I couldn’t figure out the keystore password. I thought for sure that the PUM configuration script asked me for a password. Apparently, it didn’t. Here’s how I figured out.
I started an article with my notes on getting PUM running over 2 years ago, but I never followed through on it. Now, everything is changed, and I’m starting over.
So, here’s my notes on getting HCM PUM 22 running.
I have an experimental Oracle Linux VM that I am playing with, and I am going to want to try to run some desktop applications inside the image. So, I want to enable the X Window Graphical Environment.
Here’s the command to install it all:
yum groupinstall “X Window System” XFCE
Then, I had to edit the /etc/inittab and change the “3” to a “5” (on the last line).
When I rebooted, it didn’t offer the login screen. I had to press Alt+F2 to get to a regular login. Then, I installed 2 more groups:
yum groupinstall Desktop “General Purpose Desktop”
I am not sure that this got me an XFCE Desktop, but it got me what I needed.
I have been reading up on PeopleSoft’s new Update Delivery model. It sounds very interesting, but one of the things that I caught was the fact that they will be delivering a Virtual Machine on Virtual Box where you can extract the updates that you need. You can watch a nice video on the topic from Oracle’s YouTube channel:
This is a continuation of my Windows 8 PeopleSoft Installation. Previously, I installed WebLogic. In this step, I plan to create the application server, batch server, and web server. After this step, we should be able to log into PeopleSoft.
This is a quick blurb about an installation problem that I ran into. Unfortunately, I didn’t get screenshots grabbed or exact error messages written down, but maybe this will still help.
The first problem was that near the end of the PeopleTools 8.53 Installer, the program gave me a window describing the usage options for the Windows installer. It was like the PeopleTools installer had called another installer but hadn’t passed the correct arguments. I got the window twice, so I am thinking that it tried to call it twice.
The next problem was that App Designer wouldn’t start. I didn’t try any of the other client programs like Data Mover, but I suspect that they would not have worked either. The error message was something about a missing DLL file.
The PeopleTools install notes had a note about the VC++ Run Time. (Page 142 of the PDF / 116 on paper of the Oracle Database one.) The solution was to simply install the Microsoft Windows machine’s CRT files. The installer is located in <PS_HOME>\setup\psvccrt. I was on a 32-bit machine, so I just ran the psvccrt_retail.msi.
In case you haven’t already noticed, PeopleTools 9.2 is out and available for download! You can download it from edelivery.
Just had to add one more screenshot … PeopleTools 8.53 starting up the new version:
I ran across Andrej Koelewijn’s article about Vagrant over a year ago, and I have been wanting to explore it ever since. I do a lot of playing around with different things, and Vagrant looked like it would be a cool, quick way to spin up a new image of an OS. I would love to get it to the point of being able to spin up an instance of PeopleSoft. I am no where near there now, though.
This is just my first run through. I set an easy goal of trying to get Oracle XE running on Ubuntu via the repositories. Unfortunately, I learned that that repository isn’t worth the time. Still, it was a fruitful exercise, and I definitely will be playing around more with Vagrant.
Follow along if you like…
I got the following error message after installing the PeopleTools 8.52.10 patch:
PeopleTools release (8.52.10) for web server/ Application Designer ‘lxdevweb02.pugetsound.edu’ is not the same as Application Server PeopleTools release (8.52.02). Access denied.
CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ApplicationException: TPESVCFAIL – application level service failure
To fix the problem, I just reconfigured the Application Server.
I found that I needed to change something to make it think that it needs to load the configuration. So, I changed the WSL option. After loading the configuration, I changed it back and loaded it a second time.
After booting the Application Server again, everything worked fine. The instructions didn’t say anything about reconfiguring the Application Server, but I found that I had to do it. I don’t know if this has anything to do with it, but I did change my PS_HOME environment variable as part of the patch installation. The tools version (patch number included) is in the path for my PS_HOME.
Now, on a side note, if you get just this message:
CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ApplicationException: TPESVCFAIL – application level service failure
The problem is probably that the web server cannot talk to the application server. Here are a few things to check:
I hope those thoughts help more than just me.