Oracle continues to add significant features to PeopleSoft Cloud Manager that make day to day operations simpler and more automated. Image 12 is the latest release of Cloud Manager and it’s packed with new capabilities in day to day operations and lifecycle management that customers can exploit - resulting in real, measurable cost savings and ease of use.
Policy Manager is probably my second favorite feature that Cloud Manager has. Why? It gives customers the ability to use both events and scheduling to take action. For instance, when a new PRP is issued by an application, Policy Manager can be configured to recognize the event (the release of the PRP) and take an action like applying it to a PUM instance. In doing so, you can always have an up to date PUM instance available. Policy Manager can do the same with PeopleTools patches or upgrades – as soon as a new patch is released, Policy Manager can apply it for you.
The other big benefit with Policy Manager involves scheduling actions. This could be bringing up environments each day, and taking them offline at the end of the day or over the weekend. With the environments AUTOMATICALLY being made available to your staff, and only when they need them, you’re going to be saving time and energy in your IT staff, as well as saving the resources that would have otherwise been wasted with environments up and running when no one is using them. Development, QA, sandbox environments, PUM environments, demo systems...all can take advantage.
Policy Manager can help throughout the day as well. If you see a spike in activity and usage increases beyond a threshold, Policy Manager can bring additional app/web servers online. Additionally, backups can be scheduled for production environments as well as things like a nightly backup for development environments.
When a policy is set up, it can be used by any number of environments; define it once, and use it over and over with no additional set up required.
You can expect that we’re going to keep looking to expand Policy Manager’s capabilities. We’re laser focused on automation when it comes to dealing with the day to day operations of PeopleSoft applications. We’re exploring how we can incorporate machine learning for things like predicting and proactively preparing for usage spikes. Stay tuned – there’s more to come with Policy Manager.
Speaking of automation, by now I’m sure you’ve heard at least something around Oracle’s Autonomous Database – if not, let me know and I can help introduce you to your technical sales rep. ;-)
Cloud Manager will now manage environments using Autonomous Database on Dedicated Exadata infrastructure (ADB-D). Autonomous database manages the database for you, automating things like patching, tuning and backups. While PeopleTools is certified with both ADB-D and Autonomous Database on Shared Exadata Infrastructure (ADB-S), Cloud Manager initiated Autonomous support with ADB-D. ADB-S is planned to be supported by Cloud Manager in a future update.
Check out this Tech Update for more information on PeopleTools support of Autonomous Database:
Tech Update – PeopleSoft Extends Support for Oracle Autonomous Database Doc ID 2765965.1
I’ve spoken with a number of customers that love the benefits of Cloud Manager, but had a hard requirement of utilizing the Government Cloud on Oracle Cloud Infrastructure (OCI) that meets standards like FedRAMP and DISA level 5. The good news is that Cloud Manager now supports managing environments housed in the Government Cloud. Any federal, state or local government agencies that were waiting on these standards may now start using Cloud Manager with Government Cloud on OCI.
One of the customer enhancement requests that we received is to have the Windows client and the Process Scheduler sharing a node. We were told It didn’t make sense to have each on their own node – this was inefficient and wasted resources. Well, that’s true. So in the spirit of saving resources and simplifying the configuration, you can now configure the Windows Client and the Process Scheduler on the same node. I think Sparky and Clippy would approve.
There are a number of reasons why a customer might need to import an environment into Cloud Manager. Perhaps and environment wasn’t on PeopleTools 8.55 or above, the minimum requirement for Cloud Manager. Maybe you needed to convert an environment from Windows to Linux. The ability to import environments into Cloud Manager in order to reap the benefits provided by Cloud Manager is important. However, we had a hole in the solution where instances that were cloned could not be imported. This has now been resolved. Environments that have been cloned, along with a Windows Process Scheduler, may now be imported to Cloud Manager.
PeopleSoft Cloud Manager Image 12 is the avenue to take to obtain the latest PeopleTools release, 8.59. Check out Dave's blog, Oracle Releases PeopleTools 8.59 to find out some of the highlights of the release. PeopleTools releases have moved to a cloud-first deployment model, so if you want to start playing with PeopleTools 8.59, set up your Cloud Manager subscription to PeopleTools 8.59, and let Cloud Manager perform the automated upgrade for you. For those wondering, the automated PeopleTools upgrade is still my favorite feature in Cloud Manager; although, Policy Manager is pretty cool and is a close second. What’s your favorite feature?
Would you like to see more information on Image 12? We’ve got it for you! Check out the PeopleSoft Cloud Manager Image 12 Highlights video. Use the following if you want to investigate a particular enhancement:
- Policy Manager (Starts at 0:08)
- Autonomous Database – Dedicated (Starts at 3:43)
- Government Cloud Support (Starts at 5:54)
- Import Cloned Environments & Windows Process Scheduler (Starts at 6:36)
- Enable Node Sharing for Windows Client and Process Scheduler (Starts at 7:13)