WS BASE64 GET METHOD

RE: WS BASE64 GET METHOD

Steven Miccile — Mon, 01 Jul 2019 15:51:08 GMT

I am not sure what you mean by "http download component and then using Base64 json Doc to binary", but I am still referring to the Base64 Request to Rest Web Service plugin. You saw that errrorlog=Changed to Local Appian Error: null Local Appian Error: null. The next troubleshooting step is to look at the application server log. You will not be able to troubleshoot without it.

RE: WS BASE64 GET METHOD

guadalupej0001 — Mon, 01 Jul 2019 15:24:36 GMT

Hi, I set the content type in headers but I'm having the same error, I can´t see the logs but I tried downloading the base64 in a file with the http download component and then using Base64 json Doc to binary and I have an error "java.lang.nullpointerexception" (in logs).

I think that my base64 string it's ok, and I tried with more strings , empty file, and nothing works.

RE: WS BASE64 GET METHOD

Steven Miccile — Fri, 28 Jun 2019 19:31:01 GMT

Well the content type changed from "text/plan;charset=ISO-8859-1" to "application/json;charset=UTF-8" which is a step forward. Did you check the logs for a stacktrace on the error?

RE: WS BASE64 GET METHOD

guadalupej0001 — Wed, 26 Jun 2019 00:13:02 GMT

My team did the change today 🙂

This is the response

Value

Dictionary success: true result: HttpResponse statusLine: "HTTP/1.1 200 " statusCode: 200 headers: Dictionary Content-Type: "application/json;charset=UTF-8" Transfer-Encoding: "chunked" Date: "Tue, 25 Jun 2019 23:18:20 GMT" Set-Cookie: "2fda0f841098fcd74d7c1f0e5a1e16ce=cddacee4b606584a58d5a087c2d642e9; path=/; HttpOnly; Secure" contentType: "application/json;charset=UTF-8" body: "{"respuesta":"A001","codigoBase64":"JVBERi0xLjUNCiW1tbW1DQoxI........

and i configured this entries

Endpoint:

="">transversalservice-aperturabei-destdoc-dev.appls.cto1.paas.gsnetcloud.corp/.../base64"

Method:

=POST

Request Body:

