Patch Installation - PeopleSoft

Size: px

Start display at page:

Download "Patch Installation - PeopleSoft"

Cornelia Franklin
6 years ago
Views:

1 Patch Installation - PeopleSoft White Paper By B Venkataramanan bvraman99@yahoo.com December 2004 Abstract This document starts with a description of methods/tools available to load a typical custom/peoplesoft patch release in a peoplesoft implementation. It discusses in detail an automated method of loading patches using available peoplesoft tools.

2 Table of contents 1 PREFACE STANDARD PEOPLESOFT PATCH INSTALLATION PROCESS PATCH CONTENTS PATCH INSTALLATION PROCESS DISADVANTAGES WITH THE ABOVE PROCESS AUTOMATED PEOPLESOFT PATCH INSTALLATION PROCESS INTRODUCTION TO UPGRADE ASSISTANT PRE-REQUISITES UPGRADE TEMPLATES Creating Custom Templates Creating New Chapters Creating New Tasks Creating New Steps Modifying Step Properties UPGRADE JOBS ADDING CUSTOM DOCUMENTATION FOR CUSTOM CHAPTERS, TASKS AND STEPS ADVANTAGES WITH THE AUTOMATED PROCESS...20 REFERENCES...21

3 1 Preface This paper summarizes the patch delivery process from peoplesoft. Later it suggests an automated method using peoplesoft delivered tools. Disclaimer Though the author has tested the method, there is no guarantee that this will work in your environment as is. Slight modification and testing needs to be performed for each environment you want to use the process suggested in this paper. 1

4 2 Standard P eoplesoft Patch Installation Process 2.1 Patch Con tents The objects delivered in a patch or application update may include changes to batch files, data changes, database code revisions and objects, record structures, and PeopleCode. In general the update contains one or more of the following: Project Files Data Mover Scripts Installation Instruction Document Delivered Resolution description document Delivered Code Details Document 2.2 Patch Ins tallation Process This section summarises the common steps involved in applying the update contents to your People Soft application environment. Perform Database auditing and verify the results. Application of Project Files using Application Designer Building of Project Files using Application Designer Application of DataMover Scripts using DataMover Any Post update steps of running application engine. 2.3 Disadvan tages with the above process These instructions are intended for the expert technical user who is responsible for applying application changes to your PeopleSoft system. This user should have a basic understanding of PeopleSoft systems Familiarity with PeopleSoft Upgrade Assistant, PeopleSoft Data Mover, PeopleSoft Application Designer, COBOL compilers, and structure query language (SQL) tools may also be necessary. The steps for loading the release is largely manual which may increase the chances of human errors. Installation time is more in case the content of the update is huge. E.g. multiple projects, data mover scripts or a big release. 2

5 3 Automate d PeopleSoft Patch Installation Process To achieve automatic loading of objects, this process would use PeopleSoft Upgrade Assistant tool. The below sections details out how the automation would be achieved using the mentioned tool. 3.1 Introducti on to Upgrade Assistant PeopleSoft Upgrade Assistant helps to assemble and organize all of the steps necessary to complete your upgrade. Upgrade Assistant can run some of the steps automatically, while others may require you to make changes manually. To run an upgrade using Upgrade Assistant, you must have an Upgrade Template and an Upgrade Job. To learn more about Upgrade Assistant features please refer Peoplesoft Upgrade Assistant PeopleBook. 3.2 Pre-Requ isites The table below describes the preparation steps required to load the update/release using upgrade assistant. Task Number Task Description 1 Install the Upgrade Assistant in your client PC. Use Peoplesoft Delivered Install Document. To install local administrator rights are needed on the workstation 2 Install the Oracle client on the installer's workstation. The Oracle client installation must include SQLPLUS Executable (SQLPLUS.EXE) file. 3 Update the TNSNAMES.ORA file on the installer's workstation (located in the ORA_HOME\...\network\admin folder) to include the TNS information of the target database 4 Turn off the automatic locking of the workstation on the installer's workstation. 5 Verify the Oracle client installation and the TNS information by executing SQLPLUS.EXE and then signing on to the target database with the database userid. If Password is not known then please arrange the database password. 6 Signon to the installer s workstation with a user id that has local administrator rights on the workstation. 3

