PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Agenda What.

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

AgendaAgenda

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


OverviewOverview

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 dependenciesPre-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


OverviewOverview

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 dependenciesPre-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


OverviewOverview

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


Environment Management FrameworkEnvironment 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)


EMF ArchitectureEMF 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


EMF Architecture – For File DeployEMF 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.


Environment

Management Hub

Change Assistant

AppSrv WebSrv

Agent

Batch File

= Agent

Request Sent



Hub Holds Requests until the Agent Pings and Accepts Work

N.B. Change Assistant will WAIT for this to happen


Environment

Management Hub

Change Assistant

AppSrv WebSrv

Agent

Batch File

= Agent

Request



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


Environment

Management Hub

Change Assistant

AppSrv WebSrv

Agent

Batch File

= Agent

Request

Success?


Installing the EMFInstalling the EMF

Prompts during CD Install PeopleTools 8.44 or Higher EM Hub Machine Name and Port

configuration.properties Starts Automatically



Installing the EM Hub Install PeopleSoft Internet Architecture

Web Application PSEMHUB

Administer the EM Hub Start/Stop the Web Server

EMF Hub



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



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



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



Validating the EMF Validate Using URL:

http://webserver_name:port/PSEMHUB/hub



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




Installing the Change AssistantInstalling 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


Configuring the Change AssistantConfiguring the Change Assistant

PeopleTools 8.44 Start Programs PeopleSoft 8 Change Assistant

PeopleTools 8.45 Start Programs PeopleSoft 8.4 Change Assistant



From the menu: Select Options Change Assistant Define SMTP Server



Select the Change Packages Tab Identify the Download Directory



Select the Directories tab Identify the %PS_HOME% Identify the Staging and Output Directory



Menu: Select OptionsEnvironment Management Hub

Define the URL for the EMHub Validate Using Ping Button



Select the Settings Tab Update the Drives to Crawl

SQL Client Utilities


Common IssuesCommon 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


FunctionalityFunctionality

1. Upload



2. Search



3. Download



4. Apply



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*


Change PackagesChange 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


Change PackagesChange 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


Tips from the FieldTips 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


Tips from the FieldTips from the Field

Implement on PeopleTools 8.44.06 or Higher Use the PeopleTools 8.45 Documentation Determine Your Starting Point

General Availability Roadmap of Applications That Can Use Change Assistant

PeopleSoft Enterprise Product Line (Must be on PeopleTools 8.44 or

higher)Baseline PeopleSoft Enterprise Release

and Maintenance LevelGeneral Availability

Date*

Financial Management Solutions FMS 8.8 17-Dec-03Supply Chain Management SCM 8.8 17-Dec-03FMS FMS 8.4 Service Pack (SP) 2 31-Mar-04SCM SCM 8.4 SP 2 31-Mar-04

Human Resources Management HRMS 8.8 SP 1 Maintenance Pack (MP) 1 17-May-04Customer Relationship Management CRM 8.8 SP1 MP 2 17-Jun-04CRM CRM 8.9 23-Jun-04Enterprise Portal Enterprise Portal 8.8 MP1 Q3 2004Enterprise Learning Management ELM 8.8 SP 1 Q3 2004Enterprise Performance Management EPM 8.8 SP 2 Q4 2004Learning Solutions HRMS and Campus Solutions 8.9 Q4 2004


AgendaAgenda

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


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 PRJ151828.XML and

PRJ151828.INI from c:\peoplesoft\modified\projects\PRJ151828 to c:\peoplesoft\extracted\upd151828\PRJ151828. 11. 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\upd151828.15. 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\upd151828. 17. 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.

PeopleSoft Proprietary and Confidential, Copyright 2004 PeopleSoft, Inc. For Internal Use Only, Do not distribute outside of PeopleSoft. Agenda What.

Documents

peoplesoft proprietary

change assistant slide

change assistant agent

agent slide

internal use

agents agents

dev re

application process