• No results found

PeopleTools 8.53: Change Assistant and Update Manager

N/A
N/A
Protected

Academic year: 2021

Share "PeopleTools 8.53: Change Assistant and Update Manager"

Copied!
208
0
0

Loading.... (view fulltext now)

Full text

(1)

PeopleTools 8.53: Change Assistant

and Update Manager

(2)

Copyright © 1988, 2013, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management

applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

(3)

Contents

Preface...vii

Understanding the PeopleSoft Online Help and PeopleBooks... vii

PeopleSoft Hosted Documentation... vii

Locally Installed Help...vii

Downloadable PeopleBook PDF Files...vii

Common Help Documentation... vii

Typographical Conventions...viii

ISO Country and Currency Codes...ix

Region and Industry Identifiers... ix

Access to Oracle Support...x

Documentation Accessibility...x

Using and Managing the PeopleSoft Online Help...x

Change Assistant and Update Manager Related Links... x

Contact Us...xi

Follow Us...xi

Part I: Configuring and Working With Change Assistant...13

Chapter 1: Getting Started with PeopleSoft Change Assistant...15

Getting Started with PeopleSoft Change Assistant...15

PeopleSoft Change Assistant Overview...15

Installation...16

Quick Start...17

Other Sources of Information... 18

Chapter 2: Understanding The Environment Management Framework and PeopleSoft Change Assistant... 19

Understanding The Environment Management Framework and PeopleSoft Change Assistant...19

Environment Management Framework...19

Change Assistant... 23

Software Update Process...24

Software Upgrade Process... 25

Source and Target Databases... 25

Chapter 3: Configuring and Running Environment Management Components... 29

Configuring and Running Environment Management Components...29

Configuring the Environment Management Hub...29

Running the Environment Management Hub... 30

Configuring an Environment Management Agent...33

Configuring Agents With a Secure PS_HOME...34

Running an Environment Management Agent...34

Monitoring Agent Status... 40

Running the Viewer...40

Configuring and Starting an Environment Management Agent on z/OS... 40

Integrating with Oracle Configuration Manager...41

Chapter 4: Configuring Change Assistant... 45

Configuring Change Assistant... 45

Setting Up Change Assistant... 45

(4)

Validating Change Assistant Settings...54

Chapter 5: Working With Change Assistant... 57

Working With Change Assistant...57

Understanding The Change Assistant Interface...57

Working With Change Assistant Menu Options...59

Working with Change Assistant Templates and Jobs... 64

Working with Steps... 66

Adding Filter Queries...71

Working with Embedded Documentation...77

Maintaining Change Assistant Directories...78

Running Change Assistant Job from the Command Line... 79

Part II: Using Change Assistant with Application Updates...81

Chapter 6: Discovering and Downloading Updates...83

Discovering and Downloading Updates...83

Discovering Updates Using My Oracle Support... 83

Downloading Updates From My Oracle Support...83

Chapter 7: Applying Updates... 85

Applying Updates...85

Reviewing the Updates Change Log... 85

Working with Templates... 86

Applying Updates To A Target Environment... 86

Part III: Working With Change Packages... 95

Chapter 8: Working with Change Packages... 97

Working with Change Packages...97

Understanding Change Packages... 97

Creating a Change Project... 98

Creating Change Packages... 102

Working With Change Package Automation... 105

Part IV: Using Change Assistant for Software Upgrades... 109

Chapter 9: Getting Started with Software Upgrades...111

Getting Started with Software Upgrades... 111

Understanding Change Assistant For Upgrades... 111

The Upgrade Process Using Change Assistant...111

Using Templates in Upgrades... 111

Chapter 10: Configuring Change Assistant for Upgrades...113

Configuring Change Assistant for Upgrades... 113

Downloading The Upgrade Template and Documentation...113

Importing and Opening a Template... 113

Confirming The PATH Variable...114

Setting the Documentation Directory...114

Configuring and Working With The Upgrade Environment...115

(5)

Using Data Conversion Utilities... 135

Understanding Data Conversion Utilities... 135

Using the Upgrade Driver Program...155

Part V: Comparing and Merging...161

Chapter 13: Comparing and Copying Managed Objects... 163

Comparing and Copying Managed Objects Introduction... 163

Comparing and Copying Managed Objects Overview... 163

Administering Projects... 163

Working With Project Administration Menu Options... 168

Comparing Definitions... 169

Copying Definitions... 170

Validating Projects...171

Chapter 14: Merging PeopleCode, SQL or XSLT...173

Merging PeopleCode, SQL or XSLT Introduction... 173

Understanding Merging PeopleCode, SQL, XSLT Programs...173

Beginning a New Merge Session...173

Using the Merge Interface...175

Appendix A: Working With Scripts... 181

Working With Scripts...181

Understanding Process, Scripts, and Syntax... 181

Running Scripts Outside of Change Assistant... 182

Appendix B: Modifying Step Properties and Parameters...185

Modifying Step Properties and Parameters... 185

Step Types... 185

Setting AE With Run Control Options for ADS Compare/Copy... 190

Step Parameters...191

Variables for All Step Types that Use Path... 193

Filter Query Variables... 194

Appendix C: Clearing Environment Management Framework Cache...197

Clearing Environment Management Framework Cache... 197

When to Clear Environment Management Framework Cache...197

Clearing EMF Cache... 198

Appendix D: Troubleshooting Change Assistant and EMF... 201

Troubleshooting Change Assistant and EMF...201

Peer Cannot Connect to the Hub...201

Servlet Request Processor Exception... 203

Error Initializing Agent...203

Distributed Object Manager Errors... 204

Cloned Databases Not Being Unique...204

Large SQL Scripts Fail on Microsoft SQL Server...204

Process Scheduler Logs Retrieved Using FTP Losing Formatting...204

(6)
(7)

Preface

Understanding the PeopleSoft Online Help and PeopleBooks

The PeopleSoft Online Help is a website that enables you to view all help content for PeopleSoft Applications and PeopleTools. The help provides standard navigation and full-text searching, as well as context-sensitive online help for PeopleSoft users.

PeopleSoft Hosted Documentation

You access the PeopleSoft Online Help on Oracle’s PeopleSoft Hosted Documentation website, which enables you to access the full help website and context-sensitive help directly from an Oracle hosted server. The hosted documentation is updated on a regular schedule, ensuring that you have access to the most current documentation. This reduces the need to view separate documentation posts for application maintenance on My Oracle Support, because that documentation is now incorporated into the hosted website content. The Hosted Documentation website is available in English only.

Locally Installed Help

If your organization has firewall restrictions that prevent you from using the Hosted Documentation website, you can install the PeopleSoft Online Help locally. If you install the help locally, you have more control over which documents users can access and you can include links to your organization’s custom documentation on help pages.

