PeopleSoft Integration Broker setup for Test Framework – Part II

In this post I’m going to cover the rest of IB basic setup.

So right now we have a clean default local node, and behind the scenes PeopleTools App Engine has done some magic for us.  Service Operations have been set up with routings using our new node.  Still, we need to do a couple more housekeeping measures.

Get your cup of coffee?  Good.  Log into your instance, go to PeopleTools, Integration Broker, Integration Setup, Nodes, Your Default Local Node.

Authentication here should be Password.  Lets cover some roles this account should have, shall we?  At a minimum this role should have PeopleTools, and one of the three PTF roles – Admin, Editor, User.  The role I’m using has all three levels altho frankly I think we would do fine with just PTF Administrator.

Now click the Portal tab.  This tab seems to have mystical and magical powers – in only that it’s a toss-up as to how useful it is, what is it used for…

For now, and because I’m not a System Admin but have some background in how HTTP Nodes work – we are going to go the conventional route.  With a bit of an explanation.

We are dealing with a distributed computing environment here using HTTP as the communication and information transport protocol.  Which is a lot of techno geek leet speak for we’re using is a specific set of rules to get one point of our internet enabled network to talk to other points.

In any event our node needs to understand where home is.  Pick your Default Portal – my company uses Employee for its HRMS implementation.  Then fill in the Content URI Text and the Portal URI Text.  There is a template provided by PS above both boxes – in any event it’s http(s)://someserver/psc/pshome/ for the Content URI and http(s)://someserver/psp/pshome/ for the Portal URI.

Okay so right now we have the basics set up for our default node, let’s hit some other tasks.

Go up into Integration Broker, Configuration, Quick Configuration.  This page covers three areas – Gateway Setup, Integration Broker Domains and the Service Configuration.  Frankly these should be mostly set up, but I’ll cover them briefly with this caveat – I’m not a system admin.

The Gateway URL should be something like this: http(s)://PeopleSoft Server>/PSIGW/PeopleSoftListeningConnector.  If you were to copy and paste that address into a browser address bar you should connect to the Integration Gateway.  In fact that is what happens when you click the Ping button.

If this was a copy from Prod then the URL needs to be changed.  Get in touch with your System Admin and have him/her help you with this part.

Integration Broker Domains – that should display the machine name and the path for your PeopleSoft instance.  It should also display a status of Active.  You should have your Gateway set up first as well as your default local node.  There is a hyperlink to the Domain Status page – if what is listed isn’t the correct environment you can try to set the status to Inactive, then do a Purge Domain Status, followed with a Refresh.  If you run into trouble at this part, I would guess you have problems with your Gateway setup.

Last is Service Configuration.  The setup here directly affects PTF.  You can stay with the default/delivered Service Namespace and Schema Namespace – but you need to fill in the Target Location.  That is the URL to your ListeningConnecter java applet in your web server.  The URL  is

– note this is http only.

For those who are running https the template is almost the same:

Some good news for those who do have installations behind load balancers – this will work.  And if your PeopleSoft instance is set up in your networks DNS tables, you won’t have to provide a port number; that is created as part of the DNS listing for your application.

This service configuration must be correct or PTF will not work.  You should at the very least be able to get a SOAP response from the server if you enter your URL into a browser address bar.  The body of the response should have a line:Integration Broker Response – that tells you that you are indeed contacting the IB instance.

More to cover in later posts!


About Lee Greffin
Just another programmer...

One Response to PeopleSoft Integration Broker setup for Test Framework – Part II

  1. Jim Marion says:

    Hi Lee, the Portal tab contents are used only with portal nodes, not integration broker nodes (nodes like EMPL, ENTP, ERP, HRMS, CRM, etc.). The URL is used by PeopleSoft when generating full URL’s for CREF’s as well as calls to the GenerateXXXContent|PortalURL functions. You can also use the Portal tab contents to create relative CREF’s for non PeopleSoft nodes. That way you can create a CREF for a dev/test/pro non-PeopleSoft resource, migrate the CREF, and not have to change the CREF’s target in the receiving system.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: