PeopleSoft Talent Management 9.1 to PeopleSoft ... - Lee College

PeopleSoft Integration Reference Guide 

Implementing Integration of Setup Data Between Campus Solutions 

9.0 and HCM 

November 2010 

Including: 

• Overview of Campus Solutions 9.0 to HCM Setup Data Integrations 

• Step-by-Step of Implementation Activities 

• Troubleshooting Tips and Techniques

PeopleSoft CS to HCM 

Copyright 2010 Oracle, Inc. All rights reserved. 

Printed on Recycled Paper. Printed in the United States of America. 

Restricted Rights 

The information contained in this document is proprietary and confidential to 

PeopleSoft, Inc. 

Comments on this document can be submitted to Global Support Center. We 

encourage you provide feedback on this Integration Guide and will ensure that it is 

updated based on feedback received. When you send information to Oracle, you 

grant Oracle a non-exclusive right to use or distribute the information in any way it 

believes appropriate without incurring any obligation to you. 

No part of this document may be reproduced or transmitted in any form or by any 

means, electronic or mechanical, including photocopying and recording, for any 

purpose without the express written permission of Oracle. 

This document is subject to change without notice, and Oracle does not warrant that 

the material contained in this document is error-free. If you find any problems with this 

document, please report them to PeopleSoft in writing. 

This material has not been submitted to any formal Oracle test and is published AS IS. 

It has not been the subject of rigorous review. Oracle assumes no responsibility for its 

accuracy or completeness. The use of this information or the implementation of any of 

these techniques is a customer responsibility and depends on the customer's ability to 

evaluate and integrate them into the customer's operational environment. While each 

item may have been reviewed by Oracle for accuracy in a specific situation, there is no 

guarantee that the same or similar results will be obtained elsewhere. Customers 

attempting to adapt these techniques to their own environments do so at their own risk 

Information in this book was developed in conjunction with use of the product 

specified, and is limited in application to those specific hardware and software 

products and levels. 

Oracles may have patents or pending patent applications covering subject matter in 

this document. The furnishing of this document does not give you any license to these 

patents 

Any pointers in this publication to external Web sites are provided for convenience only 

and do not in any manner serve as an endorsement of these Web sites. 

PeopleSoft, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, PeopleTalk, and 

Vantive are registered trademarks, and Pure Internet Architecture, Intelligent Context 

Manager, and The Real-Time Enterprise are trademarks of Oracle. All other company 

and product names may be trademarks of their respective owners. The information 

contained herein is subject to change without notice.

TABLE OF CONTENTS 

Table of Contents 3 

Chapter 1 - Introduction 4 

Structure of this Document ........................................................................................................................................................ 4 

Related Materials ....................................................................................................................................................................... 4 

Chapter 2 - Overview 5 

Introduction ................................................................................................................................................................................ 5 

Who Should Read This Guide? .................................................................................................................................................. 5 

Before You Begin ...................................................................................................................................................................... 6 

Common Terms .......................................................................................................................................................................... 6 

Assumptions ............................................................................................................................................................................... 6 

Chapter 3: Configuring and Administering PeopleSoft CS to HCM Integrations 7 

Understanding PeopleSoft CS to HCM Setup Data Integrations ............................................................................................... 7 

Loading the Setup Data .............................................................................................................................................................. 8 

Configuring and Administering CS – HCM Setup Data integrations ...................................................................................... 11 

Configuring FullSync Service Operations................................................................................................................................ 14 

Configuring Incremental Sync Services ................................................................................................................................... 27 

APPENDIX A – CONFIGURING INTEGRATION BROKER GATEWAY AND NODES ..................................................... 28 

APPENDIX B – FULLSYNC AND SYNC SERVICE OPERATIONS INCLUDED FIELDS .................................................. 32 

APPENDIX C – INTEGRATION BROKER TROUBLESHOOTING ....................................................................................... 85 

Integration Broker Troubleshooting ......................................................................................................................................... 85 

APPENDIX D – VALIDATION AND FEEDBACK .................................................................................................................. 89 

Customer Validation 89 

Field Validation 89 

APPENDIX E – REVISION HISTORY ...................................................................................................................................... 90 

Authors ..................................................................................................................................................................................... 90 

Revision History ....................................................................................................................................................................... 90 

© Copyright Oracle USA 2010. All rights reserved. Page 3 of 90

Implementing Integration of Setup Data Between Campus Solutions 9.0 and HCM 

CHAPTER 1 - INTRODUCTION 

This Integration Guide is a practical guide for functional and technical users, installers, system administrators, and 

programmers who implement, maintain, or develop applications for your PeopleSoft system. In this Integration Guide, we 

discuss configuration of CS – HCM integrations to support shared Setup Data values; this includes configuring and 

troubleshooting a PeopleSoft Integration Broker environment. 

Structure of this Document 

This Integration Guide provides guidance for the implementation of CS to HCM Integrations. It outlines the scope and 

configuration steps of objects available to support CS – HCM integrations. 

Keep in mind that Oracle updates this document as needed so that it reflects the most current feedback we receive from the 

field. Therefore, the structure, headings, content, and length of this document is likely to vary with each posted version. To see 

if the document has been updated since you last downloaded it, compare the date of your version to the date of the version 

posted on My Oracle Support. 

Related Materials 

We recommend that before you read this guide, you also read the Campus Solutions-HCM Integration White Paper, it provides 

an overall summary of the objectives and various approaches to supporting separate CS and HCM instances. 

In addition to this document, additional implementation guides have been developed to assist you in understanding and 

implementing your CS – HCM integrations. These documents and Campus Solutions-HCM Integration White Paper are 

posted to My Oracle Support, associated with Feature Pack 4 Documentation (ID 1259484.1 ). 

 

 

 

 

Implementing Person Bio-Demo Data Integration between CS and HCM on My Oracle Support 

Implementing External Search/Match between CS and HCM on My Oracle Support 

Implementing CS Integration with the Higher Education Constituent Hub on My Oracle Support (Note that this 

document will not be released until late 2010 or early 2011) 

Implementing Portal Navigation aggregation for CS and HCM Integration on My Oracle Support 

This document is not a general introduction to Integration Broker and we assume that our readers are experienced IT 

professionals, with a good understanding of PeopleSoft‟s Internet Architecture. To take full advantage of the information 

covered in this document, we recommend that you have a basic understanding of system administration, basic Internet 

architecture, integration technologies, relational database concepts/SQL, and how to use PeopleSoft applications. 

This document is not intended to replace the documentation delivered with the PeopleTools 84x or 8.5x PeopleBooks. We 

recommend that before you read this document, you also read the PIA related information in the PeopleTools PeopleBooks to 

ensure that you have a well-rounded understanding of our PIA technology. Note: Much of the information in this document 

eventually gets incorporated into subsequent versions of the PeopleBooks. 

Many of the fundamental concepts related to PIA are discussed in the following PeopleSoft PeopleBooks: 

PeopleSoft Internet Architecture Administration (PeopleTools|Administration Tools|PeopleSoft Internet 

Architecture Administration) 

Application Designer (Development Tools|Application Designer) 

Application Messaging (Integration Tools|Application Messaging) 

PeopleCode (Development Tools|PeopleCode Reference) 

PeopleSoft Installation and Administration 

PeopleSoft Hardware and Software Requirements 


PeopleSoft 9.0 CS – HCM Setup Data Integration Guide 

CHAPTER 2 - OVERVIEW 

This chapter includes the following topics: 

 

 

 

 

Introduction 

Who Should Read This Guide? 

Before You Begin 

Common Terms 

Introduction 

The Campus Solutions suite of products has historically resided in a single database instance with HCM. This coupling has 

enabled CS and HCM to share a person model, a single instance of a person in the system, and student refund processing 

through HR Payroll. Certain key values and codes used throughout Campus Solutions are defined using HCM pages (and the 

data is saved in core HCM tables). 

Oracle is supporting a set of integrations (asynchronous fullsync and incremental sync) that will keep many of these setup data 

values synchronized between your separate CS and HCM systems. Full sync requires user intervention to initiate the process 

for each table. Incremental sync uses services that are triggered by PeopleCode in the online components when data changes. 

The list of available integrations for shared setup data is detailed later in this document. You will want to understand, and 

determine, which of the setup data integrations you will need to use with your CS – HCM integrations. Most of these shared 

setup data values are required for core Person data, and therefore, fundamental to the integration of your Person data. 

Depending on what type of integration approach your institution implements, you will need to analyze which of these data 

values will be important for you to keep in sync. 

CS 9.0 Instance 

HCM 9.0/9.1 Instance 

Reference 

Data 

Transaction 

Data 

For more information on shared HRMS Data Elements that are used in Campus Solutions, see PeopleSoft Enterprise Campus 

Community Fundamentals PeopleBook, “Designing Campus Community,” Understanding Campus Community and PeopleSoft 

Enterprise HRMS Shared Elements 

Who Should Read This Guide? 

Typically, administrative users configure and administer the application. An administrative user can be either an Oracle 

Consulting Services representative or the designated members of your implementation team who are familiar with Integration 

Broker and your organization‟s business process requirements. 



Functional users with a good understanding of core CS Campus Community and Human Resources functionality will be an 

essential part of your implementation. 

This guide assumes at least that level of knowledge and describes how to implement PeopleSoft Campus Solutions - HCM 

Setup Data Integrations. 

Before You Begin 

Before you can setup, administer, or use PeopleSoft Campus Solutions - HCM integrations, you must install or upgrade the 

HCM 9.0 / 9.1 environment and then set up / configure the Integration Broker between the two applications for your institution. 

The steps detailing the installation or upgrade of your HCM 9.0/9.1 system are not part of the scope of this document. 

Some examples of the configuration tasks that you must perform for your CS to HCM Integrations include: 

 

 

 

 

Configuring the PeopleSoft CS and HCM installation and PeopleTools options tables. 

Setting up the integration gateway and integration nodes within the Integration Broker system. 

Activating services, service operations, and routings within the Integration Broker system. 

Defining roles and permissions for your user profiles. 

Common Terms 

This table provides definitions for some of the common terms that are used in this guide. 

Term 

Definition 

EIP 

Owner 

SOR 

User Profiles 

Enterprise Integration Point. These include Fullsync and incremental Sync 

service operations. 

Another term for System of Record; the system that publishes data to a 

subscribing system in synchronization services. 

System of Record; the system that publishes data to a subscribing system in 

synchronization services data loads. 

User profiles define individual PeopleSoft users. You define user profiles and then 

link them to one or more roles. Typically, a user profile must be linked to at least 

one role to be a usable profile. The majority of the permissions that make up a 

user profile are inherited from the linked roles. 

Assumptions 

 

 

Synchronization of your related language data will be handled by PeopleTools. 

Base language in your CS 9.0 and HCM 9.0 or 9.1 should be the same. 



CHAPTER 3: CONFIGURING AND ADMINISTERING PEOPLESOFT CS TO HCM 

INTEGRATIONS 

This chapter discusses how to configure and administer Integrations for your system. It provides an overview of the Integration 

Broker system and discusses the following topics: 

 

 

 

 

Understanding CS – HCM Setup data integrations 

Loading the Setup data 

Configuring and administering the integrations 

Loading and administering user profiles. 

Understanding PeopleSoft CS to HCM Setup Data Integrations 

For PeopleSoft CS - HCM integrations, you must configure both systems, and then load data from your system of record to 

your subscribing target system before you configure additional application features and deploy the application from your 

website to the intended users. 

Determine your system of record (owner) for this data by fully evaluating the business processes and data ownership practices 

at your institution. You may determine that revised process and data governance policies would be beneficial as you 

implement separate CS and HCM systems. 

For customers implementing an Owner/Subscriber integration model, Oracle recommends a best practice of establishing your 

HCM system as the system of record, with your CS 9.0 system as the subscribing target. The HCM instance is the system of 

record for required HCM data, including basic HR Workforce Administration setup data and Workforce transactional data. 

Note: This document demonstrates examples of an Owner/Subscriber implementation, where HCM 9.1 is the system of 

record, and CS 9.0 is the subscribing target system. If you plan to implement a Distinct Ownership model, you can follow the 

same steps to configure and use the Fullsync and Sync service operations for the setup data you will keep in sync between your 

CS and HCM systems. 

Administrative Tasks for CS – HCM Setup Data Integrations 

This section lists the high-level administrative tasks that you must complete to enable your CS – HCM setup data integrations. 

The following table lists the required tasks, the tool required to complete each task, and additional instructional notes. 

Task Phase System Tool 

Required 

Comments 

Configure Integration 

Broker messaging 

Implementation CS 9.0 

HCM 

9.0/9.1 

Integration 

Broker 

Configure remote gateway. Add integration nodes 

for Integration Broker environment. 

Configure FullSync and Sync Setup Data service 

integrations. 

Run full synch 

messaging 


HCM 


Enterprise 

Component 

Full Data 

Publish 

Assumes that Integration Broker is fully 

configured. 



Task Phase System Tool 

Required 

Comments 

Validate data load in 

Integration Broker 

environment 


or 

HCM 


Online 

access or 

online 

query 

In event of data errors, use online pages, reports, 

and queries to validate the data. Rerun full synch 

process as necessary. 

Configure Portal 

Navigations 


or 

HCM 


Online 

access 

See the Implementing Portal Navigation 

aggregation for CS and HCM Integration guide 

(on My Oracle Support). 

Provide navigation links to system of record for 

users to add or update data. 

Configure Permissions Implementation CS 9.0 

or 

HCM 


Online 

access 

See the Implementing Portal Navigation 

aggregation for CS and HCM Integration guide 

(on My Oracle Support), and related PeopleBooks. 

Limit, or provide display-only access to setup data 

pages in the subscriber system. (Users should not 

be allowed to update data directly in a subscribing 

target system, if the data is kept synchronized 

using integrations). 

Ongoing data sync 

(updates) 

Sustaining 

Support 

CS 9.0 

or 

HCM 


Integration 

Broker 

Assumes that Integration Broker is fully 

configured for Sync services, publishing from 

system of record to subscribing target system. 

Loading the Setup Data 

Your CS and HCM systems are integrated to enable setup data to flow between the two environments. The integration is based 

on PeopleTools Integration Broker Asynchronous Service Operations. After your system is installed, you must load the setup 

data to use. 

In place of using the delivered integrations, you may choose to manually update the data in both systems; be sure to review 

these implementation decisions in context of your business practices and data ownership decisions. If you will be 

implementing an Owner/Subscriber model for your separate CS and HCM systems, you will need to be certain that the related 

setup data is kept in sync. Oracle recommends that you make use of the delivered integrations to keep these setup data 

elements in sync. 

Note. For these integrations, the data flow is one way only from your system of record to your subscribing target. To maintain 

data integrity in this one-way flow, much of the setup data loaded from the system of record should be hidden from view or 

made display-only in the subscribing target system. This is further discussed later in this document. 

You can use the following methods to load data from your system of record to the subscribing target system: 

 

 

Full Synchronization Services (full sync – initial load only) 

Incremental Synchronization Services (sync) 

No matter what method you use, you must load data in the proper sequence to accommodate data dependencies. 



You must also load the specific data tables within each set of tables in proper order. For example, for setup tables, you must 

load the Country Table first, then the Currency Code Table, then the States/Provinces table, and so on. 

This section gives a high-level description of each method and provides the required table loading sequences. 

Full Synchronization 

A full synchronization service (full sync) captures all of the data that you specify in the system of record (SOR) and publishes 

it to the subscribing system. It first deletes all data of the specified type that is in the subscriber and replaces it with the 

captured data. 

Warning! Because of the data deletion associated with full sync, consider running full sync only at implementation time or if 

you must clear your CS to HCM system and begin again. Use the full sync process for data that infrequently changes. 

Defining Integration Definitions 

Load data from your system of record to your subscribing target system for implementation using the full sync method. To use 

full sync, first define full data publish rules. Then define run controls to schedule and run the full sync service for each rule. 

Use integration definitions pages in Enterprise Components to enable full sync data publishing. 

 

 

 

 

On the Full Data Publish Rules page, identify each message structure to use as a service and any chunking rules. 

Chunking rules allow data to be broken into more manageable pieces for tables with many rows. 

If you want to define a subset of data to publish, use the Record Mapping page. For example, if you are implementing 

only one subsidiary of your organization in CS to HCM Integrations, you might create a view that isolates that data, 

and then that view to map to a record contained within the service structure. 

On the Languages page, identify whether you want to send base language content, all related language content, or 

specified languages to CS to HCM Integrations. 

Initiate the full sync service for each table on the Full Data Publish page using the appropriate table loading sequence. 

For more information on full data publishing rules or any of the Enterprise Component pages described in this section, see 

PeopleSoft Enterprise Components PeopleBook for PeopleSoft Enterprise HRMS & Campus Solutions, “Assigning Publishing 

Rules.” 

Setup Data Loading Sequence 

Minimum setup information must be available and loaded from your HCM system to your CS 9.0 system for implementation. 

Oracle recommends that your HCM instance be the system of record for your setup table data. 

Table 1 below lists the available service operations and applicable tables. These should loaded in order as specified. 



Integration Description Integration Name Table(s) 

Country Codes COUNTRY_FULLSYNC COUNTRY_TBL 

Currency Codes CURRENCY_FULLSYNC CURRENCY_CD_TBL 

State/Province Codes STATE_FULLSYNC STATE_TBL 

SetIDs SETID_INITIALIZE SETID_TBL 

Tableset Controls TBLSET_CONTROL_INITIALIZE SET_CNTRL_TBL 

SET_CNTRL_GROUP 

SET_CNTRL_REC 

Regulatory Regions REGULATORY_REGION_FULLSYNC REG_REGION_TBL 

HR Business Units BUS_UNIT_HR_FULLSYNC BUS_UNIT_TBL_HR 

Company Codes COMPANY_FULLSYNC COMPANY_TBL 

Location Codes LOCATION_FULLSYNC LOCATION_TBL 

Department Codes DEPT_FULLSYNC DEPT_TBL 

Job Codes JOBCODE_FULLSYNC JOBCODE_TBL 

Holiday Date Schedules HOLIDAY_DATE_FULLSYNC HOLIDAY_TBL 

HOLIDAY_DATE 

National ID Types NID_TYPE_FULLSYNC NID_TYPE_TBL 

Name Types NAME_TYPE_FULLSYNC NAME_TYPE_TBL 

Name Prefixes NAME_PREFIX_SUFFIX_FULLSYNC1 NAME_PREFIX_TBL 

Name Suffixes NAME_PREFIX_SUFFIX_FULLSYNC2 NAME_SUFFIX_TBL 

Name Royal Prefixes NAME_PREFIX_SUFFIX_FULLSYNC3 NM_ROYPREF_TBL 

Name Royal Suffixes NAME_PREFIX_SUFFIX_FULLSYNC4 NM_ROYSUFF_TBL 

Name Titles TITLE_FULLSYNC TITLE_TBL 

Address Types ADDRESS_TYPE_FULLSYNC ADDRESS_TYP_TBL 

Person of Interest Types POI_TYPE_TBL_FULLSYNC POI_TYPE_TBL 

Ethnic Group Codes ETHNIC_GRP_FULLSYNC ETHNIC_GROUP_TBL 

US Standard Occupational US_SOC_FULLSYNC 

US_SOC_TBL 

Codes (USA) 

Supporting Documents SUPPORT_DOC_FULLSYNC 

(Visa/Permits) 

SUPPORT_DOC_TBL 

Visa Permit Types VISA_PERMIT_FULLSYNC VISA_PERMIT_TBL, 

VISA_PERMIT_SUP 

Major Codes COMPETENCY_FULLSYNC3 MAJOR_TBL 

Table 1 Setup Data Integrations 

Incremental Synchronization 

Data in the supporting tables in your system of record may change over time after the initial loading of setup, transactional 

data, and security data. Use incremental sync (Sync) services to send this information from your system of record to your 

subscribing target system to maintain data integrity. 

An incremental sync captures data that was created, added, changed, or deleted in the system of record since the last 

synchronization. It uses the captured data to overwrite the same data in the subscribing system, thereby refreshing the 

subscribing system so that both systems have the same data. 

After the initial Fullsync data loads have completed in your subscribing target system, you may inactivate the associated 

FullSync services, and then activate the appropriate incremental Sync services to keep your systems updated. 



Manual Entry Data Load 

You can, if necessary, type data manually into your CS 9.0 and HCM 9.0/9.1 systems, however it would be tedious, time 

consuming, and possibly introduce typographical errors. Oracle does not recommend this method for most data elements unless 

required to load a small amount of data. 

Configuring and Administering CS – HCM Setup Data integrations 

FullSync and Sync Service Operations and Handlers 

The following table identifies the FullSync and Sync Service Operations, and subscription handlers that you should use to 

configure your CS – HCM setup data integrations. You should configure all integrations that you have identified according to 

your business requirements and implementation plans. 

Table 2 FullSync and Sync Service Operations and Handlers 

Service Operation Description Queue Subscription Handler App Pkg 

ADDRESS_TYPE_FULLSYNC 

ADDRESS_TYPE_SYNC 

BUS_UNIT_HR_FULLSYNC 

BUS_UNIT_HR_SYNC 

Address Type 

Table 

Address Type 

Table 

HR Business Unit 

Table 

HR Business Unit 

Table 

PERSON_SETUP 

PERSON_SETUP 

HR_SETUP 

HR_SETUP 

AddressTypeFullSync 

(ADDRESS_TYPE_FULLSYNC/AddressTypeFullSync/On 

Notify) 

AddressTypeSync 

(ADDRESS_TYPE_SYNC/AddressTypeSync/OnNotify) 

BusUnitHRFullSync 

(BUS_UNIT_HR_FULLSYNC/BusUnitHRFullSync/OnNo 

tify) 

BusUnitHRSync 

(BUS_UNIT_HR_SYNC/BusUnitHRSync/OnNotify) 

COMPANY_FULLSYNC Company Codes PERSON_SETUP CompanyFullSync 

(COMPANY_FULLSYNC/CompanyFullSync/OnNotify) 

COMPANY_SYNC Company Codes PERSON_SETUP CompanySync 

(COMPANY_SYNC/CompanySync/OnNotify) 

COMPETENCY_FULLSYNC3 

COMPETENCY_SYNC3 

College Major 

Subject Codes 

College Major 

Subject Codes 

COMPETENCY 

COMPETENCY 

COUNTRY_FULLSYNC Countries ENTERPRISE_SE 

TUP 

COUNTRY_SYNC Countries ENTERPRISE_SE 

TUP 

CURRENCY_FULLSYNC Currency Codes ENTERPRISE_SE 

TUP 

CURRENCY_SYNC Currency Codes ENTERPRISE_SE 

TUP 

DEPT_FULLSYNC Departments ENTERPRISE_SE 

TUP 

DEPT_SYNC Departments ENTERPRISE_SE 

TUP 

ETHNIC_GRP_FULLSYNC 

ETHNIC_GRP_SYNC 

HOLIDAY_DATE_FULLSYNC 

Ethnic Group 

Table 

Ethnic Group 

Table 

Holiday Date 

Schedules 

TAM_INTEGRAT 

ION 

TAM_INTEGRAT 

ION 

PERSON_SETUP 

CompetencyFullSync3 

(COMPETENCY_FULLSYNC3/CompetencyFullSync3/On 

Notify) 

CompetencySync3 

(COMPETENCY_SYNC3/CompetencySync3/OnNotify) 

GEN_UPG_HANDLER_12332 

(COUNTRY_FULLSYNC/CountryFullSync/OnNotify) 

CountrySync 

COUNTRY_SYNC/CountrySync/OnNotify 

CurrencyFullSync 

CURRENCY_FULLSYNC/CurrencyFullSync/OnNotify 

CurrencySync 

CURRENCY_SYNC/CurrencySync/OnNotify 

DeptFullSync 

(DEPT_FULLSYNC/DeptFullSyncNoCI/OnNotify) 

DeptSync 

DEPT_SYNC/DeptSync/OnNotify 

EthnicGrpFullSync 

ETHNIC_GRP_FULLSYNC/EthnicGrpFullSync/OnNotify 

EthnicGrpSync 

ETHNIC_GRP_SYNC/EthnicGrpSync/OnNotify 

HolidayDateFullSync 

HOLIDAY_DATE_FULLSYNC/HolidayDateFullSync/On 

Notify 




HOLIDAY_DATE_SYNC 

Holiday Date 

Schedules 

PERSON_SETUP 

HolidayDateSync 

HOLIDAY_DATE_SYNC/HolidayDateSync/OnNotify 

JOBCODE_FULLSYNC Job Codes PERSON_SETUP JobcodeFullSync 

JOBCODE_FULLSYNC/JobcodeFullSync/OnNotify 

JOBCODE_SYNC Job Codes PERSON_SETUP JobcodeSync 

JOBCODE_SYNC/JobcodeSync/OnNotify 

LOCATION_FULLSYNC 

LOCATION_SYNC 

NAME_PREFIX_SUFFIX_FUL 

LSYNC1 

Company Site 

Locations 

Company Site 

Locations 

Name Prefixes 

ENTERPRISE_SE 

TUP 

ENTERPRISE_SE 

TUP 

NAME_PREFIX_ 

SUFFIX_TABLES 

LocationFullSync 

(LOCATION_FULLSYNC/LocationFullSync/OnNotify) 

LocationSync 

(LOCATION_SYNC/LocationSync/OnNotify) 

NamePrefixSuffixFullSync1 

NAME_PREFIX_SUFFIX_FULLSYNC1/NamePrefixSuffi 

xFullSync1/OnNotify 


LSYNC2 

Name SuffixTable 

NAME_PREFIX_ 

SUFFIX_TABLES 





LSYNC3 

Name Royal Pref 

Table 

NAME_PREFIX_ 

SUFFIX_TABLES 





LSYNC4 

Name Royal Suff 

Table 

NAME_PREFIX_ 

SUFFIX_TABLES 




NAME_PREFIX_SUFFIX_SYN 

C1 

Name Prefixes 

NAME_PREFIX_ 

SUFFIX_TABLES 

NamePrefixSuffixSync1 

NAME_PREFIX_SUFFIX_SYNC1/NamePrefixSuffixSync 

1/OnNotify 


C2 

Name SuffixTable 

NAME_PREFIX_ 

SUFFIX_TABLES 



2/OnNotify 


C3 

Name Royal Pref 

Table 

NAME_PREFIX_ 

SUFFIX_TABLES 



3/OnNotify 


C4 

Name Royal Suff 

Table 

NAME_PREFIX_ 

SUFFIX_TABLES 



4/OnNotify 

NAME_TYPE_FULLSYNC Name Type Table PERSON_SETUP NameTypeFullSync 

NAME_TYPE_FULLSYNC/NameTypeFullSync/OnNotify 

NAME_TYPE_SYNC Name Type Table PERSON_SETUP NameTypeSync 

NAME_TYPE_SYNC/NameTypeSync/OnNotify 

NID_TYPE_FULLSYNC 

NID_TYPE_SYNC 

OPR_DEF_FULLSYNC 

OPR_DEF_SYNC 

National ID Type 

table 

National ID Type 

table 

Operator Defaults 

Table - HR 

Operator Defaults 

Table - HR 

PERSON_SETUP 

PERSON_SETUP 

TAM_INTEGRAT 

ION 

TAM_INTEGRAT 

ION 

NidTypeFullSync 

NID_TYPE_FULLSYNC/NidTypeFullSync/OnNotify 

NidTypeSync 

NID_TYPE_SYNC/NidTypeSync/OnNotify 

OprDefFullSync 

OPR_DEF_FULLSYNC/OprDefFullSync/OnNotify 

OprDefSync 

OPR_DEF_SYNC/OprDefSync/OnNotify 

POI_TYPE_TBL_FULLSYNC POI Type Table PERSON_SETUP POITypeTBLFullSync 

