#26 – WebLogic Filters

This week we talk about HR Image 17, the new Security Automation tool, and share some comments from David Kurtz about PeopleSoft on 12c. Then, Kyle dives into WebLogic Servlet Filters and shares how filters can be used with PeopleSoft.

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

Change Assistant and File Servers

Last week I talked about setting up a new directoy on our file servers to handle patches: PS_APP_PATCH_HOME. The role of PS_APP_PATCH_HOME is to hold SQR, COBOL source, and other file system objects from PUM Patches. But, to make it easier to apply patches to the new PS_APP_PATCH_HOME, we want those folders to show up in Change Assistant as a file server. Then Change Assistant will deploy the files to PS_APP_PATCH_HOME for us.

With two changes, we can get our PS_APP_PATCH_HOME to show up as a file server.

  1. Copy the file appsfilesrvr.info from PS_APP_HOME\bin\client\winx86\ to PS_APP_PATCH_HOME\bin\client\winx86\.
  2. In the PSEMAgent\envmetadata\config\configuration.properties file for your file server, add the path for PS_APP_PATCH_HOME to the windowsdrivestocrawl or unixdrivestocrawl. For example, windowsdrivestocrawl=e:/psoft/hr92dev-patch|<your other folders>

After you add PS_APP_PATCH_HOME, issue a recrawl to your EMF Agent.

startagent.bat recrawl

When you re-open Change Assistant and validate the environments, the new path should show up. The e:\psoft\hr92dev-patch folder will also show up in the list of File Servers when applying a patch.

PS_APP_PATCH_HOME as a File Server

#25 – Intro to Elasticsearch

This week Dan talks about using a PS_APP_PATCH_HOME environment variable, Kyle discusses PeopleSoft features that require Windows servers and then we give an introduction to Elasticsearch.

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

PS_APP_PATCH_HOME and Custom COBOL Compile

The delivered COBOL compile scripts support compiling each HOME individually, but we can’t combine homes into a single CBLBINA folder. Additionally, with PeopleTools 8.55 dropping support for PS_CUST_APP_HOME, we are using a custom PS_APP_PATCH_HOME folder in the layer between PS_CUST_HOME and PS_APP_HOME.

To learn about PS_APP_PATCH_HOME, check out this video overview of the custom home we built for patching.

 

CBLBINA Directories Before

Before the change, we compiled each decoupled home separately we had 3 CBLBINA directories.

+-------------+  +-------------+  +--------------+
|             |  |             |  |              |
|   PS_HOME   |  | PS_APP_HOME |  | PS_CUST_HOME |
|             |  |             |  |              |
+-------------+  +-------------+  +--------------+

CBLBINA Directories After

After the change, we have 2 CBLBINA directories. One for the PeopleTools COBOL programs, and one for the application programs. The application COBOL programs are stored in our PS_CUST_HOME\CBLBINA folder.

+-------------+  +-------------------+
|             |  | PS_APP_HOME       |
|   PS_HOME   |  | PS_APP_PATCH_HOME |
|             |  | PS_CUST_HOME      |
+-------------+  +-------------------+

Modified Build Script

We use a batch helper script to configure the environment and call our new cblbld_all.bat script. The script CompileHR92DEVCobols_APP_PATCH_CUST.bat script will configure the environment variables for HR92DEV. Then it calls cblbld_all.bat e: \psoft\temp\compile ASCII to compile the COBOL source files.

This command cblbld_all.bat e: \psoft\temp\compile ASCII will trigger:

  1. File copy from PS_APP_HOME\src\cbl\base
  2. File copy from PS_APP_PATCH_HOME\src\cbl\base
  3. File copy from PS_CUST_HOME\src\cbl\base
  4. Compile the combined source files
  5. Copy compiled COBOLs to PS_CUST_HOME\CBLBINA

The delivered cblbld_mf.bat file was copied to e:\psoft\tools and renamed to cblbld_all.bat. The script was modified to support the changes above. We also merged in code from the cblsrc.bat script that copied the source files. The cblbld_all.bat script does all the steps for our compilation process.

This is the high-level code for the script. The actual script is longer, contains extra code from the delivered script, like folder/permissions checks, and has Oracle’s copyright. So here are the changes we made to cblbld_mf.bat.

rem ------------------------------------------------
set COMPILEDRIVE=%1
set COMPILEDIR=%2
set CBLSRCDR=%PS_HOME%\SRC\CBL
set CBLBINDR=%PS_CUST_HOME%\CBLBINA
set PS_purge_CBLBLDLOG = Y
set CBLBLDLOG=%COMPILEDRIVE%%COMPILEDIR%\CBLBLD.LOG

