#30 – Exadata w/ Karl Arao

Karl Arao joins us this week to talk about Exadata. Karl gives a great introduction to Exadata and explains how it can benefit PeopleSoft applications.

We want to make this podcast part of the community discussion on PeopleSoft administration. If you have comments, feedback, or topics you’d like us to talk about, we want to hear from you! You can email us at podcast@psadmin.io, tweet us at @psa_io, or use the Twitter hashtag #psadminpodcast.

You can listen to the podcast here on psadmin.io or subscribe with your favorite podcast player using the URL below, or subscribe in iTunes.

Podcast RSS Feed

Show Notes

  • Introduction to Exadata @ 2:00
  • Indexes @ 13:30
  • Migrating to an Exadata @15:30
  • Upgrading to 12c with Exadata @ 24:00
  • Value of Exadata @ 29:00
  • Exadata and PeopleSoft @ 34:00
  • Patching Exadata @ 37:00

Links

Managing 32-bit and 64-bit Oracle Client

Beginning with PeopleTools 8.54, the PeopleTools client tools became 64-bit applications. This means the client tools require the 64-bit Oracle client. If are still running on PeopleTools 8.53 (or earlier), you’ll need both 32-bit and 64-bit Oracle clients installed. Managing both versions can be cumbersone, and often times frustrating.

Tim Slater offered a great solution for managing Oracle clients in the psadmin.io Community. Here is Tim’s method for managing Oracle clients:

  1. Install Oracle 32-bit client to c:\oracle2\product\12.1.0\client_1
  2. Install Oracle 64-bit client to c:\oracle\product\12.1.0\client_1
  3. Create a symbolic link c:\windows\system32\oracle to point to the 64-bit installation folder.

    mklink /j c:\windows\system32\oracle c:\oracle\product\12.1.0\client_1
    
  4. Create a symbolic link c:\windows\sysWOW64\oracle to point to the 32-bit installation folder.

    mklink /j c:\windows\sysWOW64\oracle c:\oracle2\product\12.1.0\client_1
    
  5. Set the ORACLE_HOME environment variable to c:\windows\system32\oracle.

  6. (Optional) Set the TNS_ADMIN environment variable to %ORACLE_HOME%\network\admin

This works because of File System Redirection in 64-bit versions of Windows. If you are running a 64-bit application, Windows will route any system calls to c:\windows\system32. But, if you are running a 32-bit application, any system calls are routed to c:\system\sysWOW64 instead. Rather than manually configuring your applications and updating the PATH environment variable, you can let Windows do the work for you.

#29 – PeopleSoft Cloud Architecture w/ Graham Smith

This week Graham Smith joins us to talk about the PeopleSoft Cloud Architecture, the future of PeopleSoft and how the PeopleSoft Administrator role is changing.

We want to make this podcast part of the community discussion on PeopleSoft administration. If you have comments, feedback, or topics you’d like us to talk about, we want to hear from you! You can email us at podcast@psadmin.io, tweet us at @psa_io, or use the Twitter hashtag #psadminpodcast.

You can listen to the podcast here on psadmin.io or subscribe with your favorite podcast player using the URL below, or subscribe in iTunes.

Podcast RSS Feed

Show Notes

  • SQL Server/Windows @ 3:00
  • Reaction to Changes in PeopleSoft @ 8:00
  • PeopleSoft Cloud Architecture @ 12:00
  • Why the PCA? @ 30:30
  • Graham’s Predictions about PeopleSoft @ 35:00
  • How the PS Admin role is changing @ 43:30

PeopleSoft DPK QuickStart Course

Introducing the first course from psadmin.io! The PeopleSoft DPK Quickstart course will introduce you to Deployment Packages, demonstrate how to use DPKs with PeopleSoft Images, and how the DPK can be used to deploy your own servers. This free course will introduce you to the DPK, show you how to use the DPK with PeopleSoft Images, and show you how to customize the DPK for your servers.

 

#28 – DPK Successes and Shortcomings

Dan and Kyle talk about tabs versus spaces, Kyle’s File Attachment migration, and three new segments we’re adding to the show. Then Dan discusses his recent DPK successes and DPK shortcomings from his PeopleTools 8.55 upgrade.

We want to make this podcast part of the community discussion on PeopleSoft administration. If you have comments, feedback, or topics you’d like us to talk about, we want to hear from you! You can email us at podcast@psadmin.io, tweet us at @psa_io, or use the Twitter hashtag #psadminpodcast.

You can listen to the podcast here on psadmin.io or subscribe with your favorite podcast player using the URL below, or subscribe in iTunes.

Podcast RSS Feed

Show Notes

  • Date “T” trick @ 2:00
  • Tabbing Personalization @ 4:00
  • Vim casts.org @ 8:30
  • tabs v. spaces @ 13:45
  • Kyle’s File Attachment migration @ 16:00
  • Three new segments @ 35:00
    • Oh No! Stories
    • How do you do it?
    • Adventures in MOS
    • Leave a voice mail with your story: 1-810-772-4654 ( or 1-810-psaio-54)
  • How you do it: Managing SQL files @ 41:00
  • Dan shares his DPK successes and shortcomings @ 46:00