6 Task Number Task Description 8 (Applicable if you are using Non-English Regional Setting) Change installer s workstation to use the U.S. English keyboard as follows. Set the windows regional settings to US from German: 1. Navigate to Start - Settings Control Panel Regional Options 2. Write down the existing setting and then make the following change. On the General tab change the 'Your locale (location)' setting to English (United States) 3. Write down the existing setting and then make the following change. On the Input Locales tab change the input locale properties for the EN keyboard to US. (This will change some of the key mapping of the keyboard. For example the keys for the letters Z and Y and interchanged. Double check what is typed on the screen) 3.3 Upgrade T emplates PeopleSoft Upgrade Assistant uses an upgrade template for each update/release. The upgrade template contains the chapters, tasks, and steps for the upgrade and consists of SQL scripts, Data Mover scripts, SQR processes, Application Engine processes, and Application Designer procedures. The examples in this section describe how to create a custom chapter, steps and tasks. It further explains what parameters needs to be configured for each type of peoplesoft object Creating Cu stom Templates To create a custom template: 1. Select the Upgrade Template view. 2. Select File, New Upgrade Template. 3. Enter the name of the new template and click OK. PeopleSoft Upgrade Assistant displays the name of your new template in the Template Tree Creating Ne w Chapters A chapter is a section heading for a group of tasks. To insert a chapter: 1. Highlight the location where you want to add the chapter. If this is the first chapter in the template, highlight the top node (template name) at the top of the Template Tree. If you are adding a task to an existing template, put your cursor where you want to insert the task. 2. On the Upgrade Assistant toolbar, select Edit, Insert Chapter. 3. Enter a unique name for your new chapter and click OK Creating Ne w Tasks A task is a section heading for a group of steps. To insert a task: 1. Highlight the location where you want to add the task. If you are adding a task to an existing template, put your cursor where you want to insert the task. 2. On the Upgrade Assistant toolbar, select Edit, Insert Task. 3. Enter a unique name for your new task and click OK. 4

3.3.4 Creating Ne w Steps A step can be any process needed to perform the upgrade. To insert steps: 1. Highlight the task where you want to add the new step. 2.

7 3.3.4 Creating Ne w Steps A step can be any process needed to perform the upgrade. To insert steps: 1. Highlight the task where you want to add the new step. 2. From the Upgrade Assistant toolbar, select Edit, Insert Step. 3. Enter a unique name for your new step and click OK. 4. PeopleSoft Upgrade Assistant displays the Step Properties dialog box. 5. You must define the step properties for the new step Modifying S tep Properties The examples below consider copying a project, building a project, running build, SQL and datamover scripts. Loading of a Project Here are the values used in the step property. Script Procedure: Enter the script or procedure, if one is associated with the current step. This field is used for SQL scripts, Data Mover scripts, SQRs, and Application Engine Processes. Type: Copy of a project from File. Parameters: #Project - Name of the Project to be copied #Directory Path of the Directory where the object is lying. Upgrade Options: Retain same options, as you would use while using Application Designer. 5

Building a Project Here are the values used in the step property. Script Procedure: Enter the script or procedure, if one is associated with the current step.

8 Building a Project Here are the values used in the step property. Script Procedure: Enter the script or procedure, if one is associated with the current step. This field is used for SQL scripts, Data Mover scripts, SQRs, and Application Engine Processes. Type: Build Project. Parameters: #Project - Name of the Project to be built Build Options: Retain same options, as you would use while using Application Designer. 6

9 Running the Build Script Here you run the build script generated by the previous step. Here are the values used in the step property. Script Procedure: Enter the script or procedure, if one is associated with the current step. This field is used for SQL scripts, Data Mover scripts, SQRs, and Application Engine Processes. Type: SQL Script Parameters: #Directory - Name of the directory where the SQL file is present #OutputDirectory Variable pointing to Upgrade Assistant output directory. 7

