Beruflich Dokumente
Kultur Dokumente
Deleting a WSDL
Restarting PUBSUB
Terminology
UserName not defined in
database
If you get this message with the web services listening connectors e.g. SOAP or REST:
Then check the Default User ID set for the ANONYMOUS Node (used by IB for web services) and make
sure that it is a valid username and that the user account is active (e.g. not locked out).
Web Service Target Locations
Web Service Target Locations are defined under:
On the target locations page, set the relevant values as suggested e.g.
http://<machine>:<port>/PSIGW/PeopleSoftServiceListeningConnector
http://<machine>:<port>/PSIGW/RESTListeningConnector
External System Contact
Error
While configuring an integration gateway in integration broker I kept getting the following error when
attempting to load the connectors for the gateway (which involves contacting the gateway through
Using the DNS entry, the gateway connectors would not load, however changing the URL to use the IP
So this indicated an issue with the DNS entry or something in that space. Further checking using the
nslookup command in Windows/Linux confirmed the issue, and after making relevant changes the
DNS entry resolved as expected. A final step that was required was to restart the web server after
Service Operation
While testing a web service (via a CI), the following message came back (this is using soapUI):
<IBResponse type="error">
<StatusCode>20</StatusCode>
<MessageParameters>
<Parameter>USER</Parameter>
<Parameter>EXAMPLE</Parameter>
</MessageParameters>
</IBResponse>
This relates to service operation security. Specifically, the user in question does not have security to
PeopleTools > Integration Broker > Integration Setup > Service Operations
On the service operation page, there will be a hyperlink labelled Service Operation Security.
Click on that to bring up the service operation security settings (opens in a new tab/window).
Add a permission list that you know the user mentioned in your message has in their security
settings.
number of errors, and could no longer get past the login screen. On the PIA, the site just kept
Not very helpful! The application server logs ( APPSRV_MMDD.LOG ) was slighty more informative, giving
request
Turns out, that the HRMS node had been made inactive. This was the node being used by the EMPLOYEE
portal for HRMS/Campus Solutions, so it needed to be active. You can check the nodes being used by
Updating the node to active, by setting ACTIVE_NODE = 1 in PSMSGNODEDEFN for the HRMS node, stopping
the application server, physically deleting the cache files, and restarting the application server
need to significantly modify or remove a web service. Fortunately, PeopleSoft have provided a ways
Search for your existing service (just hit search if you don't know what it is called). Select the
to re-export the WSDL to the repository and get the URL to view it:
As you can see WSDL follow the following format which you might be able to use as a shortcut to find
it:
http(s)://<machine>:<port>/PSIGW/PeopleSoftListeningConnector/<SERVICE_NAME>.<VERSION>.wsdl
Deleting a WSDL
To delete an existing WSDL, navigate to:
PeopleTools > Integration Broker > Service Utilities > Service Administration
The first page (tab) allows for you to search for and delete the WSDL associated with a service (which
Note in PeopleTools 8.5x, there is also a hyperlink to Clear WSDL Export Statu s which is used to find
and resolve inconsistencies with WSDL exported to the WSDL repository. It is essentially a tool to find
and fix service operations without an associated WSDL which have been provided as web services.
Message Referenced in
Runtime Tables
Once a message has been published in Integration broker, you can no longer update it. The fields will
What if you didn't get the message and schema quite right? How do you update your message?
Behind the scenes the logic that disables the message is in the function checkruntime which lives in
four tables, and if any return a row for the service operation associated with your message, the
PSAPMSGPUBCON
PSAPMSGSUBCON
PSIBLOGHDR
PSAPMSGPUBHDR
What you'll need to do is delete any transactions associated with your message through the service
operations monitor.
PeopleTools > Integration Broker > Service Operations Monitor > Monitoring
NOTE: that you'll need to open up the messages for the appropriate service & service type.
Alternatively, if you have a lot of transactions, you could clear out the four tables through the
database.
Also if you see this with a message used by a web service, you'll need to check the synchronous
services area of the service operations monitor. This can be viewed from PS_AMM_SYNCLIST which is a
view to PSIBLOGHDR .
Exclude PeopleSoft
Authentication Token
Integration broker in PeopleTools 8.5x includes a new setting in the service configuration to exclude
the PeopleSoft authentication token on outbound requests to other PeopleSoft nodes. In plain english,
this means you can configure service operations so that they don't require the same user/operator to
exist between two PeopleSoft systems, for example between PeopleSoft HRMS and PeopleSoft
Financials.
Previously, this was a requirement, otherwise the integration would fail with a message like this:
The exclude PeopleSoft authentication token setting is available from the following navigation:
PeopleTools > Integration Broker > Configuration > Service Configuration > Exclude PSFT AUth Token
Tab
From the screen, search for a relevant service or service operation (e.g. VENDOR_SYNC ) and check the
you open the page. However, you can confirm the settings have been saved by searching for all
services/service operations with the Exclude PSFT Auth Token flag set (check box).
Deleting Duplicate Routings
Duplicate routings can cause problems with Integration Broker messaging. Fortunately PeopleSoft has
provided (as of PeopleTools 8.48 anyway) functionality to search for and delete duplicate routings.
PeopleTools > Integration Broker > Service Utilities > Service Administration
The search will find any duplicate routings and allow you to select and delete them.
Behinds the scenes PeopleCode searches the PSIBRTNGDEFN Integration Broker Routing Definition for
any cases where more than one active routing is associated with the same service operation for any
local to local routings, any to local routings and point to point routings.
I'm not convinced the code being used is perform the search for duplicate routings is 100% correct. I
also used the following query to identify potential duplicate routings and found some cases that
weren't being picked up so it might be worth double checking with this query as well.
select
IB_OPERATIONNAME,
VERSIONNAME,
SENDERNODENAME,
RECEIVERNODENAME,
count(distinct ROUTINGDEFNNAME)
from
PSIBRTNGDEFN
where
EFF_STATUS = 'A'
group by
IB_OPERATIONNAME,
VERSIONNAME,
SENDERNODENAME,
RECEIVERNODENAME
setCertificate fails
During IB configuration while loading gateway connectors the following error messages kept
appearing:
This is to do with two entries in the integrationGateway.properties configuration file which you can
PeopleTools > Integration Broker > Configuration > Gateways > {Open Gateway} > Gateway Setup
Properties
secureFileKeystorePath=
secureFileKeystorePasswd=
The secureFileKeystorePath needs to point to the correct location of the PeopleSoft Keystore ( pskey )
which for example might live under $PS_HOME/webserv/<domain./piaconfig/keystore/pskey but this will
vary depending on your web server and PeopleTools version. Just make sure the path is correct.
To encrypt the password (only in PeopleTools 8.5x), use the password encryption utility at the bottom
of the gateway properties page, and paste the encrypted value in the field.
If you are setting up integration between two systems, and one is on PeopleTools 8.5x or above and
one is on PeopleTools 8.4x, then you need to make sure you have set up the
PeopleTools 8.5x
PeopleTools 8.4x.
So, with such a set up, you will have a combination of encrypted and unencrypted passwords that
need to match up. If you have any of this wrong, you'll get the same message above when you try to
ping nodes between the two systems. That will tell you which side you have wrong.
Restarting PUBSUB
For integration broker configuration changes, it is possible just to restart the PUBSUB group of
processes on the application server (rather than the entire application server).
Here's how:
Start psadmin
1) Application Server
1) Administer a domain {Pick the appropriate domain}
5) Tuxedo command line (tmadmin) (this may vary depending on your PeopleTools version)
In the tuxedo command line, use the help or h command to show a list of commands. The two you'll
succeeded
6 processes stopped.
PSBRKHND_dflt :
PSPUBDSP_dflt :
PSSUBDSP_dflt :
6 processes started.
through:
Open your local Gateway (usually called LOCAL ) and click on the Gateway Setup Properties.
Login to the gateway properties using the default user ID and password (they are provided on the
page). You may need to ask your system administrator for the appropriate credentials if the default
Once you login, click on the Advanced Properties Page link. This will open the
Scroll through the integrationGateway.properties file until you find the logging section. The following
ig.log.level=2
Level Value
Suppress
-100 any
logging
Language
-1
Exception
Standard
1 Gateway
Exception
Level Value
Errors
2 and
Warnings
Important
information,
3 errors
and
warnings
Standard
and
important
4 information,
errors
and
warnings
Low
importance,
standard,
and
5 important
information,
errors
and
warnings
The default log level of 2 should be sufficient for troubleshooting. Remember with logging less is
more. It is easier to dig deeper once you've found the relevant issue rather than creating a haystock
of log output.
You can view the message and error logs using your browsing by pointing to:
If you are having trouble determining the URL for these, look at your local gateway URL or ping it and
use the same URL up to the PSIGW/ and then enter the appropriate message log page name.
NOTE: the names of the HTML files are case sensitive! So errorlog.html may not work while
If there have been no messages or errors logged then these files won't exist. Their locations/names
may also have been changed in the integrationGateway.propertie file.
ig.messageLog.filename
ig.errorLog.filename
Terminology
Integration broker is one of those areas of PeopleSoft that introduces a lot of terminology (jargon).
You really need to get your head around this terminology before you can understand what's going on.
Unfortunately, the documentation in PeopleBooks can be a little terse. Here's a quick summary.
Gateways: Are the pathways between systems. There is always a LOCAL gateway in PeopleSoft
which refers to the source PeopleSoft system. Other gateways may exist - for example when there are
Domains: Refer to PeopleSoft application server (tuxedo) domains for publish/subscribe (pub/sub)
services. These are turned on at the application server and required for Integration Broker to work.
Nodes: Define what application a message belongs to - any system that integration broker can talk
Messages: Define the structure of the XML sent between nodes. The key difference between
acknowledge by the receiver, asynchronous ones don't. Web services typically use synchronous
messages.
Queues: Are used to manage and group messages so that all messages are sent through the
multiple pipes. Queues are used for administration of integration broker to avoid stopping everything
when something is wrong. For example you can pause a one queue for messages to the report
Routings: Link a service operation to a node, and can also specify transformation of a message.
Service Operations: Bring together messages, queues, handlers and routings. They essentially
Services: Group service operations into the conceptual service provided. For example, you might
have a service based on a component interface. The service operations would be the methods
(create/find/get/update/update data) and the service would be the interface to that component
interface.