PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Agenda  What is Change Assistant  Overview  Installation  Environment Management Framework (EMF)  Change Assistant (CA)  Common Setup Issues  Functionality  Fix Application Process  Tips from the Field  Questions

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Overview 1. Discover & Analyze 2. Select & Download 3. Apply, Test and Deploy What fits my system? Version, Applications, Languages What do I need for regulatory compliance? What is already applied? Review documentation Find dependencies Pre-requisites Post-requisites Translations Re-analyze if needed Download Determine Order Apply to Demo Compare to Dev Re-customize Re-package and re-install (3+ times) Fix Application Process

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Overview 1. Discover & Analyze 2. Select & Download 3. Apply, Test and Deploy What fits my system? Version, Applications, Languages What do I need for regulatory compliance? What is already applied? Review documentation Find dependencies Pre-requisites Post-requisites Translations Re-analyze if needed Download Determine Order Apply to Demo Compare to Dev Re-customize Re-package and re-install (3+ times) Fix Application Process - Automated Activity using Change Assistant

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Overview What is Change Assistant?  Introduced with PeopleTools 8.44  Applies Change Packages  Standalone Windows Application  Similar in Functionality to Upgrade Assistant  Introduced with PeopleTools 8.44  Works with the Environment Management Framework

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Environment Management Framework  Carries Out Commands Remotely  Framework Consists of:  Hub - Central Repository  Agent(s) - Responsible for collecting/sending/receiving Change Assistant EM Agent EMF Hub File,App,Prcs,Web (Agents) Database Server (Agents)

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. EMF Architecture  Environment Management Framework:  One-way connection provides enhanced security  Hub CANNOT ping agents – agents check in for more work PeopleTools 8.45 Environment Environment Management Hub Change Assistant AppSrv WebSrv Agent Batch File = Agent

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. EMF Architecture – For File Deploy  Change Assistant Agent Sends Request to Hub  Highlights in this Request which Agents to Queue Work  Batch Server, Web Server, etc. PeopleTools 8.45 Environment Environment Management Hub Change Assistant AppSrv WebSrv Agent Batch File = Agent Request Sent

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. EMF Architecture – For File Deploy  Hub Holds Requests until the Agent Pings and Accepts Work  N.B. Change Assistant will WAIT for this to happen PeopleTools 8.45 Environment Environment Management Hub Change Assistant AppSrv WebSrv Agent Batch File = Agent Request

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. EMF Architecture – For File Deploy  Agents then deploy the files to the appropriate directory on their server  Take parameters from File Type Code for this  eg %ps_home%\sqr  Agents send success message back to CA PeopleTools 8.45 Environment Environment Management Hub Change Assistant AppSrv WebSrv Agent Batch File = Agent Request Success?

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the EMF  Prompts during CD Install  PeopleTools 8.44 or Higher  EM Hub Machine Name and Port  configuration.properties  Starts Automatically

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the EMF Installing the EM Hub  Install PeopleSoft Internet Architecture  Web Application PSEMHUB Administer the EM Hub  Start/Stop the Web Server EMF Hub

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the EMF Installing the EM Agent  Location of the EM Agent: %PS_HOME%/PSEMAgent  Setup on each Physical Server  Validate the configuration.properties  %PS_HOME%/PSEMAgent/envmetadata/config

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the EMF The Global Unique Identifier (GUID)  Must be Unique for Each Database  Stored in the PSOPTIONS Table  Used by EMF  Distinguishes Environment  The Environment Name  Unique Name  Update the Long Name, Short Name, and System Type  Log into PIA and Navigate to: PeopleTools  Utilities  Administration  PeopleTools Options

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the EMF Administer the EM Agent  Starting  Windows - %PS_HOME%\PSEMAgent\StartAgent.bat  UNIX - $PS_HOME/PSEMAgent/StartAgent.sh  Stopping  Windows - %PS_HOME%\PSEMAgent\StopAgent.bat  UNIX - $PS_HOME/PSEMAgent/StopAgent.sh  Note  Windows can define a Service (PT 8.45 and greater)  UNIX – run in background

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the EMF Validating the EMF  Validate Using URL:

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the EMF Viewing the Information Collected by the Hub  Using the EM Viewer:  Installed onto the Web Server under:  %PS_HOME%\PSEMViewer  Can only run on the Web Server  Windows - %PS_HOME%\PSEMViewer\GetEnvInfo.bat  UNIX - $PS_HOME/PSEMViewer/GetEnvInfo.sh  View the viewer.html:  Windows - %PS_HOME%\PSEMViewer\envmetadata\data  UNIX - $PS_HOME/PSEMViewer/envmetadata/data

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the EMF

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Installing the Change Assistant  Install on a Windows Workstation  Use PS_HOME/setup/PsCA/setup.exe  Install RDBMS Client Utility  Update Windows Path  To include: %PS_HOME%\bin\client\winx86  Create Directory Structures for:  Download  Output  Stage

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Configuring the Change Assistant  PeopleTools 8.44  Start  Programs  PeopleSoft 8  Change Assistant  PeopleTools 8.45  Start  Programs  PeopleSoft 8.4  Change Assistant

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Configuring the Change Assistant  From the menu: Select Options  Change Assistant  Define SMTP Server

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Configuring the Change Assistant  Select the Change Packages Tab  Identify the Download Directory

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Configuring the Change Assistant  Select the Directories tab  Identify the %PS_HOME%  Identify the Staging and Output Directory

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Configuring the Change Assistant  Menu: Select Options  Environment Management Hub  Define the URL for the EMHub  Validate Using Ping Button

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Configuring the Change Assistant  Select the Settings Tab  Update the Drives to Crawl  SQL Client Utilities

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Common Issues  EM Agent not Running  Run EM Agent in Background  EM Agent not Connecting to EM Hub  Start PIA  Make Certain Hub URL is Correct  CA Workstation – Path not Updated  Validate Path  CA Workstation – SQL Client Utility not Found  Review search-results.xml

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Functionality 1. Upload

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Functionality 2. Search

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Functionality 3. Download

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Functionality 4. Apply

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Functionality Working with Customizations  Run Compares against Database with Customizations  Apply Change Packages to new Environment  Reapply Customizations  Repackage Fixes with Change Packager  Migrate Change Package Containing Maintenance & Customizations 5. Migrate*

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Change Packages  Using Change Packages for Managing Updates  Change Packager Content  Traditional Objects  Records, Fields, Pages, Components, PeopleCode etc  XML Project File  File Types and File References  All files attached to same ZIP file as Database Objects  New Flags for Files  Deploy  Execute  Other Key Points:  Follows the standard PeopleSoft Directory Structure  Change Assistant Template enforces consistent updates look & feel  Change Packager-generated HTML Documentation ensures consistency for install instructions within updates

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Change Packages  If you do not have a version control utility….  Use the Change Packager to Manage your Updates  Save ZIP files for audit purposes  Have Developers Package Changes  Then have a Separate User Migrate Changes

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Tips from the Field General Troubleshooting Tips  Need Customer Connection User Account/Password to download package  Database connectivity software needs to installed on the CA client  Be aware of Additional Directories Needed  Some PIA Components that have not Traditionally Carried a Full PS_HOME  App and Web Servers need PSEMAgent  When Cloning a Database the GUID must be set to blank  Application Server Assigns a Random GUID when Booting Up for the First Time  Used by the EMF framework to Identify a Unique Environment  File Deployment Mechanism Overwrites Existing Objects  Run SYSAudit and DDDAudit Before and After Change Package

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Tips from the Field  Implement on PeopleTools or Higher  Use the PeopleTools 8.45 Documentation  Determine Your Starting Point General Availability Roadmap of Applications That Can Use Change Assistant

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Agenda  What is Change Assistant  Overview  Installation  Environment Management Framework (EMF)  Change Assistant (CA)  Common Setup Issues  Functionality  Fix Application Process  Tips from the Field  Questions

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Appendix: Migrating Change Packages or Maintenance Updates This appendix describes the procedure used to migrate change packages or maintenance updates to your environment. Note. This process is required for every change package delivered by PeopleSoft. For example, Financials 8.8 Maintenance Pack 1 is delivered in 5 change packages—therefore, financial customers would need to create 5 modified change packages for each of the delivered change packages. PeopleSoft does not support the addition or removal of files in any delivered change package. Migrating Change Packages or Maintenance Updates 1.Using PeopleSoft Change Assistant, apply a change package or maintenance update to the demo database. 2.Run the project compare operation of installed updates to the development or copy of production. 3.Review each customized object and decide whether or not you want to allow the object to be copied into your development database. 4.Copy project from the demo database to the development or copy of production database. 5.Select the objects in the project that require re-customization, and reapply customizations. 6.Select the Upgrade checkbox for each object that required re-customization. 7.Copy project to file. 8.You can specify any location; for example, c:\peoplesoft\modified\project. 9.Extract the files from the delivered change package. 10.Update the project files (.xml and.ini) in the extracted project directory with the exported custom project. For example, copy PRJ XML and PRJ INI from c:\peoplesoft\modified\projects\PRJ to c:\peoplesoft\extracted\upd151828\PRJ Examine the files changes in the maintenance pack with customized files. Typically, these files exist in the updXXXXXX_batch directory. 12.Update file changes where necessary. 13.Open the modified project in PeopleSoft Application Designer and repackage the change package by selecting Tools, Finalize Change Package. 14.When you are prompted for the directory, enter the high-level extracted directory. For example, c:\peoplesoft\extracted\upd Apply the modified maintenance updates to the test or production database or both. 16.When you are prompted to enter the apply directory, enter the directory that contains the modified change package. For example, c:\peoplesoft\extracted\upd The modified change package already includes customizations from the development database and modified files from the development environment. Therefore, now PeopleSoft Change Assistant can be used to migrate both the delivered and the customized objects in the customer's environment without additional manual interventions.