This week on the podcast, Kyle finds that Cloud Manager removed a feature and Dan discusses some architectural designs for Integration Broker.
This week on the podcast, Charlie Sinks joins us to recap the Reconnect 2020 conference. We share our favorite sessions from the week, some of the things we learned this week, and what we liked about the virtual format.
- Virtual Format Likes and Dislikes @ 1:30
- Session Recaps @ 17:00
- PeopleSoft Product Update
- PeopleTools Roadmap
- Elasticsearch Best Practices
- Remote Client Functionality
- Platform Overview
- File Integration Framework
- Baking more than PI with OCI
- Taking PeopleSoft Swimming in an Instance Pool
- Running PeopleSoft on OCI
- Jim Marion Sessions
- PeopleTools Product Panel
This week on the podcast, Dan and Kyle talk about psadmin.io Cloud Operations. .io Cloud Ops is the methodology and tools we use to run PeopleSoft on Oracle Cloud Infrastructure. We discuss what it is and talk about the new open source tools that help us run PeopleSoft on OCI.
- PSUG – OCI Fireside Chat @ 1:00
- PeopleSoft Innovator Summit – Advanced PeopleSoft Administration @ 3:00
- Upcoming Openings for Dan and Kyle @ 6:30
- Why DPK? Automation? @ 8:30
- psadmin.io Cloud Operations @ 12:00
- Resource Manager Drift Detection @ 25:00
This week on the podcast, Kyle and Dan discuss Rundeck and how to manage scripts used by Rundeck, share their virtual meeting tips, get back on the conference speaking circuit.
- Upcoming sessions at events @ 1:00
- PSUG OCI Fireside Chat
- Appsian PeopleSoft Summit – Advanced PeopleSoft Administration
- Running PeopleSoft on OCI (Dan)
- Taking PS swimming in an OCI Instance Pool (Kyle)
- Baking more than PI with OCI (Kyle)
- .conf 2021 @ 9:00
- Virtual Meeting Tips @ 10:00
- Rundeck Script Management @ 23:30
- Where does Rundeck fit? @ 33:00
This week on the podcast, Kyle and Dan talk about Elasticsearch Direct Transfer architecture and a few edge cases with the setup. They also remind everyone about mosbot, and also talk about accessing metadata on OCI instances.
This week on the podcast, Dan and Kyle discuss autonomous database and linux support with PeopleSoft, Kyle shares some follow-up on Instance Pools, and Dan explains why a Pre-Production environment is important.
This week on the podcast, Dan shares a tip to generate App Designer crash logs, Kyle talks about adapting and learning to new technologies and some tips for using the OCI CLI.
- Adapting to new things @ 1:30
- App Designer Dump Files @ 6:00
- PeopleTools 8.58 Overview Course @ 10:15
- Cloud Manager 11 Backup and Restore @ 12:45
- Cloud Manager Start/Stop Domains @ 18:00
- oci_cli_rc @
This week on the podcast, Dan talks about using ACM for basic configuration and his tips for using proxies to debug search and IB issues. Kyle shares how he used Terraform and Resource Manager to auto-deploy Cloud Manager.
This week on the podcast, Dan talks about a contextual Nav Bar idea and then he and Kyle discuss the idea of using the Cloud Manager libraries for general automation.
- Quick Start Reference for PeopleSoft Update Images on PeopleTools 8.58 @ 3:00
- 8.58 First Thoughts @ 5:00
- PeopleSoft and Elasticsearch Security Examined @ 13:15
- Presentation: PeopleSoft and ElasticSearch Security Examined
- Cloud Manager Kit @ 16:45
Now that Cloud Manager is here, we have self-service ability to create PeopleSoft environments in OCI. Cue Uncle Ben… “With great power comes great responsibility.” Having a self-service portal that allows for the creation of these environments is fantastic, but how do we put some controls around this awesome power? This is where Environment Template security comes in to play.
To create an Environment in Cloud Manager, you first need an Environment Template. This template is created using some General Details, a Topology, and finally Security. It is this security detail that will help us control who can use these templates to create environments in the future. When you are creating a template, you will see the following section 3 – Define Security in the wizard. Let’s break down what our options are.
Assign Template to Zone(s)
Templates can be assigned to a single or multiple Zones. As of Image 11, there are currently three zones to choose from:
A Zone is just “a logical grouping of environments,” according to Oracle’s Cloud Manager FAQ. At this time, it doesn’t serve any other purpose outside of helping you organize your environments. I could see a level of security being added to Zones in the future. If not by Oracle, maybe a custom bolt-on?
Assign Template to Role(s)
Templates can also be assigned to PeopleSoft security Roles. Any user that has a Role specified in this section will have the ability to create an Environment based on this template. Cloud Manager delivers three roles intended to be used with templates:
- Cloud Administrator (PACL_CAD)
- Cloud PeopleSoft Administrator (PACL_PAD)
- Self-Service User (PACL_SSC)
As you would expect with PeopleSoft security, you are free to create and use your custom roles here. I think the delivered roles make it clear how Oracle sees the breakdown of potential users. Users who admin OCI resources, users who admin PeopleSoft, and users of PeopleSoft who might want ad-hoc environments(thinking developers or maybe even business staff looking for demos). I could see the OCI and PS admin roles combined often. Also, the self-service user might be split out into a technical and functional role or disabled altogether. Each organization will have to review this for themselves and come up with a good policy. Just keep in mind, you can add multiple roles to each template.
Once the security and other details are added to a template, it will be available to use when creating an Environment.
Only the templates the user has access to will be in the Template Name dropdown. The Zone dropdown will also be populated with available zones from the selected template. If a single zone were added, this would be auto-selected and read-only.
Overall, I feel that Environment Template security offers a lot of control. It gives us enough control to provide a level of self-service environment deployments if desired. I do look forward to seeing actual functionality added to Zones. It might be easier to manage this security if we could somehow control access by zone versus strictly individual template security.