This discussion is archived
6 Replies Latest reply: Jul 6, 2011 6:17 AM by Nicolas.Gasparotto RSS

PeopleSoft Configuration Script with new HCM 9.1/PT 8.51 template

psadminMD Newbie
Currently Being Moderated
Has anyone used the PeopleSoft Configuration script? Bascially I am trying to figure out if this script and the function the documentation mentions (ovm_configure_pre) is what I would use to establish my own PS_HOME directories?
If I was going to deploy my non-production environments using this template, I would definitely not want to use the delivered directory structure (/opt/oracle... and /home/psadm2...) and am trying to figure out how you can control where the templates creates the PS_HOMEs (if thats possible)? For example, say I want my template to put the PS_HOMEs under /peoplesoft, can I control that using this script? If not, is there some other way to control that? I can't imagine you would be stuck with the delivered directory structures.

Thanks.
  • 1. Re: PeopleSoft Configuration Script with new HCM 9.1/PT 8.51 template
    Nicolas.Gasparotto Oracle ACE
    Currently Being Moderated
    I don't think the template's scripts create (control) the PS_HOME, it's part of the given golden image. On the PSOVM deployment, you can decide or not to install Cobol and PIA, but not Peopletools which is already there (same for Tuxedo and Weblogic).
    I would definitely not want to use the delivered directory structure (/opt/oracle... and /home/psadm2...)
    Whether I understand, these are only used for demo and learning purpose, what's wrong to use these by default ? /home/psadm2 is nothing but PS_CFG_HOME which can be anything. With some effort, you could move these folders where ever you want, taking care of the left space on device though.
    In the end, you could move the folders and create your own golden image for future deployment.

    But right, so far I didn't spent much time on the scripts you are talking about.

    Nicolas.
  • 2. Re: PeopleSoft Configuration Script with new HCM 9.1/PT 8.51 template
    psadminMD Newbie
    Currently Being Moderated
    For demo purposes I have no problem leaving them as they were created. However, according to Oracle's website, these templates are theoretically meant for more than demo and can be used for non-production and even production environments (with some additional configuration).

    I can't imagine if you were going to use the templates for your actual deployment you would be stuck with their default directory structure. Yes, I could move things around, but it might be more trouble then its worth and I would think could possibly cause issues with Weblogic and Tuxedo since those installations always ask for the location of your PS_HOME. If I had to go through all of that pain, I might as well build it from scratch.

    If you or anyone else has any experience with that script or can confirm if I can change the PS_HOME locations using it upon creation, I would love to know that!

    Thanks!
  • 3. Re: PeopleSoft Configuration Script with new HCM 9.1/PT 8.51 template
    Nicolas.Gasparotto Oracle ACE
    Currently Being Moderated
    pspeon2.0 wrote:
    ...However, according to Oracle's website, these templates are theoretically meant for more than demo and can be used for non-production and even production environments (with some additional configuration).
    Not according to the readme documentation coming within the template :
    "+1. Introduction+
    +===============+

    +PeopleSoft HCM templates, allow fast deployment of a small demo HCM environment...+
    +<snipped>+
    +The following considerations were made when these templates were designed:+

    +· This template was built for demo purposes. Out of the box it is not recommended for production use....+"

    Nicolas.
  • 4. Re: PeopleSoft Configuration Script with new HCM 9.1/PT 8.51 template
    Nicolas.Gasparotto Oracle ACE
    Currently Being Moderated
    Hi,

    I spent quite some time on this, eventhough that's much better to use the default delivered PSOVM I'd tend to think. I can say that the folder change cannot be done in ovm_configure_pre or in any other function, too much thing have to be done.
    I have had a look into the ovm scripts running on deployment, as I thought everything is hardcoded in ovm scripts, so that's probably a huge task to go through every single script and modify the string to point to the new one. And still, that would be far not enough to make the all server working. Because all the software are already installed before the deployment (Peopletoools, Weblogic, Oracle) and they keep the directory in configuration files.
    If you really want to change the directory, it will take some effort and time. Frankly speaking, that's not something I do daily...

    Let's assume we want to change the /opt/oracle/psft/pt (default) to /appl.
    As a reminder, /opt/oracle/psft/pt contains not only Peopletools, but all the required software (Tuxedo, Weblogic, Oracle client).
    Here we go.

    To move from the default /opt/oracle/psft/pt to /appl

    *1. First step, change the name of the mount point*
    As root
    [root@psovmfscmfp1 /]# df -k
    Filesystem           1K-blocks      Used Available Use% Mounted on
    /dev/xvda2             7077468    668884   6335572  10% /
    /dev/xvda1               93307     11335     77155  13% /boot
    tmpfs                  1048576         0   1048576   0% /dev/shm
    /dev/xvdb1            12902320   9904384   2604720  80% /opt/oracle/psft/pt <--
    [root@psovmfscmfp1 /]# ls /opt/oracle/psft/pt
    bea  cobol  lost+found  oracle-client  tools
    Let's change the mount point to the new directory
    [root@psovmfscmfp1 /]# more /etc/fstab
    LABEL=/                 /                       ext3    defaults        1 1
    LABEL=/boot             /boot                   ext3    defaults        1 2
    tmpfs                   /dev/shm                tmpfs   defaults        0 0
    devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
    sysfs                   /sys                    sysfs   defaults        0 0
    proc                    /proc                   proc    defaults        0 0
    LABEL=SWAP-VM           swap                    swap    defaults        0 0
    #LABEL=FSCMTOOLS         /opt/oracle/psft/pt     ext3    defaults        1 2 <-- commented
    LABEL=FSCMTOOLS         /appl                   ext3    defaults        1 2 <--
    Then unmount the previous mount point, if it fails, check what is running and kill the process
    [root@psovmfscmfp1 /]# umount /opt/oracle/psft/pt
    umount: /opt/oracle/psft/pt: device is busy
    umount: /opt/oracle/psft/pt: device is busy
    [root@psovmfscmfp1 /]# fuser -m /dev/xvdb1
    /dev/xvdb1:           1496ce
    [root@psovmfscmfp1 /]# ps -ef|grep 1496
    root      1496     1  0 03:10 ?        00:00:00 ./mflm_manager
    root      1681  1500  0 03:51 pts/0    00:00:00 grep 1496
    [root@psovmfscmfp1 /]# kill -9 1496
    [root@psovmfscmfp1 /]# umount /opt/oracle/psft/pt
    Create the new directory and mount (based on /etc/fstab)
    [root@psovmfscmfp1 /]# mkdir /appl
    [root@psovmfscmfp1 /]# mount -a
    [root@psovmfscmfp1 /]# df -k
    Filesystem           1K-blocks      Used Available Use% Mounted on
    /dev/xvda2             7077468    668888   6335568  10% /
    /dev/xvda1               93307     11335     77155  13% /boot
    tmpfs                  1048576         0   1048576   0% /dev/shm
    /dev/xvdb1            12902320   9904384   2604720  80% /appl <--
    [root@psovmfscmfp1 /]# ls /appl
    bea  cobol  lost+found  oracle-client  tools
    [root@psovmfscmfp1 /]#
    Ok, from now the software are stored in the new directory.

    *2. Change the profile (enabled on user's connection)*
    As root, modify /etc/profile to reflect the new directory of every single folder under /appl
    #export ORACLE_HOME=/opt/oracle/psft/pt/oracle-client/11.1.0.7-64bit
    export ORACLE_HOME=/appl/oracle-client/11.1.0.7-64bit
    ...
    #TUXDIR=/opt/oracle/psft/pt/bea/tuxedo
    TUXDIR=/appl/bea/tuxedo
    ...
    #. /opt/oracle/psft/pt/tools/psconfig.sh
    . /appl/tools/psconfig.sh
    #export PATH=/opt/oracle/psft/pt/tools/appserv:$PATH
    export PATH=/appl/tools/appserv:$PATH
    ...
    #export COBDIR=/opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit
    export COBDIR=/appl/cobol/svrexp-51_wp4-64bit
    ...
    *3. Change the psadmin and psconfig files*
    Here is one of the tricky point, when installed, Peopletools created symbolic link and environment variable according to the directory it was installed into, it has to be changed.
    As psadm1, recreate symbolic link /appl/tools/appserv/psadmin
    [psadm1@psovmfscmfp1 appserv]$ pwd
    /appl/tools/appserv
    [psadm1@psovmfscmfp1 appserv]$ rm -f psadmin
    [psadm1@psovmfscmfp1 appserv]$ ln -s ../bin/psadmin .
    Environment variable is set in /appl/tools/psconfig.sh, update it :
    #PS_HOME="/opt/oracle/psft/pt/tools"; export PS_HOME
    PS_HOME="/appl/tools"; export PS_HOME
    *4. Change symbolic links in Oracle home directory*
    Similarly to Peoplesoft, Oracle installation create symbolic links according to the folder it was installed into, change it :
    [root@psovmfscmfp1 ~]# su  - psadm1
    [psadm1@psovmfscmfp1 ~]$ cd $ORACLE_HOME/lib
    [psadm1@psovmfscmfp1 lib]$ rm -f libclntsh.so.10.1 libclntsh.so
    [psadm1@psovmfscmfp1 lib]$ ln -s /appl/oracle-client/11.1.0.7-64bit/lib/libclntsh.so.11.1 libclntsh.so
    [psadm1@psovmfscmfp1 lib]$ ln -s /appl/oracle-client/11.1.0.7-64bit/lib/libclntsh.so.11.1 libclntsh.so.10.1
    *5. Reconfigure existing domains with new settings*
    To make the change persistent and take them in account, disconnect and reconnect as psadm2, reconfigure APPDOM and PRCSDOM (it will reinit the TUXDIR setting), configure has to be forced.

    *6. Restart existing domains with new settings*
    As psadm2, restart APPDOM and PRCS

    *7. PIA settings to be change*
    Similarly to Peopletools and Oracle, Weblogic installation took the folder it was installed into when set the environements variables, all have to be updated across all the configuratin files.
    As psadm1, go to $PS_HOME/webserv/peoplesoft/bin, and change the files
    --> setEnv.sh
    #PS_HOME=/opt/oracle/psft/pt/tools
    PS_HOME=/appl/tools
    #BEA_HOME=/opt/oracle/psft/pt/bea
    BEA_HOME=/appl/bea
    #WL_HOME=/opt/oracle/psft/pt/bea/wlserver_10.3
    WL_HOME=/appl/bea/wlserver_10.3
    
    --> singleserverStatus.sh
    #DOMAIN_HOME=/opt/oracle/psft/pt/tools/webserv/peoplesoft
    DOMAIN_HOME=/appl/tools/webserv/peoplesoft
    
    --> startPIA.sh
    #DOMAIN_HOME=/opt/oracle/psft/pt/tools/webserv/peoplesoft
    DOMAIN_HOME=/appl/tools/webserv/peoplesoft
    
    --> stopPIA.sh
    #DOMAIN_HOME=/opt/oracle/psft/pt/tools/webserv/peoplesoft
    DOMAIN_HOME=/appl/tools/webserv/peoplesoft
    
    --> createThreadDump.sh
    #DOMAIN_HOME=/opt/oracle/psft/pt/tools/webserv/peoplesoft
    DOMAIN_HOME=/appl/tools/webserv/peoplesoft
    
    --> /appl/bea/wlserver_10.3/common/bin/commEnv.sh
    # Set up BEA Home
    #BEA_HOME="/opt/oracle/psft/pt/bea"
    BEA_HOME="/appl/bea"
    
    # Set up Middleware Home
    #MW_HOME="/opt/oracle/psft/pt/bea"
    MW_HOME="/appl/bea"
    
    # Set up WebLogic Home
    #WL_HOME="/opt/oracle/psft/pt/bea/wlserver_10.3"
    WL_HOME="/appl/bea/wlserver_10.3"
    
    # Set up Common Modules Directory
    #MODULES_DIR="/opt/oracle/psft/pt/bea/modules"
    MODULES_DIR="/appl/bea/modules"
    
    # Set up Common Features Directory
    #FEATURES_DIR="/opt/oracle/psft/pt/bea/modules/features"
    FEATURES_DIR="/appl/bea/modules/features"
    ...
    #  JAVA_HOME="/opt/oracle/psft/pt/bea/jrockit-jdk1.6.0_17"
      JAVA_HOME="/appl/bea/jrockit-jdk1.6.0_17"
    *8. Start PIA*
    As psadm2, start PIA
    [psadm2@psovmfscmfp1 bin]$ cd $PS_HOME/webserv/peoplesoft/bin
    [psadm2@psovmfscmfp1 bin]$ ./startPIA.sh
    Attempting to start WebLogic Server PIA
    No activity will be logged to this window.
    Server activity will be logged to /appl/tools/webserv/peoplesoft/servers/PIA/logs/PIA_*
    PID for WebLogic Server PIA is: 3207
    [psadm2@psovmfscmfp1 bin]$ tail -f /appl/tools/webserv/peoplesoft/servers/PIA/logs/PIA_stdout.log
    ...
    <May 5, 2011 6:16:24 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <May 5, 2011 6:16:24 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    
    [psadm2@psovmfscmfp1 bin]$
    *9. Cobol*
    You may want to reboot the server itself to restart the Cobol license, it should take in account the modification done earlier in /etc/profile, nothing else to do.


    Enjoy the new directory. That way works absolutely fine.



    ***
    For your record, I tried the following as well, trying to take the folder change in account to redeploy the vm with the new setting (but so far unsuccessfully, probably I have to restart the all thing from scratch)
    Change ovm scripts_
    Under /opt/oracle/psft/vm, make the following changes in the corresponding files
    --> installpia.sh
    #PT_HOME=/opt/oracle/psft/pt
    PT_HOME=/appl
    --> oraclevm-template-appbatch.sh
    #    COBOL_INSTALLBITS_DIR=/opt/oracle/psft/pt/cobol/install-bits
        COBOL_INSTALLBITS_DIR=/appl/cobol/install-bits
    ...
    #        COBOL_INSTALL_DIR=/opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit
            COBOL_INSTALL_DIR=/appl/cobol/svrexp-51_wp4-64bit
    ...
    #        COBOL_MICROFOCUS_DIR=/opt/oracle/psft/pt/cobol/microfocus
            COBOL_MICROFOCUS_DIR=/appl/cobol/microfocus
    ...
    #    COBOL_INSTALL_DIR=/opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit
        COBOL_INSTALL_DIR=/appl/cobol/svrexp-51_wp4-64bit
    ...
    #        COBOL_MICROFOCUS_DIR=/opt/oracle/psft/pt/cobol/microfocus
            COBOL_MICROFOCUS_DIR=/appl/cobol/microfocus
    ...
    #            cd /opt/oracle/psft/pt/cobol
                cd /appl/cobol
    --> oraclevm-template-utils.sh
    #    PS_APP_HOME=$VM_APP_HOME/psft/pt/tools
        PS_APP_HOME=/appl/tools
    #    PS_PIA_HOME=$VM_APP_HOME/psft/pt/tools
        PS_PIA_HOME=/appl/tools
    Reinit the VM_
    As root using VNC client
    /usr/sbin/oraclevm-template --cleanup
    /usr/sbin/oraclevm-template --enable
    Restart VM and reconfigure it as it was the first time, at that point I have had few issues on APPDOM/PIA and Cobol.
    ***

    Nicolas.
  • 5. Re: PeopleSoft Configuration Script with new HCM 9.1/PT 8.51 template
    psadminMD Newbie
    Currently Being Moderated
    Thank you so much for you extensive reply. Apparently they have conflicting information regarding the templates in their documentation because in their whitepaper they say:

    The templates described herein may serve as a demonstration environment or as a starting point for a fully functioning PeopleSoft HCM installation. and The PeopleSoft HCM template is a fully functioning environment that contains a limited set of
    demo data. All HCM 9.1 application functionality is present. This is equivalent to the demo database that is shipped in a traditional PeopleSoft HCM distribution. This means that it is possible to use upgrade tools to add production data to the Database. Indicting that you can use it for systems other them demo. I know I also read them stating somewhere that with additional configuration that you can have it as a production system.

    I did not realize that you had responded back in May. I currently have a ticket open with Oracle regarding the changing of direcotries, so it will be interesting to see what they come back with.

    Again, I appreciate all the detail and work you put in! its extremely helpful and something I can play with.
  • 6. Re: PeopleSoft Configuration Script with new HCM 9.1/PT 8.51 template
    Nicolas.Gasparotto Oracle ACE
    Currently Being Moderated
    pspeon2.0 wrote:
    ... I currently have a ticket open with Oracle regarding the changing of direcotries, so it will be interesting to see what they come back with.
    Any news on that ?

    Nicolas.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points