In addition, if you locally install the PeopleSoft Online Help, you can use any search engine for full-text searching. Your installation documentation includes instructions about how to set up Oracle Secure Enterprise Search for full-text searching.

See PeopleTools 8.53 Installation for your database platform, ”Installing PeopleSoft Online Help.” If you do not use Secure Enterprise Search, see the documentation for your chosen search engine.

Note: Before users can access the search engine on a locally installed help website, you must enable the Search portlet and link. Click the Help link on any page in the PeopleSoft Online Help for instructions.

Downloadable PeopleBook PDF Files

You can access downloadable PDF versions of the help content in the traditional PeopleBook format. The content in the PeopleBook PDFs is the same as the content in the PeopleSoft Online Help, but it has a different structure and it does not include the interactive navigation features that are available in the online help.

Common Help Documentation

Common help documentation contains information that applies to multiple applications. The two main types of common help are:

(8)

• Using PeopleSoft Applications

Most product lines provide a set of application fundamentals help topics that discuss essential information about the setup and design of your system. This information applies to many or all applications in the PeopleSoft product line. Whether you are implementing a single application, some combination of applications within the product line, or the entire product line, you should be familiar with the contents of the appropriate application fundamentals help. They provide the starting points for fundamental implementation tasks.

In addition, the PeopleTools: PeopleSoft Applications User's Guide introduces you to the various elements of the PeopleSoft Pure Internet Architecture. It also explains how to use the navigational hierarchy, components, and pages to perform basic functions as you navigate through the system. While your application or implementation may differ, the topics in this user’s guide provide general information about using PeopleSoft Applications.

Typographical Conventions

The following table describes the typographical conventions that are used in the online help.

Typographical Convention Description

Bold Highlights PeopleCode function names, business

function names, event names, system function names, method names, language constructs, and PeopleCode reserved words that must be included literally in the function call.

Italics Highlights field values, emphasis, and PeopleSoft or

other book-length publication titles. In PeopleCode syntax, italic items are placeholders for arguments that your program must supply.

Italics also highlight references to words or letters, as in the following example: Enter the letter O.

Key+Key Indicates a key combination action. For example, a plus sign (+) between keys means that you must hold down the first key while you press the second key. For Alt+W, hold down the Alt key while you press the W key.

Monospace font Highlights a PeopleCode program or other code example.

. . . (ellipses) Indicate that the preceding item or series can be repeated any number of times in PeopleCode syntax.

(9)

Typographical Convention Description

& (ampersand) When placed before a parameter in PeopleCode syntax, an ampersand indicates that the parameter is an already instantiated object.

Ampersands also precede all PeopleCode variables.

⇒ This continuation character has been inserted at the end of a line of code that has been wrapped at the page margin. The code should be viewed or entered as a single, continuous line of code without the continuation character.

ISO Country and Currency Codes

PeopleSoft Online Help topics use International Organization for Standardization (ISO) country and currency codes to identify country-specific information and monetary amounts.

ISO country codes may appear as country identifiers, and ISO currency codes may appear as currency identifiers in your PeopleSoft documentation. Reference to an ISO country code in your documentation does not imply that your application includes every ISO country code. The following example is a country-specific heading: "(FRA) Hiring an Employee."

The PeopleSoft Currency Code table (CURRENCY_CD_TBL) contains sample currency code data. The Currency Code table is based on ISO Standard 4217, "Codes for the representation of currencies," and also relies on ISO country codes in the Country table (COUNTRY_TBL). The navigation to the pages where you maintain currency code and country information depends on which PeopleSoft applications you are using. To access the pages for maintaining the Currency Code and Country tables, consult the online help for your applications for more information.

Region and Industry Identifiers

Information that applies only to a specific region or industry is preceded by a standard identifier in parentheses. This identifier typically appears at the beginning of a section heading, but it may also appear at the beginning of a note or other text.

Example of a region-specific heading: "(Latin America) Setting Up Depreciation"

Region Identifiers

Regions are identified by the region name. The following region identifiers may appear in the PeopleSoft Online Help:

• Asia Pacific • Europe • Latin America • North America

(10)

Industry Identifiers

Industries are identified by the industry name or by an abbreviation for that industry. The following industry identifiers may appear in the PeopleSoft Online Help:

• USF (U.S. Federal)

• E&G (Education and Government)

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/ lookup?ctx=acc&id=trs if you are hearing impaired.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Using and Managing the PeopleSoft Online Help

Click the Help link in the universal navigation header of any page in the PeopleSoft Online Help to see information on the following topics:

• What’s new in the PeopleSoft Online Help. • PeopleSoft Online Help acessibility.

• Accessing, navigating, and searching the PeopleSoft Online Help. • Managing a locally installed PeopleSoft Online Help website.

Change Assistant and Update Manager Related Links

Oracle's PeopleSoft PeopleTools 8.53 Documentation Home Page [ID 1494462.1] PeopleSoft Information Portal on Oracle.com

(11)

Contact Us

Send us your suggestions Please include release numbers for the PeopleTools and applications that you are using.

Follow Us

Get the latest PeopleSoft updates on Facebook. Follow PeopleSoft on Twitter@PeopleSoft_Info.

(12)
(13)

Configuring and Working With Change

Assistant

(14)
(15)

Getting Started with PeopleSoft Change

Assistant

Getting Started with PeopleSoft Change Assistant

These topics provide a high-level overview of Change Assistant and describe:

• What needs to be in place before you can configure and use PeopleSoft Change Assistant.

• A 'quick start' list to help you understand the technology and get you up and running with Change Assistant.

• Where you can look for other sources of information.

PeopleSoft Change Assistant Overview

Oracle's PeopleSoft Change Assistant is a standalone, Windows based, Java program that expedites the process of applying a PeopleSoft software update or performing an upgrade by automating most of the steps. Change Assistant utilizes all of the elements included in the Environment Management Framework to monitor information specific to your PeopleSoft implementation and deploy the necessary application updates throughout your system.

See the PeopleSoft Update Manager home page (Doc ID 1464619.1) on My Oracle Support for more information.

PeopleSoft Update Manager (PUM) is a lifecycle management tool and maintenance delivery mechanism for application updates that will be implemented as a component of Change Assistant in the future. When PUM is made available for application updates, this book will be revised to include details on how to use this new tool.

Change Assistant provides these main benefits:

• Automates many of the steps in an upgrade or update process.

• Provides a clear step-by-step definition of the process for applying maintenance or performing an upgrade. Whether the process is automated or manual, as long as you complete each step, you will successfully apply the application maintenance or perform the upgrade.

• Provides in-line documentation for each of the steps in the process. The Environment Management Framework performs these key tasks:

• Crawls local drives and directory paths to discover and validate the components associated with a given PeopleSoft environment. Change Assistant can selectively retrieve the environment information to create CA environments for use by CA jobs and other activities.

