Setting Up Integration Between PeopleSoft CRM and PIM Clients

This chapter discusses how to:

Define dataset rules and roles.
Set up PIM preferences.
Set up PIM user settings.
Install PeopleSoft Infosync Client.
Set up Integration Broker.
Specify conflict resolution rules.
Modify synchronization settings.

Note. This chapter covers all the tasks that are involved in setting up the integration between PeopleSoft CRM and PIM clients. Administrators can take full advantage of the system-delivered data that is predefined for some tasks (for example, dataset rules, dataset roles, PIM preference, and so on), or they can modify and create new rules and preferences that best fit their business needs.

Defining Dataset Rules and Roles

This section provides an overview of discusses how to:

Define dataset rules.
Define dataset roles.

A dataset is a collection of dataset rules that are used to determine what data end users receive on their PIM clients as a result of synchronization. In the integration setup process, you define the relationship between end users and dataset rules using this logic:

Each user is associated with a PIM preference.
Each PIM preference specifies a dataset role for each synchronization object (contact, consumer, worker, calendar, and task).
Each dataset role is associated with a dataset (group of dataset rules) for each synchronization object.

When synchronization completes, end users receive updates on data based on the associated dataset rules. For example, suppose that you use the system-delivered dataset rules for synchronizing sales user tasks. After synchronization, the updates that sales users get for the task object come from their own tasks (rule: MY TASKS), tasks that are assigned to their leads (rule: TASKS ON MY LEADS), and opportunities (rule: TASKS ON MY OPPORTUNITIES). PeopleSoft delivers predefined datasets and dataset rules for this integration. You can modify them or create custom dataset rules to work with your implementation.

