Content Contributed by Biju Narayanan
This post is the first in a series on Configuration Management
PeopleSoft system administrators have generally spent a good deal of time on manual, repetitive tasks while setting up and configuring their PeopleSoft system. When you set up a new PeopleSoft demo environment or upgrade/clone environments, considerable effort is spent on configuration-related activities. This often involves going through hundreds of user interface pages to manually configure functional components like Integration Broker, Secure Enterprise Search, Process Scheduler, and so on. Testing for correctness is also required. If you cloned or made copies of systems configurations, they needed to be redone. Host name entries are spread within many configurations from webserver to appserver tiers and in many objects within databases, which adds to the challenge.
With PeopleSoft 8.55, configuration is centralized with the Cloud Deployment Architecture (CDA). Deployment Packages (DPK) are a new delivery mechanism provided with PeopleTools 8.55 (for use with Linux and Windows operating systems). Deployment Packages contain all the software created by PeopleSoft as well as the required components pre-installed and fully patched, along with a deployment and configuration automation system. In addition, all Update Images delivered after 8.55 will also take advantage of the Deployment Framework, and will be comprised of Deployment Packages. DPKs have three parts:
With DPKs configuration is centralized in Pupprt configuration files, and can be customized by overriding configuration attributes in psft.customizations.yaml.
Automated Configuration Manager (ACM) is a tool set available beginning with PeopleTools 8.54. It is used to automate PeopleTools product configuration. ACM allows you to externalize product configuration as a template and then use the template to automate configurations across systems. ACM comes with graphical user interfaces, command-line tools, and a suite of configuration plugins that help administrators configure the base PeopleSoft components.
Peopletools 8.55 delivers the following predefined templates that you can start with.
The other functional plugins include the following:
An administrator typically performs the following process to develop a configuration automation template. The template contains configuration units, and the sequence and dependencies in which the configuration has to be automated. After the template is developed, it is tested and used as a base version to automate other environments.
4. Test and Debug: After the execution you can monitor and debug the execution by navigating to PeopleTools>Automation Configuration Manager>Monitor
After you generate a working version of the template, you can keep it as a configuration baseline and use it to clone configurations across multiple environments. The template is the source of truth for configuration, and ACM allows you to re-run the configuration any number of times.