When configuring the Report Repository using the Scheduler Transfer tool you will want to configure the node using the http/https settings:

Home > PeopleTools > Process Scheduler > Report Nodes

The URL will be the same as it always is, this variable is primarily used for the link in process monitor to view the reports/logs.  The URI host is usually set to the web server name, however, if you are using a load balancer you might wish to use one web server to handle the traffic or configure it to go to an internal site that can handle the balancing.  URI Port will be the port of the webserver, typically the regular access port, but if you are using a balancer and it is redirecting the port may need to setup with the internal port number.  URI Resource is the class that handles the transfers, it should be:

SchedulerTransfer/<piasite>

Be very careful of case here.  See picture as an example.  Lastly, you will want to make sure that the user that is handling the process scheduler in question has the Role: ProcessSchedulerAdmin, and that the default Local Node has been configured to have a password associated with it (Home>PeopleTools>Integration Broker>Nodes).

When doing the initial installation for most PeopleSoft environemnts you need to do several installations one of them being Cobol Server Express if you are running Cobol on a Unix environment.  Most PeopleSoft 9.1 applications support using version 5.1.

After you get the license installed, you need to ensure that the license manager is running.  Three commands will come in handy here:

1. Stopping License Manager, you need to be root to do this:

cd $COBDIR/lmf
lmfgetpv k

2. Show Status of License Manager: (If running it will return the version, if stopped it will report it is stopped)

cd $COBDIR/lmf
lmfgetpv

3. Staring License Manager, you need to be root to do this:

cd $COBDIR/lmf
sh ./mflmman

You can change the directory to {COBDIR}/aslmf and then run ./apptrack If this is the first time it will ask you to set a password or enter in 6 blank spaces to set the password to null. Once the password is set, you can select from the list of options to show a license summary. This should show your license you have installed, and if it doesn’t you can install your license from this menu.

If you are using a LMF Development License, you can install it by going to {COBDIR} and running the command:

sh mflmcmd

Enter I to install a license, enter in your Serial and License numbers you received from Oracle. You should now be able to go back into apptrack and see the installed license.

Just to drive the system administrator nuts, for some reason Redhat sysctl parameters by default are not robust enough to handle starting up even a small application server. There are several cases on My Oracle Support that explain how to set the variables but at a minimum I found this to a good starting point:

fs.file-max = 65536
kernel.msgmni = 512
kernel.msgmax = 1048576
kernel.msgmnb = 1048576
kernel.shmmni = 4096
kernel.shmmax = 33554432
kernel.sem = 250 256000 64 1024

You can add/modify these entries in the sysctl.conf file (/etc/sysctl.conf). Once they are modified you can put them into effect by issuing sysctl -p. If you want to do a change temporarily you can issue: sysctl -w parameter=value.

I just started working for a new client, and they have a very long domain name, and then the new servers they created for their new HR 9.1 environment were on a subdomain as well.  So the server name (LMID – logical machine ID) exceeds 30 characters in length, which happens to cause Tuxedo to get very angry.  I found the easy way to resolve this issue is by doing the following:

Step: 1
Add a new environment variable called PMID (physical machine id). The value I set to simply the machine name (without the domain).
export PMID=psappmachine1

Step: 2
Verify that there is a psappmachine1 reference in the hosts file so that the IP can resolve
more /etc/hosts

Step: 3
Change the psappsrv.ubx file that is in the $PS_HOME/appserv directory. Change all references to {MACH} to the value of PMID, making sure that the case matches exactly.
vi psappsrv.ubx
:%s/{MACH}/psappmachine1/g

Step: 4
Build a new domain for the application server and there should be no CMDTUX_CAT:122 or 868 errors.

This is a super awesome Red Paper from Peoplesoft (Oracle), on clusering and high availability.  Should be in every system administrators handbag.  Tools Clustering