Scribd
Upload
414 views11 pages

NOFILE Enquiry and WSDL Configuration Guide

This document provides instructions for configuring a NOFILE enquiry using the TEST.PUBLISHENQ routine, including: 1. Identifying the relevant STANDARD.SELECTION, ENQUIRY, and DFE.CONNECTOR.DETAILS records 2. Specifying the correct SOAP.ACTION in the DFE.PARAMETER record 3. Mapping the CUSTOMER.XML request to the web service using DFE.MAPPING and CUSTOMER.XSLT

Uploaded by

Emmanuel Uchenna Chukwu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
414 views11 pages

NOFILE Enquiry and WSDL Configuration Guide

This document provides instructions for configuring a NOFILE enquiry using the TEST.PUBLISHENQ routine, including: 1. Identifying the relevant STANDARD.SELECTION, ENQUIRY, and DFE.CONNECTOR.DETAILS records 2. Specifying the correct SOAP.ACTION in the DFE.PARAMETER record 3. Mapping the CUSTOMER.XML request to the web service using DFE.MAPPING and CUSTOMER.XSLT

Uploaded by

Emmanuel Uchenna Chukwu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
  • Nofile Enquiry Standard Selection
  • Enquiry Record Details
  • File Class Integration
  • Web Service Connector Details
  • SOAP Action Retrieval
  • Customer XML Mapping
  • XSLT Configuration
  • Browser Enquiry Output

1. STANDARD.

SELECTION record of the NOFILE enquiry

2. Corresponding NOFILE routine used – [Link]


3. ENQUIRY record – [Link]

4. TShow of the NOFILE routine from classic


5. Copy the class file generated in any jar file in order to reflect the same in TAFJEE servlet.

6. [Link] record – WEBSERVICE


7. [Link] record – WEBSERVICE

Note:

The value in the field [Link] is the mock wsdl service created from the TWS project.

Cause of the Error in received Server log:

Error:

[Link],178 INFO [stdout] (http-/[Link]:8080-1) [Link],178 [[Link]]


ERROR - Err:014:IOException:[Link]: Server returned HTTP response code: 500 for URL:
[Link]

[Link],194 ERROR [stderr] (http-/[Link]:8080-1) [Link]: Server returned HTTP response


code: 500 for URL: [Link]

[Link],205 ERROR [stderr] (http-/[Link]:8080-1) at


[Link].getInputStream0([Link])

Reason:

The above error will occur if the [Link] field in [Link] is not provided/has an incorrect
value. So correct value should be provided. A sample is shown below.
How to retrieve value of [Link] field:

The value in the field [Link] should be provided as below which can be retrieved from the “WS-
Addressing related settings” tab Action value in SOAP UI as below.
8. [Link] record – [Link]
9. [Link] – [Link]
Value of the field [Link]:

TWS WSDL output:

Note:

The error “[Link],882 ERROR [stderr] (http-/[Link]:8080-1) SystemId Unknown; Line #-1; Column #-1;
Premature end of file.” will occur if the corresponding XSLT is not correctly mapped with the created
web service using TWS.

Check the TWS WSDL in order to correct the existing [Link] to avoid the Premature end of file
error. A sample for the local nofile enquiry is attached above.

Enquiry output from tSS prompt:


Enquiry output from Browser:

1. STANDARD.SELECTION record of the NOFILE enquiry 2. Corresponding NOFILE routine used – TEST.PUBLISHENQ
3. ENQUIRY record – NOFILE.DFE.TEST 4. TShow of the NOFILE routine from classic
5. Copy the class file generated in any jar file in order to reflect the same in TAFJEE servlet. 6. DFE.CONNECTOR.DETAILS rec
7. DFE.PARAMETER record – WEBSERVICE Note: The value in the field WSDL.URL is the mock wsdl service created from the TWS proj
How to retrieve value of SOAP.ACTION field: The value in the field SOAP.ACTION should be provided as below which can be retri
8. DFE.MAPPING record – CUSTOMER.XML
9. DFE.TRANSFORM – CUSTOMER.XSLT
Value of the field XSLT.MAPPING: TWS WSDL output: Note: The error “08:42:46,882 ERROR [stderr] (http-/0.0.0.0:8080-1) SystemI

You might also like