(16)

• Facilitate the deployment of files to various components in the PeopleSoft environment.

Related Links

Environment Management Framework

Change Assistant Actions

Change Assistant supports the following actions:

Apply Updates Apply Updates is used to apply updates and fixes downloaded from My Oracle Support. Updates are downloaded as change packages.

Apply Updates can be used with any change packages.

Update Manager Reserved for future use.

Application Upgrade Application Upgrade is used to perform upgrade to a new application release, which typically includes a PeopleTools upgrade as well. Full application upgrades are delivered with detailed templates and documentation tailored to your specific upgrade path.

Upgrade PeopleTools Upgrade PeopleTools is used to do a PeopleTools only upgrade.

Compare/Copy Managed Objects or

Merge Select Object Types Provides the ability to copy and compare Managed Objects,ADS projects and Application Designer projects in Change Assistant. You also have the ability to view and merge PeopleCode, SQL and XSLT. This option uses project Administration.

Create or Modify Templates Change Assistant templates are composites of all the possible steps that apply to an update or upgrade. The templates are delivered as part of the change package. Once you select a change package, the template is loaded into the Change Assistant internal storage. You can edit the template or add additional chapters, tasks and steps, if needed.

Installation

Prior to using Change Assistant the following items must be in place:

(17)

Quick Start

The following items provide a quick start reference for the main steps and concepts related to the implementation and use of Change Assistant. This list is designed to help get you up and running with Change Assistant as well as to help you to understand the main functions for which Change Assistant was designed.

Application Updates

The steps appear in the logical order that you would perform them, and the links point to the location where the information for a specific item exists within this PeopleBook.

Step Reference

1. Configure and start the PSEMHUB within your

PeopleSoft environment. See Configuring the Environment Management Hub. 2. Configure and start the PSEMAgent on every server

within your PeopleSoft environment. See Configuring an Environment Management Agent. 3. Install and configure Change Assistant, specifying

the proper directories for file download and storage, and ensuring it can connect to the PSEMHUB.

See Setting Up Change Assistant.

4. Use My Oracle Support (MOS) to identify the bundles and updates that need to be applied to your specific environment.

See Discovering Updates Using My Oracle Support.

5. Download the required bundles and updates. See Downloading Updates From My Oracle Support. 6. Use Change Assistant to apply the bundles and

updates. See Applying Updates To A Target Environment.

Application Upgrade

The steps appear in the logical order that you would perform them, and the links point to the location where the information for a specific item exists within this PeopleBook.

Step Reference

1. Download the Change Assistant template and

documentation. See Downloading The Upgrade Template andDocumentation 2. Import the template into Change Assistant. See Importing and Opening a Template

3. Configure your upgrade environment. See Configuring and Working With The Upgrade Environment

4. Create an upgrade job. See Creating Upgrade Jobs

5. Set the documentation directory. See Setting the Documentation Directory 6. Start the upgrade process. See Running the Upgrade Job

(18)

Other Sources of Information

This section provides information to consider before you begin to use PeopleSoft Change Assistant. In addition to implementation considerations presented in this section, take advantage of all PeopleSoft sources of information, including the installation guides, release notes, PeopleBooks, and training courses and your PeopleSoft application upgrade documentation.

Related Links

PeopleTools 8.53: PeopleSoft Application Designer Developer's Guide

PeopleTools 8.53: PeopleSoft Application Designer Lifecycle Management Guide PeopleTools 8.53: PeopleSoft Change Impact Analyzer

(19)

Understanding The Environment

Management Framework and PeopleSoft

Change Assistant

Understanding The Environment Management Framework and PeopleSoft

Change Assistant

These topics provide overview information regarding: • Environment Management Framework

• Change Assistant • Software update process • Software upgrade process • Source and target databases

Environment Management Framework

Environment management framework-Environment Management Framework (EMF) is a collection of software elements that gathers and publishes PeopleSoft installation, configuration, and update information. It enables you to identify and view data about PeopleSoft environments. You can use EMF to obtain a snapshot of configuration and setup information about the file servers, the web servers, the application servers, the individual hosts, and the PeopleSoft Process Scheduler servers that comprise your PeopleSoft system. EMF also provides a vehicle to carry out commands remotely on different machines on the network, directed by Change Assistant, which uses EMF to apply updates to PeopleSoft installations and configurations.

EMF consists of the following core elements:

• The Environment Management hub (PSEMHUB) • Environment Management Agent (PSEMAgent) • The Environment Management viewer

Environment Management Hub

The Environment Management hub is a web application that is installed with the PeopleSoft Internet Architecture and portal. It is started along with the rest of the web applications when the user boots the web server. The hub is the broker for all communication between peers.

The Environment Management hub handles: • Peer registration.

(20)

The hub registers all of the information that is published by the agents. It also assigns a unique peer ID for every peer that engages in a dialogue with the hub.

• Maintenance of configuration information.

The hub handles updates to configuration information, the correlation of information, and the grouping into environments based on the information that is published by the agents.

• Agent health monitoring.

The hub keeps track of the state or "health" information of the managed components. It shows whether a peer is still running remotely or not.

• Message brokering.

The hub services message service requests and responses from peers. The messages can be delivered to the respective peers even if the peers are not currently running. They are picked up the next time the peers “call in” to the hub. Typical messages include requests to deploy files to managed servers. It's recommended that the managed server agents be left up and running at all times to listen for messages from the hub. This is critical when applying software updates.

The Environment Management hub is installed as part of the standard PeopleSoft Internet Architecture installation. It supports both single-server and multi-server installations. The Environment Management hub is deployed in the J2EE containers as web application modules. They can be managed like any of the standard web application modules.

The following Environment Management hub directories are created on the J2EE container for the hub: • With Oracle WebLogic:

PIA_HOME\webserv\domain\applications\peoplesoft\PSEMHUB • With IBM WebSphere:

PIA_HOME\webserv\server\installedApps\domainNodeCell/domain.ear\PSEMHUB.war The required JAR files for the Environment Management hub are installed in the WEB-INF\lib subdirectory.

Agents

An Environment Management agent is a Java executable installed on the servers in a PeopleSoft environment, such as application servers, Process Scheduler servers, web servers, and so on. The Environment Management agent initiates communication with the hub and is assigned a unique peer ID. This ID persists and is reused for later connections by the agent.

The primary function of the agent is crawling the managed servers to identify manageable components. The metadata of the search results of the crawling are saved to the local hard disk. On startup, if the agent

(21)

database with which the application server or Process Scheduler communicates. The agent publishes this information to the hub upon initial connection and upon a recrawl or revalidate.

The agent also determines heartbeat and command execution. On every heartbeat, the agent pings the server to determine whether it has any pending messages. If there are pending messages for the agent, the messages are retrieved from the hub and carried out locally on the agent machine.

