Connector for Oracle PeopleSoftThe Oracle PeopleSoft Connector is built on the Web Services Connector. Please refer to the TechNet documentation for the Web Services Connector for additional information.

SummaryFeatures Supported variants

Connected data source versions Oracle PeopleSoft 9.1Scenarios Object Lifecycle Management

Password ManagementOperations Full import

Delta import (With custom code) Export Password Management

Schema Person/Employee User

Permissions in connected data sourceTo create or perform any of the supported tasks in Web Service connector for all the supported data sources, you must have following permissions.

1. Permissions

HCSPNAVHP HCPPALL HCSPPRFL HCDPALL

2. Roles EOPP_USER Employee HCM Security Administrator HR Administrator PAPP_USER PeopleSoft User PeopleTools Portal Administrator Security Administrator

Ports and protocolsThis is depends upon the PeopleSoft installation and configuration.

Connector update historyBuild Release Revision list5.0.458.0 2012 June First release of the Web Services Connector.

Requirements, before you begin, and installation

Installation of Default ProjectsThe default project installer file is available at the Microsoft Download Center . Download the installer file and run to install.

Double click the downloaded project file to begin installation.

a. The following screen appears, click Yes.

b. Next license agreement screen appears; click Yes to accept the terms and conditions.

c. The next screen prompts to specify the location for installing the default project. Specify the location: %FIM_INSTALL_DIR\2010\Synchronization Service\Extensions and click OK.

d. The installation starts and the successful completion is reported. Click OK to exit setup wizard.

Oracle PeopleSoft HRMS 9.1a. The default project consumes the exposed CIs in the form of web service through WSDL path.

Ensure that the web service is exposed correctly and includes all the required native CIs. For more information, see Exposing Web Service in Oracle PeopleSoft 9.1.

b. For Delta Import you must create Custom Component Interface (CI) using PeopleSoft Internet Architecture. For information on complete procedure, see Creating custom CIs in Oracle PS for Delta Import.

Content of Default Project

Web ServicesThe discovery operation retrieves the endpoint PSCONNECTORWEBSERVICE_Port and all the CIs that have been exposed through the web service at PeopleSoft. The exposed web service here includes only the native CIs listed below:

CI_USER_PROFILE_UP CI_USER_PROFILE_UD CI_USER_PROFILE_G CI_USER_PROFILE_C CI_ROLE_MAINT_UP CI_ROLE_MAINT_UD CI_ROLE_MAINT_G CI_ROLE_MAINT_F CI_ROLE_MAINT_C CI_DELETE_USER_PROFILE_UD CI_DELETE_USER_PROFILE_F CI_CI_PERSONAL_DATA_UP CI_CI_PERSONAL_DATA_UD CI_CI_PERSONAL_DATA_G CI_CI_PERSONAL_DATA_F CI_CI_PERSONAL_DATA_C

CI_CI_JOB_DATA_UP CI_CI_JOB_DATA_UD CI_CI_JOB_DATA_G CI_CI_JOB_DATA_F CI_CI_JOB_DATA_EMP_C

Important:There are few attributes that are defined for the default projects of each of the supported data source These are mandatory for calling the BAPIs/CIs/APIs successfully.Below is the list of these mandatory attributes:

Functions Attributes

CI_JOB_DATA taxLocationCodeCI_JOB_DATA_EMP

Workflows A native CI in PeopleSoft is used to perform a single task. There are certain operations for which native CIs are not available and hence the default project does not support them. But they can be configured with the help of custom CIs by including them in the web service and then configuring the required workflow. Following are the workflows that are supported for:

User Object

FIM Operation Implemented through native web service (CI) operation

Full Import Yes

Delta Import No

Export Add Yes (user can only be created without a password)

Export Delete Yes

Export Replace Yes

Set Password No

Change Password Not supported

Employee Object

FIM Operation Implemented through native web service (CI) operation

Full Import Yes

Delta Import No

Export Add Yes (Employee ID is provided by provisioning code)

Export Delete Yes

Export Replace Yes

Set Password N/A

Change Password N/A

Exposing Web Service in Oracle PeopleSoft HCM 9.1Web Service Configuration Tool discovers the Web service through a WSDL (Web Services Description Language) and retrieves its services, endpoints and operations (CIs) it provides. Services, endpoints and operations (CIs) are used by the Web Service Connector to access the Oracle PeopleSoft server and synchronize identities with Forefront Identity Manager (FIM) 2010.

