Using the Simple Post Class

This section provides an overview of the Simple Post class, including its:

  • Usage

  • Syntax

  • Parameters

The standard usage of the Simple Post class is:

com.peoplesoft.pt.simplepost.SimplePost [-options]

The syntax for sending an XML message from a third-party system to the integration gateway is:

com.peoplesoft.pt.simplepost.SimplePost -reqnode 
<requesting node> -opername <service operation.version> 
-url <destination server URL. This is always 
the HTTP listening connector> -infile <input file 
name and path> -outfile <output file name and path> 
-opertype <operation type>  -destnode <destination node name(s)>
-v <Display debugging output> −to  
<timeout value> -?-help <Display help>

Note that you enter the syntax as a single line.

The Simple Post utility parameters that you can pass are described in the following table.

Parameter

Description

-reqnode

Identifies the requesting node name.

-opername

Identifies the service operation and service operation version that you are sending.

For example: ADD_PO.v1

-msgname

Identifies the name of the message that you are sending.

This parameter is not used in PeopleTools 8.48 and higher releases.

-url

Identifies the destination server URL.

-infile

Identifies the path and file name to send.

The root node must be name of the message. For example, if the name of the message is SYNC_TEST, the root node of the XML input file must be <SYNC_TEST>.

-outfile

Identifies the path and filename where the utility generates the response from the server.

-opertype

(Optional.) Identifies the service operation type. Values are:

  • sync: The service operation is synchronous.

  • async: The service operation is asynchronous.

  • ping: Tests the application server to make sure it is available and accepting requests.

-msgtype

(Optional.) Identifies the message type. Values are:

  • sync: The message is synchronous.

  • async: The message is asynchronous.

  • ping: Tests the application server to make sure it is available and accepting requests.

This parameter is not used in PeopleTools 8.48 and higher releases.

-msgver

(Optional.) Identifies the version number to apply to the message.

For example, VERSION_1.

This parameter is not used in PeopleTools 8.48 and higher releases.

-destnode

(Optional.) Identifies the destination node name.

-v

(Optional.) Displays any debugging output.

-en

(Optional.) Compresses and base64-encodes the data.

When this command line option is located on the Simple Post call, the logic compresses and base64-encodes the data, places it into the Data node, and then adds the required headers into the request.

-to

(Optional.) Identifies the timeout value.

This integer value determines the amount of time, in seconds, that the Simple Post class will wait for a response from the server.

-pwd

(Optional.) Identifies the password for the destination node.

This parameter is optional, unless the destination node requires a password.

-ou

(Optional.) Identifies the ID of the originating user.

-on

(Optional.) Identifies the name of the originating node.

-op

(Optional.) Identifies the name of the originating process.

-sq

(Optional.) Identifies the subqueue.

-sc

(Optional.) Identifies the subchannel.

This parameter is not used in PeopleTools 8.48 and higher releases.

-fdn

(Optional.) Identifies the name of the final destination node.

-emid

(Optional.) Applies a unique external message ID to a message to ensure no duplicate messages are sent to PeopleSoft Integration Broker.

The ID cannot exceed 70 characters.

-nr

(Optional.) Specifies whether to turn on nonrepudiation. The valid values are:

  • Y: Turn on nonrepudiation.

  • N: Turn off nonrepudiation. (Default)

-h

(Optional.) Specifies an HTTP header.

For example:

SOAPAction: QE_SYNC_MSG.v1

There can be one:many –h parameter invocations. For example:

com.peoplesoft.pt.simplepost.SimplePost -reqnode 
QE_UNDERDOG -opername QE_SYNC_MSG.v1 -url 
"http://jfranco040303/PSIGW/HttpListeningConnector" 
-infile "C:\User\My Documents\QE_SYNC_MSG\
QE_SYNC_MSG.xml" -outfile "C:\Documents and Settings\
Desktopout.txt" -h "SOAPAction:QE_SYNC_MSG.v1" -h 
"test2:Joe_User"

Note: When Simple Post encounters an HTTP header name of SOAPAction, the content of the input file is not wrapped into IBRequest XML format and no IBInfo data is built. The IBInfo data, such as service operation name, requesting node, requesting node password, destination node, and so on, can be pulled from the SOAPAction field.

-?-help

(Optional.) Displays a list of the Simple Post utility parameters.