PSEMAgent:

• uses HTTP to connect to PSEMHub.

• reads files from PS_HOME, PS_APP_HOME, and PS_CFG_HOME. • writes files to PS_HOME and PS_APP_HOME.

• runs psae.

Note: You install the Environment Management agent by running the PeopleTools CD installation. The Environment Management agent is installed in the PSEMAgent directory in your PS_HOME with the server installation. If additional components are installed in the same PS_HOME location, the installer warns you that existing software may be overwritten.

Note: Multiple EM Agents can be run, but they must be run using a different agentport. See PeopleTools installation documentation for your database platform.

Viewer

The Environment Management viewer is a command-line tool enabling you to view data stored on the Environment Management hub. This data is saved in an XML file that contains data that is specific to individual customer sites—such as, information about environments, software updates, hosts, file servers, application servers, PeopleSoft Process Scheduler servers, and web servers. Users can view this static data in HTML.

The Environment Management viewer may only be executed on PeopleSoft web servers, from its

installed location in PS_HOME\PSEMViewer. You don't have to carry out any additional installation steps to install the viewer.

EMF Terminology

The following terms relate to Environment Management:

Manageable component A component that can be individually managed from the Environment Management hub. A manageable component for PeopleSoft is typically a file server, an application server, a web server, individual hosts, or a PeopleSoft Process Scheduler server.

Peer A manageable component that is involved in a transaction with

one or more peers in the Environment Management by using the hub as the intermediary. A peer may also be responsible for delegation of management responsibility to a collection of manageable components. Examples of peers are agents, Change Assistant, and the Environment Management viewer.

(22)

Heartbeat “I am alive messages” sent by every peer to the hub. The default interval is configurable. On every heartbeat, the peer pings the server to see if it has any pending messages. If it does, the messages are taken and carried out.

Environment All of the manageable components in the enterprise that share the same globally unique identifier (GUID) in the database. There can be more than one instances of a type of managed component in an environment. For example, development environments can contain several application servers, Process Schedulers, and web servers.

GUID Uniquely identifies a particular PeopleSoft system. PeopleSoft

assigns a unique value, referred to as a GUID, to each PeopleSoft application installation. This value can't be

customized. When an Environment Management agent notifies the hub that it has found a manageable component belonging to an environment, if the GUID of the environment is not recognized, the hub creates a new environment representation.

Crawling The process of scanning the hard disk for known PeopleSoft patterns for manageable components. The hub has a set of configurable parameters by which the recrawl intervals can be altered. Based on this, the hub can issue a recrawl command to the agents to discover information about newly installed or changed configurations.

Note: During crawling, the Environment Management Framework uses the psserver property in the peopletools. properties file within each PS_HOME installation to determine the type of server(s) installed. For example, APP is application server, BATCH is Process Scheduler, DB is database server, WEB is web server, and FILE is file server.

Note: Recrawling includes revalidating.

Revalidate The process of checking whether the last set of managed components that have been discovered is still valid. The agent iterates through the list of components that have been discovered from the last recrawl. It then checks whether the current set of configuration parameters for the managed components have changed the management scope for the component. If so, the information is updated. If the new set of

(23)

Change Assistant

Change Assistant is a standalone application that enables you to assemble and organize the steps necessary to apply updates and fixes for PeopleSoft application maintenance updates as well as

performing upgrades. Change Assistant automates many of the steps, but will prompt you and guide you through any manual steps with embedded documentation.

You use Change Assistant for these situations:

• Applying maintenance packs, bundles, and individual updates related to PeopleSoft application maintenance. Maintenance packs, bundles, and updates all come in the form of change packages. • Performing upgrades, which includes PeopleTools-only upgrades, PeopleSoft application-only

upgrades, and combined PeopleTools and application upgrades.

Note: You do not use Change Assistant to apply PeopleTools patches.

Note: You use Change Assistant to apply updates that have a .ZIP extension. You do not use Change Assistant to apply updates that have an .EXE extension.

In order to perform reliable and accurate updates, Change Assistant gathers all the necessary information including the change log from the Environment Management hub and uploads it to Oracle. With the environment data available, Oracle can determine what updates apply to your environment.

You can obtain a list of all updates that have not been applied for a given application environment including all prerequisites. You can then download a set of change packages associated with the update IDs and install the patches and fixes with minimal effort.

Understanding Change Assistant Versions

You can use a newer version of Change Assistant than the version of PeopleTools you are using. However, the environment management agents and hub must be at the same version level as Change Assistant.

For example, your PeopleTools version could be at 8.53.09, but you can run Change Assistant at the 8.53.14 level as long as the agents and hub are also at the 8.53.14 level.

Maintaining Change Assistant

Periodically, Oracle provides patches for PeopleTools that supply fixes to critical defects. With each PeopleTools patch version, Oracle provides the following updates in executable format:

Executable Description

version.exe

For example, 85014.exe

Contains all current fixes to the entire PeopleTools product, including those fixes to the software update technology, which includes Change Assistant and all environment management elements (agents, hub, and so on).

(24)

Executable Description

version-PSCA.exe

For example, 85014-PSCA.exe

Contains only the current fixes to apply to the software update technology, which includes Change Assistant and all environment management elements (agents, hub, and so on).

The software update technology runs independently from the rest of PeopleTools.

Note: If you install a complete PeopleTools patch, you do not need to apply the -PSCA patch individually. Apply the -PSCA patch individually only if you are interested in just the fixes for the software update tools and not the fixes for the entire PeopleTools product.

The -PSCA patch enables you to apply only the latest fixes to Change Assistant and the environment management framework without applying the latest full PeopleTools patch. By doing so, you can avoid the regression testing that typically occurs after applying a full PeopleTools patch.

Software Update Process

The software update process refers to applying updates to your current PeopleSoft application. Software update tools include:

• Environment Management Framework Used to collect environment information. See Running the Environment Management Hub • Change Assistant

Used to apply change packages to the environment. See Applying Updates To A Target Environment • Change Packager

Creates the change package in Change Assistant.

Note: Change Assistant is not used to apply maintenance builds or patches to PeopleTools releases.

Software Update Process

The software update process refers to applying change packages, bundles, and maintenance packs to your current PeopleSoft application. For example, PeopleSoft application development teams periodically

(25)

Step Description

1 Install and configure Change Assistant and the

Environment Management components.

2 Use My Oracle Support (MOS) to search for updates.

3 Download the Change Packages from MOS.

4 After you have downloaded the change packages,

you can then apply them in a batch or individually. If prerequisites or post-requisites are required, they will be included in the list as well.

Software Upgrade Process

The software upgrade process refers to moving from one release level to a newer release. This typically involves installing a new version of PeopleTools and a new version of an existing PeopleSoft application. This process uses Change Assistant, and the Environment Management Framework 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 Target Databases

