How to check PeopleSoft Integration Gateway or Default Node is active

Integration Broker is one of the most important tools in PeopleSoft system which enables us to perform asynchronous and synchronous messaging among internal systems and third-party systems. Integration Broker is a middleware technology and it can;

• Performs asynchronous and synchronous messaging among internal systems and third-party systems.
• Exposes PeopleSoft business logic as web services to PeopleSoft and third-party systems.
• Consumes and invokes web services from third-party and PeopleSoft systems.

PeopleSoft Integration Broker consists of two subsystems: the integration gateway and the integration engine. Main difference between integration gateway and integration engine is that the integration gateway resides on a PeopleSoft web server, and the integration engine is installed on an application server as part of the PeopleSoft application.

This post we will look at how to check that your Integration Gateway and Integration Engine is active. 

For more information on Integration Broker technology please look 

Check Integration Gateway Status

Here we are going to check the status of the integration gateway (which is reside in the web server). 

Login to your PeopleSoft Application and Navigate to Main Menu > PeopleTools > Integration Broker > Configuration > Gateway

Click on the Ping Gateway button to see if the Integration Gateway is up and running. If the gateway is up and running you will see a window a below

Check Default Node Status

In order to enable communication between web server and application server (for inbound traffic) we need to find the default local node of our PeopleSoft Application.
Navigate to PeopleTools > Integration Broker > Integration Setup > Nodes
On the search page, click on the search button to query all the nodes. After that click on the Default
Local Node header of the result grid. The default local node (e.g. PSFT_HR) will now be shown as follows. Then select the default node.

Now that you know the default local node of your Integration Broker. Now Navigate to PeopleTools > Integration Broker > Configuration > Gateway. Then, Click on the link Gateway Setup Properties. In the next screen you have to provide User ID and Password (Please contact your PeopleSoft system administrator if you do not know the User ID and Password).
After you successfully enter the integration gateway security credentials, the PeopleSoft Node Configuration page appears.

Click on Ping Node button for your default local node. If successful the following screen will appear. which means the Integration Gateway can now successfully communicate with the application server.

why these checks are important

This might be useful when you are working with integration broker and if you want to check that gateway and node are active. As an example if you are working with web services and when you want to troubleshoot something then you might want to see whether these component are active in your system.

Read More»

How to Display a detailed SQL error (Online)

Sometimes when you navigate to a PeopleSoft page or while doing some work online you might come up with this error.

"A sql error occurred. Please consult log for Administrator."

As developers when we build and test it is handy if we can see detailed error so that we can rectify it quickly. Sometimes it is not that obvious where the error is coming from even though you build the records, views etc.. Otherwise, you have to get the Appserver logs to find out where the error is coming from.

There is a way you can enable SQL error details so that it will be displayed to the users (in this case developers)

If you want SQL error details to be visible to users, set this property as follows:

Suppress SQL Error=0

This property exists in the PSTOOLS section of the PSAPPSRV.CFG file.

"For security purposes, this option has a default value of 1 to prevent SQL error details from being displayed to users.
Any SQL errors that occur don't display details, but refer users to consult the system log.
The details that were in the SQL message are written to the log file. This helps to prevent SQL injection vulnerabilities."

So, if you want to see the detailed SQL error online, ask your PeopleSoft Sysadmin to change this option in App Server PSAPPSRV.CFG file so that next time you can see the detailed SQL error message.

Read More»

How to Add Non-Default Font to BI Publisher Report in PeopleSoft

Oracle BI publisher for peoplesoft, support limited number of default-font types. However, when you want to add another font which is not a default font type delivered by BI publisher your report will not display the appropriate font you want. 
In order to change the font you want, you have to take a configuration change in BI publisher. 
BI Publisher system properties settings are defined in the xdo.cfg file. The default xdo.cfg file is located in the $PSHOME/appserver directory, which is shared by all application server and process scheduler domains by default.
For example you want to use font say "Bodoni MT" which is not a default font configured in BI Publisher settings in Application Server. 
Therefore, a xdo.cfg BI publisher config file in App server need to be modified to include "Bodoni MT" font. 
Here is the example xdo.cfg file with added Bodoni MT font. 

<config version="1.0.0" xmlns="http://xmlns.oracle.com/oxp/config/"> 
    <!-- Properties --> 
    <properties> 
        <!-- System level properties --> 

        <!-- PLEASE SELECT A VALID TEMPFILE DIRECTORY!!! --> 
        <property name="system-temp-dir">c:/Temp</property> 

        <!-- PDF compression --> 
        <property name="pdf-compression">true</property> 

        <!-- PDF security --> 
        <property name="pdf-security">false</property> 
        <property name="pdf-open-password">user</property> 
        <property name="pdf-permissions-password">owner</property> 
        <property name="pdf-no-printing">true</property> 
        <property name="pdf-no-changing-the-document">true</property> 
    </properties> 


   <!-- Font setting --> 
    <fonts> 

      <!-- Windows Wingdings font --> 
      <font family="Wingdings" style="normal" weight="normal"> 
       <truetype path="C:\WINNT\fonts\wingding.ttf" /> 
      </font> 

      <font family="GnuMICR" style="normal" weight="normal"> 
       <truetype path="C:\WINNT\fonts\GnuMICR.ttf" /> 
      </font> 

      <font family="Times New Roman" style="normal" weight="normal"> 
       <truetype path="C:\windows\Fonts\times.ttf" /> 
      </font> 

      <font family="3 of 9 Barcode" style="normal" weight="normal"> 
       <truetype path="C:\WINNT\fonts\3of9.ttf" /> 
      </font> 
       
      <font family="Bodoni MT" style="normal" weight="normal"> 
       <truetype path="C:\WINDOWS\Fonts\BOD_R.TTF" /> 
      </font> 

    </fonts> 
</config> 

to add a font, add font element (see example above for Bodoni MT) and set the truetype path as above.

Read More»