For a web service to be discovered, it is first required to be exposed at the Oracle PeopleSoft 9.1. This topic describes the process of exposing the web service from Oracle PeopleSoft 9.1 UI. You must perform following activities to expose the web service at Oracle PeopleSoft server:1. Checking the connectivity and status of LOCAL Gateway2. Checking the configuration of PeopleSoft delivered Nodes3. Checking the Service Configuration Setup4. Checking Service Operation GETWSDL and Domain are Active5. Provide permissions to Component Interfaces (CIs) in PeopleSoft6. Creating CI Based Web Service7. Creating Single Web Service8. Exposing / Providing the Web Service

Checking the connectivity and status of LOCAL Gateway1. Login to PeopleSoft Application using URL (For ex:

http://<HostName>:<Port>/psp/HRMS91/EMPLOYEE/HRMS/?cmd=logout) and appropriate credentials.

2. Navigate the following path-Main Menu > PeopleTools > Integration Broker > Configuration > Gateways

Search with Gateway ID as LOCAL. Check the URL, it should be http://<HostName>:<Port>/PSIGW/PeopleSoftListeningConnector.

Click Ping Gateway, it should show Status ACTIVE.

3. Click Gateway Setup Properties. Enter standard login credential to logon:User ID: administrator and Password: password

4. Specify the PeopleSoft Application Server URL, userID and password for the same. You must also mention PeopleSoft Tools Release version that you are using. On the Nodes, specify the PeopleSoft Local Node. Verify Application Server URL, UserID and Password details with PeopleSoft Administrator.

Click Advanced Properties Page, to review the LOCAL Gateway advanced properties. You can choose to provide the encrypted password for the Application server and LOCAL Node and set

the flags for the Integration Broker log. You can encrypt the password in Password Encryption utility just below the advanced properties file.

You must check the following things in the advance properties file:1. Encrypted password: When you have encrypted the password you must then you must

enter the encrypted password in the sectionig.isc.serverURL=//<Host IP>:<Port>ig.isc.userid=PSig.isc.password={V1.1}6O5vpwGxd5o= ig.isc.toolsRel=8.51

ig.isc.PSFT_HR.serverURL=//<Host IP>:<Port>ig.isc.PSFT_HR.userid=PSig.isc.PSFT_HR.password={V1.1}6O5vpwGxd5o=ig.isc.PSFT_HR.toolsRel=8.51In this example both the password for the application server and the Local Node are same and encrypted.

2. Logging: In the Logging section of advance properties file you must check the logging level is set to 2.ig.log.level=2

3. Name and location of file used to output the message logs: It can be set to the same or different file as error logs location. For ex:ig.messageLog.filename=<drive>:/PSHOME/webserv/HRMS91/applications/peoplesoft/PSIGW.war/msgLog.html

4. Name and location of file used to output error logs: It can be set to the same or different file as message logs location. For ex:ig.errorLog.filename=<drive>:/PSHOME/webserv/HRMS91/applications/peoplesoft/PSIGW.war/errorLog.html

Checking the configuration of PeopleSoft delivered NodesThe web service exposing procedure requires configuration of two nodes viz. Sender and Receiver Nodes.

Checking the PeopleSoft delivered Sender Node1. The sender Node in PeopleSoft is PSFT_HR. It serves as the Default Local Node and all the

information is already defined in PeopleSoft. You must confirm the configuration against the below example screens to ensure that no changes have been made in the default settings. If there are deviations then correct them as shown in below example screens. Navigate the path Main Menu >PeopleTools> Integration Broker > Integration Setup > Nodes.

Open the node PSFT_HR by searching with Node Name. Enter Authentication Option as Password, Node Password and Default UserID as PS. In the properties there is an application

server password PS, you can choose to encrypt this password using Password Encryption utility.

Note: Default User ID, PS is the PeopleSoft User and must have access to permission list PTPT1200 to invoke the web service operations.You can confirm whether the logged on user (PS) has the permission list PTPT1200 assigned, by following below steps:Navigate through the path Main Menu >PeopleTools>Security> User Profiles > User Profiles

Search the User Id you have used to logon to PeopleSoft server and go to Roles tab. The list of Roles must display the PeopleTools permission.

2. Go to Connectors Tab on the path Main Menu > PeopleTools > Integration Broker > Integration Setup > Nodes and check the details.

3. Click Portal tab, and check the details.

4. Click WS Security tab and check the details.

Checking the PeopleSoft delivered Receiver Node

1. The receiver node in PeopleSoft is ANONYMOUS. It serves as the External node and is already configured. You must check the configuration to confirm if there are any deviation from the standard details, if yes then revert them back to the data in below shown example screens.Navigate the path Main Menu > PeopleTools > Integration Broker > Integration Setup > Nodes and open the node ANONYMOUS by searching with Node Name.

2. Enter Authentication Option as None and Default User ID as PS. ANONYMOUS is a PS delivered external node.

Note: Default User ID PS is the PeopleSoft User and must have access to permission list PTPT1200 to invoke the web service operations.

3. Click Connectors tab and check the details.

4. Click Portal and WS Security tab and check the details respectively.

5. On the WS Security tab, select the Authentication Token Type as Username Token which implies Basic Authentication method is applicable. Check the Encrypted check box and Encrypt Level should be All.

6. Go back to the Node Definitions tab and then enter values for External User ID and External Password. Press enter and confirm password. In the end click Save.

Checking the Service Configuration Setup1. Next step is to check the setup of service configuration. It is used to define the target Location

where the web service will be exposed.Navigate the pathMain Menu >PeopleTools> Integration Broker > Configuration > Service Configuration

You must specify the target location as http://<HostName>:<PortName>/PSIGW/PeopleSoftServiceListeningConnector

Checking Service Operation GETWSDL and Domain are ActiveIt is mandatory to check if the service operation GETWSDL is Active and has all the routings Active.

1. To check the same navigate the path

Main Menu > PeopleTools > Integration Broker > Integration Setup > Service Operations

2. Go to the Routings tab. You must specify the sender and receiver node. The Third Party System (FIM) sends request to the server with the help of sender node i.e. ANY, representing below the ANONYMOUS node.

3. In addition, you must also confirm that the PeopleSoft Application Server Domain Status is Active. Navigate the path Main Menu > PeopleTools > Integration Broker > Configuration > Quick Configuration

4. Click Domain Status on the above screen. The Status String will show ACT implies that the Domain is active.

Provide permissions to Component Interfaces (CIs) in PeopleSoftPeopleSoft Component Interfaces are defined to accomplish particular tasks utilized for managing the User and Employee data. These pre-configured CIs are assigned to the user to whom a particular permission is to be granted. Later these are packaged together in a web service and then exposed.The User Id (PS) used to logon to the PeopleSoft Internet Architecture (PIA) must have access to all the CIs. The steps to grant permissions to CIs are

1. Open the permission list associated with the User PS2. Add the CI and provide Full Access to all the methods.

Navigate the path

Main Menu > PeopleTools > Security > Permissions & Roles > Permission ListOpen the desired Component Interface to grant the Permissions as “Full Access” for all the methods as mentioned in the below screen examples. The same CIs must be opened.

USER_PROFILE

DELETE_USER_PROFILE

CI_PERSONAL_DATA

CI_JOB_DATA

CI_JOB_DATA_EMP

ROLE_MAINT

Creating CI Based Web ServiceYou must create a web service for each CI encapsulating the operations that web service is required to accomplish.

1. Navigate the pathMain Menu > PeopleTools > Integration Broker > Web Services > CI-Based Services and choose the CI to create web service.USER_PROFILE

2. Select the CI and click Review CI Status.

3. Select the operations you wish to create and click Display Selected Actions.

4. Click Perform Selected Actions.

As a result the operations are created for the selected CI.

Follow the same steps for all the CIs that you have granted Full Access permission.

DELETE_USER_PROFILE

Select the CI and Press “Review CI Status”.

Select the operations which needs to created and press Display Selected Actions.

Click Perform Selected Actions.

CI_PERSONAL_DATA

There can be cases where for particular CI, service already exists in the system. You can check the same by clicking Review CI status.

Status shows Service exists.

In case service does not exist, follow the wizard steps as shown above for the User Profile CIs.

CI_JOB_DATA

Status shows Service exists.

CI_JOB_DATA_EMP

Click Review CI Status.

Status shows “Service exists”.

ROLE_MAINT

Select the CI and Click Review CI Status:

Select the operations which needs to created and click Display Selected Actions.

Click Perform Selected Actions.

Creating Single Web ServiceThe web service created for each CI is separate and cannot be consumed by Web Service Configuration Tool for FIM. You must again package all the services in to one web service and expose them in the form of a single WSDL with all the required operations.

1. Create the new web service by clicking Add a New Value.

2. Add the description and then Save the service first.

3. After saving the service, use Link Existing Operations link in order to add the required operations one by one as shown:

4. Look out for the required existing Service operation and then click Search:

Select the operation and Save.

5. Again click Link Existing Operations” for adding next operation. Add all the operations you want to link in the service.

Save the service.

Inside the web service, open each service operation by clicking the service operation link one by one:

Check and follow the following 3 steps:

1> Operation is Active and User/Password Required check box is checked. User/Password Required is used to implement the Basic Authentication.

2> Routings are Active

3> Provide Service operation SecurityAll the web operations must be provided the security permission list of PTPT1200, in order the User PS to access/invoke all the web operations successfully.

Open “Service Operation Security” link for that service operation:

New Pop Up window will get open, add Permission List “PTPT1200” and give “Full Access”. Save.

Return to the web service from the service operation by clicking the link “Return to Service”.

Follow the above 3 steps for all the service operations present inside the web service you created one by one.

You can verify that all the operations have permission list PTPT1200 by opening the same:

Open “Web Services” link:

You can see the name of your web service. Open “Edit”: All the service operations should be there with Full Access.

Press OK and save the Permission List.

Exposing / Providing the Web ServiceNavigate the path

Main Menu > PeopleTools > Integration Broker > Web Services > Provide Web Service

Click “Next”. You will get the following screen:

Select all the operations and click “Next”.

Again click “Next”.

Select WSDL repository and click “Finish”.

WSDL generated and has been inserted in the repository.

Creating Custom CIs in Oracle PeopleSoft for Delta ImportThis topic describes how to create custom component interfaces and expose them after encapsulating in a web service through Oracle PeopleSoft Internet Architecture 9.1. The exposed web service is consumed by the Web Service Configuration Tool that is integrated with Microsoft Forefront Identity Manager (FIM) Synchronization Service 2010. It will perform the delta import operation triggered in FIM UI and configured as a workflow in Web Service Configuration Tool.For more information of Workflows in Web Service Configuration Tool see, Workflows in Web Service Configuration Tool.This topic covers the delta import of two types of identities viz. Employee and User. Below is the sequence of steps that you should follow to configure:

1. Creating the Input and Output message structure and SQL View to fetch the identity data and last updated date and time

2. Creating Request message in PeopleSoft / Pure Internet Architecture3. Creating Response message in PeopleSoft / Pure Internet Architecture4. Creating Web Service and write handler / custom program segment5. Attaching handler program to Service Operation6. Exposing / Providing the Web Service

Delta Import - EmployeeThis section describes the process of creating custom CIs for delta import of Employees. Logon to the PeopleTool s and open the Application Designer. It is used to define schema of messages and writing custom / handler code.

Creating Input and Output message structure a. Application designer for Input message structure:

Create input record in the Application designer.

The Record Type should be SQL Table.

Save and build the record.

b. Application designer for Output message structure:

Create the output record of Type, SQL Table in the Application designer.

Save and build the record.

c. Creating the view for fetching the data as per the requirement.

As per the requirement, you need to load view with the EMPLID along with the last updated Date Time (the EMPLID gets updated if there is change in Job data, personal details, name, address etc.).

Here the Record Type should be SQL View.

d. Press, Click to open SQL Editor and paste the following SQL code snippet to load the view. This view will retrieve the last updated dat-time and emp id from all the employee related tables.

Code:

SELECT A.EMPLID , A.LASTUPDDTTM , B.LAST_CHILD_UPDDTM , C.LASTUPDDTTM , D.LASTUPDDTTM , E.LASTUPDDTTM

FROM PS_JOB A , PS_PERSON B , PS_NAMES C , PS_ADDRESSES D , PS_PERSONAL_DATA E WHERE A.EFFDT = (SELECT MAX(A_ED.EFFDT) FROM PS_JOB A_ED WHERE A.EMPLID = A_ED.EMPLID AND A.EMPL_RCD = A_ED.EMPL_RCD AND A.EFFSEQ = A_ED.EFFSEQ AND A_ED.EFFDT <= SYSDATE) AND A.EFFSEQ = (SELECT MAX(A_ES.EFFSEQ) FROM PS_JOB A_ES WHERE A.EMPLID = A_ES.EMPLID AND A.EMPL_RCD = A_ES.EMPL_RCD AND A.EFFDT = A_ES.EFFDT) AND A.EMPLID = B.EMPLID AND A.EMPLID = C.EMPLID AND C.EFFDT = (SELECT MAX(C_ED.EFFDT) FROM PS_NAMES C_ED WHERE C.EMPLID = C_ED.EMPLID AND C.NAME_TYPE = C_ED.NAME_TYPE AND C_ED.EFFDT <= SYSDATE) AND A.EMPLID = D.EMPLID AND D.EFFDT = (SELECT MAX(D_ED.EFFDT) FROM PS_ADDRESSES D_ED WHERE D.EMPLID = D_ED.EMPLID AND D.ADDRESS_TYPE = D_ED.ADDRESS_TYPE AND D_ED.EFFDT <= SYSDATE) AND A.EMPLID = E.EMPLID

Creating the Request message in PeopleSoft / Pure Internet Architecture (PIA)

a. Logon to PIA and navigate the path Main Menu > PeopleTools > Integration Broker > Integration Setup > Messages. Click Add a New Value.

b. Enter the input message name created in application designer, by entering the Type as Rowset and Message Name. Click Add.

c. Click Add Record to Root link and specify input record you created.

d. Click OK. The system will redirect you to previous page.

e. Click Save.

Creating the Response message in PeopleSoft / Pure Internet Architecture (PIA)a. Logon to PIA and navigate the path Main Menu > PeopleTools > Integration Broker >

Integration Setup > Messages. Click Add a New Value.

b. Enter the output message name created in application designer, by entering the Type as Rowset and Message Name. Click Add.

c. Click Add Record to Root link and specify output record you created.

d. Click OK. The system will redirect you to previous page.

e. Click Save.

Creating Web Service and preparing Handler / Custom Code

1. Navigate the path Main Menu > PeopleTools > Integration Broker > Integration Setup > ServicesClick Add a New Value. Enter the Service name and click Add.

Now create the service operations for delta Import by adding like this:

Click the “Add” button:

Specify:

Operation Description, Version description and tick the check box for “Generate Any-to-Local”. Also provide with the Request and Response message name. Save the service operation.

“Return to service” and save the service.

HANDLER/CUSTOM CODEIn the Application designer, create the Application package for writing the custom code for processing according to i/p received and generate the o/p:

Write the code as below:

Code:

importPS_PT:Integration:IRequestHandler;class CUST_EMP_CLASS1 implements PS_PT:Integration:IRequestHandlermethod CUST_EMP_CLASS1();methodOnRequest(&message As Message) Returns Message;end-class;

/* constructor */method CUST_EMP_CLASS1 %Super = create PS_PT:Integration:IRequestHandler();end-method;

methodOnRequest /+ &message as Message +/ /+ Returns Message +/ /+ Extends/implements PS_PT:Integration:IRequestHandler.OnRequest +/

Local Rowset&rs;

Local Message &MSG; Local string &RES_EMP, &STR;

&rs = &message.GetRowset(); Local string &UPD = &rs.GetRow(1).GetRecord(Record.CUST_EMP_IN1).LASTUPDDTTM.Value;

Local array of string &BOTH;&BOTH = CreateArray("");

Local SQL &sql = CreateSQL("Select EMPLID from PS_CUST_EMP_VW1 where (JOB_UPD > :1) OR (PER_UPD > :2) OR (NAME_UPD > :3) OR (ADDRESS_UPD > :4) OR (PERSONAL_UPD > :5) order by EMPLID", &UPD, &UPD, &UPD, &UPD, &UPD);

While &sql.Fetch(&RES_EMP)&BOTH.Push(&RES_EMP); End-While;

Local string &SHF = &BOTH.Shift();&STR = &BOTH.Join(); Local Message &response = CreateMessage(Operation.CUST_EMP1_OP1, %IntBroker_Response);&response.GetRowset().GetRow(1).GetRecord(Record.CUST_EMP_OUT1).GetField(Field.DATACHUNK).Value = &STR; Return &response;end-method;

Attaching handler program to Service OperationOpen the Service operation “CUST_EMP1_OP1” and go to the “Handler” tab:

Specify any name for Handler; provide the Type, Implementation & status as shown above.

Click “Details” link and on the page specify the handler description, package name, path, class ID & method as shown below:

Click OK and return to the “General” tab:

Click OK and save the service operation. Also provide “Service operation security”; New Pop Up window will get open, add Permission List “PTPT1200” and give “Full Access”. Save.

Save the service operation.

Delta Import - UserThis section describes the process of creating custom CIs for delta import of User. Logon to the PeopleTools and open the Application Designer. It is used to define schema of messages and writing custom / handler code.

The o/p record structure & thus the response message for User:

Create the new Service operation for user in the existing service:

Application package for the User:

Code:

importPS_PT:Integration:IRequestHandler;

class CUST_USE_CLASS1 implements PS_PT:Integration:IRequestHandlermethod CUST_USE_CLASS1();methodOnRequest(&message As Message) Returns Message;end-class;

/* constructor */method CUST_USE_CLASS1 %Super = create PS_PT:Integration:IRequestHandler();end-method;

methodOnRequest /+ &message as Message +/ /+ Returns Message +/ /+ Extends/implements PS_PT:Integration:IRequestHandler.OnRequest +/

Local Rowset&rs; Local Message &MSG; Local string &RES_EMP, &STR;

&rs = &message.GetRowset(); Local string &UPD = &rs.GetRow(1).GetRecord(Record.CUST_USE_IN1).LASTUPDDTTM.Value;

Local array of string &BOTH;&BOTH = CreateArray("");

Local SQL &sql = CreateSQL("SELECT OPRID FROM PSOPRDEFN WHERE LASTUPDDTTM >= :1 ORDER BY OPRID", &UPD);

While &sql.Fetch(&RES_EMP)&BOTH.Push(&RES_EMP); End-While;

Local string &SHF = &BOTH.Shift();&STR = &BOTH.Join(); Local Message &response = CreateMessage(Operation.CUST_USE1_OP1, %IntBroker_Response);&response.GetRowset().GetRow(1).GetRecord(Record.CUST_USE_OUT1).GetField(Field.DATACHUNK).Value = &STR; Return &response;end-method;

Attach the handler code:

Service operation security:

Exposing / Providing the Web Service

Web Service Configuration Tool discovers the Web service through a WSDL (Web Services Description Language) and retrieves its services, endpoints and operations (CIs) it provides. Services, endpoints and operations (CIs) are used by the Web Service Connector to access the Oracle PeopleSoft server and synchronize identities with Forefront Identity Manager (FIM) 2010.

For a web service to be discovered, it is first required to be exposed at the Oracle PeopleSoft 9.1. To perform the complete process of exposing web service in Oracle PeopleSoft server, see Exposing Web Service in Oracle PeopleSoft 9.1

Performance TestingScale Topology Hardware

10,000 User objects data

10,000 Person objects data

Two servers

FIM Synchronization Service and FIM Synchronization database collocated on one server (FIM Server).

Oracle PeopleSoft Application

FIM Server Hardware Configuration:

2-gigabyte (GB) SDRAM

Intel® Xeron® 2.27GHz Processor

Server Hard disk volumes:

o Single volume

Note: The server hardware used is not representative for a large organization. The numbers presented should be used to understand the difference between different operations. You are encouraged and expected to configure your own test environments to more accurately estimate capacity and performance. Microsoft cannot guarantee that organizations will experience the same capacity or performance characteristics, even if the FIM Synchronization service components are deployed and configured identically to the components that are described in this guide,

The tests and results shown in the following table were performed using scripted provisioning code.

Operation Elapsed time (minutes: seconds) Statistics Rate

PeopleSoft Connector Full Import (User Object)

58:21 Total Imported users:10,000

2.85 objects read/ second

PeopleSoft Connector Full Import (Person Object)

312:07 Total Imported Persons:10,000

0.53 objects read/ second

PeopleSoft Connector Delta Import (User Object)

255:37 Update: 10,000 Users .65 objects updated/ second

PeopleSoft Connector Delta Import (Person Object)

305:49 Update: 10,000 Persons 0.55 Objects updated/ second

PeopleSoft Connector Export (UserObject)

a) 436:18b) 255:37c) 2730:27

a) Adds: 10,000 Usersb) Update: 10,000

Usersc) Delete: 10,000

Users

a) 0.38 Objects exported / second

b) .65 Objects updated/ second

c) .06 Objects deleted / second

PeopleSoft Connector Export (Person Object)

a) 268:49b) 305:49c) 464:15

a) Adds: 10,000 Persons

b) Update: 10,000 Persons

c) Delete:10,000 Persons

a) 0.62 Objects exported/ second

d) 0.55 Objects updated/ second

b) .36 Objects deleted / second

Reference information