Integration Broker

Setup & Verfication

PeopleTools Release 8.4x

Last Updated 05/14/2003

Table of Contents
Section 1

General Setup

Section 2

PING Verify Environmental Setup

Section 3

Troubleshooting

Section 1
Integration Gateway Setup
Step 1 Create a Gateway within the Integration Broker
This procedure will create a Gateway in the Integration Broker. The Integration Broker- pub/sub requires a
Gateway definition be created before any transactions can occur using the Integration Gateway.
Note: The following steps should be performed in order, each step builds upon the previous step.
For our purposes here we will be using a predefined and delivered Gateway definition.
Navigate to PeopleTools>Integration Broker >Gateways
Click the Find an Existing Value tab or link

Enter LOCAL as the Gateway ID

NOTE: If you are adding a remote gateway, do not Select Local Y/N check box if there is already a
local gateway present (only one local gateway allowed per database)
Click the

button.

NOTE: We deliver standard connectors with the LOCAL Gateway ID. They must be loaded to the
newly defined gateway. You must save the Gateway URL first then load the connectors.
Modify the Gateway URL. Enter http://LOCALHOST/PSIGW/PeopleSoftListeningConnector
NOTE: When this URL is pasted in the Browser the following message should appear:

Click the
Click the

Click OK

button.
button.

Click the

button.

Step 2 Modify the IntegrationGateway.Properties file to add Target Node

information
Note: When modifying this properties file, it is critical to get all the data entered completely
and correctly. This would be one area to verify if PUB/SUB fails to process correctly. Data
must be entered exactly as shown below in blue. When modifying the
IntegrationGateway.Properties file, please remember that the entries used in this document
are examples only.
# ***************************************************************************
# Confidentiality Information:
*
#
*
# This module is the confidential and proprietary information of
*
# PeopleSoft, Inc.; it is not to be copied, reproduced, or
*
# transmitted in any form, by any means, in whole or in part,
*
# nor is it to be used for any purpose other than that for which
*
# it is expressly provided without the written permission of
*
# PeopleSoft, Inc.
*
#
*
# Copyright (c) 1988-2002 PeopleSoft, Inc. All Rights Reserved
*
# ***************************************************************************
#
*
# SourceSafe Information:
*
#
*
# $Header:: /PT84/WEB/integrationgateway/integrationGateway.proper $
*
# ***************************************************************************
#
#######################################
#
#
#
INTEGRATION GATEWAY PROPERTIES FILE
#
#
#

#######################################
#
# This file, which conforms to the java.util.Properties file definition,
# configures the Peopletools Integration Gateway.
#
## Integration Gateway VERSION Section
#
# Versioning : The entry below is required as it is used to determine the
#
version of your Integration Gateway.It is also used as an
#
indicator of whether this file has been read by the Gateway.
ig.version=1.0
#
## End of Integration Gateway VERSION Section
#
#
## Integration Gateway ADMINISTRATOR USER and PASSWORD Section
#
ig.admin.user=admin
ig.admin.password=psft
#
## End of Integration Gateway ADMINISTRATOR USER and PASSWORD Section
#
#
## Integration Gateway CLASS INSTALLATION Section
#
# Directory where your Integration Gateway classes are installed. This
# information is used on introspection calls to determine the location, name
# and properties of target connectors.
ig.installdir=C:\\bea\\wlserver6.1\\config\\peoplesoft\\applications\\Psigw\\Web-inf\\classes
#
## End of Integration Gateway CLASS INSTALLATION Section
#
#
## DELIVERED CONNECTOR CONFIGURATION Section
#
# URI prefix prepended to any Connector name
ig.connector.prefix=com.peoplesoft.pt.integrationgateway.targetconnector.
# Default Connector used to connect to Remote Integration Gateway(s) (should not be modified)
ig.connector.defaultremoteconnector=HttpTargetConnector
# Default Connector used by the Integration Gateway to connect to the Integration Server
# Core running on the Application Server (should not be modified)
ig.connector.ibtargetconnector=PeopleSoftTargetConnector

# SMTP host used by the SMTP Target Connector

# Example:
#ig.connector.smtptargetconnector.host=psp-smtp-02
ig.connector.smtptargetconnector.host=<mailServerName>
#
## JOLT connect string setting for optional Default Application Server. Do NOT specify a
NODENAME.
#
# Example:
#ig.isc.serverURL=//MYSERVER:9000
#ig.isc.userid=MYUSERID
#ig.isc.password=MYPASSWORD
#ig.isc.toolsRel=8.40
#
# Replace information shown in <> with the correct information for your Node (remove the <> as
well)
#
# If no default is required the following settings should be commented out.
#
ig.isc.serverURL=//LROBINSO082301:9500
ig.isc.userid=VP1
ig.isc.password=VP1
ig.isc.toolsRel=8.40-U2
#
## JOLT connect string settings for Application Server(s) with known NODENAMEs.
#
# Example:
#
#ig.isc.QE_KACNODE.serverURL=//MYSERVER:9000
#ig.isc.QE_KACNODE.userid=MYUSERID
#ig.isc.QE_KACNODE.password=MYPASSWORD
#ig.isc.QE_KACNODE.toolsRel=8.40
#
# Replace $NODENAME with the exact name used for that Node.
# Replace information shown in <> with the correct information for your Node (remove the <> as
well)
#
# If a Non-Default Node is required the following settings should be uncommented.
#
ig.isc.QE_LOCAL.serverURL=//LROBINSO7100D:9001
ig.isc.QE_LOCAL.userid=VP1
ig.isc.QE_LOCAL.password=VP1
ig.isc.QE_LOCAL.toolsRel=8.40-U2
ig.isc.QE_UNDERDOG.serverURL=//LROBINSO082301:9500
ig.isc.QE_UNDERDOG.userid=VP1
ig.isc.QE_UNDERDOG.password=VP1
ig.isc.QE_UNDERDOG.toolsRel=8.40-U2
#
## Settings for support of Messages from a PeopleSoft application running on PeopleTools 8.1x