In various places within this PeopleBook, as well as any PeopleSoft documentation related to upgrades or database compares, the terms source and target are used. Knowing the meanings of these terms helps you to understand the context of a description or step.

During 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. The definitions of these terms are:

source database The source database is the database from which the new changes are coming.

target database The target database is the database to which you are moving the new changes.

Note: Depending on whether you are performing an upgrade or update, and the stage within the process you are, these terms are relative and can refer to different databases.

For example, in a typical upgrade, you install the new version to a demonstration database, referred to as Demo. Then, you create a copy of your production database, referred to as Copy of Production. You then copy the modified definitions from the Demo database into the Copy of Production. In this context, your Demo database is your source and the Copy of Production is the target. Likewise, after you complete the initial copy and perform the required compares and tests, you begin a Move to Production pass. In this pass you take the Copy of Production database and incorporate the modified definitions into the Production database. In this context, the Copy of Production is your source and the Production database is your target.

(26)

When applying an update using the "Apply with Database Compare/Copy" option, the source database is the Demo database where the update (change package) has already been applied.

Change Assistant Environments and Terminology

Depending on the action to perform, the environment must be configured. Each environment will include: • Database name

• Database type • Unicode

• User Ids and passwords • SQL query executable • Products

Products are selected for the target database only. The source database will inherit these values from the target.

• Languages

Languages are selected for the target database only. The source database will inherit these values from the target.

• Paths to the current environment home directories. • PS_HOME

• PS_APP_HOME • PS_CUST_HOME

• For application upgrades only , the target database will also include paths to the old environment home directories.

Paths to Home Directories

The order by which the PeopleTools runtime will pick up objects from the file system is as follows: 1. PS_CUST_HOME

2. PS_APP_HOME 3. PS_HOME

(27)

Action Databases and Paths Used

Application Upgrade Target database with path for current environment and path for old release.

Source database is the dedicated demo database for your application.

(Optional) Copy of current demo database with path for current environment.

(Optional) Production database with path for current environment.

Upgrade PeopleTools Target database with path for current environment. Copy/Compare Managed Objects Target database with path for current environment.

(28)
(29)

Configuring and Running Environment

Management Components

Configuring and Running Environment Management Components

These topics discuss how to:

• Configure the Environment Management hub. • Run the Environment Management hub. • Configure an Environment Management agent. • Run an Environment Management agent. • Run the viewer.

• Handle common error conditions.

• Configure and start an Environment Agent on z/OS.

Configuring the Environment Management Hub

Before you can run the Environment Management hub, you must ensure that it's properly configured. The hub issues automatic recrawl and revalidate commands to the agents, and it can be configured to accept automatic updates from Change Assistant. You configure the hub by setting appropriate parameters in its configuration file, which is located as follows:

• WebLogic:

PIA_HOME\webserv\domain\applications\peoplesoft\PSEMHUB\envmetadata\config \configuration.properties

• WebSphere:

PIA_HOME\webserv\server\installedApps\domainNodeCell/domain.ear\PSEMHUB.war/ envmetadata/config\configuration.properties

(30)

Configuration Parameter Description Default Value

recrawlinterval The interval, in hours, between two successive recrawl commands that have been issued to a peer. The server issues recrawl commands only to agents that are connected to the hub and have no pending messages in the queue. This configuration parameter is ignored by the agent.

24 hours

Note: A 0 value means that it will not recrawl.

Recrawling includes a revalidating.

revalidateinterval The maximum time, in hours, between two successive automatic revalidates that the hub issues.

6 hours

Note: A 0 value means that it will not revalidate.

Hub Security Considerations

Environment Management framework does not support HTTPS connections. The agent and hub communicate using standard HTTP only.

On WebSphere, or for a single server configuration on WebLogic, PSEMHUB is a web application running within PIA. If PIA is configured to be accessed using HTTPS, you need to configure a separate server instance for the hub to enable the HTTP connections between agents and hub.

Configuring Hub Logging

The Environment Management hub logs are located as follows:

• WebLogic: PIA_HOME\webserv\domain\applications\peoplesoft\PSEMHUB\envmetadata\logs • WebSphere: PIA_HOME\webserv\ps1\installedApps\<domain>NodeCell/<domain>.ear

\PSEMHUB.war/envmetadata/logs

Edit the ...\PSEMHUB\envmetadata\config\Logconfig.properties to configure logging for the hub. The following two Logconfig.properties parameters, which determine the maximum size of each log file, and the amount of log files rolled over, can be changed:

• log4j.appender.R.MaxFileSize=1024KB • log4j.appender.R.MaxBackupIndex=1"

Running the Environment Management Hub

(31)

Running the Hub on a Single Server

On a single server, the PSEMHUB starts within PIA, so use the command you use for your web server to start PIA.

Running the Hub on Multiple Servers

Environment Management also supports multi-server installs. However, the Environment Management hub does not support clustering. The Environment Management hub persists metadata into the file system on the J2EE container. This is not replicated in a clustered environment. You experience erroneous behavior when you attempt to run the Environment Management hub in a clustered environment.

The Environment Management hub deals with large binary files that Change Assistant sends to the agents by using the hub as the intermediary dispatcher. This can create significant overhead to a production system that is running on a multi-server clustered environment. Therefore, PSEMHUB must always run on separate servers dedicated to the Environment Management hub requests.

Starting PSEMHUB on Multiple Servers on WebLogic

In a multiple server configuration, the PSEMHUB server listens on port 8081, by default. Use the following steps to start the WebLogic hub:

1. Configure the Environment Management hub to run on a server that is different from the PeopleSoft Internet Architecture servers.

2. Configure the reverse proxy to redirect any network traffic with a uniform resource identifier (URI) of PSEMHUB to the server running the Environment Management hub.

On the machine from which the RPS application runs, access the HttpProxyServlet folder. Select PSEMHUBHttpProxyServlet and click the Init Params tab. Replace WebLogicHost , WebLogicPort with the host and port from which your PSEMHUB server listens.

Note: Save your new configuration.

Use the following commands in sequence to start the Environment Management hub in a multi-server installation:

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

...\StartManagedWebLogic.cmd PSEMHUB

Then use the following URL to access PSEMHUB: http://RPS host:RPS port/PSEMHUB/hub.

Note: For a single server install using a reverse proxy, this additional step needs to be performed in order for the Environment Management hub to be able to process the PSEMHUB requests. You need to edit: PIA_HOME\webserv\domain\applications\HttpProxyServlet\WEB-INF\web.xml. In the PSEMHUBHttpProxyServlet section, change the default port from 8001 to 80.

The following is a sample configuration: - <servlet> <servlet-name>PSEMHUBHttpProxyServlet</servlet-name> <servlet-class>weblogic.servlet.proxy.HttpProxyServlet</servlet-class> - <init-param> <param-name>WebLogicHost</param-name> <param-value>localhost</param-value>