POI_TYPE_TBL_FULLSYNC/POITypeTblFullSync/OnN 

otify 

POI_TYPE_TBL_SYNC POI Type Table PERSON_SETUP POITypeTBLSync 

POI_TYPE_TBL_SYNC/POITypeTblSync/OnNotify 




REGULATORY_REGION_FUL 

LSYNC 

REGULATORY_REGION_SY 

NC 

Regulatory Region PERSON_SETUP RegRegionFullSync 

REG_REGION_FULLSYNC/RegRegionFullSync/OnNotif 

y 

Regulatory Region PERSON_SETUP RegRegionSync 

REG_REGION_SYNC/RegRegionSync/OnNotify 

SETID_INITIALIZE SetIDs TBLSET_CONTR 

OL 

STATE_FULLSYNC State Codes ENTERPRISE_SE 

TUP 

STATE_SYNC State Codes ENTERPRISE_SE 

TUP 

SUPPORT_DOC_FULLSYNC 

SUPPORT_DOC_SYNC 

TBLSET_CONTROL_INITIALI 

ZE 

Visa Supporting 

Documents 

Visa Supporting 

Documents 

TableSet Control 

Records 

TAM_INTEGRAT 

ION 

TAM_INTEGRAT 

ION 

TBLSET_CONTR 

OL 

SetidInitialize 

(SETID_INITIALIZE/SetidInitialize/OnNotify) 

StateFullSync 

STATE_FULLSYNC/StateFullSync/OnNotify 

StateSync 

STATE_SYNC/StateSync/OnNotify 

SupportDocFullSync 

SUPPORT_DOC_FULLSYNC/SupportDocFullSync/OnNo 

tify 

SupportDocSync 

SUPPORT_DOC_SYNC/SupportDocSync/OnNotify 

TblsetControlInitialize 

TBLSET_CONTROL_INITIALIZE/TblsetControlInitiatlize 

/OnNotify 

TITLE_FULLSYNC Title Table PERSON_SETUP TitleFullSync 

TITLE_FULLSYNC/TitleFullSync/OnNotify 

TITLE_SYNC Title Table PERSON_SETUP TitleSync 

TITLE_SYNC/TitleSync/OnNotify 

US_SOC_FULLSYNC 

US_SOC_SYNC 

US Standard 

Occupational 

Codes 

US Standard 

Occupational 

PERSON_SETUP 

PERSON_SETUP 

USSocFullSync 

US_SOC_FULLSYNC/USSocFullSync/OnNotify 

USSocSync 

US_SOC_SYNC/USSocSync/OnNotify 

Codes 

VISA_PERMIT_FULLSYNC Visa Permit Types VISA_PERMIT VisaPermitFullSync 

VISA_PERMIT_FULLSYNC/VisaPermitFullSync/OnNotif 

y 

VISA_PERMIT_SYNC Visa Permit Types VISA_PERMIT VisaPermitSync 

VISA_PERMIT_SYNC/VisaPermitSync/OnNotify 



Configuring Integration Broker Gateways and Nodes 

Your CS and HCM systems must have appropriate connectivity established before you configure and run any fullsync or sync 

data load process. Please refer to Appendix A of this document for the appropriate steps to configure Integration Broker 

Gateways and Nodes in your CS and HCM systems. 

Configuring FullSync Service Operations 

This section of the document outlines the implementation steps for setting up and activating each FullSync service operation in 

Integration Broker. 

Repeat these steps for each FullSync service operation you will use. 

Source Database Configuration Tasks 

Note: The examples shown for the source database configuration tasks are of an HCM 9.1 database on PeopleTools 8.51. 

1. Update security by adding the Service Operation(s) to your primary permission list: 

a. Go to PeopleTools > Permissions & Roles > Permission Lists. 

b. Select the relevant permission list from the search dialog box. 

c. Go to the “Web Services” tab. 

d. Enter the corresponding Service(s) for the Service Operation(s) you wish to use. 

e. Click on the “Edit” link and add access to the relevant Service Operation(s) listed on the Web Service Permissions 

secondary page by selecting the “Full Access” option for the “”Access” column. 



Figure 1 Permission List Web Services Security 

Figure 2 Web Service Permissions – Full Access 

2. Activate Service Operation(s) and Create Routing(s): 

a. Go to PeopleTools > Integration Broker > Integration Setup > Service Operations. 

b. Select the relevant Service Operation(s) from the search dialog box. 

c. Check the “Active” check box on the “General” tab. 



d. Make note of the “Queue Name” field, as you will need to verify that the Queue is in the “Running” status later. 

e. Click on the “Routings” tab and add a new routing for the Service Operation by entering a value in the “Routing 

Name” field and clicking the “Add” button. 

Figure 3 Service Operation Definition 



Figure 4 Service Operations Routings 

f. Enter a “Sender Node” and a “Receiver Node” on the “Routings Definition” page of the “Routings” component. 

g. Verify that the “Active” check box is checked. 

h. Click the “Save” button at the bottom of the “Routings Definition” page to save the routing. 

i. Click the “Return” button at the bottom of the “Routings Definition” page to return to the Service Operation setup 

component. 

j. Save the Service Operation by clicking the “Save” button at the bottom of any of the pages in the Service 

Operations component. 



Figure 5 Service Operation Routing Definitions Detail 

3. Activate Message Queue 

k. Go to PeopleTools > Integration Broker > Service Operations Monitor > Administration > Queue Status. 

l. Scroll down the page until you find the relevant Queue Name (from the Service Operation setup page noted 

earlier). 

m. Review the queue “Status” and activate the queue by pushing the “Run” button if needed. The queue status 

should be set to “Running” before leaving this page. 



Figure 6 Queue Status 

Target Database Configuration Tasks 

Note: The examples shown for the target database configuration tasks are a CS 9.0 database on PeopleTools 8.51. 

1. Update security by adding the service operation to the required user’s permission list. 

a. Go to PeopleTools > Permissions & Roles > Permission Lists. 

b. Select the relevant permission list from the search dialog box (primary permission list for the user). 

c. Go to the “Web Services” tab. 

d. Enter the corresponding Service(s) for the Service Operation(s) you wish to leverage. 

e. Click on the “Edit” link and add access to the relevant Service Operation(s) listed on the Web Service Permissions 

secondary page. 

f. Click “OK” to return to the “Web Services” page. 

g. Click “Save” to save the updated Permission List. 



Figure 7 Permission List Web Services Security 

Figure 8 Web Services Permissions - Full Access 



2. Activate Service Operation and Create Routing. 

a. Go to PeopleTools > Integration Broker > Integration Setup > Service Operations. 

b. Select the relevant Service Operation(s) from the search dialog box. 

c. Check the “Active” check box on the “General” tab. 

d. Make note of the “Queue Name” field, as you will need to verify that the Queue is in the “Running” status later. 

Figure 9 Service Operation Definition 

e. Click on the “Routings” tab and add a new routing for the Service Operation. 

f. Enter a “Sender Node” and a “Receiver Node” on the “Routings Definition” page of the “Routings” component. 

g. Verify that the “Active” check box is checked. 