Links

Renaming VirtualBox DPK Images

If you are using the VirtualBox DPK PeopleSoft Images, you may have noticed the Virtual Machine names are not descriptive. By default, the names use this pattern: SHELL_8_55_xx. This name is the PeopleTools version the image is based on, but it tells you nothing about the application release. I prefer to use a different naming standard for our VirtualBox PeopleSoft Images, like: HCMDB-8-55-03-017. This naming convention tells me what application (HCMDB), PeopleTools release (8-55-03), and image number (017) a vm is running.

You can change the name of a VirtualBox vm pretty easily. When the vm is stopped (the vm can’t be running, or in a paused state), click the Settings button or select Machine > Settings. In the Name field, change the vm name to something meaningful. This will change the label of the vm in VirtualBox, as well as the folder name on the machine. It will not change the name of the hard drive files.

DPK Considerations

When you run the VBox DPK bootstrap script, you get a question that asks if you want to “Import the PeopleSoft Appliance into VirtualBox”. If you answer “Yes”, the new vm will use the name SHELL_8_55_xx. You can shutdown the vm after it is configured and rename it at that time.

If you answer “No”, you can import the SHELL_8_55_xx.ova file manually. The import page in VirtualBox lets you set the name of the vm. Keep in mind, if you import it manually you will need to create a Shared Folder back to the DPK files.

#27 – PeopleTools Performance Guidelines

Dan and Kyle talk about the a recent update in the PeopleSoft search replacement, a new tool to give you a 360 view of your application, and then we talk about changes in the PeopleTools Performance Guidelines document.

We want to make this podcast part of the community discussion on PeopleSoft administration. If you have comments, feedback, or topics you’d like us to talk about, we want to hear from you! You can email us at podcast@psadmin.io, tweet us at @psa_io, or use the Twitter hashtag #psadminpodcast.

You can listen to the podcast here on psadmin.io or subscribe with your favorite podcast player using the URL below, or subscribe in iTunes.

Podcast RSS Feed

Show Notes

Switching File Attachment Storage

In previous posts I have talked about the File Attachment storage options in PeopleSoft. The three basic options are Database, FTP or HTTP. My organization initially went with HTTP, but now we are looking to move to Database storage. The requirement is to move not only future file attachments, but attachments from the past as well. At first I thought this would require a lot of work, including custom conversion AE programs, etc. However, there is a delivered process called Copy File Attachements that does all the heavy lifting for you. There is an online and batch method to run this, but I highly recommend the batch mode. There are a few other steps needed to fully convert all attachments, but it is fairly straight forward. Below are the steps I used in FSCM 9.2.17, PeopleTools 8.54.18.

Create new File Attachment Server

  1. Navigate to Main Menu > Set Up Financials/Supply Chain > Common Defictions > File Attachments > Administer File Attachments
  2. Click Add Database Server
  3. Record Name will default to PV_ATT_DB_SRV. The default is fine, but change if you would like.
  4. Set Pick Active Server to match the ID of your new server.
  5. Save. Future File Attachments will now be stored in your database.

Copy File Attachments

  1. If needed, create new URL for Database storage – PeopleTools > Utilities > Administration > URLs. Values URL Identifier: PSA_ATT_DB, URLID:record://PV_ATT_DB_SRV
  2. Navigate to run control page PeopleTools > Utilities > Administration > Administer File Processing > Copy File Attachments (Batch)
  3. Values Source: URL.PSA_ATT_HTTP, Destination:URL.PSA_ATT_DB
  4. Run the App Engine COPYATTS through Process Scheduler.
  5. This will take a long time to run, possibly hours depending on your attachment count.
  6. After completion, you will want to review the trace file AE_COPYATTS_[PIN].trc file. The AE should produce this automatically.
  7. I used this trick to generate a log of ONLY errors from the trace:

    grep "EvalCopyAttachments: failed getting file" AE_COPYATTS_*.trc > AE_COPYATTS.errors

  8. Take action on any errors that occurred.

Update previous File Attachment URL

  1. These steps point the old HTTP server setup to point to the new DB server.
  2. Navigate to PeopleTools > Utilities > Administration > URLs. Values URL Identifier
  3. Open the URL used for the previous File Attachment Server setup. Example: PSA_ATT_HTTP
  4. Change the URLID value to the new Database server URL values. Example: record://PV_ATT_DB_SRV
  5. I recommend adding comments describing this conversion process – especially if HTTP or FTP is in the URL ID and it now points to the DB. This can help avoid confusion in the future.

After we completed these steps, we decided to keep our old storage location around just in case we found any issues after the fact. We ended up renaming the directory path, just to make sure nothing was still referencing the old location. After a few weeks of no issues, we went ahead and destroyed this old storage location. As mentioned above, this was done in the FSCM application which has its own File Attachment framework built on top of the one Tools delivers. You should be able to take a similar approach with other applications, but the Create new File Attachment Server section above won’t be relevant. Instead, you can simply complete the Update previous File Attachment URL steps after your copy is complete.