Here are a few things that you will want to do to your new installation to prepare for installing the database and other components.
Today, we had trouble with a SQL Server installation of PeopleSoft asking for a tablspace. We created a new record, and when we saved it, it asked for a tablespace name. The problem was that we had no tablespaces setup in PeopleSoft. Therefore, we couldn’t pick a tablespace and essentially couldn’t save a new record.
What was more frustrating was the fact the SQL Server does not have tablespaces. On a SQL Server system the tablespace settings are completely ignored. It should not show the tablespace dialog.
The solution was to turn off platform compatibility mode. The compatibility mode allows you to create records that could be migrated to a database such as Oracle. With this option turned on, it will ask you for the tablespace so that it will have it when it gets on the Oracle database. You can turn it on or off in the PeopleTools Options page (PeopleTools > Utilities > Administration > PeopleTools Options).
Is it possible that Oracle might offer PeopleSoft applications as virtual templates? If you haven’t seen my “idea” on Oracle Mix, please check it out and vote for it. Currently, it has 14 votes.
Today Justin Kestelyn commented “Stay tuned.” Does this mean something is in the works? I am tuned!
This is the first part in creating a virtual image with PeopleSoft HR installed. We will use VMWare Server for the virtual machine and the host machine is a linux machine. The PeopleSoft server will be Linux too so that everything is installed from downloads. Of course, this will not be a production ready machine, but it should work great for learning and testing purposes. You can always deviate from the instructions enough to use Windows or other supported tools if you wish.
VMWare server can be installed easily enough using these instructions:
Installation on other host operating systems is not difficult. You should be able to use any host operating system you like assuming that it is supported by VMWare. You can download VMWare Server directly from here:
Once installed, log in and click the create a new virtual machine — click the “Create a new virtual machine” button.
This will open the wizard to create the new machine.
Next, choose a typical image.
Next, choose Linux and Red Hat Enterprise Linux for the version.
Next, choose a name for the new virtual machine.
Next, choose a networking option. If you wish to transfer files using Windows File Sharing, you may want to choose bridged. This gives you the ability to access files from other computers/servers on the network. If you are on a computer with multiple ethernet cards like a laptop with a wired and wireless card, you might want to choose NAT so that you don’t have to worry about which one should be mapped to the machine.
Next, choose a hard drive size. It works best/easiest if you choose a huge size like 100G and don’t allocate now. This makes the hard drive flexible, and you don’t have to worry about trying to make it larger later. The image will take as much as it needs without crashing. If you need to delete files and conserve space later you can and then shrink the hard drive to free up the space on the host.
Finally, click Finish, and you should have a new empty virtual computer.
Here is an error that I ran across and how I fixed it.
Error in EMHub error log:
<Jul 17, 2008 2:53:48 PM EDT> <Notice> <Stdout> <000000> <WARN [ACTIVE] ExecuteT
hread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’ EMF_CATEGORY – Una
ble to register peer com.peoplesoft.emf.peer:id=2 with the EMHub>
Error that PSAgent gives:
ERROR main EMF_CATEGORY – Error while connecting to ‘http://pserv01:8000/PSEMHUB /hub’.
ERROR main EMF_CATEGORY – Error: Internal Exception: – Error registering peer
ERROR main EMF_CATEGORY – Error while connecting to server – retrying attempt 1
The fix was to reset the GUI
select GUID from PSOPTIONS
UPDATE PSOPTIONS SET GUID = ‘ ‘
Then, you need to restart the application server and the web server.
We have had trouble with our interface picking up the wrong file. The client thinks they have put the file in the right place, but the server is looking at a different file for some reason. Placing the date/time in the standard output helps identify these situations. Here is how you can do that:
Local JavaObject &javaFile;
Local JavaObject &javaFormat;
&javaFile = CreateJavaObject(“java.io.File”, “c:\temp\myFile.txt”);
&javaFormat = CreateJavaObject(“java.text.SimpleDateFormat”, “yyyy/MM/dd hh:mm:ss aa”);
MessageBox(0, ” “, 0, 0, File Timestamp: %1”, &javaFormat.format(&javaFile.lastModified()));