h. Click the “Save” button at the bottom of the “Routings Definition” page to save the routing. 

i. Click the “Return” button at the bottom of the “Routings Definition” page to return to the Service Operation setup 

component. 



j. Save the Service Operation by clicking the “Save” button at the bottom of any of the pages in the Service Operations 

component. 

Figure 10 Service Operation Routings 

Figure 11 Routing Definitions 

3. Activate or create the required Service Operations OnNotify handler. 

a. Click on the “Handlers” tab of the Service Operations component. 

b. Enter a Handler Name as shown below if one does not exist. 



c. Set Handler Name = [please see Table 1 “Full Sync Service Operations” table below (Application Package Name/ 

Class/ Method column) for the required value for this field. (example: “BusUnitHRFullSync”)] 

d. Set Type = “OnNotify” 

e. Set Implementation = “Application Class” 

f. Set Status = “Active” 

g. Click on “Details” link 

h. Set Package Name = [see Table 2 FullSync Service Operations listed above (Application Package Name/ Class/ 

Method column) for the required value for this field. (Example: “GEN_UPG_HANDLER_12332 ”)] 

i. Set Path = “:” 

j. Set Class ID = [see Table 2 FullSync Service Operations listed above (Application Package Name/ Class/ Method 

column) for the required value for this field. (Example: CountryFullSync) 

k. Set Method = “OnNotify” 

l. Click “OK” to return to the Handlers setup page. 

m. Click “Save” button at the bottom of the Handlers page to save your changes. 

Figure 12 Service Handlers 



Figure 13 Handler Details 

4. Activate Message Queue. 

a. Go to PeopleTools > Integration Broker > Service Operations Monitor > Administration > Queue Status. 

b. Scroll down the page until you find the relevant Queue Name (from the Service Operation setup page noted earlier). 

c. Review the queue “Status” and activate the queue by pushing the “Run” button if needed. 

Executing the Full Data Publish Utility 

Run the Full Data Publish process to synchronize the data between your HCM and CS systems. 

1. Define Full Data Publish Rules 

a. Go to Enterprise Components > Integration Definitions > Full Data Publish Rules 

b. Enter the Message Name of the Service Operation 

c. Enter a Publish Rule ID, a Description, and set the Status field to “Active” 

d. Check the Create Message Header and Create Message Trailer check boxes 

e. Save the page 



Figure 14 Full Table Publish Rules 

2. Execute the Full Data Publish Process 

a. Go to Enterprise Components > Integration Definitions > Initiate Processes. 

b. Create a new Run Control ID as shown below. 

c. Enter a “Request ID”. 

d. Select “Always” for the Process Frequency. 

e. Enter the Message Name from the Full Table Publish Rule created earlier (example: COUNTRY_FULLSYNC). 

f. Save the page and click the “Run” button. 

g. Select the “Full Table Data Publish” process from the Process Scheduler Request page. 

h. Verify the process ran successfully. 



Figure 15 Full Data Publish 

Figure 16 Process Scheduler Request 

1. Go to PeopleTools > Integration Broker > Service Operations Monitor > Monitoring > Aynchronous Services to review 

the status of the Full Sync messages created by the Full Data Publish process. 



Figure 17 Asynchronous Service Operations Monitor 

Configuring Incremental Sync Services 

Once your Fullsync data loads are complete in your subscribing system, you should configure and activate the appropriate 

Sync services to keep your CS and HCM systems updated 

The steps to configure the Sync services in the publishing system of record, and subscribing target are the same as for 

Fullsyncs documented above. Refer to the table of Fullsync and Sync services for the appropriate Service name and 

Subscription Handlers to use. 

You will not need to execute the Full Data Publish Utility for incremental Sync services. The setup data changes made through 

online PIA pages will be triggered and published once you have configured and activated the Sync services. Plan carefully to 

anticipate when users will have access to the system, and may be making data changes that you need to keep in sync. Your 

Sync services should be activated before this time to properly update all data values as appropriate between the systems. 



Appendix A – Configuring Integration Broker Gateway and Nodes 

This appendix describes the steps to configure the Integration Broker Gateways and Nodes in your CS and HCM databases. 

Note: The steps detailed in the following tasks demonstrate the setup for an HCM 9.1 and CS 9.0 databases. 

1. Set the Service Configuration in the HR 9.1 database 

2. Configure the Gateway in the HR 9.1 database 

3. Configure the default local node in the HR 9.1 database 

4. Configure the HR Gateway in the CS H900P7R2 database. 

5. Configure the CS node in the HR database 

6. Configure the default LOCAL node in the CS database 

7. Configure the HR node in the CS database 

8. Configure the CS node in the HR database. 

9. Update the HR Gateway nodes in the HR database 

10. Update the HR Gateway nodes in the CS database. 

11. Update the Single Sigonon nodes. 

12. Testing Nodes 

1. Setting the Service Configuration in the HR 9.1 database 

a. Navigate: PeopleTools > Integration Broker > Configuration > Service Configuration. 

b. Set Service Namespace = 'http://xmlns.oracle.com/Enterprise/HCM/services'. 

c. Set Schema Namespace = 'http://xmlns.oracle.com/Enterprise/Tools/schemas' 

d. Set Target Location = „http://machinename:port/PSIGW/PeopleSoftServiceListeningConnector‟ 

e. Set Service System Status = 'Production'. 

2. Configure the Gateway in the HCM 9.1 database 

a. Navigate: PeopleTools > Integration Broker > Configuration > Gateways. 

b. Select Integration Gateway ID = 'LOCAL' 

c. Set URL = 

„http://machinename:port/PSIGW/PeopleSoftServiceListeningConnector/SPLTHL91' 

d. Click the 'Load Gateway Connectors' button. It should load 9 connectors. 

e. Save. 

f. Click the 'Ping Gateway' button. It should be successful and show the status as 'Active'. 

3. Configure the default local node in the HCM 9.1 database 

a. Navigate: PeopleTools > Integration Broker > Integration Setup > Nodes. 

b. Select the default local node. 

c. Set Descr = 'HCM 9.1 Instance'. 



d. Set Authentication Option = 'Password'. 

e. Node Password = 'PS'. 

f. Default User ID = 'PS'. 

g. Click the 'Connectors' tab. 

h. Use gateway ' LOCAL'. 

i. Set Connector Id = 'PSFTTARGET'. 

j. Click the Portal tab. 

k. Set Tools Release = '8.50.xx'. (Note: by pressing the +J keys, you should be able to see 

the tools release string. 

l. Set Application Release = 'HCM 9.1'. 

m. Set Content URI Text = ' http://machinename:port/psc/SPLTHL91'. 

n. Set Portal URI Text = ' http://machinename:port/psp/SPLTHL91'. 

o. Click the WS Security tab. 

p. Set Authentication Token Type = 'none'. 

q. Disable the 'encrypted' checkbox. 

r. Click Save 

4. Configure the HCM Gateway in the CS 9.0 database. 

a. Navigate: PeopleTools > Integration Broker > Configuration > Gateways 

b. Add a New Value 

c. Integration Gateway ID = . 

d. URL = „http://machinename:port/PSIGW/PeopleSoftListeningConnector/databasename' 

e. Click the 'Load Gateway Connectors' button. It should load 9 connectors. 

f. Save. 

g. Click the 'Ping Gateway' button. It should be successful and show the status as 'Active'. 

5. Configure the CS node in the HCM database 

a. Navigation: PeopleTools > Integration Broker > Integration Setup > Nodes. 

b. Add Node = 

c. Set Descr = „CS 9.0 Instance'. 

d. Set Authentication Option = 'Password'. 

e. Node Password = 'PS' 

f. Default User ID = 'PS' 

g. Click the 'Connectors' tab 

h. Set Gateway = ' LOCAL' 

i. Set Connector ID = 'PSFTTARGET' 



j. Click the Portal tab 

k. Set Tools Release = '8.50.xx‟ (Note: by pressing the +J keys, you should be able to see 

the tools release string) 

l. Set Application Release = 'CS 9.0'. 

m. Set Content URI Text = 'http://machinename:port/psc/databasename' 

n. Set Portal URI Text = 'http://machinename:port/psp/databasename'. 



q. Disable the 'Encrypted' checkbox. 

r. Click Save. 

6. Configure the default LOCAL node in the CS database 

[Note: the gateway used by this node is the HCM gateway. The node passwords must be consistent 

between the CS database and the HCM database.] 

a. Navigation: PeopleTools > Integration Broker > Integration Setup > Nodes 

b. Select the default local node 

c. Set Descr = „CS 9.0 Instance'. 

d. Set Authentication Option = 'Password' 




h. Select Gateway = (Note: this is not the local gateway.) 



k. Set Tools Release = '8.50.xx. (Note: by pressing the +J keys, you should be able to see 

the tools release string. 

l. Set Application Release = 'CS 9.0'. 

m. Set Content URI Text = ' http://machinename:port/psc/databasename 

n. Set Portal URI Text = ' http://machinename:port /psp/databasename 



q. Disable the 'encrypted' checkbox. 


7. Configure the HCM node in the CS database 

[Note that each node is defined twice: once in each database. They should all use the same 

gateway.] 

a. Navigation: PeopleTools > Integration Broker > Integration Setup > Nodes. 



b. Add Node: 

c. Set Descr = „HCM 9.1 Instance' 

d. Set Authentication Option = 'Password' 




h. Gateway ID = (Note: this is not the local gateway.) 



k. Set Tools Release = '8.50.xx'. (Note: by pressing the +J keys in the HR database PIA, 

you should be able to see the tools release string. 

l. Set Application Release = „HCM 9.1‟ 

m. Set Content URI Text = ' http://machinename:port/psc/databasename‟ 

n. Set Portal URI Text = ' http://machinename:port/psp/databasename‟ 



q. Disable (turn off) the „Encrypted‟ checkbox. 


s. Node Saved message box. Click OK. 

8. Update the HCM Gateway nodes in the HCM database 

Both CS and HCM database nodes should point to the same Gateway. The specific Gateway should also 

have both Nodes listed in the Gateway Advanced Properties. 

Point to both nodes. 


b. Select gateway 'LOCAL'. 

c. Select the 'Gateway Setup Properties' link. 

d. User ID = „administrator‟ 

e. Password = „password‟ 

f. Click OK. 

g. In the 'Gateway Default App. Server' frame, Set the App Server URL = ' //machinename:port 

(Note: your port must match that specified in your HCM application server.) 

h. Enter the appropriate User ID 

i. Enter the appropriate Password 

j. Set the tools release = '8.50.xx'. (Note: by pressing the +J keys, you should 

k. be able to see the tools release string.) 



l. Make sure both the HCM and CS nodes are in the 'PeopleSoft Nodes' tab 

m. Ping the HCM node. It should be successful. 

n. Click return. 

9. Update the HCM Gateway nodes in the CS database. 


b. Select gateway 'LOCAL'. 

c. Select the 'Gateway Setup Properties' link. 

d. User ID = „administrator‟ 

e. Password = „password‟ 

f. Click OK. 

g. In the 'Gateway Default App. Server' frame, Set the App Server URL = ' //machinename:port 

(Note: your port must match that specified in your HCM application server.) 

h. Enter the appropriate User ID 

i. Enter the appropriate Password 

j. Set the tools release = '8.50.xx'. (Note: by pressing the +J keys, you should 

k. be able to see the tools release string.) 

l. Make sure both the HCM and CS nodes are in the 'PeopleSoft Nodes' tab 

m. Ping the HCM node. It should be successful. 

n. Click return. 

10. Update the Single Signon nodes in both CS and HCM databases 

Single signon is used in this recommended configuration. 

a. Navigate: PeopleTools > Security > Security Objects > Single Signon. 

b. Make sure that both the default local node and the other node you will be using are listed. 

11. Testing Nodes 

Both nodes must be 'pingable' from each database. 

a. Navigate: PeopleTools > Integration Broker > Service Operations Monitor > Administration> 

Node Status. Do this on each database. 

b. For each node name, enter its name and click the 'Ping Node' button. 

c. It should respond with 'Success'. 

Appendix B – FullSync and Sync Service Operations Included Fields 



This appendix details the included fields in each of the Fullsync and Sync message structures. It is for reference only. 

Message Versions are current as of November 2010, and are shown for CS 9.0 (HRCS 9.0). 

Address Types 

Figure 18 ADDRESS_TYPE_FULLSYNC 

Figure 19 ADDRESS_TYPE_SYNC 



HR Business Units 

Figure 20 BUS_UNIT_HR_FULLSYNC 



Figure 21 BUS_UNIT_HR_SYNC 



Company Codes 







Figure 22 COMPANY_FULLSYNC 









Figure 23 COMPANY_SYNC 



Competency (Major Codes) 

Figure 24 COMPETENCY_FULLSYNC3 

Figure 25 COMPETENCY_SYC3 



Country Codes 

Figure 26 COUNTRY_FULLSYNC.VERSION_2 



Figure 27 COUNTRY_SYNC.VERSION_2 



Currency Codes 

Figure 28 CURRENCY_FULLSYNC.VERSION_1 

Figure 29 CURRENCY_SYNC 





Departments 



Figure 30 DEPT_FULLSYNC 





Figure 31 DEPT_SYNC 



Ethnic Group Codes 

Figure 32 ETHNIC_GRP_FULLSYNC 

Figure 33 ETHNIC_GRP_SYNC 



Holiday Date Schedules 

Figure 34 HOLIDAY_DATE_FULLSYNC 

Figure 35 HOLIDAY_DATE_SYNC 



Job Codes 









Figure 36 JOBCODE_FULLSYNC 











Figure 37 JOBCODE_SYNC 



Location Codes 



Figure 38 LOCATION_FULLSYNC 





Figure 39 LOCATION_SYNC 



Name Prefixes 

Figure 40 NAME_PREFIX_SUFFIX_FULLSYNC1 

Figure 41 NAME_PREFIX_SUFFIX_SYNC1 



Name Suffixes 





Name Royal Prefixes 





Name Royal Suffixes 





Name Types 

Figure 48 NAME_TYPE_FULLSYNC 

Figure 49 NAME_TYPE_SYNC 



National ID Types 

Figure 50 NID_TYPE_FULLSYNC 

Figure 51 NID_TYPE_SYNC 



Person of Interest (POI) Types 

Figure 52 POI_TYPE_TBL_FULLSYNC 



Figure 53 POI_TYPE_TBL_SYNC 



Regulatory Regions 

Figure 54 REGULATORY_REGION_FULLSYNC 

Figure 55 REGULATORY_REGION_SYNC 



SetIDs 

Figure 56 SETID_INITIALIZE 

State Codes 

Figure 57 STATE_FULLSYNC 



Figure 58 STATE_SYNC 

Visa Permit Supporting Documents 

Figure 59 SUPPORT_DOC_FULLSYNC 



Figure 60 SUPPORT_DOC_SYNC 

TableSet Control Records 

Figure 61 TBLSET_CONTROL_INITIALIZE 



Name Titles 

Figure 62 TITLE_FULLSYNC 

Figure 63 TITLE_SYNC 



US Standard Occupational Codes 

Figure 64 US_SOC_FULLSYNC 

Figure 65 US_SOC_SYNC 



Visa Permit Codes 

Figure 66 VISA_PERMIT_FULLSYNC 



Figure 67 VISA_PERMIT_SYNC 



1 

Appendix C – Integration Broker Troubleshooting 

Integration Broker Troubleshooting 

This chapter includes some basic troubleshooting techniques and is for reference only. 

Publication Contract not created 

Possible causes: 

1. No publication PeopleCode exists. 

2. Publication PeopleCode is incorrect. 

Publication Contract stays in NEW status 


1. Message Queue is paused. 

2. Publication Dispatcher has crashed or has been brought down. 

3. Node should be Active. 

4. Previous message had a status of Retry, Error, or Timeout. 

5. Domain is not active. 

6. Incorrect Gateway URL defined on Message Node. 

7. After unsuccessful ping, a row may be added to the table PSNODESDOWN; which will hold up the message queue. 

Query the table PSNODESDOWN. 

Publication Contract stays in RETRY status 


1. The remote node cannot be pinged successfully. The publication contract will be processed when the remote node 

comes back up. 

2. No publication handler available, either because it‟s crashed or it‟s been brought down. 

Publication Contract stays in WORKING status 


1. The publication handler processing the contract is on another machine and either the machine or the domain is down. 

Processing should continue when the pub/sub system on the other machine comes back up. 

2. Single threading on the application server is making things slow. 

Publication Contract is in TIMEOUT status 


1. Transaction is not setup on the target node definition. Check APPSRV.LOG file for possible cause. 

2. Subscribing Node should be Active. 

3. Message Node URL is incorrect in the integrationGateway.properties file. 



4. No subscription PeopleCode exists on the subscribing system, or subscription PeopleCode is incorrect. 

5. An exception occurred on the target application server (look in APPSRV.LOG file for details) verify the following: 

a. Source node defined in target database. 

b. Verify correct password on node, target and source (if using password). 

c. Message or Channel not defined in target database. 

d. Incorrectly routed reply. Check Gateway for correct machine address or target node. 

e. No target local node defined. 

f. Bad XML syntax. 

Publication Contract is in ERROR status 


1. Message Node URL is incorrect. 

2. Subscription PeopleCode is bad. 

Subscription Contract not created 


1. Message subscription is inactive. 

2. Queue routing rule not set up properly. 

Subscription Contract stays in NEW status 


1. Application Server down. 

2. Pub/Sub process not configures on the Application Server domain. 

3. The Subscription Dispatcher has crashed or has been brought down. 

4. Message definition not active. 

5. Subscription PeopleCode is not active. 

6. Message queue is paused. 

7. Node is paused. 

8. Previous message had errors or timed out. 

9. No row was inserted into PSAPMSGSUBPRCID. To insert a row enter the following SQL statement: 

Insert into PSAPMSGSUBPRCID values(0) 

Subscription Contract stays in STARTED status 


1. Subscription Handler down. 

2. Check the target component online to make sure they are valid. 

Subscription Contract stays in WORKING status 


1. No subscription PeopleCode exists. 

2. Subscription Handler crashed while processing message. 



Subscription Contract is in ERROR status 


1. Message queue property if Ordered will allow subscription contracts to go in random order. This will cause 

FULLSYNC message to error out when the transaction as subscribed before the header. 

2. Subscription PeopleCode error. 

3. Application Data error. 

4. Verify auto-number sequence. 

Subscription Contract is in EDIT status 

Possible cause: 

1. Message was edited and has yet to be resubmitted for processing. 

Subscription Contract is in RETRY status 


1. Subscription PeopleCode is empty. 

2. Message Definition on target in not active. 

Cannot find message in Message Monitor 


1. User does not have security for the message channel. 

2. The Service Operations Monitor criteria have filtered out the message. 

Messages are being processed in an incorrect order 


1. The queue has been partitioned, and the resulting sub-channels do not match what was assumed for the ordering of the 

messages. 

Message Instance not created 


1. Message is inactive. 

Message Instance stays in NEW status. 


1. The Application Server is down. 

2. Pub/Sub services not configured on Application Server domain. 

3. The Message Dispatcher has crashed or has been brought down. 

4. The item is not at the top of the queue. All messages with the same Channel/Sub-channel are in the same queue. 



Message Instance stays in STARTED status. 


1. All message Handlers have crashed or have been brought down. Processing will resume when Message Handlers 

come brought back up. 

2. The Message Dispatcher processing the message is on another machine, and either the machine or the application 

server domain is down. 

Message Instance stays in WORKING status. 


1. Message Broker Handler has crashed. 

2. The Message Handler working on the message is blocked. The service will time out, and the Message Dispatcher will 

retry the message. 

My Publish() PeopleCode finishes successfully, but there is no message in the Message Monitor 


1. The message definition is inactive. 

Unable to ping a node 


1. The web server for the Gateway is down. 

2. The Gateway is not configured properly. 

3. The Application Server for the node is down. 

4. Verify URL is correct. Copy URL in browser address, should see: 

5. Also try to ping both machines using machine names. If that fail, use their IP-addresses instead. 



Message Queue is PAUSED 

Some message channels are delivered from PeopleSoft as paused. 

1. Change the status to RUN in order for the messages to process from NEW to WORKING. 

Appendix D – Validation and Feedback 

This section documents the real-world validation that this Integration Guide has received. 

CUSTOMER VALIDATION 

PeopleSoft is working with PeopleSoft customers to get feedback and validation on this document. Lessons learned from these 

customer experiences will be posted here. 

FIELD VALIDATION 

PeopleSoft Consulting has provided feedback and validation on this document. Additional lessons learned from field 

experience will be posted here. 



Appendix E – Revision History 

Authors 

PeopleSoft Enterprise Campus Solutoins Development and Support Teams 

Revision History 

October 2010 - Created document.

PeopleSoft Talent Management 9.1 to PeopleSoft ... - Lee College

Create successful ePaper yourself

Delete template?

Save as template?