="{ ""canal"":""CANAL DIGITAL"", ""appOrigen"":""APERTURA DE CUENTAS"", ""nivel"":""PMN1"", ""tipoDocumento"":"""", ""tipoConsulta"":""B64"", ""tipoOper"":""A"", ""parametros"":[ { ""filenet"":""morales"", ""idDocumento"":""A089E56A-0000-CD17-970C-4FE9ED4F6C85"" } ]}"

Document Json Path:

="codigoBase64"

File Name:

="archivo.txt"

Folder:

"TMP_From_WS"

But I have an error, but I don't know which is

the errorocurred=true

the errrorlog=Changed to Local Appian Error: null Local Appian Error: null

Any help???

Thanks

RE: WS BASE64 GET METHOD

guadalupej0001 — Tue, 25 Jun 2019 19:04:51 GMT

ok, thanks

I'll tell you how everything goes.

Thanks!!!!!!

RE: WS BASE64 GET METHOD

Steven Miccile — Tue, 25 Jun 2019 19:02:57 GMT

Correct. And if the body for example becomes:

{"document":"jkasjkdjkajksdhkjahdsajkshdjaksdhajkshdaskjhdakjh"}

then the node input called "Document JSON Path" becomes "document"

RE: WS BASE64 GET METHOD

guadalupej0001 — Tue, 25 Jun 2019 18:59:15 GMT

I think the same, I made a request to the programmer maybe on thursday could be done the change, until that I suppose I have to wait.

RE: WS BASE64 GET METHOD

Steven Miccile — Tue, 25 Jun 2019 18:55:18 GMT

That's rather strange. JSON is generally name/value pairs:

https://www.w3schools.com/js/js_json_syntax.asp

Since yours is not, I would not be surprised if the plugin is not designed to work for this edge case, which is what the error message is indicating.

Can the service be changed to have a name/value pair as the response body?

RE: WS BASE64 GET METHOD

guadalupej0001 — Tue, 25 Jun 2019 18:48:57 GMT

It's correct in the body is the only thing, the base64 string

RE: WS BASE64 GET METHOD

Steven Miccile — Tue, 25 Jun 2019 18:47:11 GMT

I'm most interested in the "body". Is "jkasjkdjkajksdhkjahdsajkshdjaksdhajkshdaskjhdakjh" meant to represent the fact that the body just contains the base64 string? Is that the only thing in the response body? No labels? Other fields?

RE: WS BASE64 GET METHOD

guadalupej0001 — Tue, 25 Jun 2019 18:38:25 GMT

SOMETHING LIKE THIS

Dictionary

success:true

result:HttpResponse

statusLine:"HTTP/1.1.200"

statusCode:200

headers:Dictionary

contentType:"text/plan;charset=ISO-8859-1"

ContentLenght:"1420552"

Date:SOMETHIG

Setcookie:"ASDJASLDJI28478JK"

contenttype:":"text/plan;charset=ISO-8859-1"

...

body: "jkasjkdjkajksdhkjahdsajkshdjaksdhajkshdaskjhdakjh"

RE: WS BASE64 GET METHOD

Steven Miccile — Tue, 25 Jun 2019 18:32:00 GMT

The error message indicates that the plugin is expecting a JSON response body, but did not find a valid one.

body: "jkasjkdjkajksdhkjahdsajkshdjaksdhajkshdaskjhdakjh"

What more specifically is the structure of the response body?

RE: WS BASE64 GET METHOD

guadalupej0001 — Tue, 25 Jun 2019 18:23:50 GMT

Thanks Steven,

I'm trying with Base64 Request to Rest Web Service plugin with the smart service "http json multidocument WS"

I have:

endpoint like "https://transversal..../consultar/base64"

method:post

request body: "{ ""value"": ""1""}"

but when I execute the process i got an error

errorocurred=true

errorlog= "the response did not include valid JSON Local Appian Error: null"

when I execute the Ws it returns something like this

contentType: "text/plain:charset=ISO-8859-1"

body: "jkasjkdjkajksdhkjahdsajkshdjaksdhajkshdaskjhdakjh"

Any help??

RE: WS BASE64 GET METHOD

Steven Miccile — Tue, 25 Jun 2019 13:58:25 GMT

As of 19.2, Appian has this out of the box with the Integration Object and the limit for a response with documents is 75mb.

https://docs.appian.com/suite/help/19.2/Appian_Release_Notes.html#receive-binary-with-integrations-and-receive-base64-inline-with-json

https://docs.appian.com/suite/help/19.2/Integration_Object.html

Before this, I have used the Base64 Request to REST Web Service plugin to turn base64 in a WS response directly into an Appian document. I don't know if there are any limits on this one.

https://community.appian.com/b/appmarket/posts/base64-request-to-rest-web-service

RE: WS BASE64 GET METHOD

venusaikumarc378 — Thu, 20 Jun 2019 23:59:57 GMT

Hi guadalupej0001,

One of the commenter in above post, upload the base64ToDoc-Appian.zip plug-in. if you are in on-premise you can deploy and use it. if it is in Cloud, you have request appian support.

RE: WS BASE64 GET METHOD

guadalupej0001 — Thu, 20 Jun 2019 22:46:39 GMT

Oracle database,

RE: WS BASE64 GET METHOD

Robert Shankin — Thu, 20 Jun 2019 22:25:46 GMT

Don't use Text. That's not appropriate for a string that large. use a blob, clob, longtext or similar.

what type of database is it?

RE: WS BASE64 GET METHOD

guadalupej0001 — Thu, 20 Jun 2019 22:10:28 GMT

Hi, I'm trying that component Get Base64 Document from Database

My problem is the length, my base64 string is too long (14,000,000)

RE: WS BASE64 GET METHOD

Robert Shankin — Thu, 20 Jun 2019 21:24:46 GMT

https://community.appian.com/b/appmarket/posts/base64-document-database-integration

I have used this component before to transform base64 strings in the database into appian documents.

RE: WS BASE64 GET METHOD

guadalupej0001 — Thu, 20 Jun 2019 21:21:13 GMT

Thanks Robert I'm going to try it, I'll tell you what happend

RE: WS BASE64 GET METHOD

guadalupej0001 — Thu, 20 Jun 2019 21:14:02 GMT

Hello Venu, that component is not available, another idea???

Thanks!!!

RE: WS BASE64 GET METHOD

Robert Shankin — Thu, 20 Jun 2019 19:23:52 GMT

Instead of a text datatypes in the data base, try something like "long" which has more space. Please use caution in your database accumulating too many long values. Plan to delete the base64 strings out of the db as soon as you've converted them back into files.

RE: WS BASE64 GET METHOD

Venu — Thu, 20 Jun 2019 01:00:36 GMT

Hi guadalupej0001,

You can sue the smart service Appian Document from Base64 String to do your job.

Below post may help you.

https://community.appian.com/discussions/f/integrations/13208/base-64-to-document/59846#59846

Thanks,

Venu.