Running the Custom SQL Script Here are the values used in the step property. Script Procedure: Enter the script or procedure, if one is associated with the current step.

10 Running the Custom SQL Script Here are the values used in the step property. Script Procedure: Enter the script or procedure, if one is associated with the current step. This field is used for SQL scripts, Data Mover scripts, SQRs, and Application Engine Processes. Type: SQL Script Parameters: #Directory - Name of the directory where the SQL file is present or #OutputDirectory Variable pointing to Upgrade Assistant output directory. 8

Running the DataMover Import Script Here are the values used in the step property. Script Procedure: Enter the script or procedure, if one is associated with the current step.

11 Running the DataMover Import Script Here are the values used in the step property. Script Procedure: Enter the script or procedure, if one is associated with the current step. This field is used for SQL scripts, Data Mover scripts, SQRs, and Application Engine Processes. Type: Data Mover User or Data Mover - Bootstrap Parameters: #Directory - Name of the directory where the SQL file is present or #OutputDirectory Variable pointing to Upgrade Assistant output directory. Note: In the Data Mover script don t use absolute path in the SET LOG statement. 9

3.4 Upgrade J obs Upgrade jobs are used to run automated upgrade steps and monitor the progress of the upgrade. Creating the Upgrade Job 1. Select the Job Status tab on PeopleSoft Upgrade Assistant.

12 3.4 Upgrade J obs Upgrade jobs are used to run automated upgrade steps and monitor the progress of the upgrade. Creating the Upgrade Job 1. Select the Job Status tab on PeopleSoft Upgrade Assistant. 2. Select File, New Upgrade Job. The Create New Job File dialog box appears. 3. Enter a name for your Upgrade Job, for example, the name of your database. 4. Select Save. The Database Configuration dialog box appears: Note: If the update does not contain any copy from database step, values in the Source are not taken into account. Configuring and Editing Options 1. Open the Job 2. Select Options, Database Configuration. 3. PeopleSoft Upgrade Assistant displays the Database Configuration dialog box. 4. Modify your selected options, click OK. 5. The Upgrade Template reappears in Job Status view. 6. Save your template. 10

13 Directory Configuration In this screen PS_HOME, output and staging directories are configured. Products In this screen 11

3.5 Adding C ustom Documentation for Custom Chapters, Tasks and Steps If you have added Chapters, Tasks and/or Steps to a delivered upgrade template or a custom template, you may want to add

14 3.5 Adding C ustom Documentation for Custom Chapters, Tasks and Steps If you have added Chapters, Tasks and/or Steps to a delivered upgrade template or a custom template, you may want to add documentation for those items. To do this you will have to edit or copy existing.htm files which comprise the delivered upgrade documentation. The examples in this section uses the PeopleTools Only Upgrade template, which is available on Customer Connection. Similar changes can be made to delivered Application templates. Upgrade Documentation Overview Each Chapter within a PeopleSoft delivered template has a corresponding.htm file: Chapter 1 = Plan Your Upgrade Chapter 2 = Prepare Your Database Chapter 3 = Install The Software Chapter 4 = Apply PeopleTools Changes Chapter 5 = Complete Database Changes The following.htm files appear in the directory where you installed the upgrade documentation: Open ch01.htm in an html editor to view the html associated with this chapter. As you scroll through the file, you will see the documentation text associated with the chapter, tasks and steps. Notice how the items are tagged Chapter label: Chapter level names: Task level names: Step level names: <H1>Chapter 1</H1> <H2>Plan Your Upgrade</H2> <H3>Task Overview</H3> <H4>Review DB Orientation Property</H4> Also notice the use of <a name=>. When clicking on an item in the template, UA searches the.htm files for <a name="itemname"> (note that spaces and commas are stripped from the name.) To familiarize yourself with how the.htm file corresponds to a particular item in the UA template, open the template in UA and select View -> Documentation. As you click on an item in the template and see its corresponding documentation text appear, locate that item and text in the 12

corresponding.htm file. (You can have the.htm file open in an html editor while UA is accessing it.) Also notice the html used to draw tables and reference.jpg files.