Note. If an end user is no longer associated with a contact, consumer, or worker (for example, a sales user reassigns a lead task to another person and therefore does not receive any updates about the lead's contacts from the CONTACTS_FOR_LEAD_TASK_ASSIGNEE dataset rules), the record is removed from the end user's address book.

Pages Used to Define Dataset Rules and Roles

Page Name	Object Name	Navigation	Usage
Dataset Rules	EOEC_DATASET	Enterprise Components, Component Configurations, Datasets, Dataset Rules	Define rules that comprise a dataset. Dataset rules are associated with users through dataset roles; they are used in the synchronization process to determine what data gets updated in PeopleSoft CRM and the PIM client.
PIM Dataset Roles	PIM_ROLE	Set Up CRM, Install, PIM, PIM Dataset Role	Define dataset roles and associate them with dataset rules.

Defining Dataset Rules

Access the Dataset Rules page.

Rule

Enter the name of the rule. When you save the page, this field becomes unavailable.

Search Record Name

Enter the name of the search record for this rule. You can create a view specifically for use in the rule.

((... and ))...

If you leave the AND or OR field blank, specify the nesting level for this condition. Be sure to match opening and closing parentheses.

Field Name

Select the field name on which this rule operates from the drop-down list of fields in the selected component.

Operator

Specify the operation with which to compare the specified field value. Select from standard conditional operators.

Field Value

Enter the value of the specified field against which to compare.

Test SQL (test structured query language button)

Click this button to test the validity of the rule conditions. The result is returned below the button.

Show SQL (show structured query language)

Click this button to view the SQL statement generated by the rule.

See Also

Defining Dataset Rules

PeopleSoft 8.9 Enterprise Components PeopleBook

Defining PIM Dataset Roles

Access the PIM Dataset Roles page.

The system delivers two PIM dataset roles: thePIM Field Service Role and the PIM Sales Role.

Dataset Name

Select a dataset for each synchronizable object: contact, consumer, worker, task, and calendar. All of the rules that are associated with this dataset are then available in the Rule grid.

Rule

Select a dataset rule that is applicable to this role.

Note. You can update, add, or remove rules from datasets for PIM roles. For example, if sales users prefer not to see tasks that are assigned to other users (even though the tasks belong to their leads and opportunities), administrators can delete the TASKS ON MY LEADS and TASKS ON MY OPPORTUNITIES rules from the task dataset of the PIM sales role.

See Also

Defining Dataset Rules

PeopleSoft 8.9 Enterprise Components PeopleBook

Setting Up PIM Preferences

This section discusses how to:

Specify overall PIM preference.
Specify PIM preference for contacts.
Specify PIM preference for consumers.
Specify PIM preference for workers.
Specify contact method mapping.
Specify PIM preference for calendar items.
Specify PIM preference for tasks.

Note. When you configure PIM preferences, consider it a one-time implementation process. Avoid changing PIM preferences after PeopleSoft Infosync Client is in production.

Pages Used to Set Up PIM Preferences

Page Name	Object Name	Navigation	Usage
Setup	PIM_PREFERENCE_PG1	Set Up CRM, Install, PIM, PIM Preferences, Setup	Specify the PIM application type for end users who take this PIM preference.
Contact	PIM_PREF_CONTACT	Set Up CRM, Install, PIM, PIM Preferences, Contact	Specify the synchronization preference for contacts.
Consumer	PIM_PREF_CONSUMER	Set Up CRM, Install, PIM, PIM Preferences, Consumer	Specify the synchronization preference for consumers.
Worker	PIM_PREF_WORKER	Set Up CRM, Install, PIM, PIM Preferences, Worker	Specify the synchronization preference for workers.
Address	PIM_PREF_ADDRESS	Set Up CRM, Install, PIM, PIM Preferences, Address	Specify contact method mapping for contacts, consumers, and workers.
Calendar	PIM_PREF_CALENDAR	Set Up CRM, Install, PIM, PIM Preferences, Calendar	Specify the synchronization preference for calendar items.
Task	PIM_PREF_TASK	Set Up CRM, Install, PIM, PIM Preferences, Task	Specify the synchronization preference for tasks.

Specifying PIM Preference

Access the Setup page.

PIM Preference ID

Enter the name of the PIM preference that is being defined. Associate each user with a PIM preference by specifying a PIM preference ID in the user preference on the Overall Preferences page.

See Associating PIM Preferences with Users.

Debug

Select to allow more specific information (for example, technical errors and message logs that are sometimes not end-user friendly) to be captured and displayed on the PIM Errors page. This is useful for administrators to debug and troubleshoot the application.

PIM Application Type

Information that is entered in this group box pertains to PeopleSoft Infosync Server and does not apply to PeopleSoft Infosync Client. However, PeopleSoft recommends that you select the PIM application type.

PIM Application Type

Select the type of PIM server (Lotus Domino or Microsoft Exchange server) that is used by PIM clients:Domino Server (default) and Exchange Server.

General Settings

Information that is entered into this group box pertains to PeopleSoft CRM.

PIA URI

Enter web server information to generate a URI on the contact page in PIM. This URI takes the end user to the associating Contact record in the 360 Degree View. If your web server address includes a port number, also include this in the address.

Note. A URI does not include the content information in the link. Think of it as a subset of the URL that points to the location of the resource, but does not include any parameters passed to that resource.

PIA Portal

Enter the level of portal access that PIM users will have.

PIA Node

Enter the PIA node that your system uses for integration.

Specifying PIM Preference for Contacts

Access the Contact page.

Contact

Specifies the synchronization preference that applies to contacts.

Contact Role Name	Select the role for which the PIM preference is created. Dataset roles are defined on the PIM Roles page.
Add Contact, Update Contact, and Delete Contact	Select to provide end users who are associated with this preference the ability to add, update, and delete contacts from their address books and to synchronize the change in PeopleSoft CRM. If any of these operations is disabled, any end user who tries to synchronize a contact to PeopleSoft CRM through the unauthorized operation receives an error message on screen and on the PIM Errors page. The corresponding contact in PeopleSoft CRM is not impacted and is used to roll back to the end user's address book at next synchronization. However, if a user adds or updates a contact directly from PeopleSoft CRM, the change is synchronized to the PIM client and is available to end users who receive updates on this contact (based on dataset rules). This is because the add, update, and delete operation settings do not control data flow originating from PeopleSoft CRM to PIM clients. Note. You cannot delete contacts from PeopleSoft CRM.
Allow Add with Invalid Company	Select to allow newly created contacts to be synchronized to PeopleSoft CRM even if they are associated with companies that do not exist in PeopleSoft CRM. When that happens, PeopleSoft Infosync Client sends a message to end users stating that the invalid company is ignored while the contact is synchronized to PeopleSoft CRM. That means that the contact is added to PeopleSoft CRM without a company. If this feature is disabled, end users get an error message if they try to synchronize any newly created contact with an invalid company name; the contact is not synchronized.
Support Multiple Companies and Company Separator	Select to allow synchronization to support a one-to-many relationship between contacts and companies. From the address book, end user can enter multiple companies for a contact in this format: <company1>;<company2>;<company3> where ; (semicolon) is the default company separator. Do not enter space between a company name and separator. When the contact record is synchronized to PeopleSoft CRM, it is associated with companies that were previously specified in the PIM client. In the PIM client, the company that has the longest relationship with the contact ranks the first in the array of companies. If a new company is added to the contact in PeopleSoft CRM, the new company appears at the end of the list after synchronization. If you add a new company to the contact in the address book and put the new company in the front, it is automatically placed at the end at next synchronization. If this feature is disabled, the synchronization process only handles the newest company relationship. If the end user clears the company field in a contact record, the current relationship becomes inactive; if the end user updates the company name to a new one, the relationship with the new company becomes active. The old company remains in the contact record, and it is no longer synchronized. By default, this feature is disabled. To enter multiple companies for a contact in Lotus Notes, click the drop-down list box for the Company field and enter the companies (in a formatted manner) in the New keyword field. Note. PeopleSoft highly recommends that you consider this configuration a one-time setup process and not make changes to it after implementation.
Contact Category	Enter a category that is used by PeopleSoft Infosync Client to identify which contacts in the PIM client to synchronize. The contact category that you specify in this field has to be identical to the one that end users use to categorize contacts in the address book. Contacts that don't belong to this category are not synchronized. You can change the category name to anything during setup, but make sure that the filter and the category mapping are updated as well. The default value is Contact.

Contact 360 Degree View

Select to enable the Contact URL to be synchronized to the PIM Client. The URL address is specified using the PeopleSoft CRM URL field on the Setup page of the PIM Preferences component. If this is disabled the URL will not be synchronized.

Note. You must associate the contact with a company for this URL to link to the contact.

My Contacts List

Specifies the synchronization preference that is specific to My Contact List.

Add

Select to enable contacts to be added to the PIM Client.

Delete

Select to enable contacts to be deleted from the PIM Client.

Specifying PIM Preference for Consumers

Access the Consumer page.

Consumer

Specifies synchronization preferences that are specific to consumers.

Enable Consumer	Select to enable contacts (with a consumer-specific category) in the address book to be synchronized as consumers in PeopleSoft CRM. Clear this check box to deactivate the rest of the page (if you decide not to support synchronization of consumers). End users who are associated with this PIM preference get an “object type not enabled” error message on screen and on the PIM Errors page when they try to synchronize consumers to PeopleSoft CRM.
Consumer Role Name	Select the role for which the PIM preference is created. Dataset roles are defined in the PIM Roles page.
Add Consumer, Update Consumer, and Delete Consumer	Select to provide users who are associated with this preference the ability to add, update, and delete consumers (as a type of contacts) from their address books and synchronize the change in PeopleSoft CRM. If any of these operations is disabled, any end user who tries to synchronize a consumer to PeopleSoft CRM through the unauthorized operation will receive an error message on screen and on the PIM Errors page. The corresponding consumer in PeopleSoft CRM is not impacted and is used to roll back to the end user's address book at the next synchronization. However, if a user adds or updates a consumer directly from PeopleSoft CRM, the change is synchronized to the PIM client and is available to all end users who receive updates on this consumer (based on dataset rules). This is because the add, update, and delete operation settings do not control data flow originating from PeopleSoft CRM to PIM clients. Note. You cannot delete consumers from PeopleSoft CRM.
Consumer Category	Enter a category that is used by PeopleSoft Infosync Client to identify which consumers in the PIM client are to be synchronized. The consumer category that you specify in this field has to be identical to the one end users use to categorize consumers in the address book. Contacts that don't belong to this category are not synchronized as consumers in PeopleSoft CRM. You can change the category name to anything during setup, but make sure the filter and the category mapping are updated as well. The default value is Consumer.
Consumer 360 Degree View	Select to allow the consumer URL to be synchronized to the PIM Client. The URL address is specified using the PIA URL field on the Setup page of the PIM Preferences component. If this is disabled, the URL won't be synchronized. Note. You must associate the consumer with a company for this URL to link to the consumer.

My Contacts List

Specifies the synchronization preference that applies to My Contact List.

Add

Select to enable consumers to be added to the PIM Client.

Delete

Select to enable consumers to be deleted from the PIM Client.

Specifying PIM Preference for Workers

Access the Worker page.

Worker

Specifies the synchronization preference that applies to workers.

Enable Worker	Select to enable contacts (with a worker specific category) in the PIM client to be synchronized as workers in PeopleSoft CRM. Clear this check box to deactivate the rest of the page (if you decide not to support synchronization of workers). End users who are associated with this PIM preference get an “object type not enabled” error message when they try to synchronize workers to PeopleSoft CRM.
Worker Role Name	Select the role for which the PIM preference is created. Dataset roles are defined on the PIM Roles page.
Update Worker and Delete Worker	Select to provide end users who are associated with this preference the ability to update and delete workers (as a type of contacts) from their address books and to synchronize the change in PeopleSoft CRM. If any of these operations is disabled, any end user who tries to synchronize a worker to PeopleSoft CRM through the unauthorized operation will receive an error message on screen and on the PIM Errors page. The corresponding worker in PeopleSoft CRM is not impacted and is used to roll back to the end user's address book at next synchronization. However, if a user updates a worker directly from PeopleSoft CRM, the change is synchronized to the PIM client and is available to end users who receive updates on this worker (based on dataset rules). This is because the update and delete operation settings do not control data flow originating from PeopleSoft CRM to PIM clients.
Worker Category	Enter a category that is used by PeopleSoft Infosync Client to identify which workers in the PIM client are to be synchronized. The worker category that you specify in this field has to be identical to the one that you use to categorize workers in the PIM client. Contacts that don't belong to this category are not synchronized as workers. You can change the category name during setup, but make sure that you update the filter and the category mapping as well. The default value is Worker.
Secure Home Contact Methods	Select to prevent worker's home contact information from being synchronized to the PIM client. This includes the phone number, address, and email that has Home as the purpose and that has Pager 1 or Page 2 as the purpose in PeopleSoft CRM. For example, if you map the business address type (PIM client) to the home address type (PeopleSoft CRM) on the Address page of the PIM preference, the business address in the PIM client is never synchronized. Home contact information in PeopleSoft CRM is secured: it doesn't take updates from the PIM client (no permission error occurs) and is not synchronized to the PIM client. This feature is enabled by default. If this check box is clear, the worker's home contact information still isn't synchronized to the PIM client. However, any update on it from the PIM client is synchronized to PeopleSoft CRM. You cannot see the change because of the security that is enforced for worker information in PeopleSoft CRM. Note. In order for end users to add home contact information for a worker from the PIM client and to synchronize the information to PeopleSoft CRM, the Secure Home Contact Methods feature must be disabled and end users must have a secured worker role. Set up secured worker roles on the Secured Worker Role page.Set Up CRM, Security, Secured Worker Role.
Worker 360 Degree View	Select to allow the Worker URL to be synchronized to the PIM Client. The URL address is specified using the PIA URL field on the Setup Page of the PIM Preferences page. If this is disabled the URL will not be synchronized. Note. The worker must be associated with a company for this URL to link to the worker.

My Contacts List

Specifies the synchronization preference that is specific to My Contact List.

Add

Select to allow workers to be added to the PIM Client.

Delete

Select to allow workers to be deleted from the PIM Client.

Specifying Contact Method Mapping

Access the Address page.

Addresses and Phones

Home Address Type, Business Address Type, and Other Address Type	Enter contact method purposes (defined in PeopleSoft CRM) that home, business, and other addresses in the PIM client are mapped to in PeopleSoft CRM after synchronization. A contact method purpose indicates when to use the specified contact method. For example, you typically send business-related correspondence to a contact using the contact's business address. To deliver an urgent document to the contact after office hours, you can use the home address. The default contact method purposes for home, business, and other address types are Home, Business, and Other. If you change the address types, the next synchronization becomes an initial synchronization. Note. The Other address type is applicable to Microsoft Outlook only.
Primary Address Type	Select the primary address type: Home, Business, or Other. If a contact has multiple addresses, the one that belongs to this address type becomes the primary address for the contact in PeopleSoft CRM.
Home Phone Type, Business Phone Type, and Other Phone Type	Enter contact method purposes (defined in PeopleSoft CRM) that home, business, and other phones in the PIM client are mapped to in PeopleSoft CRM after synchronization. The default contact method purposes for home, business, and other phone types are Home, Business, and Other. Note. The other phone type is applicable to Microsoft Outlook only.
Phone Ext (phone extension)	Enter a prefix for phone extensions. PeopleSoft Infosync Client supports phone extensions in all phone types.

Specifying PIM Preference for Calendar Items

Access the Calendar page.

Calendar

Specifies the synchronization preference that is specific to calendar items.

Calendar Role Name

Select the role for which the PIM preference is created. Dataset roles are defined on the PIM Roles page.

Add Calendar, Update Calendar, and Delete Calendar	Select to provide users who are associated with this preference the ability to add, update, and delete items from the calendar and to synchronize the change in PeopleSoft CRM. If any of these operations is disabled, any end user who tries to synchronize a calendar item to PeopleSoft CRM through the unauthorized operation will receive an error message on screen and on the PIM Errors page. The corresponding calendar item in PeopleSoft CRM is not impacted and is used to roll back to the end user's calendar at next synchronization. If an end user adds, updates, or deletes a calendar item directly from PeopleSoft CRM, the change is synchronized to the PIM client and is available to end users who receive updates on this calendar item (based on dataset rules), regardless of the selection. This is because the add, update, and delete operation settings do not control data flow originating from PeopleSoft CRM to PIM clients.
Task Type on PIA with Time	Select a Task Type that will be associated with a time.
Task Type on PIA without Time	Select a Task Type that will not be associated with a time.
Task Notes Sync Option	Select Concatenate or Most Recent to view the Task Notes.
Add Notes Begin Delimiter and Add Notes End Delimiter	Define a beginning and ending delimiter that defines where the task note begins and ends. The note description field in the PIM Client shows these delimiters to define where the note text must be added. PeopleSoft recommends that you use only characters, numbers, or dashes.
Calendar Category	Enter a category that is used by PeopleSoft Infosync Client to identify which items in the calendar are to be synchronized. The calendar category that you specify in this field has to be identical to the one that you use to categorize calendar items in the PIM Client. Calendar items that don't belong to this category are not synchronized. You can change the category name during setup, but make sure that you also update the filter and the category mapping. The default value is PeopleSoft.

Specifying PIM Preference for Tasks

Access the Task page.

Task

Specifies the synchronization preference that applies to tasks.

Task Role Name	Select the role for which the PIM preference is created. Dataset roles are defined on the PIM Roles page.
Add Task, Update Task, and Delete Task	Select to provide users who are associated with this preference the ability to add, update, and delete tasks from the to-do list and synchronize the change in PeopleSoft CRM. If any of these operations is disabled, any end user who tries to synchronize a task to PeopleSoft CRM through the unauthorized operation will receive an error message on screen and on the PIM Errors page. The corresponding task in PeopleSoft CRM is not impacted and is used to roll back to the end user's to-do list at next synchronization. However, if a user adds, updates, or deletes a task directly from PeopleSoft CRM, the change is synchronized to the PIM client and is available to end users who receive updates on this task (based on dataset rules). This is because the add, update, and delete operation settings do not control data flow originating from PeopleSoft CRM to PIM clients.
Task Type on PIA	Select a Task Type that will be associated with a task in PeopleSoft.
Task Notes Sync Option	Select Concatenate or Most Recent to view the Task Notes on the PIM Client.
Add Notes Begin DelimiterAdd Notes End Delimiter	Enter a beginning and ending delimiter that defines where the task note begins and ends. The note description field in the PIM Client shows these delimiters to define where the note text must be added. PeopleSoft recommends that you use only characters, numbers, or dashes.
Task Category	Enter a category that is used by PeopleSoft Infosync Client to identify which tasks in the to-do list are to be synchronized. The task category that you specify in this field has to be identical to the one that end users use to categorize tasks in the PIM client. Tasks that don't belong to this category are not synchronized. You can change the category name, but make sure that you also update the filter and category mapping. The default value is PeopleSoft.

Setting Up PIM User Settings

This section discusses how to associate PIM preferences with users.

Pages Used to Set Up PIM User Settings

Page Name	Object Name	Navigation	Usage
Users	PIM_PREF_USERS	Set Up CRM, Install, PIM, PIM Preferences, Users	Associate end users with or disassociate end users from the PIM preference.
Overall Preferences	OPR_DEF_TABLE_RB1	Set Up CRM, Security, User Preferences, Overall Preferences	Associate users with the PIM preference.

Associating PIM Preferences with Users

Access the Users page.

Note. You can associate PIM preference with users by accessing either the Users page or the Overall Preferences page.

User ID

Click to select the PeopleSoft user ID of end users to be associated with the given PIM preference. You can add or delete end users from the list as necessary. If you add a new user who is currently linked to another PIM preference, doing so associates the user with the new PIM preference.

Complete the prerequisite on saving the user preference record for each PIM end user; otherwise, all of the user IDs may not be available for selection.

Last Sync Date (last synchronization date)

Displays the date and time when the last synchronization occurred. The last transaction date for different end users varies upon whether data updates actually occurred between PeopleSoft CRM and the PIM client. If there's no data update for some end users after synchronization, their last synchronization date displays an earlier time stamp than other users who have just received data update.

Access the Overall Preferences page.

SetID

Enter a setID for the end user. This setID is used as the default setID for consumers (created by the end user in the PIM client) as the records are synchronized in PeopleSoft CRM (if sales business units are not applicable to that end user).

Localization Country

Enter a country code for the user.

Note. You must specify this value for PIM end users because PeopleSoft Infosync Client uses it as a default value in scenarios where a user adds a contact in the address book but forgets to enter a country for the contact. When synchronization occurs, the process populates the contact's missing country value with the localization country value of the end user (who creates the contact); otherwise, the user receives synchronization errors.

PIM Preference ID

Select a PIM preference with which the user is associated. When synchronization occurs, the process verifies the user's PIM preference and dataset rules that are associated with that preference to determine what data gets updated in the PIM client for the user. Set up PIM preference using the PIM Preferences component.

See Also

Defining Overall Preferences

Installing PeopleSoft Infosync Client

Refer to the supplemental installation instructions for PeopleSoft Infosync Client for information on how to install the client application. This document is available on Customer Connection. Select Support, Documentation, Documentation Updates, Customer Relationship Management, All in Selected Product Line.

Additional Note for Installing PeopleSoft Infosync Client

After client installation is complete, you must configure the client. When you are in the Choose Translator dialog box to select which PIM application to run, these three operations are available for selection: Import, Export and Synchronize.

Select Import for the integration to perform one-way data update from the PIM Client to PeopleSoft CRM.
Select Export for the integration to perform one-way data update from PeopleSoft CRM to the PIM Client.
Select Synchronize for the integration synchronize data between PeopleSoft CRM and the PIM client.

Setting Up Integration Broker

A complete Integration Broker setup is provided as part of PeopleSoft Infosync Client. This setup synchronizes data between PeopleSoft CRM and PIM clients. The setup delivers these Integration Broker objects, which are used in this integration:

Two nodes: PSFT_INFOSYNC and PSFT_PIM.
One transaction message: PIM_CONTACT_SYNC.
Two codesets for data translation: INFOSYNC TO PIM and PIM TO INFOSYNC.

PeopleSoft recommends that you perform these tasks before using Integration Broker:

Change the default password that is used in the external node (that is, PSFT_PIM) by selectingPeopleTools, Integration Broker, Node Definitions.

After you've changed the password on the Node Info page, do the same to the URI parameter in the DCSSettings.cfg file.
Modify the IntegrationGateway.properties file under PSIGW\WEB-INF:
- If the integration gateway supports only one database, set up the IntegrationGateway.Properties file with the default application server like this:
```
ig.isc.serverURL=//<yourappserver:jsl_port>
ig.isc.userid=VP1
ig.isc.password=JekncVtPdNg=
ig.isc.toolsRel=8.43
```
- If the integration gateway supports more than one database and you cannot set the default application server to point to the correct database, set up a node as follows:
```
ig.isc.<default local node in PIM database>.serverURL=//<yourappserver:jsl_port>
ig.isc.<default local node in PIM database>.userid=VP1
ig.isc.<default local node in PIM database>.password=JekncVtPdNg=
ig.isc.<default local node in PIM database>.toolsRel=8.43
```
  In every database, there is only one default local node. The Default Local Node check box is selected for this node.
  
  Note. Make sure that the toolsRel value matches the version of your PeopleTools release.
If you change the Integration Broker user ID and password, make sure they are updated in the IntegrationGateway.properties file.

Enter the password in the encrypted form. PeopleSoft provides a utility that returns an encrypted version for the password that you provide. The utility is called pscipher.bat and it's available under the peoplesoft domain in the web server. Run the file in the command prompt like so:
```
c:\bea\wlsever6.1\config\peoplesoft>pscipher <your_password>
```
Verify that the gateway URL is updated (with the web server name on which Integration Broker resides) in the Gateways page.

Select PeopleTools, Integration Broker, Gateways, and click the Load button to populate the connector information and save.

Note. Do not log on to PeopleSoft Infosync Client and perform synchronization using the same user ID that Integration Broker uses, as specified in the IntegrationGateway.properties file.

Refer to the PeopleTools 8.45 PeopleBook: PeopleSoft Integration Broker for more details on how to set up and administer Integration Broker.

Considerations for Modifying Integration Broker Setup

Here are guidelines for modifying any Integration Broker setup data that is delivered with PeopleSoft Infosync Client:

Do not change node names, even if you must modify system-delivered nodes.

Follow the structure of the nodes listed here as you make modification:

Node Name	PSFT_INFOSYNC (internal node)
Node Type	PIA
Routing Type	Implicit
Authentication Option	None
Code Set Group Name	INFOSYNC
Gateway ID	LOCAL
Transaction Request Message	PIM_CONTACT_SYNC

Node Name	PSFT_PIM (external node)
Node Type	External
Routing Type	Explicit
Authentication Option	Password (delivered password is infosync)
Code Set Group Name	PIM
Gateway ID	LOCAL
Transaction Request Message	PIM_CONTACT_SYNC

See PeopleTools 8.45 PeopleBook: PeopleSoft Integration Broker

Do not change the transaction message.

See PeopleTools 8.45 PeopleBook: PeopleSoft Integration Broker
Do not change the names of codesets or codeset groups because it requires corresponding code changes in the system, which is a consulting project.

For each delivered codeset group, the supported match names are company, title, and status. A match name is the name of a data field that might be part of a message sent by a node belonging to this codeset group. You can enter match values (possible values of the data field represented by the match name) for match names, as well as return values to facilitate data translation. For example, end users may enter the country United States of America differently in the PIM client: U.S.,United States,U.S.A., and so on. If PeopleSoft CRM uses the term USA as the name of the country, and you want the translation program to recognize U.S., United States,and U.S.A.the same as USA, add additional codeset group entries using country as the match name, U.S., United States, and U.S.A. (three entries in total) as the match value and USA as the return value in the PIM TO INFOSYNC codeset.

Currently, if you want to add new match names (using XML names in the field mapping tables) to translate data in other data fields, it's considered a consulting project (because it requires certain code change).

The implementation of data translations for PeopleSoft Infosync Client is a three-step setup and verification process, which includes the setting up of codeset groups, codesets, and codeset values. For more information on how the data translation framework works, refer to the Performing Data Translation section of the Applying Filtering, Transformation, and Translation chapter in the PeopleSoft Integration Broker PeopleBook.

Specifying Conflict Resolution Rules

Access the Conflict Resolution page.

Note. Conflict resolution rules are predefined in PeopleSoft Infosync Client. Administrators should determine which rule to use before the client application is distributed to end users.

Add all conflicting items	Select to add both conflicting items to the database.
Ignore all conflicting items	Select to ignore all items if they are conflicting. Warning! It is recommeded to not use this option. There is a potential for overwriting data.
Notify me when conflicts occur	Select to notify the user when there is a conflict, giving the user the flexibility to select which item to update (default value).
PeopleSoft InfoSync Wins	Select to allow entries made in PeopleSoft CRM to overwrite what is in the PIM client.
Lotus Notes Wins	Select to allow entries made in PIM to overwrite what is in PeopleSoft CRM. PeopleSoft supports Lotus Notes 4.6, 5.x, and 6.0. MS Outlook Wins (Microsoft Outlook wins) appears if the selected PIM application is Microsoft Outlook.

Note. For information on how to use the Infosync Client, refer the online help available in the client application. Missing important information about the Infosync Client is documented in this PeopleBook.

See Also

Field Mapping

Modifying Synchronization Settings

After PeopleSoft Infosync Client is installed, you must apply several changes to the configuration file, DCSSettings.cfg. The file is located under C:\Program Files/PeopleSoft/PeopleSoft Infosync.

Note. PeopleSoft provides a utility called Infosync Admin Console Wizard to facilitate the deployment of configuration changes to PIM end users. It collects the configuration information that is entered by administrators and creates a compression file that PIM end users use to apply the update. Refer to the Supplemental Installation Instructions for PeopleSoft Infosync Client document for more information on the utility.

Apply these changes:

Update the Server URL parameter to the web server name on which Integration Broker is running, the Port parameter to indicate the port number that Integration Broker listens to. indicate the web server name on which Integration Broker is running, and the URI parameter to reflect the default node that you use. For example:

[Connection]

Server URL=<web_server_name>

Port=<Intgration_broker_listening_port>

URI=/PSIGW/HttpListeningConnector?From=PSFT_PIM&To=<default_node_name>&MessageName=PIM_CONTACT_SYNC&MessageType=sync&Password=infosync

If you use a secure connection, make sure that the information on secure server URL, secure port, and secure URI is accurate.
Change the value of the Email2 Field parameter to 1:

[Contact Options]

mail2 Field=1

Other Street=0

In addition to the DCSSettings.cfg file, administrators are recommended to increase the timeout value in the pstools.properties file under the PSIGW\WEB-INF\classes directory to allow Integration Broker longer for initial synchronization. To do so, copy the file from the PORTAL\WEB-INF\psftdocs\ps directory and change the value of the tuxedo_receive_timeout parameter to 1200 (in seconds). For example:

tuxedo_receive_timeout=1200

Rule	Enter the name of the rule. When you save the page, this field becomes unavailable.
Search Record Name	Enter the name of the search record for this rule. You can create a view specifically for use in the rule.
((... and ))...	If you leave the AND or OR field blank, specify the nesting level for this condition. Be sure to match opening and closing parentheses.
Field Name	Select the field name on which this rule operates from the drop-down list of fields in the selected component.
Operator	Specify the operation with which to compare the specified field value. Select from standard conditional operators.
Field Value	Enter the value of the specified field against which to compare.
Test SQL (test structured query language button)	Click this button to test the validity of the rule conditions. The result is returned below the button.
Show SQL (show structured query language)	Click this button to view the SQL statement generated by the rule.