peoplesoft update manager

8/20/2019 PeopleSoft Update Manager

1/93

PeopleSoft Update Manager

PeopleSoft Update Manager (PUM) is a lifecycle management process that is used with the PeopleSoftUpdate Manager PIA application, which runs on the PeopleSoft Image database.

PeopleSoft Images are racle !irtual"o# $irtual machines that you download locally. %here is onePeopleSoft Image per product family (database instance) and they will be released periodically

according to the image schedule posted on the PeopleSoft Update Manager &ome Page. %hePeopleSoft Image is the master source en$ironment from which you will pull the updated ob'ects, createa custom change pacage, and apply updates to your en$ironment. %he PeopleSoft Image for yourapplication is cumulati$e so you will download the most current PeopleSoft Image and get all of theupdates that you need.

%he PeopleSoft Update Manager PIA Application and the PeopleSoft Image wor together thePeopleSoft Image contains the updates and the PeopleSoft Update Manager PIA Application is thesearching tool and custom change pacage definition generator. PeopleSoft *hange Assistantorchestrates the entire process flow. *hange Assistant is the tool used to analy+e and comparechanges, to apply the changed ob'ects to your en$ironment, to add in your customi+ations, and togenerate custom change pacages.

Software Update Process

%he software update process refers to applying updates to your PeopleSoft application. %he procedure

for applying updates depends on whether the PeopleSoft application is PUM enabled.

PUM Enabled PeopleSoft Systems

All PeopleSoft updates for a product family are made a$ailable on a PeopleSoft Image. %he PeopleSoft

Image is a !irtua"o# image that contains the $ery latest PeopleSoft woring database, applications,

managed ob'ects, codeline, and the data and metadata reuired to use the PeopleSoft Update Manager.

%he PeopleSoft Image is posted and downloaded from My racle Support (MS). %he schedule for

images will be posted in ad$ance on MS for each PeopleSoft application database instance.

Software update tools include-

• n$ironment Management /ramewor

Used to collect en$ironment information.

See 0unning the n$ironment Management &ub

• *hange Assistant

Used to upload target database information to the PI, create change pacages from the custom

change pacage definitions created using PeopleSoft Update Manager, and to the apply change

pacages to target databases.

See Applying Updates %o A %arget n$ironment

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunningtheEnvironmentManagementHub-0711a9.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunningtheEnvironmentManagementHub-0711a9.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_ApplyingUpdatesToATargetEnvironment-0711d6.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_ApplyingUpdatesToATargetEnvironment-0711d6.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_ApplyingUpdatesToATargetEnvironment-0711d6.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunningtheEnvironmentManagementHub-0711a9.html


2/93

• PeopleSoft Update Manager PIA Application

Used to search for updates and create custom change pacage definitions.

%he PeopleSoft Update Manager PIA Application is posted on PeopleSoft Update Manager &ome

Page 1I2 3454536.37

• *hange Pacager

*reates the change pacage in *hange Assistant based on the change pacage definition created

in PUM.

Image: Software Update Process in Change Assistant

%his diagram illustrates the Software Update process steps for the initial pass.

https://support.oracle.com/epmos/faces/DocContentDisplay?id=1464619.1https://support.oracle.com/epmos/faces/DocContentDisplay?id=1464619.1https://support.oracle.com/epmos/faces/DocContentDisplay?id=1464619.1https://support.oracle.com/epmos/faces/DocContentDisplay?id=1464619.1


3/93

Steps Used in Software Update Process

%his table lists the steps used to search for and apply updates to your de$elopment or target database.


4/93

Step

3

8

9

4

:

5

;

<

6

Non-PUM Enabled PeopleSoft Systems

%his software update process is only used for PeopleSoft systems that are not PeopleSoft Update

Manager enabled. /or PUM enabled systems refer to the pre$ious section.

%his software update process refers to applying change pacages, bundles, and maintenance pacs to

your non=PUM enabled PeopleSoft application. /or e#ample, PeopleSoft application de$elopment teams

periodically post change pacages containing fi#es to $arious application elements, such as pages and

People*ode programs, that you can download and apply to your PeopleSoft system. >ou use *hange

Assistant to apply software updates.


5/93

Step escription

3 Install and configure *hange Assistant and the n$ironment Management components.

8 Use My racle Support (MS) to search for updates.

9 2ownload the *hange Pacages from MS.

4 After you ha$e downloaded the change pacages, you can then apply them in a batch or indi$idually. If

prereuisites or post=reuisites are reuired, they will be included in the list as well.

Software Upgrade Process

%he software upgrade process refers to mo$ing from one release le$el to a newer release. %his typically

in$ol$es installing a new $ersion of People%ools and a new $ersion of an e#isting PeopleSoft application.

%his process uses *hange Assistant, and the n$ironment Management /ramewor when running

remote upgrade processes. If you are upgrading from one release of a PeopleSoft application to another

application release, also consult your specific application?s install and upgrade documentation.

Source and %arget 2atabases

In $arious places within this People"oo, as well as any PeopleSoft documentation related to upgrades

or database compares, the terms source and target are used. @nowing the meanings of these terms

helps you to understand the conte#t of a description or step.

2uring a PeopleSoft update or upgrade, in most cases, you copy application definitions (such as pages

and records) from a source database to a target database. %he definitions of these terms are-


6/93

so!rce database %he source database is the database from which the new changes

are coming.

target database %he target database is the database to which you are mo$ing thenew changes.

Note: 2epending on whether you are performing an upgrade or update, and the stage within the

process you are, these terms are relati$e and can refer to different databases.

/or e#ample, in a typical upgrade, you install the new $ersion to a demonstration database, referred to

as 2emo. %hen, you create a copy of your production database, referred to as *opy of Production. >ou

then copy the modified definitions from the 2emo database into the *opy of Production. In this conte#t,

your 2emo database is your source and the *opy of Production is the target . iewise, after you

complete the initial copy and perform the reuired compares and tests, you begin a Mo$e to Productionpass. In this pass you tae the *opy of Production database and incorporate the modified definitions

into the Production database. In this conte#t, the *opy of Production is your source and the Production

database is your target .

Bhen applying an update using the CApply with 2atabase *ompareD*opyC option, the source database

is the 2emo database where the update (change pacage) has already been applied.

Change Assistant En"ironments and #erminology

2epending on the action to perform, the en$ironment must be configured. ach en$ironment will include-

• 2atabase name

• 2atabase type

• Unicode

• User Ids and passwords

• SE uery e#ecutable

• Products

Products are selected for the target database only. %he source database will inherit these $alues

from the target.

• anguages


7/93

anguages are selected for the target database only. %he source database will inherit these $alues

from the target.

• Paths to the current en$ironment home directories.

PSF&M

PSFAPPF&M

PSF*US%F&M

• /or application upgrades , the target database will also include paths to the old en$ironment

home directories.

Paths to $ome irectories

%he order by which the People%ools runtime will pic up ob'ects from the file system is as follows-

3. PSF*US%F&M

8. PSFAPPF&M

9. PSF&M

*hange Assistant will loop through the paths in order of precedence until it finds the first instance of the

file ob'ect at which time it will e#ecute the step.

atabases Used for Each Action

Action atabases and Paths Used

Apply Update %arget database with path for current en$ironment.

Update Manager %arget database with path for current en$ironment.

