Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Configuring: PeopleSoft Settings and PeopleTools 8.13 Settings
 

Classic Java CAPS

Configuring JMS Clients

Configuring Java CAPS for SSL Support

Configuring Java CAPS Business Processes

Configuring Environment Components for the Sun Business Process Manager

Configuring Sun Master Indexes (Repository)

Configuring Java CAPS Project Components for Application Adapters

Configuring Java CAPS Project Components for Communication Adapters

Configuring Java CAPS Project Components for Database Adapters

Configuring Java CAPS Project Components for Web Server Adapters

Configuring Java CAPS Environment Components for Application Adapters

Using the Environment Properties Editor

To Configure the Environment Properties

Configuring Oracle Applications Adapter Environment Properties

Outbound Oracle Applications Adapter Properties

Outbound Oracle Adapter Properties with XA support

Configuring the PeopleSoft HTTP Client Adapter Environment Properties

HTTP Settings

Proxy Configuration

Security and Authentication

Security and SSL

PeopleSoft Settings

PeopleSoft Settings and PeopleTools 8.42 Settings

PeopleSoft Settings and PeopleTools 8.13 Settings

Configuring SAP BAPI Adapter Environment Properties

Inbound SAP BAPI Adapter

Outbound SAP BAPI Adapter

Configuring the Siebel EAI Adapter Environment Properties

Siebel EAI

HTTP Settings

Proxy Configuration

Security

Additional SSL Section Notes

Adapter Environment Properties

Configuring the SWIFT Alliance Gateway Adapter Environment Properties

To Configure the SWIFT AG Adapter Environment Properties

SWIFT AG Adapter Environment Properties

Transport

Connection Pool Settings

Configuring Websphere MQ Adapter Environment Properties

Inbound MQSeries Adapter -- Inbound Adapter Environment Configuration

Outbound MQSeries Adapter (XA) -- Outbound Adapter Environment Configuration

Outbound MQSeries Adapter (XA) -- Connection Retry Settings

Outbound MQSeries Adapter (XA) -- Connection Pool Settings

Outbound MQSeries Adapter -- Outbound Adapter Environment Configuration

Outbound MQSeries Adapter -- Connection Retry Settings

Outbound MQSeries Adapter -- Connection Pool Settings

Outbound MQSeries Adapter -- Connection Establishment Mode

Accessing Non-Local Queue Managers and Non-Local Queues

Configuring Java CAPS Environment Components for Communications Adapters

Configuring Java CAPS Environment Components for Database Adapters

Configuring Java CAPS Environment Components for Web Server Adapters

Configuring JDBC/ODBC Drivers

Configuring SAP R/3 for the SAP BAPI Adapter

Configuring Secure Network Communications for SAP

Configuring Siebel EAI Workflows

Importing an SNA Custom Handshake Class

Configuring WebLogic for Asynchronous Communication

Configuring Master Index (Repository) Connectivity and Environments

Related Topics for Sun Adapter for Batch/FTP

Java EE Based Components

Broadcasting Master Index Updates to External Systems

Configuring Sun Master Indexes

PeopleSoft Settings and PeopleTools 8.13 Settings

The PeopleSoft Settings and PeopleTools 8.13 Settings section of the PeopleSoft HTTP Client Adapter Environment properties contains the top-level parameters displayed in the following table.

The PeopleTools settings must match the configurations for the PeopleSoft server.

At minimum, you must specify the following properties:

Environment Configuration - PeopleSoft Settings and PeopleTools 8.13 Settings

Name
Description
Required Value
MessageVersion
Specifies the message version.
The message version.
ToNode
Specifies the name of the node for which the message is intended. This must correspond to an entry in the node lookup table on the gateway servlet, and the name of the local node (node definition) on the receiving PeopleSoft system.
The name of the node for which the message is intended.
FromNode
Specifies the name of the node from which messages originate. The node name must match the node definition for the third party system as defined in the receiving PeopleSoft system.
The name of the node from which the messages originate.
Channel
Specifies the name of the message channel containing the message.
The name of the message channel.
PublicationProcess
Specifies the application-defined name of the program that generated the message. This may be required by the application.
The application-defined name of the program that generated the message.
Password
Specifies the password associated with the destination node.

This value is stored in the PeopleSoft database and must be communicated to the system administrators for the publishing system. If the node definition on the sending system has a node group defined, the password will be present. If the node definition on the receiving system has a node group defined, the password must be present and must match the node group password.

The password associated with the destination node.
DefaultDataVersion
Specifies the default message version for the sending system.
The default message version.
OriginatingNode
Specifies the name of the node that originally published the message. This property is used to prevent circular publishing. If not in the XML file, the system sets it to the publishing node name.
The name of the node that originally published the message.
PublicationID
Specifies the system generated identifier for the publication.

The fields, FromNode, Channel, and PublicationID, uniquely identify the publication. If the FromNode is specified and the Publication ID is omitted, the publication ID is set to the next available publication ID on that channel within the subscribing PeopleSoft database.

The system generated identifier for the publication.
Publisher
Specifies the application-defined operator ID class that published the message. This may be required by the application.
The application-defined operator ID class that published the message.
SubChannel
Specifies the name of the subchannel that contains the message.

Messages in the same channel, but in different subchannels, are assumed to refer to distinct objects (for example, different POs or different employees), and are processed in parallel if possible. This field contains the concatenated values that represent the subchannel. For example, if the subchannel is Business Unit, Journal ID, then the value of this field is M04123456789 where Business Unit = M04 and Journal ID = 123456789. Include this field if the subscribing PeopleSoft system has a defined subchannel, otherwise, it may be omitted.

The name of the subchannel that contains the message. See the description for the naming format.
Subject
Specifies the name of the message as defined in the PeopleSoft system.
The name of the message as defined in the PeopleSoft system.
SubjectDetail
Specifies the application defined subtype of the message name.
The application defined subtype of the message name.