├── .gitignore ├── .travis.yml ├── README.md ├── STYLE.md ├── admin ├── admin.md ├── bandwidth_test.md ├── long_paths.md ├── tuxedo_port_block.md ├── windows_sevices.md └── wl_demo_certs.md ├── database ├── database.md └── sql_refresh.md ├── development ├── custom_change_packages.md ├── development.md └── event_mapping_links.md ├── getting_started ├── mos_searching.md └── tools.md ├── images ├── ElasticHQOverview.png ├── snippet.gif └── ui │ ├── cones.svg │ ├── docs-desktop.svg │ ├── footer-logo.svg │ ├── icon-arrowtabs.svg │ ├── icon-flag.svg │ ├── search.svg │ └── travis-logo.svg ├── middleware ├── cookie_configuration.md ├── elastichq.md ├── elasticsearchmonitoring.md ├── middleware.md ├── pia_404_errors.md └── slow_weblogic_start.md ├── pca ├── cleanup.md ├── cloud_manager.md ├── common_dpk_errors.md ├── custom_facts.md ├── pca.md ├── pi_passwords.md ├── puppet_helpers.md └── sample_yaml.md ├── peopletools ├── hardcoded_roles.md ├── peopletools.md ├── resend-content-sql.md └── search-callback-user.md └── talks ├── adv_ps_admin.md ├── oci.md └── talks.md /.gitignore: -------------------------------------------------------------------------------- 1 | .bundle 2 | .DS_Store 3 | .rvmrc 4 | _site 5 | bin 6 | source/tmp/* 7 | .sass-cache 8 | tmp/ 9 | .jekyll-metadata 10 | .jekyll-cache 11 | node_modules 12 | generated-language-mapping.json 13 | token.md -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | sudo: false 2 | dist: trusty 3 | language: ruby 4 | rvm: 5 | - 2.5 6 | cache: bundler 7 | branches: 8 | only: 9 | - master 10 | script: 11 | - "cd ..; git clone https://github.com/psadmin-io/psadmin-wiki-builder builder; mv builder/* ." 12 | - "mv psadmin-wiki posts" 13 | - "bundle install --full-index" 14 | - "bundle exec rake build" 15 | deploy: 16 | provider: pages 17 | skip_cleanup: true 18 | github_token: $GH_TOKEN # Set in travis-ci.org dashboard 19 | local_dir: _site 20 | repo: psadmin-io/psadmin-io.github.io 21 | fqdn: wiki.psadmin.io 22 | target_branch: master 23 | on: 24 | branch: master 25 | env: 26 | matrix: 27 | secure: A5NnQo7ykdKysHgEmoTfz9vJ685RT20TbTZ32Oe8lYQCESnYIOBBiKD9QPSlRKEuYY6U/XC6E9j7dxiDU1xCdcPjnpIxn3saP/+njx3qDAC2Zd1dhOmVyfvu9E8FtAsaRDVwmttFhdMvGmgzcAHwPGySij/QwcJEcM0pzL3KFhM/E262cAMXyXnfGFmecb69xLTE60SP8jC8WPYfA1f/xR2PJ1Kb1MrP2eaBaAf9qHIJPHRqVKIIrM+b3V3uO7K5io0jG3vWszP0VEU33i4QbvmSQszeid6XePD3ihinXnYJyypMkcFAhE2gurTH9nrUcscFkRoqpH+ybZrWtq8L9tr1ZfRD0IcwOjDDps9U0CmuMTuG3Uj0gDFhM8c4daw+rmgZDbJQP5O6dAA5xNYR/fl01Jv/GhPhUtFG6U/bjfE2u6be03mQGM0HeziEvbktmQZi95GAJ0dH97b5BaIe0rR/E3WRAAjRDYeVqeKB9Hn1nyaW/eQf0FN62eFKXxJ3S3nPzGtlobx7FTyljC14GSRzcfplEXnpBgXngfc8dpWoFWI8+jvPI/3Jp37RuSmDB61YLeJVlodgmvWzvxY/NR0E64Cz4ACPmHmZ0H45kvlLJV1pwzujHRYSN9LK5D36tyWJu20GdLlqW0z8ZxnVrsHFjHO9KQLYPBaP/8xa2vU= 28 | 29 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # About this repository [![Build Status](https://travis-ci.org/psadmin-io/psadmin-wiki.svg?branch=master)](https://travis-ci.org/psadmin-io/psadmin-wiki) 2 | 3 | The Community Wiki is a place for PeopleSoft Administrators to share documentation on setting up new features, how they resolved issues, and anything else they would like to share. 4 | 5 | ## How to use the wiki 6 | 7 | On the left are folder to group the various topics related to PeopleSoft Adminstration: 8 | 9 | * **[PeopleTools](peopletools/peopletools.md)**: Looking to configure a feature that is available under `Main Menu > PeopleTools`? Look under here. 10 | * **[Database](database/database.md)**: Articles about managing or working the the database. 11 | * **[Middleware](middleware/middleware.md)**: Want to read about Tuxedo, Java, WebLogic, COBOL. The middleware folder is for all supporting software that runs PeopleSoft 12 | * **[PeopleSoft Cloud Architecture](pca/pca.md)**: This area include Deployment Packages, Puppet, or anything about automation. 13 | * **[Server Administration](admin/admin.md)**: Articles about working with Windows, Linux, AIX or other server management topics. 14 | * **[Development](development/development.md)**: Posts about PeopleSoft development. 15 | 16 | ## How to contribute with GitHub 17 | 18 | Anyone can contribute to the Communtiy Wiki. 19 | 20 | There are two ways to contribute: online using GitHub, or on your local machine with `git` and a text editor. [For a video overview on how to use Github, check it out on the main wiki site](https://wiki.psadmin.io). 21 | 22 | **To edit an existing document:** 23 | 24 | 1. Open the page in the repository and click the pencil icon. 25 | 1. When you are done editing the document, add a commit comment and select "Create a new branch for this commit and start a pull request." You can change the branch name to something descriptive. 26 | 1. Click the "Propose file change" button. 27 | 1. On the Pull Request page, click the "Create pull request" button to submit your change for inclusion. 28 | 29 | **To add a new document:** 30 | 31 | 1. Open the folder where you want to create the file and click the "Create new file" button. 32 | 1. Add file name (use underscores for spaces) with the `.md` extension. 33 | 1. At the top of the new document, add the front-matter: 34 | 35 | ```markdown 36 | --- 37 | title: Sample Title 38 | layout: en 39 | permalink: /posts/folder/sample_title/ 40 | --- 41 | ``` 42 | 43 | 1. Add your title to the front-matter section. 44 | 1. Modify the `folder` and `sample_title` in the permalink section to match the folder and your filename. 45 | 1. When you are done creating and editing the document, add a commit comment and select "Create a new branch for this commit and start a pull request." You can change the branch name to something descriptive. 46 | 1. Click the "Propose file change" button. 47 | 1. On the Pull Request page, click the "Create pull request" button to submit your change for inclusion. 48 | 49 | **Publishing your changes** 50 | 51 | GitHub will test your changes with the wiki to ensure the wiki builds successfully. When the test has completed, a wiki administrator will approve your changes into the `master` branch. Commits to the `master` branch will trigger a new wiki build and update the site `wiki.psadmin.io` in a few minutes. 52 | 53 | ## How to contribute from a local Git repo 54 | 55 | Anyone can contribute to the Communtiy Wiki. To make a contribution or edit from a local copy of the repository, you'll need Git installed. It's also recommended you use a good text editor (like SublimeText, VS Code, Notepad++, vi) and are familiar with [Markdown formatting](https://guides.github.com/features/mastering-markdown/). 56 | 57 | ### Clone the wiki git repository 58 | 59 | To add your change, use Git to clone this repository to your local machine: 60 | 61 | git clone https://github.com/psadmin-io/psadmin-wiki.git 62 | 63 | This will copy the repositiory to the folder `psadmin-wiki`. 64 | 65 | ### Create a new branch 66 | 67 | Next, open the repository and create a new branch: 68 | 69 | cd psadmin-wiki 70 | git checkout -b 71 | 72 | For your branch name, use something descriptive so people know what the branch contains. (E.g, `update-README`, `push-notification-install`, etc) 73 | 74 | ### Add your article 75 | 76 | All the wiki articles live under the `posts` folder, and are organized into a few sections. Put your file under the section that most applies to the topic you are contributing. Under each section is an OVERVIEW articles with guidelines on what the topics are included. 77 | 78 | * PeopleTools 79 | * Database 80 | * Middleware 81 | * PeopleSoft Cloud Architecture 82 | * Server Administration 83 | * Development 84 | 85 | Now you can use your text editor to add a new article. For example, we'll add a new article that shows a sample `psft_customizations.yaml` file under the *PeopleSoft Cloud Architecure* section. I'll create a new file with VS Code: 86 | 87 | code posts/pca/sample_yaml.md 88 | 89 | #### Front-data 90 | 91 | At the top of every wiki article is some YAML data that tells the wiki how to render the document. 92 | 93 | --- 94 | title: Sample psft_customizations.yaml 95 | layout: en 96 | permalink: /posts/pca/sample_yaml/ 97 | --- 98 | 99 | Update the title and permalink values. For the `permalink`value, use the convention `/posts/
//` The permalink will be the URL to the wiki page. 100 | 101 | #### Wiki article 102 | 103 | Start the wiki article with a heading (two `##`) and the title. Everything after here is the article. You can use Markdown formatting throughout the article to create code blocks, headings, lists, etc. 104 | 105 | ## Sample psft_customizations.yaml File 106 | 107 | Below is a sample `psft_customizations.yaml` file to give you an idea of how to define configuration for the DPK. 108 | 109 | #### Gists 110 | 111 | You can include GitHub gists if you want. Copy the code below and replace the `src=` with the link to your Gist. 112 | 113 | 114 | 115 | ### Create a git commit 116 | 117 | Once your article is done and added to the sidebar, create a Git commit for your chagnes. 118 | 119 | git add . 120 | git status 121 | 122 | Make sure everything you changed is added to the commit. 123 | 124 | git commit -m "Added sample `psft_customizations.yaml` article" 125 | 126 | Then, push your changes up to GitHub so they can be reviewed before merging into the master wiki branch. 127 | 128 | git push origin 129 | 130 | ### Create a pull request 131 | 132 | GitHub has an excellent Pull Request (PR) feature where you can submit changes to the wiki. The PR will be submited for review and the wiki changes will be tested to make sure nothing in the wiki broke. 133 | 134 | 1. In GitHub, open the repository page for the wiki, click on the *Pull Requests* tab and select *Create Pull Request*. 135 | 1. Select `master` as the base, and `` as the compare. 136 | 1. Click the *Create Pull Request* button submit it for review. 137 | 1. Add a title and fill out a description of the changes you made. 138 | 1. Click *Create Pull Request* to finish the PR. 139 | 140 | After submitting the PR, the wiki branch you submitted will be pulled into a Travis-CI test build. If there are errors with the build, the results are displayed on the PR page. If the test build succeeded, the PR page will show a successful test. 141 | 142 | A wiki administration will review the PR and merge the branch into `master` if there are no issues. 143 | 144 | ## How to check your edits before sending PR 145 | 146 | You can inspect how your edits will be reflected on the published wiki if you want to view the changes before submitting a PR. 147 | 148 | ### Install dependencies 149 | 150 | 1. Make sure you have Ruby and RubyGems installed. 151 | 152 | 1. Install [bundler](http://bundler.io/): 153 | 154 | ```sh-session 155 | $ gem install bundler 156 | ``` 157 | 158 | 1. Install application dependencies: 159 | 160 | ```sh-session 161 | $ bundle install --binstubs 162 | ``` 163 | 164 | ### Run the Jekyll application server 165 | 166 | You are now ready to start your documentation site, using Jekyll or Puma. 167 | For documentation edits, Jekyll is sufficient. 168 | 169 | #### Starting and inspecting edits with Jekyll 170 | 171 | 1. Run Jekyll server: 172 | 173 | ```sh-session 174 | $ rake 175 | $ bundle exec jekyll serve 176 | ``` 177 | 178 | 1. Open [localhost:4000](http://localhost:4000/) in your browser. 179 | 180 | -------------------------------------------------------------------------------- /STYLE.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Style Guide 3 | layout: en 4 | permalink: /style_guide/ 5 | --- 6 | 7 | # psadmin.io Community Wiki Style Guide 8 | 9 | (Copied from the Travis CI documentation style guide - it's realy good.) 10 | 11 | ## Markdown and structure 12 | 13 | ### Headings 14 | 15 | For historical reasons, the top level heading in Jekyll markdown files is level 2 (##) not level 1 (#). 16 | 17 | We use ATX style headings, and do not use the optional closing hashes: 18 | 19 | ```markdown 20 | ## This is an H2 21 | 22 | ### This is an H3 23 | 24 | #### This is an H4 25 | ``` 26 | 27 | We do not use underline style headings: 28 | 29 | ```markdown 30 | Do not use this style heading 31 | ============================= 32 | ``` 33 | 34 | ### Lists 35 | 36 | If you have long lists you can wrap them into 2 (`.column-2`) or 3 (`.column-3`) columns using one of the follow CSS classes after your list item: 37 | 38 | ```css 39 | * long list item 1 40 | * long list item 2 41 | {: .column-2 } 42 | ``` 43 | 44 | ### TOC 45 | 46 | Add a table of contents to a page with the following HTML snippet: 47 | 48 | ```html 49 |
50 | ``` 51 | 52 | ### Beta features 53 | 54 | Mark all beta features with a specially formatted note. Both the `> BETA` and 55 | the `{: beta}` are required. 56 | 57 | > BETA Awesome new feature that might not be enabled and is subject to change. 58 | {: .beta} 59 | 60 | ### GUI 61 | 62 | Make sure all references to items in a GUI match the case of the UI, and are marked with *asterisks*. 63 | 64 | ### Links 65 | 66 | Make sure all links have titles: 67 | 68 | ```markdown 69 | The [link][example1] in the text 70 | 71 | [example1]: http://www.example.com "Example URL" 72 | ``` 73 | 74 | or 75 | 76 | ```markdown 77 | The [link](http://www.example.com "Example URL") in the text 78 | ``` 79 | 80 | ### Code Inline 81 | 82 | All function names, filenames, etc should be marked with `back-ticks`. 83 | 84 | If you're talking about applications or services, only the actual command should be marked as code, not the name of the service: 85 | 86 | - Start SQL*Plus by running `sqlplus`. 87 | 88 | ### Blockquotes / Notes / Warnings 89 | 90 | Use `>` to indicate notes and warnings: 91 | 92 | ```markdown 93 | > Note this important info! 94 | 95 | ``` 96 | 97 | ### Code blocks 98 | 99 | Code blocks should be fenced with triple back-ticks "\`\`\`" and named according to [prism.js][prism] for syntax highlighting. 100 | 101 | [prism]: http://prismjs.com/#languages-list "Prism language list" 102 | 103 | ```markdown 104 | your code here 105 | ``` 106 | 107 | You can also set the filename for a code block by adding a Kramdown attribute after it: 108 | 109 | ```markdown 110 | This code is in .travis.yml 111 | ``` 112 | {: data-file=".travis.yml"} 113 | 114 | 115 | ## Images 116 | 117 | Always include text for configuration items. Screenshots and images should only be used to accompany the text description; never use only an image for documentation. -------------------------------------------------------------------------------- /admin/admin.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Server Administration 3 | layout: en 4 | permalink: /posts/admin/ 5 | --- 6 | 7 | This section is for articles on managing servers for PeopleSoft. Articles here are for working with Windows, Linux, etc. -------------------------------------------------------------------------------- /admin/bandwidth_test.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Bandwidth Test 3 | layout: en 4 | permalink: /posts/admin/bandwidth_test/ 5 | --- 6 | 7 | ## Bandwidth Testing with iperf 8 | 9 | If you want to do a quick test of your network between two servers (say, between to reqions in a cloud provider), you can quickly do that with [`iperf`](https://iperf.fr). `iperf` is a multi-platform utility to test and measure the capacity of your network. 10 | 11 | ### Installation 12 | 13 | Install `iperf` on two servers. Make sure to choose two servers that will traverse the part of the network you want to test. If you are running some cloud servers and want to test the bandwith from your on-prem network, install `iperf` on one on-prem server and one cloud server. 14 | 15 | For Linux, set the EPEL repo first. 16 | 17 | **Linux 7** 18 | 19 | ```bash 20 | wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm 21 | sudo rpm -ivh epel-release-latest-7.noarch.rpm 22 | ``` 23 | 24 | **Linux 6** 25 | 26 | ```bash 27 | wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm 28 | sudo rpm -ivh epel-release-6-8.noarch.rpm 29 | ``` 30 | 31 | Use `yum` to intall `iperf`. 32 | 33 | ```bash 34 | sudo yum install iperf -y 35 | ``` 36 | 37 | On Windows, visit the [download page](https://iperf.fr/iperf-download.php#windows) or use [Chocolatey](https://chocolatey.org/packages/iperf3) 38 | 39 | ```powershell 40 | choco install iperf3 -y 41 | ``` 42 | 43 | ### Run a bandwith test 44 | 45 | On `server1` we will configure `iperf` to act as the receiving end (the server). 46 | 47 | ```bash 48 | sudo iperf -s 49 | ``` 50 | 51 | On `server2` we will configure `iperf` to send data to our server. 52 | 53 | ```bash 54 | sudo iperf 10.0.10.1 55 | ``` 56 | 57 | `iperf` will run a short test and report the results. 58 | 59 | ``` 60 | ------------------------------------------------------------ 61 | Client connecting to 10.0.10.1, TCP port 5001 62 | TCP window size: 45.0 KByte (default) 63 | ------------------------------------------------------------ 64 | [ 3] local 10.0.9.1 port 59004 connected with 10.0.10.1 port 5001 65 | [ ID] Interval Transfer Bandwidth 66 | [ 3] 0.0-10.0 sec 717 MBytes 601 Mbits/sec 67 | ``` 68 | 69 | You can reverse the test too so that `server1` sends the data back to `server2`. Just add the `-R` flag. 70 | 71 | ```bash 72 | sudo iperf 10.0.10.1 -R 73 | ``` 74 | 75 | You can also control how long the test runs by adding the `-t` flag and specify the number of seconds to run the test. 76 | 77 | ``` 78 | sudo iperf 10.0.10.1 -t 60 79 | ``` 80 | 81 | You can also tell `iperf` to run parallel tests with `-P` if you really want to try maxing out your network. 82 | 83 | ```bash 84 | sudo iperf 10.0.10.1 -P 3 -t 120 85 | ``` -------------------------------------------------------------------------------- /admin/long_paths.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Remove Long Paths 3 | layout: en 4 | permalink: /posts/admin/long_paths/ 5 | --- 6 | 7 | ## Remove Long Paths 8 | 9 | Windows often has issues removing folder where nested paths are longer than 256 characters. Two quick ways to remove the folder: 10 | 11 | ```powershell 12 | Cmd /C ("rmdir /S /Q " + $problematicDir) 13 | ``` 14 | 15 | ```powershell 16 | mkdir empty 17 | robocopy .\empty .\weblogic /MIR 18 | rm .\empty; rm .\weblogic 19 | ``` -------------------------------------------------------------------------------- /admin/tuxedo_port_block.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Unblock Tuxedo 3 | layout: en 4 | permalink: /posts/admin/unblock_tuxedo/ 5 | --- 6 | 7 | ## Unblock Tuxedo Connection Due Failed Logins 8 | 9 | Starting with PT 8.56 Oracle delivered a new feature with Tuexedo that will block a server if too many failed loggins occured or if Tuxedo believes it is being attatched by the server. 10 | 11 | As a default, if a client login fails three (3) times in 60 seconds, the associated IP address is blocked. 12 | 13 | If warranted for your environment, you can tune the TM_WS_MAX_FAILED_TRIAL (limit of failed login attempts) and TM_WS_ATTACK_IP_CHK_INTERVAL (time interval for failed login attempts) environment variables to allow for more login failures and/or a different, smaller interval. 14 | If you're certain that there is no actual attacker, it may consider disabling this option. You can disable it by setting the TM_WS_MAX_FAILED_TRIAL environment variable to 0 (TM_WS_MAX_FAILED_TRIAL=0). 15 | 16 | The limit on failed login attempts is a security mechanism to protect against a client guessing a password. 17 | Changing the values of these environment variables is done at your own risk. 18 | 19 | These log errors are in the TUXLOG log files. 20 | 21 | To view current blocked connections 22 | 23 | ```powershell 24 | cd $env:PS_CFG_HOME 25 | $env:TUXCONFIG="${env:PS_CFG_HOME}\appserv\<>\PSTUXCFG" 26 | cmd /c tmadmbclist -l 27 | ``` 28 | 29 | To unblock a specifed ip address run the following 30 | ```powershell 31 | cd $env:PS_CFG_HOME 32 | $env:TUXCONFIG="${env:PS_CFG_HOME}\appserv\<>\PSTUXCFG" 33 | cmd /c tmadmbclist -b <> 34 | ``` 35 | -------------------------------------------------------------------------------- /admin/windows_sevices.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Windows Services 3 | layout: en 4 | permalink: /posts/admin/windows_services/ 5 | --- 6 | 7 | ## Start/Stop Services 8 | 9 | The built-in cmdlets are great for starting and stopping a group of services. If you have Powershell Remoting enabled, you can use the `-computername` parameter to pass in a server or list of servers to execute the command remotely. 10 | 11 | *Start* 12 | 13 | ```powershell 14 | get-service -name psft* -computername | start-service 15 | ``` 16 | 17 | *Stop* 18 | 19 | ```powershell 20 | get-service -name psft* -computername | stop-service 21 | ``` 22 | 23 | ## Change Startup Type of Service 24 | 25 | Situations sometimes arise where you need to set service startup to either `Manual`, `Automatic` or `Disabled`. To achieve that, use `Set-Service` command, e.g. 26 | 27 | ```powershell 28 | # Set All PeopleSoft Services to manual startup 29 | Get-Service *psft* | Set-Service –StartupType 'Manual' 30 | ``` 31 | 32 | ## Delete Services 33 | 34 | Since there is no `delete-service` cmdlet, use this command to delete services by name. For each service that contains "psft", loop through the services and delete them. 35 | 36 | ```powershell 37 | Get-WmiObject -Class Win32_Service | Where-Object { $_.name -like 'Psft*' } | % { $_.delete() } 38 | ``` 39 | 40 | You can also drop into a Windows Command Shell or PowerShell and use `sc.exe` to delete a service. 41 | 42 | ```powershell 43 | sc.exe delete PsftAppServerDomainAPPDOMService 44 | ``` 45 | -------------------------------------------------------------------------------- /admin/wl_demo_certs.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: WebLogic Demo Certificates 3 | layout: en 4 | permalink: /posts/admin/wl_demo_certs/ 5 | --- 6 | 7 | ## WebLogic Demo Certificates 8 | 9 | The demo certificates delivered with WebLogic and used by the PIA are stored in the file: 10 | 11 | ```bash 12 | $PS_CFG_HOME/webserv//security/DemoIdentity.jks 13 | ``` 14 | 15 | To access the keystore, you can use `keytool` which is included with the JDK: 16 | 17 | ```bash 18 | keytool -list -keytore $PS_CFG_HOME/webserv//security/DemoIdentity.jks 19 | ``` 20 | 21 | | Property | Value | 22 | |----------------------|-----------------------------------------------------------| 23 | | Trust store location | `$ORACLE_HOME/bea/wlserver/server/lib/DemoTrust.jks` | 24 | | Trust store password | `DemoTrustKeyStorePassPhrase` | 25 | | Key store location | `$PS_CFG_HOME/webserv//security/DemoIdentity.jks` | 26 | | Key store password | `DemoIdentityKeyStorePassPhrase` | 27 | | Private key password | `DemoIdentityPassPhrase` | 28 | 29 | > This information is from [G's Blog](http://kingsfleet.blogspot.com/2008/11/using-demoidentity-and-demotrust.html) -------------------------------------------------------------------------------- /database/database.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Database 3 | layout: en 4 | permalink: /posts/database/ 5 | --- 6 | 7 | This section is for articles on managing PeopleSoft databases. This includes Oracle, SQL Server and DB2 platforms. -------------------------------------------------------------------------------- /database/sql_refresh.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: SQL to Update Tables on Refresh 3 | layout: en 4 | permalink: /posts/database/sql_refresh/ 5 | --- 6 | 7 | ## SQL to Update Tables on Refresh 8 | 9 | We all refresh production PeopleSoft database to non-production environments. How we handle those refreshes can vary, but in the end we need to update tables in the database to make the copy of production work in the new environment. This article will give a list of tables to update and sample SQL statements to make those updates. 10 | 11 | > Unless called out, SQL is written for Oracle databases 12 | 13 | ### Access ID 14 | 15 | ```sql 16 | -- -------------------- 17 | -- Set New Schema Owner 18 | -- -------------------- 19 | 20 | alter user SYSADM identified by ; 21 | 22 | update ps.psdbowner set 23 | ownerid = 'SYSADM', 24 | dbname = 'DEV' 25 | where dbname = 'PRD'; 26 | 27 | update psadm.psstatus set 28 | ownerid = 'SYSADM', 29 | lastrefreshdttm = sysdate; 30 | 31 | update psadm.psaccessprofile set 32 | STM_ACCESS_ID = '', 33 | STM_ACCESS_PSWD = '', 34 | STM_ACCESS_PART1 = '', 35 | STM_ACCESS_PART2 = '', 36 | ENCRYPTED = '1', STM_ENCRYPTION_VER = '1' 37 | WHERE SYMBOLICID = 'SYSADM1'; 38 | ``` 39 | 40 | ### PSOPTIONS -------------------------------------------------------------------------------- /development/custom_change_packages.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Working with a Custom Change Package 3 | layout: en 4 | permalink: /posts/development/custom_change_package/ 5 | --- 6 | 7 | Author: Andy Dorfman 8 | 9 | ## Prepare External Objects 10 | 11 | ### Create DMS file 12 | 13 | - `d:\temp\update_psstatus.dms` 14 | ```sql 15 | set log update_psstatus.log; 16 | update PSSTATUS set LASTCHANGEDTTM = %CurrentDateTimeIn; 17 | ``` 18 | 19 | ## Application Designer portion 20 | 21 | ### Create Custom File Code (PSTYPECODEDEFN) 22 | 23 | - `Application Designer` > `Tools` > `Miscellaneous Definitions` > `File Type Codes` 24 | ```yaml 25 | FILEREFTYPECODE: 'CUSTOM_SCRIPTS' 26 | FILEREFPATH: '%ps_cust_home%\scripts' 27 | DESCRLONG: 'LBC PS_CUST_HOME\scripts folder' 28 | ``` 29 | 30 | ### Create Custom Script File Reference 31 | 32 | - `Application Designer` > `New` > `File Reference` 33 | ```yaml 34 | File Name and Path: "Click on ... to select a file `D:\temp\update_psstatus.dms`" 35 | Binary: 'No' 36 | Database Platform: 'All' 37 | PeopleSoft Server: 'File Server' 38 | Operating System: 'All' 39 | ``` 40 | 41 | - `Application Designer` > `File` > `Save As` 42 | ```yaml 43 | Save Name As: 'UPDATE_PSSTATUS_DMS' 44 | File Type Code: 'CUSTOM_SCRIPTS' 45 | ``` 46 | - Click `OK` to save 47 | - Replace `D:\temp\update_psstatus.dms` with `%FILEREFPATH%\update_psstatus.dms` 48 | - Click `OK` to save again 49 | - Click `F7` to import File Reference Definition into the project 50 | 51 | - `Application Designer` > `File` > `Save Project` 52 | ```yaml 53 | Save Project Name As: 'LBC_IT0001' 54 | ``` 55 | - Click `OK` to save 56 | 57 | - `Application Designer` > `Tools` > `Project Properties` 58 | ```yaml 59 | Description: 'Testing CUSTOM_SCRIPTS File References' 60 | Comments: 'Testing description' 61 | Change Project: 'Check' 62 | Update ID: 'LBC_IT0001' 63 | Add: 64 | ``` 65 | - Click `OK` 66 | - `Application Designer` > `File` > `Save All` 67 | - `Application Designer` > `Upgrade` Tab 68 | - Doube-Click on `File References`, Check `Execute` Flag 69 | - `Application Designer` > `File` > `Save All` 70 | 71 | ### Create Change Package 72 | 73 | - `Application Designer` > `Tools` > `Create Change Package` 74 | - Click `OK` 75 | ```yaml 76 | Export Directory: 'd:\temp\LBC_IT0001' 77 | File Reference Path: 'D:\temp' 78 | Update ID: 'LBC_IT0001' 79 | Generate New Template: 'Check' 80 | ``` 81 | 82 | - `Application Designer` > `Tools` > `Finalize Change Package` 83 | ```yaml 84 | Export Directory: 'd:\temp\lbc_it0001\updlbc_it0001' 85 | ``` 86 | - Click `OK` 87 | 88 | ### Apply Change Package 89 | 90 | - Place `d:\temp\LBC_IT0001\updLBC_IT0001\updLBC_IT0001.zip` in CA's `download` directory 91 | - `Change Assistant` > `Tools` > `Apply Change Package` > `Apply Automatically Without Compare` > `Next` > `Apply without using Change Impact Analyzer` > `Next` > Select product line release > `Next` > Select target environment > `Next` > Select Host > `Next` > Provide Credentials > `Next` > Select download directory > `Next` > Select `UPDLBC_IT0001` > `Next` > `Next` > `Validate Now` (make sure psemagent is running) > `Begin Apply` 92 | 93 | - Examine the log file for `Deploy Files` > `File Type Code: CUSTOM_SCRIPTS` > `UPDATE_PSSTATUS_DMS` 94 | 95 | > It looks like it's finding only 1 file server under PS_HOME and deploying the file udpate_psstatus.dms only to that 1 location, most likely due to me selecting only 'File Server' during File Reference creation. Nothing got transferred to PS_CUST_HOME 96 | 97 | - Examine the view Script for `Execute File References` > `Execute DMS` > `UPDATE_PSSTATUS_DMS` 98 | 99 | > It is executing update_psstatus.dms script from the staging directory 100 | -------------------------------------------------------------------------------- /development/development.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: PeopleSoft Development 3 | layout: en 4 | permalink: /posts/development/ 5 | --- 6 | 7 | This section is for articles on PeopleSoft development. -------------------------------------------------------------------------------- /development/event_mapping_links.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Event Mapping Links 3 | layout: en 4 | permalink: /posts/development/event_mapping_links/ 5 | --- 6 | 7 | ## A collection of links about Event Mapping 8 | 9 | *Chris Malek on Event Mapping* 10 | 11 | * [Discovering Event Mapping](https://www.cedarhillsgroup.com/knowledge-base/kbarticles/pt855-assigning-application-class-peoplecode-to-component-events/) 12 | 13 | *Colton Fischer on Event Mapping* 14 | 15 | * [Blog posts about Event Mapping](http://www.peoplesoftmods.com/categories/#event-mapping) 16 | 17 | *Sasank Vemana on Event Mapping* 18 | 19 | * [Blog posts about Event Mapping](https://pe0ples0ft.blogspot.com/search?q=Event+mapping) 20 | 21 | *psadmin.io on Event Mapping* 22 | 23 | * [Event Mapping Demo](http://psadmin.io/2016/02/10/8-55-event-mapping-demo/) 24 | * [Interview with Colton Fischer on Event Mapping](http://psadmin.io/2016/11/18/55-2fa-and-event-mapping-w-colton-fischer/) 25 | * [blog posts and podcast search](http://psadmin.io/?s=event+mapping) 26 | * [Reduce your customizations](http://psadmin.io/2015/12/29/8-55-reduce-your-customizations/) 27 | -------------------------------------------------------------------------------- /getting_started/mos_searching.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Searching in My Oracle Support 3 | layout: en 4 | permalink: /posts/getting_started/mos_searching/ 5 | --- 6 | 7 | Some tips when searching in My Oracle Support to help you find relevant documents. 8 | 9 | ### Platform Codes 10 | 11 | Use the platform codes to narrow down your search. For example, `E-RD` will search for Report Distribution documents related to PeopleSoft Enterprise. 12 | 13 | Here is a list some common codes to use when searching 14 | 15 | * `E-PIA`: PIA related issue 16 | * `E-ES`: Elasticsearch 17 | * `E-PTSF`: PeopleSoft Search Framework (ES, SES and the PeopleSoft side) 18 | * `E-SSL`: SSL and PeopleSoft 19 | 20 | If you look at the beginning of a document title, you can pick up on common platform codes and use those in the future to help narrow your search. 21 | 22 | ### Helpful MOS Bookmarks 23 | 24 | MOS allows you to bookmark a document by clicking the faint yellow star on the top left of any page next to the title. Once you have added it to your bookmark list, you can organize your list into folders by selecting the yellow star in the top right next to the search bar and selecting **Manage Favorites...** 25 | 26 | #### Adventures in MOS 27 | * `TODO`: Include list of Adventures in MOS docs mentioned on the podcast 28 | 29 | #### Database 30 | * [Announcement: Release Schedule of Current Database Releases \[ID: 742060.1\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=742060.1) 31 | * [Bulletin: Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration \[ID: 413484.1\] 12/07/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=413484.1) 32 | * [Announcement: Oracle Database Advisor Webcast Schedule and Archive recordings \[ID: 1456176.1\] 12/07/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1456176.1) 33 | * [Document: Oracle Premier Support - Oracle Database Support News Archive \ID: 1284265.1\] 12/07/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1284265.1) 34 | * [How To: Oracle Database Upgrade Path Reference List \[ID: 730365.1\] 30/04/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=730365.1) 35 | * [Document: Information Center: Oracle Database 12c Release 1 \[ID: 1595421.2\] 04/05/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1595421.2) 36 | 37 | #### Enterprise Manager 38 | * [Bulletin: How to Configure the Enterprise Management Agent Host Credentials for PAM and LDAP \[ID: 422073.1\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=422073.1) 39 | * [Database patch plan validation fails when normal and privileged creds are same \[Oracle\] [ID: 19130520] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=19130520) 40 | * [Bulletin: Prerequisite script for Exadata Discovery in Oracle Enterprise Manager Cloud Control 12c and 13c \[ID: 1473912.1\] 24/08/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1473912.1) 41 | * [Reference: Release Schedule for Enterprise Manager Cloud Control 12c Plug-ins \[ID: 1486995.1\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1486995.1) 42 | * [Document: Information Center: Enterprise Manager Base Platform Release Cloud Control 12c \[ID: 1379818.2\] 12/07/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1379818.2) 43 | * [How To: How to integrate the JIRA ticketing tool with Enterprise Manager Cloud Control 12c \[ID: 1537815.1\] 19/05/2017](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1537815.1) 44 | 45 | #### EVERYTHING 46 | * [Document: Privacy and Security Feature Guidance for all Oracle Products (On Premise) \[ID: 113.2\] 27/06/2019](https://support.oracle.com/epmos/faces/DocContentDisplay?id=113.2) 47 | * [System Doc: Oracle Premier Support - Product Support Blog and Newsletter Index \[ID: 222.1\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=222.1) 48 | * [Document: Catalog: Oracle Information Centers: All Products - Database - Exadata - EBS - JDE - Fusion - Middleware - GBUs - Siebel - Sun Systems - Peoplesoft - Enterprise Manager \[ID: 1987485.2\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1987485.2) 49 | * [Document: Oracle Support Lifecycle Advisors \[ID: 250.2\] 16/01/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=250.2) 50 | * [Announcement: Advisor Webcasts: Current Schedule and Archived Recordings \[ID: 740966.1\] 12/01/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=740966.1) 51 | 52 | #### Exadata 53 | * [Document: Information Center: Oracle Exadata Database Machine \[ID: 1306791.2\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1306791.2) 54 | * [Reference: Oracle Exadata Database Machine exachk or HealthCheck \[ID: 1070954.1\] 24/08/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1070954.1) 55 | * [Reference: Exadata Critical Issues \[ID: 1270094.1\] 12/07/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1270094.1) 56 | * [Announcement: Oracle Engineered Systems Advisor Webcast Schedule and Archive recordings \[ID: 1456202.1\] 12/07/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1270094.1) 57 | * [Reference: Exadata Database Machine and Exadata Storage Server Supported Versions \[ID: 888828.1\] 12/07/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=888828.1) 58 | 59 | #### Java 60 | * [Reference: All Java SE Downloads on MOS \[ID: 1439822.1\] 17/01/2019](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1439822.1) 61 | * [White Paper: How to Install and Maintain the Java SE Installed or Used with FMW 11g/12c Products \[ID: 1492980.1\] 17/01/2019](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1492980.1) 62 | 63 | #### Patching 64 | * [FAQ: E-WL: Frequently Asked Questions about Upgrading WebLogic 12c for PeopleTools 8.56 to a Newer Patch Set Update (PSU), Release, and/or a Newer Java Patch Level \[ID: 2281647.1\] 04/09/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2281647.1) 65 | * [Bulletin: RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU" (OJVM PSU/RU) Patches \[ID: 2217053.1\] 04/05/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2217053.1) 66 | * [Announcement: Patch Set Update (PSU) Release Listing for Oracle WebLogic Server (WLS) \[ID: 1470197.1\]](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1470197.1) 67 | * [Announcement: Error Correction Support Dates for Oracle WebLogic Server \[ID: 950131.1\] 12/01/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=950131.1) 68 | * [Reference: PeopleSoft Enterprise PeopleTools Certification Table of Contents \[ID: 759851.1\] 18/01/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=759851.1) 69 | * [Reference: Critical Patch Update (CPU) Program January 2018 Patch Availability Document (PAD) \[ID: 2325393.1\] 17/01/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2325393.1) 70 | 71 | #### Peoplesoft 72 | * [How To: pscbo_stats - Improving Statistics in Oracle RDBMS for PeopleSoft Enterprise \[ID: 1322888.1\] 19/01/2017](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1322888.1) 73 | * [Document: PeopleSoft Update Manager (PUM) Home Page \[ID: 1641843.2\]](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1641843.2) 74 | * [System Doc: PeopleSoft PeopleTools Maintenance Schedule \[ID: 876292.1\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=876292.1) 75 | * [Reference: Tech Update - Main Page \[ID: 764222.1\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=764222.1) 76 | * [Reference: Required Interim Patches for the Oracle Database with PeopleSoft \[ID: 1100831.1\] 29/04/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1100831.1) 77 | * [Reference: Oracle''''s PeopleSoft PeopleTools 8.56 New Features Overview \[ID: 2267247.1\] 07/11/2017](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2267247.1) 78 | * [How To: E-IB: Example for PeopleSoft REST provider service (GET/POST methods) \[ID: 1533318.1\] 14/02/2019](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1533318.1) 79 | * [Document: PeopleSoft PeopleTools Patches Home Page \[ID: 2062712.2\] 17/12/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2062712.2) 80 | * [Document: Oracle''''s PeopleSoft PeopleTools 8.57 Home Page \[ID: 2433119.2\] 17/01/2019](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2433119.2) 81 | * [How To: E-PORTAL: How To Force All Browsers To Update Cache? \[ID: 1509442.1\] 12/11/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1509442.1) 82 | * [Document: Oracle''''s PeopleSoft PeopleTools 8.56 Home Page \[ID: 2259140.2\] 14/02/2019](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2259140.2) 83 | * [How To: E-ORA Advice for the PeopleSoft Oracle DBA \[ID: 1445965.1\] 12/06/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1445965.1) 84 | * [How To: E-ORA How to Configure PeopleSoft for Maximum Availability \[ID: 1446793.1\] 02/08/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1446793.1) 85 | * [How To: E-INST PT8.4x, PT 8.5x: How to Copy/Clone/Migrate/Refresh a PeopleSoft Environment \[ID: 643499.1\] 04/04/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=643499.1) 86 | * [Document: Lifetime Support Summary for PeopleSoft Releases \[ID: 2238983.2\] 19/03/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2238983.2) 87 | 88 | #### Platinum support 89 | * [Reference: Welcome to Oracle Platinum Services \[ID: 1605750.1\] 24/08/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1605750.1) 90 | * [Announcement: Platinum Welcome Community Call and OASP Call Schedule \[ID: 1960456.1\] 24/08/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1960456.1) 91 | * [Reference: How To Request Management Attention to a Service Request (SR) with Oracle Support Services \[ID: 199389.1\] 21/11/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=199389.1) 92 | * [Reference: Oracle Platinum Services – Quick Reference Guide \[ID: 1993848.1\] 21/11/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1993848.1) 93 | * [System Doc: Working Effectively With Oracle Support - Best Practices \[ID: 166650.1\] 16/05/2017](https://support.oracle.com/epmos/faces/DocContentDisplay?id=166650.1) 94 | * [How To: How to Schedule Exadata Patching Request using Oracle Advanced Support Gateway (OASG) Portal for Platinum Customers. \[ID: 2190010.1\] 26/07/2018](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2190010.1) 95 | 96 | #### RMAN 97 | * [FAQ: Top 10 Backup and Recovery Best Practices \[ID: 388422.1\] 12/12/2016](https://support.oracle.com/epmos/faces/DocContentDisplay?id=388422.1) 98 | * [How To: STEP BY STEP RMAN DUPLICATE Database From RAC ASM To RAC ASM \[ID: 1913937.1\] 16/05/2017](https://support.oracle.com/epmos/faces/DocContentDisplay?id=1913937.1) 99 | * [Problem: ORA-4062 During the Backup of FRA \[ID: 2007972.1\]](https://support.oracle.com/epmos/faces/DocContentDisplay?id=2007972.1) 100 | -------------------------------------------------------------------------------- /getting_started/tools.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Software and Tools 3 | layout: en 4 | permalink: /posts/getting_started/tools/ 5 | --- 6 | 7 | 8 | This page is a collection of different tools that I use to make a PS Admin's job easier. Some of these are freeware or open source while others are worth paying for. 9 | 10 | ## Security 11 | 12 | * [Password Safe][1] - Free Password Safe offers excellent security for all the passwords you manage. You could memorize your passwords (ugly), keep them on a spreadsheet (bad), or use Password Safe to keep all your passwords safely encrypted. The only password you need to remember is the safe's master password. Once you open the safe, just double-click on the password you want to use and paste password. You don't even need to know the underlying passwords! Password Safe also has a good password generator feature. You can set up the password rules and let it generate them for you. 13 | * [Keystore Explorer][2] - Free Keystore Explorer is a great tool for working with java keystore files, like `pskey`. The `pskeymanager` wrapper only offers a subset of functions for the Java `keytool` program. Keystore Explorer offers the same features as `keytool` but has a nice GUI to work with. 14 | 15 | ## Server Administration 16 | 17 | * [RDC Manager][3] - Free If you are in a Windows-heavy environment, this tools is a great way to manage all of your servers and remote connections. RDC Manager easily organizes all of your servers into groups, lets you connect to multiple RDC sessions, and saves your login credentials. 18 | 19 | * [mRemoteNG][4] - Free remote desktop tool that supports both RDP and PuTTy SSH connections. 20 | 21 | * [Beyond Compare][5] = $30 or $50 for Pro Beyond Compare is the best file and directory compare utility. It is incredibly fast for comparing two folder together, changing what differences you see, easily compares complex files and can synchronize folders. Beyond Compare is also scriptable, so you can take advantage of it's features on the command line. 22 | 23 | ## Development 24 | 25 | * [SublimeText][6] - Free to Try, $70 SublimeText is my favorite text editor. There are many editors to choose from, and I've tried lots, but I keep coming back to SublimeText. SublimeText has lots of plug-ins for editing and syntax highlighting, and is very responsive with large files. [Package Control][7] is a plug-in manager for SublimeText that makes it easy to install new plug-ins. Install Package Control when you open Sublime Text for the first time. 26 | 27 | * [Visual Studio Code][17] - Free, Visual Studio Code is a streamlined code editor with support for development operations like debugging, task running and version control. It aims to provide just the tools a developer needs for a quick code-build-debug cycle and leaves more complex workflows to fuller featured IDEs. 28 | 29 | * [Programmer's File Editor][8] - Free PFE has almost no modern features, but it does one thing well: it opens very large text files without any issues. Do you have 1GB trace file that needs to be searched? Use PFE. 30 | 31 | * [SQR Express][9] - $149 SQR Express is a great editor for SQR programs. The ability to run the program within the editor is wonderful and it has useful tools for writing SQR programs. 32 | 33 | * [TraceMagic][10] - Free TraceMagic simplifies much of the information in `.tracesql` files. TraceMagic will group SQL statements, show you all the tables in the FROM clause, tables that are being Updated or Inserted. It is much easier to find the errors using TraceMagic. You will need an Oracle Support account to download; search for Doc ID `1470578.1`. 34 | 35 | * [SQL Developer][11] - Free SQL Developer has really improved in the latest versions and I enjoy using it more than Toad. It's a great SQL tool when working on Oracle databases. Not much else to say, it's a solid tool. 36 | 37 | * [PSChrome Extension][12] - Free For Chrome only, but this extension has features to make working in PeopleSoft easier. I really like the Auto-Refresh on the Process Scheduler page and the Field Information mode. The Auto-Refresh will select the Refresh button on the Process Scheduler page at an interval you want. It's a simple way to watch what is happening on the scheduler. The Field Information mode will let you click on any text box, button, or label on a page and it gives you the record and field name. That saves a trip to App Designer. 38 | 39 | * [DataDumper Application Class][13] - Free The DataDumper application class let's you dump the structure and content of a PeopleCode object to file. You can even email the output so you don't have find it on the server. Import the `CHG_DataDumper` class and away you go. There is even a [great overview video on how to use the application class][14]. 40 | 41 | ## Documentation 42 | 43 | * [Instiki][15] - Free I have found that wiki is the best way to keep documentation as a PS Admin. Instiki is a very simple wiki that makes it easy to create pages, link topics, and reduces the amount of work to keep documentation up-to-date. It is a light-weight wiki based on Ruby on Rails which makes it easy to run on any server. 44 | 45 | * [Confluence](https://www.atlassian.com/software/confluence) - A cheap and powerful tool for team documentation. 46 | 47 | * [Trello](https://trello.com/) - Trello is a Kanban board that is great for managing lists. 48 | 49 | * [Slack][16] - Free for small teams 50 | 51 | Slack is essentially IRC, but web-based and app-based with better features. I love using it with remote teams because it replaces the hallway discussions and creates better communication within teams. 52 | 53 | [1]: http://www.pwsafe.org 54 | [2]: http://keystore-explorer.sourceforge.net 55 | [3]: http://www.microsoft.com/en-us/download/details.aspx?id=44989 56 | [4]: https://github.com/mRemoteNG/mRemoteNG 57 | [5]: http://www.scootersoftware.com 58 | [6]: http://www.sublimetext.com 59 | [7]: https://packagecontrol.io/installation#st3 60 | [8]: http://www.lancaster.ac.uk/~steveb/cpaap/pfe/pfefiles.htm 61 | [9]: http://www.bcstools.com 62 | [10]: http://support.oracle.com 63 | [11]: http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html 64 | [12]: https://chrome.google.com/webstore/detail/pschrome/cpgoncheakfjhldfbebekijoeaabnfeb?hl=en 65 | [13]: http://www.cedarhillsgroup.com/training-videos/peoplecode-debugging-with-the-datadumper 66 | [14]: http://www.cedarhillsgroup.com/knowledge-base/kbarticles/introduction-to-the-datadumper-logger 67 | [15]: https://github.com/parasew/instiki 68 | [16]: https://slack.com 69 | [17]: https://code.visualstudio.com/ 70 | -------------------------------------------------------------------------------- /images/ElasticHQOverview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/psadmin-io/psadmin-wiki/817827d51d4d42ab989490a08ca78a70cc1e8f67/images/ElasticHQOverview.png -------------------------------------------------------------------------------- /images/snippet.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/psadmin-io/psadmin-wiki/817827d51d4d42ab989490a08ca78a70cc1e8f67/images/snippet.gif -------------------------------------------------------------------------------- /images/ui/cones.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 5 | 7 | 8 | 10 | 13 | 14 | 16 | 18 | 19 | 21 | 23 | 25 | 28 | 30 | 34 | 36 | 37 | 39 | 41 | 42 | 44 | 46 | 48 | 51 | 53 | 57 | 58 | -------------------------------------------------------------------------------- /images/ui/docs-desktop.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 14 | 16 | 17 | 22 | 23 | 24 | 25 | 27 | 29 | 30 | 35 | 36 | 37 | 38 | 39 | 40 | 42 | 43 | 45 | 48 | 50 | 53 | 55 | 57 | 58 | 59 | 60 | 61 | 64 | 65 | 66 | Eat themhere or there? 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 85 | 86 | 87 | 89 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 151 | 152 | 153 | 155 | 156 | 158 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 168 | 169 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 219 | 220 | 221 | 223 | 224 | 225 | 227 | 228 | 229 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | 259 | 260 | 261 | 262 | 263 | 264 | 265 | 266 | 267 | 268 | 269 | 270 | 271 | 272 | 273 | 274 | 275 | 276 | 277 | 278 | 279 | 280 | 281 | 282 | 283 | 284 | 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | 294 | 295 | 296 | 297 | 298 | 299 | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 | 313 | 314 | 315 | 316 | 317 | 318 | 319 | 320 | 321 | 322 | 323 | 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 | 338 | 339 | 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 | 348 | 349 | 350 | 351 | 352 | 353 | 354 | 355 | 356 | 357 | 358 | 359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | 368 | 369 | 370 | 371 | 372 | 373 | 374 | 375 | 376 | 377 | 378 | 379 | 380 | 381 | 382 | 383 | 384 | 385 | 386 | 387 | 388 | 389 | 390 | 391 | 392 | 393 | 394 | 395 | 396 | 397 | 398 | 399 | 400 | 401 | 402 | 403 | 404 | 405 | 406 | 407 | 408 | 409 | 410 | 411 | 412 | 413 | 414 | 415 | 416 | 417 | 418 | 419 | 420 | 421 | 422 | 423 | 424 | 425 | 426 | 427 | 428 | 429 | 430 | 431 | 432 | 433 | 434 | 435 | 436 | 437 | 438 | 439 | 440 | 441 | 442 | 443 | 444 | 445 | 446 | 447 | 448 | 449 | 450 | 451 | 452 | 453 | 454 | 455 | 456 | 457 | 458 | 459 | 460 | 461 | 462 | 463 | 464 | 465 | 466 | 467 | 468 | 469 | 470 | 471 | 472 | 473 | 474 | 475 | 476 | 477 | 478 | 479 | 480 | 481 | 482 | 483 | 484 | 485 | 486 | 487 | 488 | 489 | 490 | 491 | 492 | 493 | 494 | 495 | 496 | 497 | 498 | 499 | 500 | 501 | 502 | 503 | 504 | 505 | 506 | 507 | 508 | 509 | 510 | 511 | 512 | 513 | 514 | 515 | 516 | 517 | 518 | 519 | 520 | 521 | 522 | 523 | 524 | 525 | 526 | 527 | 528 | 529 | 530 | 531 | 532 | 533 | 534 | 535 | 536 | 537 | 538 | 539 | 540 | 541 | 542 | 543 | 544 | 545 | 546 | 547 | 548 | 549 | 550 | 551 | 552 | 553 | 554 | 555 | 556 | 557 | 558 | 559 | 560 | 561 | 562 | 563 | 564 | 565 | 566 | 567 | 568 | 569 | 570 | 571 | 572 | 573 | 574 | 575 | 576 | 577 | 578 | 580 | 581 | 582 | 583 | 584 | 585 | 586 | 587 | 588 | 589 | 590 | 591 | 592 | 593 | 594 | 595 | 596 | 597 | 598 | 599 | 600 | 601 | 602 | 603 | 604 | 605 | 606 | 607 | 608 | 609 | 610 | 611 | 612 | 613 | 614 | 615 | 616 | 617 | 618 | 619 | 620 | 621 | 622 | 623 | 624 | 625 | 626 | 627 | 628 | 629 | 630 | 631 | 632 | 633 | 634 | 637 | 638 | 639 | 640 | 641 | 642 | 643 | 644 | 645 | 646 | 647 | 648 | 649 | 650 | 651 | 652 | 653 | 654 | 655 | 656 | 657 | 658 | 659 | 660 | 661 | 662 | 663 | 664 | 666 | 667 | 668 | 670 | 671 | 672 | 673 | 674 | 675 | 676 | 677 | 678 | 679 | 680 | 681 | 684 | 685 | 686 | 687 | 688 | 689 | 690 | 691 | 692 | 693 | 694 | 695 | 696 | 697 | 698 | 699 | 700 | 701 | 702 | 703 | 704 | 705 | 706 | 707 | 708 | 709 | 710 | 711 | 712 | 713 | 714 | 715 | 716 | 717 | 718 | 719 | 720 | 721 | 722 | 723 | 724 | 725 | 726 | 727 | 728 | 729 | 730 | 731 | 732 | 733 | 734 | 735 | 736 | 738 | 739 | 740 | 742 | 743 | 744 | 745 | 746 | 747 | 748 | 749 | 750 | 751 | 752 | 753 | 755 | 756 | 757 | 759 | 760 | 761 | 762 | 763 | 764 | 765 | 766 | 767 | 768 | 769 | 770 | 771 | 772 | 773 | 774 | 775 | 776 | 924 | 925 | 926 | 930 | 931 | 932 | 936 | 937 | 938 | 942 | 943 | 944 | 948 | 949 | 950 | 951 | 952 | 953 | 957 | 958 | 959 | 963 | 964 | 965 | 966 | 967 | 968 | 971 | 972 | 973 | 976 | 977 | 978 | 982 | 983 | 984 | 988 | 989 | 990 | 994 | 995 | 996 | 997 | 998 | 999 | 1003 | 1004 | 1005 | 1009 | 1010 | 1011 | 1014 | 1015 | 1016 | 1020 | 1021 | 1022 | 1023 | 1024 | 1025 | 1029 | 1030 | 1031 | 1034 | 1035 | 1036 | 1039 | 1040 | 1041 | 1045 | 1046 | 1047 | 1051 | 1052 | 1053 | 1057 | 1058 | 1059 | 1063 | 1064 | 1065 | 1066 | 1067 | 1068 | 1072 | 1073 | 1074 | 1077 | 1078 | 1079 | 1082 | 1083 | 1084 | 1087 | 1088 | 1089 | 1093 | 1094 | 1095 | 1098 | 1099 | 1100 | 1103 | 1104 | 1105 | 1108 | 1109 | 1110 | 1114 | 1115 | 1116 | 1119 | 1120 | 1121 | 1125 | 1126 | 1127 | 1130 | 1131 | 1132 | 1135 | 1136 | 1137 | 1140 | 1141 | 1142 | 1143 | 1144 | 1145 | 1149 | 1150 | 1151 | 1152 | 1153 | 1154 | 1156 | 1157 | 1158 | 1162 | 1163 | 1164 | 1168 | 1169 | 1170 | 1174 | 1175 | 1176 | 1177 | 1178 | 1179 | 1180 | 1181 | 1182 | 1185 | 1186 | 1187 | 1191 | 1192 | 1193 | 1194 | 1195 | 1196 | 1198 | 1199 | 1200 | 1203 | 1204 | 1205 | 1206 | 1207 | 1208 | 1211 | 1212 | 1213 | 1214 | 1215 | 1216 | 1218 | 1219 | 1220 | 1223 | 1224 | 1225 | 1228 | 1229 | 1230 | 1231 | 1232 | 1233 | 1235 | 1236 | 1237 | 1240 | 1241 | 1242 | 1245 | 1246 | 1247 | 1249 | 1250 | 1251 | 1253 | 1254 | 1255 | 1257 | 1258 | 1259 | 1260 | 1261 | 1262 | 1265 | 1266 | 1267 | 1269 | 1270 | 1271 | 1274 | 1275 | 1276 | 1277 | 1278 | 1279 | 1282 | 1283 | 1284 | 1287 | 1288 | 1289 | 1291 | 1292 | 1293 | 1296 | 1297 | 1298 | 1300 | 1301 | 1302 | 1304 | 1305 | 1306 | 1308 | 1309 | 1310 | 1313 | 1314 | 1315 | 1316 | 1317 | 1318 | 1320 | 1321 | 1322 | 1325 | 1326 | 1327 | 1330 | 1331 | 1332 | 1334 | 1335 | 1336 | 1339 | 1340 | 1341 | 1342 | 1343 | 1344 | 1347 | 1348 | 1349 | 1350 | 1351 | 1352 | 1355 | 1356 | 1357 | 1358 | 1359 | 1360 | 1362 | 1363 | 1364 | 1367 | 1368 | 1369 | 1370 | 1371 | 1372 | 1376 | 1377 | 1378 | 1379 | 1380 | 1381 | 1382 | 1383 | 1384 | 1385 | 1386 | 1387 | 1388 | 1389 | 1390 | 1391 | 1392 | 1393 | 1396 | 1397 | 1398 | 1401 | 1402 | 1403 | 1406 | 1407 | 1408 | 1409 | 1410 | 1411 | 1414 | 1415 | 1416 | 1418 | 1419 | 1420 | 1422 | 1423 | 1424 | 1427 | 1428 | 1429 | 1430 | 1431 | 1432 | 1433 | 1434 | 1435 | 1438 | 1439 | 1440 | 1441 | 1442 | 1443 | 1444 | 1445 | 1446 | 1449 | 1450 | 1451 | 1452 | 1453 | 1454 | 1455 | 1456 | 1457 | 1458 | 1459 | 1460 | 1462 | 1463 | 1464 | 1465 | 1466 | 1467 | 1468 | 1469 | 1470 | 1471 | 1472 | 1473 | 1474 | 1475 | 1476 | 1478 | 1479 | 1480 | 1481 | 1482 | 1483 | 1484 | 1485 | 1486 | 1487 | 1488 | 1489 | 1490 | 1491 | 1492 | 1493 | 1494 | 1495 | 1496 | 1497 | 1498 | 1500 | 1501 | 1502 | 1503 | 1504 | 1505 | 1506 | 1507 | 1508 | 1509 | 1510 | 1511 | 1513 | 1514 | 1515 | 1516 | 1517 | 1518 | 1519 | 1520 | 1521 | 1522 | 1523 | 1524 | 1526 | 1527 | 1528 | 1529 | 1530 | 1531 | 1532 | 1533 | 1534 | 1535 | 1536 | 1537 | 1539 | 1540 | 1541 | 1542 | 1543 | 1544 | 1546 | 1547 | 1548 | 1549 | 1550 | 1551 | 1552 | 1553 | 1554 | 1555 | 1556 | 1557 | 1558 | 1559 | 1560 | 1561 | 1562 | 1563 | 1565 | 1566 | 1567 | 1569 | 1570 | 1571 | 1572 | 1573 | 1574 | 1575 | 1576 | 1577 | 1578 | 1579 | 1580 | 1582 | 1583 | 1584 | 1585 | 1586 | 1587 | 1588 | 1589 | 1590 | 1591 | 1592 | 1593 | 1594 | 1595 | 1596 | 1598 | 1599 | 1600 | 1601 | 1602 | 1603 | 1604 | 1605 | 1606 | 1607 | 1608 | 1609 | 1610 | 1611 | -------------------------------------------------------------------------------- /images/ui/footer-logo.svg: -------------------------------------------------------------------------------- 1 | 3 | 4 | 5 | 6 | 9 | 13 | 15 | 17 | 22 | 25 | 26 | 27 | 29 | 30 | 37 | 42 | 43 | 44 | 45 | 48 | 51 | 54 | 55 | 57 | 64 | 65 | 70 | 71 | 72 | 90 | 92 | 94 | 95 | 97 | 98 | 99 | 100 | 103 | 106 | 112 | 113 | 114 | 115 | 116 | 117 | 119 | 121 | 124 | 126 | 130 | 134 | 137 | 139 | 147 | 149 | 150 | 152 | 153 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 167 | 170 | 171 | 173 | 174 | 175 | 176 | 177 | 178 | 180 | 181 | 183 | 184 | 185 | 204 | 207 | 208 | 210 | 212 | 213 | 216 | 218 | 219 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 234 | 236 | 239 | 240 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 252 | 253 | 254 | 255 | 257 | 274 | 276 | 277 | 278 | 279 | 281 | 283 | 285 | 287 | 289 | 290 | 302 | 304 | 305 | 307 | 308 | 310 | 312 | 314 | 315 | 316 | 320 | 325 | 327 | 329 | 367 | 368 | 369 | 370 | 372 | 373 | 374 | 377 | 378 | 381 | 382 | 487 | 488 | 489 | -------------------------------------------------------------------------------- /images/ui/icon-arrowtabs.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 5 | 8 | 9 | 10 | -------------------------------------------------------------------------------- /images/ui/icon-flag.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | -------------------------------------------------------------------------------- /images/ui/search.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 6 | 13 | 14 | -------------------------------------------------------------------------------- /images/ui/travis-logo.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 6 | 7 | 8 | 10 | 14 | 16 | 18 | 23 | 26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /middleware/cookie_configuration.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Cookie Configuration 3 | layout: en 4 | permalink: /posts/middleware/cookie_configuration 5 | --- 6 | 7 | # Cookie Configuration 8 | 9 | To make cookie management easier when managing multiple PeopleSoft environments and applications, use this pattern to simplify the cookie configuration. 10 | 11 | `[DBNAME]-PORTAL-PSJESSIONID` 12 | 13 | Replace `[DBNAME]` with your database name. This configuration is set in the `weblogic.xml` file for your PIA domain. Below is an example `weblogic.xml` file. 14 | 15 | ```xml 16 | 17 | 18 | 19 | PeopleSoft Internet Architecture 20 | 21 | 22 | 32 23 | HRDEV-PORTAL-PSJSESSIONID 24 | .psadmin.io 25 | USERID 26 | wl_servlet_sessions 27 | true 28 | 31 | 32 | 33 | -1 34 | true 35 | 36 | / 37 | 38 | ``` 39 | -------------------------------------------------------------------------------- /middleware/elastichq.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: ElasticHQ 3 | layout: en 4 | permalink: /posts/middleware/elastichq/ 5 | --- 6 | 7 | If you want a utility to help you monitor your Elasticsearch nodes and clusters, ElasticHQ is a plugin that can give you a nice GUI. 8 | 9 | ## Installation 10 | 11 | There are two ways you can install ElasticHQ. If your Elasticsearch server has access to the Internet, you can install the plugin from the command line: 12 | 13 | ```powershell 14 | cd $ES_HOME\bin 15 | .\plugin install royrusso/elasticsearch-HQ/v2.0.2 16 | ``` 17 | 18 | > You need to use version `2.0.2` with the Elasticsearch 2.3.2 that ships with PeopleTools 8.55 and 8.56. The latest version of ElasticHQ is built for Elasticsearch 5.x 19 | 20 | To manually install ElasticHQ: 21 | 22 | 1. [Download version 2.0.2 from here](https://github.com/royrusso/elasticsearch-HQ/releases) 23 | 1. Copy the .zip (or .tar) file to your Elasticsearch server. 24 | 1. Extract the .zip file to `$ES_HOME\plugins\hq` 25 | 1. Restart Elasticsearch 26 | 1. Log into ElasticHQ at http://localhost:9200/_plugin/hq with the `esadmin` account 27 | 28 | ## Using ElasticHQ 29 | 30 | ElasticHQ is meant to give you a read-only view of the system. If you want to make changes, I'd recomment you use Elasticsearch's REST API. 31 | 32 | To view a node, enter the URL into the box at the top and click 'Connect'. If your node is part of a cluster, ElasticHQ will show the cluster's nodes. You can view the size of indexes, the stats of each node, and the cluster stats as well. 33 | 34 | ![ElasticHQ Screenshot]({{ site.url }}/posts/images/ElasticHQOverview.png) 35 | 36 | -------------------------------------------------------------------------------- /middleware/elasticsearchmonitoring.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Elasticsearch Monitoring Tools 3 | layout: en 4 | permalink: /posts/middleware/elasticsearchmonitoring/ 5 | --- 6 | 7 | ## Elasticsearch Monitoring Tools 8 | 9 | Elasticsearch is an API-based tool so there are no delivered GUI tools to monitor Elasticsearch. If you want a GUI to view the status of a cluster, node or indexes, you can use these tools: 10 | 11 | * [ElasticHQ](https://wiki.psadmin.io/posts/middleware/elastichq/) 12 | * [Elasticsearch Head](https://mobz.github.io/elasticsearch-head/) 13 | * [Cerebro](https://github.com/lmenezes/cerebro) 14 | * [Monitoring (from Elasticsearch)](https://www.elastic.co/products/stack/monitoring) 15 | -------------------------------------------------------------------------------- /middleware/middleware.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Middleware 3 | layout: en 4 | permalink: /posts/middleware/ 5 | --- 6 | 7 | This section is for articles on WebLogic, Tuxedo, Java and other software supporting PeopleSoft. -------------------------------------------------------------------------------- /middleware/pia_404_errors.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: PIA 404 Errors 3 | layout: en 4 | permalink: /posts/middleware/pia_404_errors/ 5 | --- 6 | 7 | If you receive a 404 error when trying to open the PIA login page, or even the `/index.html` file at the root of your web server, this is most likely due to errors in your `web.xml` file. 8 | 9 | `$PS_CFG_HOME/webserv//application/peoplesoft/PORTAL.war/WEB-INF/web.xml` 10 | 11 | This file defines the filters used by WebLogic to control traffic, servlets that are registered, and MIME Type Mappings. If there are syntax errors in this file, the WebLogic application won't successfully start (even though the web server instance is booted). 12 | 13 | Syntax errors might be: 14 | 15 | * un-matched XML tags 16 | * duplicate tags 17 | 18 | After fixing the errors in `web.xml`, restart your web server. -------------------------------------------------------------------------------- /middleware/slow_weblogic_start.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Slow WebLogic Starts 3 | layout: en 4 | permalink: /posts/middleware/slow_weblogic_starts/ 5 | --- 6 | 7 | If Weblogic is booting slowly on Linux, it might be a low entropy situation. To view your entropy available: 8 | 9 | ```bash 10 | sudo watch -n 1 cat /proc/sys/kernel/random/entropy_avail 11 | ``` 12 | 13 | If entropy is less than 1000, you should install a tool to help generate more entropy. 14 | 15 | ## haveged 16 | 17 | [`haveged`](https://issihosts.com/haveged/) is one tool to help generate entroy on Linux. 18 | 19 | **Linux 6** 20 | ```bash 21 | sudo rpm -Uvh https://download.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm 22 | sudo yum install haveged -y 23 | sudo chkconfig haveged on 24 | sudo /usr/sbin/haveged -w 1024 25 | ``` 26 | 27 | **Linux 7** 28 | ```bash 29 | sudo rpm -Uvh http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm 30 | sudo yum install haveged -y 31 | sudo systemctl enable --now haveged 32 | ``` 33 | 34 | ### Verify Entropy Levels 35 | Test that entropy is added to the system. 36 | 37 | ```bash 38 | cat /dev/random | rngtest -c 1000 39 | ``` -------------------------------------------------------------------------------- /pca/cleanup.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: DPK Cleanup Process 3 | layout: en 4 | permalink: /posts/pca/cleanup/ 5 | --- 6 | 7 | ## DPK Cleanup Process 8 | 9 | The DPK uses a process called "cleanup" to remove installed software and domains. The cleanup process uses Puppet to delete installed files and folders. You can run the cleanup process two ways: 10 | 11 | 1. The bootstrap script 12 | 1. Using `puppet apply` 13 | 14 | ### The bootstrap script 15 | 16 | The bootstrap scripts (`psft-dpk-setup`) has a parameter you can pass to remove installed software: 17 | 18 | *8.55 DPK on Windows* 19 | ```powershell 20 | .\psft-dpk-setup.ps1 --cleanup 21 | ``` 22 | *8.56 DPK on Windows* 23 | ```bat 24 | .\psft-dpk-setup.bat --cleanup 25 | ``` 26 | *Linux* 27 | ```powershell 28 | .\psft-dpk-setup.sh --cleanup 29 | ``` 30 | 31 | 32 | ### Using puppet apply 33 | 34 | To run the cleanup process with Puppet, you set the `ensure: absent` parameter in the `defaults.yaml` file. When you run `puppet apply`, Puppet will remove everything it knows about. 35 | 36 | ### Controlling the cleanup process 37 | 38 | If there is software, domains or users you want to keep, you can use your `psft_customizations.yaml` file to keep things. For example, if you want to keep your old PS_HOME folder, copy the `ps_home:` hash to your `psft_customizations.yaml` file and add the `remove: false` to the hash: 39 | 40 | ```yaml 41 | ps_home: 42 | db_type: "%{hiera('db_platform')}" 43 | unicode_db: "%{hiera('unicode_db')}" 44 | location: "%{hiera('ps_home_location')}" 45 | remove: false 46 | ``` 47 | 48 | Many of the hashes in the `psft_deployment.yaml` and `psft_unix_system.yaml`support the `remove: false` setting. -------------------------------------------------------------------------------- /pca/cloud_manager.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Cloud Manager Overview 3 | layout: en 4 | permalink: /pca/cloud_manager/ 5 | --- 6 | 7 | This page will contain an overview of PeopleSoft Cloud Manager. 8 | 9 | # DPK Files Repository 10 | 11 | Below is an example of how Cloud Manger organizes DPK files in the Download Repository. 12 | 13 | ``` 14 | /cm_psft_dpk/dpk 15 | ├── linux 16 | | ├── IH 17 | | │   ├── 11 18 | | │   │   ├── IH-910-UPD-011-LNX_1of11.zip 19 | | │   │   ├── IH-910-UPD-011-LNX_2of11.zip 20 | | │   │   └── ... 21 | | │   └── custom 22 | | │   └── ODS-DPK-LNX-12.1.0.2-200114.zip 23 | │ ├── FSCM 24 | │ ├── HCM 25 | │ ├── ELM 26 | │ ├── CRM 27 | │ ├── CS 28 | │ └── tools 29 | │ ├── 858 30 | │ │ ├── 06 31 | │ │   │   ├── PEOPLETOOLS-LNX-8.58.06_1of4.zip 32 | │ │   │   ├── PEOPLETOOLS-LNX-8.58.06_2of4.zip 33 | │ │   │   └── ... 34 | │ │ └── custom 35 | │ │ ├── COBOL-DPK-LNX-8.58_03.zip 36 | │ │ ├── ELK-DPK-LNX-7.0.0_03.zip 37 | │ │ ├── ILOG-CPLEX-12.7.1_01.zip 38 | │ │ └── PT-INFRA-DPK-LNX-8.58-200720.zip 39 | │ ├── 857 40 | │ └── ... 41 | └── windows 42 | └── ... 43 | ``` 44 | 45 | # File Structure Example 46 | Example from a Cloud Manager deployed instance. 47 | 48 | ``` 49 | /u01/app.oracle/product 50 | ├── db 51 | ├── 52 | | ├── dpk 53 | | │   ├── archives 54 | │   | ├── pt-manifest 55 | | │   ├── puppet 56 | | │   └── readme.txt 57 | | ├── home 58 | | │   ├── esadm1 59 | | │   ├── oracle2 60 | | │   ├── psadm1 61 | | │   ├── psadm2 62 | | │   └── psadm3 63 | │   └── ps_cfg_home 64 | |    ├── appserv 65 | |    ├── ... 66 | |    └── webserv 67 | └── pt 68 | ├── bea 69 | │   ├── ... 70 | │   ├── tuxedo 71 | │   └── wlserver 72 | ├── jdk1.8.0_241 73 | ├── oracle-client 74 | ├── ps_home8.58.03 75 | └── tools_client 76 | ``` 77 | -------------------------------------------------------------------------------- /pca/common_dpk_errors.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Common DPK Errors 3 | layout: en 4 | permalink: /pca/common_dpk_errors/ 5 | --- 6 | 7 | Here are some common DPK errors and how to resolve them. 8 | 9 | ## This platform is not supported 10 | 11 | This error can occur when running the bootstrap script (`psft-dpk-setup`) if the `setup` folder is in the wrong location. After downloading the DPK files, you need to extract the first .zip file. Make sure the `setup` folder from the first .zip file (and other files from the .zip file) are at the same directory as the remaining .zip files. 12 | 13 | If the `setup` folder is one level deeper (e.g, under `PEOPLETOOLS-WIN-8.56.02_1of4\setup`) you will see this error. 14 | 15 | . 16 | ├── PEOPLETOOLS-WIN-8.56.02_1of4 17 | │   ├── setup 18 | │   └── readme.txt 19 | ├── PT-DPK-WIN-8.56.02-1of2.zip 20 | ├── PT-DPK-WIN-8.56.02-2of2.zip 21 | ├── PTC-DPK-WIN8.56.02-1of1.zip 22 | 23 | To resolve the error, move the `setup` folder (and other files in the directory) up one level. 24 | 25 | . 26 | ├── PT-DPK-WIN-8.56.02-1of2.zip 27 | ├── PT-DPK-WIN-8.56.02-2of2.zip 28 | ├── PTC-DPK-WIN8.56.02-1of1.zip 29 | ├── readme.txt 30 | └── setup 31 | 32 | 33 | ## found character that cannot start any token while scanning for the next token 34 | 35 | This error will display during the Puppet catalog build. The catalog build is when Puppet is performing Hiera lookups. The error can result from two common causes: 36 | 37 | 1. The YAML file has a Tab character in it 38 | 1. A string with special characters is not quoted 39 | 40 | To resolve the first issue, use your text editor to convert any Tab characters into spaces. For the second issue, make sure you use single quotes around passwords or any value that has special characters in it. 41 | -------------------------------------------------------------------------------- /pca/custom_facts.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Custom Facts 3 | layout: en 4 | permalink: /posts/pca/custom_facts/ 5 | --- 6 | 7 | You can easily deploy custom facts to your server for use with the DPK and Puppet. Facter has a number of built-in facts, like `::hostname`, but we can use our own. 8 | 9 | ## facts.d 10 | 11 | Under the `C:\ProgramData\puppetlabs\facter\facts.d\` folder, we can put YAML file with custom values. 12 | 13 | ```yaml 14 | --- 15 | ps_role: provider 16 | region: dev 17 | app: hr 18 | ``` 19 | 20 | You can save the file as `facts.yaml`. 21 | 22 | ## Ruby Facts 23 | 24 | Another option is to implement facts via Ruby. There are many locations the ruby script can live, but one option is to create a new "facts" module under the delivered `modules` directory. Create a folder structure similar to this: 25 | 26 | ``` 27 | modules 28 | └───facts 29 | └───lib 30 | └───facter 31 | 32 | ``` 33 | 34 | In this directory, create a script such as `facts.rb`: 35 | 36 | ```ruby 37 | require 'facter' 38 | 39 | Facter.add(:application) do 40 | setcode do 41 | application = 'hcm' 42 | application 43 | end 44 | end 45 | ``` 46 | In these scripts you can use all sorts of logic using other facts, regex, and conditionals to create facts based upon the current environment (such as hostname, operating system, other facts, etc). This is just a small hardcoded example. 47 | 48 | ## Hiera and Custom Facts 49 | 50 | In your `psft_customizations.yaml` file, you can reference these facts. For example, if you wanted your PIA domains to include the region in the name, the YAML would look like this: 51 | 52 | ```yaml 53 | pia_domain_list: 54 | "peoplesoft-%{::region}": 55 | ``` 56 | 57 | ## Fact Override 58 | 59 | You can also override some facts using environment variables. To override a fact, set an environment variable like `$env:FACTER_factname="newvalue"`. The environment variable must start with `FACTER_`. 60 | -------------------------------------------------------------------------------- /pca/pca.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Cloud Architecture 3 | layout: en 4 | permalink: /posts/pca/ 5 | --- 6 | 7 | The PeopleSoft Cloud Architecture section includes the following technologies: 8 | 9 | * Deployment Packages 10 | * Automated Configuration Management 11 | * Puppet/Facter/Hiera 12 | * Anything related deploying software and managing server configuration -------------------------------------------------------------------------------- /pca/pi_passwords.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: PeopleSoft Image Passwords 3 | layout: en 4 | permalink: /posts/pca/pi_passwords/ 5 | --- 6 | 7 | ## PeopleSoft Image Passwords 8 | 9 | With PeopleTools 8.56, there are some new passwords you create when installing a PeopleSoft Image. Each password has different complexity requirements, so it can be confusing when creating demo passwords. Here is a sample file of passwords to use: 10 | 11 | 12 | 13 | The `admin_pwd` password is a new field for 8.56. This password is for the `SYS` and `SYSTEM` account in Oracle Database. The complexity requriements are strange; a special character is required but the special character can only be `_` `-` or `#`. -------------------------------------------------------------------------------- /pca/puppet_helpers.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Puppet Helper Functions 3 | layout: en 4 | permalink: /posts/pca/puppet_helpers/ 5 | --- 6 | 7 | ## Puppet Apply Powershell Function 8 | With 8.56, the command line to run Puppet with the DPK got longer. You have to pass in the `--confdir` parameter and path every time you run Puppet. 9 | 10 | To simplify the command, a simple Powershell function can be used to run the DPK. Add this function to your `C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell_profile.ps1` file. 11 | 12 | ```powershell 13 | function pa { 14 | $starttime = $(get-date) 15 | set-location c:\psft\dpk\puppet 16 | stop-service Psft* 17 | puppet apply .\manifests\production\site.pp --confdir=c:\psft\dpk\puppet --strict off -d 18 | $elapsedtime = $(get-date) - $starttime 19 | Write-Output "Run Time: ${elapsedtime}" 20 | } 21 | ``` 22 | 23 | ## Hiera Lookup Snippet 24 | When doing a lot of Hiera lookups in your YAML files, it can be tedious to type out the `%{hiera('')}` string everytime. Here is a handy VSCode "snippet" for making this easier. If the YAML Language extension is installed [(redhat.vscode-yaml)](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml), `lookup` will be able to autocomplete into the snippet, using `tab` to get inside, and then out of the hiera lookup. Add a new user snippet for the YAML file type with the following code: 25 | 26 | ```json 27 | "lookup": { 28 | "prefix": "lookup", 29 | "body": ["\"%{hiera('$1')}\"$0"], 30 | "description": "Hiera Lookup Snippet" 31 | } 32 | ``` 33 | ![hiera-snippet](../../images/snippet.gif "Snippet Gif") 34 | -------------------------------------------------------------------------------- /pca/sample_yaml.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sample psft_customizations.yaml 3 | layout: en 4 | permalink: /posts/pca/sample_yaml/ 5 | --- 6 | 7 | ## Sample psft_customizations.yaml File 8 | 9 | Below is a sample `psft_customizations.yaml` file to give you an idea of how to define configuration for the DPK. 10 | 11 | 12 | -------------------------------------------------------------------------------- /peopletools/hardcoded_roles.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Hardcoded Roles 3 | layout: en 4 | permalink: /posts/peopletools/hardcoded_roles/ 5 | --- 6 | 7 | There's a few hardcoded roles that if you don't know about, you can spend hours debugging why data is missing, or something isn't working. 8 | 9 | Some aren't strictly hardcoded, but are good bootstrap roles that give you the right permission lists to get productive quicker. 10 | 11 | The are mostly just for admin/priveleged accounts, and should probably not be used everyday in Production. 12 | 13 | # PeopleTools 14 | 15 | ## PeopleSoft Administrator 16 | 17 | The godfather. Gives you full access to all pages/components, and bypasses permission list security 18 | 19 | ## Portal Administrator 20 | 21 | The godmother. Gives you full access to the portal objects (folders and content refs), so you can find and navigate to all components (which you then access via PeopleSoft Administrator role) 22 | 23 | ## ProcessSchedulerAdmin 24 | 25 | Allows you to see all processes in *PeopleTools > Process Scheduler > Process Monitor* 26 | 27 | ## ReportSuperUser 28 | 29 | Allows you to see all reports in *PeopleTools > Reporting Tools > Report Manager* 30 | 31 | ## ADS Designer 32 | 33 | Allows you to apply delivered change packages that use Application Data Sets via Change Assistant without complaint 34 | 35 | ## PivotGridAdmin 36 | 37 | Allows you to see all the delivered (and other users') pivot grids via *Reporting Tools > Pivot Grids > Pivot Grid Wizard* 38 | 39 | ## XMLP Report Developer 40 | 41 | I don't think you can get far in *Reporting Tools > BI Publisher* without this. 42 | 43 | ## Search Administrator, Search Developer 44 | 45 | Use these when seeing up Elasticsearch using the activity guides 46 | 47 | # HCM 48 | 49 | # Financials 50 | 51 | # Campus 52 | -------------------------------------------------------------------------------- /peopletools/peopletools.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: PeopleTools 3 | layout: en 4 | permalink: /posts/peopletools/ 5 | --- 6 | 7 | This section is for articles on PeopleTools features. This includes features on the *PeopleTools* menu like: 8 | 9 | * Security 10 | * Search Framework 11 | * Integration Broker 12 | * Web Profile 13 | * Performance Monitor -------------------------------------------------------------------------------- /peopletools/resend-content-sql.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mass Resend Reports 3 | layout: en 4 | permalink: /posts/peopletools/resend_content_sql/ 5 | --- 6 | 7 | [David Kurtz has a great post on resending reports in a "Not Posted" status](http://blog.psftdba.com/2008/04/bulk-re-sending-batch-output-to-report.html). The SQL he provides works on Oracle. The SQL below will do the same on MS SQL Server. 8 | 9 | ```sql 10 | 11 | DECLARE @PRCSINSTC INT; 12 | 13 | DECLARE PROCESSINSTANCE_CURSOR CURSOR FOR 14 | SELECT PRCSINSTANCE 15 | FROM PSPRCSRQST 16 | WHERE DISTSTATUS = 4 --THAT ARE NOT POSTED 17 | AND RUNSTATUS = 9; --SUCCESSFUL PROCESSES 18 | 19 | OPEN PROCESSINSTANCE_CURSOR 20 | FETCH NEXT FROM PROCESSINSTANCE_CURSOR INTO @PRCSINSTC 21 | WHILE @@FETCH_STATUS = 0 22 | BEGIN 23 | PRINT @PRCSINSTC 24 | UPDATE PSPRCSRQST 25 | SET DISTSTATUS = '7' 26 | WHERE PRCSINSTANCE = @PRCSINSTC; 27 | 28 | UPDATE PSPRCSQUE 29 | SET DISTSTATUS = '7' 30 | WHERE PRCSINSTANCE = @PRCSINSTC; 31 | 32 | UPDATE PS_CDM_LIST 33 | SET DISTSTATUS = '8' 34 | , TRANSFERINSTANCE = 0 35 | WHERE PRCSINSTANCE = @PRCSINSTC 36 | AND DISTSTATUS <> '5'; --POSTED 37 | FETCH NEXT FROM PROCESSINSTANCE_CURSOR INTO @PRCSINSTC 38 | END; 39 | CLOSE PROCESSINSTANCE_CURSOR; 40 | DEALLOCATE PROCESSINSTANCE_CURSOR; 41 | GO 42 | ``` -------------------------------------------------------------------------------- /peopletools/search-callback-user.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Search Framework Call Back User 3 | layout: en 4 | permalink: /posts/peopletools/search_callback_user/ 5 | --- 6 | 7 | In Oracle Support and in PeopleBooks, the Search Framework call back user is said to require the `PeopleSoft Administrator` role. Given the power that role gives to a user, this breaks many security policies. Thankfully, this role isn't required for the call back user. Instead follow these guidelines for security with the call back user: 8 | 9 | * Set `PTPT3100` as the Primary, Process Profile, and Row Security Permission List 10 | * Assign the following roles: 11 | * `PeopleSoft User` 12 | * `Search Administrator` 13 | * `Search Developer` 14 | * `Search Query Administrator` 15 | * `Search Server` 16 | * `Search-xxx` 17 | 18 | For your application, the `Search-xxx` Role will give access to the Search Catetories you want to deploy. These roles will change depending on your application and configuration. 19 | -------------------------------------------------------------------------------- /talks/adv_ps_admin.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Advanced PeopleSoft Administration 3 | layout: en 4 | permalink: /posts/talks/adv_ps_admin/ 5 | --- 6 | 7 | ### PeopleSoft Administration 8 | 9 | * [Advanced PeopleSoft Administration - September 2020](https://wiki.psadmin.io/talk.adv-ps-admin2/) 10 | -------------------------------------------------------------------------------- /talks/oci.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Oracle Cloud Infrastructure 3 | layout: en 4 | permalink: /posts/talks/oci/ 5 | --- 6 | 7 | ### Oracle Cloud Infrastucture 8 | 9 | * [Fireside Chat: PeopleSoft and Oracle Cloud](https://wiki.psadmin.io/talk.psa-and-oci) -------------------------------------------------------------------------------- /talks/talks.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Talks 3 | layout: en 4 | permalink: /posts/talks/ 5 | --- 6 | 7 | Talks from psadmin.io 8 | 9 | ### PeopleSoft Administration 10 | 11 | * [Advanced PeopleSoft Administration - September 2020](https://wiki.psadmin.io/talk.adv-ps-admin2/) 12 | 13 | ### Oracle Cloud Infrastucture 14 | 15 | * [Fireside Chat: PeopleSoft and Oracle Cloud](https://wiki.psadmin.io/talk.psa-and-oci) --------------------------------------------------------------------------------