Source database (PeopleSoft Image !irtual"o#) with path for

current en$ironment.

Application Upgrade %arget database with path for current en$ironment and path

for old release.

Source database (PeopleSoft Image !irtual"o#) with path for


8/93

Action atabases and Paths Used


(ptional) *opy of current demo database with path for


(ptional) Production database with path for current

en$ironment.

Upgrade People%ools %arget database with path for current en$ironment.

*opyD*ompare Managed b'ects or Merge

Selected b'ect %ypes

Multiple databases can be copied, compared and merged.

*onfiguring the n$ironment Management &ub

"efore you can run the n$ironment Management hub, you must ensure that it?s properly configured.

%he hub issues automatic recrawl and re$alidate commands to the agents, and it can be configured to

accept automatic updates from *hange Assistant. >ou configure the hub by setting appropriate

parameters in its configuration file, which is located as follows-

• Bebogic-

PIA_HOME Gwebser$GdomainGapplicationsGpeoplesoftGPSM&U"Gen$metadataGconfigGconfiguration.

properties

• BebSphere-

PIA_HOME Gwebser$Gserver GinstalledAppsGdomainHode*ellDdomain.earGPSM&U".warDen$metada

taDconfigGconfiguration.properties

%he following table describes the primary configuration.properties parameters for the hub-

Config!ration

Parameter

escription efa!lt %al!e

recrawlinter$al %he inter$al, in hours, between two successi$e recrawl commands 24 hours


9/93

Config!ration

Parameter


that ha$e been issued to a peer. %he ser$er issues recrawlcommands only to agents that are connected to the hub and ha$e no

pending messages in the ueue. %his configuration parameter is

ignored by the agent.Note: A 0 $alue

means that it will not

recrawl.

0ecrawling includes a

re$alidating.

re$alidateinter$al %he ma#imum time, in hours, between two successi$e automatic

re$alidates that the hub issues.6 hours

Note: A 0 $alue

means that it will not

re$alidate.

$!b Sec!rity Considerations

n$ironment Management framewor does not support &%%PS connections. %he agent and hub

communicate using standard &%%P only.

n BebSphere, or for a single ser$er configuration on Bebogic, PSM&U" is a web application

running within PIA. If PIA is configured to be accessed using &%%PS, you need to configure a separate

ser$er instance for the hub to enable the &%%P connections between agents and hub.

Config!ring $!b &ogging

%he n$ironment Management hub logs are located as follows-

• Bebogic- PIA_HOME Gwebser$GdomainGapplicationsGpeoplesoftGPSM&U"Gen$metadataGlogs

• BebSphere- PIA_HOME Gwebser$Gps3GinstalledAppsGdomainJHode*ellDdomainJ.earGPSM&U

".warDen$metadataDlogs

dit the .....GPSM&U"Gen$metadataGconfigGogconfig.properties to configure logging for the hub. %he

following two ogconfig.properties parameters, which determine the ma#imum si+e of each log file, and

the amount of log files rolled o$er, can be changed-

• log4'.appender.0.Ma#/ileSi+eK3L84@"

• log4'.appender.0.Ma#"acupInde#K3C


10/93

Page Ha$igation &eader

0unning the n$ironment Management &ub

%his section discusses how to-

• 0un the hub on a single ser$er.

• 0un the hub on multiple ser$ers.

"efore you run the n$ironment Management agent, you must first ensure that it?s properly configured in

the hub?s configuration.properties file.

'!nning the $!b on a Single Ser"er

n a single ser$er, the PSM&U" starts within PIA, so use the command you use for your web ser$er to

start PIA.

'!nning the $!b on M!ltiple Ser"ers

n$ironment Management also supports multi=ser$er installs. &owe$er, the n$ironment Management

hub does not support clustering. %he n$ironment Management hub persists metadata into the file

system on the 8 container. %his is not replicated in a clustered en$ironment. >ou e#perience

erroneous beha$ior when you attempt to run the n$ironment Management hub in a clustered

en$ironment.

%he n$ironment Management hub deals with large binary files that *hange Assistant sends to the

agents by using the hub as the intermediary dispatcher. %his can create significant o$erhead to a

production system that is running on a multi=ser$er clustered en$ironment. %herefore, PSM&U" must

always run on separate ser$ers dedicated to the n$ironment Management hub reuests.

Starting PSEM$U( on M!ltiple Ser"ers on )eb&ogic

In a multiple ser$er configuration, the PSM&U" ser$er listens on port 0!, by default.

Use the following steps to start the Bebogic hub-

3. *onfigure the n$ironment Management hub to run on a ser$er that is different from the

PeopleSoft Internet Architecture ser$ers.

8. *onfigure the re$erse pro#y to redirect any networ traffic with a uniform resource identifier (U0I)

of PSM&U" to the ser$er running the n$ironment Management hub.

n the machine from which the 0PS application runs, access the &ttpPro#ySer$let folder.


11/93

Select PSM&U"&ttpPro#ySer$let and clic the Init Params tab. 0eplace Bebogic&ost ,

BebogicPort with the host and port from which your PSM&U" ser$er listens.

Note: Sa$e your new configuration.

Use the following commands in seuence to start the n$ironment Management hub in a multi=ser$er

installation-

...\StartWebLogicAdmin.cmd (start the admin server)

...\StartManagedWebLogic.cmd RPS

...\StartManagedWebLogic.cmd PSEMHUB

%hen use the following U0 to access PSM&U"- http-DD"P# host -"P# port DPSM&U"Dhub.

Note: /or a single ser$er install using a re$erse pro#y, this additional step needs to be performed in

order for the n$ironment Management hub to be able to process the PSM&U" reuests. >ou need to

edit-PIA_HOME Gwebser$GdomainGapplicationsG&ttpPro#ySer$letGB"=IH/Gweb.#ml. In thePSM&U"&ttpPro#ySer$let section, change the default port from


12/93

8. 0emo$e this line from all other ser$ers- Uri Affinity*ooieKCSSSIHI2C

AffinityU0IdentifierKC'sessionidC HameKCDPSM&U"DNC DJ. %he ser$er you chose for PSM&U"

should only ser$ice PSM&U" reuests so that it can run independently and can be shut down

without affecting the rest of the system.

9. 0estart the re$erse pro#y using - I$M_pro%&_'ase_director& GbinGapachectl restart.

4. 0estart all the ser$ers. /or Bindows, the directory

is- (e'#phere_Appserver_director& GbinGstartSer$er.bat ser$erO. /or UHIO, the directory

is- (e'#phere_Appserver_director& DbinDstartSer$er.sh ser$erO.

:. Use the following U0 to access PSM&U"

http-DDreverse_pro%&_host -reverse_pro%&_port DPSM&U"Dhub.

%he re$erse pro#y?s listen port is defined in I$M_reverse_pro%&_'ase_director& GconfGhttpd.conf.

Stopping the PSEM$U( on M!ltiple Ser"ers on )eb&ogic

In a multiple ser$er en$ironment, target the ser$er which is dedicated to PSM&U" then

e#ecutePIA_HOME Gwebser$GdomainGstopBebogic.cmd PSM&U" on Bindows

andP#_HOME Dwebser$DdomainDstopBebogic.sh PSM&U" on UHIO. %his will only stop the ser$er

ser$icing PSM&U" reuests. %he other ser$ers will still be up processing PIA reuests.

%he following is a sample OM configuration file for the Bebogic multi=ser$er installation-

,., Sam$"e -ML conigration i"e or WebLogic M"tiserver insta""ation

!Uri/ro$ 0ame12dea"t3host3server,3st"n%+435"ster3UR6s2#

!Uri Ainit&5oo7ie128SESS6906:2 Ainit&URL6dentiier12;sessionid20ame12'


13/93

0ame12'PS60=ERL60>S'


14/93

Config!ration

Parameter


successi$e attempts that the peer maes tocontact the hub. All peers that access this

configuration file ha$e the same ping inter$al.Note: %he minimum reuired pinginter$al

$alue is 3LLL.

windowsdri$estocrawl n Microsoft Bindows, the set of local dri$es

or directory paths where PSF&M,

PSF*/F&M and PIAF&M are located.

Separate the dri$e letters or directory paths

with spaces and a pipe symbol ( Q ).

c- Q d-

Note: 2o not lea$e a trailing ?D? or ?G?

character at the end of the path.

uni#dri$estocrawl n UHIO, the set of local dri$es or directory

paths where PSF&M, PSF*/F&M,

and PIAF&M are located.

R&M

Note: 2o not lea$e a trailing ?D? or ?G?

character at the end of the path.

chunsi+e nly applicable to large files, which may be

chuned when sent. %he chunsi+e represents

the ma#imum si+e in bytes of each chun.

3L4


15/93

*onfiguring Agents Bith a Secure PSF&M

*hange Assistant deploys the updates to the PSF&M using the agents running on the managed

ser$ers. %herefore, the agent running on a ser$er should ha$e write access to the PSF&M and its

subdirectories.

Note: Bhile specifying the crawl path in configuration.properties, mae sure that the decoupled

configuration home (PSF*/F&M) is also included.

0unning an n$ironment Management Agent


• 0un an agent.

• Start an agent automatically in Bindows.

'!nning an Agent

"efore you run an n$ironment Management agent, you must ensure that it?s properly configured in the

agent?s configuration.properties file.

Starting the Agent

At a command prompt, na$igate to P#_HOME GPSMAgent.

Use one of these scripts to start the n$ironment Management agent-

• n Microsoft Bindows, run P#_HOME GPSMAgentGStartAgent.bat.

Note: If you want the agent to start automatically when the machine starts, use the Microsoft

Bindows ser$ice that?s deli$ered as part of People%ools. r, you can add the script to the startup

applications.

• n UHIO, run P#_HOME DPSMAgentDStartAgent.sh.

Note: If you want the n$ironment Management agent to start automatically on UHIO when themachine starts, add StartAgent.sh to the loginDboot scripts.

%he first time an agent starts, it crawls the machine to locate PeopleSoft elements on that machine. %he

results of searching the hard dis are sa$ed in the en$metadataGdataGsearch=results.#ml file.

Note: Bhen starting an agent manually from the command prompt or from a script, the command

prompt will continue to stay open, and it is normal to see the output of the periodic heartbeat e$ents


16/93

(Csending pulseC) in the command prompt as the agent communicates with the hub. "y default these

CpulsesC are e$ery 3L seconds, e#cept when en$ironment information is being uploaded to the hub. >ou

can configure the agent to run in the bacground using the pro$ided Bindows ser$ice, and on UHIO by

using the noh$ command. %hese options are documented in other sections of this People"oo.

Note: nly one n$ironment Management agent can be started per machine. If an agent is already

started, you may recei$e error messages indicating that the agent cannot be started because there is

already one running on the machine.

See Starting an Agent in the "acground on UHIO.

See Starting an Agent Bith PSMAgent Bindows Ser$ice.

Starting the Agent on a Sec!re PS*$+ME

n Microsoft Bindows-

3. *reate a new shortcut from the destop (right=clic, Hew, Shortcut).

8. In the %ype the location of the item enter-

)P#_HOME*+P#EMAgent+#tartAgent,'at -u .)domainname*+)username*

/or e#ample-

c.+ptinsta//s+pt!+P#EMAgent+#tartAgent,'at -u .'igcompan&,com+tsaw&er

Bhere the user specified has write access to PSF&M.

Note: Bhen you run PSF&MJGPSMAgentGStartAgent.bat =u -domainnameJGusernameJ,

the %MP directory is used. "oth the user that runs the command and the CrunasC user need

writeDe#ecute access to the %MP directory.

9. *lic He#t, and enter a name for the shortcut.

4. Use this shortcut to start the agent.

n UHIO-

3. og in as the user who has write access to the PSF&M.

8. PSF&MDPSMAgentDStartAgent.sh.

See Securing PSF&M on UHIO.

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunninganEnvironmentManagementAgent-07119c.html#StartinganAgentintheBackgroundonUNIX-2e731fhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunninganEnvironmentManagementAgent-07119c.html#StartinganAgentintheBackgroundonUNIX-2e731fhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunninganEnvironmentManagementAgent-07119c.html#StartinganAgentWithPSEMAgentWindowsService-0711a2https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunninganEnvironmentManagementAgent-07119c.html#StartinganAgentWithPSEMAgentWindowsService-0711a2https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunninganEnvironmentManagementAgent-07119c.html#StartinganAgentWithPSEMAgentWindowsService-0711a2https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tsvt/task_SecuringPS_HOMEonUNIX-eb6cbe.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tsvt/task_SecuringPS_HOMEonUNIX-eb6cbe.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunninganEnvironmentManagementAgent-07119c.html#StartinganAgentintheBackgroundonUNIX-2e731fhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_RunninganEnvironmentManagementAgent-07119c.html#StartinganAgentWithPSEMAgentWindowsService-0711a2https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tsvt/task_SecuringPS_HOMEonUNIX-eb6cbe.html


17/93

Stopping the Agent

Use one of these scripts to stop the n$ironment Management agent-

• n Microsoft Bindows, run P#_HOME GPSMAgentGStopAgent.bat.

• n UHIO, run P#_HOME DPSMAgentDStopAgent.sh.

'ecrawl

If you install new software components, the running n$ironment Management agent doesn?t

automatically detect them. %his is because, to impro$e performance, the agent doesn?t crawl e$ery time

it starts up. Instead it crawls only if the search=results.#ml file does not e#ist.

>ou can force a recrawl and mae the new components manageable by reissuing the StartAgent

command with the recrawl option-

3. pen a new command line window.

8. *hange directories to P#_HOME GPSMAgent.

9. Issue the following command-

StartAgent recra"

%his forces a recrawl and creates a new search=results.#ml file. If an agent is already running, it

publishes the results to the hub.

If the running n$ironment Management agent is connected to the hub constantly, the recrawl inter$aloccurs e$ery 84 hours by default. If the agent has not been connected to the hub for a few days, the hub

reuests the agent to recrawl when the agent contacts the hub the ne#t time.

Note: 0ecrawling includes re$alidating.

Note: %he recrawl process assumes the n$ironment Management agent is running. If it is not running,

you may see error messages in the output. It is recommended that before running a recrawl, you mae

sure the agent is running.

'e"alidate

If the n$ironment Management agent does not recogni+e any of the installed components, the search=

results.#ml file may not e#ist or may contain only an entry for &ost. %he problem may be that the agent

needs to ha$e permission to read directories as well as e#ecute programs. rant these permission for

the agent. Also chec whether the agent has permission to create a file on the local file system. /inally,

chec whether the dis is full. %he agent might ha$e no dis space to create a search=results.#ml file.

If the hub is not running, you may recei$e the following error messages in the agent log or console-


18/93

• "roen connection = attempting to reconnect

• 0emote#ception while connecting to ser$er = retrying attempt 3



nce the n$ironment Management hub is bac up, the agent will successfully connect. %here?s no

need to stop and restart the agent.

Note: If you are performing a recrawl, you don?t need to separately re$alidate.

Command-&ine Arg!ments for the Agent

>ou can run these command=line arguments with the startAgent.bat (or startAgent.sh) script.

Arg!ment escription Sample +!tp!t

$ersion 0eturns the $ersion of the agent. !ersion-


19/93

Arg!ment escription Sample +!tp!t

is baced up.

Note: 0ecrawling includes re$alidating.

isrunning 0eturns true if an agent is already running and false if an

agent is not already running.

HA

remo$e 0emo$es the peer and all its registered components from

the hub.

0emo$al *ompleted= PeerI2 8 has been

remo$ed.

0emo$al /ailed= PeerI2 8 could not be

remo$ed from the hub.

Starting an Agent in the (ac,gro!nd on UNI

Use the UHIO noh$ command with the StartAgent.sh script to start an agent automatically and run in

the bacground. %his enables you to a$oid ha$ing a command prompt open at all times showing the

constant heartbeat of the agent. >ou can specify an output file to store heartbeat information.

/or e#ample,

noh$ .'StartAgent.sh # agent3ot$t."og

Starting an Agent )ith PSEMAgent )indows Ser"ice

>ou can set an n$ironment Management agent to start automatically when your n$ironment

Management machine boots and run in the bacground. %his enables you to a$oid ha$ing a command

prompt open at all times showing the constant heartbeat of the agent.

/or this option, use the P#EMAgent Bindows ser$ice that?s deli$ered as part of People%ools.

Installing the PSEMAgent Ser"ice

>ou install the PSMAgent ser$ice from a command prompt. *opies of the install program are located in

two places-

P#_HOME GbinGclientGwin#


20/93

3. At a command prompt, change to either location of the install program.

8. nter the following command-

PSMAgentSer$ice Dinstall P#_HOME GPSMAgent

Bhere P#_HOME is the People%ools installed location.

%he PSMAgent ser$ice is now installed, but not started. It?s configured by default to start

automatically when the system boots, and to log on using the local system account. >ou can start it

manually, or wait for the ne#t reboot.

Note: %he PSMAgent ser$ice is configured to start as an automatic ser$ice, by default. &owe$er,

the &ub must be running prior to the PSMAgent ser$ice attempting to start, or the PSMAgent

ser$ice will not start successfully. It is recommended to set the PSMAgent ser$ice to manual start

in the Bindows Ser$ices interface. %hen, to start the PSMAgent ser$ice, start it manually from the

Ser$ices interface.

Starting the PSEMAgent Ser"ice

>ou can start the PSMAgent ser$ice from a command prompt, or from the Bindows Ser$ices control

panel. %he name of the ser$ice follows this con$ention- Peop/e#oft Environment Management Agent-

)re/ease*.

• %o start the PSMAgent ser$ice from a command prompt, use the H% S%A0% command. /or

e#ample-

0E= S=AR= 2Peo$"eSot Environment Management Agent*.@+2

• %o start the PSMAgent ser$ice from the Bindows Ser$ices control panel-

3. pen the Bindows *ontrol Panel, then double=clic Administrati$e %ools, then Ser$ices.

8. In the Ser$ices control panel, right=clic the Peop/e#oft Environment Management

Agent entry and selectStart.

Stopping the PSEMAgent Ser"ice

>ou can stop the PSMAgent ser$ice from a command prompt, or from the Bindows Ser$ices control

panel.

• %o stop the PSMAgent ser$ice from a command prompt, use the H% S%P command. /or

e#ample-

0E= S=9P 2Peo$"eSot Environment Management Agent*.@+2

• %o stop the PSMAgent ser$ice from the Bindows Ser$ices control panel-


21/93

3. pen the Bindows control panel, then double=clic Administrati$e %ools, then Ser$ices.

8. In the Ser$ices control panel, right=clic the PeopleSoft n$ironment Management Agent

entry and selectStop.

Uninstalling the PSEMAgent Ser"ice

>ou uninstall the PSMAgent ser$ice from a command prompt.

%o uninstall the PSMAgent ser$ice-

3. At a command prompt, change to either location of the uninstall program.

*opies of the uninstall program are located in two places-

P#_HOME GbinGclientGwin#


22/93

3. 0un a a$a program to connect to the hub and retrie$e the information in OM format.

0un the appropriate script for your en$ironment in from P#_HOME GPSM!iewer. >ou will be

prompted for the web ser$er?s listening port.

• UHIO- .Detn$Info.sh

• Bindows- etn$Info.bat

Note: /or security reasons, the a$a program connects only to the local host.

8. pen P#_HOME GPSM!iewerGen$metadataGdataG$iewer.html to $iew the information in the

generated OM file

*onfiguring and Starting an n$ironment Management Agent on +DS

%o run an agent on +DS, you must ha$e installed 0 deli$ered with People%ools on the +DS machine.

%o configure and start the agent on +DS-

3. dit the configuration.properties file (P#_HOME DPSMAgentDen$metadataDconfig).

8. dit hubU0 and define the hub machine name and hub port.

9. dit uni#dri$estocrawl and set it to the set of directories that need to be crawled.

4. dit StartAgent.sh.

n the first line, replace PSF&M with your P#_HOME location.

dit the last line to point to your 0 location.

:. dit StopAgent.sh.

n the first line, replace PSF&M with your P#_HOME location.

dit the last line to point to your 0 location.

%he default charset on +DS is "*2I*. If you wish to $iew the content

of P#_HOME DPSMAgentDen$metadataDdataDsearch=results.#ml, you need to run the following

commands-

cd PS_HOME 'PSEMAgent'envmetatda'data


23/93

. PS_HOME '$sconig.sh

PS_HOME 'bin'$sniconv t* searchres"ts.%m" ccsid,+C res"t.t%t

%his comment is also true for P#_HOME DPSMAgentDen$metadataDdataDmatchers.#ml.

>ou can find a $iewable $ersion of the results in result.t#t. >ou can also /%P (binary) these files to adifferent machine running a different operating system and $iew them in any editor.

Integrating with racle *onfiguration Manager

%his section contains an o$er$iew and discusses how to instrument People%ools for racle

*onfiguration Manager data collection.

Understanding +racle Config!ration Manager for PeopleSoft

racle *onfiguration Manager (*M) is used to collect configuration data from customer en$ironments

and upload that data to a *ustomer *onfiguration 0epository (**0) stored and managed by racle.

*M wors in tandem with PeopleSoft M/ for collecting configuration data from a PeopleSoft

en$ironment. %he *M data collection agents collect configuration data using the feed pro$ided by the

PeopleSoft M/ agents.

%he PSMAgent has to be running on the instance so that configuration data can be collected. After

crawling the en$ironment, PSMAgent writes the en$ironment data in OM format (with a .psft

e#tension) to the P#_HOME DccrDstate directory.

*M is installed and configured on a People%ools en$ironment as part of the application ser$er,

Process Scheduler ser$er, and web ser$er People%ools installation. >ou can also install and configure

*M by directly downloading the standalone install it from My racle Support.

See Peop/eoo/s ,3 Insta//ation )for &our p/atform* 5sing the Peop/e#oft Insta//er7

Instr!menting People#ools for Config!ration ata Collection

%his section pro$ides an o$er$iew of the data collection and discusses-

• Setting up Integration "roer for *M.

• 2eploying Ser$ices for *M.

• Setting up security for *M.

• Publishing ueries for *M.


24/93

Understanding People#ools Instr!mentation for +CM

%he optional configuration information collected from a PeopleSoft system for racle *onfiguration

Manager (*M) are defined as ueries and shipped with *M collectors. %he uery definitions need to

be instrumented after the installation and configuration of *M on a PeopleSoft en$ironment. %he

instrumentation step publishes the ueries that are reuired to gather configuration information from a

PeopleSoft system using Integration "roer. %he ueries can be instrumented by a a$a program

TpsftFrypub and are part of the *M collector. %he publishing of ueries is a one=time acti$ity

performed after the configuration of **0 collectors.

%he Integration "roer ser$ices and interfaces used by the publishing engine are-

Ser"ice Name +peration Name escription

EASFE0>FS0!I* EASFO*U%E0>S>H*FP0 2isco$ers application type.

EASFIS%EU0>FP0 2etermines whether data already e#ists.

EASFEU0>F2%FP0 2eletes uery for republishing.

EASFSA!FEU0>FP0 Sa$es uery definition.

P%F**0FEU0> **0F%0FA22F0* Adds participating records of a uery to

EU0>F%0F**0.

Setting Up Integration (ro,er for +CM

Setting up Integration "roer is discussed in the Integration "roer documentation.

Bhen setting up Integration "roer for *M, mae sure that-

• your gateway is configured and pointing to the appropriate gateway U0, such as

http-DDwebser$erFmachinenameJ-httpportJDPSIBDPeoplesoftistening*onnector.

• all other connectors are loaded.

• on the PeopleSoft Hode *onfiguration page you specify the appropriate ateway 2efault App.

Ser$er $alues and PeopleSoft Hodes $alues.


25/93

• you can ping the node successfully.

• on the Ser$ice *onfiguration page (People%ools, Integration "roer, Ser$ice *onfiguration) that

the target location http-DDwebser$erJ-httpportJDPSIBDPeopleSoftSer$iceistening*onnector.

eploying Ser"ices for +CM

%o publish EAS ser$ices-

3. Select People%ools, Integration "roer, Beb Ser$ices, Pro$ide Beb Ser$ice.

8. Search and select the EASFE0>FS0!I* ser$ice, and clic He#t.

9. Select !iew All to see all operations in the grid.

4. *hoose the following operations-

• EASFO*U%E0>S>H*FP0

• EASFIS%EU0>FP0

• EASFEU0>F2%FP0

• EASFSA!FEU0>FP0

:. *lic He#t until the final step and clic /inish.

5. Mae note of the BS2 U0 generated, and open the wsdl in a new browser and mae sure itwas generated successfully.

%o publish **0 ser$ices-

3. Select People%ools, Integration "roer, Beb Ser$ices, Pro$ide Beb Ser$ice.

8. Search for and select P%F**0FEU0>, and clic He#t.

9. *hoose the following operation. **0F%0FA22F0*.$3.

4. *lic He#t until the final step and clic /inish.

:. Mae note of the BS2 U0 generated, and pen the wsdl in a new browser and mae sure it

was generated successfully.

%o $erify permissions for ser$ice P%F**0FEU0> and operation **0F%0FA22F0*-

3. Select People%ools, Integration "roer, Integration Setup, Ser$ice perations.


26/93

8. /or search criteria enter- for-

• Ser$ice- P%F**0FEU0>

• Ser$ice peration- **0F%0FA22F0*

• peration %ype- Synchronous

9. *lic **0F%0FA22F0* and select Ser$ice peration Security.

4. Mae sure that the permission list P%P%3LLL has /ull Access is set.

Setting Up Sec!rity for +CM

%his section defines setting up of two user accounts.

User

Acco!nt

escription

Publisher Used by the client publisher a$a program to publish ueries using Integration "roer.

%o set up this user profile, add the **0 Publisher role to the user profile.

PSMAgent Used for configuring your application ser$er and Process Scheduler. PMAgent uses the same

credentials to run the ueries for publishing the configuration information to *M.

%o set up this user profile, add the **0 #ecution role to the user profile.

See Boring Bith User Profiles.

P!blishing .!eries

%he publisher program can be in$oed by running psftFrypub.bat in

PSF&MJDccrDsysmanDadminDutil.

Setting Up *hange Assistant

%his section co$ers topics related to setting up *hange Assistant, including how to-

• Install *hange Assistant.

• *onfirm the path $ariable.

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tsec/task_WorkingWithUserProfiles-c076b9.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tsec/task_WorkingWithUserProfiles-c076b9.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tsec/task_WorkingWithUserProfiles-c076b9.html


27/93

• Scan the worstation.

• 2efine en$ironment identification.

Installing Change Assistant

*hange Assistant runs only on supported Microsoft Bindows worstations. *hange Assistant is not

automatically installed when you install People%ools. >ou install *hange Assistant by running a separate

setup.e#e program in-

P#_HOME GsetupGPs*A

After installing *hange Assistant, you open it by selecting selectStart, then selectPrograms, then

selectPeopleSoft *hange Assistant


28/93

4. *lic n$ironment !ariables.

:. Select the Path $ariable in the System !ariables section, then clic the dit button.

%he dit System !ariables screen appears.

5. n the dit System !ariables dialog bo#, ensure that in the !ariable !alue field, the following

directory locations appear as the first entries in the Path string-

5D\PS3H9ME\bin\c"ient\in%*4

;. If you?$e made any modifications, clic @ to sa$e your settings.

efine En"ironment Identification

In the browser, na$igate to the People%ools ptions page (People%ools, Utilities, Administration,

People%ools ptions) and mae sure that the n$ironment ong Hame and n$ironment Short

Hame are specified correctly.

%he n$ironment Management /ramewor and *hange Assistant use these $alues, along with the

UI2, to identify an en$ironment and associate en$ironment information with a particular named

en$ironment. iewise, it enables you to search for updates for a specific en$ironment.

+pening Change Assistant the /irst #ime

%he first time you open *hange Assistant after installing it, you will be presented with the Belcomemenu. >ou can select not to display this page again.

Image: Change Assistant )elcome men!

%his e#ample illustrates the fields and controls on the *hange Assistant Belcome menu.


29/93

*lic He#t to $iew the *hange Assistant ptions.

Image: Change Assistant )i0ard-Select Action dialog bo1

%his e#ample illustrates the fields and controls on the *hange Assistant Bi+ard=Select Action dialog bo#.>ou can find definitions for the fields and controls later on this page.


30/93

2epending on the action you select, the *hange Assistant Bi+ard will guide you through the steps. ach

of these actions has a topic that will pro$ide details.

Apply Updates Any systems that are not PUM enabled, will use the Apply Updatesoption to apply updates downloaded from My racle Support.

Apply Updates can be used with any non=PUM change pacages.

See Applying Updates %o A %arget n$ironment

Update Manager Update Manager is used to create and apply PUM *hangePacages and PUM PeopleSoft 0elease Patches (P0P). %hePeopleSoft Image is the $irtual machine that contains the updates

for a PeopleSoft application. Update Manager currently onlysupports applications patching. %he PeopleSoft Update Manager PIAapplication is used in the PeopleSoft Image to search for updates,re$iew potential change impact, and create a custom changepacage definition that is based on the updates you selected for your en$ironment.

Note: Update Manager is only a$ailable for 6.8 applicationspatching.

See Update Manager Action $er$iew

Application

Upgrade

Application Upgrade is used to perform upgrade to a new applicationrelease, which typically includes a People%ools upgrade as well. /ullapplication upgrades are deli$ered with detailed templates anddocumentation tailored to your specific upgrade path.

See %he Upgrade Process Using *hange Assistant

UpgradePeople#ools

Upgrade People%ools is used to do a People%ools only upgrade.

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_ApplyingUpdatesToATargetEnvironment-0711d6.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_ApplyingUpdatesToATargetEnvironment-0711d6.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_UpdateManagerActionOverview.html#UpdateManagerOverview-5740571Fhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_UpdateManagerActionOverview.html#UpdateManagerOverview-5740571Fhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_TheUpgradeProcessUsingChangeAssistant-0711e9.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_TheUpgradeProcessUsingChangeAssistant-0711e9.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_ApplyingUpdatesToATargetEnvironment-0711d6.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_UpdateManagerActionOverview.html#UpdateManagerOverview-5740571Fhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_TheUpgradeProcessUsingChangeAssistant-0711e9.html


31/93

Compare2CopyManaged +b3ects or Merge Select +b3ect#ypes

Pro$ides the ability to copy and compare Managed b'ects pro'ectsand 2ata Migration Borbench pro'ects in *hange Assistant. >oualso ha$e the ability to $iew and merge People*ode, SE and OS%.

Create or Modify#emplates

*hange Assistant templates are composites of all the possible stepsthat apply to an update or upgrade. %he templates are deli$ered aspart of the change pacage. nce you select a change pacage, thetemplate is loaded into the *hange Assistant internal storage. >oucan edit the template or add additional chapters, tass and steps, ifneeded.

Understanding #he Change Assistant Interface

*hange Assistant enables you to run, $iew, and modify *hange Assistant templates. >ou open *hange Assistant on a Bindows worstation by selecting Start, Programs, PeopleSoft *hange Assistant


32/93


33/93

Interface Area escription

selected node on the template tree.

Acti$ity bo# %he Acti$ity bo# displays the processing and status messages associated with a step, when a 'ob is running in *hange Assistant. %his is similar to the utput window in the Application2esigner worspace.

Image: 4ob open in Change Assistant

%his e#ample illustrates the *hange Assistant interface for a 'ob running in *hange Assistant.

Boring Bith *hange Assistant Menu ptions

%his section describes the menu options a$ailable when using *hange Assistant.

Note: Some menu options are enabled only during a specific *hange Assistant action, which is

determined in the *hange Assistant Actions dialog bo#.


34/93

/ile Men!

%he /ile menu contains some generic Bindows options, plus these specific *hange Assistant options-

Men! +ption escription

Hew %emplate *reates a new *hange Assistant template.

pen

%emplate

pens a template of 'ob from the *hange Assistant storage (internal database).

Sa$e

%emplate

Sa$es the template into the *hange Assistant storage (internal database).

Sa$e

%emplate As

Sa$es the new template with the name you specify.

Hew ob *reates a new *hange Assistant 'ob.

pen ob pens a 'ob from the *hange Assistant storage (internal database).

Sa$e ob Sa$es the 'ob into the *hange Assistant storage (internal database).

Sa$e ob As Sa$es the 'ob with the name you specify.

*lose *loses the current template or 'ob.

Import%emplate

Imports an e#isting template into *hange Assistant.

Note: Any modifications to the current template will not affect the original template that you

imported. If you want others to obtain a copy of your modified template, you need to e#port it out of

*hange Assistant.

2elete 0emo$es the template from *hange Assistant. Bhen you delete a template, you also delete all the


35/93


%emplate 'obs associated with the template.

Note: Press and hold the *%0 ey to select multiple templates for deletion.

#port

%emplate

#ports a copy of the template out of *hange Assistant so others can use it.

2elete ob 0emo$es a 'ob associated with the current template.

Hewn$ironment

aunches the 2atabase *onfiguration wi+ard for creating a new en$ironment.

*hange Assistant uses these settings to locate P#_HOME directories, connect to the %arget

database, and so on.

pen

n$ironment

pens a defined en$ironment.

Import

n$ironment

Imports an e#isting en$ironment.

#port

n$ironment

#ports an e#isting en$ironment.

2elete

n$ironment

2eletes an e#isting en$ironment.

#it #its *hange Assistant.

Note: %his option is disabled when a *hange Assistant step is running. %o e#it *hange Assistant

while a process is running, you must first ill the process (select 0un, @ill). Bhen you relaunch

*hange Assistant you can resume at the point where you illed the process.


36/93


37/93


!iew og pens the current 'ob processing log.

!iew Script pens the script associated with the selected step.

ob Properties nables you to set properties for the upgrade 'ob created.

Set 2ocumentation

2irectory

Specifies the directory into which your upgrade documentation is sa$ed. *hange Assistant

loads the documentation for $iewing when you open a template or 'ob.

dit 2ocumentation nables you to modify the documentation associated with the selected chapter, tas, or

step.

/inali+e

2ocumentation

enerates the &%M files

%iew Men!

%he !iew menu contains these specific *hange Assistant options-


Step 2etails 2isplays the step properties bo# in the *hange Assistant worspace.

2ocumentation 2isplays the documentation bo# in the *hange Assistant worspace.

Acti$ity 2isplays the Acti$ity bo# in the *hange Assistant worspace.

'!n Men!

%he 0un menu contains these specific *hange Assistant options-


38/93

Men!

+ption

escription

0un "egins the e#ecution of a *hange Assistant 'ob.

*ancel Stops the processing of a *hange Assistant 'ob after the currently running process completes.

@ill Stops the processing of a *hange Assistant 'ob completely and immediately, inc/uding the step that?s

currently running.

#ools Men!

%he %ools menu contains these specific *hange Assistant options-


*reate *hange

Pacages

nabled when action type is Update Manager.

pens *hange Assistant Bi+ard to select your en$ironment information and leads you

through the process to create a change pacage.

See Peop/e#oft pdate Manager , Using Update Manager Action, 2efining a Hew*hange Pacage

Apply *hange

Pacages


pens *hange Assistant Bi+ard to select your en$ironment information and leads you

through the process to apply a change pacage.

See Peop/e#oft pdate Manager , Applying *ustom *hange Pacages, Applying *hange

Pacage

Apply PeopleSoft

0elease Patchset


pens *hange Assistant Bi+ard to guide you through applying PeopleSoft release

patchset to the PeopleSoft Image.

See Peop/e#oft pdate Manager , Applying PeopleSoft 0elease Patchset to PeopleSoft


39/93


Image, Applying 2ownloaded PeopleSoft 0elease Patchset to PeopleSoft Image

!alidate !alidates the *hange Assistant settings in your en$ironment, that the reuired elements

are up and running, and that *hange Assistant can connect to them.

Merge

People*odeDSE

nabled when action type is *ompareD*opy Managed b'ects or Merge Select b'ect

%ypes.

Allows you to start a new merge session or open an e#isting session.

2efault Merge 0ules nabled when action type is *ompareD*opy Managed b'ects or Merge Select b'ect

%ypes.

pens the 2efault merge 0ules dialog bo#.

Pro'ect Administration nabled when action type is *ompareD*opy Managed b'ects or Merge Select b'ect

%ypes.

pens Pro'ect Administration page.

Scan *onfiguration Searches the *hange Assistant worstation for tools and utilities reuired to perform

updates and upgrades. /or e#ample, this process locates the local SE tool, 2ata

Mo$er, Application 2esigner, and so on.

*hange Actions pens *hange Assistant Bi+ard Select Action page.

See pening *hange Assistant the /irst %ime

ptions pens the *hange Assistant ptions dialog bo#, enabling you to select *hange Assistant configuration options. %he options a$ailable depend on the Action selected.

Boring with *hange Assistant %emplates and obs

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_OpeningChangeAssistantTheFirstTime.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_OpeningChangeAssistantTheFirstTime.html


40/93

Bhether you are performing an update or an upgrade, you wor with *hange Assistant templates and

'obs. %he temp/atesare composites of all possible steps that apply to an update or upgrade, whether

they apply to your en$ironment or not.

%he source of the template is dependant on the action you are performing in *hange Assistant. %his

table lists the template source for each *hange Assistant action.

Change

Assistant

Action

#emplate

Apply Update *hange Assistant template comes in the change pacage downloaded from MS.

/or change pacages created in Application 2esigner, the template is generated when you

select enerate Hew %emplate.

Update Manager *hange Assistant template is either generated from the custom change pacage when you

select to apply the change pacage or deli$ered from PeopleSoft if you are applying a P0P

(PeopleSoft 0elease Patchset.).

Upgrade *hange Assistant template for your upgrade path is downloaded from MS.

After you specify the reuired settings in *hange Assistant regarding your en$ironment, you use *hange

Assistant to build a 9o' tailored to your en$ironment. Bhen building the 'ob, *hange Assistant filters thesteps so that the 'ob contains only the steps applicable to your implementation. /or e#ample, the

resulting *hange Assistant 'ob will ha$e only steps that apply to your database type, your installed

applications, your languages, and so on.

Bhen you apply updates or run an upgrade, *hange Assistant automatically loads the template into the

*hange Assistant internal storage system. >ou can add additional chapters, tass, and steps to the

template, if needed. %o edit a template, you must be in the *reate or Modify %emplates mode, specified

on the *hange Assistant ptions dialog bo#.

#amples of custom steps that might be added include, dropping inde#es, adding inde#es, bacing up a

database, and so on.

Note: In most cases, it is not necessary (or recommended) to modify a deli$ered template. Any changes

that you mae to the imported template won?t affect the original template that you downloaded. &owe$er,

if you choose to edit a template, eep a bacup of the original.

Creating New #emplate Elements

>ou can add chapters, tass and steps to an e#isting template.


41/93

%o insert a template element-

3. &ighlight the location where you want to add the element.

If you want to add a chapter abo$e the e#isting first chapter in the template, highlight the template

root node (template name) at the top of the template tree.

8. /rom the dit menu (or toolbar) select the appropriate option- Insert *hapter, Insert %as, Insert

Step.

9. nter a uniue name for your new element.

Note: ach chapter in the update template must ha$e a uniue name, each tas within a chapter

must ha$e a uniue name, and each step within a tas must ha$e a uniue name.

4. *lic @.

Bhen creating new steps, *hange Assistant displays the Step Properties dialog bo# for specifyingstep options.

eleting #emplate Elements

%o delete a chapter, tas, or step-

3. &ighlight the chapter, tas, or step that you want to delete.

Note: Press and hold the *%0 ey to select multiple steps for deletion.

Warning! If you delete a chapter, *hange Assistant deletes all the tass and steps within thechapter. If you delete a tas, *hange Assistant deletes all the steps within the tas.

8. Select from the following-

a. If you want to delete a chapter, select dit, 2elete *hapter.

b. If you want to delete a tas, select dit, 2elete %as.

c. If you want to delete a step, select dit, 2elete Step.

9. *hange Assistant deletes the chapter, tas, or step and updates the template.

4. Sa$e the template.

E1porting #emplates

In order for others to use the template that you create or modify, you need to e#port it from *hange

Assistant. If you want to o$erwrite an e#isting template file, enter the name of the original template.


42/93

%o e#port a template-

3. pen the template in *hange Assistant by selecting /ile, pen %emplate.

8. Select /ile, #port %emplate.

%he #port %emplate dialog bo# appears.

9. Ha$igate to the folder in which you want to sa$e the template.

4. nter the name of the template.

Note: If you want to o$erwrite the original template that you downloaded, enter the original name of

the template.

:. *lic Sa$e.

E1porting 4obs to M&5 $#M&5 or Microsoft E1cel /ormat

*hange Assistant allows you to e#port 'obs to OM, &%M, or Microsoft #cel file formats.

%o e#port a 'ob-

3. Select /ile, #port ob.

8. nter the desired e#ported filename and the select the desired file type format.

>ou can use this option to enable other implementation team members, who do not ha$e access to the

machine on which *hange Assistant is running, to view the 'ob. #porting the 'ob to Microsoft #celenables you to $iew the timings in a spreadsheet format.

Note: >ou can not e#port a *hange Assistant 'ob and either import it or open it on another machine with

*hange Assistant installed and then run or modify the 'ob on that other machine.

Boring with Steps


• Set step properties.

• Set filter ueries.

• !iew step status.


43/93

Setting Step Properties

PeopleSoft deli$ers update templates with default settings and steps to perform updates. If needed, you

can modify the steps, or create new steps, based on the conditions that apply when you run the update

process.

%o modify the step properties, highlight the step for which you want to modify the step properties, then

double=clic on the step or select selectdit, then selectStep Properties. After maing any changes to

step properties, clic @, and sa$e your template.

Note: 2epending on what mode you are in, some of the fields may be disabled.

Note: Under normal circumstances, it is recommended that you do not modify or edit the step properties

in your deli$ered template.

%his section describes fields and options on the Step Properties dialog bo#. >ou can modify step

properties for a step when adding or editing steps in the template.

Image: Step Properties dialog bo1

%his e#ample illustrates the fields and controls on the Step Properties dialog bo#. >ou can find

definitions for the fields and controls later on this page.


44/93

Step escription %his field displays the current step.

Script2Proced!re nter the name of the script, procedure, pro'ect, or program name

to which you want to assign the properties of the step. /or

e#ample, enter #:#A;I .

%his field is reuired for all step types e#cept manual stop.

#ype Select a step type. %his selection defines the type of action to be

performed by the step. /or e#ample, if you are running the

S>SAU2I% SE0 report, select #


45/93

in this People"oo.

See Step %ypes

Parameters nter additional parameters that you may need to run the step. /or

e#ample, for SE commands, you enter the actual SE command

in this field. In other cases, you use this edit bo# to o$erride $arious

en$ironment settings or other parameters so that the step

completes successfully.

2etailed information related to the parameter options for each step

type appears elsewhere in this People"oo.

See Step Parameters

/rom #ools 'elease Specify the People%ools releases to which a step applies. Use the

associated operator dropdown list to indicate ranges of releases.

%he default $alues are A// with the =operator.

%he operator dropdown list enables you to e#press greater than,

less than, eual to, and ?in? relationships.

%he in operator enables you to specify more specific ranges, such

as ?in?


46/93

remotely.

• "emote Agent - runs the step on a remote ser$er. 2uring a

full upgrade, some steps are data intensi$e and, for

performance reasons, can be run on a remote ser$er. If youselect "emote Agent , before running the step you need to

configure the 0emote Agent options on the *hange Assistant

ptions dialog.

%he details of setting up this option are documented in the

upgrade portion of this People"oo.

See *onfiguring 0emote Agent Processing.

+rientation Specify which database the step needs to be run against. ptionswill $ary based on the action selected, but may include-

• #ource

• arget

• 8op& of 8urrent ;emo

• Production

Step type and type of upgrade determine $alid orientation settings.

See Source and %arget 2atabases.

Prod!cts *lic the Products icon. *hange Assistant displays the Select

Products dialog bo#, which enables you to select the product line,

the industry, and the products to which your step should be run

against (for e#ample, /IHDS*M, *ommercial, Asset Management).

Note: >ou must select at least one product.

Apply #ype Specify the type of upgrade to which this step applies-

• Initia/ Pass- refers to the initial application of a change

pacage or new release to your *opy of Production database.

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_ConfiguringRemoteAgentProcessing-4a7849.html#ConfiguringRemoteAgentProcessing-4a7849https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_SourceandTargetDatabases-2e760a.html#SourceandTargetDatabases-2e760ahttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_ConfiguringRemoteAgentProcessing-4a7849.html#ConfiguringRemoteAgentProcessing-4a7849https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_SourceandTargetDatabases-2e760a.html#SourceandTargetDatabases-2e760a


47/93

• Move to Production- refers to the upgrade between your

*opy of Production database and your test or production

system.

• $oth- refers to steps that need to be run in both apply types.

Note: Bhen the 'ob is created, the system filters the template steps

to be e#ecuted by the apply type specified. /or e#ample, if Move to

Production is specified as the apply type, only steps in the template

specified as Mo$e to Production or "oth will be included in the 'ob.

Allow for Errors Indicates how the system should react to any errors that may arise

during a step run. If set to :es, if the step encounters errors the

system does not perform any error handling and continues on to

the ne#t step.

2efault is set to 1o.

'!n Conc!rrently nables you to set multiple steps (programs, processes, and so on)

to run simultaneously.

If you select this option for two or more consecuti$e steps, *hange

Assistant starts those processes concurrently, until the 'ob reaches-

• a step with 0un *oncurrently set to 1o.

• a step type of Manua/ #top.

• the Ma#imum *oncurrent Processes $alue, as set on the

*hange Assistant ptions dialog bo#.

"y setting 0un *oncurrently to :es, you are indicating to *hange

Assistant that this step can run concurrently with the following step.

%he total number of processes that can run concurrently is

determined by the Ma#imum *oncurrent Processes setting on the

*hange Assistant ptions dialog bo#.

/or e#ample, assume there are four steps set to run concurrently,

followed by a fifth step set not to run concurrently, with the

Ma#imum *oncurrent Processes $alue set to 3. In this scenario,

*hange Assistant launches the first three steps to run concurrently.

Bhen one of the first three steps completes, the fourth step starts

processing, and as soon as another step completes, the fifth step


48/93

begins processing. %he step after the fifth step does not start until

the fifth step completes.

0unning steps concurrently is a strategy reser$ed for application

upgrades to sa$e time when running the following step types on aremote host through a remote M/ agent or Process Scheduler-

• Application ngine

• SE

• 2ata Mo$er

*oncurrent processing is not enabled in any circumstances for

these step types-

• 2"%S/IO

• oad "ase 2ata

• Upgrade People%ools

• Manual Stop

Note: If a step is dependent on a pre$ious step, it is not

recommended to set it to run concurrently with that step.

Note: Steps set to run concurrently can span across multiple

consecuti$e tass or chapters, and can be of different step types.

Note: In an application upgrade, do not run the CUpdate

People%ools System %ablesC step concurrently, and, unless

specifically instructed to do so, do not run any of the steps in the

CApply People%ools *hangesC chapter concurrently.

See the upgrade documentation for your specific upgrade for

recommendations on specific steps within that upgrade that can be

run concurrently.

Setting /ilter .!eries

/ilter ueries pro$ide the ability to add ad=hoc step filtering criteria to a template to further impro$e

applicability of 'ob to the customer and where possible remo$e unnecessary manual steps.

See Adding /ilter Eueries

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_AddingFilterQueries.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_AddingFilterQueries.htmlhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_AddingFilterQueries.html


49/93

%iewing Step Stat!s

Bhen woring with templates and 'obs, you see these status icons to the left of steps-

0un Indicates that *hange Assistant runs this step or processautomatically without manual inter$ention.

Stop Indicates that *hange Assistant stops on this process. It also

indicates that there may be manual steps to perform for this step.

0e$iew the documentation window for further instructions. After

completing the wor described in a manual step, you must set the

status to 8omp/ete,

0estart Indicates a restart process. If a step failed and you corrected the

problem, you can set the step to restart from the point of failure.

Processing Indicates that the process is running.

/ailure Indicates a failure has occurred that needs immediate attention.

%his appears if a 2ata Mo$er script, SE script , or pro'ect copy

step fails. 0esol$e the error before continuing with processing.

Barning Indicates a warning for this step which does not need immediate

attention. %he 'ob continues processing with no ad$erse affects.

After the 'ob completes, re$iew the steps in a warning state and

e$aluate for further action.

*omplete Indicates that the step is complete.


50/93

Adding /ilter Eueries

/ilter ueries pro$ide the user with the ability to add ad=hoc step filtering criteria to a template in order to

impro$e the applicability of a 'ob to the customer and where possible remo$e unnecessary manual

steps.


• *reate /ilter Euery Step type.

• Assign /ilter Euery to a step.

• *ut and Paste filter ueries

• *reate and e#ecute 'obs that include filter ueries.

Creating /ilter .!ery Step #ype

A template can ha$e LVn /ilter Euery steps defined and they can be defined at any position in the

template. %he location of the filter uery step will determine when the filter ueries associated to that

step will be e#ecuted.

Image: /ilter .!ery Step dialog bo1

%his e#ample illustrates the fields and controls on the /ilter Euery Step dialog bo#. >ou can find

definitions for the fields and controls later on this page.


51/93

Script2Proced!re %he ScriptDProcedure is defaulted to /ilternW3J where n is set to L

for a new template and incremented by 3 each time a /ilter Euery

step type is added and sa$ed.

%he first /ilter Euery step created in a template will be named

/ilter3, the second will be named /ilter8, and so on.

%hese $alues must be uniue, deletion of a filter uery step, will not

change the n $alue. Bhen a filter uery step is deleted, the $alue is

ne$er reused.

efine /ilter .!ery Use this button to access the 2efine /ilter Eueries dialog bo#.

%he following step attributes can be set for /ilter Euery step type-

• /rom %ools release


52/93

• rientation

• Products

• Platforms

• anguages

• Apply %ype

Setting Step Properties

%he following step attributes cannot be changed and will be greyed out.

• Parameters X not reuired for Euery /ilter step type

• 0un ocation (2efault K ocal)

• Allow for rrors (2efault K Ho)

• 0un *oncurrently (2efault K Ho)

Note: A filter uery step cannot be filtered by itYs own uery. A filter uery step can not be filtered by a

filter uery defined in another step.

efining /ilter .!eries

%he 2efine /ilter Eueries page is used to define the actual filter ueries. %he grid is displayed in read=

only mode and always contains a minimum of one row in the $iew.

• %o add a new filter uery, right=clic and select Add Hew /ilter Euery.

• %o delete an e#isting filter uery, right=clic on the row and select 2elete Selected /ilter Euery.

• %o update an e#isting filter uery either-

0ight=clic on the row and select dit Selected /ilter Euery.

2ouble clic on the row.

efining /ilter

Use the /ilter 2efinition dialog bo# to define the filter.

Image: /ilter efinition dialog bo1

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_WorkingwithSteps-307d65.html#SettingStepProperties-307b61https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/concept_WorkingwithSteps-307d65.html#SettingStepProperties-307b61


53/93

%his e#ample illustrates the fields and controls on the /ilter 2efinition dialog bo#. >ou can find definitions

for the fields and controls later on this page.

/ilter I %he /ilter I2 must be uniue within the /ilter Euery step. %he /ilter

I2 $alue in con'unction with the ScriptDProcedure name is used to

ensure uniueness within the template. /or e#ample- /ilter3VAP

*hec.

escription nter a description for the filter uery.

.!ery efinition nter the SE statement for the uery.

Special filter ueries are also a$ailable as described in the ne#t

section.

Note: %he SE statement is not $alidated.

/ilter if #r!e %al!e %he /ilter if %rue !alue can be a numeric or a string. !alid operator

are-

• Humeric

K, , J, JK, K, J


54/93

• String

*ontains, 2oes Hot *ontain

/or a single filter uery, when the @i/ter if rue a/ue is %rue thenthe associated step will be filtered.

Special /ilter .!eries

In addition to the standard user defined ueries, a special platform=based filter uery is a$ailable where

*hange Assistant le$erages itYs own metadata about the en$ironments to resol$e the uery.

%he following would be inserted in lieu of an actual SE statement. %he $ariables cannot be used as a

part of the actual SE statement. #amples of uniue identifier pairing would be-

• ZPA%/0MFS0*KZPA%/0MF%%

• ZPA%/0MFS0*KZPA%/0MF2M

• ZPA%/0MFS0*KZPA%/0MFP02

%he return $alue for these pairings will be : for yes and 1 for no.

/or more information on $ariables see /ilter Euery !ariables

Assigning /ilter .!ery to a Step

%o use a filter uery, the filter uery must be assigned to a step. %he following rules apply-

• %he drop down list of filter ueries will be restricted to filter ueries that are defined in the

template at a position ahead or abo$e the step being updated.

• Steps can only be associated to /ilter Eueries that would e#ecute prior to the step being

e#ecuted.

• Steps cannot be associated to the same /ilter Euery twice.

Adding a .!ery /ilter to a Step

%o add a uery filter to a step-

3. 2ouble=clic on the step to open the Step properties.

8. Select the /ilter Eueries tab.

https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_StepParameters-3077c1.html#pstopic2-162-8E9E84CEhttps://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tswu/task_StepParameters-3077c1.html#pstopic2-162-8E9E84CE


55/93

Image: /ilter .!eries dialog bo1

%his e#ample illustrates the fields and controls on the /ilter Eueries dialog bo#. >ou can find definitions

for the fields and controls later on this page.

Step will be filtered

if:Select when filtering will be done.

• All /ilter Eueries listed 0eturn %rue !alues

AH2 condition

• ne /ilter Euery listed returns %rue $alue

0 condition

/ilter Name Select the /ilter name from the drop down list.

%o add additional filter ueries, right=clic and select Insert Euery.

/ilter Identifier Select the /ilter Identifier from the drop down list.

Note: %he drop down list will contain all of the /ilter I2s for the

selected /ilter Hame. %his field will be grayed out if a /ilter namehas not been specified.

%o add additional /ilter Eueries, right=clic on a row and select Insert Euery.


56/93

eleting a .!ery /ilter from a Step

%o delete a uery filter-

3. 2ouble=clic on the step to open the Step properties.

8. Select the /ilter Eueries tab.

9. 0ight=clic on the row with the filter and select 2elete Euery.

4. *lic @.

C!tting and Pasting /ilter .!eries

nce /ilter Euery Step types ha$e been defined and used as filters for additional steps, you must tae

care in deleting or mo$ing the steps in the template. @eep in mind the following points-

• 2eleting a /ilter Euery Step

If you delete a /ilter Euery step from the template, you will recei$e a warning that the deletion will

result in all references to all filters defined in that step will be deleted. If you choose to continue, the

process will remo$e all step references to the deleted ScriptDProcedure W /ilter I2 $alues.

• *utting and pasting a /ilter Euery Step to another location in the template

Pasting to a position abo$e or ahead of the original position has no impact.

Pasting to a position below the original position will result in a warning message

indicating that mo$ing step will result in remo$al of references to the current filter uery step

abo$e itYs new position.

If you choose to continue, the process will remo$e all step references to the

mo$ed ScriptDProcedure W /ilter I2 $alues in steps that precede it in the re$ised template.

• *utting and pasting a non=filter uery step

Pasting to a position below the original position has no impact.

Pasting to a position abo$e the original position will result in a warning message

indicating that mo$ing the step will result in remo$al of references to filter ueries below itYs

new position.

If you choose to continue, the process will remo$e all step references to the

impacted ScriptDProcedure W /ilter I2 $alues within the relocated step.


57/93

Creating and E1ec!ting 4obs that Incl!de /ilter .!eries

%his section discusses how filter ueries affect-

• ob *reation

• ob #ecution

4ob Creation

At the time of 'ob creation, /ilter Euery steps can be filtered by any of the standard attributes (such as

Platforms) as is the case for any other Step type. %he filtering of a /ilter Euery step in this manner does

not in$alidate or cause steps that reference the filter uery to filtered.

At 'ob creation all /ilter Eueries defined within the template will be set to a default $alue of Hull or Ho

!alue. Ho Step will be filtered by an Ad=&oc /ilter Euery at 'ob creation, because no /ilter ueries ha$e

been run at that time. %he earliest these /ilter Eueries can be e#ecuted is in the first step of the

templateD'ob.

A step can be filtered by a System /ilter Euery at 'ob creation, assuming that the associated step does

not also ha$e any ad=hoc /ilter Eueries associated to it.

4ob E1ec!tion

n /ilter Euery step e#ecution, results are retrie$ed for all filter uery I2Y s defined within that specific

/ilter Euery step. %hese results are written to the *hange Assistant database.

• %he e#ecution accounts for the orientation of the /ilter Euery step.

• %he return $alues for each /ilter Euery are noted in the *A log listing the /ilter Identifier, /ilter I2,

the &ide if %rue *ondition, the return $alue and whether the &ide if %rue *ondition was met.

• In the e$ent of a SE error, an error message is written to the *A log and the step is mared

as @ai/ed .

• In the e$ent that the SE returns a $alue of the wrong type (numeric as string) ,an error message

is written to the *A log and the step is mared as @ai/ed .

Upon completion of this e#ecution, the template is refreshed and as part of this action filtering of steps

will occur. /iltering of steps by filter uery can only occur where all associated /ilter IdentifierY s ha$e

been resol$ed and are not in the Hull or no $alue state. %his is true e$en when only a single /AS is

reuired to filter a step.

Bhen a ob is opened or refreshed V the filter uery filtering will e#ecute to ensure that all reuired

filtering has occurred.

Boring with mbedded 2ocumentation


58/93


59/93

Creating and Editing oc!mentation

%o create or edit documentation-

3. Select the desired element node.

8. Select selectdit, then selectdit 2ocumentation.

9. In the edit bo# on the dit 2ocumentation dialog bo#, insert your cursor, and add new content or

modify e#isting content.

*lic Attach to incorporate additional files, such as graphics or additional te#t files. Attaching files

mo$es that file into the documentation directory and inserts a lin to that file in the embedded

documentation.

4. *lic @.

/inali0ing oc!mentation

After modifying any documentation for indi$idual template elements, select selectdit, then

select/inali+e 2ocumentation to compile the indi$idual documentation changes into the master &%M file.

Maintaining Change Assistant irectories

After you download and apply change pacages, it?s not uncommon for there to be a number of files leftin the local *hange Assistant directories. %his section describes when it?s safe to remo$e the files andwhat to consider if you want to remo$e any of the files.

irectory Maintenance Consideration

2ownload ocation where the system stores your downloaded bundles and change pacages. After the updates ha$e been applied to all en$ironments, you may delete the updates from thisdirectory.

%his can be ad$antageous when applying change pacages by eeping the list ofchange pacages on theSelect *hange Pacages page of the Apply *hange Pacageswi+ard at a manageable length.

&owe$er, eep in mind that if you delete the updates, and then you need to recreateanother en$ironment, you will need to download the update again.

Staging A temporary holding place for files needed during the application of a change pacage. Itis safe to delete files in this directory after a change pacage has been successfullyapplied to all target databases.

utput *ontains all the logs related to the processing of a change pacage. %he files in this

directory should be ept as long as it is feasible in case problems are detected later. %helogs contain $aluable information for troubleshooting.

PeopleSoft UpdateManager 2irectory

%his is a networ share that maps to the PIF&M share of the image. 2o not deletethese files.

PSF&MGMaint *ontains script files and other files that are only reuired during the application of thechange pacage. It is safe to delete files in this directory after a change pacage hasbeen successfully applied.


60/93

0unning *hange Assistant ob from the *ommand ine

*hange Assistant 'obs can be run from the command line to automate applying updates to multiple

en$ironments.

Command &ine for '!nning PUM Updates 678 and $igher

All PUM=enabled en$ironments will use the en$ironment information defined $ia the Update Manager

Action ptions UI. SeePeop/e#oft pdate Manager , Using Update Manager Action, Selecting Update

Manager Action, *onfiguring *hange Assistant for Update Manager.

*ommand line format-

5hangeassistant.e%e SR5E0F !$eo$"eSot 6mage database# =/=E0F !targetdatabase# G UP: !change $ac7age# S !i"e server# :L !don"oad director=IPE !initia" $ass or move to $rodction# 9U= !"og i"e director E-90ERR!"anch /U6 I or 0#

#ample command line-

5hangeassistant.e%e SR5E0F HR6MA/E =/=E0F HRJKA G UP: $dP>/,

In this e#ample the source database (PeopleSoft Image) is named &0IMA, the target database is

named &068A and the change pacage to apply is upgP@3 (name of the custom change pacage

created in Update Manager with the upg prefi# when the change pacage is created). All of the other

parameters will use the default.

Parameter escription

=S0*H! Hame of source en$ironment containing the PeopleSoft Image database. (0euired)

=%%H! Hame of target en$ironment. (0euired)

=UP2 %he *hange Pacage to apply. (0euired)

Specify either a// , a single or multiple *hange Pacages to apply to the specified en$ironment.

/or e#ample-

• =UP2 all

• =UP2 upd333333


61/93


• =UP2 upd333333,upd888888

=/S /ile Ser$er path to apply the *hange Pacage to the specific en$ironment. (ptional)

Select either a// or list a specific file ser$er configuration path in order.

/or e#ample-

• =/S all

• =/S c-Gpt


62/93

5hangeassistant.e%e M9:E !$date manager mode# A5=690 !APPLI $r$# =/=E0F!name o target environment # G UP: !change $ac7age# =IPE !initia" $ass ormove to $rodction# 9U= !"og i"e director E-90ERR !"anch /U6 I or 0#

#ample command line-

5hangeassistant.e%e M9:E UM A5=690 PRPAPPLI =/=E0F HR6MA/E G UP: $dP>/,

In this e#ample the target database (PeopleSoft Image) is named &0IMA and the change pacage to

apply is upd33333 (name of the downloaded P0P change pacage). All of the other parameters will use

the default.


=M2 *hange Assistant Action (0euired)

UM K Update Manager

=A*%IH Action name (0euired)

P0PAPP> K Apply P0P

=%%H! Hame of target en$ironment containing the PeopleSoft Image database. (0euired)



/or e#ample-

• =UP2 all

• =UP2 upd333333

• =UP2 upd333333,upd888888

=%>P Apply %ype. (ptional)

• I K Initial Pass (default)


63/93


• M K Mo$e to production

=U% Path of log file (ptional)

If the log directory is not specified it uses the default defined under eneral ptions.

=OH00 Specify whether or not to launch UI if an error or manual stop is encountered. (ptional)

• > K 2o not aunch

• HK aunch (default)

Command &ine for Uploading Change Assistant En"ironments that were Pre"io!sly E1ported

%o upload a *A en$ironment that was pre$iously e#ported use this command line format-

changeassistant M9:E UM A5=690 E0F6MP 6LEPA=H !"ocation o %m" i"e# 6LE!%m" i"e name#


=M2 *hange Assistant Action (0euired)

UM K Update Manager

=A*%IH Action name (0euired)

H!IMP K Import n$ironment

=/IPA%& ocation of #ml file to be uploaded. (0euired)

#ample- =/IPA%& *-Gpt


64/93


#ample- =/I P%6L903.#ml

Command &ine for Non PUM-Enabled En"ironments

/or Hon PUM=enabled en$ironments (PeopleSoft Image is not installed), use the following command

line format-

5hangeassistant.e%e E0F !target database# G UP: !change $ac7age# S !i"eserver# 5A !access id# 5AP !access $assord# 59 !ser id# 5P !ser$assord# :L !don"oad director BL: !mana" or ato# 9U= !"og i"edirector E-90ERR !"anch /U6 I or 0#

Note: M/ Agent must be running.


=H! %arget database. (0euired)



/or e#ample-

• =UP2 all

• =UP2 upd333333

• =UP2 upd333333,upd888888

=/S /ile Ser$er path to apply the *hange Pacage to the specific en$ironment. (0euired)

Select either a// or list a specific file ser$er configuration path in order.

/or e#ample-

peoplesoft update manager

Documents