15 corresponding.htm file. (You can have the.htm file open in an html editor while UA is accessing it.) Also notice the html used to draw tables and reference.jpg files. Adding documentation for Custom Steps, Tasks and Chapters. Below is a screen shot of a template, which contains a custom Chapter, a custom Task and Step within an existing Chapter, and a custom Step within an existing Task. In order to proceed with this example, add these items to your template and save the template. Be sure to add the Custom items in the exact locations as shown in this screen capture. You can set the step properties to Manual - Stop for the custom steps. Step First we will address Custom Step2 within the existing Task, 'Performing Script Modifications'. Using an html editor, open the.htm file which corresponds to the 'Apply PeopleTools Changes' chapter, ch04.htm. Search the file for the step name which follows the new Custom Step, 'Run a DBTSFIX Report': <a name="runadbtsfixreport"></a><h4>run a DBTSFIX Report</H4> We want to insert custom documentation above this step since our new custom step was added above this step. At a minimum you will need to add two lines: one to tag the step name, the other to contain its assocatiated text. You can copy the existing text and customize as appropriate: <a name="customstep2"></a><h4>custom Step2</H4> <P>This is documentation for a custom step under Performing Script Modifications. </P> Note that the space has been removed from the step name for the <a name=> tag. Since we are adding documentation for a step, the <H4> tag is used. Save the.htm file. To view the newly added custom documentation, click on this step within the UA template. You should see the following: 13

Task You will use this same approach to add custom documentation for Custom Task and Custom Step1. Edit the ch04.htm file and locate the task, 'Performing Script Modifications'.

16 Task You will use this same approach to add custom documentation for Custom Task and Custom Step1. Edit the ch04.htm file and locate the task, 'Performing Script Modifications'. The documentation for Custom Task and Custom Step1 will be added directly above this line since this is where they was added in the template: <a name="performingscriptmodifications"></a><h3>performing Script Modifications</H3> The easiest approach is to copy and paste the html associated with the task, Performing Script Modifications, and the step we added in the example above. You can then simply edit the names and text content: <a name="customtask"></a><h3>custom Task</H3> <p>this is the documentation for a custom task.</p> <a name="customstep1"></a><h4>custom Step1</H4> <p>this is documentation for a custom step under Custom Task. </P> Again, be sure to remove spaces and commas from the <a name=> tags. Save the.htm file. To view the newly added custom documentation, click on the task and step within the UA template. Verify that the custom documentation appears. 14

Chapter In order to add documentation for the Custom Chapter, a new.htm file will need to be created. The easiest way to do this is to make a copy of an existing.htm file. Make a copy of ch01.

In our example, you will need to modify the Chapter tags and associated text, delete the Task/Step tags and text which are not needed.

17 Chapter In order to add documentation for the Custom Chapter, a new.htm file will need to be created. The easiest way to do this is to make a copy of an existing.htm file. Make a copy of ch01.html and name it customchapter.htm. Open customchapter.htm in an html editor and edit it so that the text corresponds with the newly added chapter. In our example, you will need to modify the Chapter tags and associated text, delete the Task/Step tags and text which are not needed. The simplest file would appear like this: <html> <head> <META http-equiv="content-type" content="text/html; charset=iso "> <SCRIPT LANGUAGE="JavaScript" SRC="commonvars.js"></SCRIPT> <SCRIPT LANGUAGE="JavaScript" SRC="booklist.js"></SCRIPT> <LINK REL="StyleSheet" HREF="content.css"> <title>custom Chapter</title> 15

</head> <BODY onload="checkprint()" onfocus="afterprint()"> <P><A NAME="topofpage"></A> <a name="customchapter"></a><h1>custom Chapter</H1> <a name="firstheading"></a><h2>first Heading</H2> <p>custom

