The PeopleSoft Connector provides real-time connectivity to query and update all PeopleSoft modules, using a common integration interface known as the Component Interface. Oracle's PeopleSoft applications are designed to address the most complex business requirements. They provide comprehensive business and industry solutions, enabling organizations to increase productivity, accelerate business performance, and provide a lower cost of ownership.
Additional Info
Requires Mule Enterprise License |
Yes |
Requires Entitlement |
Yes |
Mule Version |
3.6.0 or higher |
Configs
Configuration
<peoplesoft:config>
Connection Management
Attributes
Name | Java Type | Description | Default Value | Required |
---|---|---|---|---|
name |
The name of this configuration. With this name can be later referenced. |
x |
||
server |
Generally conformed by the host:port (e.g. localhost:9999) |
x |
||
username |
The username to access the service |
x |
||
password |
The password to access the service |
|
||
domainConnectionPwd |
The password for all PeopleSoft Internet Architecture Jolt connections to that application server domain |
|
||
componentInterfaceIdsWhiteList |
List of the CI names (IDs) that will be gathered for DataSense. |
|
||
componentInterfaceInteractiveMode |
boolean |
Controls whether to apply values and run business rules immediately, or whether items are queued and business rules are run later, in a single step. Note: You should use interactive mode when testing and debugging a component interface. Interactive mode in a production environment slows performance because of the number of server trips required. If you are using a component interface as part of a batch process in which thousands of rows are to be inserted, running in interactive mode may reduce performance so much on some UNIX servers that the application times out with a connection failure. |
false |
|
componentInterfaceGetHistoryItems |
boolean |
Controls whether the component interface runs in Update/Display mode or Correction mode when the underlying component is effective-dated. If GetHistory is set to true, then historical data can be retrieved but not modified. GetHistory items work in accordance with EditHistory items. |
false |
|
componentInterfaceEditHistoryItems |
boolean |
Controls whether the component interface runs in Update/Display All mode, Update/Display mode, or Correction mode when the underlying component is effective-dated. If EditHistory items are set to true, then historical data can be modified. EditHistory items work in accordance with GetHistory items. |
false |
|
dateFormat |
Date format used to parse dates when we call the Peoplesoft instance or read the values . This is set by default to \"MM/dd/yyyy K:mm:ssa\" . Where : MM : month. dd : day yyyy : year K : hour mm : minutes ss : seconds a : AM/PM . Changing this value may break the mule apps . |
MM/dd/yyyy K:mm:ssa |
|
Processors
Invoke Component Interface
<peoplesoft:invoke-operation>
DataSense enabled
Invoke Operation will invoke a PeopleSoft operation depending on the type selected. DataSense discovers the structure of the entities in the system in Designtime/Runtime and uses it to perform the operation for the type selected. This will vary for Find, Get, Create and the rest.
XML Sample
<peoplesoft:invoke-operation config-ref="PeopleSoft__Configuration" key="JOB_TASK_TABLE||Find" />
Attributes
Name | Java Type | Description | Default Value | Required |
---|---|---|---|---|
config-ref |
Specify which config to use |
x |
||
key |
The type of the entity as determined by DataSense. Once all the types are gathered from Sandbox, Entities are composed as {CI}||{Operation}. E.g. JOB_TASK||Get. |
x |
||
payload |
A Map with the parameters to be used in the operation. |
#[payload] |
|
Update user profile id type
<peoplesoft:update-user-profile-id-type>
Changes the ID type of an USER_PROFILE record and assigns it an attribute.