I have never created a trigger, nor an audit record.

Your instructions were perfect.
I followed them and had success the first time.

Thank you.

While reading through this I noticed what I think is a small bug. Doubt it would ever show or cause issue, but thought I'd mention it.

 method GetResultText ... When = %ObEmail_NotDelivered Return "Delivery not attempted"; Break; When = %ObEmail_NotDelivered Return "Partially delivered"; Break; ... end-method; 

I think this should actually be

  When = %ObEmail_NotDelivered Return "Delivery not attempted"; Break; When = %ObEmail_PartiallyDelivered Return "Partially delivered"; Break; 

Thanks!

-Frank

Tuition Calc -
TUIT_CALC_TBL
CALC_MESSAGES
OPT_FEE_STDNT

Group Post -
GROUP_CONT_INFO
GROUP_LINE

Cashiering -
CSH_BD_CSH_OPEN
CSH_OFF_RECEIPT
CSH_OFF_RCPT_L
CSH_OFF_RCPT_T

Third Party Contracts/Deferral Contracts/Payment Plans -
TP_CONTRACT
TP_STUDENT

Refunds -
REFUND_HDR
REFUND_DTL
REFUND_CHECK

Collections -
COLLECTION_SF

1098-T Reporting -
SF_1098_DTL_SF
SF_1098_ITEM

GL Interface -
SF_ACCTG_LN

Optional Fees -
OPT_FEE_STDNT

Tuition Group Setup -
SEL_GROUP_TBL
SEL_GROUP_CRITR
GROUP_FEE_TBL

Criteria Setup -
SEL_CRITER_TBL
SEL_CRITR_TBL
SEL_VALUE_TBL

Term Fee Setup -
TERM_FEE_TBL
TERM_FE_CD_TBL
TERM_SF_CD_TBL
TERM_SUBFEE_TBL

Waiver Setup -
WAIVER_CODE_TBL
WAIVER_TBL

Item Type Setup -
ITEM_TYPE_TBL
ITEM_ACCT_TYPE
GL_INTERFACE

Billing -
BI_BILL_HEADER
BI_BILLING_LINE
BI_BILL_MESSAGE
BI_STD_REQ_TBL

You should be able to pass the (simple) authentication information through the SOAP request header, something like:

 <wsse:Security soap:mustUnderstand="1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>PS</wsse:Username> <wsse:Password>PS</wsse:Password> </wsse:UsernameToken> </wsse:Security> 

You can generate the request message with the correct security settings using the generate SOAP template functionality:
PeopleTools > Integration Broker > Service Utilities > Generate SOAP Template

I believe this happens when the service configuration has been set incorrectly under:
PeopleTools > Integration Broker > Configuration > Service Configuration

In particular, the target location. It should follow the example/alternate example provided:

 http://<machine>:<port>/PSIGW/PeopleSoftServiceListeningConnector http://<machine>:<port>/PSIGW/PeopleSoftServiceListeningConnector/<defaultlocalnode> 

Check the settings here, for example it may have been accidentally set with the connector PeopleSoftListeningConnector instead of the correct PeopleSoftServiceListeningConnector or perhaps the default local node (alternate example) is required?

Thanks for the great sharing.
I try to provide web service through the method which u introduce.
The confirm result showing everything fine.
But when i try to open the wsdl url tat the system generated, it only show me message like this :

PeopleSoft Integration Gateway
PeopleSoft Listening Connector
Tools Version : 8.50
Status: ACTIVE

and do not consist any content other that the message above.
I wondering is that its success?

Thanks.

The SQR Code will take the COBOL Trace file as input, parse through each cursor and bind variable, and produce an analyzed version of the Trace File. The end result is an easy to read and even execute trace file, with all of the bind variables inside the respective SQL statements.

The code is free. View code at SQRTricks.com

Additional State Record fields that are common to include are AE_APPLID and AE_SECTION. These are required on AE Programs which have dynamic Call Section Actions, as the values in these fields will control what AE Step is called next — either in the current program or something outside.