Comments

  • Hemanth Lakkaraju

    I think at the moment, the only way is to get the authentication token *by some means* and use it in OIC. You may try out Javascript functions, if there is a support!

  • Hemanth Lakkaraju

    I believe param declaration should be above the template start. Also are you sure the $Base64_assign_1 has valid xml content? The parseXML is failing because it cannot find a xml tag. If it is xml content, can you try replacing parseXML with parseEscapedXML and see?

  • Hemanth Lakkaraju

    The wsdl defines the request and response to use a namespace and so the mapper expects it. Your target service seems to send response without namespace in body (looking at the soap envelope you posted). This is clear violation of wsdl contract. So when the response is applied on mapper, the mapper can't recognize the source and it fails. The service should response with namespace.

  • Hemanth Lakkaraju

    Not sure what/how you configured in the old flow. See if you can remember and reproduce the issue, let me know!

  • Hemanth Lakkaraju

    Not reproducible. I can see the required elements. Can you create a new invoke in the same flow with same connection and see if it displays?

  • Hemanth Lakkaraju

    Not sure I understand. The question is how did you configure the adapter using the connection.

  • Hemanth Lakkaraju

    This is the request XSL, your problem seems to be in response XSL. The request is using namespace

    xmlns:ns0="www.dha.gov.ae"

    I assume the response might also have the same, but the actual soap response does not have any!

    <soapenv:Body>
          <getApplicationStatusResponse>
             <applicationStatus>In Process</applicationStatus>
          </getApplicationStatusResponse>
       </soapenv:Body>

    The expected response must be 

    <getApplicationStatusResponse xmlns="www.dha.gov.ae">
             <applicationStatus>In Process</applicationStatus>
          </getApplicationStatusResponse>

  • Hemanth Lakkaraju

    Your XSLT doesn't define the variable as a parameter and the error is genuine. Actually there are 2 errors:

    1. NetwokCSVExport is not defined as a parameter to XSLT.
    2. copy-of statement uses Base64_assign_1 variable incorrectly. It should be used with $Base64_assign_1.

    Moreover, all this is not needed to write the report data from BIP to stage file. BIP response will have the base64encoded data in response (reportBytes element). You can simply use opaque schema to write to stage directory and map the reportBytes element to opaque element, which will write to stage file! You need this approach to read the stage file, but with above mentioned corrections!

  • Hemanth Lakkaraju

    Your subject says file adapter but you are using FTP - both are different! Probably, you misunderstood the fields and their usage.

    1. Header is not displayed even after "Use first row as header" option

    This option just tells you first record in the file contains headers - for sampling, to show in the UI. for read, to list out them as column names and for write, you have to explicitly write the headers first and then write the data because during runtime, you map only the data and not headers so when the file is first written it is not aware of what header values are!

    I have a field named first name and it is string and it can have (,) comma in the data, even though i have selected optionally enclosed by " my data is not enclosed by ".

    Not sure I understand your expectation here. A column value having comma, splits the record as per csv structure. Selecting optionally enclosed by "", tells parser that the column value may be enclosed in quotes. Are you passing value for a column with comma enclosed in quotes and that is not written to file?

  • Hemanth Lakkaraju

    This is how a connection is created. I'm how the connection is used in the integration.

  • Hemanth Lakkaraju

    You should tell how the connection is configured also to understand the problem. Is this configured as a callback invoke?

  • Hemanth Lakkaraju

    It is GA, FF is not required.

  • Hemanth Lakkaraju

    You should tell the complete usecase before you mention *there is an issue here*. The SOAP response doesn't have any namespace associated with the body elements - getApplicationStatusResponse and mapper doesn't work without namespaces. So the configuration you did must be expecting a namespace in the mapper which your invoke response is not giving and the map fails.

    Either your modelling is incorrect or the way the service behaves is incorrect! Just wondering which rest service on earth would return a soap envelope! :)

  • Hemanth Lakkaraju

    How did you transform? Which tool you have used? It could be a problem with the tool/transformation logic as well? What's you sampling for this request look like in REST Adapter? Are you able to see a repeating element for formActions, gridRowEvents, gridColumnEvents in mapping? Can you share the screenshot of mapping/configuration/the schema generated?

    You can use stage action to write same json sample to a file, read opaquely, decode and see how the actual json looks like in OIC.

  • Hemanth Lakkaraju

    Normally, the encodings are considered platform default unless specified. Are you using csv write or xml write? I believe for csv you'll have an option to specify the encoding type based on sampled data. So, in this case, it may be the client/tool you are using to look the data in the file as well may be problematic.