PeopleTools 8.50.14 and 8.50.15 black listed

2 versions of PeopleTools 8.50 were black listed by Oracle, for security and stability issues.

PeopleTools 8.50.14 and 8.50.15 are not available any more frome Oracle Support, and you are advised to patch to the latest release.

While I'm writing this note, 8.50.19 is available, but when we discovered the issue we decided to patch to the latest release available (8.50.17) where the security issue is solved.

Update PSIGW configuration without restarting the PIA

If you need to reconfigure the PeopleSoft Integration Gateway, you can avoid downtime for users by redeploying only the Gateway.

With this methodology, you don’t need to restart the PIA.

1^st modify the gateway configuration files as desired that reside in:

$PIA_HOME/myWebserver/applications/peoplesoft/PSIGW.war/WEB-INF

You can modify the 2 following files:

integrationGateway.properties (the gateway parameters)

gatewayUserProfile.xml (the gateway user and password)

2^nd use the Deployer tool to redeploy the PSIGW module

cd $PIA_HOME/myWebserver/bin

. ./setEnv.sh

a) run the following command if you are running a one PIA server

java -classpath weblogic.jar weblogic.Deployer -adminurl myserver.mydomain.net:9999 -verbose -username system -password mypassword -name peoplesoft -redeploy -targets PSIGW@PIA

a) run the following command if you are running a PeopleSoft Cluster

java -classpath weblogic.jar weblogic.Deployer -adminurl myserver.mydomain.net:9999 -verbose -username system -password mypassword -name peoplesoft -redeploy -targets PSIGW@peoplesoftCluster

c) or run the following command if you want to redeploy the PSIGW module on both PIA and PeopleSoft Cluster

java -classpath weblogic.jar weblogic.Deployer -adminurl myserver.mydomain.net:9999 -verbose -username system -password mypassword -name peoplesoft -redeploy -targets PSIGW@PIA,PSIGW@peoplesoftCluster

The output will look like this:

<May 20, 2011 9:51:36 PM GMT+10:00> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, peoplesoft [archive: null], to PIA .>

Task 2 initiated: [Deployer:149026]redeploy application peoplesoft on PIA.

Task 2 completed: [Deployer:149026]redeploy application peoplesoft on PIA.

Target state: redeploy completed on Server PIA

Monitoring PeopleSoft WebLogic Domains with Enterprise Manager

A great feature you can use in Enterprise Manager is to monitor WebLogic Domains, part of Oracle Fusion Middleware.

Either, you create a single-server domain, or multi-server domain, you can monitor PIA, RPS and WebLogicAdmin (console).

Before registering a WebLogic Domain in EM, you need first to activate IIOP (Internet Inter-ORB Protocol) in the WebLogic Administration console, or EM will not be able to communicate with the servers.

- connect to the WebLogic Administration console:

- http://myhost:9999/console

- navigate to Environment > Servers

- repeat this steps 1 to 4 for each server you want to monitor in EM, ie for PIA:

          - 1. click on PIA

          - 2. click on Protocols tab

          - 3. click on IIOP tab

          - 4. check the box “Enable IIOP”

PeopleSoft Voucher upload configuration to work with a load balancer

You may have to modify the Excel Macro for Voucher upload, in case you are using a load balancer in front of your Web servers.

The reason for this is that the technology used in this macro (xml link) does not behave the same as a direct connection to the PIA.

Search for this code in the macro:

        xHTTP.Open "POST", Sheets(1).Range("K2") & "/Excel_Voucher_Import", False

And replace it by:

        xHTTP.Open "POST", Sheets(1).Range("K2"), False

Edit cell K2 and set it to :

https://[fqdn]/psc/ps/EMPLOYEE/ERP/s/WEBLIB_AP.VOUCHER_ID.FieldFormula.Iscript_Excel_Voucher

How to kill a socket used by PeopleSoft Application server (JSL), using rmsock on AIX