18 </head> <BODY onload="checkprint()" onfocus="afterprint()"> <P><A NAME="topofpage"></A> <a name="customchapter"></a><h1>custom Chapter</H1> <a name="firstheading"></a><h2>first Heading</H2> <p>custom chapter text. </P> </body> </html> Save the.htm file. To view the newly added custom documentation, click on the custom chapter within the UA template. Verify that the custom documentation appears: Adding Tables and Graphics The examples shown above are very simplistic in that only custom text is added. It is possible that you may want to add tables and graphics as part of your custom documentation. You can look in the delivered.htm files for sample code to use. Tables In UA, click on the task, 'Updating Statistics' located in the chapter, 'Prepare Your Database'. The following table appears in the documentation window: 16

19 To view the html associated with this task, open ch02.htm in an html editor. Search for '<a name="updatingstatistics">'. The following html block appears for this task: <table border=1 cellspacing=0 WIDTH=100%> <tr> <td WIDTH="20%" valign=top style='background:navy;padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLEHEAD><b>DB Orientation</b></P> </td> <td WIDTH="20%" valign=top style='background:navy; padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLEHEAD><b>Initial/MTP</b></P> </td> <td WIDTH="20%" valign=top style='background:navy; padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLEHEAD><b>Products</b></P> </td> <td WIDTH="20%" valign=top style='background:navy; padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLEHEAD><b>Platforms</b></P> </td> <td WIDTH="20%" valign=top style='background:navy; padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLEHEAD><b>Languages</b></P> </td> </tr> <tr> <td WIDTH="20%" valign=top style='padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLE>Target</P> </td> <td WIDTH="20%" valign=top style='padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLE>Both</P> </td> <td WIDTH="20%" valign=top style='padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLE>All</P> </td> <td WIDTH="20%" valign=top style='padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLE>All</P> 17

</td> <td WIDTH="20%" valign=top style='padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLE>All</P> </td> </tr> </table> You can copy this block of html code and modify it as needed to create your own table.

20 </td> <td WIDTH="20%" valign=top style='padding:6.0pt 2.0pt 6.0pt 2.0pt'> <P CLASS=TABLE>All</P> </td> </tr> </table> You can copy this block of html code and modify it as needed to create your own table. Graphics In UA, click on the step, 'Run the Initial Alter Audit, located in the chapter, 'Prepare Your Database', under task, 'Running Initial Audit Reports'. Scroll down to step 12 in the documentation window. Click on the 'Build dialog box' icon. The following graphic, ch02_0002.jpg, appears: 18

21 To view the html associated with this step, open ch02.htm in an html editor. Search for 'ch02_0002.jpg'. The following html block appears for this task: <P CLASS=EXHIBIT><SCRIPT LANGUAGE="JavaScript">PopupLogic('<img src=ch02_0002.jpg WIDTH=369 HEIGHT=350>','','popup')</SCRIPT> <P CLASS=CAPTION>Build dialog box</p> You can copy this block of html code and modify it to reference a custom.jpg file. Additional Resources Creating and testing custom documentation is very straightforward, as the above examples indicate. If your custom Chapters, Tasks and/or Steps require more complex documentation than the examples provided in this document, you may want to consult an HTML reference guide. 19

22 3.6 Advantag es with the automated process The installer need not be an expert technical user. The instructions are simple and easy to follow. The steps for loading the release are largely automatic which will decrease the occurrence of human errors. Reduced installation time In the tests conducted, on an average 70% reduction in installation time was achieved. The processing time for loading the project and run time of the data mover scripts remained the same as the manual approach. This approached greatly reduced the time taken by the installer to read and execute the instructions manually. In a typical test scenario, a large update was prepared with the following contents: Loading and Building of 10 Projects in Sequence. The Build options were different for each project. Loading of 8 Datamover Scripts Running 4 Data Migration SQL scripts Same target environments were used. In the manual approach, the installation was completed in 45 Mins In the automatic approach with upgrade assistant, installation completed in 12 mins. 20

23 References Upgrade Assistant PeopleBook Peoplesoft Customer Connection Knowledge-base Application Designer PeopleBook 21

Using Change Assistant for Migrations

Using Change Assistant for Migrations Dan Iverson 1 Agenda Goals for Migration Automation Change Assistant Functionality Environment Management Framework Change Packages Advanced Migrations 2 Target Audience