(32)

- <init-param>

<param-name>WebLogicPort</param-name> <param-value>80</param-value>

</init-param> </servlet>

Start the WebSphere Hub on Multiple Servers

If you are using multiple servers, then you need to dedicate one of them to handle PSEMHUB requests. All PSEMHUB requests should be routed to the same server instance. The following steps show the configuration changes that are required for this purpose:

1. Edit your reverse proxy's plug-in configuration file (plugin-cfg.xml) then make sure that only one server is dedicated to PSEMHUB.

2. Remove this line from all other servers: <Uri AffinityCookie="JSESSIONID"

AffinityURLIdentifier="jsessionid" Name="/PSEMHUB/*" />. The server you chose for PSEMHUB should only service PSEMHUB requests so that it can run independently and can be shut down without affecting the rest of the system.

3. Restart the reverse proxy using : IBM_proxy_base_directory\bin\apachectl restart.

4. Restart all the servers. For Windows, the directory is: WebSphere_Appserver_directory\bin \startServer.bat serverX. For UNIX, the directory is: WebSphere_Appserver_directory/bin/ startServer.sh serverX.

5. Use the following URL to access PSEMHUB http://reverse_proxy_host:reverse_proxy_port/ PSEMHUB/hub.

The reverse proxy's listen port is defined in IBM_reverse_proxy_base_directory\conf\httpd.conf.

Stopping the PSEMHUB on Multiple Servers on WebLogic

In a multiple server environment, target the server which is dedicated to PSEMHUB then execute

PIA_HOME\webserv\domain\stopWebLogic.cmd PSEMHUB on Windows and PS_HOME/ webserv/domain/stopWebLogic.sh PSEMHUB on UNIX. This will only stop the server servicing PSEMHUB requests. The other servers will still be up processing PIA requests.