In project phase, when you build and rebuild environments, you might face the issue where a port is not released correctly by the host.

Here is an example to identify which process is assigned to this port, and how to release it (kill).

psft@AIXHOST0001(ORACLE_SID):/peoplesoft/HRMS91/pt850x/appserv> netstat -@aA | grep 9700

Global  f1000e0007054bb0 tcp4       0      0  AIXHOST0001.9700  *.*                LISTEN

psft@AIXHOST0001 (ORACLE_SID):/peoplesoft/HRMS91/pt850x/appserv> rmsock f1000e0007054bb0 tcpcb                

The socket 0x7054808 is being held by proccess 13959176 (JSL).

psft@AIXHOST0001 (ORACLE_SID):/peoplesoft/HRMS91/AU/pt850x/appserv> kill -9 13959176

Installing PeopleBooks 8.50 on Linux/Unix

You may have faced issues installing PeopleBooks Linux/Unix ?

./setup.aix  -is:tempdir /temp -i console

There is a bug with the installer that is looking for a previous JRE release (1.4.x).

You can use the Java installer instead :

java -jar setup.jar -console

If you issue the following command:
./setup.aix  -is:javahome $/usr/java5 -is:log /tmp/pbooks.log -is:tempdir /tmp -i console
 
You can verify in the logs, that the installer is looking for a 1.4 JVM …
 
Finding a JVM
Checking user specified Java home directory => $/usr/java5
Verifying JVM at $/usr/java5/jre/bin/java
   for JVM: AIX Java 1.4.X by IBM
$/usr/java5/jre/bin/java does not exist
Verifying JVM at $/usr/java5/jre/bin/java
   for JVM: AIX Java 1.4.X by IBM
$/usr/java5/jre/bin/java does not exist
Initiating JVM search based on hints...
Searching for AIX Java 1.4.X by IBM using platform hints
Searching for AIX Java 1.4.X by IBM using path hints
Checking path hint /usr/java14*

nVision drill down bugs in Japanese with PeopleTools 8.49 and 8.50

nVision drill down issues can be very difficult to diagnose, especially if you use drill down report with Japanese data.

You must have specific java librairies on you Web server if Linux/Unix,and specific DLL on the Windows server generating the drill down documents.

This issue is applicable to both PeopleTools 8.49.x and 8.50.x

Contact me if you need additional details.

Configurez votre clavier en Français sous Solaris 11 Express - Set Solaris 11 Express keyboard to French

>>> Français
Si vous avez essayé la machine virtuelle Solaris 11 Express avec VirtualBox 4.x, vous avez peut être rencontré des problèmes pour configurer votre clavier en Français …
Voici une astuce qui devrait régler votre problème !

Connectez-vous en user root, et créez le fichier :  /etc/hal/fdi/policy/10-x11-input.fdi

<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
  <device>
   <match key="info.capabilities" contains="input.keys">
    <merge key="input.x11_options.XkbRules" type="string">base</merge>
    <merge key="input.x11_options.XkbModel" type="string">sun_type6_usb</merge>
   <merge key="input.x11_options.XkbLayout" type="string">fr</merge>
  </match>
</device>
</deviceinfo>

Redémarrez votre VM, et vous devriez pouvoir enfin vous connecter en Français dès l’écran de login.

>>> English
if you tried Solaris 11 Express Virtual Machine in Virtual Box 4.x, you may have faced issues with your French keyboard not detected …

To fix this issue, create a file /etc/hal/fdi/policy/10-x11-input.fdi

<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
  <device>
   <match key="info.capabilities" contains="input.keys">
    <merge key="input.x11_options.XkbRules" type="string">base</merge>
    <merge key="input.x11_options.XkbModel" type="string">sun_type6_usb</merge>
   <merge key="input.x11_options.XkbLayout" type="string">fr</merge>
  </match>
</device>
</deviceinfo>

Then restart your VM, and your French keyboard should be active from the login prompt.