rem ------------------------------------------------
rem Delete the contents of the compile directory.
if defined PS_purge_CBLBLDLOG (
    echo Y | del %COMPILEDRIVE%%COMPILEDIR% > NUL
)

rem ------------------------------------------------
rem Copy Source Files
call %PS_HOME%\SETUP\CBLRTCPY %CBLBINDR% >> %CBLBLDLOG% 2>&1
copy %PS_HOME%\src\cbl\base\PTC*.cbl %COMPILEDRIVE%%COMPILEDIR%
copy %PS_HOME%\src\cbl\win32\* %COMPILEDRIVE%%COMPILEDIR%
copy %PS_APP_HOME%\src\cbl\base\*.cfg %COMPILEDRIVE%%COMPILEDIR%
copy %PS_APP_HOME%\src\cbl\base\*.cbl %COMPILEDRIVE%%COMPILEDIR%
copy %PS_APP_PATCH_HOME%\src\cbl\base\*.cfg %COMPILEDRIVE%%COMPILEDIR%
copy %PS_APP_PATCH_HOME%\src\cbl\base\*.cbl %COMPILEDRIVE%%COMPILEDIR%
copy %PS_CUST_HOME%\src\cbl\base\*.cfg %COMPILEDRIVE%%COMPILEDIR%
copy %PS_CUST_HOME%\src\cbl\base\*.cbl %COMPILEDRIVE%%COMPILEDIR%

rem ------------------------------------------------
rem Compile COBOL Programs
call CBLMAKE ALL >> %CBLBLDLOG%  2>&1

rem ------------------------------------------------
rem Deploy
IF EXIST %CBLBINDR%\*.EXE echo Y | del %CBLBINDR%\*.EXE
IF EXIST %CBLBINDR%\*.GNT echo Y | del %CBLBINDR%\*.GNT
IF EXIST %CBLBINDR%\*.INT echo Y | del %CBLBINDR%\*.INT

call %PS_HOME%\SETUP\CBLBIN %COMPILEDRIVE%%COMPILEDIR% %CBLBINDR% >> %CBLBLDLOG%

#24 – App Server Tuning w/ David Kurtz

Dan and Kyle discuss the new Ubuntu Bash shell for Windows 10, our plans to upgrade to Oracle 12c and introduce the new psadmin.io Community. We complete our interview with David Kurtz and talk about tuning the app server.

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

#23 – The App Server w/ David Kurtz

This week David Kurtz joins us again to talk about the application server. David get’s into the details on how the application server works. Dan and Kyle also discuss a proposal for Control-J information on mobile devices and Fluid pages.

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

8.55 – Enable App Server Features with the DPK

A comment on the Build Images with DPK post had a great question. Instead of answering it there, I wanted to share the solution as a post so more people would see it. The question deals with enabling (or disabling) features on the app server using the DPK. With the current PI’s based on PeopleTools 8.55.01, you can change app server configuration when you create the PI’s using the DPK.

If you have already built the PI’s, the 8.55.01 DPK doesn’t handle changes to the current configuration well.

To enable the WSL and Debugger when you build a DPK:

  1. Run the VBox or NativeOS DPK psft-dpk-setup script.
  2. Answer No to the “Do you want to continue with the default initialization” question.
  3. Create the file psft_customizations.yaml in the folder C:\ProgramData\PuppetLabs\Puppet\etc\data or /etc/puppet/data
  4. Add these lines to your psft_customizations.yaml file (notice the lines WSL: "Yes" and DBGSRV: "Yes" are different)
  5. Navigate to c:\programdata\puppetlabs\puppet\etc\manifests or /etc/puppet/manifests.
  6. Run puppet apply site.pp

If you have already build the PI, you can do in manually through psadmin, but that’s no fun 😉 In PeopleTools 8.55.03, the DPK (Puppet modules) is better at handling configuration changes in the psft_customizations.yaml file. I’d guess the next PI’s will be based .04 (or higher), so this should be able to make the change after you built the PeopleSoft Image.

Update: If you want to learn more about the DPK, check out our new PeopleSoft DPK QuickStart course. 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.

 

#22 – PeopleSoft on the Cloud

This week we talk about their system branding, share a great tip on customizing VERSION, and even discuss PeopleTools 8.56. Then, we dive into running PeopleSoft on the Cloud.

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