The following is a sample XML configuration file for the WebLogic multi-server installation: 1.1 Sample XML configuration file for WebLogic Multiserver installation <UriGroup Name="default_host_server1_st-lnx06_Cluster_URIs">

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/*" /> <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid"

Name="/PSIGW/*" />

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/PSINTERLINKS/*" />

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/PSOL/*" />

(33)

Name="/PSEMHUB/*" /> </UriGroup>

Stopping PSEMHUB on Multiple Servers on WebSphere

In a multiple server environment, target the server which is dedicated to PSEMHUB then execute WebSphere_Appserver_directory\bin\stopServer.bat serverX on Windows and

WebSphere_Appserver_directory/bin/stopServer.sh serverX on UNIX. This will only stop the server servicing PSEMHUB requests. The other servers will still be up processing PIA requests

Configuring an Environment Management Agent

Before you can run an environment management agent, you must ensure that it's properly configured. You configure the agent by making appropriate entries in its configuration.properties file, which is located under:

PS_HOME\PSEMAgent\envmetadata\config

The following table describes the configuration.properties parameters for the Environment Management agent:

Configuration Parameter Description Default Value

hubURL The URL that contains the host name and the port number of the machine on which the Environment Management hub is running (inside a J2EE container).

http://hostname:port/PSEMHUB/ hub.

agentport A port that the agent uses for internal life cycle management. 5283. pinginterval The interval, in milliseconds,

between two successive attempts that the peer makes to contact the hub. All peers that access this configuration file have the same ping interval.

10000 (in milliseconds for the heartbeat)

Note: The minimum required pinginterval value is 1000. windowsdrivestocrawl On Microsoft Windows, the set of

local drives or directory paths where PS_HOME, PS_CFG_HOME and PIA_HOME are located. Separate the drive letters or directory paths with spaces and a pipe symbol ( | ).

c: | d:

Note: Do not leave a trailing '/' or '\' character at the end of the path.

unixdrivestocrawl On UNIX, the set of local drives or directory paths where PS_HOME, PS_CFG_HOME, and PIA_HOME are located.

$HOME

Note: Do not leave a trailing '/' or '\' character at the end of the path.

(34)

Configuration Parameter Description Default Value

chunksize Only applicable to large files, which may be chunked when sent. The chunksize represents the maximum size in bytes of each chunk.

1048576 (1 MB) (used for large file transfers).

Configuring Agent Logging

The Environment Management agent's logs are located under PS_HOME\PSEMAgent\envmetadata\logs. Edit PS_HOME\PSEMAgent\envmetadata\config\Logconfig.properties to configure the logging for the agent.

The following parameters determine the maximum size of each log file and the amount of log files rolled over. You can change the values of these parameters.

• log4j.appender.R.MaxFileSize=1024KB • log4j.appender.R.MaxBackupIndex=1"

Configuring Agents With a Secure PS_HOME

Change Assistant deploys the updates to the PS_HOME using the agents running on the managed servers. Therefore, the agent running on a server should have write access to the PS_HOME and its subdirectories.

Note: While specifying the crawl path in configuration.properties, make sure that the decoupled configuration home (PS_CFG_HOME) is also included.

Related Links

"Working with the Default PS_CFG_HOME (PeopleTools 8.53: System and Server Administration)" "Securing PS_HOME on UNIX (PeopleTools 8.53: System and Server Administration)"

"Securing PS_HOME on Windows (PeopleTools 8.53: System and Server Administration)"

Running an Environment Management Agent

This section discusses how to: • Run an agent.

• Start an agent automatically in Windows.

(35)

• On Microsoft Windows, run PS_HOME\PSEMAgent\StartAgent.bat.

Note: If you want the agent to start automatically when the machine starts, use the Microsoft Windows service that's delivered as part of PeopleTools. Or, you can add the script to the startup applications.

• On UNIX, run PS_HOME/PSEMAgent/StartAgent.sh.

Note: If you want the Environment Management agent to start automatically on UNIX when the machine starts, add StartAgent.sh to the login/boot scripts.

The first time an agent starts, it crawls the machine to locate PeopleSoft elements on that machine. The results of searching the hard disk are saved in the envmetadata\data\search-results.xml file.

Note: When 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 events ("sending pulse") in the command prompt as the agent communicates with the hub. By default these "pulses" are every 10 seconds, except when environment information is being uploaded to the hub. You can configure the agent to run in the background using the provided Windows service, and on UNIX by using the

nohup command. These options are documented in other sections of this PeopleBook.

Note: Only one Environment Management agent can be started per machine. If an agent is already started, you may receive error messages indicating that the agent cannot be started because there is already one running on the machine.

See Starting an Agent in the Background on UNIX.

See Starting an Agent With PSEMAgent Windows Service.

Starting the Agent on a Secure PS_HOME

On Microsoft Windows:

1. Create a new shortcut from the desktop (right-click, New, Shortcut). 2. In the Type the location of the item enter:

<PS_HOME>\PSEMAgent\StartAgent.bat -u :<domainname>\<username>

For example:

c:\ptinstalls\pt851\PSEMAgent\StartAgent.bat -u :bigcompany.com\tsawyer

Where the user specified has write access to PS_HOME.

Note: When you run <PS_HOME>\PSEMAgent\StartAgent.bat -u :<domainname>\<username>, the %TEMP% directory is used. Both the user that runs the command and the "runas" user need write/ execute access to the %TEMP% directory.

3. Click Next, and enter a name for the shortcut. 4. Use this shortcut to start the agent.

(36)

1. Log in as the user who has write access to the PS_HOME. 2. PS_HOME/PSEMAgent/StartAgent.sh.

See "Securing PS_HOME on UNIX (PeopleTools 8.53: System and Server Administration)".

Stopping the Agent

Use one of these scripts to stop the Environment Management agent: • On Microsoft Windows, run PS_HOME\PSEMAgent\StopAgent.bat. • On UNIX, run PS_HOME/PSEMAgent/StopAgent.sh.

Recrawl

If you install new software components, the running Environment Management agent doesn't

automatically detect them. This is because, to improve performance, the agent doesn't crawl every time it starts up. Instead it crawls only if the search-results.xml file does not exist.

You can force a recrawl and make the new components manageable by reissuing the StartAgent command with the recrawl option:

1. Open a new command line window.

2. Change directories to PS_HOME\PSEMAgent. 3. Issue the following command:

StartAgent recrawl

This forces a recrawl and creates a new search-results.xml file. If an agent is already running, it publishes the results to the hub.

If the running Environment Management agent is connected to the hub constantly, the recrawl interval occurs every 24 hours by default. If the agent has not been connected to the hub for a few days, the hub requests the agent to recrawl when the agent contacts the hub the next time.

Note: Recrawling includes revalidating.

Note: The recrawl process assumes the Environment 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 make sure the agent is running.

(37)

• RemoteException while connecting to server - retrying attempt 1 • RemoteException while connecting to server - retrying attempt 2 • RemoteException while connecting to server - retrying attempt 3

Once the Environment Management hub is back up, the agent will successfully connect. There's no need to stop and restart the agent.

Note: If you are performing a recrawl, you don't need to separately revalidate.

Command-Line Arguments for the Agent

You can run these command-line arguments with the startAgent.bat (or startAgent.sh) script.

Argument Description Sample Output

version Returns the version of the agent. Version:8.45 Build Number: 109 shutdown Shuts down a previous instance of

the agent if it is running. If the agent does not exist:

Shutting down Agent.... Unable to detect a running agent...

Instance does not exist

If the agent exists:

Shutting down Agent.... Shut down normally

url Prints the URL of the hub with which the agent is configured to communicate.

http:// 216.131.222.227:80/ PSEMHUB/hub

validate Validates the current set of managed components that have been

discovered from the last crawling by the agent.

Not applicable (NA)

recrawl Recrawls the hard disk to detect new configurations. Recrawls the detected database environments to update database information. The current search-results.xml file is backed up.

Note: Recrawling includes revalidating.

NA

isrunning Returns true if an agent is already running and false if an agent is not already running.

(38)

Argument Description Sample Output

remove Removes the peer and all its

registered components from the hub. Removal Completed- PeerID 2 hasbeen removed. Removal Failed- PeerID 2 could not be removed from the hub.

Starting an Agent in the Background on UNIX

Use the UNIX nohup command with the StartAgent.sh script to start an agent automatically and run in the background. This enables you to avoid having a command prompt open at all times showing the constant heartbeat of the agent. You can specify an output file to store heartbeat information.

For example,

nohup ./StartAgent.sh > agent_output.log &

Starting an Agent With PSEMAgent Windows Service

You can set an Environment Management agent to start automatically when your Environment Management machine boots and run in the background. This enables you to avoid having a command prompt open at all times showing the constant heartbeat of the agent.

For this option, use the PSEMAgent Windows service that's delivered as part of PeopleTools.

Installing the PSEMAgent Service

You install the PSEMAgent service from a command prompt. Copies of the install program are located in two places:

PS_HOME\bin\client\winx86

PS_HOME\bin\server\winx86 To install the PSEMAgent service:

1. At a command prompt, change to either location of the install program. 2. Enter the following command:

PSEMAgentService /install PS_HOME\PSEMAgent Where PS_HOME is the PeopleTools installed location.

The PSEMAgent service 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. You can start it manually, or wait for the next reboot.

(39)

Starting the PSEMAgent Service

You can start the PSEMAgent service from a command prompt, or from the Windows Services control panel. The name of the service follows this convention: PeopleSoft Environment Management Agent-<release>.

• To start the PSEMAgent service from a command prompt, use the NET START command. For example:

NET START "PeopleSoft Environment Management Agent-8.50" • To start the PSEMAgent service from the Windows Services control panel:

1. Open the Windows Control Panel, then double-click Administrative Tools, then Services. 2. In the Services control panel, right-click the PeopleSoft Environment Management Agent entry

and select Start.

Stopping the PSEMAgent Service

You can stop the PSEMAgent service from a command prompt, or from the Windows Services control panel.

• To stop the PSEMAgent service from a command prompt, use the NET STOP command. For example:

NET STOP "PeopleSoft Environment Management Agent-8.50" • To stop the PSEMAgent service from the Windows Services control panel:

1. Open the Windows control panel, then double-click Administrative Tools, then Services. 2. In the Services control panel, right-click the PeopleSoft Environment Management Agent entry

and select Stop.

Uninstalling the PSEMAgent Service

You uninstall the PSEMAgent service from a command prompt. To uninstall the PSEMAgent service:

1. At a command prompt, change to either location of the uninstall program. Copies of the uninstall program are located in two places:

PS_HOME\bin\client\winx86

PS_HOME\bin\server\winx86 2. Enter the following command: PSEMAgentService /uninstall

PSEMAgentService determines if the service is currently started, and automatically stops it before completing the uninstall operation. You'll see messages reporting on the status of the operation.

(40)

Note: If the service is currently stopped, you'll see an error message indicating that it can't be stopped. Regardless of this, the uninstall operation completes normally.

Monitoring Agent Status

If the Hub does not receive status from a peer for three ping cycles ("I am alive" messages) then it changes the state of the peer from Running to Not Running. Information related to agent status can be accessed from a browser using the following URL:

http://hub_host:hub_port/PSEMHUB/hub

Running the Viewer

To view data from the Environment Management hub:

1. Run a Java program to connect to the hub and retrieve the information in XML format.

Run the appropriate script for your environment in from PS_HOME\PSEMViewer. You will be prompted for the web server's listening port.

• UNIX: ./GetEnvInfo.sh • Windows: GetEnvInfo.bat

Note: For security reasons, the Java program connects only to the local host.

2. Open PS_HOME\PSEMViewer\envmetadata\data\viewer.html to view the information in the generated XML file.

Configuring and Starting an Environment Management Agent on z/OS

To run an agent on z/OS, you must have installed JRE delivered with PeopleTools on the z/OS machine. To configure and start the agent on z/OS:

1. Edit the configuration.properties file (PS_HOME/PSEMAgent/envmetadata/config). 2. Edit hubURL and define the hub machine name and hub port.

3. Edit unixdrivestocrawl and set it to the set of directories that need to be crawled. 4. Edit StartAgent.sh.

(41)

Edit the last line to point to your JRE location.

The default charset on z/OS is EBCDIC. If you wish to view the content of PS_HOME/PSEMAgent/ envmetadata/data/search-results.xml, you need to run the following commands:

cd PS_HOME/PSEMAgent/envmetatda/data . PS_HOME/psconfig.sh

PS_HOME/bin/psuniconv utf-8 search-results.xml ccsid1047 result.txt This comment is also true for PS_HOME/PSEMAgent/envmetadata/data/matchers.xml.

You can find a viewable version of the results in result.txt. You can also FTP (binary) these files to a different machine running a different operating system and view them in any editor.

Integrating with Oracle Configuration Manager

This section contains an overview and discusses how to instrument PeopleTools for Oracle Configuration Manager data collection.

Understanding Oracle Configuration Manager for PeopleSoft

Oracle Configuration Manager (OCM) is used to collect configuration data from customer environments and upload that data to a Customer Configuration Repository (CCR) stored and managed by Oracle. OCM works in tandem with PeopleSoft EMF for collecting configuration data from a PeopleSoft environment. The OCM data collection agents collect configuration data using the feed provided by the PeopleSoft EMF agents.

The PSEMAgent has to be running on the instance so that configuration data can be collected. After crawling the environment, PSEMAgent writes the environment data in XML format (with a .psft extension) to the PS_HOME/ccr/state directory.

OCM is installed and configured on a PeopleTools environment as part of the application server, Process Scheduler server, and web server PeopleTools installation. You can also install and configure OCM by directly downloading the standalone install kit from My Oracle Support.

See PeopleTools 8.53 Installation <for your platform>, “Using the PeopleSoft Installer”

Instrumenting PeopleTools for Configuration Data Collection

This section provides an overview of the data collection and discusses: • Setting up Integration Broker for OCM.

• Deploying Services for OCM. • Setting up security for OCM. • Publishing queries for OCM.

Understanding PeopleTools Instrumentation for OCM

The optional configuration information collected from a PeopleSoft system for Oracle Configuration Manager (OCM) are defined as queries and shipped with OCM collectors. The query definitions need to be instrumented after the installation and configuration of OCM on a PeopleSoft environment. The instrumentation step publishes the queries that are required to gather configuration information from a PeopleSoft system using Integration Broker. The queries can be instrumented by a Java program

(42)

“psft_qrypub” and are part of the OCM collector. The publishing of queries is a one-time activity performed after the configuration of CCR collectors.

The Integration Broker services and interfaces used by the publishing engine are:

Service Name Operation Name Description

QAS_QRY_SERVICE QAS_EXECUTEQRYSYNC_OPER Discovers application type. QAS_LISTQUERY_OPER Determines whether data already

exists.

QAS_QUERY_DELETE_OPER Deletes query for republishing. QAS_SAVE_QUERY_OPER Saves query definition.

PT_CCR_QUERY CCR_TREE_ADD_REC Adds participating records of a query to QUERY_TREE_CCR.

Setting Up Integration Broker for OCM

Setting up Integration Broker is discussed in the Integration Broker documentation. When setting up Integration Broker for OCM, make sure that:

• your gateway is configured and pointing to the appropriate gateway URL, such as http:// <webserver_machinename>:<httpport>/PSIGW/PeoplesoftListeningConnector.

• all other connectors are loaded.

• on the PeopleSoft Node Configuration page you specify the appropriate Gateway Default App. Server values and PeopleSoft Nodes values.

• you can ping the node successfully.

• on the Service Configuration page (PeopleTools, Integration Broker, Service Configuration) that the target location http://<webserver>:<httpport>/PSIGW/PeopleSoftServiceListeningConnector.

Deploying Services for OCM

To publish QAS services:

1. Select PeopleTools, Integration Broker, Web Services, Provide Web Service. 2. Search and select the QAS_QRY_SERVICE service, and click Next.

(43)

• QAS_SAVE_QUERY_OPER

5. Click Next until the final step and click Finish.

6. Make note of the WSDL URL generated, and open the wsdl in a new browser and make sure it was generated successfully.

To publish CCR services:

1. Select PeopleTools, Integration Broker, Web Services, Provide Web Service. 2. Search for and select PT_CCR_QUERY, and click Next.

3. Choose the following operation. CCR_TREE_ADD_REC.v1. 4. Click Next until the final step and click Finish.

5. Make note of the WSDL URL generated, and pen the wsdl in a new browser and make sure it was generated successfully.

To verify permissions for service PT_CCR_QUERY and operation CCR_TREE_ADD_REC: 1. Select PeopleTools, Integration Broker, Integration Setup, Service Operations.

2. For search criteria enter: for: • Service: PT_CCR_QUERY

• Service Operation: CCR_TREE_ADD_REC • Operation Type: Synchronous

3. Click CCR_TREE_ADD_REC and select Service Operation Security. 4. Make sure that the permission list PTPT1000 has Full Access is set.

Setting Up Security for OCM

This section defines setting up of two user accounts.

User Account Description

Publisher Used by the client publisher Java program to publish queries using Integration Broker.

To set up this user profile, add the CCR Publisher role to the user profile.

References

Related documents

To understand the interdependence of pangenome features (such as the number of core and accessory genes) and to study the impact of environmental and phylogenetic constraints on

Within each case study I elaborate on the situation of each composer in the Weimar modernist homeworld before detailing their experiences and compositional activity during

3 In contrast, latest RCP guidelines published in 2012 recommend that thrombolysis is considered within 3 hours of symptom onset “regardless of age or stroke

Incubus  - Drive player version Architects  - Naysayer player version Plini  - Atlas player version. Black Veil Brides  - Knives And Pens

The Application Designer is also responsible for defining data structures in PeopleSoft applications and for building database objects, so some of the PeopleTools tables that

The present project evaluates multiple disturbance effects on soil properties and regeneration of a subalpine forest 15 years after a catastrophic wind-storm (or blowdown)

Standards for data quality outline a framework to enable the collection, analysis and use of good quality data to support the delivery of health and social care and to report

List of diatom species found in both the RAIA sediment trap and surficial sediment sample (Geo B 11002). Species that appeared in more than one sediment trap sample with a