# ApplicationMessagingListeningConnector must specify one of the node names below

EXACTLY.
#

Nodes Set in the IntegrationGateway.properties file

A. Default Node
Within any inbound message, the only information the integration gateway requires is the
names of the message and the sending node. If the message was sent by an Integration Broker
system, it also includes the name of the target node. The gateway searches the
integrationGateway.properties file for the Jolt connect string properties for the specified target
node, so it can properly direct the message.
However, the integration gateway can fail to determine the correct target node in the
following situations:
The sending node isn't a PeopleSoft Integration Broker system, or it doesn't
specify a target node.
The Jolt connect string settings for the specified target node are missing from the
integrationGateway.properties file.
The message format doesn't allow for a target node specification.
To handle these cases, you can specify a default target node for the gateway to use if no valid
target node can be determined. Use the default Jolt connect string properties:
B. Non-Default Nodes
Jolt Connection String for specified Target Node contained in messages sent through
Integration Broker.

PSCipher in PeopleTools 8.41x and greater

The PSCipher bat file (NT) and shell script (UNIX) are now delivered with PeopleTools
8.41 to encode the Node passwords contained in the IntegrationGateway.properties file. The script
should run this script to encode the password for the Jolt Connect string on the 8.41 side only.
FYI this is discussed in the release notes for 8.41also
Running the script:
--- From NT ---1. Open up a dos window
2. Change directory to C:\bea\wlserver6.1\config\peoplesoft
3. Type in PSCipher <password> ex : PSCipher VP1
4. The ecrypted password will be produced ex:
--- From Unix ---1. Open a telnet session to the Web Server Machine
2. Change directory to /bea/wlserver6.1/config/peoplesoft
3. Type in PSCipher.sh <password> ex : PSCipher.sh VP1
4. The ecrypted password will be produced
5. Cut n Paste into the integrationGateway.properties file.
SEE BELOW for a sample:
ig.isc.PSFT_EP.serverURL=//CISPSA2D:9700
ig.isc.PSFT_EP.userid=VP1
ig.isc.PSFT_EP.password=JegGdkmded= example of the encrypted password
ig.isc.PSFT_EP.toolsRel=8.41.02

This is the link to the release doc for 8.41

http://www4.peoplesoft.com/contdoc.nsf/fe62033bc677319f88256700006d756a/c42debf8672518
7788256bf400646a61?OpenDocument
If you get either of these errors:
"'pscipher' is not recognized as an internal or external command,
operable program or batch file."
or
"Exception in thread "main" java.lang.NoClassDefFoundError: iaik/java/security/Key"
Then you will first need to set java in your path. Please see resolution 200727920 for details.

Gateway password encryption in 8.44+

You may now encrypt your Gateway passwords from the Gateways page in PIA. Click the
properties link > enter userID and password (the default is administrator / password), and
expand the section Encryption Utility:

When you click the Apply button, this refreshes the new Gateway settings the same way the
Refresh button does in the following step.

Step 3 Refresh the IntegrationGateway.properties file

Section 2
PING Verify Environmental Setup
After any Node setup is complete, the PING should be exercised and log results verified to determine if the
environmental configuration is correct. If the PING does not result in a SUCCESS status STOP do not
publish. Begin troubleshooting activities to correct integration issues.

Step 1 Login to PIA

Step 2 Navigate to the Application Message/Integration Broker Monitor
Step 3 Click on the Node Status Tab
Step 4 Select the appropriate Node Name

Step 5 Click the PING button

Step 6 Verify Results are SUCCESS

Section 3
TroubleShooting
The Log Files for the IntegrationGateway, msgLog.htm and ErrorLog.htm, are located at
<wlserver6.1 home>\config\peoplesoft\applications\PSIGW\.

Each Connector processes both a request and a response. Listening Connectors receive a
request immediately, and later in processing return a synchronous response to the
requestor. Target Connectors generate a request, send it, and wait for a response from the
external system.
PeopleSoft-delivered Connectors conform to an implementation in which each Connector
must log the actual, raw request and response sent/received. Connectors also create log
entries when an error condition is encountered.
Each section of the log file will be described below.
Section 1

This log entry was created when the IBListeningConnector received a request most likely from the Broker
Engine running on the PS Application Server. Note that the format is not XML, but MIME (the internal
messaging standard for the Integration Broker).
Section 2

Mirroring the Section 1 entry above, the IBListeningConnector has logged the actual response that it sent
back to the requesting system, most likely a Broker Engine on the PS Application Server.
Section 3

An error condition has been encountered, and thus a log entry is generated. Note that this log differs from
standard message logging, such as Section 2 above. The Java stack trace is displayed for debugging
purposes. Also, if and when possible the internal IBRequest or IBResponse is displayed to help in
tracking down why a problem has be

Common Errors:
Scenario One If the Source Node is not defined on the Target System PING will
result in the following error:

Correction Procedure Enter the Source Node Definition on the Target System and re-PING.
Verify Results = SUCCESS

Scenario Two If the WebServer/Gateway is down PING will result in the following
error:

Correction Procedure Enter boot the web server and re-PING.

Verify Results = SUCCESS

Scenario Three If the Target AppServer is down PING will result in the following
error:

Correction Procedure Enter boot the AppServer and re-PING.

Verify Results = SUCCESS