Premium
Anypoint Connector for PeopleSoft provides real-time connectivity to query and update any PeopleSoft module using a common integration interface known as the Component Interface.
Guide: PeopleSoft Connector
PeopleSoft Connector 1.1.0 is compatible with:
| Application/Service | Version |
|---|---|
Mule Runtime |
3.6.x |
PeopleSoft |
9.2 |
PeopleTools |
8.53.02 or higher |
Java |
1.7.0_x |
Anypoint Studio |
5.1 or Higher |
-
Added native library support for Mule projects created in Anypoint Studio without Maven. It enables you to add the required PeopleSoft Java Object Adapter (psjoa.jar) library from the Global Element configuration, without having to use Maven or to install the JAR locally and add the dependency to the Project Object Model (POM).
-
Included new demo examples for invoking Find, Get, and Save operations on your Component Interfaces.
PeopleSoft Connector 1.0 Public Beta is compatible with:
| Application/Service | Version |
|---|---|
Mule Runtime |
3.5.2 or higher |
PeopleSoft |
9.2 |
PeopleTools |
8.53.02 or higher |
Java |
1.7.0_x |
Based on the Component Interface White List provided in Connection Management, PeopleSoft connector exposes the PeopleSoft components through the Invoke operation. Using DataSense, the connector automatically populates the Record fields and methods defined by the Component Interface. Record fields on the component are mapped to the keys and properties of the component interface. Both Standard and User-defined methods created in the PeopleSoft Application Designer on the component are retrieved by the connector using DataSense feature of Mule Devkit.
Because of the complex nature and the underlying limitations of PeopleSoft and its integration interfaces, you may encounter the following while using the PeopleSoft connector.
| Issue Type | Description |
|---|---|
Compatibility |
PeopleSoft connector works only in Java 1.7.0_x environment. You need to make sure that AnyPoint Studio, Mule Standalone ESB, CloudHub deployment ,or any associated software is using Java 1.7.0_x for the connector to work properly. |
The connector supports integration with PeopleSoft v9.2 and PeopleTools v8.53.02 or higher. |
|
Component Interface Configuration |
Since Component Interfaces provide an API that is identical to the business Component they provide an interface to, the input data is also bound by all of the defaults, codes and required values that would be required to use the Component in a Web browser. Values provided must match the values provided to the component, which may require looking up. (For example, drop downs may contain "US Dollars" as a value visible to the user, but the code "USA" is provided to the Component Interface.) |
When you try to use the connector with a PeopleSoft Component Interface, you may receive errors related to the functional validity of the data. You need to work with a PeopleSoft functional specialist to resolve the reason for these errors. |
|
Due to the design of Component Interfaces, the names of some operations can be misleading. For example, Create operations only returns a handle to a new instance (logically equivalent to clicking New for a given component), but does not update the data in PeopleSoft. If you want to make changes to the PeopleSoft data, you must use the Save operation. |
|
Mule Application Configuration |
You must provide a Component Interface white list in your Mule flow for DataSense and the connector to work correctly. |
You must provide a |
-
Learn how to Install Anypoint Connectors using Anypoint Exchange.
-
Read more about the PeopleSoft Connector, including examples of how to use it
-
Access MuleSoft’s Forum to pose questions and get help from Mule’s broad community of users.
-
To access MuleSoft’s expert support team, subscribe to Mule ESB Enterprise and log in to MuleSoft’s Customer Portal.